1. A video receiver device comprising:
an input interface for receiving external data;
a receiver connected to the input interface for obtaining from said external data a stream of video data for a succession of video frames;
an output interface connected to the receiver for outputting said stream of video data;
a detector for detecting indicator data in the external data, the indicator data indicating at least one frame of the stream of video data for use in representing the video data;
a memory for storing a plurality of video frames;
a data capturer connected to the receiver and the memory and arranged to capture individual video frames from the stream of video data and store captured frames in the memory;
a controller connected to the detector, the data capturer and the memory and responsive to detection by the detector of indicator data to control the data capturer to capture the frames indicated by the detected indicator data and store the captured frames in the memory; and
an image provider connected to the memory, the output interface and the controller, the image provider being responsive to the controller to obtain one or more selected frames from the memory and provide the one or more selected frames to the output interface for use in representing the stream of video data.
2. A video receiver device according to claim 1 wherein:
the controller is configured to provide, in conjunction with the image provider, output data for display of an electronic program guide and is configured to insert, into the electronic program guide, frames indicated by the indicator data for respective programs listed in the electronic program guide.
3. A video receiver device according to claim 2 wherein:
the controller is configured to insert, into the electronic program guide, for respective programs, frames captured from streams of video data for trailers for the programs.
4. A video receiver device according to claim 1 wherein:
for a received stream of video data for a television program, the controller is configured to provide for output, in conjunction with the image provider, index data for the television program including said selected frames for the television program.
5. A video receiver device according to claim 1 wherein:
the memory is arranged to store said plurality of video frames in full resolution as received from the receiver.
6. A video receiver device according to claim 1 wherein:
the controller is configured to produce thumbnail video frames of reduced size andor resolution for storage as said video frames in said memory.
7. A video receiver device according to claim 1 wherein:
the input interface is arranged to receive external data containing the indicator data from a different source to external data containing said stream of video data.
8. A video receiver device according to claim 1 wherein:
the receiver is arranged to separate external data containing the indicator data from external data containing said stream of video data.
9. A video receiver device according to claim 1 further comprising:
a display for displaying at least said stream of video data.
10. A video receiver device according to claim 1 further comprising:
a recording apparatus for recording at least the stream of video data.
11. A video transmission apparatus comprising:
an input interface for providing, from a source, a stream of video data for a succession of video frames;
an output interface connected to said input interface and arranged to provide the stream of video data for transmission;
a user interface connected to said input interface and arranged to provide a display of video frames of said stream and to enable a user to select particular frames for use in representing the stream; and
an indicator creator connected to the input interface, the user interface and the output interface, wherein the indicator creator is arranged to create, in response to control from the user interface following selection of particular frames by a user, indicator data indicating at least one frame as selected by the user from the stream of video data and to provide the indicator data to the output interface.
12. A video transmission apparatus according to claim 11 wherein:
the output interface is arranged to embed the indicator data in the stream of video data.
13. A video transmission apparatus according to claim 11 wherein:
the output interface is arranged to provide a data stream containing the indicator data for transmission with the stream of video data.
14. A video transmission apparatus according to claim 11 wherein:
the output interface is arranged to provide output data containing the indicator data for transmission separately from the stream of video data.
15. A data-bearing signal representative of indication data provided to the output interface of the video transmission apparatus of claim 11.
16. A method of providing a receiver of a transmitted stream of video data for an ongoing succession of video frames with one or more images representing the stream of video data, the method comprising:
creating indicator data which identifies individual frames in the stream of video data for use as said one or more images; and
transmitting said indicator data to the receiver.
17. A method for identifying one or more video frames in an external stream of video data and for providing data corresponding to one or more frames of the video data stream to an output interface for use in representing a portion of the video data stream, the method comprising the steps of:
receiving the external data stream and deriving the video data stream therefrom,
detecting indicator data in the external data, the indicator data indicating at least one frame of the stream of video data for use in representing the video data,
storing a plurality of video frames;
capturing one or more individual frames in accordance with the detected indicator data, and
providing one or more captured frames to an output interface.
18. A data carrier having stored thereon data portions corresponding to at least one sequence of video frames, table of contents data identifying the data portions and data representing one or more video frames corresponding to at least some data portions, the data representing the one or more video frames being displayable as part of an index display of the contents of the data carrier and having been stored on the data carrier in accordance with the method of claim 17.
19. A video device comprising:
an input interface for receiving external data;
a receiver connected to the input interface for obtaining from said external data a stream of video data for a succession of video frames;
an output interface connected to the receiver for outputting said stream of video data;
a detector for detecting indicator data in the external data, the indicator data indicating at least one frame of the stream of video data for use in representing the video data; and
a controller connected to the detector and arranged to control the detector to provide the indicator data to the output interface for output with said stream of video data.
20. A video device according to claim 19 further comprising:
a recorder arranged to receive from the output interface the stream of video data and the indicator data and to record the stream of video data and the indicator data on a recording medium.
21. A video device comprising:
an input interface for receiving external data;
a receiver connected to the input interface for obtaining from said external data a stream of video data for a succession of video frames;
a detector for detecting indicator data in the external data, the indicator data indicating at least one frame of the stream of video data for use in representing the video data; and
a recorder arranged to receive from the receiver and the detector the stream of video data and indicator data and to record the stream of video data and indicator data on a recording medium.
22. A method for generating a representation of at least one video data item, having a plurality of frames, stored on a recording medium for display using a graphical user interface (GUI), the method comprising the steps of:
launching a GUI application,
deriving, from the recording medium, indexing data for each of the video data items,
deriving, from the recording medium, indicator data indicating at least one frame of video for a respective video data item,
identifying, at least in part under the control of the GUI application, and using the indicator data, at least one frame of video included in the respective video data item,
outputting the at least one frame of video to an interface accessible by the GUI application, and
displaying, in the GUI, a representation of at least one video data item stored on the recording medium, the representation including for the said at least one video data item, one or more frames of video representing the video data item obtained from the said interface and indexing data.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method of operating a hub in a first domain of a Content-Centric Network (CCN), the method comprising:
identifying a route from the hub to an anchor hub in the first domain, the anchor hub being configured to store routing information between a first border hub of the hubs in the first domain and a second border hub in a second domain;
detecting a neighboring hub based on a sync direction of the identified route; and
sharing the routing information with the neighboring hub, the sharing of the routing information comprising performing a sync operation with the neighboring hub,
wherein the hub is configured to generate a routing table for the first domain based on information of avoided domains, and wherein the avoided domains indicate domains that are excluded from a routing route and the avoided domains are defined based on a trust relationship.
2. The method of claim 1, wherein each of the hubs in the first domain comprises a first sync tree, a second sync tree, or a combination thereof, the first sync tree comprising first connection information on a connection between the first domain and the second domain, the second sync tree comprising second connection information on a connection between the anchor hub, the first border hub, and the hubs in the first domain.
3. The method of claim 2, wherein the identifying of the route is based on the first connection information and the second connection information.
4. The method of claim 2, wherein:
the second domain comprises one or more hubs, each of the hubs of the second domain comprising the first sync tree, the second sync tree, or the combination thereof; and
the hubs of the first domain and the hubs of the second domain are configured to generate a routing table of the first domain and the second domain, the routing table being configured to store the routing information being based on the first sync tree, the second sync tree, or the combination thereof.
5. The method of claim 1, further comprising:
updating the sync direction based on whether the routing information is exchangeable through the identified route.
6. The method of claim 1, further comprising:
connecting the first border hub and the second border hub through the sync operation; and
disconnecting the first border hub and the second border hub based on results of a traffic relationship, a trust relationship, or a combination thereof established between the first domain and the second domain.
7. The method of claim 6, further comprising:
deleting connection information in the first border hub, the second border hub, or a combination thereof on a connection between the first border hub and the second border hub in response to the first border hub and the second border hub being disconnected.
8. The method of claim 6, wherein the anchor hub in the first hub is configured to store history information of a connection between the first border hub and the second border hub.
9. The method of claim 8, further comprising:
reconnecting the first border hub and the second border hub based on the history information; and
sharing routing information obtained by the reconnecting of the first border hub and the second border hub.
10. A non-transitory computer readable recording medium storing a program to cause a computer to implement the method of claim 1.
11. A hub included in a first domain of a Content-Centric Network (CCN), the hub comprising:
a hardware processor configured to
identify a route from the hub to an anchor hub in the first domain, the anchor hub being configured to store routing information between a first border hub of the hubs in the first domain and a second border hub in a second domain,
detect a neighboring hub based on a sync direction of the identified route; and
perform a sync operation with the neighboring hub to share the routing information with the neighboring hub, wherein
the hub is configured to generate a routing table for the first domain based on information of avoided domains, and wherein the avoided domains indicate domains that are excluded from a routing route and the avoided domains are defined based on a trust relationship.
12. The hub of claim 11, wherein the anchor hub in the first domain comprises the first border hub in the first domain.
13. The hub of claim 11, further comprising:
a first sync tree comprising first connection information of a connection between the first domain and the second domain;
a second sync tree comprising second connection information or a connection between the hub, the anchor hub, and the first border hub in the first domain; or
a combination thereof.
14. The hub of claim 13, wherein the hardware processor is further configured to identify the route based on the first connection information and the second connection information.
15. The hub of claim 13, wherein the first sync tree comprises a list of domains excluded from the identified route.
16. The hub of claim 13, wherein the first border hub is configured to match the first sync tree and the second sync tree with the first sync tree and the second sync tree of the second border hub in response to the sync operation being performed.
17. The hub of claim 13, further configured to generate second routing information and update the sync direction to a next-hop hub in a route having the shortest distance to the anchor hub in response to the routing information being determined to be nonexchangeable.
18. The hub of claim 11, wherein the hardware processor is configured to update the sync direction based on whether the routing information is exchangeable through the identified route.
19. The hub of claim 11, wherein:
the first border hub and the second border hub are configured to be connected through the sync operation; and
wherein the first border hub and the second border hub are configured to be disconnected based on results of a traffic relationship, a trust relationship, or a combination thereof established between the first domain and the second domain.
20. The hub of claim 19, wherein the first border hub, the second border hub, or a combination thereof is configured to delete connection information on a connection between the first border hub and the second border hub in response to the first border hub and the second border hub being disconnected.
21. The hub of claim 19, wherein the anchor hub is configured to store history information associated with a connection between the first border hub and the second border hub.
22. The hub of claim 21, wherein the hardware processor is further configured to share routing information obtained by reconnecting the first border hub and the second border hub in response to the first border hub and the second border hub being reconnected based on the history information.
23. The hub of claim 22, wherein the anchor hub in the first domain is configured to connect with an anchor hub in the second domain in response to the reconnection between the first border hub and the second border hub failing.
24. The hub of claim 22, wherein the anchor hub in the first domain acquires a Session Initiation Protocol address from an anchor hub in a neighboring domain, names of the anchor hubs are generated to correlate the first domain to the first anchor hub and the second domain to the second anchor hub, and the first border hub and the second border hub is configured to perform a sync operation in response to the anchor hub in the first domain acquiring a Session Initiation Protocol address.
25. A Content-Centric Network (CCN), comprising:
an anchor hub in a first domain, the anchor hub being configured to:
identify a route to one or more first hubs in a first domain;
detect a neighboring hub based on a sync direction of the identified route; and
share routing information with a neighboring hub based on the sync direction of the identified route;
a border hub in the first domain connected to a hub in a second domain, the second domain being distinguished from the first domain; and
one or more second hubs obtained by excluding the anchor hub and the border hub from the first domain and the second domain, wherein
the first hubs in the first domain are configured to generate a routing table of the first domain based on information of avoided domains, and wherein the avoided domains indicate domains that are excluded from a routing route and the avoided domains are defined based on a trust relationship.
26. The CCN of claim 25, wherein the border hub is configured to delete connection information between the border hub in the first domain and the border hub of a domain connected to the first domain and reduce a size of the routing table In response to the first border hub being disconnected from the border hub of a domain connected to the first domain, and wherein
the border hub of the first domain is independent of the border hub of the domain connected to the first domain.
27. The CCN of claim 25, wherein the first border hub and the border hub of the domain connected to the first domain are configured to be reconnected based on whether the first domain and the domain connected to the first domain form a social network or a physical network, in response to the first border hub and the border hub of the domain connected to the first domain being disconnected.
28. The CCN of claim 25, wherein the routing table is used to generate a Forwarding Information Base (FIB), and a difference between the routing table and the FIB is determined based on whether to notify a next hub to be connected.