EP2965531A1 - Fourniture de données vidéo - Google Patents

Fourniture de données vidéo

Info

Publication number
EP2965531A1
EP2965531A1 EP14703153.8A EP14703153A EP2965531A1 EP 2965531 A1 EP2965531 A1 EP 2965531A1 EP 14703153 A EP14703153 A EP 14703153A EP 2965531 A1 EP2965531 A1 EP 2965531A1
Authority
EP
European Patent Office
Prior art keywords
video
time stamp
event
chunks
sequence
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.)
Ceased
Application number
EP14703153.8A
Other languages
German (de)
English (en)
Inventor
Andrew Peter Gower
Stephen Howard Johnson
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.)
British Telecommunications PLC
Original Assignee
British Telecommunications PLC
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
Priority claimed from EP13250026.5A external-priority patent/EP2775731A1/fr
Application filed by British Telecommunications PLC filed Critical British Telecommunications PLC
Priority to EP14703153.8A priority Critical patent/EP2965531A1/fr
Publication of EP2965531A1 publication Critical patent/EP2965531A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • 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/47—End-user applications
    • H04N21/475—End-user interface for inputting end-user data, e.g. personal identification number [PIN], preference data
    • H04N21/4756—End-user interface for inputting end-user data, e.g. personal identification number [PIN], preference data for rating content, e.g. scoring a recommended movie
    • 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/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/84—Generation or processing of descriptive data, e.g. content descriptors
    • 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/8549—Creating video summaries, e.g. movie trailer

Definitions

  • This invention relates to the provision of video data over a communications medium.
  • it is relates to the identification of 'highlights' of a recorded programme, by applying "bookmark" data to the programme.
  • These can be used by the user who created them, or other users, to identify the parts of greatest interest. They may be used, for example, to identify parts of the broadcast for compilation into a short video sequence.
  • the provision of such highlights is an important part of many television services, particularly in sports coverage.
  • the extracts required to compile a sequence of "highlights" clips are typically created from within a longer video sequence using standard digital video editing tools that define the start and end points of each video clip either directly or by reference to a key event within the clip.
  • Each clip is typically saved as an independent file which can subsequently be provided to viewers.
  • a viewer requesting a "highlights" sequence is provided with an address, or set of addresses, from which to retrieve the clips that make up the required sequence.
  • the present invention provides a video service platform for generating video clips from a sequence of video data elements for delivery and playback on demand, comprising:
  • a user input unit for receiving a plurality of individual time stamp data inputs, each generated by a respective user, identifying a part of the video data to be used to generate a clip
  • an aggregation system for calculating an aggregated time stamp value derived from the plurality of the individual lime stamp data
  • an event marker unit for associating an event marker flag with an element of the video data sequence in accordance with the aggregated time stamp data
  • an output unit for generating a video clip from a plurality of video data elements defined by relation to the event marker flag.
  • the invention also provides a method for generating video clips from a sequence of video data elements for delivery and playback on demand, wherein individual time stamp data inputs generated by each of a plurality of users identifying a part of the video data to be used to generate clips are aggregated to calculate an aggregate time stamp value, and associating an event marker flag with an element of the video data sequence in accordance with the aggregated time stamp.
  • the process for determining the aggregate time stamp value may be selected according to metadata associated with the individual time stamp values, and/or the distribution of time stamp data inputs.
  • the distribution of time stamp data inputs may also be used to control the duration of part of a video clip before and/or after the event marker for that clip, for example by selecting a total duration time, or selecting the proportion of the clip that appears before the event marker.
  • the invention enables viewers to identify a number of key events within a video sequence (such as goals in a football match) using viewer-defined 'temporal bookmarks'. These bookmarks are stored as time-codes along with associated metadata which identifies the time-code as belonging to a certain type of event.
  • a first value marks a key event and a second value is used to define a ratio to identify the relative duration of the clip to be provided before and after the marked point.
  • the actual duration can be adjusted whilst preserving this ratio.
  • a clip can be identified and generated easily and in real-time on a live video stream by a non-expert user through a single interaction at the moment of the key event.
  • users may vary in the time they take to respond to the key event, either through unfamiliarity with the control device, variations in the time taken to realise the significance of the event, external distractions, etc. This can reduce the effectiveness of the system as different users will receive different clips, showing more or less of the events of interest.
  • the clips would have to be long enough to ensure that the key moment (goal, catch, putt, overtaking manoeuvre, according to the sport in question), is caught, resulting in any clip delivered being likely to include more of the events leading up to, and/or following, the key moment than is desirable. This in turn means that fewer clips can be shown to a user in a given time.
  • a further disadvantage is that a very large number of event markers are stored. As well as causing a storage problem for the service provider, it makes retrieval difficult, especially if the clips are made available to viewers who did not see or bookmark the original broadcast, or parts of it, and wish to use the bookmarks to create a highlights sequence. Many of the bookmarks will relate to the same event and, without detailed analysis, it would be difficult for a user to identify which of the many bookmarks relating to an event will provide the most accurate view. Even for the users who created the bookmarks, their reaction times may vary from one mark to another which will result in the start and end points of some clips being earlier or later than is desirable.
  • the present invention overcomes this by analysing the temporal distribution of event markers generated by a plurality of users during a video transmission (which may be streamed live or may be being watched as an "on-demand" time-shifted recording), identifying event markers in close temporal proximity to each other, generating an aggregated time stamp, and generating an aggregate event marker having the value of the aggregated time stamp.
  • the aggregated value may be a simple median value, or some earlier or later point in the distribution of the time stamps, such as the 25 th percentile.
  • Metadata provided by the users in conjunction with the event markers may be used both to initially identify event markers relating to the same event, and for determining which of a plurality of aggregation processes is to be used for each such group - for example it would be expected that the user's bookmarking action for a "set piece" such as a penalty shot, etc would suffer less scatter than for an unscheduled event such as collisions, goals from free play, etc.
  • a common approach to delivering video over HTTP involves the dissection of large video files into multiple smaller files (called chunks), with each chunk corresponding to a segment of video perhaps a few seconds in length, and each with its own URL (universal resource locator).
  • the a server platform provides a manifest file to the client, which specifies the URL of each chunk of the clip requested, so that the client can request, compile and then play back the video.
  • the manifest file is created and interpreted by the client device so as to prioritise delivery of content based on its narrative importance, by downloading the chunks relating to the key events (such as goals) first, followed by further 'video chunks' in the sequence preceding and following each individual event.
  • Chunks relating to the lower priority events may start to be delivered before delivery of all the chunks of the higher priority ones are complete, by prioritising the defining "event marker" chunk of a lower priority event ahead of chunks occurring some distance before and after the event markers of the high priority events. In any event, after delivery, the chunks are reassembled into their correct chronological order for viewing.
  • This arrangement enables 'highlight clips' to be provided in a flexible manner suited to the bandwidth available. This would be beneficial to viewers using low-capacity networks or those with unreliable coverage, for example as may be experienced by a mobile user. This arrangement would allow the number of individual highlight clips made available to the viewer to be optimised in the presence of restrictions in bandwidth availability or connection reliability. The prioritisation of video chunks would also enable video clips to be dynamically compiled On the fly' matched to specific play-back length restrictions. This facility may be useful when providing 'late- comer' catch-up facilities which would enable the viewer to be provided with a synopsis of key events which took place prior to joining the live stream.
  • Figure 1 depicts a number of different video clips created according to the invention
  • Figure 2 depicts a conventional download sequence for a series of clips
  • Figures 3A, 3B and 3C depict the download sequence for a series of clips according to the invention, for different download conditions
  • Figure 4 depicts a media server and client server arranged to operate according to the invention, and also depicting the process used to compile video data into a clip sequence.
  • Figure 5A depicts a display for use in creating bookmark metadata
  • Figure 5B depicts a display for use in navigating the bookmark metadata and playing back video clips
  • FIG. 6 is a flow diagram illustrating the processes performed in the operation of the invention
  • Figure 7 is a diagram illustrating the capture of bookmark data.
  • the numbers 1 ,2, ....133 etc in Figures 1 and 3 are priority levels, indicating the order in which the video chunks may be delivered to the client, or the (reverse) order in which the chunks should be dropped if a shorter sequence is to be compiled. For example, if each chunk is 1 second in length, there are 6 clips each with equal importance and PPER, and the desired playback duration is 60 seconds, then the playback sequence should only be assembled from chunks with a NIV of 10 or less (60/6). In high bandwidth situations these can be downloaded chronologically In particular note that in Figure 3 more than one chunk has the same priority level. In Figure 2 the numbers indicate the (different) order in which they are to be presented - that is, in chronological order of the events they depict.
  • the mechanisms outlined include:
  • a viewer can identify key events (such as goals) within a video sequence and mark them using 'temporal bookmarks'. These 'temporal bookmarks' can then be used by the viewer to navigate easily back to their favourite moments in the video sequence.
  • Bookmarked events are stored as time- codes along with associated metadata provided by the viewer to classify the event.
  • the metadata enables the individual video chunks to be prioritised for delivery and presentation by the video service provider.
  • the viewer uses a video device 40 such as a television set to view broadcast or recorded video content such as coverage of a sports event.
  • a video device 40 such as a television set to view broadcast or recorded video content such as coverage of a sports event.
  • the viewer may also be using a tablet device 41 or other terminal onto which has been loaded an application ("App").
  • App an application
  • a number of such applications are available which can synchronise such a terminal to the output of a video device 40 linked to a server 42 so that the server can monitor the content being watched by the viewer.
  • the server also has data related to the content being watched. For example for a football match, it would have data on the identities of the teams and individual players.
  • the App provides a user interface that enables the viewer to bookmark the video stream and add metadata to that bookmark.
  • the application loaded on the tablet device 41 allows a user to bookmark events in the television content and add metadata relating to that event, to be stored on the server 42. This enables the user to locate the event in order to share a video clip of it with other users using a social network, or to review the clip again after the event, or participate in a vote or competition which requires the nomination and submission of a clip. ;
  • Event Marker The Event Marker would typically identify the exact moment of the event of interest, for example when a ball crosses the goal mouth, or the moment a bad tackle was committed.
  • Each EM is specified by a time-code, frame or video chunk identifier within a video sequence.
  • the viewer may also provide additional metadata associated with the bookmark (step 63). This would include further information such as the type of event - (goal, pass, shot on goal, save, corner, red card, etc), the main primary person associated with the event - (Footballer, Referee, Manager, linesman, etc), and comments or descriptions the viewer may wish to add to the event to support later retrieval or to add context to the video clip.
  • type of event - goal, pass, shot on goal, save, corner, red card, etc
  • the main primary person associated with the event - “Footballer, Referee, Manager, linesman, etc)
  • comments or descriptions the viewer may wish to add to the event to support later retrieval or to add context to the video clip.
  • Such metadata can also be created automatically to simplify the bookmark creation process. For example, using other data sources 444 (for example the real-time data feed provided by OPTA Sports Ltd) it would be possible for the system to provide data on which player had possession of the ball when the 'save bookmark' button was selected by the viewer.
  • other data sources 444 for example the real-time data feed provided by OPTA Sports Ltd
  • the event markers and additional metadata are recorded in associated XML files 43, 44, (steps 62, 64) typically stored in association with the server device 42 so as to be accessible to both the viewer's Local Area Network and the video service provider.
  • the server 42 can modify the bookmark time-code by using a user-specific Reaction Time Offset value (RTO), (step 61 ) which attempts to minimise differences between when the event actually occurred and when the viewer indicated it occurred.
  • RTO Reaction Time Offset value
  • the RTO for each user can be calculated by using reference video content in which event markers have previously been identified.
  • the average difference between time-code for a reference event marker and the time code of the equivalent event marker identified by a viewer can be used to calculate a user's RTO.
  • this process 61 is depicted as being performed by the server platform 42, but it could be done by the client device 41.
  • the bookmark time-code can be further improved through comparison with bookmarks (600, 601 , 602) created by other viewers.
  • bookmarks 600, 601 , 602
  • identifying a significant number of bookmarks saved by viewers relating to the same event (as identified by metadata applied by the users, or simply by chronological proximity to each other), and calculating a single representative value from them, a more accurate time code for an event marker can be calculated (step 65).
  • This time-code adjustment process would take place on the server's centralised bookmark store 42 and returned to the event marker store 43.
  • the curve 90 represents the cumulative total over time of bookmarks 60, 600, 601 , 602 etc transmitted by different users in relation to a single event, and identified as relating to the same event by comparison of the metadata 63 associated with them.
  • the details of the shape of the distribution of bookmarks over time will vary somewhat depending on the type of event being flagged. Empirical systems may be used to estimate, using the shape of the distribution 90 and the metadata 64 supplied by the users bookmarking the data, the optimum time to place the event marker 93.
  • the event marker can be defined as a predetermined percentile of the bookmark times - for example the first quartile (25 th percentile) 92, or the median (50 th percentile) 95, depending on the type of event being bookmarked.
  • the spread 94 of data may also be used to determine an appropriate PPER to apply.
  • the event marker is at the median point, which is chunk 12.
  • the EM and PPER determine the order in which he chunks are to be delivered - the point at which the sequence is terminated is determined by the receiving system.
  • the chunks to be selected for the clip are determined by an event marker 93 and associated ratio PPER, but the invention may also be used to select the timing of clips defined conventionally, using start and end times specified by reference to the distribution of bookmarks - for example from the first decile (10 th percentile) 91 (chunk 3) to the ninth decile (90 th percentile) 99 (chunk 15).
  • the refined or aggregated bookmark is added to a bookmark list available to the application stored on individual client devices 41. Users may be given the option of using their own markers instead of the aggregated values. Bookmarks saved in the XML file are automatically uploaded to a centralised data store.
  • the central data store can be used by viewers and TV production to identify and prioritise video clips for use in other applications such as a TV sports highlights programme.
  • the bookmark list available to an individual viewer can include bookmarks to which he has not himself contributed - for example he may have missed an incident because of interruptions in the data connection over which he was viewing live coverage.
  • bookmarks to which he has not himself contributed for example he may have missed an incident because of interruptions in the data connection over which he was viewing live coverage.
  • the bookmark list can be filtered using the metadata tags, thereby enabling easy navigation and replay of video clips.
  • Bookmarks can also be used as playlists, for example to enable a viewer to see all the goals within the match they have added to their bookmark list.
  • the bookmark (or Event Marker) "93" only defines a specific moment in time, around which a 'clip' can be defined.
  • chunks each being for example two seconds in length
  • a video clip can be defined by the number of chunks that occur before and after the Event Marker.
  • the chunks to be selected are determined with reference to two other properties. Firstly, a ratio before and after a single event time-code is determined (step 67) in accordance with metadata retrieved from the store 43 (step 66). This ratio is referred to herein as a Pre Post Event Ratio (PPER).
  • PPER determines the position within the clip of the time specified by the event marker - more specifically the ratio between the number of "chunks" to be provided preceding the EM and the number of "chunks" to be provided subsequent to the EM.
  • Figure 1 shows three clips 101 , 102, 103, each of thirteen “chunks” but with PPERs of respectively 1 :1 , 2:1 and 3:1. It will be seen that although in each case the clip has the same duration, the event marker (labelled as "1" in each case) occurs as - respectively, the 7 th , 9 th or 1 1 th chunk in the sequence, and thus the start and finish times of these clips differ.
  • the event marker labelled as "1” in each case
  • the value determined for the PPER ratio is used to generate a set of Narrative Importance Values (NIV) (step 68) for the individual chunks in a clip, which are maintained in a store 45.
  • NIV Narrative Importance Values
  • a manifest file 46 is created within the network video server 42 (step 70) by retrieving the event markers 43 associated with the clips requested, and determining the network addresses of the individual video chunks to be delivered and their associated narrative importance values (NIV) 45 (steps 701 , 702).
  • the manifest file 46 is delivered to a client 41 requesting a clip (step 72), allowing the client to request the video chunks in order of their narrative importance value (step 76). Delivery and compilation of video clips using the prioritised delivery schedule (figure 4)
  • the PPER can be used to specify in which order the video chunks are to be downloaded for a PPER of 1 :1 , 2:1 and 3:1 respectively.
  • the Event Marker would always be identified as chunk number 1.
  • the PPER would be used to identify the Narrative Importance Value (NIV) for each video chunk, which would then be used by the server to generate a video manifest file 46 which specifies the order in which individual video chunks would be requested by a client device video player application. So, for example, with a PPER of 1 :1 , chunks will be allocated NIVs in descending order at the same rate both before and after the event marker. For a PPER of 2:1 two chunks will be allocated before the EM for each chunk afterwards.
  • NIV Narrative Importance Value
  • the ratio specified by the PPER is preserved as nearly as possible. It will be seen from the examples that although in each case the clip has a duration of 13 chunks, (e.g 26 seconds) the event marker occurs at different points within it - respectively, the 7 th , 9 th or 11 th chunk in the sequence. Similarly, if the sequence is truncated before delivery is complete, the ratio specified by the PPER is preserved as nearly as possible given the fundamental granularity of the chunks (i.e that fractions of chunks are not possible).
  • Figure 4 illustrates the server and client apparatus which co-operate to perform the process, and the exchanges of data required.
  • Figure 4 depicts a client device 41 having an output to a television set 40 or other monitor device, and a connection over a communications network to a server 42.
  • the server has a number of data stores 43, 44, 45, 46 which store event markers and other metadata associated with the video data, and manifest files for specifying which parts of the video data are to be delivered to individual clients, and in what order.
  • the manifest files 46 may be created in response to specific requests from clients, or may be pre-prepared.
  • the client server 41 has a corresponding store for downloaded manifest files 46, and may also have a store of personalised priorities 47 for modifying the manifest file in order to prepare a request 48 for delivery of video content.
  • the server platform 42 has a store of video content 49 from which is retrieved the content 490 specified in the request 48 for delivery to the client device 41.
  • the user When requesting a videoclip, the user selects an identity (e.g by reference to its bookmark EM) and a desired duration (step 69). He may select a single clip or a series, defined either one-by-one or as a compilation defined by the user himself or by another user. In the case of a compilation the user may specify its overall duration, rather than the individual durations.
  • the length of the clip, or of each clip in the sequence, is defined by the receiving client device 41 which orchestrates the request of clips and the composition of a multi-clip video sequence for presentation.
  • the server uses the bookmark data associated with each event marker to determine a priority list.
  • This list may be tailored towards the user's preferences - for example in a football game the user may give priority to viewing goals scored for the team he supports rather than those scored for the opposition, and may prioritise goals over other incidents such as events surrounding a caution or dismissal of a player.
  • the client 41 requests a particular manifest file 46 from the server 42 (step 69), specifying one or more individual clips
  • the manifest file is compiled from the EM and NIV data (step 70 - Figure 6)
  • the server 42 delivers the manifest file 46 to the client 41 (step 72)
  • the Client 41 reads the manifest file 46 (step 73)
  • the client 41 interprets the manifest file 46, and applies the client's own Event and Personal Priorities 47 (step 74)
  • the client 41 creates a modified prioritised video chunk list 48, derived from the manifest file 46 as modified by the priorities 47 (step 75) specifying the video chunks in the order they are to be transmitted.
  • the client 41 transmits the chunk list 48 to the server 42 (step 76)
  • the server 42 retrieves the video chunks 49 and transmits them in the order specified in the request (step 77)
  • the client receives the video chunks 49 and reassembles them into chronological order for presentation to the user (step 78).
  • the client device 41 assembles a shorter sequence from those it has received. All the chunks are stored, either for later playback or for near-immediate display: however, because the chunks preceding each event marker are delivered in reverse order to the order in which they are to be shown, display of the full sequence cannot start until all the pre-event chunks of the first clip have been delivered.
  • Figure 2 illustrates how video chunks would be typically assembled by a client device to form a compilation of video sequences, in this case two video sequences 1-13 and 14-22.
  • the chunks are numbered in the order they are to be displayed.
  • the flag icons indicate the divisions between the individual video clips.
  • the chunks selected will be those which satisfy the required duration, ratio and EM.
  • the first sequence (1-13) has a ratio of 2:1 and a duration of 13
  • the second a duration of 9 chunks and a ratio of 1 :0 (i.e the EM is to be the last chunk of the sequence, however long it is).
  • the user device composes them into a set of video clips which together create a complete video 'highlights' show.
  • each chunk is allocated a value referred to herein as its NIV (Narrative Importance Value) and the order the chunks are delivered is determined in accordance with their individual NIVs.
  • the order in which the chunks are delivered is therefore, in general, different from that in which they are to be assembled.
  • Figures 3A, 3B and 3C illustrate how video chunks can be downloaded across multiple video clips in sequence.
  • the client device has requested a manifest file suitable for 'transient networks' where network connection cannot be guaranteed.
  • the manifest file specifies an ordering of video chunks, relating to several video clips.
  • each clip has the same duration (7 chunks) and PPER ratio (1 :1 ), but the principle can be extended to compilations of clips in which these values differ. This approach enables the key highlights to be prioritised.
  • the individual chunks are numbered in order of priority, and it is in that order that they are downloaded.
  • the server will first deliver the EM chunk from each clip (labelled “1"). When all the “1” chunks have been delivered, all the “2” chunks will be delivered, and so on.
  • Figure 3A shows a partially downloaded video sequence compiled from three video clips (87, 88, 89). If the download were interrupted after only twelve chunks had been delivered a video sequence comprising three short clips 87, 88, 89 could be compiled by the player 41 , and presented to the user. If the server 42 had instead delivered the chunks in the sequence in which they are to be played, an interruption after twelve chunks would result in the viewer only receiving, and being able to view, the entire first clip and part of the second, but nothing of the third clip.
  • the client platform would stop the download after delivery of the highest priority four chunks (those with NIVs of 1 ,2,3, or 4) from each of the three video clips 31 , 32, 33.
  • Figure 3C shows the fully downloaded video sequence, if all the chunks were downloaded.
  • the duration of the "catch-up" download may be determined to be dependent on the amount of the video that has already been shown, in order that the end of the 'catch-up sequence' coincides with the return to watching the live match. Any further event that is bookmarked during the actual download time can be added to the sequence "on the fly", the high-priority chunks from the additional clip displacing the lowest priority chunks from earlier clips, that would otherwise have been downloaded last, in order to keep the total time of the catch-up sequence the same, so that the end of the 'catch-up sequence' coincides with the return to watching the live match.
  • This invention would enable the dynamic delivery of a compilation of predetermined length without having to pre-define the number of clips in the compilation, and even adding further clips to the compilation as the download progresses without changing the overall duration of the compilation.
  • each clip's respective event marker all have the same priority
  • clips may be provided with a priority descriptor to be used by the server to define how video chunks may be prioritised within the manifest file.
  • priorities may be determined according to several criteria, such as using the volume of bookmarks associated with an event to understand the level of importance and thereby change the priority and provision of individual video chunks (referred to herein as "Social priority").
  • individual clients can interpret the manifest file and tailor their requests to the server to match the individual needs of the device and the preferences of the user. For example an event description (goal, pass, foul, etc.) can be used to prioritise delivery of the clip e.g. events such as goals would be higher priority than fouls. Ratings and the level of comments made about events may also be used to influence priority (referred to herein as "Event priority").
  • Event priority Using the personal preferences of the viewer such as which team they support, the delivery of video clips can be further prioritised according to those preferences, for example by omitting, or curtailing, clips relating to their opponents.
  • Figures 5A and 5B show the layout of a companion screen application to be used by the viewer.
  • Figure 5A shows the user interface to create temporal bookmarks. Having first called up the bookmark screen (which causes the time to be recorded) the user can then select an event type from a first menu 51 and other metadata (e.g team 52, or individual player 53) to be stored in the metadata store 44 associated with the event marker 43.
  • Figure 5B shows the user interface to navigate bookmarks in order to compile a video clip sequence. Individual event markers 50 are displayed in association with the metadata 51 , 52, 53 recorded with them, with the facility to select one or more such events for download, for example by scrolling through the events and operating a select function for those required.
  • Individual event markers 50 are displayed in association with the metadata 51 , 52, 53 recorded with them, with the facility to select one or more such events for download, for example by scrolling through the events and operating a select function for those required.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

L'invention concerne la fourniture de données vidéo. Des données d'entrée de marqueur temporel individuel générées par des utilisateurs différents d'une émission ou d'une autre sortie vidéo sont utilisées pour identifier des parties des données vidéo à utiliser pour générer une séquence de clips vidéo ou de « moments forts ». Les marqueurs temporels individuels pour chaque événement sont regroupés pour créer un fanion indicateur unique (93) pour chaque événement, défini par exemple comme la valeur médiane (95) (ou tout autre point) dans la distribution (90) des marqueurs temporels.
EP14703153.8A 2013-03-05 2014-01-31 Fourniture de données vidéo Ceased EP2965531A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP14703153.8A EP2965531A1 (fr) 2013-03-05 2014-01-31 Fourniture de données vidéo

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
EP13250026.5A EP2775731A1 (fr) 2013-03-05 2013-03-05 Distribution de données vidéo
EP14703153.8A EP2965531A1 (fr) 2013-03-05 2014-01-31 Fourniture de données vidéo
GB2014000003 2014-01-31

Publications (1)

Publication Number Publication Date
EP2965531A1 true EP2965531A1 (fr) 2016-01-13

Family

ID=54771259

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14703153.8A Ceased EP2965531A1 (fr) 2013-03-05 2014-01-31 Fourniture de données vidéo

Country Status (1)

Country Link
EP (1) EP2965531A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050154637A1 (en) * 2004-01-09 2005-07-14 Rahul Nair Generating and displaying level-of-interest values
US20130051757A1 (en) * 2008-08-15 2013-02-28 At&T Intellectual Property I, L.P. System and method for generating media bookmarks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050154637A1 (en) * 2004-01-09 2005-07-14 Rahul Nair Generating and displaying level-of-interest values
US20130051757A1 (en) * 2008-08-15 2013-02-28 At&T Intellectual Property I, L.P. System and method for generating media bookmarks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO2014135827A1 *

Similar Documents

Publication Publication Date Title
US9865308B2 (en) Provision of video data
EP2965532B1 (fr) Distribution de données vidéo
US11290791B2 (en) Generating a customized highlight sequence depicting multiple events
US20160134945A1 (en) Provision of video data
US10642465B2 (en) Method and system for media selection and sharing
JP6544779B2 (ja) エキサイトデータに基づくデジタルビデオコンテンツを配信するためのシステム及びプロセス
US20160105733A1 (en) Generating a customized highlight sequence depicting an event
AU2015330769A1 (en) Customized generation of highlight show with narrative component
US10149009B2 (en) Indexing and compiling recordings in dwindling memory
WO2010150226A2 (fr) Procédés et systèmes permettant d’indexer un contenu vidéo sur demande dans un système de câble
US20120179786A1 (en) Managing media content streamed to users via a network
US8527880B2 (en) Method and apparatus for virtual editing of multimedia presentations
CN115004713A (zh) 视频分发装置、视频分发方法以及视频分发程序
US9215575B2 (en) Encoding and distribution of game play through compact message encoding and graphical rendering
US9602879B2 (en) Indexing, advertising, and compiling sports recordings
EP2965531A1 (fr) Fourniture de données vidéo
KR102143766B1 (ko) 콘텐츠의 주요 장면 표시를 위한 장치 및 방법
KR102143765B1 (ko) 콘텐츠의 주요 장면 표시를 위한 장치 및 방법
Davies et al. MECHANISM FOR QUEUING LIVESTREAM CONTENT IN A MEDIA CONTENT DISPLAY QUEUE

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20150825

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170928

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: BRITISH TELECOMMUNICATIONS PUBLIC LIMITED COMPANY

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: BRITISH TELECOMMUNICATIONS PUBLIC LIMITED COMPANY

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20221102