Publishing system, publishing method, and nonvolatile storage medium

Abstract

Provided are a publishing system, a publishing method, and a non-volatile storage medium. By means of a configuration in which the display order and display frames of content are determined in advance on the basis of negotiation among publishing operators participating in a plan, each publishing operator can freely publish content at any moment in a negotiated framework of the operator. The publishing system comprises an application server and a program meta-server. The application server generates a template in which a plurality of content display frames are configured, wherein the content display frames indicate positions at which thumbnails corresponding to content are displayed. The program meta-server uses the template acquired from the application server, and content information corresponding to content acquired from a publishing operator server that publishes the content, to configure the thumbnails corresponding to the content in the content display frames comprised in the template, and outputs the thumbnails to a receiver.

Description

Publishing system, publishing method and non-volatile storage medium

[0001] Cross-reference to related applications

[0002] This application claims priority to Japanese Patent Application No. 2025-040310, filed on March 13, 2025, entitled "Publishing System, Publishing Method and Procedure", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to a publishing system, a publishing method, and a non-volatile storage medium. Background Technology

[0004] Previously, a publishing system was known to have multiple content display boxes in a program overview, with each display box showing content from multiple publishing operators.

[0005] Existing technical documents

[0006] Patent documents

[0007] Patent Document 1: Japanese Patent Application Publication No. 2024-60693. Summary of the Invention

[0008] For example, in a service that aggregates content from multiple publishers, when displaying thumbnails corresponding to the content on the screen, it's considered to display these thumbnails in the order of their registration time. However, if a publisher's registration time is later, the screen must scroll to display the thumbnails corresponding to the content published by that publisher, making it difficult for users to access content published by publishers with later registration times. Therefore, this could be disadvantageous to newly joined publishers. Furthermore, for existing publishers, it's also worth considering that many arrangements are needed to display thumbnails corresponding to their recommended content in a position that doesn't require scrolling.

[0009] The purpose of this application is to provide a mechanism by which the display order of thumbnails corresponding to content and the construction of display frames are determined through negotiation among publishing operators based on a pre-participation plan, allowing each publishing operator to freely publish content at any time within the framework of their negotiation. Furthermore, this framework provides a construction that can be re-examined at any time based on market conditions.

[0010] The publishing system of this implementation includes an application server and a program meta server. The application server generates a template configured with multiple content display frames, each indicating the position where a thumbnail corresponding to the content is displayed. The program meta server uses the template obtained from the application server and the content information corresponding to the content obtained from the publishing operator's server to configure the thumbnail corresponding to the content in the content display frames contained in the template and outputs it to the receiver. Attached Figure Description

[0011] Figure 1 is a diagram illustrating an example of the overall structure of the publishing system according to an implementation method;

[0012] Figure 2 is a diagram illustrating an example of the structure of program metadata in an implementation method;

[0013] Figure 3 is a diagram illustrating an example of a box definition file for an implementation method;

[0014] Figure 4 is a diagram illustrating an example of a content information file for an implementation method;

[0015] Figure 5 is a diagram illustrating a first display example of the TOP page of the implementation method;

[0016] Figure 6 is a diagram illustrating a second display example of the TOP page of the implementation method;

[0017] Figure 7 is a diagram showing an example of the display of the Genre page of the implementation method;

[0018] Figure 8 is a diagram illustrating an example of a VPF page display according to an implementation method;

[0019] Figure 9 is a template used to illustrate the implementation method;

[0020] Figure 10 is a diagram illustrating the content information of the implementation method;

[0021] Figure 11 is a diagram illustrating the content information of the implementation method;

[0022] Figure 12 is a diagram illustrating the subpages and a list of types used to explain the implementation methods;

[0023] Figure 13 is a flowchart up to the point where information including the template of the implementation method is displayed;

[0024] Figure 14 is a flowchart up to the point where the list of objects for the TOP screen display of the embodiment is generated;

[0025] Figure 15 is a flowchart up to the point where the list of objects for the TOP screen display of the implementation method is generated;

[0026] Figure 16 is a flowchart up to the point where the list of objects for the TOP screen display of the embodiment is generated;

[0027] Figure 17 is a flowchart up to the point where the list of objects for displaying the TOP screen of the embodiment is generated;

[0028] Figure 18 is a flowchart up to the point where the list of objects for the TOP screen display of the implementation method is generated;

[0029] Figure 19 is a flowchart up to the point where the list of objects for displaying the TOP screen of the embodiment is generated;

[0030] Figure 20 is a flowchart up to the point where the TOP screen of the implementation method is generated;

[0031] Figure 21 is a flowchart up to the point where the TOP screen of the implementation method is generated;

[0032] Figure 22 is a flowchart up to the point where the TOP screen of the implementation method is generated;

[0033] Figure 23 is a flowchart up to the point where the TOP screen of the implementation method is generated;

[0034] Figure 24 is a flowchart up to the point where the TOP screen of the implementation method is generated;

[0035] Figure 25 is a flowchart up to the view of the TOP screen of the implementation method;

[0036] Figure 26 is a flowchart up to the point where the TOP screen of the implementation method is generated.

[0037] Explanation of reference numerals in the attached diagram: 1… Publishing system, 2, 3, 4… Publishing operator server, 5… Application server, 6… Program meta server, 8, 9… Receiver, 83, 93… Display unit, 241… Content display frame. Detailed Implementation

[0038] The following description uses accompanying drawings to illustrate the publishing system, publishing method, and procedure of this embodiment.

[0039] Figure 1 is a diagram illustrating an example of the overall structure of the publishing system 1 according to an embodiment. As shown in Figure 1, the publishing system 1 includes publishing operator servers 2, 3, and 4, application server 5, program meta server 6, publishing network 7, and receivers 8 and 9. The number of publishing operator servers 2, 3, and 4 and receivers 8 and 9 shown in Figure 1 is an example, and multiple units may be included.

[0040] The publishing system 1 displays multiple contents on receivers 8 and 9 based on the template generated in application server 5, which has multiple content display boxes, the display order of the contents of multiple publishing operators set in application server 5, and the contents generated in publishing operator servers 2, 3, and 4.

[0041] The publishing operator server 2 includes a content publishing unit 21, an encoder 22, a publishing unit 23, and a generation unit 24. The publishing operator server 2 uses VPF (Video Platformer)-A as an example. The publishing operator server 2 is managed and controlled by the publishing operator (VPF).

[0042] Content publishing unit 21 stores content containing video. Content publishing unit 21 outputs content containing video to encoder 22. Encoder 22 compresses the content into a video and audio stream. Encoder 22 outputs the video and audio stream to publishing unit 23. Publishing unit 23 outputs the video and audio stream to publishing network 7, thus publishing the content.

[0043] The generation unit 24 obtains a template configured with multiple content display frames from the application server 5. The generation unit 24 generates information (content information) related to multiple contents according to the multiple content display frames. The generation unit 24 outputs the multiple content information to the program meta server 6.

[0044] The publishing operator server 3 includes a content publishing unit 31, an encoder 32, a publishing unit 33, and a generation unit 34. Publishing operator server 3 uses VPF-B as an example. Publishing operator server 3 has the same structure as publishing operator server 2.

[0045] The publishing operator server 4 includes a content publishing unit 41, an encoder 42, a publishing unit 43, and a generation unit 44. Publishing operator server 4 uses VPF-C as an example. Publishing operator server 4 has the same structure as publishing operator server 2.

[0046] Application server 5 includes a generation unit 51. Generation unit 51 generates multiple templates configured with content display frames, each indicating the location for displaying content to the display unit 83 of receiver 8. Each template contains multiple content display frames. Generation unit 51 outputs these templates to publishing operator servers 2, 3, and 4, and program meta server 6.

[0047] The generation unit 51 sets the display order (display order), which refers to the order in which the content is displayed according to each of the multiple content display boxes in the multiple templates.

[0048] The program metadata server 6 includes a receiving unit 61, a processing unit 62, and a sending unit 63. The receiving unit 61 receives program metadata from the publishing operator servers 2, 3, and 4, and the application server 5. For example, the receiving unit 61 receives multiple templates from the application server 5.

[0049] For example, receiving unit 61 receives information related to the content published by the publishing operator (program metadata, etc., also known as content information) and information on the thumbnails corresponding to the content from publishing operator servers 2, 3, and 4, respectively, and receives templates from application server 5.

[0050] The content information includes information about the thumbnail corresponding to the content (the URL of the publisher storing the thumbnail). This thumbnail is displayed in the content display box of the template. The receiving unit 61 outputs multiple pieces of content information and multiple templates to the processing unit 62.

[0051] The processing unit 62 stores multiple content information items and multiple templates. The processing unit 62 converts the content information into a format that the receiver 8 can display, compresses it, and outputs it along with the multiple templates to the transmitting unit 63. The transmitting unit 63 outputs the multiple content information items and multiple templates to the receivers 8 and 9.

[0052] The receiver 8 includes a receiver 81, a decoder 82, a display 83, a processing unit 84, a screen selection unit 85, a control unit 86, and a remote controller 87.

[0053] The receiving unit 81 receives video and audio streams from the publishing network 7. The receiving unit 81 outputs the video and audio streams to the decoder 82. The decoder 82 decompresses the video and audio streams and restores them to the original video content. The decoder 82 outputs the video content to the display unit 83.

[0054] The processing unit 84 receives multiple content information and multiple templates from the program meta server 6. The processing unit 84 processes the multiple content information and multiple templates and outputs them to the selection screen unit 85. The selection screen unit 85 constructs a display screen and outputs it to the display unit 83.

[0055] Display unit 83, based on a template configured with multiple content display frames, displays thumbnails corresponding to multiple contents in the multiple content display frames in display order. Remote control 87 sends commands to control unit 86 by being operated by the user. Control unit 86 receives commands from remote control 87 and performs the prescribed processing.

[0056] Receiver 9 includes a receiver 91, a decoder 92, a display 93, a processing unit 94, a screen selection unit 95, a control unit 96, and a remote controller 97. Receiver 9 has the same structure as receiver 8.

[0057] Figure 2 is a diagram illustrating an example of the structure of the program metadata 10 according to an embodiment. The program metadata 10 is stored in the program metadata server 6. The program metadata 10 includes a template for a display screen, in which thumbnails corresponding to multiple contents displayed on the receivers 8 and 9 are configured. In addition, the program metadata 10 includes a URL that retrieves information about the thumbnails corresponding to the contents displayed on the display frame of the template.

[0058] Specifically, for example, program metadata 10 includes templates for the TOP page, templates for the category page, templates for the VPF page, and information about the thumbnails corresponding to the content configured on each page.

[0059] As shown in Figure 2, the program metadata 10 includes operator information 11, operator ID-A12, operator ID-B14, and template 16. The program metadata 10 uses JSON (JAVASCRIPT (registered trademark) OBJECT NOTATION) format, etc.

[0060] Template 16 has TOP17 and Category 18. TOP17 has TOP Template List 171. TOP Template List 171 is the template list for the TOP page. TOP Template List 171 is the arrangement of the templates listed on the TOP page. The template names are set by the publishing operator servers 2, 3, and 4.

[0061] Category 18 includes a category list 181, a news template list 182, a sports (baseball) template list 183, and a subpage 19. Category list 181 defines the category display order, category name, or category icon image. News template list 182 is an example of a category page's template list. Sports (baseball) template list 183 is also an example of a category page's template list. Category names or icon images are defined by publishing operator servers 2, 3, and 4.

[0062] Subpage 19 contains a list of news subpage templates 191. The list of news subpage templates 191 is, for example, a detailed page of the news template list 182.

[0063] Carrier Information 11 includes multiple carrier IDs, carrier names, carrier logos, usage agreements, and privacy policies.

[0064] Carrier ID-A12 includes template 13, channel information 130, and programs. Template 13 includes TOP 131, category 132, and VPF 133. TOP 131 includes TOP content information 1311. TOP content information 1311 consists of thumbnails and other content configured on the TOP page.

[0065] Category 132 includes news content information 1321, sports (baseball) content information 1322, etc. News content information 1321, sports (baseball) content information 1322, etc., are examples of thumbnails and other content information configured on the category page.

[0066] VPF133 includes the VPF template list 1331 and VPF content information 1332. The VPF template list 1331 is the list of templates for the VPF page. The VPF content information 1332 contains content information such as thumbnails configured in the VPF page.

[0067] Channel information 130 includes service ID, service name, service description, category, parenting, service thumbnail image, logo, paid / free information, and animated image URL (the same for all programs within the channel).

[0068] Carrier ID-B14 has template 140, etc. Carrier ID-B14 has the same structure as Carrier ID-A12.

[0069] Figure 3 is a diagram illustrating an example of a frame definition file 100 according to an implementation method. The frame definition file 100 is generated by the application server 60 through protocols between multiple publishing operators. Specifically, for example, the frame definition file 100 is a file that specifies the display frames for each template of the TOP page. Additionally, the frame definition file 100 is a file that specifies the display frames for each template of the category page.

[0070] As shown in Figure 3, the frame definition file 100 includes a TOP frame definition file 110 and a category (special issue) file 120. The TOP frame definition file 110 defines the display frames for the TOP template list 171. For example, it may have TOP1 VPF mixed in 111, TOP2 application information 112, TOP3 VPF-B alone 113, etc.

[0071] TOP1 VPF Mixed in 111: For example, this is defined as configuring VPF thumbnails and other content information mixed in within the display box of the TOP page. TOP2 Application Information 112: For example, this is defined as configuring content information stored in receivers 8 and 9. TOP3 VPF-B Standalone 113: This is defined as configuring thumbnails and other content information for a single publishing operator.

[0072] Category file 120 defines the display box for category list 181. For example, it may have category 1, category 2, category 3, etc. Category file 120 defines what categories exist. For example, category file 120 defines categories such as news and sports.

[0073] Category 1 box definition file 121 defines display boxes associated with Category 1. For example, it defines a display box for a list of news templates. Category definition files are generated similarly for Category 2 and Category 3. Category 1 box definition file 121 includes Category 1-1 VPF Mixed 1211, etc. Category 1-1 VPF Mixed 1211 is defined, for example, as configuring VPF content information mixed in within the display boxes of a Category 1 page.

[0074] Figure 4 is a diagram illustrating an example of the content information file 150 in an embodiment. As shown in Figure 4, the content information file 150 displays multiple thumbnails and other content information in the display box of the definition file. The content information file 150 is generated by each of the publishing operator servers 2, 3, and 4.

[0075] For example, let's take VPF-A as an example. Content information file 150 includes a TOP content information file 151, a Category 1 content information file 152, and a content information file 153 for VPF individual pages.

[0076] The multiple content information files 150 contain images of icons and thumbnails displayed in the content display box. The multiple content information files 150 are generated according to the file format set in the content display box. For example, the file formats set in the content display box include those for banners, linear playback, VOD content, live streaming, and subpage display. Specifications regarding file formats, etc., are shown in Figures 9 to 12.

[0077] The TOP content information file 151 contains, for example, the content information used by the TOP1 display box. The content information used by the TOP1 display box is configured, for example, in the TOP box definition file 110, where TOP1 VPF is mixed in 111.

[0078] Type 1 content information file 152, for example, contains content information for Type 1-1 display boxes. The content information for Type 1-1 display boxes is configured in Type 1-1 VPF in Type 1 box definition file 121, which is mixed in with 1211.

[0079] VPF standalone pages use content information file 153, which is the content information configured in the display box of a VPF-A page. The VPF template list file and VPF content information file are configured in a VPF standalone page. This explanation uses VPF-A as an example, but the same applies to VPF-B and VPF-C.

[0080] Figure 5 is a diagram illustrating a first display example of the TOP page according to the embodiment. For example, it is a display example of a web application program (Web app) displayed on receivers 8 and 9. Specifically, it is a TOP template list 200 displayed on the TOP page.

[0081] As shown in Figure 5, the TOP template list 200 includes an item overview 210, a TOP sliding label 220, and a content area 230. The item overview 210 has multiple selection sections for migrating to various pages. By selecting a selection section in the item overview 210, one can migrate to various pages. These selection sections include, for example, a TOP selection section 211 for migrating to the TOP page, and a category selection section for migrating to categories.

[0082] The TOP slider 220 is, for example, an advertising area for content. The TOP slider 220 toggles and displays content information such as thumbnails of VPF content advertisements. The TOP slider 220 is defined by the TOP box definition file 110.

[0083] For each of the multiple templates 240 defined by the box definition file, a content area 230 is configured. The content area 230 displays the multiple templates 240 by scrolling the screen.

[0084] Template 240 is categorized, for example, into Recommendations (VPF Crossover), Recently Viewed Content, etc. Template 240 has multiple content display boxes 241, and content information such as thumbnails generated by the publishing operator for each content display box 241.

[0085] Template 240 and multiple content display boxes 241 are defined by box definition file 100. For example, in the case of template 240 being recommended (VPF traversal), multiple publishing operators are assigned to the multiple content display boxes 241 respectively. The display order (assignment) is set according to the agreements of the multiple publishing operators.

[0086] Figure 6 is a diagram illustrating a second display example of the TOP page of the implementation method. For example, it is a page displayed by scrolling the TOP page of the first display example. As shown in Figure 6, multiple templates 240 are displayed in the content area 230. For example, template 240 is Live VPF-A provided, Now-ON VPF Crossover, etc. Here, VPF Crossover means that the display order of content information such as thumbnails of multiple publishing operators displayed in the content display box is mixed.

[0087] Figure 7 is a diagram illustrating an example of a category page in an embodiment. Specifically, it is a list of templates for the category page. As shown in Figure 7, the category template list 250 includes an item overview 210 and a content area 230.

[0088] The category page is moved from other pages and displayed by selecting the category selection section 212 of the item overview 210. Multiple category pages are generated for each of the category files 120 in the box definition file 100. Here, as an example, the category 1 page is shown. The structure within the content area 230 is omitted as it is the same as the TOP page.

[0089] Figure 8 is a diagram illustrating a display example of a VPF page according to an implementation method. Specifically, it is a list of templates for a VPF page. As shown in Figure 8, the VPF template list 260 includes an item overview 210 and a content area 230.

[0090] The VPF page is migrated and displayed from other pages by selecting the operator selection section 213 in the project overview 210. Multiple VPF template lists and individual VPF pages are generated using content information file 153. Here, as an example, a VPF-A page is shown. The structure within the content area 230 is the same as the TOP page. The content area 230 is freely created according to each publishing operator.

[0091] Figure 9 is a diagram illustrating the template used in the implementation. Figure 9 is used to illustrate the program meta-specifications associated with the template. For example, as shown in Figure 9, the template represents the identifiers, descriptions, etc., of each item in the file of TOP template list 171.

[0092] For example, in the case of the TOP page, template categories are set. Additionally, content providers are set according to the display boxes for each piece of content. Specifically, within the template category items, templates are set for arranging the TOP sliding tabs and for arranging recently viewed content.

[0093] Additionally, for example, in the title, there are strings set for display according to each template category. For required / optional items, for example, required is represented by "〇" and optional is represented by "△".

[0094] Figure 10 is a diagram illustrating the content information for implementing the method. For example, as shown in Figure 10, the specifications for defining the content information are explained. For example, the template is a TOP sliding banner.

[0095] For example, in the case of the top sliding tab, the content information includes the content provider's identifier and descriptive phrases. Specifically, the content information includes identifiers for the publishing operator and TV operator. Additionally, for example, a sliding tab icon is provided for each piece of content.

[0096] Figure 11 is a diagram illustrating the content information for the implementation method. In Figure 10, the case where the template is a TOP sliding label is used as an example. In Figure 11, the case where the template is content information (contensts) is used as an example.

[0097] For example, in the case of content information, the content information may include a publishing operator identifier, content type, etc. Specifically, the content type may include linear playback, VOD, season, subpage, etc. Additionally, service identifiers and season identifiers may be set based on the content type.

[0098] Figure 12 is a diagram illustrating the subpages and category list for illustrating the implementation method. Subpages are associated with the category page folder and the VPF page folder. In the case of a category page subpage, it is configured in a specified folder within the program metadata path. In the case of a VPF page subpage, it is configured within the folder of each VPF.

[0099] In addition to the subpage information, Figure 12 also shows the category display information and the category list information. The category list information includes items for major category categories and minor category categories.

[0100] Figure 13 is a flowchart up to the point where information including the template of the implementation method is displayed. As shown in Figure 13, application server 5 requests the content it wants to display from publisher server (VPF-A) 2. VPF-A2 sends the content information of the content to be displayed to application server 5 according to the content display request (step S1).

[0101] Similar to VPF-A2, application server 5 requests the content it wants to display from publisher server (VPF-B) 3 and publisher server (VPF-C) 4. VPF-B3 and VPF-C4 send the content information of the content they want to display to application server 5.

[0102] The publishers, application server administrators, and others hold discussions, including the content each publisher wants to display and their business requirements. Application server 5 generates a template based on the discussion results (step S2). Additionally, the template includes content display boxes. VPF is configured for each content display box. That is, the display order of content information such as the publisher's thumbnail is set across multiple content display boxes.

[0103] Application server 5 outputs a template to program meta server 6. This template contains a content display box that sets the display order of content information. In addition, application server 5 outputs templates to VPF-A2, VPF-B3, and VPF-C4. This template contains a content display box that sets the display order of content information for each VPF (step S3).

[0104] VPF-A2, according to the template settings, has a VPF-A2 display box and generates VPF-A content information (program information). VPF-A2 outputs (uploads) the generated VPF-A content information to the program meta server 6 (step S4). In addition, VPF-B3 and VPF-C4 generate content information in the same way as VPF-A2 and output it to the program meta server 6.

[0105] For example, the user uses remote control 87 to launch the web application of receiver 8 (step S5). The web application generates a display screen according to a template containing a content display box.

[0106] The web application of receiver 8 requests a template containing a content display box from program meta server 6 (step S6). Program meta server 6 responds with the template containing the content display box. Thus, the web application of receiver 8 reads the template containing the content display box from program meta server 6.

[0107] The web application of receiver 8 retrieves content information from program meta server 6 according to a template including a content display box. Specifically, the web application of receiver 8 requests content information for VPF-A2 (step S7). Program meta server 6 responds with content information for VPF-A2. The same applies to VPF-B3 and VPF-C4.

[0108] Specifically, the web application operating on receiver 8 sends an HTTP GET request and receives its response, thereby obtaining the template list file and content information file configured in program meta server 6.

[0109] The web application of receiver 8 generates a display screen using templates and content information. For example, the web application of receiver 8 outputs the display screen of the TOP page and displays it to the user (step S8).

[0110] Here, VPF-A2 regenerates VPF-A content information at any time within the scope provided by the template, including the content display frame. VPF-A2 outputs the generated VPF-A content information to the program meta server 6 (step S9). Additionally, VPF-C4 generates content information in the same way as VPF-A2 and outputs it to the program meta server 6.

[0111] When the user requests a new startup request, the web application of receiver 8 generates a display screen according to a template that includes a content display box. The web application of receiver 8 outputs, for example, the display screen of the TOP page and displays it to the user (step S10).

[0112] Furthermore, the processing in receiver 8 is performed by a web application that is installed or loaded into receiver 8. The same processing occurs in receiver 9. For example, in the case of installed applications in operating systems such as iOS and Android, when actions are performed in a browser, the loaded web application performs the execution. Additionally, even on Android, it can be performed by loading a pre-installed web application.

[0113] Figures 14 to 19 are flowcharts up to the generation of the object list for displaying the TOP screen in the embodiment. Specifically, the process from the start of the web application on the receiver 8 until the generation of the object list for displaying the TOP screen is described. For example, the generation of the object list is performed in the processing unit 84 of the receiver 8.

[0114] As shown in Figure 14, the web application of receiver 8 obtains the operator list from the operator information file stored in program meta server 6 (step S21). The web application of receiver 8 obtains the channel information of each operator from program meta server 6 (step S22).

[0115] The web application of receiver 8 obtains the template list for the TOP screen from the program meta server 6 (step S23). The web application of receiver 8 obtains the content list for the TOP screen of each operator from the program meta server 6 (step S24).

[0116] The web application of receiver 8 initializes each object (step S25). The web application of receiver 8 begins the repeat (REPEAT) process (step S26). The web application of receiver 8 reads the template object (step S27).

[0117] The web application of receiver 8 is processed according to each template type (template_kind) (step S28). Each process is illustrated using Figures 15 to 19.

[0118] Figure 15 illustrates the processing of the top sliding banner. As shown in Figure 15, the web application of receiver 8 reads the providers of the template object (step S101). The web application of receiver 8 determines the data type of the provider (step S102).

[0119] If the web application of receiver 8 is an array in step S102, it begins repeat processing (step S110). The web application of receiver 8 processes the providers sequentially (step S111).

[0120] The web application of receiver 8 retrieves the object with the attribute set in template_id from the list of TOP screen content information of the operator shown by the provider (step S112).

[0121] The web application of receiver 8 reads a matching content object (step S113). The web application of receiver 8 appends the read content object to the list of objects for displaying the TOP sliding tab (step S114).

[0122] The web application of receiver 8 determines whether there is an unprocessed provider (step S115). If there is an unprocessed provider (step S115; yes), the web application of receiver 8 returns to step S110.

[0123] If there is no unprocessed provider in the web application of receiver 8 (step S115; no), the list of objects for displaying the TOP sliding tab is added to the list of objects for displaying the TOP screen (step S130).

[0124] Returning to step S102, the web application of receiver 8 retrieves the object with the attribute set in template_id from the TOP screen content information list of the operator represented by the provider (step S120).

[0125] The web application of receiver 8 generates a list of objects for displaying a TOP sliding tab (step S121). Next, proceed to step S130.

[0126] The web application of receiver 8 determines whether there is an unprocessed template object (step S131). If there is an unprocessed template object (step S131; yes), the web application of receiver 8 returns to step S26. If there is no unprocessed template object (step S131; no), the web application of receiver 8 ends the processing of the TOP sliding label.

[0127] Figure 16 illustrates the processing related to recently watched content. As shown in Figure 16, the web application of receiver 8 reads the list of played content stored within the web application (step S201). The web application of receiver 8 generates a list of objects for displaying recently watched content (step S202).

[0128] The web application of receiver 8 adds recently viewed content to the object list displayed on the TOP screen (step S203).

[0129] The web application of receiver 8 determines whether there is an unprocessed template object (step S204). If there is an unprocessed template object (step S204; yes), the web application of receiver 8 returns to step S26. If there is no unprocessed template object (step S204; no), the web application of receiver 8 ends the processing of recently viewed content.

[0130] Figure 17 illustrates the processing related to the type entries. As shown in Figure 17, the web application of receiver 8 obtains the type list file from program meta server 6 (step S301).

[0131] The web application of receiver 8 obtains the category display name, category template file name, VPF content information file name, and category image icon information from the category list file (step S302).

[0132] The web application of receiver 8 generates a list of objects for displaying category entries (step S303). The web application of receiver 8 adds the list of objects for displaying category entries to the list of objects for displaying on the TOP screen (step S304).

[0133] The web application of receiver 8 determines whether there is an unprocessed template object (step S305). If there is an unprocessed template object (step S305; yes), the web application of receiver 8 returns to step S26. If there is no unprocessed template object (step S305; no), the web application of receiver 8 ends the processing of the category entry.

[0134] Figure 18 illustrates the processing related to VPF entries. As shown in Figure 18, the web application of receiver 8 begins repeat processing (step S401). The web application of receiver 8 reads the operator information (step S402).

[0135] The web application of receiver 8 obtains the operator information name and operator icon image information from the operator information (step S403). The web application of receiver 8 receives the operator entry display object list (step S404).

[0136] The web application of receiver 8 determines whether there is any unprocessed operator information (step S405). If there is unprocessed operator information (step S405; Yes), it returns to step S401. If there is no unprocessed operator information (step S405; No), the web application of receiver 8 adds the operator entry to the object list displayed on the TOP screen (step S406).

[0137] The web application of receiver 8 determines whether there is an unprocessed template object (step S407). If there is an unprocessed template object (step S407; yes), the web application of receiver 8 returns to step S26. If there is no unprocessed template object (step S407; no), the web application of receiver 8 ends the processing of the VPF entry point.

[0138] Figure 19 illustrates the processing related to content. As shown in Figure 19, the web application of receiver 8 reads the provider of the template object (step S501). The web application of receiver 8 determines the data type of the provider (step S502).

[0139] If the web application of receiver 8 is an array in step S502, it begins repeated processing (step S510). The web application of receiver 8 processes the providers sequentially (step S511).

[0140] The web application of receiver 8 retrieves the object whose attribute is set in template_id from the list of TOP screen content information of the operator represented by the provider (step S512).

[0141] The web application of receiver 8 reads a matching content object (step S513). The web application of receiver 8 appends the read content object to the content display object list (step S514).

[0142] The web application of receiver 8 determines whether there is an unprocessed provider (step S515). If there is an unprocessed provider (step S515; yes), the web application of receiver 8 returns to step S510.

[0143] If there is no unprocessed provider in the web application of receiver 8 (step S515; no), the content of the object list for display is appended to the object list for display on the TOP screen (step S530).

[0144] Here, returning to step S502, the web application of receiver 8, in the case of a string, retrieves the object whose attribute is set to template_id from the list of TOP screen content information of the operator represented by the provider (step S520).

[0145] The web application of receiver 8 generates a list of objects for content display (step S521). Next, proceed to step S530.

[0146] The web application of receiver 8 determines whether there are any unprocessed template objects (step S531). If there are unprocessed template objects (step S531; yes), the web application of receiver 8 returns to step S26. If there are no unprocessed template objects (step S531; no), the web application of receiver 8 ends the content processing. Through the above processing, a list of objects for TOP screen display is generated.

[0147] Next, Figures 20 to 26 are flowcharts up to the generation of the view of the TOP screen in the embodiment. Specifically, the process from the generation of the object list for displaying the TOP screen by the web application of the receiver 8 until the generation of the view of the TOP screen will be described. For example, the generation of the view of the TOP screen is performed by the selection screen unit 85 of the receiver 8.

[0148] As shown in Figure 20, the web application of receiver 8 initializes the list of view objects (step S31). In order to control the focus and display area, the web application of receiver 8 hooks user operations (step S32).

[0149] The web application of receiver 8 begins repeating the process (step S33). The web application of receiver 8 reads the TOP screen display object list sequentially (step S34). The web application of receiver 8 processes each template type (template_kind) (step S35). Each process is illustrated using Figures 21 to 26.

[0150] Figure 21 illustrates the processing related to the TOP slide banner. As shown in Figure 21, the web application of receiver 8 reads the list of objects for displaying the TOP slide banner (step S601). The web application of receiver 8 then begins the repeat processing (step S602).

[0151] The web application of receiver 8 retrieves information about the displayed words and images from the list of objects for displaying the TOP sliding tab (step S603). The web application of receiver 8 creates a sub-object of the view (step S604).

[0152] The web application of receiver 8 processes each pattern (step S605). In the case of linear playback, the web application of receiver 8 obtains the specified content from the operator information and channel information (step S611). The web application of receiver 8 registers the action at the time of selection to the view (step S612).

[0153] The web application of receiver 8 appends the generated view sub-objects to the view map of the TOP sliding tab (step S650).

[0154] Returning to step S605, in the case of VOD, the web application of receiver 8 retrieves the specified content from the operator information, channel information, and video information (step S621). The web application of receiver 8 registers the action taken during selection in the view (step S622). Next, proceed to step S650.

[0155] Returning to step S605, in the case of a season, the web application of receiver 8 retrieves the specified content from the operator information, channel information, and season information (step S631). The web application of receiver 8 registers the action taken during selection in the view (step S632). Next, proceed to step S650.

[0156] Returning to step S605, in the case of VPF, the web application of receiver 8 generates operator page information based on the operator information (step S641). The web application of receiver 8 registers the action taken during selection to the view (step S642). Next, proceed to step S650.

[0157] After the addition in step S650, the web application of receiver 8 determines whether there is an unprocessed TOP slider display object (step S651). If there is an unprocessed TOP slider display object (step S651; yes), the web application of receiver 8 returns to step S602. If there is no unprocessed TOP slider display object (step S651; no), the web application of receiver 8 proceeds to step S660.

[0158] As shown in Figure 22, the web application of receiver 8 appends the created view map to the view of the TOP page (step S660). The web application of receiver 8 determines whether there is an unprocessed list of objects for displaying the TOP screen (step S661). If there is an unprocessed list of objects for displaying the TOP screen (step S661; yes), the web application of receiver 8 returns to step S33. If there is no unprocessed list of objects for displaying the TOP screen (step S661; no), the web application of receiver 8 ends the processing of the TOP sliding label.

[0159] Figure 23 illustrates the processing related to recently watched content. As shown in Figure 23, the web application of receiver 8 reads the list of objects for displaying recently watched content (step S701). The web application of receiver 8 then begins the repeat process (step S702).

[0160] The web application of receiver 8 obtains the operator information, channel information, video information, and playback position information of the matching content (step S703). The web application of receiver 8 determines whether matching content exists (step S704).

[0161] If the web application of receiver 8 has matching content (step S704; Yes), it processes the content according to each content type (step S705).

[0162] If the process in step S705 is linear, the web application of receiver 8 creates a sub-object of the view containing thumbnails, titles, etc. (step S710). The web application of receiver 8 determines whether there is any unprocessed recently viewed content (step S770). If there is unprocessed recently viewed content (step S770; yes), it returns to step S702. If there is no unprocessed recently viewed content (step S770; no), it proceeds to the processing after step S660.

[0163] Returning to step S704, if the web application of receiver 8 does not currently contain matching content (step S704; no), proceed to step S770.

[0164] Returning to step S705, in the case of a VOD, the web application of receiver 8 determines whether playback has occurred (step S720). If playback has not occurred (step S720; no), the web application of receiver 8 creates a sub-object of the view, including thumbnails, titles, playback positions, etc. (step S730). The web application of receiver 8 registers the action taken during selection in the view (step S731). Next, proceed to step S770.

[0165] Returning to step S720, if the video has already been played (step S720; Yes), the web application of receiver 8 determines whether a season is playing (step S740).

[0166] If a performance season exists (step S740; Yes), the web application of receiver 8 creates a sub-object of the view using the performance season (step S760). The web application of receiver 8 registers the action at the time of selection to the view (step S761). Next, proceed to step S770.

[0167] Returning to step S740, if there is no performance (step S740; No), the web application of receiver 8 creates a sub-object of the view using video information (step S750). The web application of receiver 8 adds a playback display (step S751).

[0168] The web application of receiver 8 registers the action taken during selection to the view (step S752). Next, proceed to step S770. After the processing in step S770, the processing of recently viewed content ends by performing the processing after step S660.

[0169] Figure 24 illustrates the processing related to the category entries. As shown in Figure 24, the web application of receiver 8 reads the category list entry display object list (step S801).

[0170] The web application of receiver 8 begins repeating the process (step S802). The web application of receiver 8 obtains the category's thumbnail and title (step S803). The web application of receiver 8 generates the page name of the migration destination (step S804).

[0171] The web application of receiver 8 creates a sub-object of the view (step S805). The web application of receiver 8 registers the action when the selection is made to the view (step S806).

[0172] The web application of receiver 8 appends the generated view sub-objects to the view map of the category entry (step S807). The web application of receiver 8 determines whether there are any unprocessed category entries (step S808). If there are unprocessed category entries (step S808; yes), return to step S802. If there are no unprocessed category entries (step S808; no), proceed with the processing after step S660 and end the processing of the category entries.

[0173] Figure 25 illustrates the processing related to the operator entries (vpf_entries). As shown in Figure 25, the web application of receiver 8 reads the list of objects for displaying the operator entries (step S901). The web application of receiver 8 then begins the repeat process (step S902).

[0174] The web application of receiver 8 obtains the operator's thumbnail and title (step S903). The web application of receiver 8 generates the page name of the migration destination (step S904).

[0175] The web application of receiver 8 creates a sub-object of the view (step S905). The web application of receiver 8 registers the action when the selection is made to the view (step S906).

[0176] The web application of receiver 8 appends the generated view sub-objects to the view map of the operator entry (step S907). The web application of receiver 8 determines whether there are any unprocessed operator entries (step S908).

[0177] If there are unprocessed carrier entries (step S908; Yes), return to step S902. If there are no unprocessed carrier entries (step S908; No), proceed with the processing after step S660 and end the processing of carrier entries.

[0178] Figure 26 illustrates the processing related to content. As shown in Figure 26, the web application of receiver 8 reads the content and displays the object list (step S1001). The web application of receiver 8 then begins the repeat processing (step S1002).

[0179] The web application of receiver 8 processes content according to each type (S1003). In the case of linear, vod, or season content, the web application of receiver 8 obtains the content's thumbnail and title, etc. (step S1010). The web application of receiver 8 creates a sub-object of the view (step S1011).

[0180] The web application of receiver 8 registers the action at the time of selection to the view (step S1012). The web application of receiver 8 appends the generated sub-objects of the view to the view map of the content (step S1013).

[0181] Returning to step S1003, if the type is a subpage, the web application of receiver 8 obtains the thumbnail and title of the subpage (step S1020). The web application of receiver 8 generates the page name of the migration destination (step S1021).

[0182] The web application of receiver 8 creates a sub-object of the view (step S1022). The web application of receiver 8 registers the action when the selection is made to the view (step S1023). The web application of receiver 8 appends the generated sub-object of the view to the view map of the content (step S1024).

[0183] After the processing in steps S1013 and S1024, the web application of receiver 8 determines whether there is any unprocessed content (step S1030). If there is unprocessed content (step S1030; yes), it returns to step S1002. If there is no unprocessed content (step S1030; no), it proceeds to the processing after step S660, ending the content processing. Through the above processing, a view of the TOP screen is generated.

[0184] The publishing system of this embodiment includes an application server and a program meta server. The application server generates a template configured with multiple content display frames, which indicate the positions where thumbnails corresponding to the content are displayed. The program meta server uses the template obtained from the application server and the content information corresponding to the content obtained from the publishing operator's server to configure the thumbnails corresponding to the content in the content display frames contained in the template and outputs them to the receiver.

[0185] This allows the system to display thumbnails corresponding to content from multiple publishers to viewers. Furthermore, multiple publishers can provide a structure that enables content to be published freely at any time. Moreover, the framework can provide a structure that can be re-evaluated based on market conditions at any time.

[0186] Furthermore, the application server of the publishing system in this embodiment sets the display order of thumbnails corresponding to the content configured in the template. This allows for setting the display order of thumbnails corresponding to the content of multiple publishing operators configured in the template. Additionally, for example, compared to setting the display order based on the registration order of the publishing operators, even publishing operators with later registration orders can be displayed first.

[0187] Furthermore, according to the publishing system of this embodiment, the publishing operator server generates content information and publishes it to the program meta server. The program meta server has a receiving unit that receives content information, converts the content information received by the receiving unit into information that can be displayed on a display unit provided by the receiver, and outputs it to the receiver. Thus, multiple pieces of content information can be generated and displayed in multiple content display frames. Additionally, thumbnails corresponding to the content can be displayed on the receiver.

[0188] Furthermore, the publishing operator server of the publishing system in this embodiment generates multiple pieces of content information based on the file format set in the content display box. Therefore, it is possible to generate content information corresponding to the file format set in the content display box.

[0189] Furthermore, according to the publishing system of this embodiment, the file formats set in the content display box include those for tags, linear playback, VOD content, live streaming, and subpage display. Therefore, content information corresponding to the file formats set in the content display box can be generated.

[0190] Furthermore, the publishing operator server of the publishing system in this embodiment sets names for multiple templates. Therefore, it is possible to set a name for each of the multiple templates.

[0191] Furthermore, the publishing operator server of the publishing system in this embodiment sets the images of icons and thumbnails displayed in multiple content display boxes. Thus, for example, by setting the size and thumbnail of each of the multiple content display boxes, content from multiple publishing operators can be displayed to the viewing user.

[0192] Furthermore, the receiver of the publishing system in this embodiment displays thumbnails corresponding to multiple contents in multiple content display boxes based on a template configured with multiple content display boxes. Therefore, the receiver can display thumbnails corresponding to multiple contents in multiple content display boxes according to the display order of the thumbnails corresponding to the contents.

[0193] The program used to implement the functions of the aforementioned distribution system 1 can also be provided as a computer-readable storage medium such as a CD-ROM, floppy disk (FD), CD-R, or DVD (Digital Versatile Disk) in a form that can be installed on a computer or as an executable file. Alternatively, the program can be configured to be stored on a computer connected to a network such as the Internet and provided by downloading it from the network. Furthermore, the program can be provided or distributed via a network such as the Internet.

[0194] The foregoing has described several embodiments of this application; however, these embodiments are shown as examples and are not intended to limit the scope of the application. These new embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the application. These embodiments or their variations are included in the scope or spirit of the application, and are included within the scope of the technical solutions described in the claims and their equivalents.

Claims

1. A publishing system, wherein, The publishing system has the following features: An application server has a template generation unit, wherein the template is configured with multiple content display boxes, which indicate the position for displaying thumbnails corresponding to the content; as well as The program meta server uses the template obtained from the application server and the content information corresponding to the content obtained from the publishing operator server that publishes the content to configure a thumbnail corresponding to the content in the content display box included in the template and output it to the receiver.

2. The publishing system according to claim 1, wherein, The application server sets and configures the display order of the thumbnails corresponding to the content in the template.

3. The publishing system according to claim 1, wherein, The publishing operator server generates the content information and publishes it to the program meta server. The program meta-server has a receiving unit that receives the generated content information. The program meta-server converts the content information received by the receiving unit in a manner that allows it to be displayed on the display unit of the receiver and outputs it to the receiver.

4. The publishing system according to claim 3, wherein, The publishing operator server generates multiple pieces of content information based on the file format set in the content display box.

5. The publishing system according to claim 4, wherein, The file formats set in the content display box include those for tags, linear playback, VOD content, live streaming, and subpage display.

6. The publishing system according to any one of claims 3 to 5, wherein, The publishing operator server sets the names of multiple templates.

7. The publishing system according to any one of claims 3 to 5, wherein, The publishing operator server sets the icons and thumbnail images displayed in multiple content display boxes.

8. The publishing system according to any one of claims 3 to 5, wherein, The receiver displays thumbnails corresponding to the multiple contents in the multiple content display boxes based on the template configured with multiple content display boxes.

9. A publishing method, which is performed by a publishing system including an application server and a program meta server, wherein, The application server generates a template configured with multiple content display boxes, each indicating the position where a thumbnail corresponding to the content will be displayed. The program meta server uses the template obtained from the application server and the content information corresponding to the content obtained from the publishing operator server that publishes the content to configure a thumbnail corresponding to the content in the content display box included in the template and output it to the receiver.

10. A non-volatile storage medium storing a program that enables a computer to function as: A generation unit generates a template configured with multiple content display boxes, each content display box indicating the position where a thumbnail corresponding to the content is displayed; and The sending unit uses the template and content information corresponding to the content to configure a thumbnail corresponding to the content in the content display box contained in the template and outputs it to the receiver.

Images