US20150032845A1 - Packet transmission protocol supporting downloading and streaming - Google Patents

Packet transmission protocol supporting downloading and streaming Download PDF

Info

Publication number
US20150032845A1
US20150032845A1 US14/178,212 US201414178212A US2015032845A1 US 20150032845 A1 US20150032845 A1 US 20150032845A1 US 201414178212 A US201414178212 A US 201414178212A US 2015032845 A1 US2015032845 A1 US 2015032845A1
Authority
US
United States
Prior art keywords
transport packet
type
payload
mpu
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/178,212
Other languages
English (en)
Inventor
Imed Bouazizi
Youngkwon Lim
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to US14/178,212 priority Critical patent/US20150032845A1/en
Assigned to SAMSUNG ELECTRONICS CO., LTD reassignment SAMSUNG ELECTRONICS CO., LTD ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BOUAZIZI, IMED, LIM, YOUNGKWON
Priority to CN201911248319.5A priority patent/CN111049820B/zh
Priority to MX2016001137A priority patent/MX356847B/es
Priority to AU2014293819A priority patent/AU2014293819B2/en
Priority to CN201480042072.0A priority patent/CN105409174B/zh
Priority to CN201911248313.8A priority patent/CN110830511B/zh
Priority to BR112016001661-0A priority patent/BR112016001661B1/pt
Priority to KR1020140094980A priority patent/KR101530825B1/ko
Priority to EP21156204.6A priority patent/EP3840313A1/en
Priority to ES14828733T priority patent/ES2878022T3/es
Priority to PCT/KR2014/006829 priority patent/WO2015012645A1/en
Priority to EP14828733.7A priority patent/EP3025464B1/en
Priority to JP2015535594A priority patent/JP5883199B2/ja
Priority to MYPI2016700246A priority patent/MY174260A/en
Priority to KR1020150000130A priority patent/KR102015963B1/ko
Publication of US20150032845A1 publication Critical patent/US20150032845A1/en
Priority to MX2018007146A priority patent/MX2018007146A/es
Priority to JP2016020212A priority patent/JP6106775B2/ja
Priority to JP2017042254A priority patent/JP6346329B2/ja
Priority to JP2018099982A priority patent/JP6526289B2/ja
Priority to KR1020190103570A priority patent/KR102127733B1/ko
Priority to US16/805,608 priority patent/US11637887B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/70—Media network packetisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/234—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
    • H04N21/23424—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving splicing one content stream with another content stream, e.g. for inserting or substituting an advertisement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/633—Control signals issued by server directed to the network components or client
    • H04N21/6332—Control signals issued by server directed to the network components or client directed to client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Definitions

  • the present application relates generally to media data transmission and, more specifically, to a packet transmission protocol that supports both downloading and streaming.
  • Moving Picture Experts Group (MPEG) media transport is a digital container standard or format that specifies technologies for the delivery of coded media data for multimedia service over heterogeneous IP network environments.
  • the delivered coded media data includes both audiovisual media data requiring synchronized decoding and presentation of a specific unit of data in a designated time, namely timed data, and other types of data that are decoded and presented in an arbitrary time based on the context of service or interaction by the user, namely non-timed data.
  • GFD Generic File Delivery
  • Embodiments of the present disclosure provide a method and apparatus generate and process transport packets using a packet transmission protocol capable of supporting downloading and streaming.
  • a method of processing a transport packet at receiving entity includes identifying, in response to receiving the transport packet, a payload type based on a field indicating the payload type in a packet header for the transport packet.
  • the method also includes identifying, in response to identifying that the payload type is a streaming mode payload type, a delivery data unit type of data unit (DU) data in the transport packet based on a field indicating the delivery data unit type in a streaming mode payload header for the DU data.
  • the method includes processing the DU data according to the identified delivery data unit type.
  • a method of generating a transport packet by a sending entity includes generating the transport packet to include an identifier of a payload type in a field indicating the payload type in a packet header for the transport packet.
  • the method also includes including, when the payload type is an streaming mode payload type, an identifier of a delivery data unit type of DU data for the transport packet in a field indicating the delivery data unit type in a streaming mode payload header for the DU data. Additionally, the method includes sending the transport packet.
  • an apparatus in a receiving entity capable of processing a transport packet includes a receiver configured to receive the transport packet. Additionally, the apparatus includes processing circuitry configured to identify a payload type based on a field indicating the payload type in a packet header for the transport packet, identify, in response to identifying that the payload type is an streaming mode payload type, a delivery data unit type of DU data in the transport packet based on a field indicating the delivery data unit type in a streaming mode payload header for the DU data, and process the DU data according to the identified delivery data unit type.
  • an apparatus in a sending entity capable of generating a transport packet includes processing circuitry configured to generate the transport packet to include an identifier of a payload type in a field indicating the payload type in a packet header for the transport packet, and include, when the payload type is an streaming mode payload type, an identifier of a delivery data unit type of DU data for the transport packet in a field indicating the delivery data unit type in a streaming mode payload header for the DU data.
  • the apparatus includes a transmitter configured to send the transport packet.
  • FIG. 1 illustrates an example of a transmission system in which various embodiments of the present disclosure may be implemented
  • FIG. 2 illustrates an MMT Package and the logical structure of the MMT Package in accordance with various embodiments of the present disclosure
  • FIG. 3 illustrates an example of timing provided by a presentation information document for presentation of MPUs from different assets in accordance with an illustrative embodiment of the present disclosure
  • FIG. 4 illustrates an exemplary structure for a streaming mode payload header in accordance with various embodiments of the present disclosure
  • FIG. 5 illustrates an exemplary structure for a timed media fragment unit (MFU) header in accordance with various embodiments of the present disclosure
  • FIG. 6 illustrates an exemplary structure for a non-timed MFU header in accordance with various embodiments of the present disclosure
  • FIG. 7 illustrates an exemplary structure for a signaling message header in accordance with various embodiments of the present disclosure
  • FIG. 8 illustrates an exemplary structure for a GFD mode packet structure in accordance with various embodiments of the present disclosure
  • FIG. 9 illustrates an exemplary structure for an MMTP packet in accordance with various embodiments of the present disclosure.
  • FIG. 10 illustrates an exemplary structure for header extension in accordance with various embodiments of the present disclosure
  • FIG. 11 illustrates an exemplary diagram of packetization of timed media data in accordance with various embodiments of the present disclosure
  • FIG. 12 illustrates an exemplary diagram of packetization of non-timed media data in accordance with various embodiments of the present disclosure
  • FIG. 13 illustrates a process for processing a transport packet at a receiving entity in accordance with an illustrative embodiment of the present disclosure
  • FIG. 14 illustrates a process for generating a transport packet at a sending entity in accordance with an illustrative embodiment of the present disclosure
  • FIGS. 1 through 15 discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.
  • the delivery functional area defines the application layer protocol and format of the payload.
  • the application layer protocol provides enhanced features, including multiplexing, for delivery of the MMT package compared to conventional application layer protocols for the delivery of multimedia.
  • the payload format is defined to carry coded media data that is agnostic to the specific media type or encoding method.
  • the signaling functional area defines the format of messages to manage delivery and consumption of MMT packages. Messages for consumption management are used to signal the structure of the MMT package and messages for delivery management are used signal the structure of payload format and configuration of the protocol.
  • MMT defines a new framework for delivery of time continuous multimedia such as audio, video and other static content such as widgets, files etc.
  • MMT specifies a protocol (i.e., MMTP) for the delivery of an MMT package to a receiving entity.
  • the MMTP signals transmission time of the MMTP package as part of the protocol header. This time enables the receiving entity to perform de-jittering by examining the transmission time and reception time of each incoming MMT packet.
  • Embodiments of the present disclosure recognize that a new packetization mode, the GFD mode, has been introduced to the MMT delivery function. GFD enables the transmission of any generic file.
  • Embodiments of the present disclosure recognize that presently MMT defines 4 other packetization modes: the media processing unit (MPU) mode, the MPU Fragment mode, Signaling Message mode, and forward error correction (FEC) mode.
  • the MPU mode delivers a complete MPU and leaves fragmentation to the transport layer.
  • the MPU Fragment mode is optimized for MPU delivery and packetization is performed in a media-aware manner, informing the receiving client about the MPU fragment type and characteristics.
  • the FEC and signaling modes are for delivering FEC repair packets and signaling messages, respectively.
  • Embodiments of the present disclosure recognize that the MPU mode may be seen as a sub-case of the GFD mode, since the whole MPU is delivered as an object and without any media-aware packetization.
  • the information about the MPU can be fully delivered as part of the metadata of the object in the GFD mode. Consequently, embodiments of the present disclosure provide to remove the MPU mode and rename the MPU Fragment mode into the MPU mode for disambiguation.
  • an MPU may be delivered either as a generic object using the GFD mode or as a set of independent fragments using this MPU mode.
  • Embodiments of the present disclosure recognize that presently the payload format of a packet is split over multiple layers. A main payload header is needed for each payload format and has a one-to-one mapping to the MMTP protocol header. Embodiments of the present disclosure recognize to merge this generic payload header with the MMTP protocol header and make the remaining payload headers dependent on the payload type. For example, fragmentation and aggregation are also dependent on the payload type, as some payload types, e.g. FEC and GFD, do not require aggregation and fragmentation. Embodiments of the present disclosure further provide a payload type for signaling messages enable easy identification of signaling messages and updates. The payload format will also enable aggregation and fragmentation of signaling messages.
  • FIG. 1 illustrates an example of a transmission system 100 in which various embodiments of the present disclosure may be implemented.
  • wireless system 100 includes a sending entity 101 , a network 105 , receiving entities, 110 - 116 , wireless transmission points (e.g., an Evolved Node B (eNB), Node B), such as base station (BS) 102 , base station (BS) 103 , and other similar base stations or relay stations (not shown).
  • Sending entity 101 is in communication with base station 102 and base station 103 via network 105 which may be, for example, the Internet, a media broadcast network, or IP-based communication system.
  • Receiving entities 110 - 116 are in communication with sending entity 101 via network 105 and/or base stations 102 and 103 .
  • receiving entities 110 - 116 may receive media data for downloading and streaming from sending entity 101 .
  • the sending entity 101 may generate and send MMTP packets and one or more of the receiving entities 110 - 116 may receive and process the MMTP packets in accordance with the teachings of present disclosure.
  • Base station 102 provides wireless access (via base station 101 ) to network 105 to a first plurality of receiving entities (e.g., user equipment, mobile phone, mobile station, subscriber station) within coverage area 120 of base station 102 .
  • the first plurality of receiving entities includes user equipment 111 , which may be located in a small business (SB); user equipment 112 , which may be located in an enterprise (E); user equipment 113 , which may be located in a WiFi hotspot (HS); user equipment 114 , which may be located in a first residence (R); user equipment 115 , which may be located in a second residence (R); and user equipment 116 , which may be a mobile device (M), such as a cell phone, a wireless communication enabled laptop, a wireless communication enabled PDA, a tablet computer, or the like.
  • M mobile device
  • Base station 103 provides wireless access to network 105 to a second plurality of user equipment within coverage area 125 of base station 103 .
  • the second plurality of user equipment includes user equipment 115 and user equipment 116 .
  • base stations 101 - 103 may communicate with each other and with user equipment 111 - 116 using OFDM or OFDMA techniques.
  • system 100 may provide wireless broadband and network access to additional user equipment. It is noted that user equipment 115 and user equipment 116 are located on the edges of both coverage area 120 and coverage area 125 . User equipment 115 and user equipment 116 each communicate with both base station 102 and base station 103 and may be said to be operating in handoff mode, as known to those of skill in the art.
  • User equipment 111 - 116 may access media data voice, data, video, video conferencing, and/or other services via network 105 .
  • one or more of user equipment 111 - 116 may be associated with an access point (AP) of a WiFi WLAN.
  • User equipment 116 may be any of a number of mobile devices, including a wireless-enabled laptop computer, personal data assistant, notebook, handheld device, or other wireless-enabled device.
  • User equipment 114 and 115 may be, for example, a wireless-enabled personal computer (PC), a laptop computer, a gateway, or another device.
  • FIG. 2 illustrates an MMT Package 200 and the logical structure of the MMT package 200 in accordance with various embodiments of the present disclosure.
  • the MMT package 200 includes presentation one or more information documents 205 and one or more assets 210 that may have associated transport characteristics 215 .
  • An asset 210 is a collection of one or more media processing units (MPUs) 220 that share a same asset identification (ID).
  • An asset 210 includes encoded media data such as audio or video, or a web page. The media data can be either timed or non-timed.
  • Presentation information (PI) documents 205 include information specifying the spatial and temporal relationship among the assets 210 for consumption.
  • the combination of hypertext markup language (HTML) and composition information (CI) documents are examples of PI documents 205 .
  • a PI document 205 may also be used to determine a delivery order of assets 210 in a package 200 .
  • a PI document 205 is delivered either as one or more messages or as a complete document. In the case of broadcast delivery, service providers may circulate presentation information documents 205 sequentially and determine a frequency at which circulation is to be performed.
  • An asset 210 is any multimedia data to be used for building a multimedia presentation. As discussed above, an asset 210 is a logical grouping of MPUs that share a same asset ID for carrying encoded media data. Encoded media data of an asset 210 can be either timed data or non-timed data. Timed data are encoded media data that have an inherent timeline and may require synchronized decoding and presentation of the data units at a designated time. Non-timed data are other types of data that can be decoded at an arbitrary time based on the context of a service or indications from the user.
  • MPUs 220 of a single asset 210 have either timed or non-timed media. Two MPUs 220 of the same asset 210 carrying timed media data may have no overlap in their presentation time. In the absence of a presentation indication, MPUs 220 of the same asset 210 may be played back sequentially according to their sequence numbers. Any type of media data which can be individually consumed by the presentation engine of an MMT receiving entity may be considered as an individual asset 210 . Examples of media data types which can be considered as an individual asset 210 are audio, video, or a web page media data types.
  • An MPU 220 is a media data item that may be processed by an MMT entity and consumed by a presentation engine independently from other MPUs 220 .
  • Processing of an MPU 220 by an MMT entity includes encapsulation/decapsulation and packetization/depacketization.
  • Consumption of an MPU 220 includes media processing (e.g. encoding/decoding) and presentation.
  • an MPU 220 may be fragmented into data units that may be smaller than an access unit (AU).
  • AU access unit
  • An MPU 220 may include a portion of data formatted according to other standards, e.g. MPEG-4 advanced video coding (AVC) or MPEG-2 transport stream (TS).
  • AVC advanced video coding
  • TS MPEG-2 transport stream
  • the media intervals defined by the ‘sidx’ box is non-overlapping, (i.e. no media sample in the k th media interval (defined by the ‘sidx’ box) in an MPU is inside the time interval defined by the sample boundaries of the j th media time interval (defined by the ‘sidx’ box) for ‘j’ different from ‘k’.
  • the concatenation of the j th MPU of the MPU of Asset with asset_id ‘Y’ with the j th MPU of the asset with asset_id ‘X’ without MPU metadata results in a valid MPU.
  • a single MPU includes an integral number of AUs or non-timed data. In other words, for timed data, a single AU is not fragmented into multiple MPUs. For non-timed data, a single MPU includes one or more non-timed data items to be consumed by presentation engine. An MPU is identified by an associated asset_id and a sequence number.
  • An MPU that includes timed media includes at least one stream access point (SAP) as defined in Annex I of ISO/IEC 14496-12, which is incorporated by reference herein.
  • the first access unit of an MPU is a SAP for processing by an MMT entity. For timed media, this implies that the decoding order of the first AU in the MPU payload is ‘0’.
  • the MPU payload starts with the information necessary for the processing of such a format. For example, if an MPU includes video data, the MPU payload includes one or more groups of pictures and the decoder configuration information required to process them.
  • the MPU payload may start with TS packets including program association table (PAT) program map table (PMT) for the remaining or subsequent TS packets.
  • PAT program association table
  • PMT program map table
  • the presentation duration, the decoding order, and the presentation order of each AU are signaled as part of the MPU metadata.
  • the MPU does not have an initial presentation time.
  • the presentation time of the first AU in an MPU is described by the PI document.
  • the PI document includes information specifying the initial presentation time of each MPU.
  • FIG. 3 illustrates an example of timing provided by a PI document for presentation of MPUs from different assets in accordance with an illustrative embodiment of the present disclosure.
  • the PI document specifies that the MMT receiving entity shall present MPU #1 of Asset #1 and of Asset #2 simultaneously. At a later point, MPU #1 from Asset #3 is scheduled to be presented. Finally, MPU #2 of Asset #1 and Asset #2 are to be presented in synchronization.
  • the specified presentation time for an MPU defines the presentation time of the first AU of that MPU.
  • An MPU that contains non-timed media data may designate one data item as the entry point.
  • MFUs enable media-aware fragmentation of an MPU for transportation purposes. This allows an MMT sending entity to perform fragmentation of MPUs with consideration for consumption at the receiving end.
  • An MFU includes a media data unit, that may be smaller than an AU for timed media data, and the included media data may be processed by the media decoder.
  • An MFU includes an MFU header that includes information on the boundaries of the carried media data. The syntax and semantics of MFU are independent of the type of media data carried in the MFU. If the size of an MFU is bigger than the size of a link layer frame, an MFU may be fragmented into multiple link layer frames.
  • An MFU includes an identifier to distinguish one MFU from another in the same MPU as well as relationship information among MFUs within a single AU in a manner that is agnostic to the encoded media format.
  • the dependency relationship among MFUs in a single AU is described as are the relative priorities of MFUs.
  • the information can be used by underlying delivery layers for enhanced delivery. For example, the delivery layer can skip delivery of discardable MFUs to support QoS under certain circumstances, e.g. insufficient bandwidth on certain links in the network.
  • an MMT payload is a generic payload used to packetize and carry assets, generic objects, and other information for consumption of a MMT package using the MMT protocol (MMTP).
  • the MMT payload may be used to packetize MPUs, generic objects, and signaling messages.
  • the MMT payload may carry fragments of MPUs, signaling messages, generic objects (including complete MPUs), repair symbols, etc.
  • the type of the payload is indicated by the type (or object type) field in the MMTP packet header, as will be discussed in greater detail with the discussion of FIG. 9 below. For each payload type, a single data unit for delivery, as well as a type specific payload header, are defined.
  • a fragment of an MPU (e.g. an MFU) is considered as a single data unit when MMT payload carries MPU fragments.
  • the MMT protocol may aggregate multiple data units with the same data type into a single payload. It can also fragment a single data unit into multiple packets.
  • the MMT payload consists of a payload header and payload data.
  • Some data types may allow for fragmentation and aggregation, in which case, a single data unit is split into multiple fragments or a set of data units are delivered in a single packet.
  • Each data unit may have its own payload header depending on the type of the payload. For types that do not require a payload type-specific header no payload type header is present and the payload data follows the MMTP header.
  • Some fields of the MMTP packet are interpreted differently based on the payload type. The semantics of these fields are defined by the payload type in use.
  • FIG. 4 illustrates an exemplary structure for a streaming mode payload header 400 in accordance with various embodiments of the present disclosure.
  • the delivery of MPUs to MMT receivers using MMT protocol requires a packetization and depacketization procedure to take place at the sender and receiver, respectively, to enable the delivery of large MPUs.
  • the MPU delivery mode considers a complete MPU or specific subparts of a single MPU as independent delivery data units for packetization or aggregation to facilitate large variances of size of MPUs.
  • the streaming mode of MMTP payload format (e.g., MPU mode) allows fragmentation of single delivery data units into multiple MMTP payloads to support delivery of MPU with a large size.
  • the streaming mode also allows aggregation of multiple delivery data units with same type into a single MMTP payload, to cater for smaller data units.
  • the packetization procedure may transform an MPU into a set of MMTP payloads that are then carried in each MMTP packets when it is fragmented.
  • depacketization is performed to recover the original MPU data.
  • the MPU is fragmented in a media-aware manner allowing the transport layer to identify the nature and priority of the fragment that is carried.
  • a fragment of an MPU may be, for example, MPU metadata, or a Movie Fragment metadata, an MFU, or a non-timed data item.
  • This streaming mode is also used for the delivery of signaling messages or recovery symbols.
  • streaming mode payload header 400 semantics and length of each field of the streaming mode payload header 400 are provided as follows: length field 402 has a length of 16 bits and this field indicates the size of entire payload including this field; the delivery Data Unit Type (DU_type) field 404 is 5 bits long and indicates the delivery data unit type of the payload, for example, as provided by Table 1 below.
  • DU_type delivery Data Unit Type
  • Delivery Data Unit Types value Description Content 0 Complete a single complete MPU as a single delivery data unit MPU 1 MPU metadata the ftyp, mmpu, and moov boxes as well as any other boxes that appear in between as a single delivery data unit - no delivery data unit header is used 2 Movie the moof box and the mdat box, excluding all media data inside fragment the mdat box as a single delivery data unit. No delivery data unit metadata header is used 3 Timed_MFU a sample or sub-sample of timed media data as a single delivery data unit - delivery data unit header discussed with regard to FIG.
  • Non- an item of non-timed media data as a single delivery data unit - timed_MFU delivery data unit header discussed with regard to FIG. 6 may be used 5 Signaling a single complete signaling message as a delivery data unit. No message delivery data unit header is used - delivery data unit header discussed with regard to FIG. 7 may be used 6 Recovery a single complete recovery symbol as a delivery data unit - no symbols delivery data unit header is used. 7 ⁇ 11 Reserved
  • the aggregation_flag (A) field 406 is 1 bit long and when set to ‘1’ indicates that more than 1 delivery data unit is present in the payload that the f_i_field 408 is ignored; the fragmentation indicator (f_i) field 408 is 2 bits long and indicates the fragmentation indicator contains information about fragmentation of data unit in the payload, for example, as illustrated in Table 2 below.
  • Payload contains one or more delivery data unit headers and complete delivery data units. 01 Payload contains the delivery data unit header and the first fragment of delivery data unit 10 Payload contains a fragment of delivery data unit that is neither the first nor the last part. 11 Payload contains the last fragment of delivery data unit.
  • the value of this field 408 may be set to ‘00’ when the value of the field ‘A’ is set to ‘1’.
  • the counter (counter) field 410 is 16 bits, indicates a number of payload containing fragments of same delivery data unit succeeding this MMT payload if the aggregation_flag is set to ‘0’, and indicates the number of delivery data units aggregated in this payload if aggregation_flag is set to ‘1’.
  • the DU_length field 412 is 16 bits long and field indicates the length of the data following this field 412 . When aggregation_flag is set to ‘0’, this field 412 may not be present. When aggregation_flag is set to ‘1’, this field 412 may appear as many times as the value of the ‘counter’ field 410 and preceding each aggregated data unit.
  • the DU_Header field 414 is the header of the data unit, which depends on the type of delivery data unit, as will be discussed in greater detail below.
  • this field 414 may appear as many times as the value of the ‘counter’ field 410 and preceding each aggregated delivery data unit.
  • this field 414 may appear when the value of the ‘f_i’ field 408 is ‘01’.
  • FIG. 5 illustrates an exemplary structure for a timed-media MFU header 500 in accordance with various embodiments of the present disclosure.
  • the timed-media MFU header 500 is one example of delivery data unit header, such as included in the DU_header 414 in FIG. 4 , for timed media data.
  • the semantics and length of each field of the timed-media MFU header 500 are provided as follows: the movie_fragment_sequence_number field 502 is 32 bits long and includes the sequence number of the movie fragment to which the media data of this MFU belongs; the sample_number field 504 is 32 bits long and includes the sample number of the sample to which the media data of the MFU; the offset field 506 is 16 bits long and includes the offset of the media data of this MFU inside the referenced sample; the subsample_priority field 508 is 8 bits long and provides the priority of the media data carried by this MFU compared to other media data of the same MPU.
  • the value of subsample_priority may be between 0 and 455, with higher values indicating higher priority.
  • the dependency_counter field 510 is 8 bits long and indicates the number of data units that depend on their media processing upon the media data in this MFU.
  • FIG. 6 illustrates an exemplary structure for a non-timed MFU header 600 in accordance with various embodiments of the present disclosure.
  • the non-timed MFU header 600 is one example of delivery data unit header, such as included in the DU_header 414 in FIG. 4 , for non-timed media data.
  • the semantics and length of each field of the non-timed MFU header 600 are provided as follows: the Item_ID field 60 is 32 bits long and includes the identifier of the item that is carried as part of this MFU. For the file types (FTs) 0 and 1, no additional DU header may be available.
  • the object identifier field of the MMTP header may be set to the MPU_sequence_number of the MPU from which the data unit is extracted.
  • the random access point (RAP) flag may be set to mark data units of FT value 0 and 1 and for MFUs that contain a sync sample or a fragment thereof, in the case of timed media, and for the primary item of non-timed MPUs.
  • FIG. 7 illustrates an exemplary structure for a signaling message header 700 in accordance with various embodiments of the present disclosure.
  • the signaling message header 700 is one example of delivery data unit header, such as included in the DU_header 414 in FIG. 4 , for a signaling message.
  • the semantics and length of each field of the signaling message header 700 are provided as follows: the message_id field 702 is 16 bits long and indicates the type of the signaling message; the version field is 8 bits long and indicates the version number of the signaling message; the reserved (RES) field is 8 bits long and is reserved for future use and may be set to 0.
  • MMTP also supports the transport of generic files and assets and uses payload type 1.
  • a generic asset consists of one or more files that are logically grouped and that share some commonality for an application, e.g. Segments of a Dynamic Adaptive Streaming over HTTP (DASH) Representation, a sequence of MPUs, etc.
  • DASH Dynamic Adaptive Streaming over HTTP
  • GFD In the GFD payload type mode, a generic asset is delivered through MMTP using the GFD payload type.
  • GFD requires a GFD session description discussed below to describe the generic asset contents and delivery characteristics.
  • Embodiments of the present disclosure provide the establishment of GFD session over the MMTP protocol. When delivered within MMTP, GFD session may be mapped on exactly one packet_id flow.
  • Each file delivered within a GFD session requires association of transport delivery information. This includes, but is not limited to information such as the transfer length.
  • Each file delivered within a GFD session may also have associated content specific parameters such as name, identification, and/or location of the file, media type, size of the file, encoding of the file or message digest of the file.
  • content specific parameters such as name, identification, and/or location of the file, media type, size of the file, encoding of the file or message digest of the file.
  • each file within one generic asset may have assigned any meta-information about the entity-body, i.e. the delivered file. Additional details of the GFD operation discussed below.
  • the files delivered in a GFD session may have to be made available to an application, for example through a proxy cache or by other means. Each object is then delivered through the GFD session.
  • the receiver Before a receiver can establish a GFD session, the receiver may need to obtain sufficient information, such as, for example, session access information and GFD session Information.
  • the session access information for the GFD session when operating in MMT, is defined in 23008-1, which has been incorporated by reference herein.
  • the GFD session information is described in greater detail below.
  • the GFD Session Description could be in a form such as the Session Description Protocol (SDP) as defined in RFC4566, XML metadata as defined in RFC3023, or HTTP/MIME headers as defined in RFC2616, etc., each of these RFC standards documents are expressly incorporated by reference herein.
  • SDP Session Description Protocol
  • the GFD table provides a list of code points. Each code point is dynamically assigned a code point value. Semantics of the GFD Table are provided in Table 3 below.
  • the processing as described below regarding the content-location template may be used to generate the content-location and the value of the URI may be treated as the content-location field in the entity-header.
  • the processing as described below regarding the content-location template may be used to generate the content-location and the value of the URI may be treated as the content-location field in the entity-header.
  • code points may be defined.
  • the definition of code points may be dynamically setup in the GFD Session Description. An example of the semantics for the code point is provided in Table 4 below.
  • CodePoint defines the Code Points in a GFD session
  • value M defines the value of the code point in the GFD session as provided in the CP value of the GFD packet header. The value may be between 1 and 455. The value 0 is reserved.
  • @maximumTransferLength M specifies the maximum transfer length in bytes of any object delivered with this code point in this GFD session.
  • @constantTransferLength OD specifies if all objects delivered by this code default: point have constant transfer length. If this ‘false’ attribute is set to TRUE, all objects may have transfer length as specified in the @maximumTransferLength attribute.
  • @contentLocationTemplate O specifies a template to generate the Content- Location of the entity header.
  • EntityHeader 0 . . . 1 specifies a full entity header in the format as defined in RFC2616, section 9.1. The entity header applies for all objects that are delivered with the value of this code point.
  • M Mandatory
  • O Optional
  • OD Optional with Default Value
  • CM Conditionally Mandatory.
  • N unbounded
  • a code point may include a @contentLocationTemplate attribute.
  • the value of @contentLocationTemplate attribute may contain one or more of the identifiers as listed in Table 6 below.
  • the identifiers from Table 5 may be replaced by the substitution parameter defined in Table 5. Identifier matching is case-sensitive. If the URL contains unescaped $ symbols which do not enclose a valid identifier then the result of URL formation is undefined.
  • the format of the identifier is also specified in Table 6 below.
  • Each identifier may be suffixed, within the enclosing ‘$’ characters following this prototype: “%0[width]d”.
  • the “width” parameter is an unsigned integer that provides the minimum number of characters to be printed. If the value to be printed is shorter than this number, the result may be padded with zeros. The value may not be truncated even if the result is larger.
  • the @contentLocationTemplate may be authored such that the application of the substitution process results in valid URIs. Strings outside identifiers may only contain characters that are permitted within URLs according to RFC 3986, incorporated by reference herein.
  • GFD operation the GFD mode of MMTP delivers regular files.
  • the object represents a file. If the code point defined in the GFD Session description contains entity-header fields or entity-header fields that can be generated, then all of these entity-header fields may apply to the delivered file.
  • FIG. 8 illustrates an exemplary structure for a GFD mode packet structure 800 in accordance with various embodiments of the present disclosure.
  • the payload packets sent using MMTP may include a GFD payload header and a GFD Payload as illustrated in FIG. 8 .
  • a GFD sender may need to produce packets that do not contain any payload. This may be required, for example, to signal the end of a session.
  • the GFD payload header has a variable size.
  • all integer fields are carried in “big-endian” or “network order” format, that is, the most significant byte (octet) first. Bits designated as “padding” or “reserved” (r) are set to 0 by senders and ignored by receivers. Unless otherwise noted, numeric constants in these examples are in decimal form (base 10).
  • the mapping between the code point and the actual codec is defined on a per session basis and communicated out-of-band as part of the session description information.
  • the Object Metadata (M) field 814 is 1 bit long and this flag indicates whether the object metadata provided as part of the payload or not. When set to 1, the payload is MIME entity, where the header may contain at least the content-type and the content-location headers.
  • the reserved field (RES) is 3 bits long and is set to 0; the start_offset field 818 (16+32*O+16*H) indicates the location of the current payload data in the object; and the GFD payload field 820 includes the GFD payload.
  • the bytes of the object are referenced such that byte 0 is the beginning of the object and byte T ⁇ 1 is the last byte of the object with T the transfer length of the object.
  • the data carried in the payload of an MMTP packet may consist of a consecutive portion of the object starting from the beginning of byte X and ending at the beginning of byte X+Y where X is the value of start_offset field in the GFD packet header and Y is the length of the payload in bytes. Y may not be carried in the packet but framing may be provided by the underlying transport protocol.
  • the MMT protocol is an application layer transport protocol designed to efficiently and reliably deliver MMT packages.
  • MMTP can be used for delivery of both timed and non-timed media data. It supports several features, such as media multiplexing, network jitter calculation, which are essential to deliver content composed of various types of coded media data.
  • MMTP may run on top of the existing protocols, e.g. UDP and IP. In the present disclosure, a specific carriage of the data formatted other than MMT payload format as is required. A single MMTP packet may carry exactly one MMT payload.
  • MMTP assumes that the sending entity performs congestion control and thus congestion control function is not specified in this specification. This is because MMTP runs on top of UDP/IP and will be used by a wide variety of applications this function is left to implementation of sending entities.
  • MMTP supports the multiplexing of different assets over a single MMT packet flow. MMTP delivers multiple types of data in the order of consumption at the receiving entity to help the synchronization between different types of media data without introducing a large delay or requiring large buffer. MMTP also supports the multiplexing of media data and signaling messages within a single packet flow. A single MMT payload may be carried in only one MMT packet.
  • MMT protocol defines two packetization modes, GFD mode and MPU mode.
  • the GFD mode e.g., download mode
  • the MPU mode e.g., streaming mode
  • MMT protocol supports mixed use of packets with two different modes in a single delivery session.
  • a single packet flow of MMT packets can be arbitrary composed of payloads with two types.
  • MMTP provides the structure and definitions to calculate and remove jitter introduced by the underlying delivery network, so that constant delay for data stream can be achieved. By using the timestamp field in the packet header, jitter can be precisely calculated without requiring any additional signaling information and protocols.
  • FIG. 9 illustrates an exemplary structure for an MMTP packet 900 in accordance with various embodiments of the present disclosure.
  • the semantics and length of each field of the MMTP packet 900 are provided as follows: version (V) field 902 is 2 bits long and indicates the version number of the protocol. This field may be set to ‘00’ to comply with this specification.
  • the type field (object type) 904 is 6 bits. This field indicates the payload type, i.e., the mode. Payload type values are provided in Table 6 below. For the fragmentation and aggregation indication data unit of each payload type is provided in Table 6 below.
  • Payload definition Semantics of Value Type of payload data ‘object_identifier’ 0x00 MPU format-aware fragments MPU sequence of MPU number 0x01 Generic a generic object such as a TOI Object complete MPU or an object of another type 0x02 signaling a single complete message signaling message 0x03 repair a single complete repair symbol symbol 0x04 ⁇ 0x1F ISO reserved for future use 0x20 ⁇ 0x3F Reserved for private use
  • the FEC_type (FEC) field 906 is 2 bits long and indicates the type of FEC scheme used to protect MMT packets. An example of values and associated descriptions for this field is listed in Table 7 below.
  • the reserved (RES) field 908 is 3 bits long and is reserved for future use;
  • the packet_counter_flag (C) field 910 is 1 bit long and a ‘1’ indicates that the packet_counter field is present;
  • the RAP_flag (R) field 912 is 1 bit long and, when set to ‘1’, indicates that the payload contains a random access point to the data stream of that data type,
  • the extension_flag (X) field 914 is 1 bit long and a ‘1’ indicates that the header_extension field is present,
  • the last (L) field 916 is 1 bit long and a ‘1’ indicates that the last one of the packets with same value of the object_identifier field;
  • the packet_id field 918 is 16 bits long and includes an integer value assigned to each asset to distinguish packets of one asset from another.
  • the packet_id is unique throughout the lifetime of the delivery session and for all MMT flows delivered by the same MMT sending entity.
  • the mapping between the packet_id and the asset_id is signaled by the MMT Package Table as part of a signaling message.
  • the mapping between packet_id and the FEC repair flow is provided in the AL-FEC message.
  • the packet_id is unique for all MMT packet flows delivered by the same MMT sending entity.
  • the object_identifier field 920 is 32 bits long and includes an identifier of the application layer object from the current payload is extracted. The exact semantics and usage of this field 920 may depend on the type of the payload.
  • the packet_sequence_number field 922 is 32 bits long and includes an integer value that is scoped by the packet_id and starts from arbitrary value incremented by one for each MMT packet. This value wraps around to ‘0’ after its maximum value is reached.
  • the timestamp field 924 is 32 bits long and specifies the time instance of MMT packet delivery.
  • the NTP time is used in timestamp as specified as the “short-format” in clause 6 of IETF RFC5905, NTP version 4, which is incorporated by reference herein. This timestamp specifies the time at the first bit of MMT packet.
  • the packet_counter field 926 is 32 bits long and includes an integer value for counting the MMT packet. The value is incremented by the sending of an MMT packet and is different from the value packet_id. This field 926 starts from arbitrary value incremented by one for each MMT packet sent. The value of the field 926 wraps around to ‘0’ after its maximum value.
  • the extension_header field 928 is includes user-defined information.
  • the header extension mechanism is provided to allow for proprietary extensions to the payload format to enable applications and media types that require additional information to be carried in the payload format header.
  • the header extension mechanism is designed in such a way that it may be discarded without impacting the correct processing of the MMT payload.
  • the extension header in the field 928 may have the format as illustrated in FIG. 10 , which illustrates an exemplary structure for header extension 1000 in accordance with various embodiments of the present disclosure.
  • the payload data field 930 includes the payload data; and the source FEC payload ID field 932 is 2 bits long and may be used only when the value of FEC type is set to ‘1’.
  • the present disclosure provides a harmonized structure for MMTP with two layers enabling indication of specific parts of an MPU for fragmented delivery.
  • the payload type e.g., download mode, streaming mode, GPU mode, MPU mode, etc.
  • type or object type
  • the delivery data unit type is signaled by the DU_type field in the MPU mode payload header.
  • FIG. 11 illustrates an exemplary diagram 1100 of packetization of timed media data in accordance with various embodiments of the present disclosure.
  • the packetization of an MPU that contains timed media may be performed in an MPU format-aware and/or MPU format agnostic mode.
  • the MPU format agnostic mode the MPU is packetized into data units of equal size (except for the last data unit, of which the size may differ) or a predefined size according to the size of MTU of the underlying delivery network by using GFD.
  • the packetization of the MPU format agnostic mode may only consider the size of data to be carried in the packet.
  • the type field for the MMTP packet header is set to 0x00 to indicate that the packetization is format agnostic mode.
  • the packetization procedure takes into account the boundaries of different types of data in MPU to generate packets by using MPU mode.
  • the resulting packets carry delivery data units of either MPU metadata, movie fragment metadata, or MFU.
  • the resulting packets may not carry more than two different types of delivery data units.
  • the delivery data unit of MPU metadata is assigned the DU_type 0x01.
  • the MPU metadata includes the ‘ftyp’ box, the ‘mmpu’ box, the ‘moov’ box, and any other boxes that are applied to the whole MPU.
  • the delivery data unit of movie fragment metadata consists of the ‘moof’ box and the ‘mdat’ box header (excluding any media data) and is assigned the DU_type 0x02.
  • the media data, MFUs in mdat box of MPU, is then split into multiple delivery data units of MFU in a format aware way. This may, for example, be performed with the help of the MMT hint track.
  • the MFU may include 1) only media data, 2) media data with a sequence number, and 3) media data with some control information. Each MFU is prepended the MFU header, which has the syntax and semantics. The MFU header is followed by the media data of the MFU.
  • FIG. 12 illustrates an exemplary diagram 1200 of packetization of non-timed media data in accordance with various embodiments of the present disclosure.
  • the packetization of non-timed media data may also be performed in two different modes.
  • the MPU format agnostic mode the MPU is packetized into delivery data units of equal size (except for the last data unit, of which the size may differ) or a predefined size according to the size of MTU of the underlying delivery network by using GFD mode.
  • the type field of MMTP packet is set to 0x00 to indicate that the packetization is generic.
  • the MPU is packetized into the packet containing delivery data units of either MPU metadata or MFU by using MPU mode.
  • the MPU metadata contains the ‘ftyp’ box, the ‘moov’ box, the ‘meta’ box and any other boxes that are applied to whole MPU.
  • Each delivery data unit of MFU contains a single item of the non-timed media.
  • Each item of the non-timed data is then used to build an MFU.
  • the MFU consists of an MFU header and the non-timed MFU data.
  • the depacketization procedure is performed at the MMT receiver to obtain the transmitted MPU.
  • the depacketization procedure may operate in one of the following modes, depending on the application needs: an MPU mode, a fragment mode, and a media unit mode.
  • MPU mode the depayloadizer regenerates the full MPU before forwarding the MPU to the application. This mode is appropriate for non-time critical delivery, i.e. the MPU's presentation time as indicated by the CI is sufficiently behind the MPU's delivery time.
  • the depayloadizer regenerates a complete fragment including the fragment metadata and the ‘mdat’ box with media samples before forwarding it to the application. This mode does not apply to non-timed media.
  • This mode is suitable for delay-sensitive applications where the delivery time budget is limited but is large enough to recover a complete fragment.
  • the depayloadizer extracts and forwards media units as fast as possible to the application.
  • This mode is applicable for very low delay media applications. In this mode, the recovery of the MPU is not required.
  • the processing of the fragment media data is not required but may be performed to resynchronize.
  • This mode tolerates out of order delivery of the fragment metadata, which may be generated after the media units are generated. This mode applies to both timed and non-timed media.
  • receiver is able to detect missing packets and apply any error correction procedures such as FEC or ARQ to recover the missing packets.
  • the payload type may be used by the sender to determine the importance of the payload for the application and to apply appropriate error resilience measures.
  • Each GFD delivery session may have a GFDT that is local to the given session.
  • a file that is delivered within the GFD session, but not described in the GFDT is not considered a ‘file’ belonging to the GFD delivery session.
  • An object that is received with an un-mapped code point should be ignored by a GFD receiver.
  • the files in the GFD session may have to be provided to an application, for example in a composition information document or a media presentation description, as defined in ISO/IEC 23009-1, which is incorporated by reference herein, may refer to the files delivered using MMTP as GFD objects.
  • the file may be referenced through the URI provided or derived from content-location, either provided in-band or as part of the GFD session description.
  • the files have an availability start time in the application.
  • the GFD session may deliver the files such that the last packet of the object is delivered such that it is available latest at the receiver at the availability start time as announced in the application.
  • Applications delivered through the GFD mode may impose additional and stricter requirements on the sending of the files within a GFD session.
  • a sender (e.g., sending entity 101 ) transmits a sequence of packets within the session.
  • Several objects may be delivered within the same GFD session. If more than one object is to be delivered within a session, then the sender may use the TOI field. In this scenario, each object may be identified by a unique TOI within the session, and the sender may use corresponding TOI for all packets pertaining to the same object.
  • the mapping between TOIs and files carried in a session is described in the GFD session description as well as in the entity-header fields if entity mode delivery is applied.
  • the GFD header may be used.
  • the GFD packet header includes a code point field that may be used to communicate to a receiver the settings for information that is established for the session and may even vary during a session. The mapping between settings and code point values is communicated in the GFD session description.
  • T>0 be the transfer-length of any object in bytes
  • the data carried in the payload of a packet consists of a consecutive portion of the object. Then for any arbitrary X and any arbitrary Y>0 as long as X+Y is at most T a packet may be generated.
  • the data carried in the payload of a packet may consist of a consecutive portion of the object starting from the beginning of byte X through the beginning of byte X+Y;
  • the start_offset field in the GFD packet header may be set to X and the payload data may be added into the packet to send; and
  • the packet header flag B may be set to 1, else the packet header flag B may be set to 0.
  • the following exemplary procedure may be used by a sender to deliver an object to generate packets containing start_offset and corresponding payload data.
  • the sender sets the byte offset counter X to 0.
  • the sender sets the length in bytes of a payload to a fixed value Y, which is a) reasonable for a packet payload (e.g., ensure that the total packet size does not exceed the MTU), b) such that the sum of X and Y is at most T, and c) such that it is suitable for the payload data included in the packet.
  • the sender then generates a packet according to the rules a-c from above.
  • the order of packet delivery may be arbitrary, but the sender may perform delivery in the absence of other constraints delivery with increasing start_offset number.
  • the transfer length may be unknown prior to sending earlier pieces of the data. In this situation, T may be determined later. However, this does not affect the sending process above. Additional packets may be sent following the rules in (A)-(C) from above. In this situation, the B flag may only be set for the packet that contains the last portion of the object.
  • the GFD Session Description contains one or multiple code points identified by different code point values.
  • the receiver e.g., one or more of receiving entities 110 - 116 .
  • the receiver may proceed with the following steps. First, the receiver parses the packet header and verifies that it is a valid header. If it is not valid, then the packet may be discarded without further processing. Second, the receiver parses the code point value and verifies that the GFD session description contains a matching code point. If it is not valid, then the packet may be discarded without further processing.
  • the receiver processes the remainder of the packet, which includes interpreting the other header fields appropriately and using the source_offset and the payload data to reconstruct the corresponding object as follows: a) the receiver can determine from which object a received packet was generated by the session information, and if present, by the TOI carried in the payload header; b) upon receipt of the first packet for an object, the receiver uses the Maximum Transfer Length received as part of the Object Transmission Information to determine the maximum length T′ of the object; c) the receiver allocates space for the T′ bytes that the object may require; d) the receiver computes the length of the payload, Y, by subtracting the packet header length from the total length of the received packet; e) the receiver allocates a Boolean array RECEIVED[0 .
  • GFD CodePoint the information about the files delivered using the GFD mode is indicated in the MP Table if the asset_scheme_code is set to “GeneralFile”.
  • the generic objects that are delivered using the GFD mode may be grouped together as an MMTP flow identified by the packet_id. Packets that carry generic objects using the GFD mode may be marked with type 1 in the MMTP packet header type field.
  • the GFD table defines one or multiple code points. The code point table is provided in Table 8 below.
  • the various embodiments of the present are not limited to MMT communications.
  • the fixed delay and buffer size determinations may be applied to any suitable type of data or media content delivery and/or any suitable type of transmission system in accordance with the principals of the present disclosure.
  • the receiving entity identifies a delivery data unit type from a field indicating the delivery data unit type in a streaming mode payload header (step 1320 ). For example, in step 1320 , the receiving entity may identify the delivery data unit type of the DU data in the transport packet such as the type of data in MMT payload.
  • the receiving entity may parse the streaming mode payload header, such as illustrated in FIG. 4 , to identify the value in the DU_type field 404 to identify the delivery data unit type in accordance with Table 1.
  • the DU data may include one of: a complete MPU, MPU metadata, movie fragment metadata, a timed MFU, a non-timed MFU, a signaling message, or recovery symbols based on the value included in the DU type field.
  • the receiving entity identifies information about whether MFU(s) are present in the transport packet from a fragmentation indicator field in the streaming mode payload header (step 1325 ).
  • the transport packet includes one or more fragments of an MPU arranged as MFUs.
  • the transport packet may include a plurality of delivery data units, each delivery data unit including a DU header and DU data.
  • the receiving entity may determine whether the DU data includes: one or more delivery data unit headers and complete delivery data units, a delivery data unit header and a first fragment of a delivery data unit, a fragment of the delivery data unit that is neither the first nor the last part, or a last fragment of the delivery data unit based on the value in the fragmentation indicator field in accordance with Table 2.
  • FIG. 14 illustrates a process for generating a transport packet at a sending entity in accordance with an illustrative embodiment of the present disclosure.
  • the process depicted in FIG. 14 may be performed by the sending entity 101 in FIG. 1 .
  • the process may also be implemented by the electronic device 1500 in FIG. 15 .
  • the sending entity then includes an identifier of a payload type in a field indicating the payload type in a packet header for the transport packet (step 1410 ).
  • the sending entity may include a value corresponding to object type, such as in Table 6, in a type field of the packet header, such as in field 904 in FIG. 9 .
  • the sending entity includes an identifier of a delivery data unit type in a field indicating the delivery data unit type in a streaming mode payload header (step 1420 ).
  • the sending entity may include a value of corresponding to the delivery data unit type for the packet in a field in the streaming mode payload header, such as illustrated by the DU_type field 404 of the streaming mode payload header in FIG. 4 accordance with the delivery data unit types Table 1.
  • the sending entity then sends the generated transport packet (step 1430 ).
  • the sending entity may send the transport packet to a receiving entity to receive and process the transport packet, for example, according to the process illustrated in FIG. 13 .
  • FIGS. 13 and 14 illustrate examples of processes for processing and generating transport packets by receiving and sending entities, respectively, various changes could be made to FIGS. 13 and 14 .
  • steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times.
  • FIG. 15 illustrates an example electronic device 1500 in which various embodiments of the present disclosure may be implemented.
  • the electronic device 1500 includes a controller 1504 , a memory 1506 , a persistent storage 1508 , a communications unit 1510 , an input/output (I/O) unit 1512 , and a display 1514 .
  • electronic device 1500 is also one example of the sending entity 101 and/or the receiving entity 110 in FIG. 1 .
  • Controller 1504 is any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same.
  • the controller 1504 may include a hardware processing unit, processing circuitry, media coding and/or decoding hardware and/or software, and/or software program configured to control operations of the electronic device 1500 .
  • controller 1504 process instructions for software that may be loaded into memory 1506 .
  • Controller 1504 may include a number of processors, a multi-processor core, or some other type of processor, depending on the particular implementation. Further, controller 1504 may be implemented using a number of heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, controller 1504 may include a symmetric multi-processor system containing multiple processors of the same type.
  • Input/output unit 1512 allows for input and output of data with other devices that may be connected to or a part of the electronic device 1500 .
  • input/output unit 1512 may include a touch panel to receive touch user inputs, a microphone to receive audio inputs, a speaker to provide audio outputs, and/or a motor to provide haptic outputs.
  • Input/output unit 1512 is one example of a user interface for providing and delivering media data (e.g., audio data) to a user of the electronic device 1500 .
  • input/output unit 1512 may provide a connection for user input through a keyboard, a mouse, external speaker, external microphone, and/or some other suitable input/output device.
  • input/output unit 1512 may send output to a printer.
  • Display 1514 provides a mechanism to display information to a user and is one example of a user interface for providing and delivering media data (e.g., image and/or video data) to a user of the electronic device 1500 .
  • media data e.g., image and/or video data
  • various functions described above are implemented or supported by a computer program product that is formed from computer-readable program code and that is embodied in a computer-readable medium.
  • Program code for the computer program product may be located in a functional form on a computer-readable storage device that is selectively removable and may be loaded onto or transferred to electronic device 1500 for processing by controller 1504 .
  • the program code may be downloaded over a network to persistent storage 1508 from another device or data processing system for use within electronic device 1500 .
  • program code stored in a computer-readable storage medium in a server data processing system may be downloaded over a network from the server to electronic device 1500 .
  • the data processing system providing program code may be a server computer, a client computer, or some other device capable of storing and transmitting program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Information Transfer Between Computers (AREA)
US14/178,212 2013-07-26 2014-02-11 Packet transmission protocol supporting downloading and streaming Abandoned US20150032845A1 (en)

Priority Applications (21)

Application Number Priority Date Filing Date Title
US14/178,212 US20150032845A1 (en) 2013-07-26 2014-02-11 Packet transmission protocol supporting downloading and streaming
MYPI2016700246A MY174260A (en) 2013-07-26 2014-07-25 Method and apparatus for packet transmission supporting downloading and streaming
PCT/KR2014/006829 WO2015012645A1 (en) 2013-07-26 2014-07-25 Method and apparatus for packet transmission supporting downloading and streaming
JP2015535594A JP5883199B2 (ja) 2013-07-26 2014-07-25 ダウンローディング及びストリーミングをサポートするパケットの送信方法及び装置
AU2014293819A AU2014293819B2 (en) 2013-07-26 2014-07-25 Method and apparatus for packet transmission supporting downloading and streaming
CN201480042072.0A CN105409174B (zh) 2013-07-26 2014-07-25 用于支持下载和流传送的分组传输的方法和设备
CN201911248313.8A CN110830511B (zh) 2013-07-26 2014-07-25 用于支持下载和流传送的分组传输的方法和设备
BR112016001661-0A BR112016001661B1 (pt) 2013-07-26 2014-07-25 Métodos e aparelhos de transmitir e receber conteúdos de mídia
KR1020140094980A KR101530825B1 (ko) 2013-07-26 2014-07-25 멀티미디어 시스템에서 미디어 컨텐츠 전송 방법
EP21156204.6A EP3840313A1 (en) 2013-07-26 2014-07-25 Method and apparatus for packet transmission supporting downloading and streaming
ES14828733T ES2878022T3 (es) 2013-07-26 2014-07-25 Procedimiento y aparato para transmisión de paquetes que soporta descarga y streaming
CN201911248319.5A CN111049820B (zh) 2013-07-26 2014-07-25 用于支持下载和流传送的分组传输的方法和设备
EP14828733.7A EP3025464B1 (en) 2013-07-26 2014-07-25 Method and apparatus for packet transmission supporting downloading and streaming
MX2016001137A MX356847B (es) 2013-07-26 2014-07-25 Método y aparato para la transmisión de paquete que soporta la descarga y transmisión.
KR1020150000130A KR102015963B1 (ko) 2013-07-26 2015-01-02 멀티미디어 시스템에서 미디어 컨텐츠 수신 방법
MX2018007146A MX2018007146A (es) 2013-07-26 2016-01-26 Metodo y aparato para la transmision de paquete que soporta la descarga y transmision.
JP2016020212A JP6106775B2 (ja) 2013-07-26 2016-02-04 ダウンローディング及びストリーミングをサポートするパケット受信方法
JP2017042254A JP6346329B2 (ja) 2013-07-26 2017-03-06 ダウンローディング及びストリーミングをサポートするパケットの伝送装置及び受信装置
JP2018099982A JP6526289B2 (ja) 2013-07-26 2018-05-24 ダウンローディング及びストリーミングをサポートするパケットの送信装置
KR1020190103570A KR102127733B1 (ko) 2013-07-26 2019-08-23 멀티미디어 시스템에서 미디어 컨텐츠 전송 방법 및 장치
US16/805,608 US11637887B2 (en) 2013-07-26 2020-02-28 Packet transmission protocol supporting downloading and streaming

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201361859015P 2013-07-26 2013-07-26
US201361896570P 2013-10-28 2013-10-28
US14/178,212 US20150032845A1 (en) 2013-07-26 2014-02-11 Packet transmission protocol supporting downloading and streaming

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/805,608 Continuation US11637887B2 (en) 2013-07-26 2020-02-28 Packet transmission protocol supporting downloading and streaming

Publications (1)

Publication Number Publication Date
US20150032845A1 true US20150032845A1 (en) 2015-01-29

Family

ID=52391425

Family Applications (2)

Application Number Title Priority Date Filing Date
US14/178,212 Abandoned US20150032845A1 (en) 2013-07-26 2014-02-11 Packet transmission protocol supporting downloading and streaming
US16/805,608 Active US11637887B2 (en) 2013-07-26 2020-02-28 Packet transmission protocol supporting downloading and streaming

Family Applications After (1)

Application Number Title Priority Date Filing Date
US16/805,608 Active US11637887B2 (en) 2013-07-26 2020-02-28 Packet transmission protocol supporting downloading and streaming

Country Status (11)

Country Link
US (2) US20150032845A1 (zh)
EP (2) EP3840313A1 (zh)
JP (4) JP5883199B2 (zh)
KR (3) KR101530825B1 (zh)
CN (3) CN110830511B (zh)
AU (1) AU2014293819B2 (zh)
BR (1) BR112016001661B1 (zh)
ES (1) ES2878022T3 (zh)
MX (2) MX356847B (zh)
MY (1) MY174260A (zh)
WO (1) WO2015012645A1 (zh)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150100996A1 (en) * 2013-10-07 2015-04-09 Samsung Electronics Co., Ltd. Practical delivery of high quality video using dynamic adaptive hypertext transport protocol (http) streaming (dash) without using http in a broadcast network
US20150117243A1 (en) * 2013-10-28 2015-04-30 Electronics And Telecommunications Research Institute Apparatus and method for transmitting/receiving moving picture experts group (mpeg) media transport (mmt) signaling message for measurement configuration (mc) processing
JP2016208461A (ja) * 2015-04-28 2016-12-08 日本放送協会 処理装置、プログラムおよびデータ構造
US20170055025A1 (en) * 2014-04-30 2017-02-23 Lg Electronics Inc. Broadcast transmission apparatus, broadcast reception apparatus, operation method of the broadcast transmission apparatus and operation method of the broadcast reception apparatus
US20170055046A1 (en) * 2014-05-21 2017-02-23 Lg Electronics Inc. Broadcast signal transmitting/receiving method and device
US20170280177A1 (en) * 2015-02-13 2017-09-28 Sk Telecom Co., Ltd. Computer-readable recording medium having program recorded therein for providing network-adaptive content and apparatus for providing network-adaptive content
WO2017200319A1 (ko) * 2016-05-18 2017-11-23 에스케이텔레콤 주식회사 적응형 스트리밍 서비스 제공 방법 및 이를 위한 장치
KR20170130273A (ko) * 2016-05-18 2017-11-28 에스케이텔레콤 주식회사 적응형 스트리밍 서비스 제공 방법 및 이를 위한 장치
US20170373918A1 (en) * 2015-03-08 2017-12-28 Lg Electronics Inc. Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal
US20180279013A1 (en) * 2017-03-24 2018-09-27 Mediatek Inc. Methods and apparatus for media content asset changes
US10116576B2 (en) 2015-10-19 2018-10-30 Samsung Electronics Co., Ltd. Methods and apparatus for random access of HEVC bitstream for MMT
US10148797B2 (en) * 2014-07-04 2018-12-04 Samsung Electronics Co., Ltd. Method and device for receiving media packets in multimedia system
US20190297357A1 (en) * 2016-05-26 2019-09-26 Samsung Electronics Co., Ltd. Method and device for transmitting and receiving mmtp packet
US20200059688A1 (en) * 2015-03-02 2020-02-20 Nec Corporation Decoding device, reception device, transmission device, transmission/reception system, decoding method, and storage medium having decoding program stored therein
US20200204609A1 (en) * 2013-07-26 2020-06-25 Samsung Electronics Co., Ltd. Packet transmission protocol supporting downloading and streaming
US11082340B2 (en) * 2014-06-10 2021-08-03 Sony Corporation Transmitting apparatus, transmitting method, and receiving apparatus

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6268066B2 (ja) * 2013-09-20 2018-01-24 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカＰａｎａｓｏｎｉｃ Ｉｎｔｅｌｌｅｃｔｕａｌ Ｐｒｏｐｅｒｔｙ Ｃｏｒｐｏｒａｔｉｏｎ ｏｆ Ａｍｅｒｉｃａ 送信方法、受信方法、送信装置及び受信装置
KR102209785B1 (ko) * 2015-06-09 2021-01-28 에스케이텔레콤 주식회사 Mmt 패킷 캐싱 처리 방법 및 이를 위한 장치, 캐싱 처리를 위한 mmt 패킷 생성 방법 및 이를 위한 장치
KR102209784B1 (ko) * 2015-06-09 2021-01-28 에스케이텔레콤 주식회사 Mmt 패킷 캐싱 처리 방법 및 이를 위한 장치, 캐싱 처리를 위한 mmt 패킷 생성 방법 및 이를 위한 장치
US10750215B2 (en) 2015-07-27 2020-08-18 Lg Electronics Inc. Method and device for transmitting metadata in WFD
US20230283651A1 (en) * 2016-02-02 2023-09-07 Shanghai Jiao Tong University Multimedia system information interaction mechanism and network transmission method
FR3052944B1 (fr) * 2016-06-15 2019-07-19 Hl2 Procede de segmentation de donnees a haut rendement
FR3052943B1 (fr) * 2016-06-15 2018-12-14 Hl2 Procede de reconstruction de donnees dans une transmission a bas debit
CN106411872B (zh) * 2016-09-21 2019-09-17 杭州迪普科技股份有限公司 一种基于数据报文分类的报文压缩的方法和装置
KR101915469B1 (ko) * 2016-11-29 2018-11-06 에스케이텔레콤 주식회사 스트리밍 서비스 제공 방법 및 이를 위한 장치
US10594618B1 (en) * 2017-06-06 2020-03-17 Juniper Networks, Inc Apparatus, system, and method for fragmenting packets into segments that comply with the maximum transmission unit of egress interfaces
KR20210021861A (ko) 2019-08-19 2021-03-02 (주)제노팜 사람 표피성장인자수용체 2 양성 암을 치료하기 위한 인터페론-베타 변이체 면역사이토카인의 용도 및 환자 선별 방법

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050190756A1 (en) * 2004-02-26 2005-09-01 Mundra Satish Kumar M. RTP payload for voice band data transmission
US20080240123A1 (en) * 2007-03-27 2008-10-02 Cisco Technology, Inc. Method and system for communicating h.263 macroblock boundaries using h.221 bas for rfc2190-compliant fragmentation
US20090052537A1 (en) * 2004-11-04 2009-02-26 Koninklijke Philips Electronics, N.V. Method and device for processing coded video data
US20130094563A1 (en) * 2011-10-13 2013-04-18 Electronics And Telecommunications Research Institute Method of configuring and transmitting an mmt transport packet
US20140133489A1 (en) * 2011-06-13 2014-05-15 Electronic and Techcommunications Research Institute Method for transmitting packet-based media data having header in which overhead is minimized
US20140369222A1 (en) * 2012-01-26 2014-12-18 Electronics And Telecommunications Research Institute Method for estimating network jitter in apparatus for transmitting coded media data
US20150113577A1 (en) * 2012-05-10 2015-04-23 Humax Holdings Co., Ltd. Hybrid transmission method through mmt packet format extension
US20150181003A1 (en) * 2012-07-10 2015-06-25 Electronics And Telecommunications Research Institute Method and apparatus for transmitting and receiving packets in hybrid transmission service of mmt
US20150201207A1 (en) * 2012-03-23 2015-07-16 Humax Co., Ltd. Hybrid delivery method and reception method for mmt packaged svc video contents
US20150373380A1 (en) * 2013-03-14 2015-12-24 Sony Corporation Transmission apparatus, transmission method, reception apparatus, and reception method
US20160073137A1 (en) * 2013-06-07 2016-03-10 Sony Corporation Transmission apparatus, transmission method, reception apparatus, and reception method
US20160073119A1 (en) * 2013-06-18 2016-03-10 Panasonic Intellectual Property Corporation Of America Transmitting method and receiving method
US20160080714A1 (en) * 2013-04-30 2016-03-17 Sony Corporation Transmitting device, transmitting method, receiving device, and receiving method
US20160112731A1 (en) * 2013-06-07 2016-04-21 Sony Corporation Transmission device, transmission method of transmission stream, and processing device

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6460086B1 (en) * 1998-12-01 2002-10-01 Sun Microsystems, Inc. Method and apparatus for delivery of a bytecode embedded within a transport stream
US6633903B1 (en) * 2000-03-23 2003-10-14 Monkeymedia, Inc. Method and article of manufacture for seamless integrated searching
US7743397B2 (en) 2001-01-17 2010-06-22 Lg Electronics Inc. Digital television signal, digital television receiver, and method of processing digital television signal
JP4399998B2 (ja) * 2001-03-22 2010-01-20 株式会社日立製作所 デジタル放送用ストリームの蓄積方法
US20030018793A1 (en) * 2001-07-19 2003-01-23 Oscar Mora Reliable transport layer protocol in low performance 8-bit microcontrollers
US7808561B2 (en) 2003-12-26 2010-10-05 Electronics And Telecommunications Research Institute Apparatus and method for transforming a digital TV broadcasting signal to a digital radio broadcasting signal
KR100565900B1 (ko) * 2003-12-26 2006-03-31 한국전자통신연구원 디지털 텔레비젼 방송신호를 디지털 라디오 방송신호로변환하는 방송신호 변환 장치 및 그 방법
KR20110022016A (ko) * 2005-08-02 2011-03-04 엘지전자 주식회사 디지털 방송 송수신기
US20070153830A1 (en) * 2006-01-05 2007-07-05 Xhafa Ariton E Methods and apparatus to provide fairness for wireless local area networks that use extended physical layer protection mechanisms
KR20080006441A (ko) * 2006-07-12 2008-01-16 삼성전자주식회사 미디어 데이터 전송 장치 및 방법 및 미디어 데이터 수신장치 및 방법
US20080040498A1 (en) * 2006-08-10 2008-02-14 Nokia Corporation System and method of XML based content fragmentation for rich media streaming
US20080115063A1 (en) * 2006-11-13 2008-05-15 Flagpath Venture Vii, Llc Media assembly
US20080134266A1 (en) * 2006-11-24 2008-06-05 Young-Seok Kang Digital broadcasting system and error correction method thereof
WO2008157770A2 (en) * 2007-06-21 2008-12-24 Interdigital Technology Corporation Signaling in a wireless communication system
US8180029B2 (en) 2007-06-28 2012-05-15 Voxer Ip Llc Telecommunication and multimedia management method and apparatus
US9852219B2 (en) * 2007-08-20 2017-12-26 Nokia Technologies Oy Segmented metadata and indexes for streamed multimedia data
KR101034758B1 (ko) * 2007-10-04 2011-05-17 에스케이 텔레콤주식회사 통합 멀티미디어 파일의 초기 실행 방법과 이를 위한시스템
KR101653310B1 (ko) * 2009-09-02 2016-09-01 엘지전자 주식회사 Ｍａｃ 헤더 타입 정보를 이용한 ｍａｃ ｐｄｕ 송수신 방법 및 장치
KR101216100B1 (ko) 2009-11-18 2012-12-26 엘지전자 주식회사 단편화 패킹 확장헤더를 수반하는 ｍａｃ ｐｄｕ를 전송하는 방법 및 장치
EP2362654A1 (en) * 2010-02-26 2011-08-31 Panasonic Corporation Short baseband frame headers
EP2418792A1 (de) * 2010-05-19 2012-02-15 Fraunhofer-Gesellschaft zur Förderung der Angewandten Forschung e.V. Digital Multimedia Broadcast (DMB) mit effizienter Übertragung der Daten zur Zugangsbeschränkung im Transportstrom-Packet mit der Programmzuordnungstabelle (Program Association Table = PAT)
EP2730052A4 (en) * 2011-07-08 2015-02-25 Samsung Electronics Co Ltd METHOD FOR GENERATING A FORWARD ERROR CORRECTION PACKAGE IN A MULTIMEDIA SYSTEM AND METHOD AND DEVICE FOR SENDING AND RECEIVING FORWARD ERROR CORRECTION PACKAGES
KR20130040090A (ko) * 2011-10-13 2013-04-23 삼성전자주식회사 복합 네트워크에서 멀티미디어 데이터를 전송하기 위한 장치 및 그 방법
KR20130040132A (ko) * 2011-10-13 2013-04-23 한국전자통신연구원 이종 ip 네트워크를 통한 미디어 코덱에 독립적인 미디어 데이터 전송 방법
KR101933465B1 (ko) * 2011-10-13 2019-01-11 삼성전자주식회사 이동 통신 시스템에서 패킷 송수신 장치 및 방법
US8930064B2 (en) * 2011-10-27 2015-01-06 Snap-On Incorporated Method and system for automated and manual data capture configuration
KR101995221B1 (ko) * 2011-11-24 2019-07-16 삼성전자주식회사 통신 시스템에서 패킷 송수신 장치 및 방법
KR102048730B1 (ko) * 2011-11-30 2020-01-08 삼성전자주식회사 방송 데이터 송/수신장치 및 방법
US9274937B2 (en) * 2011-12-22 2016-03-01 Longitude Enterprise Flash S.A.R.L. Systems, methods, and interfaces for vector input/output operations
US20140344875A1 (en) * 2012-01-20 2014-11-20 Electronics And Telecommunications Research Institute Method for transmitting media data having access unit divided into media fragment units in heterogeneous network
HUE063722T2 (hu) * 2012-04-25 2024-01-28 Samsung Electronics Co Ltd Eljárás adatok átvitelére multimédia átviteli rendszerben
KR20140002447A (ko) * 2012-06-29 2014-01-08 삼성전자주식회사 멀티미디어 시스템에서 적응적 미디어 구조 송수신 방법 및 장치
KR102185384B1 (ko) * 2012-07-11 2020-12-02 한국전자통신연구원 Mpeg 데이터의 랜덤 억세스를 지원하는 방법 및 시스템
US9462043B2 (en) * 2013-03-13 2016-10-04 Cisco Technology, Inc. Framework for dynamically programmed network packet processing
KR102117445B1 (ko) * 2013-04-17 2020-06-01 톰슨 라이센싱 패킷 헤더 압축을 위한 방법 및 장치
US9872227B2 (en) * 2013-04-23 2018-01-16 Qualcomm Incorporated Systems and methods for identification in a neighborhood aware network
US20150032845A1 (en) * 2013-07-26 2015-01-29 Samsung Electronics Co., Ltd. Packet transmission protocol supporting downloading and streaming

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050190756A1 (en) * 2004-02-26 2005-09-01 Mundra Satish Kumar M. RTP payload for voice band data transmission
US20090052537A1 (en) * 2004-11-04 2009-02-26 Koninklijke Philips Electronics, N.V. Method and device for processing coded video data
US20080240123A1 (en) * 2007-03-27 2008-10-02 Cisco Technology, Inc. Method and system for communicating h.263 macroblock boundaries using h.221 bas for rfc2190-compliant fragmentation
US20140133489A1 (en) * 2011-06-13 2014-05-15 Electronic and Techcommunications Research Institute Method for transmitting packet-based media data having header in which overhead is minimized
US20130094563A1 (en) * 2011-10-13 2013-04-18 Electronics And Telecommunications Research Institute Method of configuring and transmitting an mmt transport packet
US20140369222A1 (en) * 2012-01-26 2014-12-18 Electronics And Telecommunications Research Institute Method for estimating network jitter in apparatus for transmitting coded media data
US20150201207A1 (en) * 2012-03-23 2015-07-16 Humax Co., Ltd. Hybrid delivery method and reception method for mmt packaged svc video contents
US20150113577A1 (en) * 2012-05-10 2015-04-23 Humax Holdings Co., Ltd. Hybrid transmission method through mmt packet format extension
US20150181003A1 (en) * 2012-07-10 2015-06-25 Electronics And Telecommunications Research Institute Method and apparatus for transmitting and receiving packets in hybrid transmission service of mmt
US20150373380A1 (en) * 2013-03-14 2015-12-24 Sony Corporation Transmission apparatus, transmission method, reception apparatus, and reception method
US20160080714A1 (en) * 2013-04-30 2016-03-17 Sony Corporation Transmitting device, transmitting method, receiving device, and receiving method
US20160073137A1 (en) * 2013-06-07 2016-03-10 Sony Corporation Transmission apparatus, transmission method, reception apparatus, and reception method
US20160112731A1 (en) * 2013-06-07 2016-04-21 Sony Corporation Transmission device, transmission method of transmission stream, and processing device
US20160073119A1 (en) * 2013-06-18 2016-03-10 Panasonic Intellectual Property Corporation Of America Transmitting method and receiving method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 1: MPEG media transport (MMT)," 2012, ISO. *
Zhu, C. "RTP payload format for H. 263 video streams." (1997). *

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11637887B2 (en) * 2013-07-26 2023-04-25 Samsung Electronics Co., Ltd. Packet transmission protocol supporting downloading and streaming
US20200204609A1 (en) * 2013-07-26 2020-06-25 Samsung Electronics Co., Ltd. Packet transmission protocol supporting downloading and streaming
US9807452B2 (en) * 2013-10-07 2017-10-31 Samsung Electronics Co., Ltd. Practical delivery of high quality video using dynamic adaptive hypertext transport protocol (HTTP) streaming (DASH) without using HTTP in a broadcast network
US20150100996A1 (en) * 2013-10-07 2015-04-09 Samsung Electronics Co., Ltd. Practical delivery of high quality video using dynamic adaptive hypertext transport protocol (http) streaming (dash) without using http in a broadcast network
US20150117243A1 (en) * 2013-10-28 2015-04-30 Electronics And Telecommunications Research Institute Apparatus and method for transmitting/receiving moving picture experts group (mpeg) media transport (mmt) signaling message for measurement configuration (mc) processing
US9641831B2 (en) * 2013-10-28 2017-05-02 Electronics And Telecommunications Research Institute Apparatus and method for transmitting/receiving moving picture experts group (MPEG) media transport (MMT) signaling message for measurement configuration (MC) processing
US20170055025A1 (en) * 2014-04-30 2017-02-23 Lg Electronics Inc. Broadcast transmission apparatus, broadcast reception apparatus, operation method of the broadcast transmission apparatus and operation method of the broadcast reception apparatus
US20170055046A1 (en) * 2014-05-21 2017-02-23 Lg Electronics Inc. Broadcast signal transmitting/receiving method and device
US11082340B2 (en) * 2014-06-10 2021-08-03 Sony Corporation Transmitting apparatus, transmitting method, and receiving apparatus
US10148797B2 (en) * 2014-07-04 2018-12-04 Samsung Electronics Co., Ltd. Method and device for receiving media packets in multimedia system
US10165311B2 (en) * 2015-02-13 2018-12-25 Sk Telecom Co., Ltd. Non-transitory computer-readable recording medium having program recorded therein for providing network-adaptive content and apparatus for providing network-adaptive content
US20170280177A1 (en) * 2015-02-13 2017-09-28 Sk Telecom Co., Ltd. Computer-readable recording medium having program recorded therein for providing network-adaptive content and apparatus for providing network-adaptive content
US20200059688A1 (en) * 2015-03-02 2020-02-20 Nec Corporation Decoding device, reception device, transmission device, transmission/reception system, decoding method, and storage medium having decoding program stored therein
US20170373918A1 (en) * 2015-03-08 2017-12-28 Lg Electronics Inc. Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal
US10721538B2 (en) 2015-03-08 2020-07-21 Lg Electronics Inc. Apparatus and method for transmitting and receiving broadcast signal
US10582274B2 (en) * 2015-03-08 2020-03-03 Lg Electronics Inc. Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal
JP2016208461A (ja) * 2015-04-28 2016-12-08 日本放送協会 処理装置、プログラムおよびデータ構造
US10116576B2 (en) 2015-10-19 2018-10-30 Samsung Electronics Co., Ltd. Methods and apparatus for random access of HEVC bitstream for MMT
WO2017200319A1 (ko) * 2016-05-18 2017-11-23 에스케이텔레콤 주식회사 적응형 스트리밍 서비스 제공 방법 및 이를 위한 장치
KR102072344B1 (ko) 2016-05-18 2020-01-31 에스케이텔레콤 주식회사 적응형 스트리밍 서비스 제공 방법 및 이를 위한 장치
KR102000084B1 (ko) * 2016-05-18 2019-07-15 에스케이텔레콤 주식회사 적응형 스트리밍 서비스 제공 방법 및 이를 위한 장치
KR20190084024A (ko) * 2016-05-18 2019-07-15 에스케이텔레콤 주식회사 적응형 스트리밍 서비스 제공 방법 및 이를 위한 장치
CN109314793A (zh) * 2016-05-18 2019-02-05 Sk电信有限公司 提供自适应流服务的方法及其设备
US11095701B2 (en) 2016-05-18 2021-08-17 Sk Telecom Co., Ltd. Method and apparatus for providing adaptive streaming service
KR20170130273A (ko) * 2016-05-18 2017-11-28 에스케이텔레콤 주식회사 적응형 스트리밍 서비스 제공 방법 및 이를 위한 장치
US20190297357A1 (en) * 2016-05-26 2019-09-26 Samsung Electronics Co., Ltd. Method and device for transmitting and receiving mmtp packet
US10880586B2 (en) 2016-05-26 2020-12-29 Samsung Electronics Co., Ltd. Method and device for transmitting and receiving MMTP packet
CN110574378A (zh) * 2017-03-24 2019-12-13 联发科技股份有限公司 用于媒体内容资产改变的方法及装置
US20180279013A1 (en) * 2017-03-24 2018-09-27 Mediatek Inc. Methods and apparatus for media content asset changes
US10958988B2 (en) * 2017-03-24 2021-03-23 Mediatek Inc. Methods and apparatus for media content asset changes

Also Published As

Publication number Publication date
BR112016001661A2 (pt) 2020-08-25
JP2015530854A (ja) 2015-10-15
MX356847B (es) 2018-06-18
JP2016129358A (ja) 2016-07-14
JP2017108458A (ja) 2017-06-15
JP6106775B2 (ja) 2017-04-05
WO2015012645A1 (en) 2015-01-29
MX2016001137A (es) 2016-04-29
EP3025464B1 (en) 2021-04-21
JP6526289B2 (ja) 2019-06-05
JP2018148577A (ja) 2018-09-20
CN110830511B (zh) 2021-10-26
KR101530825B1 (ko) 2015-06-29
EP3025464A1 (en) 2016-06-01
MY174260A (en) 2020-04-01
CN105409174B (zh) 2020-01-03
CN111049820A (zh) 2020-04-21
KR20150015542A (ko) 2015-02-10
KR20150013081A (ko) 2015-02-04
KR102127733B1 (ko) 2020-06-30
CN105409174A (zh) 2016-03-16
MX2018007146A (es) 2020-11-06
KR20190101351A (ko) 2019-08-30
EP3840313A1 (en) 2021-06-23
JP6346329B2 (ja) 2018-06-20
AU2014293819B2 (en) 2018-05-17
AU2014293819A1 (en) 2016-02-04
CN110830511A (zh) 2020-02-21
US20200204609A1 (en) 2020-06-25
JP5883199B2 (ja) 2016-03-09
BR112016001661B1 (pt) 2023-04-18
KR102015963B1 (ko) 2019-08-30
CN111049820B (zh) 2022-06-03
ES2878022T3 (es) 2021-11-18
US11637887B2 (en) 2023-04-25
EP3025464A4 (en) 2017-01-11

Similar Documents

Publication Publication Date Title
US11637887B2 (en) Packet transmission protocol supporting downloading and streaming
US11805286B2 (en) Apparatus and method for transmitting/receiving processes of a broadcast signal
US20180123810A1 (en) Methods for delivery of flows of objects over broadcast/multicast enabled networks
KR20130140117A (ko) 방송 시스템에서 멀티미디어 데이터의 전송 장치 및 방법
JP2017528025A (ja) マルチメディア通信システムにおけるパケット送受信装置及び方法
KR20160000722A (ko) 통신 시스템에서 이종 네트워크를 통하여 멀티미디어 콘텐츠를 송수신하는 방법 및 장치

Legal Events

Date Code Title Description
AS Assignment

Owner name: SAMSUNG ELECTRONICS CO., LTD, KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BOUAZIZI, IMED;LIM, YOUNGKWON;REEL/FRAME:032198/0640

Effective date: 20140210

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION