JP2011180762A - Terminal device, content navigation program, recording medium recording the same and content navigation method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow a service provider to more easily and more flexibly change and expand original content navigation, in a metadata service. <P>SOLUTION: The terminal device 100 includes: a storage means storing a navigation information table 150 described with information related to the content navigation transmitted from a metadata server 200; an input means 110 receiving content navigation operation from a user; a metadata request means 120 generating a retrieval request of metadata based on the content navigation operation in reference to the navigation information table 150, transmitting it to the metadata server 200, and receiving the metadata as a retrieval result from the metadata server 200; and a presentation means 130 generating a content navigation screen based on the navigation information table 150 and the received metadata, and presenting it. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a metadata service, and in particular, in content portals and ECG (Electronic Contents Guide) using TV-Anytime metadata, service providers have their own content navigation (genre configuration, page transition, etc.) It relates to the technology to realize.

  As a core technology of the IPTV service, there is a metadata technology for describing / searching information (for example, title, content, genre, performer, etc.) of content provided on multiple channels or video on demand. As an example, TV-Anytime, a private international standard organization, and ARIB, a domestic private standard organization, standardize the metadata schema that defines the content and format described as metadata, making it easy for users to obtain the desired content. It is possible to search and select. At this time, by standardizing a classification scheme dictionary that defines content attribute information, different service providers can construct a common metadata database (see Non-Patent Document 1). .

ARIB STD-B38 "Encoding, transmission and storage control method in server type broadcasting", Appendix 1 Metadata Genre Dictionary

  TV-Anytime and ARIB standardize the metadata schema and classification scheme, and specify the two-way communication method of metadata, but do not specify the actual implementation method of content portal or ECG. Moreover, when an attempt is made to create a genre search screen or the like as an ECG, it is not a general and constant genre structure defined by the ARIB genre dictionary (see FIG. 13) such as news, animation, music, and overseas dramas. Demand to change the genre composition flexibly and timely in line with the service, such as subdividing the genre by anime supply company or adding Korean dramas or Chinese dramas to overseas dramas according to trends. Is done.

  Here, it is conceivable to change the ARIB genre dictionary as appropriate, but the ARIB genre dictionary defines a standard genre structure that does not depend on the service provider. It is difficult to change in a flexible and timely manner. Furthermore, the ARIB genre dictionary is a collection of genre systems that are assigned as content attributes. From the viewpoint of content navigation (genre structure / attributes, page transitions, etc.), The name, order, and hierarchical structure between genres cannot be defined individually.

 The present invention has been made in view of the above circumstances, and an object of the present invention is to easily and flexibly change and extend unique content navigation by a service provider in a metadata service. .

  In order to achieve the above object, the present invention is a terminal device that receives content metadata from a metadata server and performs content navigation, and the terminal device relates to content navigation transmitted from the metadata server. A storage unit that stores a navigation information table in which information is described, an input unit that receives a content navigation operation from a user, and generates a metadata search request based on the content navigation operation with reference to the navigation information table The content navigation screen based on the metadata request means for transmitting to the metadata server and receiving metadata as a search result from the metadata server, the navigation information table, and the received metadata. The navigation information table uniquely identifies a genre in content navigation and has an identifier that expresses a hierarchical structure of the genre, and the identifier is in the description order of the navigation information table. The display order on the content navigation screen of the genre specified by is defined.

  The present invention is a content navigation program for causing a computer to function as the terminal device.

  The present invention is a computer-readable recording medium on which the content navigation program is recorded.

  The present invention relates to a content navigation method performed by a terminal device that receives content metadata from a metadata server and performs content navigation, wherein the terminal device describes information related to content navigation from the metadata server. A storage step of receiving the navigation information table and storing it in the storage unit, an input step of accepting a content navigation operation from the user, and a metadata search request based on the content navigation operation with reference to the navigation information table Based on the metadata requesting step of generating, transmitting to the metadata server, and receiving metadata from the metadata server as a search result, the navigation information table, and the received metadata. The navigation information table uniquely identifies a genre in content navigation and has an identifier that expresses a hierarchical structure of the genre. The display order on the content navigation screen of the genre specified by the identifier in the description order is defined.

   According to the present invention, in a metadata service, a service provider can change and expand unique content navigation more easily and flexibly.

It is a block diagram which shows the structure of one embodiment of this invention. It is a figure explaining the example of a navigation information table. It is a figure explaining the schema of a navigation information table. It is a sequence diagram explaining the process between the receiving terminal and metadata server at the time of content navigation in one embodiment of this invention. It is a figure explaining the example of a top screen. It is a figure explaining the example of a genre selection screen (main genre list display). It is a figure explaining the example of a genre selection screen (sub genre list display). It is a figure explaining the example of a genre selection screen (search result display). It is a figure explaining the example of the metadata of content. It is a flowchart figure explaining the production | generation of the menu list and genre list | wrist using a navigation information table. It is a figure explaining the example of the navigation information table used in Example 1 and Example 2. FIG. It is a figure explaining the example of NavigationNodeTypeCS used in Example 2. FIG. It is a figure explaining ARIB genre dictionary (ARIBGenreCS).

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

  FIG. 1 is a block diagram showing a configuration of a content navigation system according to an embodiment of the present invention. This system includes a receiving terminal 100 that presents (displays) a content navigation screen to a user (user), and a metadata server 200 that is connected to the receiving terminal 100 via a network 300. Although only one receiving terminal 100 is shown in FIG. 1, a plurality of receiving terminals 100 are actually connected to the metadata server 200 via the network 300.

  The receiving terminal 100 (terminal device) is a terminal used by the user, and includes an input unit 110 that receives a content navigation operation from the user, and metadata that generates a search request to the metadata server 200 and receives metadata. The request unit 120, the classification scheme dictionary file 140 in which various terms of the metadata service are defined, the navigation information table 150 in which information on content navigation is described, the metadata, the classification scheme dictionary file 140, and the navigation information table 150 A presentation unit 130 for generating and presenting (displaying) a content navigation screen based on the content navigation screen.

  The classification scheme dictionary file 140 and the navigation information table 150 held by the receiving terminal 100 are synchronized with the classification scheme dictionary file 230 and the navigation information table 240 managed by the metadata server 200 (so as to hold the same data). ), And is updated at a predetermined timing (for example, when the receiving terminal 100 is activated or periodically).

  The metadata server 200 is a server managed and operated by a service provider, and performs a metadata service that provides desired metadata to the receiving terminal 100. The metadata server 200 shown in the figure transmits metadata to the receiving terminal 100 via the network 300 and also transmits a classification scheme dictionary file 230 and a navigation information table 240, a metadata search unit 210, a metadata DB 220, a classification It has a scheme dictionary file 230 and a navigation information table 240. The metadata DB 220 stores, for each content, metadata in which various information related to the content (content storage location, title, genre, description, etc.) is described.

  FIG. 2 is a diagram illustrating an example of the navigation information tables 150 and 240. In the navigation information table, as shown in the figure, a genre configuration or a page configuration in content navigation (genre configuration / attribute, page transition, etc.) is described in units of NodeDescription. At this time, an identifier for uniquely identifying each genre or page is described in “NodeDescription genreIdRef”, and the genre or page configuration (hierarchical structure or the like) is expressed using the identifier.

  Further, the name and attribute of each genre or page are defined by the element specified by the identifier, and the display order on the content navigation screen is defined in the description order of the navigation information table of the element specified by the identifier. Specifically, the genre / page name is “Title”, the genre / page description is “Synopsis”, the genre / page attribute information is “Genre”, and the genre / page related information is “RelatedMaterial”. The parental attribute of the genre and page is described in “ParentalGuidance”, respectively.

  Hereinafter, the genre defined in the navigation information tables 150 and 240 is referred to as “Navi genre”, and the identifier described in “NodeDescription genreIdRef” of the navigation information table is referred to as “Navi genre ID”.

  FIG. 3 is a diagram showing a schema of the navigation information tables 150 and 240.

  As the receiving terminal 100 and the metadata server 200 described above, for example, a general-purpose computer system including a CPU, a memory, an external storage device such as an HDD, an input device, and an output device can be used. In this computer system, each function of each device is realized by the CPU executing a predetermined program loaded on the memory. For example, the functions of the receiving terminal 100 and the metadata server 200 are the CPU of the receiving terminal 100 in the case of the program for the receiving terminal 100, and the CPU of the metadata server 200 in the case of the program for the metadata server 200. It is realized by executing each.

  Further, the program for the receiving terminal 100 and the program for the metadata server 200 can be stored in a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, or a DVD-ROM. It can also be distributed via.

  Next, processing of the receiving terminal 100 and the metadata server 200 during content navigation will be described with reference to the sequence diagram of FIG.

  First, in the receiving terminal 100, the system is activated when the input unit 110 accepts a user operation (step S100). Thereby, the input unit 110 accesses the metadata server 200, acquires the latest classification scheme dictionary file 230 and navigation information table 240 managed by the metadata server 200, and acquires the classification scheme dictionary file 140 and navigation of the receiving terminal 100. The information table 150 is updated to the latest state (step S101). Thereby, the metadata server 200 and the receiving terminal 100 can hold the same classification scheme dictionary file and navigation information table.

  The process of obtaining the classification scheme dictionary file 230 and the navigation information table 240 of the metadata server 200 and updating the classification scheme dictionary file 140 and the navigation information table 150 of the receiving terminal 100 to the latest state is performed only at the time of system startup. Instead, it is performed at an arbitrary timing such as periodically at predetermined time intervals.

  Then, the presentation unit 130 refers to the updated navigation information table 150, generates a top screen (content navigation screen), and displays it on the display device of the receiving terminal 100. At this time, NodeDescription having a Navi genre ID one level lower than the Navi genre ID corresponding to the top screen is displayed as a menu list (step S102).

  For example, in the case of the navigation information table 150 shown in FIG. 2, specifically, the “top screen” with the Navi genre ID ““ NavigationCS: 2 ”” 201 is the root node, and one level lower in the lower layer. “NavigationCS: 2.1” 202 with “Navi Genre ID” 202 “Genre Search”, “NavigationCS: 2.2” 203 “New Arrival of this Month”, “NavigationCS: 2.3” 204 “Ranking”, “Keyword search” of “NavigationCS: 2.4” 205 is presented as a menu list. FIG. 5 shows an example of the top screen.

  Next, when a desired menu on the top screen or a desired genre on the genre selection screen (content navigation screen) is selected via the input unit 110 in accordance with a user operation instruction (step S103), the presentation unit 130 Referring to the navigation information table 150, a genre selection screen is generated and displayed based on the selected menu or NodeDescription information corresponding to the genre. At this time, the Navi genre ID corresponding to the selected menu or genre is notified by the presentation unit 130, and NodeDescription having a Navi genre ID one level lower than the Navi genre ID is displayed as a genre list (step S104). ).

  For example, in the case of the navigation information table 150 shown in FIG. 2, when the “genre search” (Navi genre ID: “NavigationCS: 2.1”) button on the top screen shown in FIG. It has "" NavigationCS: 2.1.1 "" 211 "foreign film", "" NavigationCS: 2.1.4 "" 212 "Japanese film", "" NavigationCS: 2.1.2 "" 213 "music", " A genre selection screen is generated and displayed with a genre list such as “NavigationCS: 2.1.3” 214 “drama” and “NavigationCS: 2.1.5” 215 “sports” (see FIG. 6). .

  In the case of the navigation information table 150 shown in FIG. 2, when the “drama” (Navi genre ID: “NavigationCS: 2.1.3”) button on the genre selection screen shown in FIG. A genre selection screen is generated and displayed with a genre list such as “Overseas drama” of “NavigationCS: 2.1.3.1” 221 with ID and “Domestic drama” of “NavigationCS: 2.1.3.3” 222 (See FIG. 7).

  Thereafter, when a genre determination operation is input by the user on the genre selection screen (step S105), the metadata request unit 120 acquires the Navi genre ID of the genre determined and operated via the input unit 110. Then, the metadata request unit 120 refers to the navigation information table 150, generates a search query using the acquired Navi genre ID as an argument, and transmits a search request including the search query to the metadata server 200 (step S1). S106).

  For example, when “domestic drama” (Navi genre ID: “NavigationCS: 2.1.3.3”) is selected on the genre selection screen shown in FIG. 7, a search query such as predicate = genre (NavigationCS: 2.1.3.3) is generated, Send to the metadata server 200.

  When receiving the search request, the metadata search unit 210 of the metadata server 200 extracts at least one metadata associated with the Navi genre ID of the argument from the metadata DB 220, and uses each extracted metadata as a search result. Transmit to the receiving terminal 100. The presentation unit 130 of the receiving terminal 100 receives the search result from the metadata server 200 (step S107), and displays the content information described in each metadata as the search result on the display device as the search result (step S108). .

  FIG. 8 shows an example of the genre search result screen. In the example shown in the figure, the metadata of the contents A, B, C, and D is received as a search result. In this case, it is assumed that the Navi genre ID to which the content belongs is described by a Genre tag (Genre href) in the metadata of each content. For example, in the metadata of the content A shown in FIG. 9, “NavigationCS: 2.1.3.3” and “NavigationCS: 2.2.3” 901 are described in the Genre tag. When the metadata search unit 210 of the metadata server 200 receives a search query search request with the Navi genre ID “NavigationCS: 2.1.3.3” or “NavigationCS: 2.2.3” as an argument, the metadata search unit 210 of the content A shown in FIG. Metadata is extracted and transmitted to the receiving terminal 100 as a search result. Accordingly, the content A is displayed as a search result on the genre selection screen of “drama> domestic drama” and “this month's new arrival> drama” for genre search.

<Use of navigation information table for display control of menu list and genre list>
Below, the presentation unit 130 of the receiving terminal 100 uses the navigation information table 150 to generate a menu list on the top screen (step S102 in FIG. 5), and a process to generate a genre list on the genre selection screen (FIG. The details of step S104) of FIG.

  FIG. 10 is a flowchart showing processing for generating a menu list and a genre list. First, the presentation unit 130 acquires a Navi genre ID (NodeDescription genreIdRef) corresponding to the top screen or the selected menu / genre (step S201). For example, “NavigationCS: 2” for the top screen, “NavigationCS: 2.1” for “genre search” on the top screen, and “NavigationCS: 2.1.” For “drama” on the genre selection screen. 3 ″ is acquired (see FIG. 2). When the user presses a desired button on each screen, the Navi genre ID corresponding to the button is notified to the presentation unit 130 via the input unit 110.

  Next, the presentation unit 130 refers to the navigation information table 150, and acquires a NodeDescription whose Navi genre ID is NavigationCS: A.X (X is an arbitrary number) (step S202). For example, in the case of the top screen (NavigationCS: 2), NavigationCS: 2.1 (genre search), NavigationCS: 2.2 (new arrival of this month), NavigationCS: 2.3 (ranking), and NavigationCS: 2.4 (keyword search) are acquired. If you select “Genre Search” (NavigationCS: 2.1) on the top screen, NavigationCS: 2.1.1 (foreign film), NavigationCS: 2.1.4 (Japanese film), NavigationCS: 2.1.2 (music), NavigationCS: 2.1. 3 (drama), NavigationCS: 2.1.5 (sports), NavigationCS: 2.1.7 (adults), etc. are acquired. If “Drama” (NavigationCS: 2.1.3) is selected on the genre selection screen, NavigationCS: 2.1.3.1 (overseas drama), NavigationCS: 2.1.3.3 (domestic drama), NavigationCS: 2.1.3.6 (R cinema) ) And the like are acquired (see FIG. 2).

  Next, the presentation unit 130 compares and checks the acquired attribute of each NodeDescription (eg, Genre, mpeg7: ParentalRating, etc.) and the attribute set in the storage unit such as the memory of the receiving terminal 100 (step S203), If it is determined that the node description can be presented (step S204: YES), it is added as a list publication target such as a menu list or a genre list (step S205).

  For example, the display target users of each genre are defined by Genre [href = “IntendedAudienceCS: X”]. In the example of FIG. 2, the display target users of the top (NavigationCS: 2) and genre search (NavigationCS: 2.1) are general. It is a user (IntendedAudienceCS: 4.1). On the other hand, the display target user of the ranking (NavigationCS: 2.3) is an internal user (IntendedAudienceCS: 4.0). As a result, the ranking is not displayed in the menu list in the receiving terminal 100 of the general user, but is displayed in the menu list in the receiving terminal 100 of the internal user.

  In this manner, for example, when a new menu is added, the display target user attribute of the genre is edited (set) in the navigation information table 240 on the metadata server 200 side, and the navigation information table 240 is stored in each receiving terminal 100. Send to. As a result, on the receiving terminal 100 side, it is possible to easily perform an operation such as first confirming in advance with the receiving terminal 100 of the internal user and releasing the information to the receiving terminal 100 of the general user after confirmation. It is assumed that user attributes (general users or internal users) are stored in a storage unit (not shown) such as a memory of each receiving terminal 100.

  Also, the viewing age limit for each genre is specified by mpeg7: ParentalRating or [href = “ARIBParentalRatingCS: X]. In the example of FIG. 2, the top (NavigationCS: 2) and drama (NavigationCS: 2.1.3) are viewed There is no age restriction (G), whereas adults (NavigationCS: 2.1.7) are R-20 and R-cinema (NavigationCS: 2.1.3.6) are R-18. When the viewing age setting of the receiving terminal 100 is set to “17 years old”, the adult genre and the R cinema genre are not displayed on the receiving terminal 100, and the viewing age setting is set to “no limit” or the like In this way, by editing the viewing age restriction attribute of the genre in the navigation information table 240 on the metadata server 200 side, the display control of the genre according to the viewing age setting of the receiving terminal 100 can be easily performed. In addition, each reception The storage unit such as a memory of the end 100 (not shown), it is assumed that the viewing age limit attribute is stored.

  After the process of step S205 or in the case of step S204: NO, the presentation unit 130 repeats the process from step S202 to step S205 until the end of the navigation information table 150 (step S206). Then, the presentation unit 130 generates a menu list and a genre list based on the created list posting target (step S207).

  Here, the arrangement order of the menus and genres in the menu list and genre list is not the Navi genre ID order, but the description order in the navigation information table 150 of each NodeDescription. By doing this, without worrying about genre ID allocation, changing the description order in the navigation information table 240 on the metadata server 200 side, by sending the navigation information table 240 to the receiving terminal 100, The arrangement order of menus and genres can be changed, and addition and deletion of menus and genres can be easily performed.

<Use of navigation information table for display items on top screen and genre selection screen>
Hereinafter, a method in which the presentation unit 130 generates a top screen and a genre selection screen with reference to the navigation information table 150 will be described. For example, the names of menus and genres refer to the titles of each node description, and descriptions of menus and genres refer to the synopsis of each node description (see FIGS. 5, 6 and 7).

  Furthermore, when the genre list is displayed, it may be possible to explicitly indicate the presence or absence of a lower genre (（mark in FIG. 6). Specifically, by performing the above-described genre list generation process (see FIG. 10) for each genre displayed on the genre selection screen, it is possible to know whether each genre has a lower genre. In the example of FIG. 2, the “Japanese movie” (NavigationCS: 2.1.4) genre is in the first layer but there is no lower genre (see FIG. 6), and “Overseas drama” (NavigationCS: 2.1.3.1) is at the lowest level. Since there is no lower genre (see FIG. 7), it can be seen visually.

[Example 1] <Search option>
In the above embodiment, after searching for a genre, when searching for content belonging to that genre, the search is performed using only the Navi genre ID (step S106 in FIG. 4). Here, as a result of the genre search, for example, search only for content within the provision period, search for only new content, or prevent adult content from being searched by keyword search, search and navigation It is conceivable to expand the search function according to the type. Usually, such a function expansion is implemented as a function on the receiving terminal 100 side, but it is desired that the search function can be expanded in a more flexible form. Therefore, in the first embodiment, a method for arbitrarily expanding a search query used at the time of searching for each type of search (navigation type) using RelatedMaterial of NodeDescription will be described.

  FIG. 11 shows an example of a navigation information table for implementing this search query extension. For example, in each genre search under “New Arrivals this Month” (NavigationCS: 2.2), consider only searching for content whose current time is included in the new arrival period. At this time, as shown in FIG. 9, it is assumed that a new arrival period (Period [type = “new_arrival”] / Start, End) 902 is set in the metadata of each content. Here, for example, when the “new arrival of this month” genre screen is displayed and “foreign film” (NavigationCS: 2.2.3) is selected from the genre list, the metadata request unit 120 displays the genre for which the determination operation has been executed. Get Navi genre ID (NodeDescription genreIdRef).

  Further, the metadata request unit 120 searches the navigation information table for a search option (RelatedMaterial / HowRelated [href = ”HowRelatedCS: 17” / MediaLocator / mpeg7: MediaUri] 1102 of the acquired Navi genre ID (NavigationCS: 2.2.3) 1101. Here, in addition to the search option, related material (genre image, etc.) can be set in RelatedMaterial, so that the search option is a classification scheme dictionary (refer to FIG. 12) referred to by HowRelated href. Distinguish by termID.

  In the example of FIG. 11, a character string “option: period (new_arrival, $ YYYYMMDDhh $, $ YYYYMMDDhh $ + 1h)” 1102 is acquired as a search option, and when used as an actual search query, Excluding option: ”, change the $ YYYYMMDDhh $ part to the current time (specified by year / month / day, hour and minute rounded down), and add $ YYYYMMDDhh $ + 1h part to the current time by one hour (hours and minutes rounded down) Change to In addition, the description method of a search option shall not be limited to the above, but shall be described in a format according to the implementation form of each system.

  As described above, when the current time is 2009/07/10/12: 23: 03, the search query to the metadata server 200 is as follows.

predicate = genre (NavigationCS: 2.2.3), period (new_arrival, 2009071012, 2009071013)
After that, the metadata request unit 120 transmits this search query to the metadata server 200, so that the metadata of the content that belongs to “this month's new arrival-drama” as the genre and the current time is included in the new arrival period (for example, (Metadata of content A in FIG. 9) is returned as a search result.

  In addition, in each genre search under “Genre search” (NavigationCS: 2.1), if you want to search only the content within the provision period (Period [type = ”availability”] / Start, End) Although it is possible to list search options in RelatedMaterial of NodeDescription, if the same search option is applied uniformly to each genre, search options are displayed in the upper NodeDescription, in this case “Related Search” (NavigationCS: 2.1) RelatedMaterial It is conceivable that the upper search option is inherited in the lower genre.

  Thereby, management becomes easy and the size of the navigation information table can be suppressed. For example, when “domestic drama” (NavigationCS: 2.1.3.3) is selected on the genre selection screen shown in FIG. 7, Navi genre ID (NavigationCS: 2.1.3.3) 1111 of “domestic drama” and “genre search” ( The search option 1112 described in RelatedMaterial of NavigatioNCS: 2.1) is acquired, and the following search query is generated. The current time is 09/07/10/12: 23: 03.

predicate = genre (NavigationCS: 2.1.3.3), period (availability, 2009071012, 2009071013)
Thereafter, the metadata request unit 120 transmits this search query to the metadata server 200, so that a content that belongs to “domestic drama” as a genre and whose current time is included in the provision period is returned as a search result.

  In addition, as a search result of “keyword search” (NavigationCS: 2.4), when it is desired to prevent adult content from being searched, “option:! Parentalrating (ARIBParentalRatingCS: R- 20) Write “1121”. Here, the search query for keyword search is “predicate = keyword (<word>)”, where <word> is a keyword character string to be searched. Here, when the above-described search options are described, a search query to the metadata server 200 is as follows.

predicate = keyword (<word>) ,! parentalrating (ARIBParentalRatingCS: R-20)
In other words, content metadata having a character string indicated by <word> and having a parental rating other than R-20 (adult) is returned as a search result. On the other hand, if the above search option is not described, the metadata of the content whose parental rating is R-20 having the character string indicated by <word> is also returned as the search result.

[Example 2] <Screen type, NavigationNodeTypeCS>
When considering content navigation (genre configuration / attributes, page transitions, etc.), not only can the genre configuration / attributes be represented, but also the final screen (for example, top screen, genre search screen, new arrival screen, ranking screen) It is necessary to be able to express the correspondence between genres and keyword search screens.

  Therefore, in the second embodiment, a method will be described in which each of the above screens is classified for each type, and the screen type used in each genre is arbitrarily specified by the type attribute of NodeDescription. Also in the second embodiment, the extended navigation information table shown in FIG. 11 is used. FIG. 12 is an example of the classification scheme dictionary files 140 and 230.

  First, the metadata server 200 classifies each screen by design and display items, and further by a search query used in each screen, and defines the screen using a classification scheme dictionary (NavigationNodeTypeCS) for screen types (see FIG. 12). In this case, NavigationNodeTypeCS only classifies screen types, and the design of each screen, display items, search queries used in each screen, and the like are managed on the receiving terminal 100 side in association with each screen type. In each receiving terminal 100, each screen design, display item, search query used in each screen, etc. transmitted (distributed) from the metadata server 200 is associated with each screen type in a storage unit such as a memory. It is remembered.

  Then, the presentation unit 130 of the receiving terminal 100 associates the genre with the screen type by referring to NavigationNodeTypeCS in each NodeDescription type of the navigation information table (see FIG. 11). As a result, the service provider (metadata server 200) can manage the correspondence between the genre configuration and the screen type managed in the receiving terminal 100.

  If the genre search screen with a modified design (color arrangement, components, etc.) (corresponding to “NavigationNodeTypeCS: genre_search2” 1201 in FIG. 12) is installed in the receiving terminal 100 side in advance, the service provider The (metadata server 200) side can easily change the design (for example, from horizontal writing to vertical writing) simply by changing the reference destination of NodeDescription type 1131 in the navigation information table (see FIG. 11) from “genre_search” to “genre_search2”. Change).

  Furthermore, when a new genre is added, by specifying an existing NavigationNodeTypeCS for the NodeDescription type, for example, a new product ranking screen can be created with the same screen type as the title ranking, or a TV program genre search can be performed with the same screen type as the genre search. You can easily create a new screen.

  In the present embodiment described above, the content navigation (genre and page configuration / attributes) in the metadata service can be defined uniquely by the service provider (metadata server) and easily changed / expanded. Become.

  Further, according to the first embodiment, the search function can be arbitrarily expanded according to the type of search and navigation, and the content navigation can be flexibly changed and expanded.

 According to the second embodiment of the present invention, it is possible to manage and specify the correspondence relationship between the genre configuration managed in the receiving terminal and the screen type to be presented on the service provider side.

  In addition, this invention is not limited to the said embodiment, Many deformation | transformation are possible within the range of the summary.

100 receiving terminal, 110 input unit, 120 metadata request unit, 130 presentation unit, 140 classification scheme dictionary file, 150 navigation information table, 200 metadata server, 210 metadata search unit, 220 metadata DB, 230 classification scheme dictionary file , 240 Navigation information table, 300 networks

Claims (10)

A terminal device that receives content metadata from a metadata server and performs content navigation,
The terminal device
Storage means for storing a navigation information table in which information about content navigation transmitted from the metadata server is described;
Input means for accepting content navigation operations from users;
Metadata request means for generating a metadata search request based on a content navigation operation with reference to the navigation information table, transmitting the metadata search request to the metadata server, and receiving metadata as a search result from the metadata server; ,
Based on the navigation information table and the received metadata, a content navigation screen is generated and provided for presentation,
The navigation information table is
A genre in content navigation is uniquely identified, and has an identifier that represents the hierarchical structure of the genre, and the display order on the content navigation screen of the genre specified by the identifier is specified in the description order of the navigation information table. Characteristic terminal device. The metadata request means includes
The terminal device according to claim 1, wherein the search request is generated using a genre identifier described in the navigation information table as a search key. In the navigation information table,
Search options used in content navigation for each genre are described,
The metadata request means includes
The terminal device according to claim 1, wherein the search request to which the search option of the navigation information table is added is generated. In the navigation information table,
The screen type used in each genre is described,
The presenting means is
4. The content navigation screen is generated by associating each genre with a screen type with reference to the screen type described in the navigation information table. 5. Terminal equipment.   The content navigation program for functioning a computer as a terminal device as described in any one of Claims 1-4.   A computer-readable recording medium on which the content navigation program according to claim 5 is recorded. A content navigation method performed by a terminal device that receives content metadata from a metadata server and performs content navigation,
The terminal device
A storage step of receiving a navigation information table in which information about content navigation is described from the metadata server, and storing it in a storage unit;
An input step for receiving a content navigation operation from a user;
A metadata request step of generating a metadata search request based on a content navigation operation with reference to the navigation information table, transmitting the metadata search request to the metadata server, and receiving the metadata as a search result from the metadata server; ,
Based on the navigation information table and the received metadata, a content navigation screen is generated and a presentation step is performed.
The navigation information table is
A genre in content navigation is uniquely identified, and has an identifier that represents the hierarchical structure of the genre, and the display order on the content navigation screen of the genre specified by the identifier is specified in the description order of the navigation information table. Feature content navigation method. The metadata request step includes:
8. The content navigation method according to claim 7, wherein the search request is generated using a genre identifier described in the navigation information table as a search key. In the navigation information table,
Search options used in content navigation for each genre are described,
The metadata request step includes:
The content navigation method according to claim 7 or 8, wherein the search request to which the search option of the navigation information table is added is generated. In the navigation information table,
The screen type used in each genre is described,
The presenting step includes
The content navigation screen is generated by associating each genre with a screen type with reference to the screen type described in the navigation information table. Content navigation method.

Images