JP2016208461A - Processor, program and data structure - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a processor which improves interoperability of contents relating to an application program that is provided in a digital broadcast service, a program and a data structure.SOLUTION: In an application package, a content route folder in which a content file relating to the application program of the digital broadcast service is disposed and package entry point metadata including content information indicating an entry point of the application program are disposed. A metadata analysis part 323 identifies the application program by analyzing the package entry point metadata from the application package, and a content structure analysis part 324 extracts the content file relating to the application program from the content route folder by analyzing structures of folders following the content route folder.SELECTED DRAWING: Figure 7

Description

  The present invention relates to a processing device, a program, and a data structure.

  The present invention relates to a packaging method and format for collectively handling content files related to an application program (hereinafter referred to as an application) distributed using a broadcast transmission path or a communication transmission path. This format is common for project management in the application development environment for broadcasting / communication cooperation services, material exchange between broadcasting stations and producers, and supply to transmitters that transmit various types of content files to broadcast waves and communication transmission paths. Used as a format.

  In the first generation terrestrial digital broadcasting / BS (Broadcasting Satellite) digital broadcasting / CS (Communication Satellite) digital broadcasting, content is described using BML (Broadcast Markup Language) which is a content description language. BML is a content description language dedicated to data broadcasting services defined in Non-Patent Document 1. Non-Patent Document 1 describes a description method of content by BML and a data structure for multiplexing and transmitting content described by BML using MPEG-2 TS (Transport Stream). However, when BML is defined, a packaging method for collectively handling content file groups described using BML has not been defined. Since the input format for material exchange between program producers and broadcast stations, or between broadcast stations, and the input format for transmission programs for transmitting content via broadcast waves are different, ensuring interoperability is an issue. Met.

Therefore, BCML (Broadcast Content Markup Language), which is a description language for content physical structure and meta information described in Non-Patent Document 2, has been defined. The physical structure of content means a hierarchical structure of folders and an arrangement method of a content file group in which the content is stored. This improved interoperability in the operation of data broadcasting services.
However, when providing a service, the physical structure of the content described in Non-Patent Document 2 needs to correspond to the data structure (for example, carousel, module, etc.) at the time of transmission of the content specified in Non-Patent Document 1. . Therefore, when describing content using BML and when describing meta information of content using BCML, the content creator is required to understand various requirements. Various requirements include, for example, differences in language specifications from HTML (Hypertext Markup Language), which is widely used as a description language for web pages posted on the Internet, need for understanding of transmission methods, and freedom of content structure. The need for a dedicated development environment, etc. Therefore, the spread of the production environment for data broadcasting contents described using BML and BCML and the securing of human resources with technology have been hindered.

  On the other hand, HTML5, which is an extension of the conventional HTML specification, has been established as a description language for web pages provided via the Internet. In HTML5, various media such as video, audio, 2D (2-Dimensional) / 3D graphics, etc. can be handled with a higher degree of freedom than conventional HTML. In response to this movement, a method of using HTML5 as a description language for data broadcasting contents has been developed (see Non-Patent Document 3). As of March 2015, a broadcasting / communication cooperation service (Hybrid Cast (registered trademark)) that uses an HTML5 application that complies with the specifications defined in Non-Patent Document 3 as part of the additional services of the first generation digital broadcasting service. Has already been put to practical use.

  In the broadcasting / communication cooperation service that has been put to practical use, the control information necessary for the receiver to acquire the application is multiplexed with MPEG-2 TS and then transmitted by broadcast waves, and the content file group is connected to the Internet. Distributed via a web server. However, transmission of content files for HTML5 applications by broadcast waves has not been put into practical use as of March 2015 due to reasons such as operation guarantees of existing receivers and restrictions on transmission bandwidth.

  In parallel with the adoption of HTML5 applications in broadcasting services, standardization of second generation digital broadcasting is underway. For example, Non-Patent Document 4 defines a digital broadcast multiplexing system using MPEG-H MMT (MPEG Media Transport, also simply referred to as MMT). Even when adopting MPEG-2 TS as a transmission system for second-generation digital broadcasting, if it is allowed not to guarantee the operation of an existing receiver, transmission of content files of an HTML5 application by broadcast waves in a broadcasting / communication cooperation service May be put to practical use. By using a broadcast wave in addition to a communication transmission line, transmission is expected to reduce the access load to the web server and to acquire and execute an application by a receiver not connected to the communication transmission line.

Radio Industry Association, Data Broadcast Coding System and Transmission System in Digital Broadcasting, ARIB STD-B24 6.1 Edition, 2014.12.16 Radio Industry Association, Data Broadcast Program Exchange Method for Digital Broadcasting, ARIB STD-B35 1.2 Edition, 2006.3.14 IPTV Forum, HTML5 Browser Specification, IPTVFJ STD-0011 2.0 Edition, 2014.4.629 Radio Industry Association, Media Transport System by MMT in Digital Broadcasting, STD-B60 1.1 Edition, 2014.12.16 “.ZIP File Format Specification”, [online], PKWARE Inc. [Search February 20, 2015], Internet <https: // pkware. cachefly. net / webdocs / APPNOTE / APPNOTE-6.3.3. TXT> Society of Motion Picture and Television Engineers, The MXF File Format Specification (the overall master document), SMPTE 377M Internet Engineering Task Force, FILE TRANSFER PROTOCOL (FTP), Request for Comments 959, 1985.10.

  As of March 2015, in the broadcasting / communication cooperation service in practical use, the HTML5 application is transmitted only through the communication transmission path. The service provider may upload the content file group as it is to one or a plurality of web servers at the time of transmission. For this reason, the internal structure of the content file group and the description method of the meta information are not stipulated, and the interoperability is not immediately impaired even if the folder serving as the base of the content is simply compressed (for example, Non-Patent Document 5). . However, in the future, the transmission path will be diversified due to the expansion of the service scale and the practical application of broadcast wave transmission of applications in the second generation digital broadcasting service. However, if content creators and service providers operate individually, Interoperability may be impaired. In interoperability, in a relatively simple operation, such as when handling content file groups all together, convenience is ensured even if the file is configured as a ZIP format file described in Non-Patent Document 5. On the other hand, interoperability with MXF (Material eXchange Format) described in Non-Patent Document 6 is expected in order to ensure the compatibility of content file group transmission in file units and the program archive system.

  The present invention has been made in view of the above points, and an object of the present invention is to provide a processing device, a program, and a data structure that can improve the interoperability of contents related to an application program provided by a digital broadcasting service. In addition to a static HTML5 application whose content file group does not change over time, the transmission of an application whose content file group to be transmitted dynamically changes over time, or the operation verification thereof is realized. . Further, interoperability between the content file group configured as a ZIP file and the content file group configured as an MXF file is ensured.

The present invention has been made to solve the above problems. [1] One aspect of the present invention is a content root folder in which a content file related to an application program of a digital broadcasting service is arranged, and an entry of the application program. A metadata analysis unit that analyzes the package entry point metadata and identifies the application program from an application package in which package entry point metadata including content information indicating points is arranged, and a folder under the content root folder And a content structure analysis unit that extracts a content file related to the application program from the content root folder.
According to the configuration of [1], the location of the entry point referred to first in the application program is immediately identified with reference to the package entry metadata. Since content files arbitrarily configured by the producer are efficiently extracted as processing targets, interoperability is improved by specifying a common processing target between the producer and the broadcaster or service provider.

[2] One aspect of the present invention is the above-described processing device, wherein the content structure analysis unit analyzes a file name of the content file and indicates a time indicated by the file name and a location of the content file. A control target file list is generated, and a file control unit that selects a content file having a file name indicating a time corresponding to a program organization time with reference to the control target file list.
According to the configuration of [2], for the content whose content file is updated as time elapses, the processing start time and the processing target file are immediately specified by the file name when the program is organized. The producer can efficiently verify the start and time of the process, and the broadcaster or service provider can smoothly organize the program based on the process start time intended by the producer.

[3] One aspect of the present invention is the processing apparatus described above, wherein the file control unit relates to the content file at a time indicated by a file name of the selected file when the selected content file is an empty file. The processing is stopped.
According to the configuration of [3], the stop time and the file to be stopped are immediately specified by the file name for the content to be stopped when the program is organized. The producer can efficiently verify the process stop and the time, and the broadcaster or the service provider can smoothly organize the program based on the process stop time intended by the producer.

[4] One aspect of the present invention is the processing apparatus described above, wherein a set including a folder in which the content file is arranged, a header indicating identification information, and data stored in the content file is between content files. And a developing unit that arranges the content file storing the data for each set in the folder indicated by the header from the files of the first format concatenated in (3) and develops them as the application package.
According to the configuration of [4], the content file to be processed is specified at the time of program organization from the application package reproduced by development from the first format file. It is possible to use a file of the first format convenient for batch handling in program organization.

[5] One aspect of the present invention is the above-described processing device, wherein each of the pieces of division data is obtained from a file of a second format in which division data indicating the arrangement of the set is further arranged at the head of each of the sets. A first conversion unit that excludes and converts the file into the first format file is provided.
According to the configuration of [5], conversion of the second format file into the first format file can be realized by a simple process such as exclusion of segmented data. The second format file that allows easy access to the individual content files based on the classification data can be converted into the first format file to facilitate batch handling.

[6] One aspect of the present invention is the above-described processing device, wherein a file of the second format is arranged by arranging division data indicating the arrangement of the set at the head of each of the sets included in the first format. The 2nd conversion part which converts into 2 is provided.
According to the configuration of [6], conversion from the first format file to the second format file can be realized by a simple process such as arrangement of segmented data. Therefore, the first format file convenient for batch handling can be converted to the second format file to facilitate access to individual content files, so that content creation and editing can be performed efficiently. it can.

[7] One aspect of the present invention is the above-described processing device, wherein the package entry point metadata includes transmission information indicating a transmission method of the content file, and uses the transmission method indicated by the transmission information. A transmission control unit for transmitting the content file is provided.
According to the configuration of [7], a content file arbitrarily configured by the producer is efficiently extracted as a transmission target, and transmitted using a desired transmission method designated by the broadcaster or service provider. Therefore, in providing a digital broadcast service, interoperability between the producer and the broadcaster or service provider is improved.

[8] One aspect of the present invention is the above-described processing device, which includes an execution unit that executes a process indicated by an instruction described in the application program.
According to the configuration of [8], content files arbitrarily configured by the producer are efficiently extracted as processing targets, so that the operation verification of the application program arranged in the produced application package can be performed smoothly. it can.

[9] According to one aspect of the present invention, a package entry point meta including a content root folder in which a content file related to an application program of a digital broadcasting service is placed on a computer of a processing device and content information indicating an entry point of the application program. Content related to the application program by analyzing the package entry point metadata from the application package in which the data is arranged to identify the application program and analyzing the structure of the folder under the content root folder A program for executing a content structure analysis procedure for extracting a file from the content root folder.
According to the configuration of [9], the location of the entry point referred to first in the application program is immediately identified with reference to the package entry metadata. Since content files arbitrarily configured by the producer can be efficiently extracted as processing targets, interoperability between the producer and the broadcaster or service provider is improved.

[10] One aspect of the present invention includes a content root folder and a package root folder in which package entry point metadata including content information indicating an entry point of an application program of a digital broadcasting service is arranged, and the content root folder is below the content root folder The data structure of the application package is characterized in that the application program file is arranged in the folder.
According to the configuration of [10], the location of the entry point referred to at the beginning of the application program is immediately identified by referring to the package entry metadata. Therefore, the content file arbitrarily configured by the creator is the processing target. Extracted efficiently. Interoperability is improved because the producer and the broadcaster or service provider can smoothly specify the processing target using a common data structure.

[11] One aspect of the present invention is the data structure described above, wherein a content file related to the application program is arranged in a folder below the content root folder, and at least one file name of the content file is the content file It includes a time code indicating the processing start time.
According to the configuration of [11], for the content whose content file is updated as time elapses, the processing start time and the processing target file are immediately specified by the file name when the program is organized. The producer can efficiently verify the start and time of the process, and the broadcaster or service provider can smoothly organize the program based on the process start time intended by the producer.

[12] One aspect of the present invention is the data structure described above, wherein an empty file whose file name includes a time code indicating at least one processing stop time of the content file is arranged in a folder below the content root folder It is characterized by being.
According to the configuration of [12], the stop time and the file to be stopped are immediately specified by the file name for the content to be stopped when the program is organized. The producer can efficiently verify the process stop and the time, and the broadcaster or the service provider can smoothly organize the program based on the process stop time intended by the producer.

[13] One aspect of the present invention is the above-described data structure, wherein a set including a folder in which a content file related to the application program is arranged, a header indicating identification information, and data stored in the content file. It is characterized by being configured as one file concatenated between content files.
According to the configuration of [13], an application package including various content files is represented as one file, so that the application package can be easily handled in a batch.

[14] One aspect of the present invention is the data structure described above, characterized in that segment data indicating the arrangement of the set is arranged at the head of each of the sets.
According to the configuration [14], it is convenient for editing and managing the contents of the individual content files by detecting the presence of the individual content files constituting the application package based on the division data.

[15] One aspect of the present invention is characterized in that the package entry point metadata includes transmission information indicating a transmission method of a content file related to the application program.
According to the configuration of [15], a content file arbitrarily configured by a producer is efficiently specified as a transmission target, and a broadcaster or a service provider specifies a desired transmission method for transmitting the specified content file can do. Therefore, interoperability between the producer and the broadcaster or service provider is improved in providing the digital broadcast service.

  ADVANTAGE OF THE INVENTION According to this invention, the interoperability of the content regarding the application program provided with a digital broadcast service can be improved.

It is a schematic block diagram which shows the structure of the broadcast communication cooperation system which concerns on this embodiment. It is a figure which shows the data structure of the application package which concerns on this embodiment. It is a figure which shows an example of the structure of the content in a content folder. It is a figure which shows an example of the time change of a transmission object file. It is a figure which shows the other example of the structure of the content in a content folder. It is a figure which shows an example of the time change of a transmission object file. It is a schematic block diagram which shows the structure of the application transmitter which concerns on this embodiment. It is a figure which shows the example of a content file group. It is a flowchart which shows the package reading process which concerns on this embodiment. It is a figure which shows the example of a time code control object file list. It is a flowchart which shows the file control process which concerns on this embodiment. It is a flowchart which shows the transmission control process which concerns on this embodiment. It is a schematic block diagram which shows the structure of the application operation verification apparatus which concerns on this embodiment. It is a figure which shows the example of a data structure of the application package of each format. It is a flowchart which shows the ZIP-MXF conversion which concerns on this embodiment. It is a flowchart which shows MXF-ZIP conversion based on this embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a schematic block diagram showing the configuration of the broadcasting / communication cooperation system B1 according to the present embodiment.
The broadcast communication cooperation system B1 according to the present embodiment includes a content management device 10, a content transmission device 20, an application transmission device 30, an encoding device 40, a multiplexing device 50, a server device 60, a broadcast facility 70, a receiver 80, and an application. The operation verification device 90 and the router device 100 are included.

  The content management apparatus 10 includes a storage medium that stores a content package for each program. Each content package is a file group storing one or more multimedia data as program components. The multimedia data refers to data broadcast as a program, that is, data such as video, audio, subtitles, applications, and other information. An application is a program that is described in a description language, for example, HTML5, and that realizes a broadcasting / communication cooperation service by causing the receiver 80 to execute a process indicated by the described instruction. Multimedia data to be presented. The content provided by the broadcasting / communication cooperation service may be particularly referred to as broadcasting / communication cooperation content. In the following description, executing the process indicated by the instruction described in the application or other program may be simply referred to as “execution” of the application or other program. When a content package includes only files related to an application among program components, the content package may be simply referred to as an application package. When a content package includes video, audio, subtitles, and other data in addition to the files that make up the application, the content package may be referred to as containing the application package. The content management device 10 is, for example, a program archive device that stores a plurality of content packages. The content management apparatus 10 is managed mainly by a broadcaster and a program producer. Further, the file group constituting the content package may be packaged in a format such as MXF or ZIP, for example.

  When the content reading trigger and the content package name information of the program to be broadcast are input, the content transmission device 20 acquires the content package specified by the package name information from the content management device 10. The content reading trigger is input from a program organization information management apparatus (not shown) which is a host system that manages program organization information. The program organization information includes a package name of a content package related to a broadcast program, organization time information of the program, application organization information of an application executed during the broadcast of the program, and the like. The content transmission apparatus 20 reads the multimedia data stored in the acquired content package, and outputs the read multimedia data to the encoding apparatus 40. Further, the content transmission device 20 reads the content package or the application package included in the content package, and outputs the read application package to the application transmission device 30.

  The application transmission device 30 acquires an application package from the content transmission device 20. The application transmission device 30 receives a package reading trigger and application package name information directly from a program organization information management device (not shown) or indirectly through the content transmission device 20. The application transmitting device 30 expands the application package specified by the package name information and generates a file group related to the application. The application transmission device 30 generates control information for controlling the operation of the application. The control information includes, for example, an application information table (AIT: Application Information Table). The AIT is data indicating control of operations such as activation and termination of an application by the receiver 80, authority of functions such as whether or not to change a broadcast video display layout, an application acquisition destination, an acquisition route, and the like. The application transmission device 30 transmits a content file group and control information regarding the developed application to the multiplexing device 50 or the server device 60.

  The encoding device 40 encodes the multimedia data received from the content transmission device 20 by a predetermined encoding method corresponding to each medium. The video encoding method is, for example, ISO / IEC 23008-2 HEVC (International Organization for Standardization / International Electrical Commission 23003, also referred to as Part 2 High Efficient Video Coding, E coding method). The audio encoding system is an encoding system standardized by, for example, ISO / IEC 14496-3 Audio (also referred to as MPEG-4 audio). The encoding device 40 transmits the encoded multimedia data to the multiplexing device 50. If the multimedia data stored in the content package is encoded data that can be processed by the multiplexing device 50 as it is, the encoding device 40 may be omitted.

  The multiplexing device 50 multiplexes the encoded multimedia data received from the encoding device 40, the control information and the content file group received from the application transmission device 30, and generates multiplexed data in a predetermined format. The multiplexed data is configured as an IP flow made up of a plurality of IP packets including, for example, an MMTP (MPEG Media Transport Protocol) packet. The MMTP packet includes an MMT package table (MPT: MMT Package Table). The MPT is control information indicating one or a plurality of multimedia data that is a component of a broadcast program, that is, a list of video, audio, subtitles, applications, other information, and the like and requirements thereof. The multiplexing device 50 transmits the generated multiplexed data to the router device 100 or the broadcasting facility 70.

The server device 60 receives the content file group and the control information file related to the application from the application transmitting device 30, and stores the received file. The server device 60 transmits a file specified by the request information received from the receiver 80 to the receiver 80 via the communication transmission path NT as a response.
In addition, the router device 100 transmits the multiplexed data received from the multiplexing device 50 to the receiver 80 via the communication transmission path NT. The router device 100 may be omitted when it is not necessary to transmit multiplexed data via the communication transmission line NT.
The communication transmission line NT is a transmission line for bidirectionally transmitting various data between the server device 60 or the router device 100 and the receiver 80. The communication transmission line NT includes, for example, a wide area communication network such as the Internet or a public wireless communication network. Note that transmitting (or transmitting or receiving) various data via the communication transmission line NT may be referred to as “transmitting (or transmitting or receiving) by communication”.

The broadcast facility 70 transmits the multiplexed data received from the multiplexing device 50 to the receiver 80 via the broadcast transmission path BT.
The broadcast transmission path BT is a transmission path for simultaneously transmitting data transmitted from the broadcast facility 70 to an unspecified number of receivers 80 in one direction. The broadcast transmission path BT is, for example, a radio wave (broadcast wave) in a predetermined frequency band that is relayed by a broadcast satellite. The broadcast transmission path BT may include a network from the broadcast facility 70 to a transmission station for transmitting radio waves. Note that transmission (or transmission, reception) of various types of data via the broadcast transmission path BT may be referred to as “transmission (or transmission, reception) by broadcast”.

The receiver 80 provides a broadcasting / communication cooperation service based on multiplexed data transmitted through the broadcasting transmission path BT or the communication transmission path NT and a content file group received via the communication transmission path NT. The receiver 80 extracts MPT from the multiplexed data received by the broadcast transmission path BT, and extracts the multimedia data, control information, and content file group specified by the MPT from the received multiplexed data. The receiver 80 presents content based on the multimedia data according to the requirements specified by the MPT. Further, the receiver 80 transmits the request information of the application file specified by the control information to the request destination server device 60 specified by the extracted control information via the communication transmission line NT. The receiver 80 receives a content file group related to the application as a response. The receiver 80 executes the application transmitted by the content file group received via the broadcast transmission path BT or the communication transmission path NT and presents the content. The receiver 80 may change the display layout of the content so that the display areas of the content do not overlap each other when permission to change the display layout is instructed by the control information.
Accordingly, various broadcasting services are configured by the broadcasting / communication linking service by contents provided by execution of an application transmitted by broadcasting or communication, and contents transmitted by broadcasting or communication.

  The application operation verification device 90 acquires an application package created by the creator, and expands an application file arranged in the acquired application package. The application operation verification device 90 verifies the operation by executing the application at the time specified by the input application composition information. An application package storing a content file group related to an application whose operation verification has been completed by the application operation verification apparatus 90 may be provided as a part of program material.

  In the example shown in FIG. 1, the number of receivers 80 is one, but in general, there are a plurality. In the example illustrated in FIG. 1, the number of server devices 60 is one, but may be plural. Moreover, all or part of the broadcasting / communication cooperation system B1 may be implemented by other contractors in addition to being implemented by the broadcaster. For example, the content management device 10 and the application operation verification device 90 can be implemented by a content creator (hereinafter referred to as a producer). Further, the application transmission device 30, the server device 60, and the router device 100 can be implemented by a service provider that is separate from the broadcaster. The receiver 80 is arranged at each home or business office mainly for the purpose of viewing a program.

(Application package data structure)
Next, the data structure (physical structure) of the application package according to the present embodiment will be described.
FIG. 2 is a diagram illustrating a data structure of the application package according to the present embodiment.
The application package according to the present embodiment has a package root folder as a base folder. The package root folder is given a folder name for specifying the folder. An arbitrary name that can be identified by a human can be set as the folder name of the package root folder. As the package root folder, a name of an application stored in the folder, an abbreviation, an alias, a version number, or a folder name having a name including these may be attached. Package entry metadata, content root folder, event message folder, and document folder are arranged in the package root folder.

  Package entry metadata is data in which information related to an application stored in an application package is described in a predetermined description language. In the description language, for example, a description method of information related to broadcasting / communication cooperation content can be defined based on XML (extensible Markup Language). The extended language specification is called, for example, HCML (Hybridcast Content Markup Language). The information described in the package entry metadata includes, as the location of the application to be stored, content information indicating the file name of the file serving as the entry point (application entry point), package information indicating the structure of the application package, etc. It includes transmission information indicating an application transmission method and control of the application in the receiver 80 as a transmission destination.

  The file name of the application entry point indicated by the content information may be specified using a file path indicating a folder in which the file is arranged. The entry point means a file that is first executed or referred to by a browser or the like that is an execution environment of the application among a group of files related to the application. The content information may include attribute information such as an application name, a program name, a broadcasting station name, and a producer name of the application. In the transmission information, for example, MMTP (MMT Protocol) and FTP (File Transfer Protocol) are specified as a transmission protocol that is one element of the transmission method. As a transmission path which is another element of the transmission method, for example, the broadcast transmission path BT or the communication transmission path NT, and the IP address and port number of the server apparatus 60 and the router apparatus 100 which are the starting points are designated. In addition, as folder hierarchy information at the time of transmission, which is another element of the transmission method, for example, a folder name that is the starting point of an application is specified in a folder structure used for transmission by MMTP or a folder structure of a transfer destination by FTP. When FTP is used, the transmission information may include information relating to file and folder permission settings in the server device 60. The designation of the transmission method may be made for the entire application package, may be made for each partial file group included in the application package, or may be made for each file. As control of the application, for example, whether to start, stop, or change the display layout is specified. Package information specifies the folder name of the content root folder, the presence / absence of the event message folder, the folder name of the event message folder, the presence / absence of the document folder, the folder name of the document folder, and the content configuration information of the content stored in the content root folder May be. The content configuration information includes, for example, a file path of a file in which the content data is stored. Each file path indicates a file name of each file and a folder name in which the file is arranged, and the hierarchical structure of the content folder of the content is represented by the entire file path. These files correspond to the content file group described above. The name of the package entry metadata may be predetermined as a predetermined name, for example, “package_entry.hcml”. The extension “hcml” indicates a metadata file described in HCML.

  The content root folder is a base folder in which content file groups are stored. The stored content file group includes an application file including a designated application entry point and a content file (content file) referred to by the application stored in the file. The referenced content may include a part of an application different from the application entry point, for example, a subprogram. Note that the application entry point file does not necessarily have to be placed in the content root folder, and may be placed in a folder lower than the content root folder. In the example shown in FIG. 2, the file of the application entry point is placed in the content root folder, and the file name is “index.html”. The extension “html” indicates that the application is described in HTML5. The content root folder contains a content file group having a physical structure uniquely defined by an application creator. As a physical structure, a folder in which each content file storing the content is arranged, and a hierarchical structure of these folders are defined. That is, the creator can arbitrarily specify the physical structure of the content file group arranged in the content root folder using the content configuration information. If the folder name of the content root folder is not specified in the package entry metadata, a default folder name (for example, “contents”) may be used. In the following description, a folder below the content root folder is called a content folder.

  The event message folder is a folder in which files related to the contents of event messages and files related to control information related to event messages such as transmission timing thereof are arranged. When the folder name of the event message folder is not specified in the package entry metadata, a default folder name (for example, “event_messages”) may be used.

  The document folder is a folder in which arbitrary files (excluding the application main body) related to the application such as application specifications and explanatory texts are arranged. A file placed in the document folder is a file that is not a transmission target. If the folder name of the document folder is not specified in the package entry metadata, a default folder name (eg, “documents”) may be used.

When the event message is not used, the event message folder may be omitted. If there is no file to be placed in the document folder, the document folder may be omitted.
Each application package may be configured as a single data file indicating the data structure described above. The data format of such an application package is, for example, a ZIP file (ZIP file) or an MXF file (MXF file). The ZIP file and MXF file are archive files that include entity data (file data) and metadata stored in one or more individual files, and are integrally configured in a predetermined format.

(Example of content structure)
Next, an example of the structure of content arranged in the content folder will be described.
FIG. 3 is a diagram illustrating an example of the structure of content in the content folder.
The example shown in FIG. 3 is an example of a file storing program-linked content data organized in conjunction with a program frame whose broadcast time is 30 minutes in the broadcast communication cooperation service. These files are placed in the “data” folder in the content root folder, and are referenced by executing the application during broadcasting. The four files shown in FIG. 3 are sequentially controlled to be replaced as the program progresses. A file whose file name is “text.json” is a file (initial file) provided from the program organization start time. The file name of the original file may be referred to as the original file name in the following description. The file whose file name is “00-12-34_text.json” is a replacement file that is replaced from the original file at 12 minutes 34 seconds after the program starts. The file name of the replacement file includes an organization time code “00-12-34” composed of alphanumeric characters, an underscore “_”, and an original file name “text.json” in that order. The organization time code “00-12-34” indicates that the time when the file is replaced from the organization start time of the program is 12 minutes 34 seconds. The original file to be replaced is specified by the original file name “text.json” included in the file name of the replacement file. When the file name includes the organization time code, it is specified that the file having the file name is a replacement file. Note that a replacement file including a time code in the file name in the application package is also transmitted as a file with the original file name excluding the time code and the underbar when transmitted from the application transmission device 30.

  Therefore, as shown in FIG. 4, the application transmitting apparatus 30, when a composition time code after “00-00-00” and before “00-12-34” is designated, “text.json” is transmitted as a transmission target file. The application transmission device 30 replaces the transmission target file with the file “00-12-34_text.json” from the initial file 12 minutes and 34 seconds after the program starts. When the knitting time code after “00-12-34” and before “00-22-57” is designated, the replacement file “00-12-34_text.json” is transmitted. The application transmitting apparatus 30 replaces the transmission target file with the file “00-22-57_text.json” from the file “00-12-34_text.json” 22 minutes 57 seconds after the program starts. When the knitting time code after “00-22-57” and before “00-28-11” is designated, the replacement file “00-22-57_text.json” is transmitted. The application transmission device 30 replaces the transmission target file with the file “00-28-11_text.json” from the file “00-22-57_text.json” 28 minutes and 11 seconds after the program starts. When the knitting time code after “00-28-11” and before “00-30-00” is designated, the replacement file “00-28-11_text.json” is transmitted.

FIG. 5 is a diagram illustrating another example of the structure of content in the content folder.
The example shown in FIG. 5 is another example of a file that stores data of program-linked content organized in conjunction with a program frame whose broadcast time is 30 minutes in the broadcast communication cooperation service. These files are placed in the “images” folder in the content root folder, and the necessity of reference from the application by the broadcast signal is controlled. Of the four files shown in FIG. 4, the file whose file name is “logo.jpeg” is the initial file. The file whose file name is “00-08-43_logo.jpeg” is a file (transmission stop file) instructing to stop transmission of the initial file or the replacement file. The file name of the transmission stop file includes the organization time code “00-08-43” consisting of single-byte alphanumeric characters, the underscore “_”, and the original file name “logo.jpeg” in the same order as the replacement file. Consists of. However, the transmission stop file is specified by being an empty file in which the data amount (file size) of the entity data to be stored is 0 bytes. The transmission stop time is designated by the time indicated by the composition time code. The replacement file specified as the stop target file for stopping transmission is the organization time indicating the last time among the original file name included in the file name of the transmission stop file and the time before the transmission stop time. A file having a file name including a code. If no such file exists, the initial file is designated as a transmission stop file.

  On the other hand, the file whose file name is “00-15-41_logo.jpeg” is a file (transmission resume file) instructing to resume file transmission. The transmission restart file is a file having actual data like the replacement target file, and the file name is composed time code “00-15-41” consisting of alphanumeric characters, underscore “_”, and original file name. It includes “logo.jpeg” in that order. The transmission restart time is specified by the time indicated by the composition time code. Of the files having the file name including the organization time code indicating the time after the transmission stop time, the file having the file name including the organization time code indicating the earliest time is identified as the transmission resume file.

Therefore, as shown in FIG. 6, the application transmitting apparatus 30, when a composition time code after “00-00-00” and before “00-08-34” is designated, log.jpeg ". The application transmitting device 30 stops transmitting the initial file “logo.jpeg” at 8 minutes 43 seconds after the program starts. Therefore, when the knitting time code after “00-08-43” and before “00-15-41” is instructed, the file is not transmitted. The application transmitting apparatus 30 starts transmitting the file “00-15-41_logo.jpeg” 15 minutes and 41 seconds after the program starts. Therefore, when the composition time code after “00-15-41” and before “00-25-16” is designated, the transmission resumption file “00-15-41_logo.jpeg” is transmitted. . The application transmitting device 30 stops transmitting the transmission resumption file “00-15-41_logo.jpeg” 25 minutes and 16 seconds after the program starts. Therefore, when a composition time code after “00-25-16” is instructed, the file is not transmitted.
The initial file is a file that includes “00-00-00” indicating an organization start time as an organization time code, an underscore “_”, and an original file name (for example, “text.json”) in that order. You may have a name. Also, the organization time code in the file name of the replacement file, transmission stop file or transmission restart file is higher, for example, “00-12-34.200-text.json” (.200 indicates 200 milliseconds). It may represent the accuracy of time.

(Configuration of application transmitter)
Next, the configuration of the application transmission device 30 according to the present embodiment will be described.
FIG. 7 is a schematic block diagram illustrating a configuration of the application transmission device 30 according to the present embodiment.
The application transmission device 30 includes a package storage unit 31, a control unit 32, an external file update unit 33, a temporary folder 34, and a transmission unit 35. The application transmission device 30 may be a dedicated device, or may be configured by executing a process indicated by a command described in a predetermined transmission control program in a general-purpose server device. One or a plurality of functional blocks may be distributed among a plurality of dedicated devices or server devices.

  The package storage unit 31 stores the application package input from the content transmission device 20. The package storage unit 31 includes, for example, a hard disk drive (HDD: Hard-disk Drive). In the example described below, a case where an application package is configured as a ZIP file is taken as an example.

  The control unit 32 includes a control device (not shown) such as a central processing unit (CPU) and a storage medium, and a process indicated by a command described in a predetermined transmission program read from the storage medium. As a result, the package development unit 321, the development package storage unit 322, the metadata analysis unit 323, the content structure analysis unit 324, the file control unit 326, the control information generation unit 328, and the transmission control unit 329 function. The storage medium includes, for example, an SRAM (Static Random Access Memory), a flash ROM (Read-only Memory), a hard disk drive (HDD: Hard-disk Drive), and the like. The function of the control unit 32 will be described later.

  The external file update unit 33 generates a content file for storing real-time content for each provision unit based on received data from an external system (not shown). Real-time content is content that is updated in real time by an information provider. The real-time content includes, for example, current affairs information (news), weather information, market price information such as stock prices and exchange rates, and the like, and may include information provided from information providers other than broadcasters. The external file update unit 33 updates the content file of the same type of real-time content by storing the generated content file in the temporary folder 34. Thereby, the content file of the real-time content referred by execution of an application is updated.

  The temporary folder 34 is a storage unit that temporarily stores a transmission target file. The temporary folder 34 may be a storage area that is separate from the storage area of the storage medium used by the control unit 32. The temporary folder 34 may be accessible from the external system via the external file update unit 33 using a predetermined transmission protocol (for example, NFS: Network File System, HTTP: Hypertext Transfer Protocol, FTP, etc.).

  The transmission unit 35 transmits various files stored in the temporary folder to the server device 60 or the multiplexing device 50. The transmission target file, transmission time, transmission method, and the like are controlled by the control unit 32.

Next, functions of the control unit 32 will be described. The package development unit 321 reads the application package indicated by the application package name information from the package storage unit 31 when a package read trigger and application package name information are input from a program organization information management device (not shown) which is an external system. . Note that the application transmission device 30 does not include the package storage unit 31 and acquires a package directly from the storage area of the content management device 10 (FIG. 1) or via the content transmission device 20 via a network or the like. May be. The application name information may include a file path indicating a file in which the application package is stored. The application organization information managed by the program organization information management apparatus includes application organization time information and application package name information. The organization time information includes information related to the organization of the application in the program, such as the organization start time and the organization end time. The program organization information management device outputs a package read trigger and application package name information set to the application transmission device 30 at least earlier than the time (processing delay) required for processing by the application transmission device 30 than the organization start time. . The package expansion unit 321 expands an application package configured as a ZIP file. The expanded application package has the plurality of folders described above, and individual files (local files) obtained by the expansion are arranged in a folder designated by a local file header (described later) included in the ZIP file. . The package expanding unit 321 stores the expanded application package in the expanded package storage unit 322. The package reading process will be described later.
The expanded package storage unit 322 is a storage unit that stores the expanded application package. Part of the storage area of the storage medium described above is used for the expanded package storage unit 322.

  The metadata analysis unit 323 reads package entry metadata from the expanded package storage unit 322 and analyzes the read package entry metadata. When the folder name of the content root folder is specified in the package entry metadata, the metadata analysis unit 323 specifies the folder having the specified folder name as the content root folder. When the folder name of the content root folder is not specified, the metadata analysis unit 323 specifies a folder having the default folder name “contents” as the content root folder (see FIG. 8A). The metadata analysis unit 323 analyzes the description in the package entry metadata, and outputs the content information to the content structure analysis unit 324 and the transmission information to the control information generation unit 328 and the transmission control unit 329.

  The content structure analysis unit 324 analyzes the content structure in the content folder that is a hierarchy below the content root folder based on the content information described in the package entry metadata input from the metadata analysis unit 323 and the package information. . First, the content structure analysis unit 324 detects an application file serving as an application entry point designated by the content information of the package entry metadata as a transmission target file (see FIG. 8A). The content structure analysis unit 324 analyzes the package information and detects a content file specified by a file path constituting the package information and a folder in which the content file is arranged. As a transmission target file, an application entry point file and a reference destination of the application, that is, a content file of a content designated as a processing target such as activation, acquisition, and presentation are detected (see FIG. 8B). The content structure analysis unit 324 stores the transmission target file transmitted from the composition start time in the temporary folder 34 while maintaining the package configuration stored therein. The content structure analysis unit 324 specifies a content file that does not include the composition time code in the file name or a content file that includes the composition time code “00-00-00” in the file name as a transmission target file transmitted from the composition start time. . Note that the content structure analysis unit 324 may analyze the description of the application serving as the application entry point and detect the reference content file specified in the description related to the execution instruction of the process referring to another file. .

  The detected file may include a time code control target file to be controlled by the composition time code. The content structure analysis unit 324 identifies the replacement file, the transmission stop file, and the transmission restart file that include the organization time code in the file name as the time code control target file. The content structure analysis unit 324 generates a list including a set in which the time code and the file path are associated with each other for the identified time code control target file, and rearranges these sets in order of the time indicated by the time code. The list obtained by the rearrangement is called a time code control target file list. The content structure analysis unit 324 outputs the generated time code control target file list to the file control unit 326.

  The file control unit 326 receives the time code control target file list from the content structure analysis unit 324 and the organization time code from the program organization information management device (not shown). The file control unit 326 refers to the time code control target file list among the time code control target files stored in the time code control target package, and selects a file having a file name corresponding to the time code suitable for the organization time code. Identify. The file control unit 326 determines that the identified file is a transmission target file, and extracts it from the application package stored in the expanded package storage unit 322. The file control unit 326 stores the extracted file in a storage area of a folder corresponding to the extraction source application package folder in the temporary folder 34. In the example shown in FIG. 8C, when the composition time code becomes “00-12-34”, at the same time or immediately after, the file control unit 326 displays the file “arranged in the folder“ data ”in the expanded package storage unit 322. 00-12-34_text.json "is extracted. The file control unit 326 deletes the initial file “text.json” in the storage area of the folder “data” in the temporary folder 34, and changes the file name of the file “00-12-34_text.json” to “text.json”. Change and place in the temporary folder 34. Since file deletion and file placement are performed instantaneously, it is equivalent to file rewriting.

  If the file size of the identified file is 0 bytes (empty file), the file control unit 326 determines that the file is a transmission stop file, and deletes the same type of file as the determined transmission stop file from the temporary folder 34. In the example illustrated in FIG. 8C, the file control unit 326 specifies that the file size of the file “00-15-41_logo.json” arranged in the folder “images” of the expanded package storage unit 322 is 0 bytes. To do. The file control unit 326 determines that the file is a transmission stop file. The file control unit 326 uses the same file name “original file name” stored in the storage area of the folder “images” of the temporary folder 34 corresponding to the folder “images” in which the transmission stop file is arranged as the same type of file. log.jpeg "is detected. The file control unit 326 updates the transmission target file by deleting the detected file. File control processing by the file control unit 326 will be described later.

  The control information generation unit 328 controls the control information related to the application including the transmission target file based on the storage state of the transmission target file in the temporary folder 34 and the transmission information indicated by the package entry metadata input from the metadata analysis unit 323. Is generated. When the transmission information is determined for each part of the file group or each file, the control information generation unit 328 generates control information including information on a part related to the transmission target file in the transmission information. The control information includes information such as control of operations such as activation and termination indicated by the transmission information, and authority of functions such as whether or not to change the display layout of the broadcast video. When the communication transmission path NT is specified as the transmission path and FTP is specified as the transmission protocol, the IP address of the server device 60 is included in the control information as the acquisition destination from the receiver 80. Note that the control information generation unit 328 generates control information in a format corresponding to the transmission method specified in the transmission information. For example, when MMTP is specified, the control information generation unit 328 controls the MH-application information table (MH-AIT), data directory management table, data asset management table, and data content management described in Non-Patent Document 4 as control information. Generate a table or the like. When FTP is designated, the control information generation unit 328 generates a file format AIT or the like as control information. The control information generation unit 328 outputs the generated control information to the transmission control unit 329.

  The transmission control unit 329 refers to the transmission information indicated by the package entry metadata input from the metadata analysis unit 323 and identifies the transmission method of the transmission target file stored in the temporary folder 34. The transmission control unit 329 outputs the file and the control information input from the control information generation unit 328 to the transmission unit 35, and causes the transmission unit 35 to transmit the file and the control information using the specified transmission method. The transmission control process by the transmission control unit 329 will be described later.

(Package loading process)
Next, the package reading process according to the present embodiment will be described.
FIG. 9 is a flowchart showing a package reading process according to the present embodiment.
(Step S101) The package development unit 321 determines whether or not a package read trigger is input from a program organization information management device (not shown). When it is determined that there is (YES in step S101), the process proceeds to step S102. When it is determined that there is not (NO in step S101), the processing in step S101 is repeated (standby).
(Step S <b> 102) The package development unit 321 reads the application package indicated by the application package name information specified by the input application package name information from the package storage unit 31. The package expanding unit 321 expands an application package configured as a ZIP file, and stores the expanded application package in the expanded package storage unit 322. Thereafter, the process proceeds to step S103.

(Step S <b> 103) The metadata analysis unit 323 reads package entry metadata from the expanded package storage unit 322. The metadata analysis unit 323 analyzes the read package entry metadata and identifies a content folder in which a content file group is stored. Thereafter, the process proceeds to step S104.

(Step S104) The content structure analysis unit 324 analyzes the structure of the content in the content folder based on the content information described in the package entry metadata and the package information, and detects a transmission target file and a time code control target file. . The content structure analysis unit 324 stores the transmission target file from the composition start time (time code “00-00-00”) in the temporary folder 34. Thereafter, the process proceeds to step S105.

(Step S105) The content structure analysis unit 324 generates a time code control target file list in which a set of a time code and a file path for each detected time code control target file is arranged in the order indicated by the time code. The content structure analysis unit 324 outputs the generated time code control target file list to the file control unit 326.

FIG. 10 is a diagram illustrating an example of a time code control target file list.
The time code control target file list shown in FIG. 10 is a file list generated by taking as an example the case where the content files shown in FIGS. 3 and 5 are arranged in the application package. This time code control target file list includes three sets of information related to time code control target files related to the two types of initial files “logo.jpeg” and “text.json”. For example, the set shown in the second row includes a number “1”, a time code “00-08-43”, and “file path contents / images / 00-08-43_logo.jpeg”. The time code “00-08-43” indicates that the time related to the time code control is 8 minutes 43 seconds after the knitting start time. Since the file “00-08-43_logo.jpeg” is a transmission stop file, this time indicates the transmission stop time of the same type of file in the immediately preceding order (in this case, the initial file “logo.jpeg”). The file path “contents / images / 00-08-43_logo.jpg” indicates that the folder to be arranged is “contents / images /” and the file name is “00-08-43_logo.jpeg”. The time code control target file list may include a file size, a file operation type, and the like as elements in addition to the time code and the file path.

(File control processing)
Next, file control processing according to the present embodiment will be described.
FIG. 11 is a flowchart showing file control processing according to the present embodiment.
(Step S111) The control unit 32 starts a file control process by activating a thread that executes the function of the file control unit 326 at the start of composition. Thereafter, the process proceeds to step S112.
(Step S112) The file control unit 326 refers to the organization time code input from the program organization information management device (not shown), and compares it with the duration of the program indicated by the content information included in the package entry metadata. Then, it is determined whether or not the knitting is finished. When the time indicated by the composition time code is equal to or longer than the duration time, the file control unit 326 determines that the composition is finished. When the time indicated by the knitting time code is less than the duration, the file control unit 326 determines that knitting is in progress. Thereafter, the process proceeds to step S113.

(Step S113) When the file control unit 326 determines that the composition is finished (YES in Step S113), the process proceeds to Step S117. If the file control unit 326 determines that knitting is in progress (NO in step S113), the process proceeds to step S114.
(Step S114) The file control unit 326 obtains the time code value of the first item in the time code control target file list (the first item in the unprocessed time code control target file) and the knitting time code value. Compare. Thereafter, the process proceeds to step S115.
(Step S115) When it is determined that the value of the knitting time code is smaller (YES in Step S115), the process returns to Step S112. When it is determined that the value of the composition time code is equal to or greater than the time code value of the time code control target file list (NO in step S115), the process proceeds to step S116.

(Step S116) The file control unit 326 extracts the file from the time code control target package stored in the temporary folder 34 as a transmission target file. The file control unit 326 replaces the extracted file with the extracted file of the same type stored in the transmission target file area of the temporary folder 34, and deletes the same type of file. However, if the extracted file is a transmission stop file (file size is 0 byte), the file control unit 326 determines that the file is a transmission stop file. The file control unit 326 then deletes the same type of file stored in the temporary folder 34 without replacing the file. Thereafter, the file control unit 326 deletes the information described in the top item of the time code control target file list, and then returns to step S112.

  Note that the file control unit 326 may replace the file name of the extracted transmission target file with the original file name from which the organization time code and underbar are removed, and store the transmission target file with the replaced file name in the temporary folder 34. Good. Thereby, the receiver 80 can refer to the replaced transmission target file without changing the file name of the reference destination designated in the application.

(Transmission control processing)
Next, transmission control processing according to the present embodiment will be described.
FIG. 12 is a flowchart showing a transmission control process according to the present embodiment.
(Step S <b> 121) The control unit 32 starts the transmission control process by activating a thread that executes the function of the transmission control unit 329 at the start of execution of the transmission program. Thereafter, the process proceeds to step S122.
(Step S122) The transmission control unit 329 determines whether or not a transmission start trigger is input from a program organization information management device (not shown). When it determines with having input (step S122 YES), it progresses to step S123. When it is determined that no input has been made (NO in step S122), the processing in step S122 is repeated (waiting).
(Step S123) The transmission control unit 329 outputs the transmission target file stored in the temporary folder 34 to the transmission unit 35, thereby transmitting the file using the transmission method specified by the transmission information included in the package entry metadata. . Similarly, the transmission control unit 329 causes the transmission unit 35 to transmit the control information input from the control information generation unit 328.
Thereafter, the process proceeds to step S124.
(Step S124) The transmission control unit 329 determines whether or not a transmission end trigger is input from a program organization information management device (not shown). If it is determined that the input has been made (YES in step S124), the process returns to step S122 (standby). If it is determined that no input has been made (NO in step S124), the process returns to step S123 (continuation of transmission).

  When MMTP is specified as a transmission protocol in the transmission information (file transmission), the transmission control unit 329 specifies the multiplexing device 50 (FIG. 1) as a direct transmission destination to the transmission unit 35, and the transmission destination is The transmission device 35 is caused to transmit the transmission target file (content file group) and the control information designated as the multiplexing device 50. The transmission control unit 329 causes the multiplexing device 50 to transmit the transmission target file and the control information transmitted to the multiplexing device 50 using the designated transmission method. The multiplexing device 50 generates multiplexed data obtained by multiplexing the transmission target file received from the application transmitting device 30, the control information, and the multimedia data received from the encoding device 40. The multiplexing device 50 subdivides the generated multiplexed data and generates an MMTP packet storing the subdivided data. The multiplexing device 50 generates an IP flow composed of a series of IP packets storing the generated MMTP packet. The multiplexing device 50 transmits the generated IP flow to a transmission destination according to the transmission path specified by the application transmission device 30. When the communication transmission path NT is designated as the transmission path, the multiplexing apparatus 50 transmits the IP flow to the router apparatus 100 (FIG. 1). When the broadcast transmission path BT is designated as the transmission path, the multiplexing device 50 transmits the IP flow to the broadcast facility 70 (FIG. 1). The IP flow transmitted to the router device 100 is transmitted to the receiver 80 (FIG. 1) via the communication transmission line NT. The IP flow transmitted to the broadcast facility 70 is transmitted to the receiver 80 via the broadcast transmission path BT. The transmission control unit 329 repeatedly transmits the transmission target file every predetermined period so that the receiver 80 can acquire the entire transmission target file from the transmitted IP flow. Further, when transmission of a file group constituting an application is started from the program composition time, a delay occurs until the receiver 80 receives all the files and the application becomes executable. For this reason, in order to enable the receiver 80 to execute the application simultaneously with the program start time, a transmission start trigger may be given to the transmission control unit 329 at a time earlier than the program scheduling time to start transmission of the file group. .

  There may be a delay from when the transmission target file stored in the temporary folder 34 is updated by the file control unit 326 to when the updated transmission target file is transmitted by the transmission control unit 329. For example, if it takes 5 seconds to transmit all the files in the temporary folder 34 once, there is a possibility that a delay of 5 seconds at the maximum occurs until the transmission of the updated file is completed. Therefore, when storing the time code control target file in the temporary folder 34, the file control unit 326 outputs file update information indicating that the transmission target file has been updated to the time code control target file to the transmission control unit 329. May be. As a result, the transmission control unit 329 preferentially transmits the updated time code control target file indicated by the file update information input from the file control unit 326, and causes the application being executed in the receiver 80 (FIG. 1) to execute. The delay until the file update is reflected can be reduced. In the transmission information, a transmission protocol other than MMTP may be specified as the IP flow transmission method. In the transmission information, a data format other than the IP flow, for example, a TS (Transport Stream) may be designated as a data format in which the transmission target file is stored. In addition, as a transmission method between the application transmission device 30 and the multiplexing device 50, transmission methods of different layers can be used. As an example, the transmission control unit 329 of the application transmission device 30 may perform file segmentation and MMTP packet generation, and the multiplexing device 50 may perform reconfiguration of control information and multiplexing of IP flows.

  In the transmission information, when FTP is specified as a transmission protocol (file transfer), the transmission control unit 329 specifies the server device 60 (FIG. 1) as an output destination to the transmission unit 35. By specifying FTP, the communication transmission line NT is specified as the transmission path. The server device 60 sends a file designated by the request information from the receiver 80 (FIG. 1) among the transmission target files (content file group) received from the application transmission device 30 via the communication transmission line NT as a response. Transmit to receiver 80. Therefore, the server device 60 needs to complete the reception of the transmission target file from the application transmission device 30 before the program organization start time. Therefore, the transmission control unit 329 may start transmission of the transmission target file at a time earlier than the composition start time by at least the transmission time (file transfer time) from the transmission start to the transmission completion. The transmission control unit 329 instructs the transmission unit 35 to delete the transmission target file transmitted to the server device 60 in response to the deletion of the transmission target file stored in the temporary folder 34 by the file control unit 326. A command may be transmitted. In addition, the transmission control unit 329 instructs the transmission unit 35 to update the transmission target file to the server device 60 in response to the update of the transmission target file stored in the temporary folder 34 by the file control unit 326. May be transmitted. The transmission timing of the FTP command may be a time that is at least earlier than the time indicated by the composition time code input to the file control unit 326 by the file transfer time. In the transmission information, even if the server device 60 is designated as the transmission destination, a transmission protocol other than FTP may be designated as the transmission protocol.

  When different transmission methods are designated in the transmission information in the plurality of application packages, the transmission control unit 329 may cause the transmission target files to be transmitted in parallel using the designated transmission methods. When a transmission method is specified for each file group in the transmission information, the transmission control unit 329 may cause the transmission target file to be transmitted using the transmission method of the file group to which the transmission target file belongs. In the transmission information, when a transmission method is specified for each file, the transmission control unit 329 may cause the transmission target file to be transmitted using the transmission method related to the transmission target file. When MMTP is specified as the transmission protocol in the transmission information, a multiplex period for the IP flow may be specified, and the multiplex period depends on the importance, urgency, etc. of the information stored in the file. It may be variable. When the multiplexing period is designated, the transmission control unit 329 causes the multiplexing device 50 to multiplex the data of the transmission target file with the designated multiplexing period, thereby generating an IP flow.

When a plurality of sets of package reading triggers and application package name information are input, the package development unit 321 reads the application package specified by each application package name information. The control unit 32 may perform the above-described processing in parallel for each of the plurality of read application packages and transmit a content file group related to each program.
In addition, the file control unit 326 and the transmission control unit 329 may realize their functions by executing a program that is different from other configurations of the control unit 32. Moreover, in order to implement | achieve the function of the external file update part 33, you may implement | achieve by execution of the same program as the control part 32, and you may implement | achieve by execution of a different program.

(Configuration of application operation verification device)
Next, the configuration of the application operation verification apparatus 90 according to the present embodiment will be described. About the same structure as the application transmitter 30 (FIG. 7), the same code | symbol is attached | subjected and the description is used.
FIG. 13 is a schematic block diagram showing the configuration of the application operation verification apparatus 90 according to this embodiment.
The application operation verification device 90 includes a package storage unit 31, a temporary folder 34, a control unit 92, and an execution unit 93. The application operation verification device 90 may be a dedicated device. The application operation verification device 90 may be configured by causing a general-purpose server device or personal computer to execute processing indicated by a command described in a predetermined application operation verification program.

  The control unit 92 includes a control device (not shown) such as a CPU and a storage medium. The control unit 92 executes a process indicated by a command described in a predetermined application operation verification program read from the storage medium, thereby It functions as a development unit 321, a development package storage unit 322, a metadata analysis unit 323, a content structure analysis unit 324, and a file control unit 326. The configuration of the control unit 92 corresponds to a configuration in which the control information generation unit 328 and the transmission control unit 329 are omitted in the control unit 32 (FIG. 7) of the application transmission device 30. This is because the application operation verification apparatus 90 does not require transmission of a file. Therefore, the control unit 92 specifies the verification target file instead of the transmission target file from the application package read from the package storage unit 31 and stores the specified verification target file in the temporary folder 34. In addition, the control unit 92 stores, from the application package, a time code control target file including a time code suitable for the composition time code in the file name as a verification target file in the verification target file area of the temporary folder 34. These verification target files correspond to content files transmitted to the receiver 80 (FIG. 1) at the time specified by the composition time code input to the file control unit 326.

  The execution unit 93 receives an operation signal by an operation input from the user, specifies an application entry point file specified by the input operation signal, and reads the specified file from the temporary folder 34. The execution unit 93 executes a process indicated by an instruction described in the application stored in the read file. The execution unit 93 analyzes the described application and reads another content file designated as a reference destination from the temporary folder 34. The execution unit 93 controls the presentation of content stored in the content file read by executing the process. Therefore, by accessing the file of the application entry point, it is possible to verify the operation specifying the time indicated by the composition time code. The execution unit 93 may be realized by executing a program separate from the application operation verification program, for example, a web browser.

(Mutual conversion)
In the above description, the case where the package deployment unit 321 (FIGS. 7 and 13) of the application transmission device 30 and the application operation verification device 90 deploys the ZIP application package is taken as an example, but the present invention is not limited to this. The application transmission device 30 and the application operation verification device 90 each read an MXF format application package, perform format conversion on the read MXF format application package, and generate a ZIP format application package (not shown). ) May be provided. In addition, the application operation verification apparatus 90 may include a second conversion unit (not shown) that performs format conversion on a ZIP application package to generate an MXF application package. In the following description, these conversion units are simply referred to as conversion units. The format conversion from the ZIP file to the MXF file is called ZIP-MXF conversion, and the format conversion from the MXF file to the ZIP file is called MXF-ZIP conversion. In addition, when the data format of the content package including multimedia data such as video and audio separate from the file related to the application stored in the content management device 10 in FIG. 1 is the MXF format, the output unit of the content management device 10 Alternatively, the content transmission device 20 may perform MXF-ZIP conversion on the content package. In that case, the application transmission device 30 receives the ZIP-format application package obtained by MXF-ZIP conversion.

Next, the data structure of each type of application package will be described.
FIG. 14 is a diagram illustrating an example of the data configuration of each type of application package.
The upper part of FIG. 14 shows an example of the configuration of an application package configured as a ZIP file. The ZIP file is a file including a plurality of sets including a local file header and file data (file entry), a plurality of central directory headers, and an end-of-central directory record in that order. The local file header is data indicating information related to the file, such as a file size and a file path, for each file (local file) arranged in the application package. The local file corresponds to an application file, various content files referenced from the application, package entry metadata, a file related to an event message, and various files arranged in a document folder. The file data (substance data) of each local file is divided by the local file header. File data of the local file is stored in an area subsequent to the local file header. Each central directory header is data indicating information such as the compression method of each local file, the file size before and after compression, and the location where the local file is stored in the entire ZIP file. The end of central directory record is data indicating the end of the ZIP file. With this configuration, in the ZIP file, data indicating the hierarchical structure between folders below the package root folder and local files arranged in each folder are stored in a lump. Therefore, the ZIP file can be expanded from the package root folder into the physical structure of the content file configuration folder and the individual local files arranged in each folder. As information accompanying each local file, another data structure may be included in one or both of the area following the local file header and the area following the file data. Another data structure may be included in one or both of the area before the first central directory header and the area between the last central directory header and the end-of-central directory record.

  The lower part of FIG. 14 shows an example of the configuration of an application package configured as an MXF file. An MXF file is a file having a data format often used in content production and management. In the MXF file, a local header of each local file constituting the ZIP file and a set of file data are stored in a predetermined data array (Generic Stream Partition) including the order. The MXF file is a file that includes a Key, Length, and Value area in that order, and further includes a plurality of KLV structures in the Value area. A data array composed of a plurality of KLV structures is called a generic stream. A value (application package identification value) indicating that the MXF file has a generic stream of the application package is set in the top key in the lower part of FIG. In the subsequent Length, a value indicating the data size of the entire plurality of subsequent KLV structures is set. Each KLV structure included in the value area of the KLV structure having the application package identification value is a data structure that includes key, length, and value in that order, and stores various data in the value area. A value (local file identification value) indicating that a local file constituting the application package is stored is set in the Key of the KLV structure from the beginning to immediately before the end. In the Length, a value (data size value) indicating the data size of data stored in the subsequent Value area is set. The Value area is a data area in which the local file header of each local file and the file data of the local file are stored. If the information accompanying the file data includes a data structure separate from the local file header, the data structure is also stored in the same Value area. That is, Key and Length are segmented data in which individual local file headers and file data sets are segmented by their insertion. The local file header of each local file stored in the ZIP file can be used as information (property description) regarding the local file.

  A value (central directory record identification value) indicating that the central directory header of each local file is stored is set in the key of the KLV structure at the end of the MXF file related to the application package. In the Length, a data size value of data stored in the Value stored in the subsequent Value is set. Value is a data area in which a central directory header and an end-of-central directory record related to each local file are stored in that order. Other data structures may be included in one or both of the area before the beginning central directory header and the area between the last central directory header and the end of central directory record. Therefore, in the last KLV structure, a file index composed of individual central directory headers stored in the ZIP file is stored as it is as index information of the content file group of the application. In the MXF file, the number of KLV structures included in the generic stream having the application package identification value is one more than the number of stored local files. With such a data structure, format conversion between a ZIP file and an MXF file described later is simplified. The MXF file structure related to the application package may be combined with the structure of an MXF file storing other multimedia data such as video and audio, and may be configured as a content package in which program contents are collected.

(Format conversion)
Next, format conversion will be described. In ZIP-MXF conversion, the conversion unit generates an MXF file by sequentially connecting a KLV structure storing a set of local file headers and file data for each local file included in the ZIP file. Specifically, the conversion unit performs the process shown in FIG.

FIG. 15 is a flowchart showing ZIP-MXF conversion according to the present embodiment.
(Step S131) The conversion unit extracts a local file header and a set of file data of each local file included in the ZIP file stored in the storage medium. Further, when the data structure related to the local file exists before and after the file data, the conversion unit also extracts them together. Thereafter, the process proceeds to step S132.
(Step S132) For each extracted set, the conversion unit stores a key in which a local file identification value is set, a length in which the data size value of the set is set, a local file header and file data of the set, and the like. The KLV structure is generated by concatenating the value regions. Thereafter, the process proceeds to step S133.

(Step S133) The conversion unit extracts the central directory header and end-of-directory record of each local file included in the ZIP file. One or both of the area before the first central directory header and the area between the last central directory header and the end-of-central directory record contain other data structures with information that is not limited to a specific local file. If so, the conversion unit also extracts them together. Thereafter, the process proceeds to step S134.
(Step S134) The converting unit sets the key in which the central directory record identification value is set, the length in which the entire data size such as the extracted central directory header and the end of central directory record is set, the extracted central directory header and the end of A KLV structure is generated by concatenating the value area storing the central directory record and the like. Thereafter, the process proceeds to step S135.

(Step S135) The conversion unit includes the Key in which the application package identification value is set, the Length in which the data size of the entire KLV structure generated in Steps S132 and S134 is set, and the KLV structure generated in Steps S132 and S134. To generate a generic stream and output an MXF file. The conversion unit stores the output MXF file in a storage medium. At this time, the conversion unit may be combined with an MXF file storing other multimedia data such as video and audio generated separately as necessary to form a content package. Thereafter, the process shown in FIG.

  In MXF-ZIP conversion, the conversion unit excludes the Key and Length that distinguish the KLV structure for each local file included in the MXF file, and sequentially concatenates a set of local file headers and file data stored in the Value area. As a result, a ZIP file is generated. Specifically, the conversion unit performs the process shown in FIG.

FIG. 16 is a flowchart showing MXF-ZIP conversion according to the present embodiment.
(Step S141) The conversion unit reads the MXF file of the application package stored in the storage medium or the MXF file of the content package containing the application package, stores the application package based on the set value of the key, and The storage location is determined, and the data size of the value area including the KLV structure related to the application package in the MXF file is determined based on the subsequent Length. Thereafter, the process proceeds to step S142.

(Step S142) The conversion unit performs local processing for each of the KLV structures from the beginning to immediately before the end among the KVL structures included in the value area of the KLV structure having the application package identification value based on the setting value of the beginning Key. Determine that the file is stored. The conversion unit determines the data size of the data stored in the subsequent Value area based on the subsequent Length. The conversion unit extracts a value area in which a local file header, file data, and the like are stored. Thereafter, the process proceeds to step S143.
(Step S143) The conversion unit stores the central directory record for the last KLV structure among the KVL structures included in the value area of the KLV structure having the application package identification value based on the setting value of the first key. Determine that. The conversion unit determines the data size of the data stored in the subsequent Value area based on the subsequent Length. The conversion unit extracts a value area in which a central directory header, an end-of-central directory record, and the like are stored. Thereafter, the process proceeds to step S144.

(Step S144) The conversion unit sequentially connects the value areas extracted in step S112, and further connects the value areas extracted in step S143 to generate a ZIP file. Thereafter, the process shown in FIG. 16 ends.

As described above, the application transmission device 30 and the application operation verification device 90 according to the present embodiment include the metadata analysis unit 323 and the content structure analysis unit 324, respectively. The metadata analysis unit 323 analyzes the package entry point metadata from the application package and specifies an application program. In the application package, a content root folder in which content files related to the application program of the digital broadcasting service are arranged, and package entry point metadata including content information indicating the entry point of the application program are arranged. The content structure analysis unit 324 analyzes the structure of a folder below the content root folder, and extracts a content file related to the application program from the content root folder.
According to this configuration, the location of the entry point referred to first in the application program is immediately identified with reference to the package entry metadata. Since content files arbitrarily configured by the producer are efficiently extracted as processing targets, a common processing target is specified between the producer and the broadcaster or the service provider. For example, the interoperability is improved by using this application package as a material exchange between the broadcaster or service provider and the producer, and as a common data format to the transmission device in the broadcaster.

In addition, the content structure analysis unit 324 analyzes the file name of the content file, and generates a control target file list indicating the time indicated by the file name and the location of the content file. The application transmission device 30 and the application operation verification device 90 include a file control unit 326 that refers to the control target file list and selects a content file having a file name indicating a time corresponding to the program organization time.
According to this configuration, for a content whose content file is updated as time elapses, the processing start time and the processing target file are immediately specified by the file name when the program is organized. The producer can efficiently verify the start and time of the process, and the broadcaster or service provider can smoothly organize the program based on the process start time intended by the producer.

Further, when the selected content file is an empty file, the file control unit 326 stops processing related to the content file at the time indicated by the file name of the selected file.
According to this configuration, the stop time and the file to be stopped are immediately specified by the file name for the content to be stopped when the program is organized. The producer can efficiently verify the process stop and the time, and the broadcaster or the service provider can smoothly organize the program based on the process stop time intended by the producer.

Further, the application transmission device 30 and the application operation verification device 90 each include a package development unit 321. The package development unit 321 arranges the content file storing data for each set from the first format file in the folder indicated by the header, and develops it as an application package. The file of the first format is configured by connecting a set including a folder in which the content file is arranged, a header indicating identification information, and data stored in the content file, between the content files. The file in the first format is, for example, a ZIP file.
According to this configuration, the content file to be processed is specified at the time of program organization from the application package reproduced by development from the first format file. It is possible to use a file of the first format convenient for batch handling in program organization.

In addition, each of the application transmission device 30 and the application operation verification device 90 includes a conversion unit. The conversion unit excludes the division data from the second format file and converts the file into the first format file. In the file of the second format, the division data indicating the arrangement of the set including the folder in which the content file is arranged and the header indicating the identification information and the data stored in the content file are further arranged at the head of each set. File. The second format file is, for example, an MXF file.
According to this configuration, the conversion from the second format file to the first format file can be realized by a simple process such as exclusion of segmented data. The second format file that allows easy access to the individual content files based on the classification data can be converted into the first format file to facilitate batch handling.

In addition, the application operation verification apparatus 90 includes a conversion unit that arranges division data indicating the arrangement of the set at the head of each of the above-described sets included in the first format and converts the data into a file of the second format.
According to this configuration, conversion from the first format file to the second format file can be realized by a simple process such as arrangement of segmented data. Therefore, the first format file convenient for batch handling can be converted to the second format file to facilitate access to individual content files, so that content creation and editing can be performed efficiently. it can. Therefore, it is possible to achieve both simple operation using the first format file, compatibility with the file base system using the second format file, and applicability to long-term archiving.

In addition, the application transmission device 30 includes a transmission control unit 329 that transmits the content file extracted using the content file transmission method indicated by the transmission information included in the package entry point metadata.
According to this configuration, a content file arbitrarily configured by the producer is efficiently extracted as a transmission target, and transmitted using a desired transmission method designated by the broadcaster or service provider. Therefore, in providing a digital broadcast service, interoperability between the producer and the broadcaster or service provider is improved.

In addition, the application operation verification device 90 includes an execution unit 93 that executes processing indicated by an instruction described in the identified application program.
According to this configuration, since the content file arbitrarily configured by the producer is efficiently extracted as a processing target, the operation verification of the application program arranged in the produced application package can be performed smoothly.

  The embodiment of the present invention has been described above with reference to the drawings. However, the specific configuration is not limited to the above-described configuration, and various design changes and the like can be made without departing from the gist of the present invention. Is possible.

  For example, the application transmission device 30 may be configured as a single device integrated with any of the content transmission device 20, the encoding device 40, the multiplexing device 50, or any combination thereof. Further, the application operation verification device 90 may be configured as a single device integrated with the content management device 10.

B1 ... broadcast communication cooperation system, BT ... broadcast transmission path, NT ... communication transmission path, 10 ... content management apparatus, 20 ... content transmission apparatus, 30 ... application transmission apparatus, 31 ... package storage section, 32 ... control section, 321 ... Package development unit, 322 ... Development package storage unit, 323 ... Metadata analysis unit, 324 ... Content structure analysis unit, 326 ... File control unit, 328 ... Control information generation unit, 329 ... Transmission control unit, 33 ... External file update unit 34 ... Temporary folder, 35 ... Transmitter, 40 ... Encoding device, 50 ... Multiplexer, 60 ... Server device, 70 ... Broadcast equipment, 80 ... Receiver, 90 ... Application operation verification device, 92 ... Control unit, 93 ... execution unit, 100 ... router device

Claims (15)

From the application package in which the content root folder in which the content file related to the application program of the digital broadcasting service is arranged, and the package entry point metadata including the content information indicating the entry point of the application program,
A metadata analysis unit that analyzes the package entry point metadata and identifies the application program;
Analyzing a structure of a folder under the content root folder, and extracting a content file related to the application program from the content root folder;
A processing apparatus comprising: The content structure analysis unit analyzes the file name of the content file, and generates a control target file list indicating the time indicated by the file name and the location of the content file,
The processing apparatus according to claim 1, further comprising: a file control unit that refers to the control target file list and selects a content file having a file name indicating a time corresponding to a program organization time.   3. The processing apparatus according to claim 2, wherein when the selected content file is an empty file, the file control unit stops processing related to the content file at a time indicated by a file name of the selected file. . From a file in a first format in which a set including a folder in which the content file is arranged and a header indicating identification information and data stored in the content file is linked between the content files, the data for each set The processing apparatus according to any one of claims 1 to 3, further comprising: an expansion unit that arranges a content file storing the content file in a folder indicated by the header and expands the content file as the application package. A first conversion unit that converts the division data indicating the arrangement of the set into a file of the first format by excluding the division data from a second type of file further arranged at the head of each of the sets; The processing apparatus of Claim 4 provided. The second conversion unit that arranges division data indicating the arrangement of the set at the head of each of the sets included in the first format and converts the data into a file of the second format. Processing equipment. The package entry point metadata includes transmission information indicating a transmission method of the content file,
The processing apparatus according to any one of claims 1 to 6, further comprising: a transmission control unit that transmits the content file using a transmission method indicated by the transmission information. The processing device according to any one of claims 1 to 6, further comprising an execution unit that executes processing indicated by an instruction described in the application program. In the computer of the processing unit,
From the application package in which the content root folder in which the content file related to the application program of the digital broadcasting service is arranged, and the package entry point metadata including the content information indicating the entry point of the application program,
A metadata analysis procedure for analyzing the package entry point metadata to identify the application program;
A content structure analysis procedure for analyzing a structure of a folder under the content root folder and extracting a content file related to the application program from the content root folder;
A program for running A content root folder and a package root folder in which package entry point metadata including content information indicating an entry point of an application program of the digital broadcasting service is arranged;
A data structure of an application package, wherein the application program file is arranged in a folder below the content root folder.   The content file related to the application program is arranged in a folder below the content root folder, and at least one file name of the content file includes a time code indicating a processing start time of the content file. Application package data structure described in.   12. The application package data according to claim 11, wherein an empty file including a time code whose file name indicates at least one processing stop time of the content file is arranged in a folder below the content root folder. Construction.   A set including a folder in which a content file related to the application program is arranged, a header indicating identification information, and data stored in the content file is configured as one file connected between the content files. The data structure of the application package according to any one of claims 10 to 12.   14. The data structure of an application package according to claim 13, wherein division data indicating the arrangement of the set is arranged at the head of each of the sets.   15. The data structure of an application package according to any one of claims 10 to 14, wherein the package entry point metadata includes transmission information indicating a transmission method of a content file related to the application program.

Images