CN103443741A - Method and apparatus for receiving presentation metadata - Google Patents

Method and apparatus for receiving presentation metadata Download PDF

Info

Publication number
CN103443741A
CN103443741A CN2012800080255A CN201280008025A CN103443741A CN 103443741 A CN103443741 A CN 103443741A CN 2012800080255 A CN2012800080255 A CN 2012800080255A CN 201280008025 A CN201280008025 A CN 201280008025A CN 103443741 A CN103443741 A CN 103443741A
Authority
CN
China
Prior art keywords
value
attribute
presents
indication
description
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.)
Granted
Application number
CN2012800080255A
Other languages
Chinese (zh)
Other versions
CN103443741B (en
Inventor
戴维·斯图尔特·弗贝克
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.)
Maliki Innovation Co ltd
Original Assignee
BlackBerry 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 BlackBerry Ltd filed Critical BlackBerry Ltd
Publication of CN103443741A publication Critical patent/CN103443741A/en
Application granted granted Critical
Publication of CN103443741B publication Critical patent/CN103443741B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
    • 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/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • 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/75—Media network packet handling
    • H04L65/752—Media network packet handling adapting media to network capabilities
    • 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/75—Media network packet handling
    • H04L65/756—Media network packet handling adapting media to device capabilities
    • 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/80—Responding to QoS
    • 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/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • 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/2343—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
    • H04N21/23439—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements for generating different versions
    • 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/643—Communication protocols
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/854—Content authoring
    • H04N21/8543—Content authoring using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/43—Querying
    • G06F16/438—Presentation of query results
    • G06F16/4387—Presentation of query results by the use of playlists
    • G06F16/4393—Multimedia presentations, e.g. slide shows, multimedia albums
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/103—Formatting, i.e. changing of presentation of documents
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Method and devices for a client device to receive a presentation streamed via HTTP. The client device receives a first segment of the presentation, the first segment including presentation metadata related to a first presentation description of the presentation. The client device sends a request based at least in part on a portion of the presentation metadata related to the first presentation description.

Description

For receiving the method and apparatus that presents metadata
Technical field
Present invention relates in general to HTML (Hypertext Markup Language) (HTTP) flow transmission, and relate more specifically to be used to indicate the method and apparatus for the change that presents description.
Background technology
HTTP flow transmission client asks receiving media to present with HTTP GET.Described and presented in presenting description, for example, in being called as media and presenting the XML document of description (MPD), described and presented, in 3GPP TS26.247, described MPD.According to MPD, which form is client for example can know with, to media content encoded (, bit rate, encoding and decoding, resolution, language etc.).Then client is selected form, one or more in the language preference that this form can be based on screen resolution, channel width, channel condition of acceptance, user etc.
In the situation that use the HTTP flow transmission, once receive a part of media.This is necessary for live content, makes the media of content broadcast to keep abreast with live coding too far away.It also makes client to be switched to adaptively different codings according to channel condition etc.Section in 3GPP HTTP self-adaptation flow transmission is Downloadable part in media, and its position (URL and possible bytes range) is described in MPD.In other words, how to access each section via MPD to the client notice.
In 3GPP, 3GPP file layout and vidclip are used in the supposition of HTTP flow transmission client.The 3GPP file layout is based on ISO/IEC14496-12ISO base medium file layout.Comprise a series of objects that are called as box (box) according to the media file of 3GPP file layout.Box can comprise media data or metadata.Each box has the box type (boxtype) (normally 4 character titles, 32 bits altogether) be associated and the size (normally 32 bit unsigned integer) be associated.In segmental file not, moov metadata box comprises for playing media data required all coding/decoding informations, timing information and positional information.For the media file of the segmentation of HTTP flow transmission, the moov box only comprises coding/decoding information, and all timing informations and positional information are included in vidclip itself.Vidclip generally includes one or more pairs of moof boxes and mdat box.The media data that the metadata that the moof box comprises vidclip and mdat box comprise vidclip.To the use of segmental file make scrambler can once write partially and make client can be once receiving media partially.With comprise metadata relatively at the moov box in advance, this comprises metadata by the moof box at media fragment, has minimized start delay.The moov box still comprises the description to the encoding and decoding for coding, but does not comprise any specifying information about media sample, such as timing, skew etc.The moof box only is allowed to comprise quoting for the encoding and decoding of listing in the moov box.If need to use the new encoding and decoding that do not define in the moov box, need in new file, create new moov box, because occur that in the media file format based on ISO two moov boxes are invalid.
Present description (for example MPD) and comprise at least one period, the period comprises at least one expression, and means to comprise at least one section.Section comprises one or more vidclips.All sections that will have a specific coding form are called expression.Each expression has the initialization segments of a correspondence, and this initialization segments means that in difference in (comprising the moov box in the 3GPP situation) can be public.Each period has implied new moov box and demoder initialization.
Current in the standard of HTTP flow transmission, do not require that client fetches the MPD of renewal between the live stream transmission period with regular intervals.Address via from MPD to client notice media segment.When together with live stream transmission, using the playlist structure of MPD, can carry out next or once several MPD that upgrades with the position of the section of new coding.Client is fetched the MPD of renewal by sending HTTP GET or part GET (the usable range request header carrys out the GET of specified bytes scope).Therefore, if client the MPD of 30 minutes has been got back to fact present in and the user want to start to watch from presenting, client has next 30 minutes required all fragment position (supposition time migration buffer zone is at least 30 minutes on the duration).Therefore, client will not need to download new MPD at about 30 minutes in (data will be finished at this moment).In addition, if in MPD, fragment position was announced before creating section, client can be known fragment position in the future, and need to when each new section is encoded, not fetch MPD.Thereby client can not fetched the MPD of renewal continually very much.For two kinds of situations 1) client listen to after a while (seeing) fact present and want from start to watch/listen to present and 2) just announced fragment position make client can know well fragment position in the future before fragment position exist, client can not fetched according to standard the MPD of renewal on relatively long interval.
The information guiding 3GPP adaptive H TTP flow transmission client provided in MPD.When the request in response to for up-to-date MPD, client is successfully fetched MPD, client or receive the MPD upgraded, or receive allowing client validation to fetch the indication that this MPD not yet upgrades since the last time.
According to existing standard, force client only in following situation, to fetch the MPD of renewal: when it receives a plurality of 404http error code, if or its be finished fragment position information.Thereby server can not cause that client upgrades its MPD delicately, and can not delicately its media file or section be moved to diverse location.
In addition, even supposing before section is actual available, client also can be announced the media segment position.Therefore, client can be known the position in future of media segment before the media segment physical presence.Therefore, when client must become available for each section this section of calculating.Client can not be supposed: because the media segment position is available in MPD, so media segment itself is available.
In order to require delicately client to upgrade its MPD, can upgrade and occur to client notice MPD by the one or more indications in the box in the section of media file.In other words, can in band, to client notice MPD, upgrade and occur.Below show example media and upgrade box:
Figure BDA00003634901600031
For this example, use following semantic:
Mpd_information_flags: the zero that comprises following reason code or the present media of more logical "or"s: 0x00 present describe to upgrade, 0x01 the preceding media present describe upgrade, 0x02 present finish and 0x03～0x07 reserved;
New_location_flag: if be made as 1, in the new position of mpd_location appointment new media present describe available;
Latest_mpd_update_time: indication is with respect to the time of sending up-to-date MPD (being that MPD sends the time), when, the MPD renewal is essential (take millisecond as unit), makes client any time between present and latest_mpd_update_time to upgrade MPD; And
Mpd_location: and if only if just occurs while being provided with new_location_flag, and it provides the URL(uniform resource locator) (URL) that presents description for new media.
The accompanying drawing explanation
In order more completely to understand the disclosure, with embodiment, following concise and to the point description is carried out to reference by reference to the accompanying drawings now, wherein, similar Reference numeral means similar part.
Fig. 1 is the figure be configured to according to the radio hand-held equipment as client work of the present disclosure;
Fig. 2 is the figure be configured to according to the system of disclosure work;
Fig. 3 shows the figure be configured to according to the message of the system of disclosure work;
Fig. 4 is for receiving the process flow diagram via the method presented of HTTP flow transmission according to of the present disclosure;
Fig. 5 is for sending the process flow diagram via the method presented of HTTP flow transmission according to of the present disclosure; And
Fig. 6 presents the figure of description according to media of the present disclosure.
Embodiment
In the situation that think appropriate, simple and clear for what illustrate, can be between accompanying drawing repeat reference numerals, to indicate corresponding or similar element.In addition, set forth a large amount of details so that the thorough understanding to embodiment described herein to be provided.Yet, those skilled in the art will appreciate that: can be in the situation that do not have these details to realize each embodiment as herein described.In other examples, do not describe well-known method, process and assembly in detail, not outstanding not make each embodiment described herein.In addition, this description should be considered as the scope of each embodiment described herein is limited.
Be received in the client that presents (that is, presenting the media segment that is not up-to-date) of working outside the time migration buffer zone via the HTTP flow transmission and may can't see in band and upgrade, and may be unaware of the MPD position and change.
In addition, if the reason of change is not provided to client, it may fetch up-to-date MPD when it is unwanted.For example, can upgrade MPD by the mode that does not affect client, for example, the reason of upgrading as MPD is to start the new period, but client just in time receives the input for backward searching in time (seek back).This client does not need to fetch MPD in this moment.On the other hand, if all sections of meaning or MPD are adjourned to different servers, client need to be fetched up-to-date MPD to obtain the position of section.In the situation that mean to be positioned on different server and one or more (but not being whole) expression of having had moved, additional information can be useful for client aspect the change reason.If the expression of client current consumption is not yet moved, client does not need to fetch at once up-to-date MPD or starts and fetches media segment from new position.On the other hand, if the expression of client current consumption is moved, if in band, do not provide position, client will want to fetch at once up-to-date MPD.If in band, provide new positional information, it will want the position got started from new to fetch media segment.
In-band signaling (that is, MPD upgrade box) can comprise indication MPD upgrade reason and/or comprise the impact which presenting partly changed indication present metadata.This with indication form presents metadata and allows client to determine when to fetch up-to-date renewal.
Can use there is sign, the indication of the form of reason code or this paper string.Sign can be indicated the Boolean of the following: 1) new section is available, 2) other parameter values that new MPD position, 3) new fragment position, 4) to MPD, upgrade or add.Reason code can be indicated a plurality of reasons via single value, and for example the new section of code 0x01=is available, the new MPD of 0x02=position, and the 0x03=parameter is upgraded etc.Standardized text string can be indicated reason with the human-readable form.
According to current HTTP flow transmission standard, can and mean on rank to use basic URL (base URL) in MPD in MPD rank, period rank.If in these basic URL, any one changes, to indicate new server and/or position, this can allow client know.Can exist MPD rank change indication, concrete period to change indication (being likely interval I D (periodID) or start time period) or specifically mean to change indication (by meaning that ID indicates).Even also likely the physical segment of indicating gauge in showing moved, for example, and by indicating each segment index of influenced section.
As a specific example, MPD upgrades box (mpdu) provides MPD is upgraded in the band occurred and indicates to HTTP flow transmission client.In addition, the sign that it also provides indication to upgrade reason, and if reason be because needs visit MPD itself or media segment from reposition, provide and which period, expression and the relevant information that section is affected.Below show the example mpdu with definition:
Figure BDA00003634901600061
New_segments_available_flag: if be provided with this sign, used new section to upgrade MPD;
New_MPD_location_flag: if be provided with this sign, MPD can use in new position;
Segment_locations_change_flag: if be provided with this sign, in MPD before the position of at least one section of announcement change;
Parameters_added_or_updated_flag: if be provided with this sign, at least one attribute or the element that in MPD, with fragment position, have nothing to do change;
Changed_segments_indicated_flag: can only in the situation that be provided with new_segment_location_change_flag, this sign be set.It is used to indicate: box comprises about changing the information of which section.
New_MPD_URL: be the character string of UTF-8 character with " null " ending, and and if only if just exists while being provided with newMPD_location_flag.The URL that this character string comprises new MPD;
BaseURL_MPD_level_changed_flag: if the value of baseURL attribute changes on the MPD rank in up-to-date MPD upgrades, this parameter is set;
Number_of_periods_with_location_changes: be without symbol 15 bit integer, it has provided and has comprised the period number that certain type position changes.This can be xlink:href property value, the baseURL of period or any change on period intrinsic representation or section rank of period itself.
Period_start: be the character string with the UTF-8 character of " null " ending.The value of the beginning attribute that this character string comprises the period;
Period_xlink_change_flag: if while quoting, the value of the xlink:href attribute of fragment position changes, this parameter is set in up-to-date MPD upgrades;
Period_baseURL_change_flag: if the value of the baseURL attribute of period changes in up-to-date MPD upgrades, this parameter is set;
Number_of_representations_with_location_changes: be without symbol 14 bit integer, it has provided the expression number within the period that comprises certain type position change.This can mean the xlink:href attribute of itself, baseURL or any change on the section rank within meaning of expression;
Representation_id: be the character string with the UTF-8 character of " null " ending, the value of the id attribute that it comprises expression;
Representation_xlink_change_flag: change if quote the value of locative xlink:href attribute in up-to-date MPD upgrades, this parameter is set;
Representation_baseURL_change_flag: if the value of baseURL attribute changes on the expression rank in up-to-date MPD upgrades, this parameter is set;
Number_of_segment_level_location_changes: be without symbol 14 bit integer, it has provided the number (on the section rank) that the sourceURL position changes;
Segment_index: be without symbol 15 bit integer, it has provided the value of the index of section.Indicate initialization segments with the index of 0x7FFF; And
SourceURL_change_flag: if the value of the sourceURL attribute of the section corresponding with segment_index becomes in up-to-date MPD upgrades, this parameter is set.
In addition, can change to add reposition itself for Servers-all/position.This provide can with in find all lastest imformations of MPD, and client even can not need to fetch MPD.Below show the example mpdu with definition:
Figure BDA00003634901600081
Figure BDA00003634901600091
New_segments_available_flag: if be provided with this sign, by new section, upgraded MPD;
New_MPD_location_flag: if be provided with this sign, MPD can use in new position;
Segment_locations_change_flag: if be provided with this sign, in MPD before the position of at least one section of announcement change;
Parameters_added_or_updated_flag: if be provided with this sign, at least one attribute or the element that in MPD, with fragment position, have nothing to do change;
New_segment_locations_present_flag: can only in the situation that be provided with new_segment_locations_change_flag, just this sign can be set.It is used to indicate box and comprises new fragment position information;
New_MPD_URL: be the character string of UTF-8 character with " null " ending, and and if only if is provided with just existence in the situation of newMPD_location_flag, and the URL that comprises new MPD;
BaseURL_MPD_level: be the character string of UTF-8 character with " null " ending, and if in latest update the value of baseURL attribute on the MPD rank, change, comprise this value; If this value does not change or be undefined, character string is empty, and only has " null " final character;
Number_of_periods_with_location_changes: be without symbol 16 bit integer, it has provided and has comprised the number of certain type position change in the interior period; This can be xlink:href property value, the baseURL of period or any change on period intrinsic representation or section rank of period itself;
Period_start: be the character string with the UTF-8 character of " null " ending, and the value of the beginning attribute that comprises the period;
Period_xlink: be the character string of UTF-8 character with " null " ending, and if in up-to-date renewal to the time fragment position xlink:href attribute quoted value change, comprise this value; If this value does not change or the period is not quoted via xlink, character string is empty, and only has " null " final character;
Period_baseURL: be the character string of UTF-8 character with " null " ending, and if in latest update the value of baseURL attribute on the period rank, change, comprise this value; If this value does not change or be undefined, character string is empty, and only has " null " final character;
Number_of_representations_with_location_changes: be without symbol 16 bit integer, it has provided and has comprised the number of certain type position change in interior expression; This can mean the xlink:href attribute of itself, baseURL or any change on the section rank within meaning of expression;
Representation_id: be the character string with the UTF-8 character of " null " ending, the value of the id attribute that comprises expression;
Representation_xlink: be the character string with the UTF-8 character of " null " ending, and if in up-to-date renewal, the value that means the xlink:href attribute that position is quoted is changed, comprise this value; If this value does not change or means, via xlink, do not quoted, character string is empty, and only has " null " final character;
Representation_baseURL: be the character string of UTF-8 character with " null " ending, and if in latest update the value of baseURL attribute on rank, change meaning, comprise this value; If this value does not change or be undefined, character string is empty, and only has " null " final character;
Number_of_segment_level_location_changes: be without symbol 16 bit integer, it has provided the number (on the section rank) that the sourceURL position changes;
Segment_index: be without symbol 16 bit integer, it has provided the value of the index of section; Make index of reference 0xFFFF indicate initialization segments; And
New_sourceURL: be the character string with the UTF-8 character of " null " ending, and the value of the sourceURL attribute that comprises the section corresponding with segment_index.
Can to another example of the information of client transmissions, be the content of MPD delta file via the box in media segment.The MPD delta file is to comprise as MPD to upgrade the description of the MPD each several part that the result of (or a plurality of renewal) changed and/or the actual variance between it at interior differential file.Can on server, support the MPD increment, because compare with downloading whole MPD, they more save bandwidth (when the actual change of information of relative small part is particularly only arranged in MPD) when downloading.The MPD delta file can be XML file itself, can be maybe text such as unix diff file etc.Alternative as MPD delta file available on server, or combine with MPD delta file available on server, the binary version of XML code, the text-string that comprises the MPD increment or the MPD increment of the content that comprises the MPD delta file can be encapsulated in the box comprised in media segment.
Therefore make and do not require that client carrys out computing medium section availability for each media segment, whether the attribute in MPD can indicate each section available at once, or to client, notifies in advance.For example, attribute can be segmentsAdvertised or segmentsAvailable attribute.If by the segmentsAdvertised setup of attribute be true or segmentsAvailable is set to puppet, announce each section, and each section may not available at once for client.Therefore, though the position of media segment in MPD, client can not suppose that media segment is present on server.In this case, must carry out and the when available relevant calculating of media segment time and duration based on providing in MPD.If be pseudo-by the segmentsAdvertised setup of attribute, or be true by the segmentsAvailable setup of attribute, client can suppose that media segment can use, and skips regularly and calculate.
Fig. 1 is the figure be configured to according to the radio hand-held equipment as client work of the present disclosure.Radio hand-held equipment 100 comprises numeric keypad 101, display 102 and one or more processor (not shown).One or more processors of equipment 100 are configured to take on HTTP flow transmission client and carry out method of the present disclosure.Equipment 100 can be configured to carry out work according to various cellular telephone communication standards (comprising 3GPP).
Fig. 2 is the figure be configured to according to the system of disclosure work.System 201 comprises client 202 and server 203, and they are via network 204 communication connections.
Client 202 can be any equipment presented for reception according to of the present disclosure.Its example comprises: mobile phone (for example, radio hand-held equipment 100), notebook, net book computing machine, flat-panel devices, laptop computer, desk-top computer etc., carry out work according to various 3GPP standards.
Server 203 can be any equipment that presents description for transmission according to of the present disclosure.Although be depicted as single server, server 203 can comprise a plurality of servers, computing machine, processor, storer and data warehouse.Server 203 can store M PD, and can also store and have presenting of one or more sections forms.Alternatively, can be on different server, storer and data warehouse (not shown) or among one or more sections of storages.
Network 204 can be that any type of communication or the network of style are provided between client 202 and server 203.Its example comprises: the public wireless carrier network of internet and mobile phone.
Fig. 3 shows the figure be configured to according to the message of the system of disclosure work.301, client 202 for example sends, for example, for presenting descriptions (, request 302 (, HTTP GET asks) MPD) to server 203.303, server 203 receives for the request 302 that presents description from client 202.
304, client 202 receives first from server 203 and presents description 305.306, server 203 sends first to client 304 and presents description 305.First presents and describes 305 positions that comprise first paragraph 311, as it to the following part comprised: with present one or more sections of being associated at least one quote.By presenting description 305 each that describe section, with the URL(uniform resource locator) (URL) of the fragment position of indicating each section and possible bytes range, be associated.
307, the request 308 that client 202 sends for first paragraph 311 to server 203.As mentioned above, server 203 can comprise a plurality of servers, makes different server to store and presents description and section.309, server 203 from client 202 receive for the request 308 of first paragraph 311.
310, client 202 receives the first paragraph 311 of asking from server 203.312, server 203 is to client 202 delivery sections 311.First paragraph 311 comprises and presents metadata, as mentioned above, presents the reason that metadata indication MPD upgrades and/or the indication that comprises the impact which presenting partly changed.
313, client 202 sends the request 314 that presents description (for example, the MPD of renewal) for second to server 203.315, server 203 receives the request 314 that presents description for second from client 202.For the second request 314 that presents description be by client 202 at least in part based on present metadata to first present describe relevant and together with first paragraph received part send.For example,, when presenting metadata and indicate one or more fragment position to change.
316, client 202 receives second from server 203 and presents description 317.318, server 203 sends second to client 202 and presents description 317.Second presents and describes 317 and be included in and present the institute indicated in metadata and change.
319, the request 320 that client 202 sends for second segment to server 203.321, the request 320 that server 203 receives for second segment 323.Request 320 presents and describes 317, the second and present that to describe 317 be according to presenting the indicated change of metadata according to second.Like this, with request, 308 compare, asking 320 can be for different server.In addition, ask 308 can be the part request of the part of only request segment.
322, client 202 receives second segment 323 from server 203.324, server 203 sends second segment 323 to client 202.As mentioned above, sending the second server that presents description 317 can be different from the server of delivery section.In addition, receive second before this one or more in section, period meaned in client device consumption being described or having presented description and present the situation of describing 317.
Fig. 4 is for receiving the process flow diagram that carrys out the method presented of flow transmission via HTTP according to of the present disclosure.Send the request that presents description for first in 401, HTTP flow transmission client.
402, the request of client based on from 401 receives first and presents description.First presents the fragment position that description comprises first paragraph.
403, client sends the request for the first paragraph presented.The fragment position of this request based on describing in presenting description.
404, the client first paragraph, first paragraph also comprises and presents metadata.As mentioned above, present metadata and comprise for upgrading first and present the indication of any reason of description, and can comprise the part of actual renewal or renewal.
405, the request of client transmitting portion based on presenting metadata.This request second presents one of second segment of describing or presenting for what present.This request can the section based on whether presenting description be designated as be advertised or be designated as available.If section is indicated as and is advertised, when available must before sending for the request of section, calculate this section for client.If section is indicated as availablely, not necessarily when available compute segment is for client, and access segment at once.In other words, when existing section available indication at once, client can be in the situation that do not calculate its availability request segment.
Availability indication can be included in first present in description and/or the box of first paragraph in.In an embodiment, client: send the request that presents description for first; Reception comprises that first of availability indication presents description; Indicate to carry out the availability calculations to the availability of one or more sections based on availability; And present based on first the availability that description comprises and indicate to send request.Therefore, when one or more sections are designated as while can be used for being accessed at once by client, this equipment is not carried out availability calculations.
In alternative, indicated that to present the section of listing in description available even listed section and availability in presenting description, section also no longer available outside the time migration buffer zone.In this case, if availability has been indicated, made media to use, needed only media in the time migration buffer zone, client does not just need calculate or otherwise determine whether to have made media to use.Therefore, client still may determine whether section is actual available.As example, if only provide 30 minutes whens buffering clients to attempt the section of access before 40 minutes at the time migration buffer zone, even availability indication indication made this section available, due to it, outside the time migration buffer zone, this section is also by unavailable.In other words, if the section that availability indication is listed in presenting description is available, and section is in the time migration buffer zone, and client can be accessed this section, that is, client do not need to carry out to section future availability definite.
406, client presents to describe by first and is updated to second and presents description via presenting metadata alternatively.In other words, client alternatively via with first paragraph, receive together present metadata by its first Replica updating that presents description for second present describe consistent.To this more kainogenesis that presents description of client, and present description without client-requested second.Herein, use and to present description increment that metadata comprises and present to describe by first and be updated to second and present description.In other words, upgrade to present to describe by first being updated to second and presenting description in the client place is used band, the interior renewal of this band will present presenting in metadata in the box that increment is included in first paragraph.Alternative can in the box of the separation of section, have the increment of description and other present metadata.In other words, section can comprise box for presenting metadata and for describing the box of increment.
407, client receives alternatively second and presents description.Herein, the request from 405 presents description for second, and 407, and this second presents description client.As mentioned above, ask at least part based on presenting metadata.
408, client receives second segment alternatively.Herein, the request from 405 is for second segment, and 408, this second segment of client.As mentioned above, this request is the part based on presenting metadata at least, makes the fragment position of using in the request at 405 places can be different from the fragment position of describing in first presents description.In other words, client is used from the request second segment of more newly arriving in the band that presents metadata received together with first paragraph.
Fig. 5 is for sending the process flow diagram that carrys out the method presented of flow transmission via HTTP according to of the present disclosure.501, server receives the request that presents description for first.
502, the content requests of server based in 501 receptions sends first and presents description.First presents the fragment position that description comprises first paragraph.
503, server receives the request for the first paragraph presented.The fragment position of this request based on describing in presenting description.
504, server upgrades the metadata that presents in the first paragraph presented alternatively.This renewal can be in response to presenting the change of description to first, and can occur in sent first present describe after and any time before sending first paragraph.
505, server sends and comprises the first paragraph that presents metadata.As mentioned above, present metadata and comprise for upgrading first and present the indication of any reason of description, and can comprise actual renewal.
506, the request of server receiving unit based on presenting metadata.This request second presents one of second segment of describing or presenting for what present.
507, server sends alternatively second and presents description.Herein, the request from 506 presents description for second, and 507, and server sends this and second presents description.As mentioned above, this request part based on presenting metadata at least.
508, server sends second segment alternatively.Herein, the request from 506 is for second segment, and, 508, server sends this second segment.As mentioned above, this request is the part based on presenting metadata at least, makes the fragment position of using in the request at 506 places can be different from the fragment position of describing in first presents description.In other words, use from the request second segment of more newly arriving in the band that presents metadata sent together with first paragraph.
Fig. 6 is the figure according to of the present disclosure section.Section 601 comprises one or more boxes 602.Each box 602 can comprise and present metadata 603.Each presents metadata 603 can comprise at least one indication 604.
Present metadata 603 and comprise one or more indications 604, indication:
At least one new section of not describing before in presenting description is available;
At least one positional information of new section is included in and presents in metadata;
Present and be described in new position and can use;
The position of at least one that before describe in presenting description section can be used in new position;
Present in description at least one attribute or element and change, wherein, this at least one attribute or element and to present the positional information of describing described section irrelevant;
The reposition that presents description;
The value of baseURL attribute changes presenting on the rank of description;
The number of the period changed at least one period;
The value of the periodStart attribute of the period at least one period;
The value of the xlink:href attribute that the position of the period at least one period is quoted changes;
The value of baseURL attribute changes on the period rank, the number of the expression that at least one changes in meaning;
The value of the representationID attribute of the expression at least one expression;
The value of the xlink:href attribute that the position of the expression during at least one is meaned is quoted changes;
The value of baseURL attribute changes on the expression rank;
The number of the section changed at least one section;
The value of the index of the section of writing index at least one section; And
The value of sourceURL attribute of having write the section of index changes.
In addition, the indication 604 value of baseURL attribute changed can comprise the value of baseURL;
The indication 604 that the value of xlink:href attribute has been changed comprises the value of xlink:href attribute;
The indication 604 that the value of baseURL attribute has been changed on the period rank comprises the value of baseURL attribute on the period rank;
The indication 604 that the value of xlink:href attribute has been changed comprises the value of xlink:href attribute;
Value to the baseURL attribute is meaning that the indication 604 changed on rank comprises that the baseURL attribute is meaning the value on rank; And
The indication 604 that the value of sourceURL attribute has been changed comprises the value of sourceURL attribute.
Can on a lot of dissimilar computer-readable mediums, provide the code that is suitable for providing said system and method, this computer-readable medium (for example comprises Computer Storage mechanism, CD-ROM, dish, RAM, flash memory, computer hard disc driver etc.), it has visibly embodied the software instruction for carrying out methods described herein and realizing device described herein of being carried out by one or more processors.
Method and apparatus disclosed herein only presents as example, and is not intended to limit the scope of theme described herein.Other variations of said method and equipment will be apparent for those skilled in the art, and therefore be regarded as in the scope of theme described herein.For example, be to be understood that: can change, revise and/or increase step and sequence of steps in processing described herein, and still realize expected result.

Claims (35)

1. one kind is carried out the method presented of flow transmission via HTTP for reception, and described method comprises:
Receive the described first paragraph presented, described first paragraph comprises and described first presenting and describe the relevant metadata that presents of presenting; And
Be sent to small part and present in metadata based on described the request that presents at least one attribute of description or the relevant part of element to described first.
2. method according to claim 1, wherein, described request for described present second present description.
3. method according to claim 1, wherein, described request is for the described second segment presented.
4. method according to claim 3, wherein, the described metadata that presents comprises the availability indication relevant to the availability of described second segment, and indicates to send described request based on described availability.
5. method according to claim 1, described method also comprises:
Present via described the description increment that metadata comprises, present to describe by described first and be updated to second and present description.
6. method according to claim 1, wherein, the described metadata that presents comprises at least one indication, and each indication is indicated upgrading described the first reason that presents description.
7. method according to claim 6, wherein, the indication in described at least one indication is indicated one of the following:
At least one new section of before not describing in described first presents description is available;
Described at least one positional information of new section is included in described presenting in metadata;
Described first presents and is described in new position and can uses;
The position of at least one section of before describing in described first presents description can be used in new position;
At least one attribute or the element in described first presents description, described change before;
Described first presents the reposition of description; And
The value of baseURL attribute presents on the rank of description and changes described first.
8. method according to claim 7, wherein, the indication that the value of baseURL attribute has been changed comprises the value of described baseURL.
9. method according to claim 6, wherein, second presents to describe and comprises at least one period, and described indication is indicated one of the following:
The number of the period changed in described at least one period;
The value of the periodStart attribute of the period in described at least one period;
The value of the xlink:href attribute that the position of the period in described at least one period is quoted changes; And
The value of baseURL attribute changes on the period rank.
10. method according to claim 9, wherein,
The indication that the value of described xlink:href attribute has been changed comprises the value of described xlink:href attribute; And
The indication that the value of baseURL attribute has been changed on the period rank comprises the value of described baseURL attribute on the period rank.
11. method according to claim 6, wherein, second presents description comprises at least one period, and each period comprises at least one expression, and described indication is indicated one of the following:
The number of the expression changed in described at least one expression;
The value of the representationID attribute of the expression in described at least one expression;
The value of the xlink:href attribute that the position of the expression in described at least one expression is quoted changes; And
The value of baseURL attribute changes on the expression rank.
12. method according to claim 11, wherein,
The indication that the value of described xlink:href attribute has been changed comprises the value of described xlink:href attribute; And
Value to described baseURL attribute is meaning that the indication changed on rank comprises that described baseURL attribute is meaning the value on rank.
13. method according to claim 6, wherein, second presents description comprises at least one period, and each period comprises at least one expression, and each expression comprises at least one section, and described indication is indicated one of the following:
The number of the section changed in described at least one section;
Write the value of index of the section of index in described at least one section; And
The value of sourceURL attribute of having write the section of index changes.
14. method according to claim 13, wherein, the indication that the value of described sourceURL attribute has been changed comprises the value of described sourceURL attribute.
15. one kind is carried out the client device presented of flow transmission via HTTP for reception, described client device comprises at least one processor, and described at least one processor is configured to:
Receive the described first paragraph presented, described first paragraph comprises and described first presenting and describe the relevant metadata that presents of presenting; And
Be sent to small part and present at least one attribute of description or the request of the part that element is associated based on described presenting in metadata with described first;
Wherein, described request is for described second presenting and describe and one of described second segment presented of presenting.
16. client device according to claim 15, wherein, the described metadata that presents comprises the availability indication relevant to the availability of described second segment, and indicates to send described request based on described availability.
17. client device according to claim 15, wherein, described at least one processor also is configured to:
Present via described the description increment that metadata comprises, present to describe by described first and be updated to second and present description.
18. a computer-readable medium that carries code, when for reception, via HTTP, coming the computing equipment presented of flow transmission to carry out described code, described code makes described computing equipment:
Receive the described first paragraph presented, described first paragraph comprises and described first presenting and describe the relevant metadata that presents of presenting; And
Be sent to small part and present at least one attribute of description or the request of the part that element is associated based on described presenting in metadata with described first;
Wherein, described request is for described second presenting and describe and one of described second segment presented of presenting.
19. computer-readable medium according to claim 15, wherein, the described metadata that presents comprises the availability indication relevant to the availability of described second segment, and indicates to send described request based on described availability.
20. computer-readable medium according to claim 15, wherein, described code also makes described computing equipment:
Present via described the description increment that metadata comprises, present to describe by described first and be updated to second and present description.
21. one kind is carried out the method presented of flow transmission via HTTP for reception, described method comprises:
Receive (310,404) described first paragraph presented (311,601), described first paragraph comprise to described present first present description (305) relevant present metadata (603); And
Send (313,319,405) and present in metadata (603) based on described the request (314,320) that presents at least one attribute of description (305) or the relevant part of element to described first at least partly.
22. method according to claim 21, wherein, described request (314) for described present second present description (317).
23. method according to claim 21, wherein, described request (320) is for the described second segment presented (323,601).
24. method according to claim 23, wherein, the described metadata (603) that presents comprises the availability indication (604) relevant to the availability of described second segment (323,601), and sends described request (320) based on described availability indication (604).
25., according to the described method of any one in claim 21 to 24, described method also comprises:
Present via described the description increment that metadata (603) comprises, present description (305) by described first and be updated to second and present description (317).
26. according to the described method of any one in claim 21 to 25, wherein, the described metadata (603) that presents comprises at least one indication (604), and each indication (604) is indicated upgrading the described first reason that presents description (305).
27., according to the described method of any one in claim 21 to 26, wherein, the indication (604) in described at least one indication (604) is indicated one of the following:
At least one new section (601) of before not describing in described first presents description (305) are available;
The positional information of described at least one new section (601) is included in described presenting in metadata (603);
Described first presents description (305) can use in new position;
The position of at least one section (601) of before describing in described first presents description (305) can be used in new position;
At least one attribute or the element in described first presents description (305), described change before;
Described first presents the reposition of description (305); And
The value of baseURL attribute presents on the rank of description (305) and changes described first.
28. method according to claim 27, wherein, the indication (604) that the value of baseURL attribute has been changed comprises the value of described baseURL.
29., according to the described method of any one in claim 21 to 26, wherein, described second presents description (317) comprises at least one period, and described indication (604) is indicated one of the following:
The number of the period changed in described at least one period;
The value of the periodStart attribute of the period in described at least one period;
The value of the xlink:href attribute that the position of the period in described at least one period is quoted changes; And
The value of baseURL attribute changes on the period rank.
30. method according to claim 29, wherein,
The indication (604) that the value of described xlink:href attribute has been changed comprises the value of described xlink:href attribute; And
The indication (604) that the value of baseURL attribute has been changed on the period rank comprises the value of described baseURL attribute on the period rank.
31., according to the described method of any one in claim 21 to 26, wherein, described second presents description (317) comprises at least one period, each period comprises at least one expression, and described indication (604) is indicated one of the following:
The number of the expression changed in described at least one expression;
The value of the representationID attribute of the expression in described at least one expression;
The value of the xlink:href attribute that the position of the expression in described at least one expression is quoted changes; And
The value of baseURL attribute changes on the expression rank.
32. method according to claim 31, wherein,
The indication (604) that the value of described xlink:href attribute has been changed comprises the value of described xlink:href attribute; And
Value to described baseURL attribute is meaning that the indication (604) changed on rank comprises that described baseURL attribute is meaning the value on rank.
33. according to the described method of any one in claim 21 to 26, wherein,
Described second presents description (317) comprises at least one period,
Each period comprises at least one expression,
Each expression comprises at least one section (601), and described indication (604) is indicated one of the following:
The number of the section (601) changed in described at least one section (601);
Described at least one section has been write the value of index of the section of index in (601); And
The value of sourceURL attribute of having write the section of index changes; And
The indication (604) that the value of described sourceURL attribute has been changed comprises the value of described sourceURL attribute.
34. a client device (100,202) comprising:
Display (102); And
One or more processors, be configured to carry out according to the described method of any one in claim 21 to 33.
35. a computer-readable medium that carries code, when carrying out described code, described code makes computing equipment (100,202) carry out according to the described method of any one in claim 21 to 33.
CN201280008025.5A 2011-02-07 2012-02-07 For receiving the method and apparatus that metadata is presented Active CN103443741B (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US13/022,572 US9661104B2 (en) 2011-02-07 2011-02-07 Method and apparatus for receiving presentation metadata
US13/022,572 2011-02-07
PCT/US2012/024123 WO2012109226A1 (en) 2011-02-07 2012-02-07 Method and apparatus for receiving presentation metadata

Publications (2)

Publication Number Publication Date
CN103443741A true CN103443741A (en) 2013-12-11
CN103443741B CN103443741B (en) 2018-01-30

Family

ID=46601425

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201280008025.5A Active CN103443741B (en) 2011-02-07 2012-02-07 For receiving the method and apparatus that metadata is presented

Country Status (6)

Country Link
US (1) US9661104B2 (en)
EP (1) EP2673686B1 (en)
CN (1) CN103443741B (en)
CA (1) CA2826552C (en)
TW (1) TWI450127B (en)
WO (1) WO2012109226A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105794160A (en) * 2014-01-06 2016-07-20 英特尔公司 Client/server signaling commands for DASH
CN106570044A (en) * 2015-10-13 2017-04-19 北京国双科技有限公司 Method and device for analyzing webpage code

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9432433B2 (en) 2006-06-09 2016-08-30 Qualcomm Incorporated Enhanced block-request streaming system using signaling or block creation
US9917874B2 (en) 2009-09-22 2018-03-13 Qualcomm Incorporated Enhanced block-request streaming using block partitioning or request controls for improved client-side handling
CN107071513B (en) * 2011-03-16 2020-03-10 艾迪尔哈布股份有限公司 Method, client and server for providing media content
US20120278495A1 (en) * 2011-04-26 2012-11-01 Research In Motion Limited Representation grouping for http streaming
US8924582B2 (en) 2012-07-09 2014-12-30 Futurewei Technologies, Inc. Dynamic adaptive streaming over hypertext transfer protocol client behavior framework and implementation of session management
CN104871514B (en) * 2012-10-18 2019-04-05 Vid拓展公司 The decoding complex degree of mobile multimedia stream
US10440084B2 (en) * 2013-02-06 2019-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Technique for detecting an encoder functionality issue
US9648320B2 (en) * 2013-02-22 2017-05-09 Comcast Cable Communications, Llc Methods and systems for processing content
CN105379293B (en) 2013-04-19 2019-03-26 华为技术有限公司 Media quality informa instruction in dynamic self-adapting Streaming Media based on hyper text protocol
WO2015009723A1 (en) * 2013-07-15 2015-01-22 Huawei Technologies Co., Ltd. Just-in-time dereferencing of remote elements in dynamic adaptive streaming over hypertext transfer protocol
CN105230024B (en) * 2013-07-19 2019-05-24 华为技术有限公司 A kind of media representation adaptive approach, device and computer storage medium
KR20170030490A (en) * 2014-07-07 2017-03-17 소니 주식회사 Reception device, reception method, transmission device, and transmission method
US10412461B2 (en) * 2015-06-12 2019-09-10 Cable Television Laboratories, Inc. Media streaming with latency minimization
US10205991B2 (en) * 2015-07-27 2019-02-12 Sony Corporation Hidden replaceable media slots
CN107040615B (en) * 2017-06-22 2021-07-02 深圳Tcl数字技术有限公司 Downloading method of media fragment, terminal and computer readable storage medium
US10904642B2 (en) * 2018-06-21 2021-01-26 Mediatek Singapore Pte. Ltd. Methods and apparatus for updating media presentation data
US11593085B1 (en) * 2020-02-03 2023-02-28 Rapid7, Inc. Delta data collection technique for machine assessment
KR20240052834A (en) * 2021-10-01 2024-04-23 바이트댄스 아이엔씨 Video processing methods, devices and media

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090303255A1 (en) * 2008-02-22 2009-12-10 Nokia Corporation Systems and methods for providing information in a rich media environment
US20100235472A1 (en) * 2009-03-16 2010-09-16 Microsoft Corporation Smooth, stateless client media streaming
US20100235528A1 (en) * 2009-03-16 2010-09-16 Microsoft Corporation Delivering cacheable streaming media presentations
US20100262711A1 (en) * 2009-04-09 2010-10-14 Nokia Corporation Systems, methods, and apparatuses for media file streaming
US20100318600A1 (en) * 2009-06-15 2010-12-16 David Furbeck Methods and apparatus to facilitate client controlled sessionless adaptation

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4692950B2 (en) * 2004-06-11 2011-06-01 ソニー株式会社 Data processing apparatus, data processing method, program, program recording medium, and data recording medium
US7529726B2 (en) * 2005-08-22 2009-05-05 International Business Machines Corporation XML sub-document versioning method in XML databases using record storages
US9432433B2 (en) * 2006-06-09 2016-08-30 Qualcomm Incorporated Enhanced block-request streaming system using signaling or block creation
US7716699B2 (en) 2006-06-29 2010-05-11 Microsoft Corporation Control and playback of media over network link
JP2009059160A (en) 2007-08-31 2009-03-19 Sony Corp Server device, network system, content discovery notification method and computer program
US8914835B2 (en) * 2009-10-28 2014-12-16 Qualcomm Incorporated Streaming encoded video data
WO2011057012A1 (en) * 2009-11-04 2011-05-12 Huawei Technologies Co., Ltd System and method for media content streaming
US8510375B2 (en) * 2009-12-11 2013-08-13 Nokia Corporation Apparatus and methods for time mapping media segments in streaming media files
CN102714662B (en) * 2010-01-18 2017-06-09 瑞典爱立信有限公司 For the method and apparatus of HTTP media stream distribution
US9497290B2 (en) * 2010-06-14 2016-11-15 Blackberry Limited Media presentation description delta file for HTTP streaming
US8468262B2 (en) * 2010-11-01 2013-06-18 Research In Motion Limited Method and apparatus for updating http content descriptions

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090303255A1 (en) * 2008-02-22 2009-12-10 Nokia Corporation Systems and methods for providing information in a rich media environment
US20100235472A1 (en) * 2009-03-16 2010-09-16 Microsoft Corporation Smooth, stateless client media streaming
US20100235528A1 (en) * 2009-03-16 2010-09-16 Microsoft Corporation Delivering cacheable streaming media presentations
WO2010107627A2 (en) * 2009-03-16 2010-09-23 Microsoft Corporation Delivering cacheable streaming media presentations
US20100262711A1 (en) * 2009-04-09 2010-10-14 Nokia Corporation Systems, methods, and apparatuses for media file streaming
US20100318600A1 (en) * 2009-06-15 2010-12-16 David Furbeck Methods and apparatus to facilitate client controlled sessionless adaptation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Live Services and Timing for DASH", 《LIVE-SERVICES-TIMING，3RD GENERATION PARTNERSHIP PROJECT(3GPP）》 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105794160A (en) * 2014-01-06 2016-07-20 英特尔公司 Client/server signaling commands for DASH
CN105794160B (en) * 2014-01-06 2019-08-20 英特尔Ip公司 Client/server signaling command for DASH
CN106570044A (en) * 2015-10-13 2017-04-19 北京国双科技有限公司 Method and device for analyzing webpage code
CN106570044B (en) * 2015-10-13 2019-12-24 北京国双科技有限公司 Method and device for analyzing webpage codes

Also Published As

Publication number Publication date
EP2673686A1 (en) 2013-12-18
US9661104B2 (en) 2017-05-23
TWI450127B (en) 2014-08-21
WO2012109226A1 (en) 2012-08-16
CN103443741B (en) 2018-01-30
EP2673686A4 (en) 2016-05-25
TW201246002A (en) 2012-11-16
US20120203867A1 (en) 2012-08-09
CA2826552A1 (en) 2012-08-16
EP2673686B1 (en) 2018-04-18
CA2826552C (en) 2016-07-19

Similar Documents

Publication Publication Date Title
CN103443741A (en) Method and apparatus for receiving presentation metadata
CA2816537C (en) Method and apparatus for updating http content descriptions
US8095626B2 (en) System and method for configuring a client electronic device
US20160029051A1 (en) Streaming Playback and Dynamic Ad Insertion
EP2887297A1 (en) Method and device for providing targeted content
WO2011143168A1 (en) Providing text content embedded with multimedia content
US20140100963A1 (en) Method, System and Device For Filtering Mobile Terminal Webpage Advertisements
US20120233235A1 (en) Methods and apparatus for content application development and deployment
KR20180043392A (en) How to recommend applications
CN114666308A (en) Request-based encoding system and method for streaming content portions
CN107656768B (en) Method and system for controlling page jump
CN108811515B (en) Delivering automatically playing media content elements from cross-source resources
CN104765617A (en) Stream application function interface distributing method and system realized on basis of HTML5
CN102948125A (en) System and method for delivery of content objects
CN102362272A (en) Device dependent on-demand compiling and deployment of mobile applications
CN101405723A (en) Estimation of initial dynamic rendering control data
EP3559818B1 (en) Maintaining session identifiers across multiple webpages for content selection
CN109716731A (en) For providing the system and method for functions reliably and efficiently data transmission
CN110677443A (en) Data transmitting and receiving method, transmitting end, receiving end, system and storage medium
US10101801B2 (en) Method and apparatus for prefetching content in a data stream
CN103370919A (en) Partial object caching
CN106603380A (en) Data transmitting method and apparatus
KR100823270B1 (en) Method and apparatus for storing contents
WO2009085718A2 (en) Method and apparatus to facilitate provision and use of a media source bundle
Irelan RSS: The Plumbing Behind the Medium

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1192337

Country of ref document: HK

GR01 Patent grant
GR01 Patent grant
REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1192337

Country of ref document: HK

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20240605

Address after: Illinois

Patentee after: Ot patent trusteeship Co.,Ltd.

Country or region after: U.S.A.

Address before: Voight, Ontario, Canada

Patentee before: BlackBerry Ltd.

Country or region before: Canada

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20240702

Address after: Ai Erlandubailin

Patentee after: Maliki Innovation Co.,Ltd.

Country or region after: Ireland

Address before: Illinois

Patentee before: Ot patent trusteeship Co.,Ltd.

Country or region before: U.S.A.