JP4396248B2 - Information processing apparatus and method, recording medium, and manufacturing method thereof - Google Patents

Description

  The present invention relates to an information processing apparatus and method, a recording medium, and a method for manufacturing the same, and in particular, can facilitate a series of user operations until content acquisition, and can enhance the response of the user terminal to the user operations. The present invention relates to an information processing apparatus and method, a recording medium, and a manufacturing method thereof.

  Recently, the Internet has become widespread. As a result, users can connect to the Internet using their own terminals as clients and acquire and use various contents distributed from the server via the Internet.

  There are a large number of contents distributed via the Internet, and it is expected that they will continue to increase in the future. In addition, the arrangement locations (distribution sources) are scattered in various places on the Internet.

  For this reason, the following functions are required as client functions. That is, the functions required of the client are functions of the entire process of searching for content, selecting, providing information, and guiding to use (operation) (client processing). Hereinafter, the generic name of such functions is referred to as a content navigation function.

  Conventionally, a client often has a content navigation function as shown in FIG. That is, FIG. 1 is a diagram for explaining a conventional form of the content navigation function.

  In FIG. 1, a client 1 and a server 2 are connected via the Internet (not shown).

  As shown in FIG. 1, information necessary for the server 2 to select a desired content from contents that can be distributed via the Internet and navigate (guide) a series of operations until it is acquired. (Hereinafter referred to as navigation information) is not held in the conventional client 1. That is, the browser 10 of the client 1 makes a navigation information acquisition request (information request) to the server 2 on the Internet whenever necessary (when there is an instruction operation from the user).

  The server 2 generates navigation information in the form of HTML (Hyper Text Markup Language) text or BML (Broadcast Markup Language) text in advance, and when receiving an information request from the client 1, the navigation information (HTML text or BML) Sentence) is transmitted to the client 1 via the Internet.

  Note that the various pieces of content information included in the navigation information are generated based on metadata held in the metadata database 3 on the Internet (or the metadata itself is used). That is, when the navigation information (HTML or BML text) is generated, the server 2 makes a metadata acquisition request (information request) to the metadata database 3 to acquire necessary metadata.

  The browser 10 of the client 1 acquires HTML text or BML text (navigation information) transmitted from the server 2 via the network, interprets it, converts it into a form such as an image, and presents it to the user.

  Thereafter, the user performs a series of instruction operations until content acquisition using the image or the like (navigation information) presented by the browser 10, that is, using the browser 10.

  Note that the other entity in the terminal in FIG. 1 refers to application software or the like for reproducing content. That is, the user performs a corresponding instruction operation using the browser 10 even when reproducing the acquired content.

  In this way, in the conventional content navigation, all navigation (processing) including interaction with the user is handled by the browser 10.

The details of such a conventional form of content navigation are disclosed in, for example, Patent Document 1. In other words, Patent Document 1 discloses a technique for a content distribution system in which, when a stream content request is received from a client, a server transmits control data for setting a playback function of the stream content to the client. Specifically, Patent Document 1 discloses a series of processing from when a client requests desired stream content to a server until playback. That is, in Patent Document 1, a client makes a request for a web page to a service server, selects desired content from the web page, acquires stream content from a URL (Uniform Resource Locator) of the selected content. A series of processes from automatically starting playback application software to playing back content is disclosed.
JP 2003-61066 A

  However, the conventional form of such a content navigation function has the following first and second problems.

  That is, the first problem is a problem that the response of the client 1 to the user's instruction operation is poor because the communication between the browser 10 and the server 2 is always performed. In particular, the first problem becomes remarkable in communication with the server 2 where access is concentrated.

  The second problem is that a user who is not familiar with the operation of the browser 10 or the like finds the desired content and the process (operation) until it is acquired is complicated and difficult to understand. .

  The present invention has been made in view of such a situation, and facilitates a series of user operations up to content acquisition and enhances the response of the user terminal to the user operations. .

An information processing apparatus according to the present invention is an information processing apparatus that acquires and uses content that is arranged externally, each of first metadata that specifies predetermined content, and a plurality of instances of predetermined content, and those The second metadata for specifying the position of the user is recorded for each content, and the first metadata is used for a series of user operations until the content to be acquired is selected from one or more contents. And the position of a predetermined instance among the plurality of instances of the content selected by the user according to the process of the guidance step is recognized from the second metadata, and the content is obtained by accessing the position. A mounting means for mounting a recording medium on which a program including the acquisition step is recorded; Using the first metadata and the second metadata to the destination unit is recorded in the loaded recording medium, each of the processing of the acquisition step and the induction step included in the program recorded on the recording medium Ru and an execution means for executing.
The second metadata includes information for identifying each of the plurality of instances of the predetermined content, information indicating the position of the instance existing on the Internet among the positions of the plurality of instances of the predetermined content, and the predetermined content Among the plurality of instances, information indicating the location of the broadcasted instance can be included.

Information necessary for acquiring the first metadata and the second metadata is further recorded on the recording medium, and the execution means records the first metadata and the second metadata according to the information . It can acquire from a medium and can perform each process of a guidance step and an acquisition step using those metadata.

  The recording medium further records information necessary for executing at least a part of the process of the guidance step or the acquisition step, and the execution means performs the process of the guidance step or the acquisition step according to the information. The corresponding processing can be executed.

In addition to the first metadata and the second metadata, the recording medium further records third metadata for specifying a purchase period, a price, and a license for each of the contents . It is possible to record a program including a guidance step that further uses the third metadata.
In addition to the first metadata, the second metadata, and the third metadata, the recording medium further includes a fourth metadata that specifies a plurality of segments obtained by dividing predetermined content in the time direction. In addition to data being recorded, there is recorded a program further including a process execution step for performing a predetermined process in units of segments on the content using the fourth metadata, and the execution means further includes: A predetermined process in the process execution step can be executed using the fourth metadata.

  The execution means further executes processing of other steps included in another program different from the program recorded on the recording medium in order to acquire and use the content, and the recording medium is included in the other program. Information necessary for executing at least a part of the processes of the other steps may be further recorded.

Data of other content different from the one or more content specified by the first metadata can be further recorded on the recording medium.

An information processing method of the present invention is an information processing method of an information processing apparatus that acquires and uses content arranged outside , and includes first metadata that identifies predetermined content, and a plurality of instances of the predetermined content The second metadata for identifying each of these and their positions is recorded for each content, and the user's series of operations until selecting the content to be acquired from the one or more contents is performed in accordance with the first metadata . Recognizing the position of a predetermined instance among the plurality of instances of the content selected by the user according to the process of the guidance step and the guidance step that uses the metadata from the second metadata, and accessing the position And a recording medium on which a program including an acquisition step for acquiring content is recorded When mounted on the location, the induction step of using the first metadata and the second metadata recorded in the recording medium mounted on the information processing apparatus, included in the program recorded on the recording medium And the respective processes of the acquisition step.

In the information processing apparatus and the information processing method of the present invention, the first metadata for specifying the predetermined content and the second metadata for specifying each of a plurality of instances of the predetermined content and their positions are provided for each content. And a guidance step for guiding the user's series of operations until selecting a content to be acquired from one or more contents using the first metadata; and A program including an acquisition step of recognizing a position of a predetermined instance among a plurality of instances of content selected according to processing from the second metadata, accessing the position , and acquiring the content is recorded. If the recording medium is mounted in the information processing apparatus, first recorded on the recording medium The use of the metadata and the second metadata, each of the processing of the acquisition step and the induction step included in the program recorded on the recording medium is performed.

The recording medium of the present invention is a recording medium that is attached to an information processing apparatus that acquires and uses content that is arranged outside, and includes a first metadata that specifies predetermined content, and a plurality of predetermined content with a second metadata identifying each and their positions instance is recorded for each content, a series of operations of a user from among one or more content until selecting content to now acquired, first A navigation step that guides using the metadata of the second metadata, and a position of a predetermined instance among a plurality of instances of the content selected by the user according to the processing of the navigation step is recognized from the second metadata, and the location is accessed. Thus, a program including an acquisition step for acquiring content is recorded.

In the recording medium of the present invention, first metadata for specifying predetermined content , and second metadata for specifying each of a plurality of instances of the predetermined content and their positions are recorded for each content . In addition, a guidance step for guiding the user's series of operations from the one or more contents until the content to be acquired is selected using the first metadata, and the content selected by the user according to the processing of the guidance step The process of recognizing the position of a predetermined instance of the plurality of instances from the second metadata, accessing the position , and acquiring the content is executed. Thereby, when the recording medium of the present invention is mounted on the information processing apparatus, the first metadata and the second metadata recorded on the recording medium are used, and the guidance step included in the program is performed. Each process with the acquisition step is executed.

Method for producing a recording medium of the present invention is a method of manufacturing a recording medium mounted on the information processing apparatus that acquires a content to be disposed outside use, first metadata identifying the predetermined content, and a predetermined A first recording step for recording in advance a second metadata specifying each of a plurality of instances of content and their positions on a recording medium for each content, and selecting a content to be acquired from one or more contents A guidance step for guiding a series of user operations up to the first metadata, and a position of a predetermined instance among a plurality of instances of content selected by the user according to the processing of the guidance step is set to a second recognized from metadata, accessing that location, pro including an acquisition step of acquiring content Including a second recording step of pre-recorded on the recording medium the ram.

In the recording medium manufacturing method of the present invention, first metadata for specifying predetermined content and second metadata for specifying each of a plurality of instances of the predetermined content and their positions are recorded for each content. A first recording step that is recorded in advance on a medium, and a program that is executed by a computer that controls the information processing apparatus, and includes a series of user operations until selecting content to be acquired from one or more contents. an induction step of inducing using the first metadata, and recognizing the position of a predetermined instance of the plurality of instances of the content selected by the user according to the process of induction steps from the second metadata, in that position access, pre and acquisition step of acquiring content including program recording medium It is recorded. Thereby, when the recording medium of the present invention is mounted on the information processing apparatus, the first metadata and the second metadata recorded on the recording medium are used, and the guidance step included in the program is performed. Each process with the acquisition step is executed.

  As described above, according to the present invention, the user can obtain desired content. In particular, a series of operations until the user acquires desired content can be facilitated, and the response of the processing of the user terminal corresponding to the user's operation can be enhanced.

  Next, embodiments of the present invention will be described with reference to the drawings.

  First, the principle of the present invention will be described with reference to FIG. 2 and FIG.

  FIG. 2 is a diagram for explaining an embodiment of a content navigation function that can solve the conventional problem (the first problem and the second problem of the above-described conventional content navigation function (see FIG. 1)).

  In the form of FIG. 2, in order to solve the conventional problem, the client 11-A is provided with a client application 21 and a client metadata database 22.

  The client application 21 is application software responsible for main user interface functions of the client 11-A in content distribution and system control of the entire client 11-A.

  The client application 21 periodically makes a metadata acquisition request (metadata acquisition request) for all accessible contents to the metadata database 3 (similar to FIG. 1) on a network (not shown), As a result, the metadata transmitted from the metadata database 3 is stored in the client metadata database 22.

  When an instruction operation such as a content acquisition instruction is made by the user, the client application 21 makes a required metadata acquisition request (information request) to the client metadata database 22, and as a result, the client metadata Using the metadata supplied from the database 22, navigation information is generated in the form of an image and presented to the user.

  Thereafter, the user uses the image presented by the client application 21 (navigation information), that is, uses the client application 21 to perform an instruction operation until content acquisition.

  As described above, in the content navigation function in the form shown in FIG. 2, the processing until the navigation information is presented to the user and the user selects the desired content (the corresponding instruction operation is performed) is performed by the client 11. -Completed by internal processing of A (communication processing via the network is not required) On the other hand, in the conventional form shown in FIG. 1, communication processing with the server 2 via the network is indispensable until the navigation information is presented to the user and the content is selected by the user. Therefore, in the following, the conventional form (the form shown in FIG. 1) of the content navigation function is referred to as network-dependent navigation, and the form shown in FIG. 2 is referred to as client-oriented navigation.

  As described above, in client-oriented navigation, information (metadata) necessary for navigation processing is stored in advance in the client metadata database 22 in the client 11-A, that is, a network such as the Internet is used. Since there is no need to newly acquire metadata by performing a communication process, it is possible to quickly access and display information. That is, it is possible to achieve an effect that can solve the conventional first problem.

  Further, in client-oriented navigation, the client application 21, not the browser 11 (FIG. 1), handles navigation (processing) including user interaction. Therefore, by applying software pursuing viewer operability as the client application 21, it is possible to realize an easy-to-understand content navigation function with a sense of unity regardless of the business operator. That is, it is possible to achieve an effect that can solve the conventional second problem.

  On the other hand, for those who manufacture or sell the client 11-A (natural person, corporation, organization, etc.), it is easy to build a differentiation strategy by installing the client application 21 on the client 11-A. It is also possible to produce an effect.

  However, the following third and fourth problems also exist in the client-based navigation capable of producing such effects.

  That is, the third problem is that when the number of contents increases, it becomes difficult to hold all of the metadata in the client metadata database 22.

  The fourth problem is that it is difficult to realize a method for dealing with the decentralization of the metadata database 3 and an operation method such as a method for updating the client metadata database 22 by periodically acquiring metadata.

  Therefore, the applicant of the present application has invented the following technique in order to solve the third problem and the fourth problem. That is, the technique invented by the applicant of the present application is a technique in which metadata is recorded on the removable recording medium 31 and the client 11-B uses the metadata as shown in FIG. In other words, it can be said that the applicant of the present application has invented a new form of the content navigation function as shown in FIG. 3 by applying this method to the client-oriented navigation of FIG.

  Hereinafter, the principle (method) of the present invention will be described in more detail with reference to FIG. In FIG. 3, portions corresponding to those in FIG. 2 are denoted by corresponding reference numerals.

  As shown in FIG. 3, a client application 21 and a client metadata database 22 are also provided in a client 11-B to which the present invention is applied, as in the case of the client 11-A in FIG.

  However, in the present invention, the metadata stored in the client metadata database 22 is not only acquired from the metadata database 3 by regular communication via the network, but can also be acquired from the removable recording medium 31. Has been.

  Note that the form of recording metadata on the removable recording medium 31 is not particularly limited. For example, a specific file can be determined so that the client 103 can easily determine that the metadata is recorded on the removable recording medium 31. Can be recorded by name. Further, when it is not generally desired to release the metadata, for example, the metadata may be recorded in a hidden fixed space such as a specific sector of the removable recording medium 31.

  As described above, by recording the metadata on the removable recording medium 31, the client 11-B can appropriately acquire the metadata from the removable recording medium 31 only when necessary. It is not necessary to hold all of the metadata on the data database 22 side. That is, it is possible to achieve an effect that can solve the third problem.

  In addition, it is easy to realize a simple operation method in which the user has the removable recording medium 31 and simply attaches the removable recording medium 31 to the client 11-B when necessary (when it is desired to acquire content). It becomes possible. That is, it is possible to achieve an effect that can solve the fourth problem.

  The form of the removable recording medium 31 for recording the metadata is not particularly limited. For example, a magnetic disk (including a floppy disk), an optical disk (CD-ROM (Compact Disk-Read Only Memory), DVD (Digital Versatile Disk)) ), Magneto-optical disks (including MD (Mini-Disk)), and semiconductor memories.

  Accordingly, the presentation form of navigation information or the like can be changed corresponding to the form of the removable recording medium 31. In other words, navigation information or the like can be presented in a presentation form similar to a general presentation form of other information (content or the like) recorded on the removable recording medium 31. As a result, the user simply acquires the content corresponding to the metadata recorded on the removable recording medium 31 by performing the same operation as the general operation when using the information recorded on the removable recording medium 31. The operation can be performed. That is, it is possible to achieve an effect that can better solve the above-described second conventional problem.

  Specifically, for example, in a DVD playback device or the like, an operation for switching contents to be viewed from a plurality of contents recorded on a DVD (for example, a main part of a movie and a digest version of another movie) In order to perform an operation of switching scenes (selecting chapters) in one content, a user interface using an image called a menu screen is provided.

  Therefore, if the client application 21 of the client 11-B has such a user interface providing function, navigation information and the like are obtained from the metadata recorded on the removable recording medium 31 formed of a DVD-ROM. It can be generated and displayed in the form of a menu screen.

  Thereby, the user uses a menu screen (navigation information or the like) provided by the DVD-ROM (removable recording medium 31), for example, a predetermined button (broadband distribution service button or the like) on the menu screen. ) Can be used to enjoy various media-linked services. Specifically, for example, a service for displaying a site on the Internet designated in advance by the service provider side (however, when the client application 21 or the like has a browsing function for HTML text or BML text), the client 11 It is possible to enjoy a reference service or the like of content that has already been downloaded to -B (for example, content that has been recommended and recorded by a certain type of service for a specific period).

  As described above, it is possible for the user who is accustomed to the operation using the menu screen of the DVD to obtain an effect that the convenience of the content acquisition operation using the menu screen becomes very high.

  As a specific application example of the present invention (FIG. 3) capable of producing such various effects, for example, the following examples can be given.

  That is, for example, the sales content (removable recording medium 31) is purchased by further recording metadata of other content different from the sales content on the removable recording medium 31 (package media) on which the sales content is recorded. This is an example of distributing metadata of other contents to the user.

  In the case of this example, there are innumerable ways of combining sales content and other content, and the method can be applied to various fields depending on the combination.

  For example, the present invention can be applied to a field in which other contents are used for the purpose of adding a premium (added value) to sales contents. Specifically, for example, assuming a song of a singer as sales content, a recorded video (data) of the singer's concert is stored on the Internet as other content, and the package of the sales content is stored. In the medium (removable recording medium 31), information necessary for obtaining a license for other content, information necessary for presenting other content (promotion), etc. are recorded as metadata. I can leave.

  Further, for example, the present invention can be applied to a field where sales content is used for the purpose of advertising other content. Specifically, for example, when a paid content (drama program, etc.) scheduled to be distributed in the future is assumed as the content to be advertised (other content), the paid content (other content) scheduled to be distributed Information necessary for acquiring licenses of other content in package media (removable recording medium 31) in which related content (for example, a movie in which the same actor appears) is recorded as sales content In addition, information necessary for presenting introduction (advertisement) of other contents can be recorded as metadata.

  In addition, when including metadata for such paid content in the removable recording medium 31, it is preferable that the metadata includes information related to the purchase period, price, and license of the corresponding paid content. It is. However, details of these metadata will be described later with reference to FIG. 10 and FIGS.

  Further, as another specific application example of the present invention (FIG. 3), for example, content metadata (and content acquisition) can be stored in a removable recording medium 31 (such as an empty removable recording medium 31) that does not include sales content. In this example, only the other information necessary for recording is recorded and the content is distributed.

  Specifically, for example, music CDs set in advance on the provider side (for example, five songs) are usually recorded on a music album sales CD. On the other hand, by applying the present invention, for example, it is easy to realize an example in which a user can freely select up to five desired music pieces from 10 preset music pieces and record them on a CD. It becomes possible. That is, the removable recording medium 31 in which only the metadata of each of the ten songs is recorded is sold to the user, and the user attaches the removable recording medium 31 to the client 11-B, so that the ten songs are recorded. It is possible to easily realize an example in which only five (desired) songs are downloaded and recorded on the removable recording medium 31.

  Furthermore, as another specific application example of the present invention (FIG. 3), for example, a removable recording medium 31 in which only the metadata of the content is recorded can be used free of charge or inexpensively for the purpose of widely distributing the content ( For example, it is distributed to users for less than the price of the content.

  By the way, in the above, it was assumed that the client application 21 was installed in the client 11-B. Therefore, when realizing the specific application example of the present invention (FIG. 3) as described above, the target user is only the person who owns the client 11-B in which the client application 21 is installed. This causes a problem that it is difficult to distribute content widely.

  Therefore, in order to solve such a problem, in the present invention, in addition to the metadata, the client application 21-A can also be recorded on the removable recording medium 31.

  In addition, as a code | symbol of the client application recorded on the removable recording medium 31, what is provided with 21-A not only 21 is the client application 21 installed in the client 11-B, and the removable recording medium. This is because the client application 21-A recorded in 31 does not necessarily correspond one-to-one.

  In other words, the client application 21-A recorded on the removable recording medium 31 has functions (for example, a content navigation function and a content acquisition function) necessary for acquiring content corresponding to metadata recorded together on the removable recording medium 31. Function) is sufficient. On the other hand, the client application 21 installed in the client 11-B often has various functions in addition to the content navigation function and the content acquisition function, as will be described later. Further, the client application 21-A recorded on the removable recording medium 31 can acquire content corresponding to the metadata recorded together with the removable recording medium 31, but can acquire other content. It is not always there.

  Therefore, hereinafter, the client application 21-A recorded in the removable recording medium 31 is appropriately referred to as a navigation program 21-A in order to clearly distinguish it from the client application 21 installed in the client 103.

  That is, the navigation program 21-A uses a metadata (stored together in the removable recording medium 31) to perform a series of user operations until selecting a content to be acquired from one or more contents. Software that has at least a content navigation function to be guided and is recorded on the removable recording medium 31. The navigation program 21-A may further have other functions. For example, as another function, the location of the content selected by the user using the content navigation function is recognized from the metadata (stored together in the removable recording medium 31), the location is accessed, and the Examples include a content acquisition function for acquiring content.

  As will be described later (as indicated by the white arrow in FIG. 8), in addition to the metadata and client application (navigation program) 21-A, a part of content corresponding to the metadata (described later). Control information such as startup file and Download.xml shown in FIG. 9 can be recorded on the removable recording medium 31. This eliminates the need for network communication for acquiring such information, and as a result, the amount of communication can be reduced. Further, as will be described later, it is possible to increase the added value of the removable recording medium 31 itself in which such information is recorded together with metadata.

  Further, commands and files for acquiring the metadata, installing or starting the client application (navigation program) 21-A, or executing a predetermined process are the metadata and the client application (navigation program) 21. It may be recorded on the removable recording medium 31 together with -A.

  Furthermore, information (commands and files) necessary for executing at least a part of the processing of the helper application (the content reproduction unit 204 to the download processing unit 207) is recorded on the removable recording medium 31. There is also.

  The outline (principle) of the present invention has been described above. Hereinafter, the present invention will be described in more detail.

  FIG. 4 shows a configuration example of a content distribution system to which the present invention is applied, that is, a content distribution system including an information processing apparatus (client or the like) to which the present invention is applied.

  As shown in FIG. 4, in the content distribution system of the present embodiment, a server 101 and a client 103 are connected to each other via a network 102.

  In FIG. 4, only one server 101 and one client 103 are shown, but it goes without saying that the number of each of the server 101 and the client 103 is not limited to 1 and should be plural. Can do. As will be described later, the server 101 may be composed of one information processing apparatus or a plurality of information processing apparatuses.

  Further, the form of the network 102 is not particularly limited, but here it is assumed to be the Internet for easy comparison with the above-described conventional example.

  The server 101 can be configured by a personal computer as shown in FIG. 5, for example. Alternatively, the server 101 can be composed of a plurality of personal computers as shown in FIG.

  In FIG. 5, a CPU (Central Processing Unit) 121 executes various processes according to a program recorded in a ROM (Read Only Memory) 122 or a program loaded from a storage unit 128 to a RAM (Random Access Memory) 123. To do. The RAM 123 also appropriately stores data necessary for the CPU 121 to execute various processes.

  The CPU 121, ROM 122, and RAM 123 are connected to each other via a bus 124. An input / output interface 125 is also connected to the bus 124.

  The input / output interface 125 includes an input unit 126 including a keyboard and a mouse, an output unit 127 including a display, a storage unit 128 including a hard disk, and a communication unit 129 including a modem and a terminal adapter. It is connected. The communication unit 129 performs communication processing with another information processing apparatus (here, the client 103 as shown in FIG. 4) via the network 102 (FIG. 4) including the Internet.

  A drive 130 is connected to the input / output interface 125 as necessary, and a removable recording medium 131 made up of a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is appropriately mounted, and a computer program read from them Are installed in the storage unit 128 as necessary.

  The removable recording medium 131 mounted on the drive 130 includes data and programs stored in the storage unit 128, such as the above-described metadata, navigation program (client application), part of content (control information), and the like. Various information is recorded as appropriate. Note that the information recorded on the removable recording medium 131 may include information supplied from the outside and received by the communication unit 129.

  In other words, the server 101 can record various information such as metadata, a navigation program (client application), and a part of content (control information) on the removable recording medium 131 attached to the drive 130. That is, a removable recording medium 131 in which metadata is recorded, a removable recording medium 131 in which a navigation program (client application) is further recorded, or a removable recording in which other information such as a part of content (control information) is further recorded. A medium 131 is manufactured by the server 101.

  The removable recording medium 131 on which at least metadata among such metadata, navigation program (client application), and other information is recorded is another information processing apparatus (not shown) different from the server 101. ).

  The example of the hardware configuration of the server 101 has been described above with reference to FIG.

  Next, the hardware configuration of the client 103 will be described.

  The client 103 can also be configured by a personal computer as shown in FIG. 5, but can also be configured by a hard disk video recorder as shown in FIG. 6, for example.

  In this case, as shown in FIG. 6, an antenna 171 and a display device 172 are further connected to the client 103.

  When the client 103 receives a broadcast radio wave broadcast from a broadcast station (not shown) via the antenna 171, the client 103 demodulates the broadcast radio wave and provides a video signal and an audio signal obtained as a result to the display device 172. At this time, if necessary, the client 103 stores the video signal and the audio signal as content in its own (auxiliary storage unit 160 of FIG. In addition, the video signal and the audio signal can be repeatedly supplied to the display device 172.

  Also, the client 103 receives the content distributed from the server 101 in FIG. 4 via the network 102, supplies the video signal and audio signal corresponding to the content to the display device 172, or supplies the content to itself. The video signal and the audio signal corresponding to the content can be repeatedly supplied to the display device 172 every time playback is instructed.

  That is, the content distribution method of the server 101 includes streaming distribution (hereinafter referred to as streaming distribution as appropriate) and download file distribution (hereinafter referred to as download distribution as appropriate). In the case of streaming distribution, the client 103 outputs content (video signal and audio signal corresponding to the content) received via the network 102 to the display device 172 in real time. On the other hand, in the case of download distribution, the content is temporarily recorded in the auxiliary storage unit 160, for example. Thereafter, every time playback is instructed, the content (file) recorded in the auxiliary storage unit 160 or the like is read, and the video signal and audio signal corresponding to the content are repeatedly supplied to the display device 172.

  The display device 172 is configured as, for example, a television receiver or a monitor. When a video signal and an audio signal are supplied from the client 103, the display device 172 displays a video corresponding to the video signal and supports the audio signal. The sound to be output is output.

  A hardware configuration example of the client 103 will be described in more detail.

  In the client 103 of FIG. 6, the tuner 151 is broadcast from a channel selected by the user (a channel corresponding to the input of the input unit 162) or a preset channel, that is, a broadcasting station corresponding to the channel. The received broadcast radio wave is received and demodulated through the antenna 171, and the resulting television broadcast signal (video signal and audio signal) is supplied to the encoder 152.

  At this time, the vertical blanking period of the terrestrial television broadcast signal may include EPG (Electronic Program Guide) information for a broadcast program to be broadcast in the future. Also, satellite television television broadcast signals may include EPG information for broadcast programs to be broadcast in the future. Therefore, the tuner 151 further supplies the demodulated video signal to the EPG acquisition unit 154.

  When EPG information is included in the supplied video signal, the EPG acquisition unit 154 extracts the EPG information and extracts a predetermined memory (for example, the main storage unit 161, the auxiliary storage unit 160, or the main storage unit 155). Etc.). This EPG information can also be used as the metadata described above.

  The encoder 152 encodes the television broadcast signal supplied from the tuner 151 by, for example, the MPEG (Moving Picture Experts Group) method, and stores the encoded signal in the auxiliary storage unit 160 via the bus 158 in a file format.

  That is, the auxiliary storage unit 160 is composed of, for example, a hard disk and stores data constituting each broadcast program, that is, an encoded television broadcast signal in a file format.

  Further, as described above, the auxiliary storage unit 160 also stores content (files) distributed from the server 101 (FIG. 4) and received by the communication unit 163.

  Further, the auxiliary storage unit 160 is installed with information recorded on the removable recording medium 131, that is, the above-described metadata and navigation program (in the example of FIG. 8 described later, client application (navigation program) 203-A). The

  Of the content (data) stored in the auxiliary storage unit 160, the content instructed to be reproduced is supplied to the decoder 153 via the bus 158. The decoder 153 decodes the content (data) by the MPEG method and supplies the decoded content (data) to the display device 172. The decoder 153 also decodes the content data (streaming content) supplied from the communication unit 163 by the MPEG method and supplies the decoded data to the display device 172.

  Furthermore, the decoder 153 also supplies various other information (for example, a list of contents shown in FIG. 14 described later) stored in the auxiliary storage unit 160 or the like to the display device 172 in the form of a video signal or an audio signal.

  Note that the encoder 152 and the decoder 153 do not supply the content or other information stored in the auxiliary storage unit 160 or the content or other information supplied from the communication unit 163 to the display device 172. The television broadcast signal output from the tuner 151 can be supplied to the display device 172 as it is.

  By the way, the bus 158 is connected to the ROM 159, the main storage unit 161, the input unit 162, and the communication unit 163 in addition to the encoder 152, the decoder 153, and the auxiliary storage unit 160 described above. The ROM 159 stores a program executed by the CPU 157 (a specific example thereof will be described later with reference to FIG. 8). On the other hand, data and parameters necessary for the CPU 157 to execute various processes are appropriately stored in the main storage unit 161 including a RAM or the like. The input unit 162 includes a key group (not shown) arranged on the surface of the client 103, a combination of the remote commander 181 and the light receiving unit (not shown) shown in FIG.

  As shown in FIG. 7, the remote commander 181 has number buttons 182 corresponding to the numbers 1 to 12. Further, a generator 183 that generates an infrared signal corresponding to a user's button operation is provided at the front end of the remote commander 181.

  On the lower side of the number buttons 182 in the figure, there are direction buttons 185U, 185D, 185L, and 185R that are operated when moving the cursor and the like up and down, and left and right, and a determination button 184 that is operated when performing a confirmation process at the center. Has been placed.

  Further, a detail button 186, a stop button 187, and a play button 188 are provided on the lower side of the remote commander 181 in the drawing. The detail button 186 is operated to instruct the presentation of more detailed information of the presented information. The stop button 187 is operated to stop the content reproduction. The playback button 188 is operated when instructing playback of content. A menu button 189 above the playback button 188 is operated when displaying a menu.

  In addition, although illustration is abbreviate | omitted, the remote commander 181 is suitably provided with various buttons to which various functions are assigned.

  Returning to FIG. 6, the communication unit 163 controls communication with the server 101 (FIG. 4) via the network 102. A specific example of information whose communication is controlled by the communication unit 163 will be described later with reference to FIG.

  Further, a drive 164 is connected to the bus 158, and a removable recording medium 131 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory is appropriately mounted, and a computer program read therefrom is supplemented as necessary. Installed in the storage unit 160. Specifically, for example, when a client application (navigation program) 203-A (see FIG. 8 to be described later) is recorded on the removable recording medium 131, it is appropriately read out as necessary, and the auxiliary storage unit 160 Installed on.

  Further, when metadata is recorded on the removable recording medium 131, it is appropriately read out as necessary and stored in a predetermined area of the auxiliary storage unit 160 (client metadata database 209 shown in FIG. 8 described later). Remembered.

  Furthermore, if other information is recorded on the removable recording medium 131 (control information such as startup file and download.xml in FIG. 9 to be described later, commands or files for the client application 203 to be described later), this is necessary. Accordingly, it is appropriately read out and stored in the main storage unit 155, the main storage unit 161, or the like.

  On the other hand, a tuner 151, an encoder 152, a decoder 153, an EPG acquisition unit 154, a main storage unit 155 including a RAM, and a CPU 157 are connected to the bus 156.

  Therefore, for example, when the client 103 is activated, the CPU 157 reads out various kinds of software recorded in the ROM 159 and executes predetermined processing in accordance with those software. At this time, the main storage unit 155 and the main storage unit 161 appropriately store data necessary for the processing at that time. Do with the corresponding block.

  FIG. 8 shows a functional configuration example of the content distribution system (FIG. 4) according to the present embodiment. That is, FIG. 8 shows an example of the functional configuration of each of the server 101 (FIG. 5) and the client 103 (FIG. 6) of the present embodiment.

  In FIG. 8, the thick arrow indicates the metadata transmission flow, the white arrow indicates the content transmission flow, and the thin arrow indicates the other information flow.

  First, paying attention to the client 103, as described above, the input unit 162 includes the remote commander 181 (FIG. 7) and the like, and inputs various commands from the user. As described above, the display device 172 displays an image constituting the content or outputs a corresponding sound. Further, the display device 172 presents various other information to the user. In the above description, the display device 172 is regarded as an external device connected to the client 103, but may be regarded as a component of the client 103. Therefore, in consideration of the fact that the display device 172 can be a constituent element of the client 103, the display device 172 is hereinafter referred to as a presentation unit 172.

  As described above, the client application 203 is application software having a main user interface function and a system control function of the client 103 so that the client 103 functions as a client terminal in content distribution.

  Specifically, as main functions of the client application 203, for example, the following functions (1) to (10) exist.

(1) Provision of entries to various functions of the client 103 (menu)
(2) Function for acquiring metadata of content (package) used by client 103 (3) Content navigation function based on metadata stored in client metadata database 209 (content (package) selection for purchase or acquisition) (See FIG. 13 to be described later), navigation function for selecting content for use (see FIG. 17 to be described later))
(4) A payment client function for performing payment related to content purchase with the payment server 222 (including a control function of the charging processing unit 206. See the processing in steps S4 and S5 in FIG. 11 described later).
(5) DRM (Digital Right Management) processing control function (including the control function of the DRM processing unit 205; see FIG. 15 described later)
(6) Download control function of content distributed from the content server 225 (including the control function of the download processing unit 207, see FIG. 18 described later)
(7) Activation of the content reproduction unit 204 (refer to processing in step S9 in FIG. 11 described later, which is processing after content selection)
(8) Instruction to move content to external media (removable recording medium 131 etc.) via drive 164 etc. (9) System control of entire client 103 (10) Timer control and energization control based on this

  Each of the functions indicated by (1) to (10) described above may be provided in advance in the client 103 (in general, functions other than (3) may be provided in advance. Many), sometimes obtained later. That is, with respect to the latter, as a result of the navigation program 203-A having at least the function (3) recorded in the removable recording medium 131 being installed in the drive 164 and installed in the removable recording medium 131, (3 ) Function will be added.

  Of course, the navigation program 203-A may have other functions in addition to the function (3), for example, the functions (4) to (7). If not provided, these functions are added by installing the navigation program 203-A.

  In addition, the client application 203 may have a browsing function. The browsing function includes, for example, an HTML (Hyper Text Markup Language) document presentation function (including CSS (Cascading Style Sheets)) and an execution function of a script included in HTML. Similarly, it includes a BML (Broadcast Markup Language) document (including CSS) presentation function and a script execution function included in BML. In addition, a function corresponding to XrML (eXtensible rights Markup Language) of Content Guard can also be included. However, the browsing function is not an essential function for the client application 203, and a browser having the browsing function may be separately provided in the client (see FIG. 38).

  As described above, the client application 203 is positioned at the top of the control of the client 103, and is software that sets a general user interface and a scenario from navigation to viewing for causing the client 103 to function as a content distribution terminal. is there.

  For such a client application 203, the content playback unit 204, DRM processing unit 205, billing processing unit 206, download processing unit 207, and the like are configured as helper application software for the client application 203, for example.

  However, the content reproduction unit 204, the DRM processing unit 205, the charging processing unit 206, the download processing unit 207, and the like may be configured in other forms such as hardware.

  The content reproduction unit 204 is configured by software typified by, for example, Microsoft Media Player (trademark), and controls and executes content reproduction and the like. The content playback unit 204 may also execute various controls incorporated in the client application 203 other than the markup language processing.

  A DRM (Digital Right Management) processing unit 205 communicates with the DRM server 224 constituting the server 101 to acquire a license relating to the content, and manages this in the client 103. Since the DRM processing unit 205 supplies a key Kc (not shown) for decrypting the encrypted data to the content reproduction unit 204, in order to securely manage the key Kc, for example, a content reproduction unit 204 is integrated.

  The billing processing unit 206 performs billing processing based on a method such as electronic money or prepaid.

  In the download distribution, the download processing unit 207 downloads content distributed in a file format from the content server 225 and stores the content in the content storage unit 208. That is, the content storage unit 208 is configured with, for example, a hard disk (one area) of the auxiliary storage unit 160 (FIG. 6), and stores content provided from the content server 225 of the server 101.

  The client metadata database 209 holds metadata communicated from the metadata database 223 of the server 101 via the network 102, and holds metadata read from the removable recording medium 131 mounted on the drive 164. To do.

  As described above, the removable recording medium 131 contains information (commands) necessary to execute at least a part of the processes of these helper applications (content reproduction unit 204 to download processing unit 207, etc.). Or file) may be recorded.

  Next, paying attention to the server 101, the server 101 includes a shop server 221, a settlement server 222, a metadata database 223, a DRM server 224, and a content server 225 in the example of FIG.

  Each unit of the server 101 exchanges information with each unit of the client 103 as shown in FIG.

  The shop server 221 has a server function as a window for the service provider user (the owner of the client 103). That is, as this server function, for example, a payment processing function (including a communication function with the payment server 222) accompanying content purchase, a license issuance procedure processing function (including a communication function with the DRM server 224) after payment processing, and a license Includes utility provision functions such as reissue and content redownload.

  In general, the server function often includes a function for providing the client 103 with navigation scenarios such as search, promotion, and description necessary for content selection as HTML text or BML document. . However, this function is not essential in this embodiment. This is because the client application 203 on the client 103 side has a function corresponding to this function, that is, a content navigation function that uses metadata stored in itself (client metadata database 209).

  The settlement server 222 communicates with the charging processing unit 206 of the client 103 and performs settlement processing. The settlement server 222 performs a settlement process based on the settlement process request from the shop server 221 and outputs the settlement result to the shop server 221.

  The metadata database 223 reads out stored metadata based on a periodic metadata acquisition request from the client application 203, supplies the metadata to the client metadata database 209 of the client 103 via the network 102, and stores it. Let

  Further, the metadata database 223 stores the stored metadata in the removable recording medium 131 based on an instruction from the server 101 administrator or the like. That is, the server 101 manufactures a removable recording medium 131 in which metadata is recorded in advance. When the removable recording medium 131 is loaded into the drive 164 of the client 103, the metadata stored in the removable recording medium 131 is read out and stored in the client metadata database 209.

  In the removable recording medium 131, as shown in FIG. 8, a part of content supplied from the client application (navigation program) 203-A and the content server 225 (startup file and Download.xml in FIG. 9 described later). In addition, the above-described various information (not shown in FIG. 8) is recorded as necessary.

  Further, the metadata database 223 supplies the metadata obtained by the search to the shop server 221 based on the metadata search request from the shop server 221.

  Based on the license issuance permission request from the shop server 221, the DRM server 224 communicates with the DRM processing unit 205 of the client 103 and executes DRM processing. This DRM processing includes authentication processing for determining whether or not a user is a licensed proper user, assignment of a key Kc necessary for decrypting encrypted data, acquisition processing, and other copyright management. Includes necessary processing. When the correct DRM process has been executed, the DRM server 224 supplies the key Kc necessary for encrypting the content to the content server 225. Further, the DRM server 224 supplies the corresponding key Kc to the DRM processing unit 205 of the client 103 when correct DRM processing can be executed.

  The content server 225 encrypts the content data using the key Kc supplied from the DRM server 224, and distributes the content data to the content reproduction unit 204 or distributes it as a download file to the content storage unit 208 for storage. .

  Here, as shown in FIG. 9 described later, content control information such as startup file and Download.xml is also considered to be part of the content (included in the content), and the content server 225 Such content control information (content) is transmitted to the client application 203 or stored in the removable recording medium 131 as described above.

  In the example of FIG. 8, the server 101 is configured by a plurality of servers (a plurality of information processing apparatuses). However, it is of course possible to configure the server 101 by a single server (a single information processing apparatus). is there.

  FIG. 9 shows the relationship between various types of information related to settlement, DRM processing, and playback. As shown in the figure, the device ID and the user ID (User ID) have a one-to-one correspondence. The device ID is an ID assigned to each client 103, and the user ID is an ID assigned to a user who uses the client 103. These IDs identify the client 103 and the user individually.

  A user assigned with a predetermined user ID makes a contract with the administrator of the server 101 to purchase a package as a product. Specifically, the user purchases a desired content from the content (program etc.) provided from the server 101 as a package. This package has a one-to-one correspondence with package metadata.

  Each package is associated with one or more contents. One content includes a content main body, Download.xml as a management information file for download, and a startup file. For example, when the content is a program, the content main body is a main body of content data representing the content of the program.

  Download.xml as a management information file is prepared when the content is a download content, and a directory, a file name, and the like are described therein. When all the files described in that directory have been received, the download is complete.

  The startup file includes information related to a distribution type indicating whether the content is data for download distribution or data for streaming distribution. That is, the startup file is control information that is executed first in the content, and starts (transitions) the Contents main body or the like based on the content.

  By the way, as described above (as indicated by the white arrow in FIG. 8), a part of content such as Download.xml and startup file (control information such as Contents itself) is added together with corresponding content metadata. It can be recorded on the removable recording medium 131 (FIG. 8).

  As a result, the client application 203 (FIG. 8) does not need to perform communication with the server 101 for acquiring such information (content control information and the like), as described later. As a result, communication with the server 101 is eliminated. The amount can be reduced.

  Further, by using a combination of metadata, a download control file, and the like, it is possible to newly create added value of the removable recording medium 131 itself.

  For example, by embedding file information (Download.xml, etc.) necessary for receiving a predetermined service in a specific area of the removable recording medium 131, a Web access operation such as a personal computer or a terminal function (keyboard) Input) etc. can be simplified (that is, the user can perform operations easier than the operation of the personal computer), and the process according to the control file (Download.xml, etc.) is executed. As a result, a set of necessary data files (Contents etc.) can be downloaded.

  By the way, content IDs (Contents ID) correspond one-to-one. The content is identified by this content ID. The content metadata further corresponds to content metadata (Contents Metadata). As shown in FIG. 10, the content metadata includes information such as a content ID (Contents_id), a title name (title name), a genre, and a program description.

  One content ID is associated with n license IDs (n is an integer of 1 or more). Similarly, n pieces of license metadata are associated with one content metadata.

  The license ID identifies a license associated with one to one. Each license includes a license ID, a usage rule, and a content key ring. This content key ring (corresponding to the above-described key Kc) is a key ring including an arbitrary number of keys (keys) necessary for decrypting the content targeted by the license, and is one-to-one with the content ID. It corresponds to.

  The license metadata has a one-to-one correspondence with the license metadata. As shown in FIG. 10, the license metadata includes a license ID (License_ID), a content ID (Contents_id), a content URL (ContentsURL (Uniform Resource Locator)), a license URL (LicenseURL), a distribution type, a content title name ( Contents title name), usage rule text (Usage1Rule text), etc. are included.

  The license metadata and the content metadata are associated with each other in an n-to-one manner according to the content ID included therein.

  The content URL of the license metadata represents an access destination when obtaining the content. The license URL represents an access destination for obtaining a license. The distribution type indicates whether the content targeted by the license is distributed by streaming or distributed as a download file.

  A package is associated with a license ID and m-to-n (m is an integer of 1 or more as in n). Similarly, package metadata is associated with license metadata in an m-to-n manner.

  As shown in FIG. 10, the package metadata includes a package ID (Package ID), a shop site URL (Shop Site URL), a package usage period, a package (Package) type, package information, and a license. It consists of an ID (License id) list.

  The package ID is information for identifying a package. The shop site URL represents an access destination of the shop site for obtaining the package. The package use period represents a period during which the package can be used.

  The package type represents whether the package is a pack or a subscription. Alternatively, the package type represents whether it is multicast or not. Pack represents a type of package that includes a predetermined number of predetermined programs. Subscription represents, for example, a type in which a program of a predetermined channel can be viewed over a predetermined number of days. Multicast indicates that the package is a type that is provided to an unspecified number of users for a fee or free of charge.

  The package information includes information on the name and fee of the package. The license ID list describes license IDs of licenses included in the package.

  The package metadata corresponds to the license metadata corresponding to the license ID described therein.

  As described above, the metadata includes at least three types of metadata such as package metadata, license metadata, and content metadata, and these three types of metadata are included in the metadata database of FIG. 223 and transferred to the client metadata database 209 of the client 103 as necessary (including both via the network 102 and the removable recording medium 131).

  Details of the metadata will be described later with reference to FIG. 18 and subsequent drawings.

  Next, processing of the client 103 (processing when content on the server 101 is acquired) will be described with reference to the flowchart of FIG.

  First, in step S <b> 1, the client 103 collects metadata necessary for content acquisition and stores it in the client metadata database 209.

  As described above, there are two types of metadata collection methods: a collection method based on regular communication via the network 102 and a collection method via the removable recording medium 131.

  A detailed example of the processing in step S1 corresponding to the latter of the two types of collection methods is shown in the flowchart of FIG. Therefore, a detailed example of the process of step S1 will be described below with reference to the flowchart of FIG.

  Hereinafter, such processing in step S1 is referred to as “metadata prior acquisition processing”.

  In step S21 in FIG. 12, the CPU 157 of the client 103 in FIG. 6 determines whether or not the removable recording medium 131 is loaded in the drive 164.

  If it is determined in step S21 that the removable recording medium 131 is not yet loaded, the process returns to step S21, and it is determined again whether or not the removable recording medium 131 is loaded. That is, the CPU 157 constantly monitors the mounting state of the drive 164.

  For example, when the user attaches a predetermined removable recording medium 131 to the drive 164, the CPU 157 determines in step S21 that the removable recording medium 131 has been attached, and in step S22, metadata is recorded on the removable recording medium 131. It is determined whether or not it has been done.

  When metadata is not recorded on the removable recording medium 131 (when it is determined in step S22 that metadata is not recorded), the “metadata pre-acquisition process” ends. However, when other information is recorded on the removable recording medium 131, processing corresponding to the other information may be executed. For example, if the removable recording medium 131 contains content for sale (movies, etc.), the content playback process may be executed.

  On the other hand, when metadata is recorded on the removable recording medium 131 (when it is determined that metadata is recorded in step S22), the CPU 157 removes the metadata from the removable recording medium 131 in step S23. Are stored in the client metadata database 209 (such as the auxiliary storage unit 160) of FIG.

  Note that the determination method of the determination process in step S22 is not particularly limited. For example, as described above, whether or not data of a specific file name (file name dedicated to metadata) is recorded, or specific The determination process of step S22 can also be performed based on whether or not data is recorded in an area (area dedicated for metadata).

  However, here, for example, it is assumed that the determination process of step S22 is performed based on whether or not a file for acquiring metadata is recorded in a specific area of the removable recording medium 131. That is, when a file for acquiring metadata is recorded in a specific area of the movable recording medium 131, the CPU 157 determines in step S22 that the metadata is recorded, and in step S23, the file is recorded. Is read out first, metadata is read out based on the contents (command, etc.) of the file, and stored in the client metadata database 209.

  In step S24, the CPU 157 determines whether or not the navigation program 203-A (FIG. 8) corresponding to the metadata has already been installed. That is, the CPU 157 determines whether or not the client application 203 includes a content navigation function corresponding to the metadata.

  If it is determined in step S24 that the navigation program 203-A corresponding to the metadata has already been installed (a function corresponding to the client application 203 is included), the CPU 157 determines in step S28 that the client application 203 Start up. This completes the “metadata pre-acquisition process”.

  Note that file information and commands for activating the navigation program 203-A may be recorded on the removable recording medium 131. In such a case, the CPU 157 activates the client application 203 according to the file information and command.

  On the other hand, if it is determined in step S24 that the navigation program 203-A corresponding to the metadata has not been installed yet (the function corresponding to the client application 203 is not included), the CPU 157 proceeds to step S25. The navigation program 203-A determines whether or not the navigation program 203-A is recorded on the removable recording medium 131.

  If it is determined in step S25 that the navigation program 203-A is not recorded on the removable recording medium 131, the CPU 157 executes a predetermined error process and ends the “metadata pre-acquisition process”. The form of error processing is not particularly limited. For example, acquisition of content corresponding to metadata recorded in the recording medium 131 (metadata recorded in the client metadata database 209 in the process of step S23). May be displayed on the display device (presentation unit) 172.

  On the other hand, if it is determined in step S25 that the navigation program 203-A is recorded on the removable recording medium 131, the CPU 157 installs the navigation program 203-A in the auxiliary storage unit 160 or the like in step S27. To do. That is, the CPU 157 adds the function of the navigation program 203-A (content navigation function that uses metadata recorded in the removable recording medium 131) to the function of the client application 203.

  Note that file information and commands for installing the navigation program 203-A may be recorded on the removable recording medium 131. In such a case, the CPU 157 installs the navigation program 203-A in the auxiliary storage unit 160 or the like according to the file information and commands.

  In step S28, the CPU 157 activates the client application 203 to which the function is added in the process of step S27. This completes the “metadata pre-acquisition process”.

  As described above, file information and commands for starting the navigation program 203-A may be recorded on the removable recording medium 131. In such a case, the CPU 157 activates the client application 203 according to the file information and command.

  Returning to FIG. 11, when the client application 203 is activated in this way, in step S2, the client 103 uses the client application 203 and the like to record the metadata (FIG. 11) recorded on the removable recording medium 131. The process of navigating the user operation until selecting the content desired for purchase from one or more contents corresponding to the metadata recorded in the client metadata database 209 in the process of step S23 of 12 is executed. That is, the client 103 executes processing corresponding to the content navigation function.

  Hereinafter, such processing in step S2 is referred to as “purchased content navigation processing”. A detailed example of this “purchased content navigation processing” is shown in the arrow chart of FIG. A detailed example of “purchased content navigation processing” will be described with reference to the arrow chart of FIG.

  In FIG. 13, the helper application includes a content reproduction unit 204, a DRM processing unit 205, a charging processing unit 206, and a download processing unit 207 (FIG. 8). The user interface includes an input unit 162, a presentation unit 172, and FIG. The same applies to other arrow charts (FIGS. 15, 16, and 17) described later.

  In step S41, the client application 203, for example, issues a metadata acquisition request, thereby reading the metadata already stored in the client metadata database 209 (stored in the process of step S23 in FIG. 12). Command.

  Note that file information and commands for acquiring metadata may be recorded on the removable recording medium 131. In such a case, the CPU 157 issues a metadata acquisition request to the client metadata database 209 according to the file information and command.

  In step S <b> 51, when the client metadata database 209 acquires a metadata acquisition request from the client application 203, the client metadata database 209 reads out a metadata group stored in advance and transmits it to the client application 203.

  Upon receiving the metadata group in step S42, the client application 203 reads the title name of the content (program) described therein, and in step S43, for example, a content list as shown in FIG. (Data) is generated and supplied to the presenting unit 172 as a user interface. In step S61, the presentation unit 172 displays the content list (data) as an image. That is, the list of contents is presented as shown in FIG. 14, for example.

  The user views the display of this list and appropriately operates the direction buttons 185U to 185R and the determination button 184 of the remote commander 183 to select content (program) having a predetermined title name and display it in the lower left in FIG. Click the “Purchase button” (the cursor is placed on the “Purchase button” and the enter button 184 is pressed).

  In step S 62, the input unit 162 supplies a selection signal (information specifying the selected program) corresponding to the user operation (purchased content selection operation) to the client application 203.

  In step S63, when the client application 203 receives the selection signal from the input unit 162, the client application 203 determines the content selected by the user as content to be purchased (hereinafter referred to as purchase content).

  Thus, the “purchased content navigation process” is completed.

  Returning to FIG. 11, when the “purchased content navigation processing” in step S <b> 2 is completed in this way, the client application 203 controls the charging processing unit 206 in step S <b> 3 to make payment for the purchased content on the server 101. To ask.

  That is, for example, the client application 203 recognizes the user ID and package ID from the metadata, performs login input with the user ID to the shop server 221, notifies the package ID, and purchases including the designation of the payment method. Make a request.

  In step S4, the client application 203 determines whether payment has been completed. If it is determined in step S4 that payment has not been completed, the process returns to step S4, and it is determined again whether payment has been completed. That is, the client application 203 waits for the process until the payment is completed.

  At this time, the following processing is executed on the server 101 side. That is, the shop server 221 connects to the settlement server 222 corresponding to the designated settlement means and performs a settlement process. When the settlement process is normally completed, the shop server 221 is purchased corresponding to the user ID of the purchaser (in this case, the user who uses the client 103) in the linked customer database (not shown). Registered package ID.

  Subsequently, the shop server 221 acquires a device ID list corresponding to the user ID from the customer database, and further acquires a license ID list corresponding to the package ID from the metadata database 223. A list of all combinations of license ID (s) is sent to the DRM server 224, which holds it.

  When the series of payment processing is completed, the shop server 221 notifies the client application 203 of that.

  Then, the client application 203 presents the completion of the payment process to the viewer through the presenting unit 172 (user interface), and updates the status of the package metadata to be purchased as purchased.

  When the above processing is completed, the client application 203 determines in step S4 that payment has been completed, and executes processing for acquiring a license for the purchased content in step S5.

  Hereinafter, the processing in step S5 is referred to as “license acquisition processing”. A detailed example of the “license acquisition process” is shown in the arrow chart of FIG. A detailed example of the “license acquisition process” will be described with reference to the arrow chart of FIG.

  In step S81, the client application 203 requests the server 101 to obtain a startup file corresponding to the purchased content. This startup file acquisition request includes a content ID for identifying purchased content. At this time, the client application 203 recognizes the content ID, the access destination of the server 101 (for example, a predetermined URL on the content server 225), and the like from the metadata stored in the client metadata database 209.

  In step S <b> 91, the server 101 (content server 225) reads a startup file of content (purchased content) corresponding to the specified content ID, and transmits it to the client application 203.

  The client application 203 receives this startup file in step S82.

  Depending on the purchased content, the startup file may not be included in the constituent elements. In such a case, steps S81 and S82 of the client application 203 and processing in step S83 described later (the server 101 associated with these processings). Step S91 on the side) is omitted.

  Further, as will be described later, one content, that is, each of the Contents main body, the startup file, and Download.xml shown in FIG. 9 described above is not necessarily in the same place (in this case, the content server 225). There is no need to be preserved. That is, as described above, for the purpose of reducing the amount of communication, in addition to metadata, it is also possible to record a startup file or Download.xml of content corresponding to the metadata on the removable recording medium 131. In such a case, the startup file acquisition request in the process of step S81 is made not to the server 101 but to the removable recording medium 131. That is, in step S82, the client application 203 acquires a startup file read from the removable recording medium 131.

  Next, in step S83, the client application 203 starts executing the process described in the startup file.

  The content of the process in step S83 differs depending on the description content of the startup file. However, here, for simplification of explanation, it is assumed that acquisition (confirmation) of the license is instructed in the startup file, and the license acquisition process is started in step S83. Specifically, for example, here, “a reference to a file describing information necessary for DRM processing (hereinafter referred to as a DRM information reference file)” is described in the startup file, and the client application 203 In step S83, the DRM information reference file is acquired from the server 101 in accordance with the description of the startup file. Here, this DRM information reference file is also handled as a part of the content.

  In this case, in step S84, the client application 203 requests the DRM processing unit 205 to acquire (confirm) a license. That is, the client application 203 issues a license acquisition (confirmation) instruction to the DRM processing unit 205 using the license ID (list) obtained by the previous settlement process and the DRM server URL as arguments.

  Upon receiving the license acquisition request, the DRM processing unit 205 accesses the DRM server 224 and executes DRM processing through communication with the DRM server 224 in step S101. That is, when viewed from the server 101 (DRM server 224) side, the DRM process for the client 103 is executed in step S92.

  Specifically, the DRM processing unit 205 attempts to acquire a license by sending a license ID to the DRM server 224 in a prescribed session. Since the DRM server 224 recognizes the terminal device (client 103) as the device ID at the beginning of this session, whether or not the license ID is permitted for the device ID when the license ID is sent. It is determined whether or not it is a valid license acquisition request. If there is no problem in the check, the DRM server 224 transmits the license to the DRM processing unit 205.

  Upon receiving the license, the DRM processing unit 205 securely stores the license, and notifies the client application 203 of the completion of the DRM processing (transmits a DRM processing completion notification) in step S102.

  That is, the DRM processing unit 205 transmits a license acquisition success / failure result from the DRM server 224 to the client application 203 as a DRM process completion notification. Note that the DRM processing completion notification indicating that the license acquisition has been successful may include a key Kc necessary for decrypting the corresponding content (in this case, purchased content).

  In step S85, when the client application 203 receives from the DRM processing unit 205 a DRM processing completion notification indicating that the license acquisition has been successful, the client application 203 has completed preparation for purchase content distribution processing in the presenting unit 172 as a user interface. Provides a message (data) indicating That is, the presentation unit 172 presents the message in the form of an image or the like in step S111. The form of presenting this message is not particularly limited. For example, when the distribution form of purchase content is download distribution, the color of the download button at the lower right of the image shown in FIG. You can take a presentation form.

  This completes the “license acquisition process”.

  When the client application 203 receives a DRM processing completion notification indicating that the license acquisition has failed from the DRM processing unit 205 in step S85, the client application 203 may return the process to step S84 and issue the license acquisition request again. Then, a predetermined error message may be presented to the user via the presentation unit 172.

  Further, as described above, the removable recording medium 131 in which metadata of the content is recorded can be distributed to users free of charge or at a low cost (less than the price of the content) for the purpose of widely distributing the content. In such a case, a license may not be set for the content. In such a case, the processing after step S84 (DRM processing or the like) can be omitted.

  Returning to FIG. 11, when the “license acquisition process” in step S5 is completed in this way, the client application 203 determines in step S6 whether the purchased content is a content for download.

  For example, if the purchased content is specified to be streaming distribution in the startup file acquired previously (step S82 in FIG. 15), the client application 203 determines that the purchased content is download content in step S6. It is determined that it is not (content for streaming delivery), and the process proceeds to step S8 without executing “download process” in step S7 described later.

  On the other hand, if it is specified in the startup file acquired earlier that the purchased content is download distribution, the client application 203 determines in step S6 that the content is for download, and step S7. The download processing unit 207 is controlled to download the content data (Contents main body) of the purchased content and store it in the content storage unit 208.

  Hereinafter, such processing in step S7 is referred to as “download processing”. A detailed example of this “download process” is shown in the arrow chart of FIG. A detailed example of the “download process” will be described with reference to the arrow chart of FIG.

  In step S <b> 151, the input unit 162 as a user interface supplies the client application 203 with a signal instructing the download of the purchase content determined in advance.

  In addition, the form of the signal which instruct | indicates download is not specifically limited, For example, the following signals are possible. That is, for example, in the state where the image of FIG. 14 described above is displayed, the user uses the direction buttons 185U to 185R of the remote commander 183 to place a cursor or the like on the “download button”, and presses the enter button 184. A signal input to the client application 203 when a pressing operation is performed (when an operation of clicking a “download button” is performed) can be used as a download instruction signal.

  Upon receiving such a download instruction, the client application 203 requests the server 101 (content server 225) to acquire Download.xml (FIG. 9) corresponding to the purchased content in step S161. This Download.xml acquisition request includes a content ID for identifying purchase content. This content ID is recognized from the metadata.

  In step S181, the server 101 (content server 225) reads Download.xml of the content (purchased content) corresponding to the specified content ID, and transmits it to the client application 203.

  In step S162, the client application 203 receives this Download.xml.

  As described above, in addition to metadata, the removable recording medium 131 can also record a startup file and Download.xml of content corresponding to the metadata. In such a case, the Download.xml acquisition request in the process of step S161 is made not to the server 101 but to the removable recording medium 131. That is, in step S162, the client application 203 acquires Download.xml read from the removable recording medium 131.

  Next, in step S163, the client application 203 supplies this Download.xml to the download control unit 207 to instruct download. That is, the client application 203 entrusts the download process to the download processing unit 207.

  The download processing unit 207 analyzes the Download.xml and checks the free space of the content storage unit 208 as download preparation processing to confirm that the license has been acquired. Further, the download processing unit 207 generates directory information indicating the storage location of the content to be downloaded (purchased content) and stores it in the client metadata database 209 as part of the metadata.

  In step S201, the server 101 (location described in Download.xml of the content server 225 or the like) is requested from the server 101 to acquire a file constituting the content described in Download.xml, for example, the Contents main body.

  In step S <b> 182, the server 101 reads out the requested contents body and transmits it to the client 103.

  In step S <b> 211, the content storage unit 208 of the client 103 stores the contents main body transmitted from the server 101 via the network 102 based on the control of the download processing unit 207. That is, the download processing unit 207 controls content data storage processing in the content storage unit 208 in step S202.

  Specifically, the download processing unit 207 causes the content storage unit 208 to store the previously acquired control file such as Download.xml and the file such as the Contents main body described in Download.xml as one content. In other words, the download processing unit 207 generates a specific directory in the content storage unit 208 and holds the directory structure in the original content under the specific directory, and each component of these contents (Content main body etc.) Write each of these.

  When all the data is stored in the content storage unit 208, the download processing unit 207 notifies the client application 203 of the completion of processing (transmits a processing completion notification) in step S203.

  In step S164, when the client application 203 receives the processing completion notification from the download processing unit 207, the client application 203 provides a message (data) indicating that the download of the purchased content is completed to the presenting unit 172 as a user interface. That is, the presentation unit 172 presents the message in the form of an image or the like in step S152. Thereby, the “downloading process” ends.

  While the download processing unit 207 is executing the processing, the client application 203 displays the download progress status on the display unit 172 as necessary (for example, when there is a user instruction operation). Can be presented to the user.

  Returning to FIG. 11, if the “download process” in step S7 is completed in this way, or if it is determined in step S6 that the content is not for download, the client application 203 temporarily performs the process. stand by. Alternatively, the client application 203 is launched.

  Thereafter, when the user operates the input unit 162 to restart or restart the processing of the client application 203 for the purpose of using (trial listening) the purchased content, in step S8, the client 103 Using the application 203 or the like, a process of navigating the user's operation until the content desired to be used (trial listening) is selected from the purchased content is executed.

  Hereinafter, such processing in step S8 is referred to as “use content navigation processing”. A detailed example of the “used content navigation process” is shown in the arrow chart of FIG. A detailed example of the “use content navigation process” will be described with reference to the arrow chart of FIG.

  When the user appropriately operates the remote commander 183 for the purpose of instructing the use of content, the input unit 162 supplies a signal corresponding to the operation to the client application 203 as a content usage instruction in step S221.

  Upon receiving this content usage instruction, the client application 203, for example, by issuing a metadata acquisition request in step S241, has already been stored in the client metadata database 209 (stored in step S23 of FIG. 12). Of the metadata) corresponding to the purchased content is commanded.

  In step S251, when the client metadata database 209 acquires the metadata acquisition request from the client application 203, the client metadata database 209 reads out a metadata group corresponding to the purchased content from among the metadata groups stored in advance. Transmit to the application 203.

  When the client application 203 receives the metadata group in step S242, the client application 203 reads the title name and the like of the content (program) described therein, and in step S243, although not shown, a list of purchased content ( Data) is generated and supplied to the presentation unit 172 as a user interface. In step S222, the presentation unit 172 displays a list (data) of purchased content as an image.

  The user views the display of this list, and appropriately operates the direction buttons 185U to 185R of the remote commander 183 (FIG. 7) to select the content (program) having the title name desired to be auditioned. The playback button 188 is pressed.

  Then, in step S223, the input unit 162 supplies a selection signal (information specifying the selected program) corresponding to this user operation (used content selection operation) to the client application 203.

  In step S244, when the client application 203 receives the selection signal from the input unit 162, the client application 203 determines the content selected by the user as content to be used (played back) by the user (hereinafter referred to as “used content”). .

  Thereby, the “use content navigation process” is completed.

  Returning to FIG. 11, when the “use content navigation process” in step S8 is completed in this way, the client application 203 activates the content playback unit 204 by plug-in and presents (plays back) the use content. Instruct.

  Then, the content reproduction unit 204 is activated, and in step S9, the content main body of the used content is acquired from the server 101 or the content storage unit 208, and is presented (reproduced) by the presentation unit 172.

  Specifically, first, the client application 203 instructs the DRM processing unit 205 to confirm the license corresponding to the used content.

  The DRM processing unit 205 executes DRM processing by confirming whether a license corresponding to the used content exists.

  When such DRM processing of the DRM processing unit 205 is correctly completed, the client application 203 instructs the content reproduction unit 204 to reproduce the used content.

  The content reproduction unit 204 tries to acquire a key (the above-described key Kc) for decrypting the used content to the DRM processing unit 205. The DRM processing unit 205 checks the usage conditions at that time, and if there is no problem, the DRM processing unit 205 securely transfers the corresponding key (key kc) to the content reproduction unit 204 and sets it to the decryptor in the content reproduction unit 204.

  When the distribution form of the usage content is streaming distribution, the content reproduction unit 204 sequentially decodes and decodes the content main body of the usage content streamed from the content server 225 of the server 101 using the key kc, It supplies to the presentation part 172.

  On the other hand, when the usage content distribution form is download distribution, the contents main body of the usage content is already stored in the content storage unit 208 in the “download process (FIG. 16)” in step S7 described above. The content playback unit 204 obtains the Contents main body of the used content from the content storage unit 208, sequentially decodes it using the key kc, decodes it, and supplies it to the presentation unit 172.

  In this way, the content reproduction unit 204 presents the used content by the presenting unit 172 in step S9.

  The processing of the client 103 according to this embodiment has been described above.

  As described above, in the processing of the client 103 according to the present embodiment, only the internal processing on the client 103 side (the browser or the like is used) with the help of the metadata transferred from the removable recording medium 131 to the client metadata database 209. It is possible to display a search screen (such as the content list described above) without performing communication processing with the outside to be used.

  Furthermore, in subsequent communication processing, the location of the content is recognized from the metadata, and the content existing at the location is transmitted using a communication protocol such as RTP.HTTP. It becomes.

  Furthermore, the client 103 according to the present embodiment uses the metadata recorded in the removable recording medium 131 to solve the third and fourth problems of the client-oriented navigation described above. Can do.

  As will be repeated, the third problem is that when the number of contents increases, it becomes difficult to hold all of the metadata in the client metadata database 209.

  The fourth problem is that it is difficult to realize an operation method such as a method for dealing with the decentralization of the metadata database 223 of the server 101 and a method for updating the client metadata database 209 by periodically acquiring metadata. It is.

  Next, a detailed example of metadata that can be used by the client 103, that is, metadata that can be recorded on the removable recording medium 161 will be described with reference to FIGS.

  As described with reference to FIG. 9 and FIG. 10 described above, the metadata includes package metadata (Package Meta data), license metadata (Licence Meta data), and content metadata (Contents Meta data). Although it can be divided into three types, such metadata can also be divided as shown in FIG. That is, FIG. 18 is a diagram for explaining a method of dividing metadata different from that in FIG.

  As shown in FIG. 18, PackageID, Shop site URL, Shop function URL, sales start / end date / time, Package type, package fee, package name, promotion information, genre information, number of selectable licenses in the package metadata. The information such as the license id list can be said to be information on the flyer of the content product or the advertising purpose. Therefore, such content product flyers and information for advertising purposes are hereinafter referred to as content product metadata. That is, some information in the metadata is classified into content product metadata.

  In addition, information such as distribution start and end date / time and content URL in the package metadata can be said to be significant information for content search processing, for example, search processing for content selection navigation processing. Therefore, information significant for content search processing, such as the title of the content, its outline, its genre, its location information, and its time information, is hereinafter referred to as content search attribute metadata. That is, some information in the metadata is classified into content search attribute metadata.

  The content search attribute metadata also includes the content URL, distribution correspondence, distribution start end date and time, and content title name of the license metadata. Further, the entire content metadata is included in the content search attribute metadata.

  Of the license metadata, information such as license ID, content ID, license URL, license expiration date, usage condition information, and resource information is information for the purpose of managing the purchased license (content viewing right). I can say that. Therefore, hereinafter, the license management purpose information is referred to as license management metadata. That is, some information in the metadata is classified into license management metadata.

  As described above, the metadata can be divided into three types such as content product metadata, license management metadata, and content search attribute metadata (however, in the package metadata, the metadata deletion date and time, the metadata Data update frequency, incidental terminal generation information, and incidental terminal generation information in license metadata are excluded).

  The symbols between the content product metadata, the license management metadata, and the content search attribute metadata are drawn according to the rules shown in FIG. For example, the symbol drawn between the content product metadata and the license management metadata shown in FIG. 18 is the top symbol in FIG. 19, and zero or more symbols are obtained from one content product metadata. Indicates that license management metadata is associated. These symbols shown in FIG. 19 are also used in FIGS. 20, 24, and 30 described later.

  By the way, for the content navigation function, as described above, the content search attribute metadata among the metadata thus classified is particularly important.

  Therefore, details of the content search attribute metadata will be further described below.

  As shown in FIG. 18, the content search attribute metadata is further classified into three types: content description metadata, instance description metadata, and segment description metadata.

  Content description metadata refers to general information about content that does not depend on the release or broadcasting form of the content. For example, the content description metadata includes information such as the title of the content, the text description of the content, and the genre. Generally, a content creator generates content description metadata before releasing content.

  Instance description metadata refers to information that describes a specific instance of content. For example, the instance description metadata includes information on the position (broadcast schedule and address) of the content instance and parameters (video format and the like) depending on the distribution medium. Instance description metadata is provided by a release or broadcast service provider or the like when content is released or broadcast.

  The segment description metadata refers to information for searching and operating a stream of content as segments separated by time. This segment description metadata is used to realize non-linear viewing such as extracting a highlight scene.

  Hereinafter, the details of the content description metadata, the instance description metadata, and the segment description metadata will be described individually in that order.

  First, content description metadata will be described.

  FIG. 20 shows a configuration example of content description metadata.

  As shown in FIG. 20, the content description metadata is composed of ProgramGroup, Program, and ProgramReview.

  The program (program) refers to information about a program (program) that is a unit of content corresponding to a program. That is, Program is information necessary when searching for a program from a title, an outline, or the like. Specifically, for example, Program (program) includes information as shown in FIG.

  In FIG. 21, CRID (Content Reference Identifier) of this program (program) is described in ProgramId (program identifier). OtherIdentifier (content identifier other than CRID) describes an identifier that can be used in addition to CRID in order to identify this Program. AVAttributes (audio visual attributes) describes media attributes (for example, encoding method and parameters).

  In MemberOf (reference to a program group), a CRID list of ProgramGroup (program group) including this Program (program) is described. The ProgramGroup will be described later. By this MemberOf (reference to the program group), it is possible to define a type indicating the program (program) derived for what reason (for example, language difference). In order to specify the episode number of the program in the series, a unique index value can be given within each ProgramGroup (program group) as MemberOf (reference to the program group).

  In BasicContentsDescription (basic content description), various basic contents as shown in FIG. 21 are described.

  That is, the title of this Program is described in Title. A plurality of titles can be described. MediaTitle (media title) describes information indicating an image that can be used as a “title”. ShortTitle describes a short format version of the title to be used as a reference when displaying.

  In Synopsis, an explanation of the contents of this Program is described.

  In the Language, the language of the sound that constitutes the Program is described. CaptionLanguage describes the language of caption information in this Program. Sign Language (sign language) describes the sign language specified in this Program.

  In the CreditsList (credit list), a list of credits such as actors appearing in the Program and directors of the Program is described.

  In Promotional Information (promotion information), contents used for sales promotion are described.

  In Keywords, a list of keywords indicating the characteristics of the program is described. A keyword refers to a single word or a complete phrase composed of a plurality of words.

  In Genre, the genre to which this Program belongs is described. Note that there are genres having a hierarchical structure as shown in FIG. That is, as the first layer (the highest layer), for example, NON-FICTUIN (non-fiction), SPORTS (sports), MUSIC AND DANCE (music / dance), LEISURE / HOBBY (leisure / hobbies), FICTION (fiction) , And AMUSEMENT (amusement) etc. can be described.

  Furthermore, NEWS (news) is described as a lower layer (second layer) of NON-FICTUIN (non-fiction), Daily News (daily news) and so on are further lower layer (third layer) of the NEWS (news). It is possible to describe special editions (special news programs). Similarly, the description of Athletics (athletics) etc. as the lower layer (second layer) of SPORTS (sports), and the description of Field (field system) etc. as the lower layer (third layer) of the athletics (athletics) , Each is possible. Further, as a lower layer (second layer) of MUSIC AND DANCE (music / dance), description such as Classical music is possible.

  Returning to FIG. 21, the Parental Guidance (viewing restriction designation) describes the viewing restriction designation of this Program. The AwardsList contains a list of awards and nominations for this Program. In RelatedMaterial (related material), reference information to other information related to this Program is described. ProductionInformation (production information) describes the date and time when this Program (program) was created and information about the country. ReleaseInformation (release information) describes the date and time when this Program was released and information about the country.

  Returning to FIG. 20, ProgramGroup (program group) refers to information about ProgramGroup (program group) in which a plurality of programs (programs) are collected. That is, ProgramGroup (program group) is information necessary when searching for a program in series program units. Specifically, for example, ProgramGroup (program group) includes information as shown in FIG.

  In GroupId (group identifier), CRID for this ProgramGroup (program group) is described.

  In GroupType (group type), the group type of this ProgramGroup (program group) is described. Specifically, for example, various types such as a series and a continuous program are described.

  Ordered (order type designation) is a flag indicating whether or not members belonging to this ProgramGroup (program group) are ordered.

  MemberOf (reference to the program group) describes a CRID list of ProgramGroup (program group) including (belonging to) this ProgramGroup (program group). That is, an index value unique to each ProgramGoup (program group) is assigned.

  BasicContentDescription refers to a basic content description, and specifically includes a description similar to the BasicContentDescription (basic content description) of the above-described Program (see FIG. 21).

  Returning to FIG. 20, Program Review (program review) refers to information about a review related to Program (program). That is, Program Review (program review) is information necessary when searching for a program based on a critic's evaluation result, rating value, or the like.

  Program Review includes Program (see program) and Review. In Program (refer to program), the CRID of the corresponding Program is described. In the Review (review), the review for the corresponding Program (program), that is, the Program (program) having the CRID designated by the Program (program reference) is described. The details of the contents of Review are omitted.

  Next, the instance description metadata will be described.

  FIG. 24 shows a configuration example of the instance description metadata.

  As shown in FIG. 24, the instance description metadata is composed of ProgramLocation (program location), OnDemandLocation (on demand location), ScheduleEvent (schedule event), and Service (service).

  ProgramLocation (program location) refers to an individual instance of Program. That is, ProgramLocation (program location) is general instance information that does not depend on the difference in media to which the Program (program) is distributed. Specifically, for example, ProgramLocation (program location) includes information as shown in FIG.

  That is, CRID of the corresponding Program (program) is described in Program (program reference).

  InstanceDescription (instance description) describes a corresponding Program (program), that is, an instance of a Program (CR) having a CRID specified by Program (program reference). Specifically, for example, in InstanceDescription (instance description), Title (title), Synopsis (outline), and AVAttributes (audio) of BasicContentsDescription (basic content description) (see FIG. 21) of Program (program) are included. Visual attributes) are described.

  Returning to FIG. 24, OnDemandLocation is information used when describing the location (URL address, time, and time) when the Program is archived on the Internet. Specifically, for example, OnDemandLocation (on-demand location) includes the information shown in FIG. 26 in addition to the attributes included in ProgramLocation (program location).

  That is, the URL is described when the corresponding Program is archived on the Internet.

  PublishedDuration (reproduction time) describes the reproduction time of the corresponding Program, that is, the Program located at the above-mentioned URL.

  In Start / EndOfAvailability (available date / time: start / end), the corresponding Program (program), that is, the date and time when the Program (program) located at the above-described URL can be used, that is, the start time and the end time, Described.

  First / LastAvailability (release information) is a flag indicating that the corresponding program (program), that is, the program (program) located at the above-described URL is the first or last time.

  Returning to FIG. 24, ScheduleEvent refers to information used to describe the position (channel, time, and time) when the corresponding Program is broadcasted. Specifically, for example, ScheduleEvent (schedule event) includes the information shown in FIG. 27 in addition to the attributes included in the corresponding ProgramLocation (program location).

  BroadcastURL (broadcast URL) describes the URL when the corresponding Program is broadcast. Specifically, for example, a URL or the like for specifying a program defined by DVB (DVB Digital Video Broadcasting) is described.

  ServiceId (service reference) describes an identifier of a Service (service) including this ScheduleEvent (schedule event).

  In the EventDescription (event description), content information of various events is described. Specifically, for example, PublishedTime (start time), PublishedDuration (duration), Live (live broadcast designation), Repeat (rebroadcast designation), First / LastShowing (first / last designation), and Free (free designation) ) Is described.

  PublishedTime (start time) describes the start time at which the corresponding Program is published on ECG (Electronic Contents Gides). PublishedDuration describes the duration for which the corresponding Program has been published on the ECG. Note that the exact start time and duration during actual operation are provided by a location resolution mechanism using a locator.

  Live (live broadcast designation) is a flag indicating whether or not the corresponding program (program) is a live broadcast. Repeat (rebroadcast designation) is a flag indicating whether or not the corresponding program is a rebroadcast. First / LastShowing (first / last designation) is a flag indicating that the corresponding Program is the first (first) or last (last) broadcast. Free (free designation) is a flag indicating whether or not the corresponding Program is free.

  Returning to FIG. 24, “Service” refers to information described about a broadcast channel that broadcasts a corresponding Program. That is, in Service (service), the contents of the entire stream including broadcast programs corresponding to a plurality of ScheduleEvents (schedule events) provided from the same broadcast service provider are described. Specifically, for example, Service (service) includes information shown in FIG.

  In other words, the service identifier (service identifier) describes the identifier of the service. In ParentService (parent service reference), information indicating a reference to the parent service (service) is described. For example, ParentService (parent service reference) can describe a specified reference valid period.

  Name is the name of the service, Owner is the trademark owner of the service, Logo is the network logo of the service, and ServiceGenre is the name of the service. Each genre is described.

  Here, with reference to FIG. 29, the Service will be described in more detail.

  That is, FIG. 29 shows a general EPG (Electronic Program Gide) displayed on the screen, and the above-described Program (Program), ProgramGroup (Program Group), ScheduleEvent (Schedule Event), and Service It shows which frame each (service) corresponds to.

  As shown in FIG. 29, each program (for example, baseball broadcast, news, quiz, drama, variety, movie, etc.) on the EPG is a channel (for example, a series of programs grouped in a ScheduleEvent). , Channels X, Y, Z, etc.) correspond to Service. Among the information of each program, the broadcast time and the like are described in ScheduleEvent (schedule event), and the content of the program itself is described in Program (program). Information of a package (for example, a baseball broadcast package) including a plurality of programs (programs) and a schedule event (schedule event) associated with the programs is described in a program group (program group).

  Next, segment description metadata will be described.

  The segment description metadata is information for realizing functions such as collecting a highlight scene of a program and viewing only a summary, or creating a bookmark of a topic headline.

  FIG. 30 shows a configuration example of the segment description metadata.

  As shown in FIG. 30, the segment description metadata is composed of a Segment (segment) and a SegmentGroup (segment group).

  By the way, as described above, one Program (program) can be made to correspond to a plurality of ProgramLocations (program locations) due to differences in physical and temporal positions from which it can be obtained. The process of selecting an instance of the program) is executed by a position resolution process based on the CRID.

  Here, assuming that the time axis at the time of stream playback of different instances corresponding to a program (program) identified by a predetermined CRID is the same, which instance of program (program) is selected in the position resolution process. The same segment description applies.

  Therefore, as shown in FIG. 30, a plurality of segments derived from different programs can be grouped as one segment group. For example, it is used when composing an original program in which only favorite actors appear.

  Specifically, the Segment refers to information about each segment obtained by dividing the corresponding Program by time. Specifically, for example, the segment (segment) includes information shown in FIG.

  In Segmented (segment identifier), the identifier of this segment (segment) is described, and in ProgramRef (program reference), the CRID of the Program (program) corresponding to this segment (segment) is described.

  The SegmentLocator (segment locator) describes the position (start time and length) of this Segment in the corresponding Program. KeyFrameLocator (key frame locator) describes the position of the key frame of this Segment.

  Various contents of this Segment (segment) are described in BasicSegmentDescription (basic segment description). Specifically, for example, Title (title), Keywords (keyword), Synopsis (outline), and RelatedMaterial (related material) are described.

  Title is the title of this segment, Keyword is a list of keywords for this segment, and Synopsis is a description of the contents of this segment However, in RelatedMaterial (related material), reference information to other related information is described.

  Returning to FIG. 30, SegmentGroup refers to information about a group of segments. When grouping, for example, group types such as highlights and bookmarks are defined. Specifically, for example, a segment group (segment group) includes information shown in FIG.

  That is, the identifier of this SegmentGroup (segment group) is described in GroupId (group identifier).

  GroupType (group type) describes the type of this SegmentGroup (segment group). As types that can be described in this GroupType (group type), "highlights" indicating highlights selected from one or more programs (programs) and "bookmarks" indicating a series of access points for programs (programs) Etc. exist.

  Ordered (order type designation) is a flag indicating whether the members in the group are ordered.

  In the duration (duration), the total time of the lengths of the segments included in this group is described. This length corresponds to the total length of Segments that are direct members of the SegmentGroup.

  In Segment / SegmentGroupRefs (refer to segment / segment group), reference information to Segment / SegmentGroup as a member is described.

  In ProgramRef (program reference), reference information to a program (program) to which this segment group (segment group) belongs is described. When segment (segment) and segment group (segment group) as members are collected from different programs, the CRID of the program group (program group) made up of these programs is referred to.

  The KeyFrameLocator (key frame locator) describes the position of the key frame of a SegmentGroup (segment group) closed in one Program (program).

  The BasicSegmentDescription (basic segment description) is a description related to the contents of the SegmentGroup (segment group), and is described in the same way as the BasicSegmentDescription (basic segment description) (see FIG. 31) of the above-described Segment (segment).

  FIG. 33 to FIG. 36 show a state in which a plurality of segments (segments) in a program (program) are collected from a predetermined viewpoint by a segment group (segment group).

  That is, FIG. 33 shows a configuration example of the first program.

  As shown in FIG. 33, the first program is composed of segments 301A to 301G.

  In the figure, a Segment having a plurality of hatched areas, that is, a Segment 301A, 301D, and 301G is a SegmentGroup whose “GroupType” is “highlights”. It belongs to.

  In the same figure, a Segment having a region in which a plurality of horizontal lines are drawn, that is, Segment 301B and 301D belongs to a SegmentGroup having a GroupType of “bookmarks”. It is shown that.

  FIG. 34 shows a configuration example of the second program.

  As shown in FIG. 34, the second Program is composed of Segments 302A to 302H.

  In the figure, a Segment having a region in which a plurality of horizontal lines are drawn, that is, a Segment 302A, 302C, and 302F is a SegmentGroup whose “GroupType” is “bookmarks”. It belongs to.

  FIG. 35 shows a segment group (segment group) whose GroupType is “highlights” from the first program (FIG. 33) and the second program (FIG. 34). ) Shows a configuration example when the segments are grouped. As described above, by using the segment description metadata, it is possible to define a SegmentGroup (segment group) in which only highlight scenes are collected.

  FIG. 36 shows a SegmentGroup (segment group) whose GroupType is “bookmarks” from the first Program (FIG. 33) and the second Program (FIG. 34). ) Shows a configuration example when the segments are grouped. In this way, by using the segment description metadata, a segment group (segment group) that collects scenes in which desired objects (for example, favorite performers) appear across multiple programs, that is, its It is possible to define a SegmentGroup (segment group) that collects such bookmarks.

  As described above, in the present invention, examples of metadata that can be recorded on the removable recording medium (removable recording medium 31 in FIG. 3 or removable recording medium 131 in FIG. 8) have been described.

  By the way, the form of the content navigation function to which the present invention is applied is not limited to the example of FIG. 3, and can take various forms. That is, the present invention can be applied not only to the client-oriented navigation of FIG. 2 but also to other content navigation functions.

  Specifically, for example, a form of content navigation function as shown in FIG. 37, that is, a form in which network-dependent navigation (FIG. 1) and client-oriented navigation (FIG. 2) are combined (hereinafter referred to as such). Such a form is referred to as hybrid navigation). That is, FIG. 37 is a diagram for explaining the hybrid navigation method.

  In the hybrid navigation method, the client 302-A is provided with both the browser 311 and the client application 312. The client 302-A is also provided with a client metadata database 313.

  Further, the server 301 is provided with a shop server 321 and a metadata database 322. Although not shown, the server 301 may be provided with a settlement server, a content server, a DRM server, and the like similar to the server 101 of FIG.

  The operation of the client 302-A in the hybrid navigation is basically the operation of the client 1 in the network-dependent navigation (FIG. 1) and the operation of the client 11-A in the client-based navigation (FIG. 2). It is a combination. Therefore, detailed description thereof is omitted here.

  As described above, the hybrid navigation has the features of the client-driven navigation (FIG. 2) and the features of the network-dependent navigation (FIG. 1) as they are.

  However, even in the hybrid type navigation, the third problem and the fourth problem described above, which the client-driven navigation has, are included as they are.

  Therefore, as shown in FIG. 38, the third and fourth problems can be solved by applying the same technique (the technique of the present invention) as in FIG. 3 to hybrid navigation. Can do. That is, FIG. 38 is a diagram for explaining another form (a form different from FIG. 3) of the content navigation method to which the present invention is applied. In FIG. 38, parts corresponding to those in FIG.

  As shown in FIG. 38, by applying the present invention to the hybrid navigation, the client 302-B is able to display the metadata stored in the metadata database 322 of the server 301 and the client application (navigation program). ) Information such as 312 -A can be acquired from the removable recording medium 332.

  Accordingly, even when the present invention is applied to the hybrid navigation (FIG. 38), it is possible to achieve the same effect as when the present invention is applied to the client-oriented navigation (FIG. 3). Become.

  Incidentally, the removable recording medium to which the present invention is applied (removable recording medium 31 of FIG. 3, removable recording medium 131 of FIG. 8, etc., removable recording medium 332 of FIG. 38, etc.) is manufactured according to the flowchart of FIG. Can do.

  That is, FIG. 39 is a flowchart for explaining a method of manufacturing a removable recording medium to which the invention is applied. Therefore, a method for manufacturing a removable recording medium to which the present invention is applied will be described below with reference to the flowchart of FIG.

  As described above, the form of the removable recording medium manufacturing apparatus is not particularly limited, but here, description will be given assuming that the server 101 in the above-described form (personal computer) in FIG. 5 is the manufacturing apparatus.

  First, in step S <b> 301, the CPU 121 of the server 101 determines whether or not the removable recording medium 131 is attached to the drive 130.

  If the removable recording medium 131 is not attached to the drive 130 (when it is determined in step S301 that the removable recording medium 131 is not attached), the process returns to step S301 to determine whether the removable recording medium 131 is attached. It is determined again whether or not. That is, the process of step S301 is repeated until the removable recording medium 131 is loaded.

  When the removable recording medium 131 is loaded in the drive 130, the CPU 121 determines in step S301 that the removable recording medium 131 is loaded, and in step S302, reads the metadata from the storage unit 128 and the like, and stores it in the removable recording medium 131. Let me record.

  In step S303, the CPU 121 determines whether or not to store the navigation program 203-A (FIG. 8).

  If it is determined in step S303 that the navigation program 203-A is not stored, the process ends. That is, the removable recording medium 131 in which only metadata is recorded is manufactured.

  If it is determined in step S303 that the navigation program 203-A is not stored, the process may not end and the process may proceed to step S305.

  On the other hand, if it is determined in step S303 that the navigation program 203-A is stored, the CPU 121 reads the navigation program 203-A from the storage unit 128 or the like and records it in the removable recording medium 131 in step S302.

  In step S304, the CPU 121 determines whether to record other information.

  If it is determined in step S305 that no other information is stored, the process ends. That is, the removable recording medium 131 in which the metadata and the navigation program 203-A are recorded is manufactured.

  On the other hand, if it is determined in step S305 that other information is to be recorded, the CPU 121 reads the corresponding information (other information) from the storage unit 128 or the like and records it in the removable recording medium 131 in step S306. As a result, the process ends, and the removable recording medium 131 on which the metadata, the navigation program 203-A, and other information are recorded is manufactured.

  By the way, when the above-described series of processing is executed by software, a program (for example, a client application) constituting the software is installed from a network or a recording medium.

  As shown in FIG. 3, FIG. 5, FIG. 6, FIG. 38, etc., this recording medium is distributed to distribute the program to the user separately from the main body of the apparatus. From floppy disk), optical disk (including CD-ROM (compact disk-read only memory), DVD (digital versatile disk)), magneto-optical disk (including MD (mini-disk)), or semiconductor memory A program that is distributed not only to the removable recording media 31 (FIG. 3), 131 (FIGS. 5 and 6, etc.) and 332 (FIG. 38) to be distributed to the user in a state of being incorporated in the apparatus main body in advance. The recorded ROM 122 (FIG. 5) and 159 (FIG. 6), the hard disk included in the storage unit 128 and the auxiliary storage unit 160, etc.

  The series of processes described above may be executed by hardware as needed.

  Further, in the present specification, the step of describing the program recorded on the recording medium is not limited to the processing performed in chronological order according to the described order, but may be performed in parallel or It also includes processes that are executed individually.

  Further, in this specification, the system represents the entire apparatus constituted by a plurality of apparatuses.

  In the above description, the client is described as being configured by the hard disk video recorder shown in FIG. 6 or the personal computer shown in FIG. 5. However, as described above, the client to which the present invention is applied is removable recording. The form is not particularly limited as long as the medium can be loaded. In addition to these, the present invention can be applied to a digital television receiver, a DVD (Digital Versatile Disk) recorder, and other various content processing apparatuses.

  Further, the content to be distributed is not limited to a television broadcast program, and can be various types of content.

It is a figure explaining the conventional form (network dependent navigation) of a content navigation function. It is a figure explaining the form (client-oriented navigation) of the content navigation function which can solve the problem which the network dependence type navigation of FIG. 1 has. It is a figure explaining the form at the time of applying this invention to the client-centered navigation of FIG. 2, ie, the form of the content navigation function to which this invention is applied. It is a block diagram which shows the structural example of the content delivery system to which this invention is applied. It is a block diagram which shows the hardware structural example of the server of FIG. It is a block diagram which shows the hardware structural example of the client of FIG. It is a front view which shows the structural example of the external appearance of the remote commander which operates the client of FIG. 6 remotely. It is a block diagram which shows the functional structural example of the content delivery system of FIG. It is a figure explaining the relationship between various ID and metadata. It is a figure which shows the relationship between package metadata, license metadata, and content metadata. 5 is a flowchart for explaining an operation example when the client in FIG. 4 acquires content distributed from a server. 12 is a flowchart for explaining a detailed example of metadata pre-acquisition processing in FIG. 11. 12 is an arrow chart for explaining a detailed example of the purchase content navigation process of FIG. 11. It is a figure which shows the example of the image (content list) for the user interface for making a user determine the purchase content which the presentation part of the client of FIG. 8 presents to a user. It is a figure explaining the detailed example of the license acquisition process of FIG. 12 is an arrow chart for explaining a detailed example of the download process of FIG. 12 is an arrow chart for explaining a detailed example of the usage content navigation process of FIG. 11. It is a figure explaining the classification method of metadata. It is a figure explaining the rule of the symbol used by FIG. It is a figure explaining the structural example of the content description metadata among the content search attribute metadata of FIG. It is a figure which shows the structural example of Program (program) among the content description metadata of FIG. It is a figure which shows the example of a hierarchical structure of the genre which can be described in Genre (genre) of Program (program) of FIG. It is a figure which shows the structural example of ProgramGroup (program group) among the content description metadata of FIG. It is a figure explaining the structural example of the instance description metadata among the content search attribute metadata of FIG. It is a figure explaining the structural example of ProgramLocation (program location) of the instance description metadata of FIG. It is a figure explaining the structural example of OnDemandLocation (on-demand location) among the instance description metadata of FIG. It is a figure explaining the structural example of ScheduleEvent (schedule event) of the instance description metadata of FIG. FIG. 25 is a diagram illustrating a configuration example of Service in the instance description metadata in FIG. 24. It is a figure which shows the example of the general EPG (Electronic Program Gide) displayed on the screen. It is a figure explaining the structural example of the segment description metadata among the content search attribute metadata of FIG. It is a figure explaining the structural example of Segment (segment) among the segment description metadata of FIG. It is a figure explaining the structural example of SegmentGroup (segment group) among the segment description metadata of FIG. It is a figure which shows the structural example of the 1st program for demonstrating the usage method of segment description metadata. It is a figure which shows the structural example of the 2nd program for demonstrating the usage method of segment description metadata. The figure which shows the structural example at the time of putting together the Segment (segment) of SegmentGroup (segment group) whose GroupType (group type) is "highlights" from the 1st program of FIG. 33 and the 2nd program of FIG. It is. The figure which shows the structural example at the time of putting together the Segment (segment) of SegmentGroup (segment group) whose GroupType (group type) is "bookmarks" from the 1st program of FIG. 33 and the 2nd program of FIG. It is. It is a figure explaining the principle of the content navigation function (hybrid type navigation) which combined the network dependence type navigation of FIG. 1, and the client main body type navigation of FIG. It is a figure explaining the form at the time of applying this invention to the hybrid type navigation of FIG. 37, ie, the other form of the content navigation function to which this invention is applied. It is a flowchart explaining the manufacturing process of a removable recording medium.

Explanation of symbols

  11-A, 11-B client, 21 client application, 21-A client application (navigation program), 22 client metadata database, 31 removable recording medium, 101 server, 102 network, 103 client, 131 removable recording medium, 157 CPU 159 ROM, 162 input unit, 163 communication unit, 164 drive, 203 client application, 204 content playback unit, 205 DRM processing unit, 206 billing processing unit, 207 download processing unit, 208 content storage unit, 209 client metadata database, 221 shop server, 222 settlement server, 223 metadata database, 2 4 DRM server, 225 content server, 301 server, 302-A, 302-B client, 311 browser, 312 client application, 312-A client application (navigation program), 313 client database, 321 shop server, 322 metadata database, 332 Removable recording medium

Claims (11)

In an information processing apparatus that acquires and uses externally arranged content,
First metadata for specifying predetermined content (content description metadata, FIG. 20, paragraphs 0299 to 0304), and a plurality of instances of the predetermined content (instances described by instance description metadata, paragraph 0296) Second metadata (instance description metadata, FIG. 24, paragraph 0325) for specifying each and their position is recorded for each content, and the content to be acquired is selected from one or more of the above contents A guidance step that guides a series of user operations up to and including the first metadata, and a predetermined instance of the plurality of instances of the content selected by the user according to the processing of the guidance step recognizing position from the second metadata Accessing that position, an acquisition step of acquiring the content, the mounting means the program recording medium that is recorded is attached including,
The guiding step included in the program recorded on the recording medium using the first metadata and the second metadata recorded on the recording medium mounted on the mounting means; the obtaining step and the respective processing information processing apparatus Ru and a execution means for executing.   The second metadata is:
    Information for identifying each of the plurality of instances of the predetermined content (ProgramLocation (program location), FIG. 24, paragraphs 0303, 0326 to 0328),
    Among the positions of the plurality of instances of the predetermined content, information indicating the position of an instance existing on the Internet (OnDemandLocation, FIG. 24, paragraphs 0329 to 0333);
    Of the positions of the plurality of instances of the predetermined content, information indicating the position of the broadcasted instance (ScheduleEvent (schedule event), FIG. 24, paragraphs 0334 to 0339) and
  including
  The information processing apparatus according to claim 1. The recording medium further records information necessary for obtaining the first metadata and the second metadata,
The execution means, the respective processing of the first metadata and the second metadata retrieved from the recording medium, wherein the obtaining step and the inductive step using these metadata according to the information Execute
The information processing apparatus according to 請 Motomeko 1. The recording medium further records information necessary for executing at least a part of the processing of the guidance step and the acquisition step,
The execution means executes a corresponding process of the guidance step and the acquisition step according to the information.
The information processing apparatus according to 請 Motomeko 1. In addition to the first metadata and the second metadata, the recording medium further includes third metadata (content product metadata) for specifying a purchase period, a price, and a license for each of the contents. Data and license management metadata (FIG. 18, paragraphs 0286, 0289) are recorded, and the program including the guiding step for further using the third metadata is recorded.
The information processing apparatus according to 請 Motomeko 1.   In addition to the first metadata, the second metadata, and the third metadata, the recording medium further specifies a plurality of segments obtained by dividing the predetermined content in the time direction. 4th metadata (segment description metadata, FIG. 18, paragraphs 0297, 0347) to be recorded and predetermined content in units of the segments for the content using the fourth metadata. The program further including a process execution step for performing a process is recorded,
  The execution means further executes the predetermined process by the process execution step using the fourth metadata.
  The information processing apparatus according to claim 5. The execution means further executes processing of other steps included in another program different from the program recorded on the recording medium in order to acquire and use the content,
The recording medium further records information necessary for executing at least a part of the processing of the other steps included in the other program.
The information processing apparatus according to 請 Motomeko 1. The recording medium further records data of another content different from the one or more content specified by the first metadata .
The information processing apparatus according to 請 Motomeko 1. In an information processing method of an information processing apparatus that acquires and uses content arranged outside,
First metadata specifying predetermined content and second metadata specifying each of a plurality of instances of the predetermined content and their positions are recorded for each content , and one or more of the contents A guidance step for guiding a series of user operations until selecting content to be acquired from among the first metadata, and the content of the content selected by the user according to the processing of the guidance step the position of a given instance of the plurality of instances recognized from the second metadata by accessing the location, an acquisition step of acquiring the content, the recording medium having a program recorded including the When attached to an information processing device,
The guiding step included in the program recorded on the recording medium using the first metadata and the second metadata recorded on the recording medium attached to the information processing apparatus And the acquisition step are executed.
Information processing method. In a recording medium attached to an information processing apparatus that acquires and uses content arranged outside,
First metadata specifying predetermined content and second metadata specifying each of a plurality of instances of the predetermined content and their positions are recorded for each content , and one or more of the contents A guidance step for guiding a series of user operations until selecting content to be acquired from among the first metadata, and the content of the content selected by the user according to the processing of the guidance step the position of a given instance of the plurality of instances recognized from the second metadata by accessing the location, the program comprising: an acquisition step of acquiring the content is recorded
Record media. In a method for manufacturing a recording medium mounted on an information processing apparatus that acquires and uses content arranged outside,
First recording that specifies first metadata for specifying predetermined content and second metadata for specifying each of a plurality of instances of the predetermined content and their positions on the recording medium for each content in advance A guiding step for guiding a series of user operations from the one or more of the contents until the user selects a content to be acquired using the first metadata; and the position of a given instance of the plurality of instances of the content selected in accordance with the processing recognized from the second metadata, accessing that location, said program comprising: an acquisition step of acquiring the content manufacturing method of the second recording step and the including record medium previously recorded on the recording medium.

Images