JP2002203070A - Metadata distribution method - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To provide a service that enables control of a method of presenting content to a user, usage conditions, and the like, and enables protection of content rights, protection of individual user rights, and the like. SOLUTION: By defining metadata describing detailed information on content, it is possible to perform various controls on the content by the metadata. On the broadcast side, content presentation methods, usage conditions,
Content storage in the encrypted state, limited reception for terminals, limited reception for individuals, etc. can be defined, and the defined contents are distributed to the receiving side together with the content, and based on these definitions, viewer viewing control, storage control, and copying are performed. It provides a service that can protect the rights of contents such as copyrights by performing control and encryption / decryption control.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a metadata distribution method, and more particularly, to a metadata distribution method in an integrated data distribution service. By defining the metadata describing the detailed information on the content, various controls on the content can be performed by the metadata. This makes it possible to control content presentation methods, usage conditions, etc. to users, protect content rights,
It is possible to provide a service that can protect the rights of the individual user.

[0002]

2. Description of the Related Art In BS digital broadcasting, SI (Service Information) is defined as information relating to contents. Although this information is content-related information, it is specialized for an EPG (Electric Program Guide) and is not content-related information corresponding to various contents. Since means for defining detailed information on various contents is not currently defined in the broadcasting standard, it is not possible to provide detailed services based on control for each content. In addition, since the existing broadcast is a service with a view to viewing the content in real time, information for performing content accumulation control and copy control is scarce.

[0003]

As described above, EPG is used as a means for defining information related to content.
Since only the information for (electronic program guide) exists in the current satellite digital broadcasting standard, it is not possible to define more detailed information than the information for each program. As a result, it is not possible to define the content in more detail than the program, so that it is not possible to provide a content control service using control for each content or detailed information on the content.

In order to provide a data distribution service, contents are directly distributed to a home or the like, and the data is stored / copied / reproduced in a digital form in the home or the like. Issues related to copyrights and other rights, such as copying and reproduction, that exceed commercial use arise. Therefore, it is necessary to protect and manage the rights of copyright holders, broadcasters, viewers, and the like of the content. Conventional digital broadcasting is mainly intended for real-time viewing and listening, so it is content encryption on a transmission path by conditional access that limits terminals capable of receiving broadcasts and content protection such as copy control for external devices. . Conventionally, keys related to encryption on the transmission path are switched at a fixed time to protect the contents.
It is necessary to accumulate tables such as
Issues relating to security for the content occur.

[0005] According to the present invention, the transmitting side attaches metadata defining the usable range of the content for each content,
An object of the present invention is to enable detailed control of a content usage method in a range defined in metadata and a method of presenting a content to a user on the receiving side by distributing the content together with the content to the receiving side. Therefore, an object of the present invention is to provide a service capable of protecting the right of the content, protecting the individual right of the user, and the like.

[0006]

A content is created in units intended by a broadcaster, and content-related information is attached to each content. The metadata attached to each content includes copyright protection information, right information related to storage and reproduction, control information, and the like, from general information related to the content. Thus, fine control can be performed for each content. Also, on the broadcast side, it is possible to define a method of presenting content to a viewer, usage conditions, content storage in an encrypted state, conditional access to a terminal, conditional access to an individual, and the like. By providing storage control, copy control, encryption / decryption control, and the like, a service capable of protecting the rights of contents such as copyrights is provided. As a result, it is possible to provide a service capable of protecting the right of the content by controlling the method of presenting the content to the user and the use conditions, and protecting the right of the user.

[0007] According to the solution of the present invention, information used for searching for a content assigned to a content specified in a unit determined by a sending side device, and a copyright defined by the sending side device Metadata storing content related information including information on a method of presenting content to a viewer and usage conditions regarding the protection of a user and related rights, and a metadata distribution method for controlling content viewing and rights protection by a receiving terminal. , The metadata stream group includes a metadata default elementary stream, the elementary stream includes a plurality of modules, and a content identifier and a metadata for acquiring necessary metadata from the metadata stream group being distributed to one of the modules. Stores information including data identifier and distribution location Metadata list provided that,
A metadata distribution method is provided in which a receiving terminal acquires necessary metadata from a metadata list, and acquires and selects content.

[0008]

BEST MODE FOR CARRYING OUT THE INVENTION Overview (Service overview) This comprehensive data distribution service is an information (data) distribution service that can be viewed at the place where you want to see the content you want to see, and is a conventional real-time type (viewing what you are broadcasting) digital Unlike broadcasting, this service provides not only real-time delivery but also storage-based information delivery. This provides a Near Video On Demand (NVOD) -like service that allows the viewer to select and view his / her favorite content from the stored content whenever he wants. . In addition, the content is directly stored in a removable medium or an external device connected to a receiving terminal that receives the service, or the content can be viewed at a user's favorite place by copying. Furthermore, in the conventional digital broadcasting service, the content usage contract form is limited to a narrow range such as a contract on a terminal basis. However, this service provides a wide range of content usage contract forms capable of contracting on an individual user basis. .

FIG. 1 shows a service configuration diagram of the comprehensive data distribution service. Hereinafter, as an overview of the comprehensive data distribution service, a storage-type television broadcast will be described with reference to FIG. In a conventional television broadcast, a content 1 (program) sent from a broadcast side (broadcasting station) is transmitted to an antenna 2 (distribution by cable or distribution by package),
Viewing is performed from the moment when the data is received by the receiving terminal 3 and distributed by a monitor device such as the television 9 (real-time viewing 6). The storage type television broadcast in the present embodiment is:
In addition to the real-time viewing 6, a storage-type viewing 8 (such as a DVD-RAM, etc.) in which the content once distributed is stored in the storage medium 4 (a large-capacity storage medium such as a hard disk) and then viewed in the same manner as in a conventional VCR. In some cases, a removable medium 5 with high portability is used as a storage medium), and services such as real-time type + storage type viewing 7 for viewing the stored content and the distributed real-time viewing type content together are possible. It is an information distribution service.

(System Overview) FIG. 2 shows an overall configuration diagram of a comprehensive data distribution service system. As a system for providing the comprehensive data distribution service, in addition to an infrastructure using radio waves such as satellite broadcasting and terrestrial broadcasting, a service using an infrastructure using communication lines such as cable television and the Internet is possible. A case where digital satellite broadcasting using such a satellite is used as an infrastructure will be described. An overview of a system in which a comprehensive data distribution service is provided will be described with reference to FIG. The system of this comprehensive data distribution service is roughly divided into a sending side 100, a receiving side 200, a satellite line 10 using a satellite which is a transmission line connecting the sending side and the receiving side, a terrestrial line 11, a distribution network 12, and a mobile telephone network 13. It is. The receiving side 200 here is not limited to the receiving terminal 3 installed in the home 201, but also a public terminal 202 such as a vending machine, a terminal installed in a store 203 such as a convenience store, and an automobile as a mobile body. The in-vehicle terminal 204, the portable terminal 205, and the like mounted on the like are also assumed. On the sending side 100, a distribution center that produces and manages the content 1 and control information and distributes it to the receiving side 200;
A key management center for generating and managing keys used for content encryption, etc .; a customer management center for managing information on a receiving-side user; a request from a receiving-side user; a ground line 11 for collecting viewing history; , A distribution line management center that distributes (delivers) content by package media such as DVDs to users, stores, and the like.

(Service Contents) Next, services performed in the system shown in FIG. 2 will be described. In the comprehensive data distribution service, for example, the following services are enabled. -A home service mainly using the satellite digital line 10 and distributing comprehensive data of video, music, electronic magazines, games, and other video, audio, and data as digital information to the receiving terminal 3 installed in the home. 300, as in the home service, distributes data to the vending machine 202 and the retail store 203, and backs up data that cannot be stored in capacity at home, data that has not been stored, vending machines, and sales Handles data etc. that can be sold only at stores, for example, purchases electronic magazines that can be sold only at stores,
Vending machine / store service 301 for viewing at home receiving terminal 3 ・ Receiving terminal 3 at home, vending machine 202, store 203, etc. for external devices such as in-vehicle device 204 and portable terminal 205 It is possible to carry content from home and view it outside the home. For example, map data distributed to the home receiving terminal can be taken out to the in-vehicle device 204 by using a removable medium such as a DVD or an IC card in the car. A service 302 for mobiles that uses music data or removes music data by using a removable medium such as a memory card or an IC card and plays the music data with the portable terminal 205. The distribution cannot be performed by the satellite circuit 10 using the distribution network 12. Distribute contents etc. by package media such as CD-ROM, DVD-ROM and receive contents such as drama When a reservation is made from the terminal, a package delivery service 303 that distributes the content to the home by a courier service or the like from the sending side to the home on a DVD-ROM or the like. By controlling the receiving terminal in the mobile phone, for example, a mobile phone service 304 for making a program reservation or the like to a home receiving terminal from an outside location by using an EPG (Electronic Program Guide) on the screen of the mobile phone 206

In the present invention, a data distribution method for a home service will be described. (Rights protection method) This comprehensive data distribution service is a service for distributing contents directly to homes, etc., and performing storage / copy / reproduction with digital data at homes, etc. Since there is a problem with copyrights such as falsification, copying, reproduction, etc. beyond personal use, it is necessary to protect and manage the copyrights of contents, broadcasters, viewers, and other rights.

FIG. 3 is an explanatory diagram of a right protection method in the comprehensive data distribution service. Hereinafter, a right protection method in the present comprehensive data distribution service will be described with reference to FIG. The rights protection method in the comprehensive data distribution service is a content obtained by encrypting metadata 18 storing information such as a method of presenting content to a viewer defined on the transmitting side, usage conditions, and a content encryption key. 17. Other PSI / SI (Program Specific Informa)
distribution / Service Information) 19 and the like, and the right protection function 16 (RMP (Rights Management
& Protection) function) to interpret the metadata 18
Reception control of the content 17 to the reception terminal 3, storage control for the storage medium 4 and the removable medium 5, copy control, encryption / decryption control, presentation control for a monitor device such as a TV 9, authentication control for the external device 14, and identification of an individual. Authentication / charging control for the IC card 15 for this purpose.

Next, the PSI / SI 19, the content 17, the metadata 18, and the RMP function in the receiving terminal distributed from the transmitting side will be described. First, PSI / SI is data for acquiring necessary data from a stream being distributed, like conventional digital broadcasting. This comprehensive data distribution service acquires metadata, encrypted content, etc. Use to do.

Second, the contents in the present comprehensive data distribution service means that the contents 17 stored in the storage medium 4, the removable medium 5 or the like in order to prevent data falsification and unauthorized use are basically kept encrypted. Stored in state. The content 17 in the comprehensive data distribution service is conceptual and can be designated in a unit intended by the sending side, not in a unit indicating a constant physical quantity. Can recognize the contents. The contents can be instantly viewed by specifying the same channel as the conventional digital broadcast. Stream-based contents such as moving images mainly for real-time viewing, or temporarily stored or stored in the receiving terminal, and then viewed. It is divided into file-based contents that focus on this.

FIG. 29 is an explanatory diagram of an example of data constituting each content. In this comprehensive data distribution service, each data of a data group constituting the content is called an element. Therefore, the content is composed of one or a plurality of elements. In this comprehensive data distribution service, as shown in the figure, the contents are classified into stream-based contents and file-based contents according to the distribution form. Elements that make up stream-based content,
The contents of the elements making up the file-based content are as shown in the figure.

Third, the metadata in the comprehensive data distribution service is used for searching for the content and structure of the content assigned to the content specified by the unit intended by the broadcaster on the transmitting side. It includes general information to be used, the method of presenting content to viewers, and the usage conditions, etc., which define the protection of copyright holders and related rights on the sending side. Is possible. So, like metadata,
Since the information to be protected is included, a part of the information is encrypted and distributed, and the data is stored in the encrypted state even when the data is stored. The metadata is classified according to distribution timing and contents. In this comprehensive data distribution service, for example, the metadata is classified into the following metadata.・ A contract code for interpreting on the receiving terminal side the broadcaster's key, which is a unique key for each pay broadcaster, and whether or not all programs broadcast by the contracted broadcaster can be viewed or partially viewed. Pre-contract metadata that is stored and delivered to the user personally and asynchronously with the delivery of the content.- The name of the content required to confirm the content to be distributed and make a viewing / storage reservation on the receiving terminal side. , Content, scheduled broadcast date, etc. are stored and distributed to all receiving terminals before distribution of the target content regardless of the user who uses the receiving terminal, mainly EPG display of the receiving terminal, viewing / storage reservation Metadata for EPG for performing, etc. ・ Information for receiving, storing, and subscribing to viewing of content is stored, and is targeted to all receiving terminals regardless of the user who uses the receiving terminal The storage / playback metadata distributed in synchronization with the delivery of the content to be stored. ・ Information on the key that encrypted the content is stored and synchronized with the delivery of the target content in the same way as the storage / playback metadata. Metadata for key distribution to be distributed and stored ・ Information for updating EPG metadata stored by using with PSI / SI, and information for acquiring necessary data from a stream group being distributed are stored , A metadata list that is constantly distributed to all receiving terminals regardless of the user who uses the receiving terminal,-Updates information common to the entire system such as a common key that is stored in the terminal in advance and is common to the entire system Metadata for system key update that stores information to be transmitted and is distributed asynchronously to the distribution of content to all receiving terminals regardless of the user who uses the receiving terminal

Fourth, the RMP function 16 is a function for controlling and managing information related to the rights of the copyright holder, the broadcaster, the user, and the like in the receiving terminal. FIG. 30 is an explanatory diagram showing an outline of the RMP function. Basically, control is performed based on the information in the metadata, and within the range defined on the broadcast side (allowed range), the content is decrypted, presented on the screen,
FIG. 3 illustrates an outline of functions of an RMP that performs operations such as accumulation, copying, and outputting to the outside. Each function includes reception control function, accumulation control function, copy control function, presentation control function,
Viewing contract control function, billing control function, personal authentication control function,
Key management function, profile management function, time management function, application authentication control function, external device authentication control function,
There is a communication line control function and the like.

2. PSI / SI Details Next, in this comprehensive data distribution service, PSI / SI distributed from the transmitting side 100 to the
The details of the SI 19, the metadata 18, and the content 17 will be described. The PSI in this comprehensive data distribution service is data storing a TS (transport stream) configuration for transmitting each data on the transmission path, and is used to acquire the metadata 18 and the content 177 from the distribution radio wave. . The SI is data that stores information indicating the contents of the content and simple right information, and is data for expressing the EPG in the existing broadcasting.
In this comprehensive data distribution service that expresses EPG by using metadata, it is basically possible not to use it. As the data in the PSI used in this comprehensive data distribution service, a PAT (packet id) specifying a PID (packt id) of a TS packet transmitting a PMT (Program Map Table) related to a broadcast program in each TS (Transport stream) is used. Program Associ
Information table), information on the transmission path, such as the modulation frequency, and information relating the broadcast service. The NIT (Network Information Table), which indicates the configuration of the entire network, and the TS packet, which transmits each coded signal that constitutes the broadcast program, are transmitted. PI
PMT (Program MapTable) to specify D, DII (Download Info Indic) to specify module configuration in carousel
ator), DDB that stores file type data (Download
DSM-CC section (Digita
l Storage Media Command and Control). The details of each data structure in the present comprehensive data distribution service will be described below.

(PAT) FIG. 4 is an explanatory diagram of the data structure and description contents of the PAT. Hereinafter, the structure of the PAT 20 will be described with reference to FIG. The PAT is transmitted by a TS packet of PID 0x0000, is present for each TS, and is data indicating the configuration of a service distributed in the TS. The data included in the PAT 20 includes table_id (0x0) for identifying the PAT on the receiving terminal side.
0), information indicating data length, transport strea to be delivered
m (TS) ID, program_number (service_id) for identifying a service to be delivered in the TS, and TS for transmitting a PMT storing information in the service corresponding to the program_number
It is composed of the PID of the packet and the like. PAT is data required to receive content and metadata,
After receiving the content and the metadata, the data becomes unnecessary and may be temporarily stored in a non-volatile memory (RAM) or the like on the receiving terminal, but is basically not stored.
In order to realize the present comprehensive data distribution service, the PAT 20 currently specified by the BS digital broadcasting standard or the like is not particularly extended.

(NIT) FIG. 5 is an explanatory diagram of the data structure and description contents of the NIT. Hereinafter, the structure of the NIT 21 will be described with reference to FIG. The NIT is data that is transmitted by a TS packet of PID 0x0010 and indicates information on the entire network in which an integrated data distribution service that exists in common for each TS is performed. The data included in the NIT 21 includes a table_id for identifying the NIT on the receiving terminal side, information indicating a data length, a network_id indicating which network is described, a network descriptor describing a network name, and a CA_EMM_TS descriptor. , A system management descriptor for identifying whether data transmitted on the network is broadcast or non-broadcast, and a _TS description for system key update for identifying a TS for transmitting system key update metadata Child, transport_stream_id indicating the configuration of TS included in the network, service configuration in each TS,
A service list descriptor indicating the format of the service, a satellite distribution system descriptor including parameters such as the polarization plane of the radio wave, the frequency, the orbital position of the satellite to be used, and the modulation method required for the receiving terminal to acquire each TS And so on.

Since the NIT 21 is data that is rarely updated, it may be stored in the receiving terminal in order to improve the processing speed of the receiving terminal. As with PAT, no special storage is required. In performing the present comprehensive data distribution service, the part to be extended to the NIT 21 currently specified is the addition of the system key update _TS descriptor 22 and a part of the data in the service list descriptor 23. As described above, the system key update _TS descriptor is information that specifies a TS that transmits system key update metadata used when updating information common to the entire integrated data distribution system in the receiving terminal. Yes, since the system key update metadata is information that needs to be preferentially acquired by the receiving terminal, it is stored in the NIT 21 that is commonly distributed by each TS, so that any service in the network can be received during reception. It becomes possible for the transmission side to make a request to receive the system key update metadata. The structure of the system key update TS descriptor is TS_i to which the system key update metadata is distributed.
d, consisting of information such as the ID of the target network. When the system key update _TS descriptor does not exist in the NIT 21, it means that the system key update metadata is not distributed. The extension of the service list descriptor is that information indicating a storage type service which is a feature of the comprehensive data distribution service is newly added to the service type specified in the service list. This makes it possible to mix a comprehensive data distribution service with an existing broadcasting service in any network, for example, a BS digital broadcasting network, a terrestrial digital broadcasting network, or a CS digital broadcasting network. In addition, when the channel (service_id) is specified on the receiving terminal side, it is possible to recognize that it is a comprehensive data distribution service, and either the receiving process of the comprehensive data distribution service or the receiving process of the existing type, eg, BS digital broadcasting, is performed. It should be possible to identify whether it should be performed, and to separate the processing for realizing a receiving terminal that can receive both the existing service and the comprehensive data distribution service, and to ensure consistency with the existing service and the comprehensive data distribution service Becomes possible.

FIG. 31 is an explanatory diagram of the type of service currently specified. Currently undefined as an extension,
Or the operator defined 0x03-0x7F, 0x80-0xA0,
A new storage-type service (with a rights protection function) shall be newly defined in 0xA9-0xBF and 0xC1-0xFF.

(PMT) FIG. 6 is an explanatory diagram of the data structure and description contents of the PMT. Hereinafter, the structure of the PMT 24 will be described with reference to FIG. PMT 24 is specified in PAT 20
There is a table of the number of services transmitted by the TS packet identified by the PID and distributed in each TS, and specifies the PID of the TS packet transmitting each coded signal constituting the broadcast program in each service. Due to its characteristics, the PMT 24 is data in which information is different for each service, and is data indicating information on a service being distributed. The data included in the PMT 24 is table_i for identifying the PMT on the receiving terminal side.
d, information indicating the data length, and program_number (service_
id), PID of TS packet transmitting ECM for entire program
, A digital copy control descriptor that specifies copy control information for the entire program, an emergency information descriptor that specifies the distribution location of the emergency broadcast program, and each stream that constitutes a service being distributed Steam_type to specify the format of the stream, ES_PID to identify the TS packet in which each stream is stored, stream identification descriptor to tag each stream, layer transmission descriptor to specify the relationship between layered streams , A digital copy control descriptor that specifies copy control information for each stream, a target area descriptor that specifies the area where ES can be obtained, a video decode control descriptor that specifies a video code, and a data signal format Data coding system descriptor, conditional access system descriptor specifying ECM PID for each stream, etc. More composed. The PMT basically does not accumulate because the contents are different for each time frame in which the service is distributed, and when the PMT information becomes necessary, it acquires the information from the radio wave being directly distributed each time. The parts to be extended by the PMT 24 in performing the present comprehensive data distribution service include the digital copy control descriptor 25, stream_type
26, a data definition part in the stream identification descriptor 27. FIG. 32 is an explanatory diagram of information controlled by the digital copy control descriptor 25. In this comprehensive data distribution service, in order to perform various copy controls of content using metadata, a definition for newly referencing metadata is specified in the copy control format of the digital copy control method descriptor 25 or in other reserved area portions. This makes it possible to separate copy control using metadata and copy control using only the digital copy control descriptor of the existing type service, and achieve consistency with the comprehensive data distribution service and the existing type service.

FIG. 33 is an explanatory diagram of the stream format currently specified. The extension of the Stream_type 26 part is to add a new format to an undefined part or a user area when a stream of a new format is used in a comprehensive data distribution service with respect to a stream currently specified. This allows the receiving terminal that receives the comprehensive data distribution service to recognize the newly defined stream format.

FIG. 34 is an explanatory diagram of currently defined tag values. As an extended part of the stream identification descriptor 27, compon for tagging the stream
This is to add a new tag to the ent_tag part. On the receiving terminal side, by recognizing the value of this tag, the tagged stream identifies a stream for transmitting video, a stream for transmitting audio, a stream for transmitting data, a default stream which is a stream to be presented first, and the like. Operate.

FIG. 35 is an explanatory diagram showing an example of the case defined by the comprehensive data distribution service. In this comprehensive data distribution service, a new definition is made in the reserved area in FIG. 34, and the receiving terminal operating based on the tag value can be controlled from the broadcasting side. Since the tag value defined in the past is a meaning for viewing in real time, the tag value defined in FIG. 35 is used when distributing the storable content which is a feature of the comprehensive data distribution service. This makes it impossible for existing receiving terminals without the rights protection function to recognize streams that deliver content, while receiving terminals that can receive this comprehensive data distribution service can recognize storage-type streams. It is possible to separate the type service and the comprehensive data distribution service and to ensure consistency. The receiving terminal for the comprehensive data distribution service is different from the existing receiving terminal that directly performs the operation of acquiring the content. When the tag value indicating each metadata is specified, the receiving terminal obtains the metadata first. The processing is controlled according to the content of the metadata. If the tag value indicating the metadata and the tag value for storage are not specified, the operation of directly acquiring the content is performed as in the case of the existing receiving terminal. The priority of the tag value of the acquisition operation on the receiving terminal side is metadata for advance contract> metadata for storage and playback> tag value for each content, and the priority of metadata for system key update and metadata for EPG is within PMT No, the system key update metadata is performed in the NIT as described above. E
The PG metadata can be obtained by checking the PG metadata at a certain fixed period when the receiving terminal is activated, without giving any particular priority.

(DSM-CC section) Next, DII and DDB constituting a carousel stream for transmitting each element constituting metadata and file-based contents will be described. In the carousel transmission method in the MPEG2 transmission standard, information on data and control information at the time of acquisition are embedded in a carousel stream of DDI. Since the receiving operation is performed after acquiring this information, the distribution cycle is set to be very short. The actual file is
DDB is divided into blocks called DDB and distributed.
The block of DII is inserted into the stream of the block in accordance with the distribution cycle. Also, an aggregate with a DDB is defined as an intermediate aggregate called a module. The intermediate aggregate is an aggregate that can be defined on the sending side and exists as an arbitrary unit. Metadata is also divided into DDBs for distribution as one file and sent in the same way. As for the information on the metadata file, simple information is defined in the DII, but the detailed information is defined as one file as a metadata list. This metadata list is also 1
Since it is defined as one file, it is distributed to DDB and distributed. However, in the present embodiment, as an example, the metadata list is necessary information first in the receiving operation, and thus is defined as a module 0, which is a block that is first assembled in the receiving operation.

(DII) FIG. 7 is an explanatory diagram of the data structure and description contents of DII. Hereinafter, the structure of DII will be described with reference to FIG. DII28 is a stre specified in PMT24
It is transmitted by a TS packet identified by ES_PID of a stream whose am_type is a carousel. The DII 28 is information indicating a module configuration in the carousel and is data existing in each carousel stream. Data included in DII 28 is table_i for identifying DII on the receiving terminal side.
d, download_id to distinguish it from other carousels,
Block_size to specify each block size of DDB,
TCDownloadScenario that specifies the timeout value from the start to the end of the carousel download, number of Modules that indicates the total number of modules in the carousel, module_id that identifies each module, module_size that specifies the size of each module, and identifies the update of each module mod
ule_version, module_ that specifies information for each module
It is composed of info_byte and so on.

FIG. 36 is an explanatory diagram of information specified in Module_info_Byte. On the receiving terminal side, the data structure itself is not required in the present comprehensive data distribution service, except that the module in which the module_id in the carousel is specified by 0x00 is always obtained first.

(DDB) FIG. 8 is an explanatory diagram of the data structure and description contents of the DDB. Hereinafter, the structure of the DDB 29 will be described with reference to FIG. DDB29 is PMT2 like DII28.
The stream_type specified in 4 is transmitted by the TS packet identified by ES_PID of the stream that is a carousel, and is transmitted by the TS packet of the same PID as DII.
Is a plurality of data in one carousel for dividing and transmitting the module defined by. DD
The data included in B29 is table_id for the receiving terminal to identify DDB29, which module is divided into blocks.
It is composed of a module_id for designating a DDB, a module_version which is an update number of the module, a Block_number indicating a position of a block constituting the designated module, a Block_data for storing data itself obtained by dividing the module into blocks, and the like. The data structure itself does not need to be particularly extended in this comprehensive data distribution service.

3. Metadata Next, metadata generated on the transmitting side and distributed to the receiving terminal will be described. The description method of the metadata in this comprehensive data distribution service can be described in a text format such as XML or in a binary format such as PSI / SI. However, the parts that need to be encrypted are described in binary format, especially for the purpose of improving the description interpretation processing in the receiving terminal. Operation by text description is also possible. Metadata is classified according to the content to be described and the timing of distribution.

FIG. 37 is a diagram for explaining the classification of metadata. The structure and description contents of each metadata shown in FIG. 37 will be described below. (Pre-Contract Metadata) FIG. 9 shows the structure and description of the pre-contract metadata. The pre-contract metadata 30 is data mainly used as a judgment material when performing limited reception of contents in the present comprehensive data distribution service, and a different business key Kw for each pay broadcasting company.
And metadata including a contract code related to a tier / flat code related to the contract form, and distributed at the time of initial contract, contract renewal, renewal of the business key Kw, etc. at the time of terminal purchase. User identification information 31 for identifying whether a receiving terminal such as a terminal ID and a personal ID is data sent to a user who uses the terminal, an ID indicating a metadata encryption method, an encrypted part, and an encryption key (terminal ID ), Encryption information 32 relating to the encryption applied to the metadata, user's own personal information 33 such as the user's name, telephone number, address, settlement ability, settlement destination, password, etc., and the ID of the contracting company to which the user contracts , A business key Kw, a contract expiration date, a contract code, a contract point, and the like. For the encrypted portion, personal information 33 in which information such as the settlement destination of each user is stored, contract information 34 in which information such as a business key Kw is stored, and a terminal-specific key used by the user, that is, a terminal The data is encrypted on the transmitting side by the different Kmc 35 every time and distributed to the receiving terminal. As for the encryption key used for encryption, it is also possible to use a personal key Km unique to the IC card distributed to each user by operation, that is, a different personal key Km for each user who receives the comprehensive data distribution service. It is also possible to store metadata attribute information to be described later in addition to the above information in the pre-contract metadata by operation.

(EPG Metadata) FIG. 10 is an explanatory diagram of the structure and description contents of the EPG metadata 36. EPG
The metadata 36 for use in this comprehensive data distribution service is mainly for the user to confirm the content to be distributed and to make a reservation for viewing / storage of the content to be distributed. / It overlaps with the distribution of playback metadata and key distribution metadata. The EPG metadata 36 includes metadata attribute information 37 such as a metadata ID for identifying each metadata, a type of metadata, a size of metadata, a version number which is an update number, and metadata for pre-contract. The encryption information 32 on the encryption part of the metadata and the program I
D, program information 38 on the program such as scheduled broadcast date and time, program content, genre, content configuration, program size, etc.
Content information 39 such as content ID, content content, element configuration, etc., users who use the content, age restrictions which are restriction information for the content itself,
Usage restriction information 40 serving as a criterion for the receiving terminal to determine whether the user can make a reservation such as a copy restriction or a storage restriction.
including. For the encrypted part, the use restriction information 40 serving as a material for determining whether or not to make a reservation corresponds. In order to enable the use of metadata for all users, a system key common to all receiving terminals is used.
It is encrypted and distributed on the sending side by Ksy1_41. The content information 39 can be distributed without being stored depending on the operation level of the EPG in the comprehensive data distribution service. In some cases, the usage restriction information is also operated without being stored.
Metadata can be delivered without encryption.

(Metadata for storage and reproduction) Next, FIG.
FIG. 2 is an explanatory diagram of the structure and description contents of storage and reproduction metadata. The storage / playback metadata 42 is metadata including information necessary for receiving, storing, and playing back content.
This metadata is used when searching for stored content and is used to control a user's content usage method. The storage / playback metadata 42 includes metadata attribute information 37 for identifying the metadata itself, encryption information 32, program information 38, content information 39, usage restriction information 40, and storage / Content encryption information 43 such as an encryption method, an encryption key ID, and a key position of the content indicated by the playback metadata; Includes billing information 45 such as billing fee and billing timing based on the contract. For the encrypted part, use restriction information 40, content encryption information 43 including information such as a content encryption method and an encryption key ID, contract information 44 including information such as a use restriction period, a charge at the time of charging, timing And the like, which is encrypted and distributed on the transmission side by the same content key Kk 46 as the key for encrypting the content. As for the content information 39 in the storage / playback metadata, information such as the distribution position of the content is added to the content information stored in the EPG metadata.

(Key Distribution Metadata) Next, FIG. 12 shows a structure of the key distribution metadata and an explanatory diagram of the description contents. The key distribution metadata 47 is metadata for distributing information related to the encryption key of the content, and when performing a limited reception in which the content is a pay broadcast, only users who have contracted with the broadcasting company can receive the content. Is metadata that includes the information of. The key distribution metadata 47 is metadata attribute information 3 for distinguishing it from other metadata.
7, encryption information 32 regarding encryption of metadata itself,
It includes content key information 48 such as a content ID and a content encryption key Kk46. As for the encrypted part, the content key information 48 such as the content key Kk46 is encrypted and distributed on the transmission side. As for the encryption key, the key distribution metadata 47 is metadata for paid content, and when performing limited reception in which only a user who has contracted with the business operator can receive, a unique business operator key Kw49 is used for each business operator. ,
In the case of metadata for free content that can be viewed by users other than the contractor, a system key Ksy1_41 common to all receiving terminals is used. Further, information such as a business operator ID and a target contract code for realizing conditional access is stored in the content key information 48, and is encrypted and distributed.

In the present invention, the content key Kk used for encrypting the content and the content key Kk used for encrypting the metadata for storage and reproduction are described as the same value, but they may be intentionally set to different key values. . In this case, for example, the content key KK1 and the content key KK2 are generated by multiplying the content key Kk by a certain value in an algorithm.
Is generated, and the content is encrypted with the content key KK1 and the storage / playback metadata is encrypted with the content key KK2. Then, the values used when generating the content key Kk, the content key KK1, and the content key KK2 are stored in the key distribution metadata and the storage / playback metadata, and the same as the transmission side owned by the receiving terminal side. It is also possible to derive the content key KK1 and the content key KK2 by an algorithm and to decrypt them.

(Metadata List) FIG. 13 is an explanatory diagram of the classification of the metadata list. The metadata list 50 is the EPG in the carousel stream being distributed.
Is a table showing the distribution positions of the metadata for storage, the metadata for storage and reproduction, the metadata for key distribution, and the metadata for pre-contract, and is information necessary for the metadata and content reception processing. Basically multiple distribution of each metadata
It is stored in the start-up module (module whose module_id is 0x00) in the default ES in the ES and distributed. An EPG metadata list 51 describing the distribution position of the EPG metadata, a storage reproduction metadata, a storage reproduction metadata list 52 describing the distribution position of the corresponding key distribution metadata, and a pre-contract metadata It is classified into a pre-contract metadata list 53 that describes a distribution position.

(EPG metadata list, storage / playback metadata list) FIG. 14 shows an EPG metadata list,
FIG. 4 shows an explanatory diagram of the structure and description contents of a storage / reproduction metadata list. Both the EPG metadata list 51 and the storage / playback metadata list 52 have the same description contents and structure for describing the distribution position of the metadata for the content. PSI for acquiring content and metadata
And information for accumulating difference metadata when the metadata stored in the receiving terminal is updated with the metadata in the distribution stream. Metadata list attribute information 54 such as a version for identifying update of information on the receiving terminal side, a content ID for each content, a corresponding metadata ID, and a distribution position.
It includes list information 55 such as component_tag, module_id, and version of metadata. EPG metadata list 51
Includes information on contents distributed by other TSs and information for a certain period of time, for example, one week depending on operation, due to its characteristics used for EPG display. On the other hand, the storage / playback metadata list 52 describes information about the content being distributed in the selected TS and information about the content to be distributed next by operation. In addition, since both metadata lists do not always include information necessary for the receiving process of the receiving terminal and information that requires protection, the metadata list is basically distributed without encryption.

(Pre-Contract Metadata List) Next, FIG.
FIG. 5 shows the structure of the pre-contract metadata list and an explanatory diagram of the description contents. Since the pre-contract metadata list is information on the distribution position of the pre-contract metadata attached to the user receiving the service, the EPG metadata list 51 and the storage / playback metadata list 52
And some description contents are different. As similar information, a metadata list 5 indicating the version of the metadata list itself, etc.
4 includes list information 5 composed of a personal ID, a terminal ID, a version of the pre-contract metadata, a distribution position, and the like targeted by the pre-contract metadata.
6 parts are included. In the pre-contract metadata list, only the description of pre-contract metadata for each user is provided to the service provider that provides services in the TS to be distributed.

(System Key Update Metadata) Next, FIG.
FIG. 6 shows an explanatory diagram of the structure and description contents of the metadata for updating the system key. The system key update metadata 57 is
Metadata for updating the system key Ksy1, which is a key common to all the receiving terminals stored in the receiving terminal, and is metadata attribute information 3 for distinguishing from other metadata.
7, encryption information 32 regarding encryption of metadata itself,
The system key information 58 includes information such as a system ID corresponding to a system key to be updated, a changed system ID, a system key, and an update timing. The encryption part is
The updated system key Ksy3, system key information 58 including information such as change timing, and the like, and the encryption key uses a system key Ksy2_59 registered in the receiving terminal in advance as a spare system key. The system key update metadata 57 is information distributed in common to all TSs, and does not include a plurality of metadata at a time. Therefore, the receiving terminal does not need a metadata list for receiving the system key update metadata 57, and thus only the system key update metadata 57 is transmitted by the carousel. However, the system key update metadata 57 is not a car sale.
Although distribution in a PES stream is possible, in the present invention, as an example, description will be made assuming that distribution is performed as a carousel. The above is the data distributed from the sending side.

4. Distribution Method Next, a distribution method of each of the above-described data in the present comprehensive data distribution service will be described. (Stream Configuration) FIG. 17 is an explanatory diagram of the configuration of a data stream distributed in the network. The stream configuration of the entire network to which the comprehensive data distribution service content is distributed will be described with reference to FIG. FIG.
7 is a network 60 for performing the comprehensive data distribution service
Is an example in which is a CS digital broadcast using a CS satellite. As described above, the network 60 includes a plurality of TSs 61, that is, TSs corresponding to broadcast stations. TS n62 in FIG.
Is a software bug fix for the receiving terminal, not the broadcasting station that transmits the content, and a dedicated TS (engineering slot) for distributing information commonly used by all broadcasting stations
It will be described as. In satellite digital broadcasting, all data is stored and delivered in the payload (data storage portion) of a TS packet. The PID value stored in the header of the packet differs depending on the data stored in the TS packet. In satellite digital broadcasting, it is a method of multiplexing and distributing TS packets consisting of a plurality of PIDs. TSP having the same PID value as the stream group shown in FIG. 17 is connected in the time direction
This indicates that a plurality of ESs (elementary streams) exist. The TS 61 is information indicating grouping when multiplexed by a plurality of TS packets, and is a unit that is grouped into units of one broadcast station or the like. In some cases, a TS is composed of a plurality of broadcasting stations depending on the operation, but in the present invention, a description will be given as a unit grouped for each broadcasting station. The network 60 is a unit for transmitting a similar service composed of a plurality of TSs, and is a unit given to the entire transmission path such as a BS digital broadcast or a CS digital broadcast.

The structure of the stream distributed by each TS, which is a broadcasting station that distributes the comprehensive data distribution service content, includes a PSI stream group 63 that distributes each table of PSI, pre-contract metadata, and pre-contract metadata list. , A storage / playback metadata stream group 65 for delivering storage / playback metadata, key delivery metadata, and storage / playback metadata lists,
EP that distributes EPG metadata and EPG metadata list
It includes a G metadata stream group 66 and a content distribution stream group 67 for distributing content. The dedicated slot TS n — 62 includes a PSI stream group and a system key update metadata stream group 68 that distributes system key update metadata.

(PSI Stream Group) Next, FIG. 18 is an explanatory diagram of a detailed stream configuration in the PSI stream group 63. The PSI stream group 63 is the PSI table described above.
It includes a PAT stream 69 storing a PAT table, an NIT stream 70 storing an NIT table, and a PMT stream 71 storing a PMT. When there are a plurality of channels in a broadcasting station, that is, in a TS, there are a plurality of PMTs, so the PMT stream 71 is also composed of a plurality of streams. Also, each
When performing a service similar to BS digital broadcasting which is an existing broadcasting service in TS and performing pay broadcasting, there is a case where a CAT stream, an EMM stream, and an ECM stream exist because the existing conditional access system is used . Further, when a plurality of networks such as a BS digital broadcast and CS digital broadcast shared receiving terminal can be used, the NIT stream 70
In some cases, there may be a plurality of NIT tables indicating information on each network.

(Pre-Contract Metadata Stream Group) FIG. 19 is an explanatory diagram of a detailed stream configuration in the pre-contract metadata stream group. Next, the pre-contract metadata stream group 64 will be described with reference to FIG. The pre-contract metadata stream group 64 exists in the TS only when delivering the pre-contract metadata,
There is no pre-contract metadata stream group 64 in a TS that delivers only free broadcast services that do not use pre-contract metadata. The pre-contract metadata stream group is basically one of the pre-contract metadata default ES72.
When it is determined that the number of pre-contract metadata 30 in one carousel increases and the receiving terminal-side pre-contract metadata 30 acquisition process is delayed, a plurality of pre-contract metadata 30 The metadata 30 can be distributed and distributed in a plurality of streams. However,
In the case of operating with a plurality of streams, the case of operating with one stream is used for both the pre-contract metadata list 53
Is stored in the start-up module 74 in the pre-contract metadata default ES 72 and distributed for describing all pre-contract metadata distributed in the TS. Therefore, only the pre-contract metadata 30 is stored and distributed in the pre-contract metadata ES 73 other than the default ES. As described above, the default ES and other ESs are identified by the component_tag in the stream identification descriptor in the PMT.
Is identified by the tag value of Also transmit each stream
Similarly, the PID of the TS packet is specified by the ES_PID in the PMT.

(Storage and Playback Metadata Stream Group) FIG. 20 is an explanatory diagram of a detailed stream configuration in the storage and playback metadata stream group. Next, the storage / playback metadata stream group 65 will be described with reference to FIG. The storage / playback metadata stream group 65 exists only when the comprehensive data distribution service content is distributed within the TS, and does not exist when only the existing type service content is distributed. The storage / playback metadata stream group 65 basically includes only one stream of the storage / playback metadata default ES 75 when only the storage / playback metadata 42 and the key delivery metadata 47 for the content being delivered are delivered. In addition, in the case of distributing the storage / reproduction metadata 42 and the key distribution metadata 47 for the content to be distributed next time, the number of metadata to be distributed in one carousel increases, and the number of metadata to be distributed to the receiving terminal increases. If it is determined that the metadata acquisition process on the side becomes slow, the metadata for the next distribution-scheduled content can be distributed as the storage / reproduction metadata ES76 which is another ES. However, in both the case where the operation is performed with a plurality of streams and the case where the operation is performed with one stream, the storage / reproduction metadata list 52 stores the distribution position of the metadata for all the contents being distributed in the TS and the distribution of the metadata for the content to be distributed next time. In order to describe the position, the metadata is stored in the startup module 74 in the storage / reproduction metadata default ES 75 and distributed. Therefore, only the metadata is stored in the storage / reproduction metadata ES 76 other than the default ES, and the metadata list is not stored. The default ES is distinguished from other ESs by PMT as described above.
It is identified by the tag value of component_tag in the stream identification descriptor in the file. Similarly, the PID of the TS packet transmitting each stream is specified by the ES_PID in the PMT. Storage / reproduction metadata 42, key distribution metadata 4
7, the storage metadata 42 and the key distribution metadata 47 for the same content are stored in one module (for example, module 1 in FIG. 20), and the storage / reproduction metadata and key distribution metadata in the module are stored. The data division of the metadata is indicated in the resource list inserted in the module, thereby enabling the receiving terminal to simultaneously acquire the storage metadata 42 and the key distribution metadata 47.

(EPG Metadata Stream Group) FIG. 21
FIG. 3 shows an explanatory diagram of a detailed stream configuration in the EPG metadata stream group. Next, the EPG metadata stream group 66 will be described with reference to FIG. The EPG metadata stream group 66 exists when performing a service of distributing the comprehensive data distribution service content in the TS,
It does not exist in TS that distributes only existing service contents. The EPG metadata stream group 66 includes not only the EPG metadata 81 for the content in the selected TS but also the EPG metadata 82 for the content to be distributed in another TS, and the distribution for one week, for example, defined by the operation. In order to distribute EPG metadata for scheduled content and EPG metadata for content to be distributed for one week or more specified by the business operator, the content is configured by a plurality of streams instead of a single stream. However, in order to improve the process of recognizing the distribution position of the EPG metadata of the receiving terminal, the EPG metadata list 51 includes a start-up module in the EPG metadata default ES77 which is first acquired by the receiving terminal among a plurality of streams. 74 for distribution. In addition, considering the scheduled distribution date and distribution location of the content targeted for the EPG metadata, one week of the content to be distributed in the own TS as shown in FIG.
EPG metadata default ES77, EPG metadata ES78 for one week of content to be distributed in other TSs, and EPG metadata E for one week or more of content to be distributed in the own TS
S79, EPG for one week or more of contents scheduled to be distributed in other TS
It can be operated separately from the metadata ES80. The identification of the default ES and each other ES is PMT as described above.
It is identified by the tag value of component_tag in the stream identification descriptor in the file. In addition, the specification of the PID of the TS packet transmitting each stream is performed when the receiving terminal is started, considering that the EPG metadata list 51 is acquired at a certain fixed period, and the receiving terminal can identify the PID before receiving the PMT. Therefore, it is fixed according to the operation rule, and the acquisition performance of the EPG metadata list 51 can be improved.

(System Key Update Metadata Stream Group) FIG. 22 is an explanatory diagram of a detailed stream configuration in the system key update metadata stream group. Then dedicated
Stream group 6 for system key update distributed only within TS
8 will be described with reference to FIG. The system key update stream group 68 is a stream that exists only in a dedicated slot when a system key update request is generated and the system key update metadata 57 is distributed in the network. Basically, there is only one system key update metadata distributed at a time, so there is only a single system key update metadata default ES83. When distributing, it is also possible to perform distribution by another ES84. The module for storing the system key update metadata 57 is distributed by the start-up module 74 in each ES. It is divided into a plurality of modules and distributed. In this case,
Use the module link descriptor in DII. As described above, the default ES and each of the other ESs are identified by the tag value of the component_tag in the stream identification descriptor in the PMT. The PID of the TS packet that transmits each stream
Specify the TS in the system key update _TS descriptor described in the NIT, and specify the ES_ in the PMT transmitted in the specified dedicated TS.
Indirectly specified by PID.

(Content Delivery Stream Group) FIG. 23
FIG. 2 shows an explanatory diagram of a content distribution stream group. Next, the content distribution stream group 67 will be described with reference to FIG. The content distribution stream group is composed of a single stream or a plurality of streams depending on the amount of content to be distributed. The format of the stream for distribution differs depending on the type of the element constituting the content. Elements constituting the stream-based content 85 are delivered in a stream of a PES (paketized elementary stream) format, and elements constituting the file-based content are delivered in a data carousel 93 in the same manner as metadata. PES format streams are also MPEG2-Vid
Video E that distributes video elements such as eo and MPEG1-Video
S87, audio ES88 for distributing audio elements such as MPEG2-AAC, MPEG2-BC, etc., synchronous ES90 which requires synchronization with other streams such as subtitle data, and asynchronous ES91 which does not need to synchronize with other streams such as character superimposition. , Are classified into ES92, etc. when delivering event messages, and the type of each ES is
It is defined by stream_type in PMT and transmits each data
The PID of the TS packet is also specified by the ES_PID in the PMT. The comprehensive data distribution service content is configured by combining these ESs in one stream or a plurality of streams. A data carousel that delivers file-based content can store a plurality of contents in order to define an element configuration in the content in metadata. The above is the data distributed from the transmitting side to the receiving terminal and the distribution method.

5. Reception Processing Next, reception processing on the receiving side of data distributed by the above-described distribution method will be described. (PSI Reception Processing) FIG. 24 is an explanatory diagram of the PSI reception processing flow in the receiving terminal. The PSI reception process is performed when the receiving terminal displays the default channel on the TV at startup, when the user selects the content being distributed by EPG, when the channel is selected, when the channel is directly specified by the remote control, etc. This is a basic process when receiving. Therefore, START 400, which is the start of the PSI receiving process, is started when the receiving terminal is started, when the user is distributing the content, and when the channel is selected, and the tuner portion in the receiving terminal sets parameters such as a receiving frequency for receiving a default TS. Has been performed. The PAT receiver 401 receives a TS packet (PAT stream) sent with a PID of 0x0000 and assembles a PAT in order to confirm whether data for the selected channel and content is distributed in a TS set as a default. In the Service_id search 402, the assembled PAT
Information about the channel, content selected within,
That is, it identifies whether the channel and the content selected in the set TS are distributed. When the receiving terminal is started, referring to Program-number in FIG. 4, there is basically a selected channel, seivice_id, in the PAT for selecting a default channel. Accordingly, when the selected channel exists, the PMT receiving 407 describing the information of the channel is received. Therefore, the PMT receiving 407 operation is performed based on the PID information of the TS packet transmitting the PMT specified in the PAT.

On the other hand, if the information for the selected channel does not exist in the PAT in the Service_id search 402,
The receiving terminal determines that the service of the selected channel is not performed in the set TS, and performs NIT reception 403 in order to recognize which TS has the selected channel distributed. NIT is TS packet with PID 0x0010 and all TS
, The receiving terminal receives the TS packet with the PID of 0x0010 in the set TS and assembles the NIT. At this time, as shown in FIG. 5, when the system key update TS descriptor 22 exists in the NIT 404, the receiving terminal needs to preferentially acquire the system key update metadata, so that the system key update Metadata reception processing 41
Perform 0. If the system key update TS descriptor does not exist in the NIT, the service list descriptor 23 identifies which TS the selected channel is distributed by as shown in FIG. 5 in the NIT. At this time, the service type (Service Type) performed on the selected channel can also be identified by the service list descriptor 23, and a service type other than the storage type service which is a feature of the present comprehensive data distribution service is used. If it is specified, the existing type reception processing 409 currently specified by the standard is performed.
When the storage type service is set, the reception processing in the comprehensive data distribution service is performed, and the service distribution TS identified by the service list descriptor 23 in the NIT is performed.
Information, set by the satellite distribution system descriptor
The parameter information for changing the TS to the service delivery TS is obtained, and the parameter is set in the tuner of the receiving terminal. When the tuner of the receiving terminal is set to the service delivery TS, the TS packet whose PID is 0x0000 is received in the set TS as in the operation of the PAT reception 401, and the PAT in the set TS is received. Receive 406. PAT
As shown in FIG. 4, a TS packet of the PID specified by the PMT_PID corresponding to the selected channel stored in the PAT is received, and information of the selected channel is described. Assembling PMT 40
7. Finally, as shown in FIG.
By analyzing 408 T, the receiving terminal selects a receiving processing flow to be performed next. The above is the PSI receiving process in the present comprehensive data distribution service.

(Pre-Contract Metadata Receiving Process) FIG. 25
FIG. 7 shows a flowchart of the pre-contract metadata receiving process. Next, regarding the pre-contract metadata reception processing, FIG.
This will be described with reference to FIG. What is the pre-contract metadata reception processing?
After performing the PSI receiving process, the component_tag (0xA
0) is the stream identification descriptor 27 in the PMT shown in FIG.
This is a process that is performed with higher priority than other processes when specified by. Therefore, in the PMT analysis 408, first, it is determined whether or not the metadata ES for the prior contract exists 41
One. If the pre-contract metadata default ES does not exist, the pre-contract metadata reception process ends (END41).
6) Then, the subsequent content reception processing is performed. If the pre-contract metadata default ES exists, the PID corresponding to the pre-contract default ES PID specified in the PMT
Of the distributed TS packet, that is, the acquisition 412 of the pre-contract metadata default ES. Since the pre-contract metadata default ES is distributed in the carousel format (the carousel format is specified in the PMT), the receiving terminal first acquires a module (module_id = 0) which is a startup module. The sending side stores and distributes the pre-contract metadata list to the start-up module in the pre-contract metadata default ES as described above, so the receiving terminal acquires the start-up module as a result and obtains the pre-contract metadata. A list 413 is obtained. The receiving terminal that has acquired the pre-contract metadata list identifies the information addressed to the own terminal in the list information in the metadata list, that is, identifies 414 whether or not the terminal ID previously owned in the receiving terminal exists in the metadata list. If the owning terminal ID does not exist, the receiving terminal recognizes that the pre-contract metadata addressed to the own terminal is not distributed, ends the pre-contract metadata receiving process (END 416), and executes the content receiving process and the like. Perform other processing. If the owning terminal ID exists, the receiving terminal recognizes that the pre-contract metadata addressed to the own terminal is being distributed, and the portion corresponding to the owning terminal ID of the list information in the metadata list Obtain the distribution position, version, etc. of the pre-contract metadata, and if the pre-contract metadata needs to be obtained, extract the stream and module ID where the pre-contract metadata is distributed from the distribution position information Then, the corresponding pre-contract metadata is acquired 415. The preceding is the pre-contract metadata reception processing in the present comprehensive data distribution service.

(EPG Metadata Reception Processing) FIG.
FIG. 4 is a flowchart illustrating a PG metadata reception process. Then EP
The G metadata receiving process will be described with reference to FIG. The EPG metadata reception process is a process that is performed at a certain fixed period or the like when the receiving terminal is started, as a process different from the PSI process. Therefore START4 of EPG metadata reception processing
When the receiving terminal is activated, the 17 trigger is performed at a certain period determined by the operation. Since the metadata for EPG is obtained separately from the PSI processing, the receiving terminal directly receives the TS packet distributed by the PID specified in the operation,
Acquisition of metadata default ES for 418 is performed. Since the metadata default ES for EPG is a stream in the carousel format, the receiving terminal first acquires a module that is a startup module in the carousel. On the transmitting side, as described above, the EPG metadata list is stored in the startup module in the EPG metadata default ES and distributed, so that the receiving terminal that has acquired the startup module acquires the EPG metadata list 419 as a result. Will be done. The receiving terminal that has acquired the EPG metadata list has previously acquired and stored the EPG
The version number of the EPG metadata is collated with the version list of the metadata for EPG, and it is determined 420 whether the metadata for EPG currently being distributed includes an updated part of the metadata for EPG stored in the receiving terminal. At this time, after purchasing the receiving terminal, etc.
If the EPG metadata list does not exist, it is handled in the same way as the version number mismatch, and it is assumed that all EPG metadata has been updated, and the operation is performed. If the version number in the EPG metadata list matches, the previously acquired EPG
Since there is no update from the metadata for EPG, the EPG metadata reception process ends (END 423). If the version numbers do not match, it is recognized that there is EPG metadata updated from the previously acquired EPG metadata, and the ID of the EPG metadata described in the acquired EPG metadata list information, The version number of each EPG metadata is compared with the corresponding part of the stored EPG metadata list, and the EPG whose version number is updated
Metadata for EPG that needs to be replaced due to time change, content change, and metadata for EPG to be added with a new ID are extracted, and the distribution position information stored in the list information is used. EPs that need to be updated or added
421, it is possible to recognize information such as a stream to which the G metadata is distributed and a module ID. The receiving terminal that has recognized the distribution position can acquire the corresponding EPG metadata from the distribution stream group 422. At this time, the receiving terminal accumulates the acquired EPG metadata and also acquires and accumulates the EPG metadata list, so that the information indicating the latest EPG metadata status in the receiving terminal at the next EPG metadata receiving process And The above is the EPG metadata reception processing in the present comprehensive data distribution service.

(Content Receiving Process) FIG. 27 is a flowchart for explaining the content receiving process. Next, content reception processing will be described with reference to FIG. The content reception process is a process performed after the PSI process and the pre-contract metadata reception process described above, and specifically, is a process of receiving storage / playback metadata, key distribution metadata, and content. Therefore, the start of the content receiving process (START 424) is after the PSI receiving process and the pre-contract metadata receiving process. First, it is determined 425 whether the metadata default ES for storage and reproduction exists in the PMT for the selected content or channel. For example, s which is the stream format designation information in the PMT 24 shown in FIG.
It is identified by tream_type26. If the metadata default ES for storage and playback does not exist, it means that the content corresponding to the storage type service, which is the feature of this comprehensive data distribution service, is not distributed in the selected channel. The receiving terminal performs the existing type receiving process 409. If there is a default ES for metadata for storage and playback, componen indicating the existence
When the t_tag (0x80) is specified by the stream identification descriptor 27 in the PMT 24 shown in FIG. 6, the receiving terminal receives the TS packet specified by the corresponding ES_PID, that is, the default of the metadata for storage and reproduction. ES 426 is performed. The metadata default ES for storage / playback shown in FIG. 20 is distributed in the carousel format (the stream format is specified in the PMT) as described above, so that the receiving terminal first acquires the startup module. On the sending side, default ES for metadata for storage and playback
In order to store and distribute the metadata list for storage and reproduction in the startup module, the receiving terminal eventually acquires the metadata list for storage and reproduction.
27. As shown in FIG. 20, the receiving terminal that has acquired the storage / playback metadata list 52 by Module 0_75 sets the storage / playback metadata 42 for the content selected by any of Modules 1 to n, Content ID selected to obtain metadata 47
Search 428 for information corresponding to (content_id). In this case, if the channel is specified directly, if the default channel only is specified at the time of starting the receiving terminal, etc., if the content is not specified only by the channel specification (service_id specification), the default content in each channel is specified As a matter of fact, the receiving terminal operates. FIG.
As shown in (2), if there is no content ID selected in the storage / playback metadata 42, or if there is no default content, it is assumed that broadcasting is suspended and the content reception processing is terminated (END432). Selected content I
D, or if there is default content,
The receiving terminal distributes streams and modules required by the metadata distribution position (Locator) corresponding to the corresponding content described in the list information as shown in FIG. Is recognizable, the module ID is acquired, and the corresponding module is acquired 429. Since the transmitting side stores and reproduces the metadata for storage and reproduction and the metadata for key distribution in each module, the receiving terminal acquires the metadata for storage and reproduction and the metadata for key distribution at this time. Data delimitation of the metadata for storage and reproduction and the metadata for key distribution in the module is performed by the resource list in the module. Next, the receiving terminal processes the acquired storage / playback metadata and key distribution metadata by the RMP function in the receiving terminal, and determines permission to receive the content.
30. For example, the RMP function encrypts key distribution metadata as shown in FIG. 12 with a system key Ksy1 (for free broadcast) or a business key Kw (for pay broadcast) to obtain a content key Kk. Thereafter, the RMP function encrypts the storage / reproduction metadata with the content key Kk as shown in FIG. 11, and determines permission to receive the content based on the usage restriction information, the contract information, the billing information, and the like. Content reception is RMP
If rejected by the function, it means that the user does not have the viewing right to the selected content, so the content reception processing is terminated (END 432). If it is determined that the content can be received (if permitted) by the RMP function, the distribution position information of each element constituting the content described in the metadata for storage and playback, the specification information of the default element (when the content is selected) Data position to be presented first), ES_PI specified in PMT
Element reception, that is, content reception, is performed 431 based on the information of D. The above is the content reception processing in the present comprehensive data distribution service.

(System Key Update Metadata Receiving Process)
FIG. 28 is a flowchart for explaining the system key update metadata receiving process. Next, system key update metadata reception processing will be described with reference to FIG. The process of receiving metadata for updating a system key is an NIT as shown in FIG.
This is a process that is preferentially performed on the receiving terminal side when the system key update TS descriptor 22 exists in the terminal. Therefore, the reception process of the system key update metadata is started (START 43
3) is started when the system key update TS descriptor is recognized in the NIT reception processing during the PSI processing described above. The receiving terminal that recognizes the system key update TS descriptor stores the TS_ID of the dedicated slot for distributing the system key update metadata stored in the system key update TS descriptor, and the satellite distribution system descriptor in the NIT. The parameter information for setting the tuner to the described TS is extracted, and the parameter of the TS for distributing the system key update metadata to the tuner is set 434. The receiving terminal is in the set TS
Receive TS packet delivered with PID 0x0000, that is, P
Upon receiving the AT, the P stored in the PAT as shown in FIG.
The PMT for identifying the PID of the stream to which the system key update metadata is distributed is acquired by the MT_PID. Thereafter, the system key updating metadata default ES which is the component_tag (0x80) defined by the stream identification descriptor 27 in the PMT as shown in FIG. 6 is recognized, and the TS packet distributed by the corresponding ES_PID is received. That is, a series of PSI processing 435 for acquiring the system key update metadata default ES, a PMT analysis processing 436,
Acquisition processing 4 of metadata default ES for system key update
Perform 37. Since the metadata for updating the system key is transmitted in the carousel format (the format of the stream is specified in the PMT), the receiving terminal first acquires the startup module. On the sending side, the system key updating metadata is stored and distributed in the startup module of the system key updating metadata default ES. At this point, the receiving terminal side acquires the system key updating metadata. The above is the reception processing of the system key update metadata in the present comprehensive data distribution service. Therefore, by performing these receiving processes, it becomes possible to receive and store each metadata and content defined for protecting the rights in the present comprehensive data distribution service.

6. Metadata Items Related to Rights Next, items used in the comprehensive data distribution service for processing related to rights that require protection, such as encryption and tampering prevention processing, stored in each metadata described above will be described. Items used for processing related to rights are described in personal information and contract information described in the metadata for pre-contract described above, use restriction information described in metadata for EPG, and metadata for storage and reproduction. Usage limit information, content key encryption information, contract information, billing information, content key information described in key distribution metadata, system key information described in system key update metadata, each metadata This is data or the like stored in the described encryption information or the like. As described above, items used for processing related to rights may be described in binary according to the processing performance of the receiving terminal. In the present invention, a case where items used for processing related to rights are described using binary description will be described. The information used for the processing related to rights includes information related to security such as encryption, information related to the expiration date of the content, information for controlling storage, information for controlling reproduction, information for controlling external output, Information for controlling the movement of content, information for controlling copying of content, information for controlling use within the home network, printout, content modification, information on user access restriction, information on billing , And information on contracts.

(Information on Security) FIG.
FIG. 3 illustrates an explanatory diagram of information regarding security. First, information relating to security among processing information relating to rights defined in this comprehensive data distribution service will be described with reference to FIG. The security level is information for granting a content license and a metadata license only to an application having the security level information indicated by the bit for an application or the like using the content on the sending side. Five levels are possible. This security level enables authentication of the application of the receiving terminal. The content encryption identification is information indicating whether or not the content is encrypted. When there is no encryption, the content encryption method bit defined later is ignored. Similarly, the metadata encryption identification is information for identifying whether the metadata is encrypted. If there is no encryption, the metadata encryption method bit is ignored. A key value (encryption key) is a key value used for encrypting content, metadata, etc.
Alternatively, it is used when distributing the value of a key used for other purposes. The key type is information indicating the type of key distributed by the key value. The digital watermark is information indicating whether a digital watermark is used for the content.

(Information on Content Expiration Date) FIG. 39 is an explanatory diagram of information on content usage expiration date. Content expiration date (absolute time)
Is information that sets, for example, the usable expiration date of the content in units of seconds, calculated from 0:00 on January 6, 1980. When the time in the receiving terminal reaches the set value, the content cannot be viewed. For example, if the reset bit included in “etc” in the usage restriction information in FIG. 11 is not resettable, the receiving terminal calculates the total time of the primary usage, the secondary usage, and the subsequent nth usage. Then, the permission of the use of the content is determined by comparing the set value. If the reset bit is resettable, primary use, secondary use,
The determination is made based on the time of each of the subsequent n-th uses.
This information is a value set at the content sending side or at the time of production. The content expiration date (relative time) is an item for setting the time until the content usage expiration calculated in minutes from the time when the content is received by the receiving terminal. When the time in the receiving terminal reaches the set value, the content cannot be viewed. If the reset bit is not resettable, the receiving terminal calculates the total time of the primary use, the secondary use, and the subsequent n-th use, compares the total time with the set value, and determines permission to use the content. If the reset bit is resettable, the determination is made based on the times of primary use, secondary use, and subsequent n-th use. This information is a value set at the content sending side or at the time of production. The content expiration date (reproduction time) is an item for setting the total reproducible time of the content in minutes.
When the time in the receiving terminal reaches the set value, the content cannot be viewed. If the reset bit is not resettable, the receiving terminal performs primary use and secondary use, and n thereafter.
The total time of the next use is calculated and compared with the set value to determine whether the use of the content is permitted. If the reset bit is resettable, the determination is made based on the times of primary use, secondary use, and subsequent n-th use. This information is a value set at the content sending side or at the time of production.
Secondary usage content expiration date (absolute time), secondary usage content expiration date (relative time), secondary usage content expiration date (reproduction time)
This is information for the next use, and the contents are the same as those described above. If at least one of the information regarding the expiration date of the content has reached the set time, the content cannot be used. Expiration date of rights (absolute time)
Is information for setting the time limit of the content right calculated from 0:00 on January 6, 1980 in seconds.
When the set value is reached, the right to the content is lost, and the content viewing contract fee for the user can be reduced. If all the bits are 1 in each of the items related to the usage period, the receiving terminal determines that there is no restriction.

(Information on Storage Control) Next, FIG.
FIG. 3 is an explanatory diagram of information on accumulation control. The playback mode is information that indicates the playback mode of the content. Only real-time playback is possible, only playback after storage is possible, both
It is possible to specify information such as both impossible. If both of them are not permitted, the receiving terminal does not perform processing such as reproduction in the receiving terminal and outputs the data to the outside through. It is possible to perform a unique service or the like using a device other than the receiving terminal. The time shift is information indicating permission for the time shift viewing of the content, and this bit is information that is valid only when the reproduction mode is real-time, and is valid only when both are possible. The storage unit is information indicating the minimum unit that can store the content to be stored. If the storage unit is a metadata unit, only the unit defined in the metadata can be stored, and there is no limit. In this case, the information indicates that the storage of each element constituting the content can be performed without depending on the metadata. The storage method is information indicating a storage method at the time of storing the content, and it is possible to designate accumulation, overwriting, no limitation, and the like. Accumulation indicates that data storage processing is performed in the free space area without performing data overwrite processing. The storage location restriction indicates the restriction on the storage location when storing the content. Only storage media built into the receiving terminal can be used as storage locations.
It is possible to specify that only D-VHS is allowed, no limit is set, and the like, and the receiving terminal built-in storage medium refers to a storage medium built in by default. When a storage medium is added, the device is treated in the same way as long as the device is regarded as built-in by the receiving terminal. The storage medium specification is an item for specifying a storage medium when storing the content. As the storage medium, a built-in storage medium, a removable medium, and no limitation can be designated. It is assumed that storage location restriction information has priority in storage medium designation and storage location restriction. This makes it possible to prevent a malfunction of the receiving terminal even when inconsistency occurs in the information. The storage location specification is an item for specifying a storage location such as a directory when the content is stored in a storage medium built in the receiving terminal, and can be set to a business area and no restrictions. When the business area is set, the information is accumulated in the area allocated to each business. The storage location specification bit is valid only when the storage medium specification is a storage medium built into the receiving terminal and there is no restriction.

(Information on Reproduction Control) Next, FIG.
FIG. 4 shows an explanatory diagram of information related to reproduction control. The reproducible count is information indicating the total reproducible count of the content. When the time in the receiving terminal reaches the set value, the content cannot be viewed. If the reset bit indicates that resetting is disabled, the receiving terminal calculates the total number of times of primary use, secondary use, and subsequent n-th use, compares the total number with the set value, and determines permission to use the content. If the reset bit is resettable, the determination is made based on the number of times of primary use, secondary use, and subsequent n-th use. The number of times of secondary use reproduction is information indicating the number of times of secondary use reproduction possible with respect to the number of times of reproduction possible, and has the same contents. The reproduction unit is information indicating a reproducible unit of the content to be reproduced, and a metadata unit and no limit can be set.
If a metadata unit is specified, the content is reproduced according to the contents defined in the metadata. If no limit is set, reproduction of each element constituting the content can be performed. The pause allowable time indicates a time during which pause can be performed during one content reproduction. It is also possible to limit the time by regarding the rewinding process as a pause process. In the pause process, the content playback process can be temporarily stopped without terminating the content playback process.
This is an effective process when there is a limit on the number of times the content can be played. By setting the possible time of the pause process, it is possible to prevent the pause process from being performed for a long time or to perform the rewind process more than necessary. The setting is made in minutes. The reproduction start possible time is, for example, 1
This is information that permits the start of reproduction of the content calculated from 0:00 on January 6, 980, and is effective when the content is distributed in advance.

(Information on Control of External Output) Next, FIG.
FIG. 2 shows an explanatory diagram of information relating to control of external output. The output device authentication is information indicating whether authentication processing with a device that outputs data is necessary. The output permission (analog) is information for specifying whether or not the receiving terminal can output the analog data of the content. The output permission (digital) is information indicating whether digital data of the content can be output from the receiving terminal. As the type of output permission, it is possible to set such that output is impossible, only encrypted data encrypted at the time of distribution or in the receiving terminal can be output, only plaintext can be output, and both encrypted data and plaintext data can be output. The encrypted data specified here does not include encryption applied to the output transmission path. Transmission path encryption (digital) is information indicating whether it is necessary to apply transmission path encryption when outputting content. The protection system (analog) is information that specifies whether to use a copy protection system for analog data, which is a function of the device at the output destination. The resolution is information indicating the resolution of the output content, and as the resolution, it is possible to set both HD and SD to allow output and only SD to allow output. To output HD content when only SD is permitted, down-conversion processing is performed, and output after conversion to SD is performed.

(Information on Content Movement) Next, FIG. 43 is an explanatory diagram of information on content movement. The movement unit is information indicating a unit in which the content to be moved can be moved. If the movement unit is set in the metadata unit, the content is defined according to the contents defined in the metadata and if there is no limit, the content is set. Can be moved in units of each element or the like. The number of times of movement (analog) before the contract is information indicating the number of times the analog content can be moved before performing the contract processing. Move refers to an operation in which data before the move is deleted and only the data after the move exists. Number of times of movement before contract (digital)
Is information indicating the number of times digital content can be moved before contract processing is performed. Move refers to an operation in which data before the move is deleted and only the data after the move exists.
The number of possible movements after the contract (analog) is information indicating the number of possible movements of the analog content after performing the contract processing. Move refers to an operation in which data before the move is deleted and only the data after the move exists. The number of times of movement after contract (digital) indicates the number of times that digital content can be moved after contract processing is performed. Move refers to an operation in which data before the move is deleted and only the data after the move exists.

(Information on Copy Control) Next, FIG.
FIG. 7 shows an explanatory diagram of information on copy control.
The copy unit is information indicating a unit in which content can be copied. If a metadata unit is specified, a unit defined by metadata can be copied. If there is no limit, each element constituting the content can be copied. Copying of units and the like becomes possible. The pre-contract copyable generation is information indicating a copyable generation of the content before performing the contract process. The number of possible copies before contract (analog) and the number of possible copies before contract (digital) are information indicating the number of possible copies of analog and digital before contract processing. The copyable generation after contract is information indicating the copyable generation after contract processing. The permitted number of copies after contract (analog) and the permitted number of copies after contract (digital) are information indicating the permitted number of analog and digital copies after the contract processing. If any one of the copyable generation and the copyable number of the information regarding the copy control becomes uncopyable, the receiving terminal cannot perform all copy processing.
In addition, the number of copies that can be made can be set differently before and after the contract, so that the pre-contract content is widely scattered, the number of parameters for collecting more contract fees is increased, and the post-contract content is restricted so that it is not scattered Flexible service such as calling is made possible. The gift contract copy is information indicating whether a gift contract is possible or not. When the gift contract is copied, a re-viewing contract is made and the current reproduction time and the number of reproductions are reset to zero.

(Home network, printout,
FIG. 45 is an explanatory diagram of home network, printout, modification, and other information related to control. The usage restriction in the home network is information indicating whether temporary copying (temporary copy) in the home network is possible or not. Temporary copy is a process of storing data during viewing and deleting data after viewing. The printout control is information indicating whether or not the content can be printed out. The modification control is information indicating whether or not the content can be modified. The charging timing is information indicating the timing at which the charging process is performed, and can be set to no charging, pre-charging, post-accumulation charging, or composite charging. With compound billing, a basic fee is collected by advance billing,
This is effective when, for example, additional billing is performed after accumulation. The reset is information indicating whether the information before the copy processing is reset to create a copy or the like. By default, the receiving terminal creates a copy while retaining the information before the copy processing.

(Information on User Usage Restriction) Next, FIG. 46 is an explanatory diagram of information on user usage restriction. The access restriction is an item indicating whether or not there is access restriction information for the user. The viewing age restriction is information for restricting the age of a user who can view the content. The advance contract is information indicating whether a prior contract is required when viewing the content.

(Information on Charging) Next, FIG. 47 shows an explanatory diagram of information on charging. The target contract code is information indicating a contract form of the content. This is a code for identifying a user who can view the content, and is a code managed in each broadcaster. The contract form is information indicating a contract form of the content, and can be set for rental and purchase. The usage restriction period is information for setting the usage period of the content after the user has made a contract, and the usable time can be set in minutes. The special fee is information indicating the existence of a discount fee or the like, and the price of the special fee is set at a subsequent fee level. The charge levels 1 to 4 are information indicating charges for the content, and when a plurality of levels are designated, it indicates that there are a plurality of contract forms and charge settings. The payment method is information indicating a method of paying a fee when viewing paid content.

(Information on Contract) Next, FIG. 48 shows an explanatory diagram of information on a contract. The user content playback time is information indicating the accumulated time during which the user has played after the content contract, and is information that is counted on the receiving terminal side. If this information exceeds the usage restriction period, it means that the contract for the user's content has expired. Similarly, the user content reproduction count is information indicating the cumulative number of times the user has performed reproduction after the content contract, and is information counted on the receiving terminal side. When the usage limit count is exceeded, the contract expires. The contract code indicates the tier / flat code with which the user has contracted, and determines the permission of the user to use the content by comparing the tier / flat code with the above-described target contract code. The contract processing is information indicating a form in which a user has made a contract. The above is the control information on the rights in the present comprehensive data distribution service. By defining this information in the metadata, the sending side can control the user who is the receiving side with fine-grained control, and realize the content storage type service with the rights protection function that is a feature of this comprehensive data distribution service. Make it possible.

[0068]

According to the present invention, as described above, the metadata defining the usable range of the content is attached to the content for each content, and the content is distributed to the receiving side together with the content. Fine-grained control of the method of using content in the range defined in the data and the method of presenting content to the user becomes possible. Therefore, according to the present invention, it is possible to provide a service capable of protecting the right of the content, protecting the individual right of the user, and the like.

[Brief description of the drawings]

FIG. 1 is a service configuration diagram of a comprehensive data distribution service.

FIG. 2 is an overall configuration diagram of a comprehensive data distribution service system.

FIG. 3 is an explanatory diagram of a right protection method in an integrated data distribution service.

FIG. 4 is an explanatory diagram of a data structure and description contents of a PAT.

FIG. 5 is an explanatory diagram of a data structure and description contents of a NIT.

FIG. 6 is an explanatory diagram of a data structure and description contents of a PMT.

FIG. 7 is an explanatory diagram of a data structure and description contents of DII.

FIG. 8 is an explanatory diagram of a data structure and description contents of a DDB.

FIG. 9 is an explanatory diagram of a data structure and description contents of metadata for advance contract.

FIG. 10 is an explanatory diagram of a data structure and description contents of EPG metadata.

FIG. 11 is an explanatory diagram of a data structure and description contents of metadata for storage and reproduction.

FIG. 12 is an explanatory diagram of a data structure and description contents of key distribution metadata.

FIG. 13 is an explanatory diagram of classification of a metadata list.

FIG. 14 is an explanatory diagram of an EPG metadata list and a storage / playback metadata list.

FIG. 15 is an explanatory diagram of a pre-contract metadata list.

FIG. 16 shows a data structure of metadata for updating a system key,
Explanatory drawing of the description content.

FIG. 17 is an explanatory diagram of a configuration of a data stream distributed in a network.

FIG. 18 is an explanatory diagram of a detailed stream configuration in a PSI stream group.

FIG. 19 is an explanatory diagram of a detailed stream configuration in a pre-contract metadata stream group.

FIG. 20 is an explanatory diagram of a detailed stream configuration in a storage / playback metadata stream group.

FIG. 21 is an explanatory diagram of a detailed stream configuration in an EPG metadata stream group.

FIG. 22 is an explanatory diagram of a detailed stream configuration in a system key update metadata stream group.

FIG. 23 is an explanatory diagram of a content distribution stream group.

FIG. 24 is a flowchart for explaining a PSI reception process.

FIG. 25 is an explanatory flowchart of a pre-contract metadata receiving process.

FIG. 26 is an explanatory diagram of a flow of EPG metadata reception processing.

FIG. 27 is an explanatory diagram of a flow of a content receiving process.

FIG. 28 is an explanatory flowchart of a system key update metadata receiving process.

FIG. 29 is an explanatory diagram of an example of data constituting each content.

FIG. 30 is an explanatory diagram of an outline of an RMP function.

FIG. 31 is an explanatory diagram of the type of service currently specified.

FIG. 32 is an explanatory diagram of information controlled by a digital copy control descriptor 25.

FIG. 33 is an explanatory diagram of a stream format currently defined.

FIG. 34 is an explanatory diagram of currently specified tag values.

FIG. 35 is an explanatory diagram of an example of a case defined by the comprehensive data distribution service.

FIG. 36 is an explanatory diagram of information specified in Module_info_Byte.

FIG. 37 is an explanatory diagram of classification of metadata.

FIG. 38 is an explanatory diagram of information related to security.

FIG. 39 is an explanatory diagram of information relating to the expiration date of content.

FIG. 40 is an explanatory diagram of information regarding accumulation control.

FIG. 41 is an explanatory diagram of information relating to reproduction control.

FIG. 42 is an explanatory diagram of information regarding control of external output.

FIG. 43 is an explanatory diagram of information regarding movement of content.

FIG. 44 is an explanatory diagram of information related to copy control.

FIG. 45 is an explanatory diagram of information related to home network, printout, modification, and other control.

FIG. 46 is an explanatory diagram of information related to user usage restrictions.

FIG. 47 is an explanatory diagram of information relating to charging.

FIG. 48 is an explanatory diagram of information regarding a contract.

[Explanation of symbols]

1 content, 2 receiving antenna, 3 receiving terminal, 4
... storage media, 5: removable media, 6 ... real-time viewing, 7 ... real-time + storage viewing, 8 ... storage viewing, 9 ... television, 10 satellites, 11 ground lines,
12: distribution network, 13: mobile phone network, 14: external equipment, 1
5: IC card, 16: RMP function, 17: encrypted content, 18: encrypted metadata, 19: PSI / SI, 20: PA
T, 21 ... NIT, 22 ... TS descriptor for system key update, 23
... Service list descriptor, 24 ... PMT, 25 ... Digital copy control descriptor, 26 ... stream_type, 27 ... Stream identification descriptor, 28 ... DII, 29 ... DDB, 30 ... Pre-contract metadata, 31 ... User identification information 32, encryption information, 33, personal information, 34, contract information, 35, terminal key Kmc, 36, EPG metadata, 37, metadata attribute information, 38, program information, 39, content information, 40,
Usage restriction information, 41: System key Ksy1, 42: Metadata for storage and reproduction, 43: Content encryption information, 44: Contract information, 45: Billing information, 46: Content key Kk, 47
... key distribution metadata, 48 ... content key information, 49
... Business key Kw, 50 ... Metadata list, 51 ... EPG metadata list, 52 ... Storage / reproduction metadata list, 53 ... Pre-contract metadata list, 54 ... Metadata list attribute information, 55 ... List information (For content), 56 ... list information (for user), 5
7: Metadata for updating the system key, 58: System key information, 59: Reserved system key Ksy2, 60: Network, 61: TS, 62: Dedicated TS, 63: PSI stream group, 64: Metadata stream for pre-contract Group, 65 ...
Storage / playback metadata stream group, 66 EPG metadata stream group, 67 Content distribution stream group, 68 System key update stream group, 69 PA
T stream, 70 NIT stream, 71 PMT stream, 72 Metadata default ES for pre-contract, 73
... Metadata ES for pre-contract, 74 ... Startup module, 75 ... Metadata default ES for storage and playback, 7
6: Metadata for storage / playback, 77: Metadata default ES for EPG, 78: EPG metadata ES1, 79 ... EPG metadata ES2, 80 ... EPG metadata ES3, 81 ... Own T
EPG metadata for one week distributed by S, 82: EPG metadata for one week distributed by other TSs, 83: Metadata default ES for system key update, 84: Metadata ES for system key update, 85 ... stream contents, 8
6: File-based content, 87: Video ES, 88: Audio
ES, 89: data ES, 90: synchronous PES, 91: asynchronous PES, 92: event message, 93: data carousel, 100: sending side, 200: receiving side, 201: home, 202: vending machine, 203 ... store, 204 ... mobile terminal, 205 ... portable terminal, 206 ... portable telephone, 30
0: home service, 301: vending machine / store service, 302: mobile service, 303: package delivery service, 304: mobile phone service, 400: START, 401: PAT reception, 402: serv
ice_id search, 403: NIT reception, 404: presence or absence of a system key update TS descriptor, 405: service_type / TS identification,
406: PAT reception, 407: PMT reception, 408: PMT analysis, 409: Existing type reception processing, 410: System key update metadata reception processing, 411: Pre-contract metadata default ES confirmation, 412: Advance contract Metadata default ES acquisition, 413: Acquisition of pre-contract metadata list, 414: Search of terminal ID / personal ID, 415: Acquisition of applicable pre-contract metadata, 416: END, 417
... START, 418 ... EPG metadata default ES acquisition,
419: Acquisition of EPG metadata list; 420: Confirmation of version number of metadata list; 421: Identification of updated part; 422: Acquisition of EPG metadata; 423: END;
4: START, 425: Metadata default E for storage and playback
Confirmation of presence / absence of S 426: Acquisition of metadata ES for storage / playback 427: Acquisition of metadata list for storage / playback
428: Information search corresponding to content_id; 429: Acquisition of corresponding module; 430: Confirmation of content reception permission; 431: Content reception; 432: END;
… START, 434… TS by TS descriptor for system key update
Selection, 435: PSI processing, 436: PMT analysis, 437: System key update metadata default ES, 438: System key update metadata acquisition, 439 ... END

Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat II (reference) G06F 17/30 220 G06F 17/30 220C H04H 1/00 H04H 1/00 CF 1/02 1/02 E H04L 9 / 08 H04N 7/173 610Z H04N 7/173 610 H04L 9/00 601A 601B 601E (72) Inventor Iori Yamazaki 4-6 Kanda Surugadai, Chiyoda-ku, Tokyo Hitachi, Ltd. Reference) 5B075 KK07 KK13 KK43 KK54 KK63 ND12 ND16 NK02 NK04 UU34 5B085 AE13 CA04 5C064 BA07 BB10 BC06 BC16 BC20 BD01 BD07 5J104 AA16 EA06 EA17 EA26 NA02 NA35 NA37 PA05 PA11

Claims (13)

[Claims] An information used for searching for a content assigned to a content specified in a unit determined by a sending side device, and a copyright holder and related rights defined by the sending side device are provided. In a metadata distribution method for controlling content viewing and right protection by a receiving terminal by metadata storing content related information including a method of presenting content to a viewer related to protection and information on usage conditions, a metadata stream group includes: It includes a metadata default elementary stream, the elementary stream includes a plurality of modules, and a content identifier, a metadata identifier, and a distribution position for acquiring necessary metadata from a group of metadata streams being distributed to one module. Metadata list in which information to be included is stored And a receiving terminal that obtains necessary metadata from a metadata list, and obtains and selects content. 2. The metadata distribution method according to claim 1, wherein the metadata is metadata for a pre-contract in which information on a contract between a user and a business is stored, and for viewing / storing content. EPG metadata storing information, and content usage metadata storing information for determining content usage and information including a content key,
A metadata delivery method, wherein each metadata is delivered at different timing or asynchronously. 3. The metadata distribution method according to claim 2, wherein the content use metadata includes user access control information for the content and key distribution metadata storing information including an encryption key.
Metadata for storage and reproduction that stores copy control information such as copy generation and fee of the content, and sends key distribution metadata with a business key for each business and metadata for storage and reproduction with a content key for each content By encrypting and distributing on the side, content rights protection is realized by enabling only users who have signed a contract with the business operator and received the business key with the pre-contract metadata to obtain the content key Metadata distribution method. 4. The metadata distribution method according to claim 3, wherein the key distribution metadata is encrypted on the transmitting side by a common system key in all receiving terminals, regardless of whether there is a contract with the business. A metadata distribution method, which enables distribution of contents including free broadcasts to all users holding a system key. 5. The metadata distribution method according to claim 1, wherein the metadata updates information common to the entire system including a system key common to the entire system stored in advance in the receiving terminal. And further includes system key update metadata distributed asynchronously with the distribution of the content to all the receiving terminals regardless of the user who uses the receiving terminal. A metadata distribution method, comprising: distributing system key update metadata obtained by encrypting information including an update system key by using a spare system key held in a receiving terminal when updating the metadata . 6. The metadata delivery method according to claim 1, wherein the metadata list includes information obtained by extending the PSI defined in the MPEG2 system, and the metadata list is mapped to the carousel transmission of the MPEG2 system by the module 0. A metadata distribution method, wherein a receiving terminal can acquire a metadata list at the beginning of a receiving operation. 7. The metadata distribution method according to claim 1, wherein, when the transmission side device distributes metadata defining a content use condition or a use range to a user of the reception terminal, data required from a stream being distributed. A program specific information stream group storing a transport stream configuration for transmitting each data on the transmission path for acquiring the data is distributed asynchronously with the metadata stream group.
A metadata distribution method comprising: acquiring content from distribution data; and performing content protection or storage / playback control by using the acquired metadata. 8. The metadata distribution method according to claim 1, wherein the program specifying information (PSI) is a program map table that specifies a transport stream (TS) packet that transmits each coded signal constituting the broadcast program. (PMT) and a program association table (PAT) for designating TS packets transmitting the PMT related to the broadcast program in each TS
A system key update TS descriptor for identifying a TS transmitting the system key update metadata, and a service list descriptor indicating a service configuration and / or service format in each TS. A metadata distribution method, comprising transmitting network information and information for associating a broadcast service, and including a network information table (NIT) indicating the configuration of the entire network. 9. A metadata distribution method according to claim 8, wherein the receiving terminal assembles a PAT at the time of start-up or when a user selects a channel during distribution, and the receiving terminal selects based on the assembled PAT. A search step for searching for a service identifier for identifying whether information on the selected channel is distributed, and when the receiving terminal determines in the search step that the selected channel is present, the receiving terminal stores the selected channel in the PAT. A PMT receiving step of receiving a TS packet specified by an identifier corresponding to the selected channel and assembling a PMT in which information of the selected channel is described; and a receiving terminal that analyzes the assembled PMT. P including a step of shifting or selecting content reception processing A metadata delivery method, characterized by performing an SI receiving process. 10. The metadata delivery method according to claim 9, wherein the receiving terminal further includes a system key updating TS descriptor if the NIT assembled in the NIT receiving step includes a system key updating TS descriptor. A metadata distribution method, comprising: performing a system key update metadata reception process for acquiring update metadata. 11. The metadata delivery method according to claim 9, wherein the receiving terminal receives the NIT and assembles it when the receiving terminal determines that the information for the selected channel does not exist in the PAT in the searching step. The receiving terminal identifies the TS in which the selected channel is distributed by the service list descriptor in the NIT, and if the storage type service is set, the PAT in the set TS. Receiving the metadata. 12. The metadata delivery method according to claim 9, wherein the receiving terminal, after the PSI receiving process, stores and reproduces metadata default elementary in a PMT for the selected content or channel. Stream (ES)
Identifying the existence of the metadata default ES; and, if the storage / reproduction metadata default ES is specified by the stream identification descriptor, acquiring the storage / reproduction metadata default ES; Recognizes the module to which the required metadata is distributed from the distribution position of the metadata corresponding to the corresponding content described in the list information of the storage and reproduction metadata list, and stores the storage and reproduction metadata and the key distribution. Acquiring the module including the metadata for use in the receiving terminal, the receiving terminal determines the permission to receive the content of the receiving terminal based on the acquired metadata for storage and reproduction and the metadata for key distribution, Receiving the content based on the metadata for storage and reproduction when the reception of the content is permitted; Performing a content receiving process including the following. 13. The metadata distribution method according to claim 1, wherein the information used for the processing related to the right protection in the metadata includes information related to encryption security, information related to use restriction of contents, accumulation or Information for controlling playback, information for controlling external output, information for controlling movement of content, information for controlling copying of content, information for controlling use in a home network, Metadata distribution characterized by executing rights protection processing by using one or more of printout, content modification, user access restriction information, billing information, and contract information. Method.