JP2003288240A - Cookie processing program, cookie processing device, cookie processing method, and contents fusion method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent deletion of special cookie data even if a cookie storage capacity is low. <P>SOLUTION: Contents data managed in hierarchical structure is transmitted from a transmitter 2. To the contents data, mapping data for specifying a directory of a mapping destination and a persistent ID are applied. A receiver 4 receives the contents data. If there is a script for forming a cookie in the contents data and a cookie formation directory designated by the script is equal to that of the mapping destination, the cookie is formed even in a directory in a space with a different name. If the persistent ID is defined in formation of the cookie, the cookie is stored as a persistent cookie not deleted even after a cookie storage area is filled fully. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to cookie data storage processing, and more particularly to processing when the number of stored cookie data and the capacity thereof are limited.

[0002]

[Related Art] In Japanese Patent Application No. 2002-049381, the inventor has already proposed a technology for sharing cookie data between a data broadcasting and a communication content server such as the Internet. This allows cookie processing across different namespaces. A brief description will be given below.

First, cooperation in different name spaces will be described. The digital broadcast receiver is connected to the Internet using a communication line. Then, the channel of the digital broadcast receiving apparatus is selected and the broadcast data to be displayed as shown in FIG. 1 is received. Module data having a hierarchical structure as shown in FIG. 2 is previously stored and received in the hard disk of the digital broadcast receiving device, and a display as shown in FIG. 1 is performed based on the data received by the receiving device. When the user selects the area 301, a screen corresponding to the linked BML data is displayed. Here, in the area 303, a script for requesting BML data specified by a certain URI from a predetermined content server connected to the Internet is described.
Therefore, the digital broadcast receiving apparatus connects to the Internet, receives the BML data from the predetermined content server, and displays it on the screen.

Next, cookie processing in different name spaces will be described. Generally, regarding the processing of cookie data, in order to ensure security, the cookie setting destination directory or the cookie reading destination directory is uniformly limited to the upper directory of the current directory. On the other hand, if the directories in different namespaces have a predetermined relationship, virtual cookie processing is performed if the two directories are linked. For example, in the directory having the structure shown in FIG. 2 and FIG.
"e: // ec / tvshopping / shop2" contains mapping information "path = http: //www.shopping" regarding cookie data processing.
mall.com/shop2 "is set. By the concatenation process using such mapping information, the above-mentioned restrictions are partially relaxed in the cookie data processing (reading and storing), and it is possible to process the predetermined cookie data even if different namespaces are mapped. Become. Figure 4B
4A shows a state in which directories in different namespaces shown in FIG. 4A are shared with respect to cookie data processing.

[0005]

The inventor has newly found the following problems when performing cookie processing in the different name space.

In the storage area for storing cookie data,
There may be limits on capacity and data count. In such a case, the oldest cookie data is normally erased and new cookie data is added by the first-in first-out method. Therefore, when the user frequently accesses another content server, the last access time of the cookie data shared between the different namespaces becomes old. As a result, the cookie data may be erased. As a result, it is necessary for the user to re-enter the ID and password for accessing the specific site.

Such a problem is not limited to the case where cookie data is shared in different namespaces, but a problem similarly occurs in a computer having a limited storage capacity and a limited number of cookie data.

An object of the present invention is to solve the above problems and provide a cookie data processing program for preventing deletion of specific cookie data.

[0009]

1) A cookie processing program according to the present invention, when a permanent cookie specific identifier and a cookie data setting command are given, a cookie setting destination directory in the cookie data setting command. The cookie data for the directory specified as is stored as non-erasable cookie data that has a higher degree of exclusion from the erasure target than the erasable cookie data. Therefore, some cookie data can be excluded from deletion targets.

2) When the cookie processing program according to the present invention is given a permanent cookie specifying identifier and a cookie data setting command, the cookie data for the directory specified as the cookie setting destination directory by the cookie data setting command is given. , Special cookie data different from normal cookie data is stored in the cookie data storage area, and when another cookie data storage command is given to the cookie data storage area, the special cookie data is not erased, Store other cookie data. Therefore, the special cookie data can be preferentially left in the cookie data storage area as compared with a normal cookie.

4) The cookie processing program according to the present invention stores the cookie data as the non-erasing target cookie data when the cookie processing program conforms to the decision rule for determining whether or not the cookie data is stored as the non-erasing target cookie data. Therefore, the non-erasing target cookie data can be determined according to the determination rule.

5) The cookie processing program according to the present invention does not erase the special cookie data and erases the other special cookie data when the determination rule for deciding whether or not to store the special cookie data is met. Store cookie data of. Therefore, the special cookie data can be held according to the decision rule.

6) In the cookie processing program according to the present invention, the cookie processing program includes a first directory managed in a first namespace and a second directory managed in a second namespace. Is present, the data managed in the first directory is assumed to be managed in the second directory, and is a cookie processing program that performs cookie processing. When the cookie setting destination directory matches the second directory specified by the mapping information, it is determined that the cookie setting destination directory matches the determination rule. Therefore, the special cookie data can be held for the directory specified by the mapping information.

7) The cookie processing program according to the present invention judges that the cookie setting destination directory matches the determination rule when the cookie setting destination directory is an upper directory of the second directory. Therefore, the special cookie data can be held even if it is a higher-level directory of the second directory specified by the mapping information.

8) When the cookie setting destination directory is the second directory, the cookie processing program according to the present invention determines that the cookie setting directory matches the determination rule. Therefore, the special cookie data can be held even in the second directory specified by the mapping information.

9) The cookie processing program according to the present invention determines that the cookie setting destination directory is the second directory when the cookie setting destination directory is omitted in the cookie data setting command. Therefore, the special cookie data can be easily held in the directory specified by the mapping information.

10) In the cookie processing program according to the present invention, when the path name of the cookie setting destination directory is omitted in the cookie data setting command, the domain name of the cookie setting destination directory is the second directory. Judge whether it matches the domain name of. Therefore, for the domain specified by the mapping information, the special cookie data can be easily held even if the path is omitted.

11) In the cookie processing program according to the present invention, when the domain name of the cookie setting destination directory is omitted in the cookie data setting command, the path name of the cookie setting destination directory is the second directory. Judge whether it matches the path name of. Therefore, with respect to the directory specified by the mapping information, the special cookie data can be easily held even if the domain is omitted.

12) In the cookie processing program according to the present invention, when the domain name and path name of the cookie setting destination directory are omitted in the cookie data setting command, the cookie setting destination directory is the second.
Judge that it matches the directory of. Therefore, the special cookie data can be easily held even if the domain and the path are omitted.

13) The cookie processing program according to the present invention is given a cookie data setting command when the first directory of the first namespace and the second directory of the second namespace are associated with each other. And a cookie processing program that assumes that the data managed in the first directory is managed in the second directory and performs a cookie data storage process.
When a permanent cookie specific identifier is given, the cookie data to be stored is stored as non-erasable cookie data that is more highly excluded from the erasing target than the erasable cookie data. Therefore, the non-erasure target cookie data can be held between directories in different namespaces.

14) In the cookie processing program according to the present invention, when the directory specified as the cookie setting destination directory is managed by the communication content server determined by the user, the cookie data is set as the non-erasure target cookie. Store as data. It can hold cookie data managed by the server that the user desires.

17, 18) In the cookie processing device or the cookie processing method according to the present invention, when a permanent cookie specifying identifier and a cookie data setting command are given, the cookie data setting command specifies the cookie setting destination directory. The cookie data for the directory to be stored is stored as non-erasable cookie data that is more likely to be excluded from being erased than the erasable cookie data. Therefore, some cookie data can be excluded from deletion targets.

19) In the content fusion method according to the present invention, in the structure description type language description data written in the structure description type language to be broadcast, a cookie is provided between the directory managing broadcast content and the directory managing communication content. A content fusion method that allows the description of mapping information for sharing data, thereby allowing a distributor of the communication content to acquire a user who accesses the communication content through the broadcast content as an entrance. When the persistent cookie setting ID and the cookie setting command are present in the structure description type language description data received by the device, it is judged whether or not the cookie setting destination directory matches the directory for managing the communication contents. , If they match, the cookie data is To store another cookie data as a persistent cookie that does not erase even in the case of new stores in the department. Therefore, even when the broadcast content and the communication content are combined, cookie processing exceeding the general cookie processing rule can be performed between the two places, and such cookie data can be stored as a permanent cookie.

20) In the content fusion method according to the present invention, whether or not the cookie setting destination directory is managed by a specific namespace is determined by the domain of the cookie setting destination directory. Therefore, the cookie data regarding the directory managed in the same domain as the cookie setting destination directory can be stored as the permanent cookie.

21) In the content fusion method according to the present invention, in the structure description language description data described in the broadcast structure description language, a cookie is provided between the directory managing broadcast content and the directory managing communication content. In the content fusion method, which allows the description of the mapping information for sharing the data, whereby the distributor of the communication content can acquire the user who accesses the communication content with the broadcast content as an entrance, If the persistent cookie setting ID and the cookie setting command are present in the structure description type language description data received by the above, it is judged whether or not the cookie setting destination directory is managed by a specific namespace, and if the two match. Stores the cookie data in another cookie in the cookie storage. Even if there is a memory of over data is stored as a persistent cookie that does not erase. Therefore, when the broadcast content and the communication content are combined, the mapping information enables cookie processing exceeding the general cookie processing rule, and the cookie data can be stored as a permanent cookie.

22) In the cookie data processing method according to the present invention, the description is made in the structure description type language including mapping information for sharing the cookie data between the directory managing broadcast contents and the directory managing communication contents. When the structure description type language description data is broadcast, the user receiving the structure description type language description data accesses the communication content via the broadcast content and reproduces the broadcast content based on the mapping information. A cookie data processing method capable of passing cookie data generated therein to a server for delivering the communication content, wherein the cookie data for a directory managed by the server for delivering the communication content is the Free space in the cookie data storage on the receiving device Stored as a persistent cookie that does not erase regardless. Therefore, the mapping information enables cookie processing beyond the general cookie processing rule, and the cookie data can be stored as a permanent cookie.

23) The deletion target cookie data determination program according to the present invention is a program for determining deletion target cookie data to be deleted from the cookie data storage area, and the deletion target cookie is included in a part or all of the cookie data. Set the retention level to determine whether to exclude from the data. By using this degree of retention, it is possible to perform processing to remove it from the deletion target.

24) The deletion target cookie data determination program according to the present invention stores the cookie data in the cookie data storage area separately for the first group and the second group, and stores a new cookie in the cookie data storage area. When deleting any cookie data for storing data, the cookie data belonging to the first group is targeted for deletion. Therefore, the cookie data excluded from the deletion target can be stored.

The "permanent cookie specific identifier" corresponds to the persistent ID in the embodiment, but may be any identifier for storing as a persistent cookie different from general cookies. Good.

In the embodiment, the "cookie data setting command" corresponds to a script storing a cookie file,
This includes not only the case of newly storing a cookie file but also the case of adding it.

The "cookie setting destination directory" refers to a directory in which a cookie file is set. In the embodiment, the case where the directory is a mapping destination has been described. However, a higher directory of the mapping destination directory may be used as the cookie setting destination directory. it can.

In the embodiment, the "erasable cookie data" corresponds to a normal cookie other than the permanent cookie file. The “non-erasure target cookie data” corresponds to a permanent cookie file in the embodiment. Note that the non-erasure target cookie data may be selected as a deletion target depending on conditions other than the exclusion degree, such as an expiration date.

In the embodiment, the "special cookie data" corresponds to a permanent cookie file.

The "decision rule" is a rule for deciding whether or not to store as the non-erasing target cookie data, and in the embodiment, when both the conditions of step S63 of FIG. 21 and step S73 of FIG. 22 are satisfied. Is applicable.

"The cookie setting destination directory matches the second directory specified by the mapping information" means that the cookie setting destination is not limited to the case where the cookie setting destination directory is the second directory. This also includes the case where the directory is a higher-level directory of the second directory.

The "persistent cookie setting ID" corresponds to the persistent ID in the embodiment, but may be any identifier as long as it is a persistent cookie to be stored and is different from general cookies. Good.

"Setting a degree of retention for determining whether or not to exclude some or all of the cookie data from the cookie data to be deleted" means associating a value representing the degree of retention with the cookie data itself. It is of course possible to group and memorize by grouping. Such grouping and storing includes not only the case where a classification flag is given to each cookie data but also the case where physically different areas are separately stored.

The "reception device" means a device having a function of receiving data from the transmission device, and is a concept including both a so-called set top box having no display device and a television set having a display device.

The "data managed in the first name space" means data belonging to the first name space. In the embodiment, for example, in FIG.
ib-file: //ec/tvshopping/shop2/index.bml ”is the first
Belongs to the namespace "arib-file: // ec / tvshopping", and is managed in the first namespace. In addition, "arib-file: // ec / tvshopping / shop2" and "a
You can also grasp "rib-file: // ec / tvshopping" in the first namespace.

In the embodiment, the "name space" means a namespace for managing communication contents specified by a domain and a path name, and a namespace for managing storage contents specified by a path of a local area in a hard disk. , And original_network_id, transport_stream_id, serv
The namespace for managing the stream content specified by ice_id and the like has been described, but any namespace that theoretically manages data in a hierarchical structure may be used.

"The data managed in the first namespace is managed in the first directory of the first namespace" means that the first directory exists in the first namespace,
This means a case where the data is managed in the first directory. In the embodiment, for example, in FIG.
If "arib-file: //ec/tvshopping/shop2/index.bml" is the data, the first directory is "ar
ib-file: // ec / tvshopping / shop2 ", and the first namespace is" arib-file: // ec / tvshopping ".

The phrase "the first directory virtually belongs to the second directory to perform the cookie processing" means, for example, that the first directory is a directory "arib-file: // ec / tvshopping / shop2 / ba
rgain ”, the second directory is the directory“ h
ttp: //www.shoppingmall/shop2 "and, if they are associated, the directory" arib-file: //
The data (including the directory) belonging to "ec / tvshopping / shop2 / bargain" is stored in the directory "http: //www.sho.
Cookie processing as it exists in "ppingmall / shop2".

"Perform the cookie process by assuming that the first directory virtually belongs to a directory one level higher than the second directory" means, for example, the first directory. Is the directory "arib-file: // ec / tvshopping / shop2 / bargain", and the second directory is the directory "http: //www.sho.
ppingmall / shop2 ", the directory" arib-
The data (including the directory) belonging to "file: // ec / tvshopping / shop2 / bargain" is stored in the directory "http: // w
Cookie processing as it exists in "ww.shoppingmall".

"The mapping information with the second directory exists in the first directory" means that the mapping information exists in any area, and the first directory as in the embodiment. In addition to the case where the mapping information for use is separately stored, the case where the mapping information is stored in the first directory is included.

The "passable data" is data that is passed to a request source to which the read request is given or a designated destination specified by the request source.
In the embodiment, cookie data is applicable.

The "directory structure" means a structure for managing data hierarchically, and not only file structure in a computer but also original_network_id, transport_str like stream contents in digital broadcasting.
Including cases where eam_id, service_id, etc. are theoretically managed in a hierarchical structure.

The "current directory" is a directory in which data such as structure description type language description data for instructing cookie data processing is located.

The "upper directory" includes, for example, a tree structure of a namespace in which the lower path and the description of the subdomain are deleted.

The "lower directory" includes, for example, a tree structure of a namespace to which lower path and sub domain descriptions are added.

"Structure description type language description data" refers to data to which display designation information such as an arrangement position when displaying document data, a size of a character string, and information regarding referenced graphic data is added. In the form, the case where the data is described in the BML language has been described.
Includes L, XML type data, MHEG standard data, and the like.

In the embodiment, the "structure description type language description data receiving means" corresponds to the reception selection processing in the tuner 32, the TS decoder 34, and the CPU 44. The “image data generating means” means the AV decoder 36,
The processing of the OSD 38 and the CPU 44 corresponds to this. The "data holding unit" corresponds to, for example, the cookie data holding process (including the additional recording process) of the CPU 44 based on FIG. In the embodiment, “mapping information” means path = htt added to the directory “shop2” shown in FIG.
p = www.shoppingmall / shop2 and path = http: //www.s added to the directory "shop2" shown in FIG.
Hopping mall / shop2 is applicable. In this embodiment, the same directory is used for mapping in FIGS. 3 and 15, but any directory (for example, a root directory or a subdirectory) can be used for mapping. "Passable data"
In the embodiment, cookie data corresponds to.

The "identification name" of the content data is a name for identifying the content data, and is a concept including a directory name, a file name and the like.

The "recording medium on which the program is recorded" means
A recording medium such as a ROM, a RAM, a flexible disk, a CD-ROM, a memory card, and a hard disk recording a program. The concept also includes communication media such as telephone lines and carrier paths. Not only a recording medium such as a hard disk that is connected to a CPU and directly executes a recorded program, but a CD-R that records a program to be executed after once installed in a hard disk or the like.
It is a concept including a recording medium such as OM.

The term "program" is a concept that includes not only a program that can be directly executed by a CPU, but also a source format program, a compressed program, an encrypted program, and the like. Further, it also includes a program that executes a part of processing in cooperation with another program such as an operating system (OS), and a program that performs distributed processing.

"Recording medium on which data is recorded" means ROM, RAM, flexible disk on which data is recorded,
A recording medium such as a CD-ROM, a memory card, and a hard disk. The concept also includes communication media such as telephone lines and carrier paths.

The term "data" means not only data that can be directly processed by the CPU, but also encrypted data, packetized data, data placed on a carrier wave (that is, a carrier wave modulated by data), and compressed data. It is a concept that includes data and the like.

In the embodiment, the case where the directory structure is directly described in the content server has been described. Further, in the hard disk of the receiving device 4, the content data is physically stored as one file for each module, and by the directory structure of each file and the resource list of the resources stored in each file, The case where each content data is logically stored in the directory structure has been described. However, the present invention is not limited to this, and any other storage method may be used.

In the present specification, the directory structure is a concept including a resource list showing an inter-module hierarchical structure and a resource list of resources in each module as in the embodiment.

[0059]

BEST MODE FOR CARRYING OUT THE INVENTION 1. [Overall Configuration] FIG. 5 shows an overall configuration of a transmission / reception system using a receiving apparatus according to an embodiment of the present invention.

An outline of the transmission / reception system will be described.
Content data managed in a hierarchical structure is transmitted from the transmission device 2. Mapping data specifying a mapping destination directory and a persistent ID are added to the content data. The receiving device 4
The content data is received. If there is a script for generating a cookie in the content data and the cookie generation directory specified by the script is the same as the mapping destination directory, the cookie is generated even if the directory has a different namespace. Further, at that time, if the persistent ID is set, the cookie is stored as a permanent cookie that is not erased even when the cookie storage area is full.

A description will be given below. The content provider transmits the content data from the content server 6 to the transmission device 2 via the Internet. The transmitter 2 receives this content data and broadcasts it. Receiver 4
Receives and stores content data via the satellite 1. The operator of the receiving device 4 can browse the accumulated content data.

FIG. 6 shows a functional block diagram of the transmitter 2. The receiving unit 8 receives the content data given from the content server 6. The content storage unit 3 stores this content data. In this embodiment, the content data stored in the content storage unit 3 of the transmission device 2 is reproduced on the reception device 4 side including the directory structure thereof. By doing so, the transmitter 2
It becomes easy to manage the content data on the side of. The mapping data storage unit 11 stores mapping data of data transmitted to the receiving device 4 in data broadcasting. The mapping data will be described later. The permanent cookie specific information storage unit 10 stores a permanent cookie specific identifier. Whether such an identifier is stored in the receiving device 4 as non-erasable cookie data that is highly excluded from being erased when compared with normal erasable cookie data when storing cookie data. Used to determine Details will be described later.

The data transmission control section 5 stores the new content data recorded in the content storage section 3 together with the mapping data and the permanent cookie specific identifier.
It is given to the multiplexing unit 7. The multiplexing unit 7 performs packetization, generates control data DII for packetization, and supplies it to the transmission unit 9 together with the data DDB. The transmitter 9 transmits the data in a carousel format using a predetermined transport stream.

The content data is not limited to still image information, but video data such as TV programs, movies, news, dramas, music data, game programs,
It includes various data such as control information of the controlled device. Further, the content data may be repeatedly transmitted and one content data may be transmitted only once.

The receiving device 4 will be described with reference to FIG. Although a so-called set top box is shown as the receiving device 4 in this embodiment, the receiving device 4 may be configured to include the monitor (TV set) 10.

The operator inputs a reception command for a desired channel to the operation receiving section 16. Upon receiving the operation instruction, the control unit 22 gives a command to the receiving unit 12 to receive the communication data (content data) of the designated channel. When the content data is given from the receiving unit 12, the control unit 22 outputs the received content data to the monitor 10. The monitor 10 displays content data and outputs audio.

Further, the content accumulation decision data for specifying the content data to be accumulated is stored in advance in the control unit 22, and the control unit 22 receives the content accumulation decision data at the designated time based on the content accumulation decision data. 1
2. Give an instruction to receive the content data specified in 2. Upon receiving the content data, the control unit 22 stores the content data in the storage unit 24. When the operation command given to the operation reception unit 17 is a command to display the content data stored in the storage control unit 24, the control unit 22 reads this and outputs it to the monitor 10.

The control unit 22 causes the cookie processing unit 14 to store the input data given from the operation receiving unit 16 as cookie data for the designated content server.
The processing of such cookie data will be described later.

When the operation instruction of the operator (user) is to execute communication through a communication line such as a telephone line, the control unit 22 gives the instruction to the Internet processing unit 13. The internet processing unit 13 sends this instruction (for example, purchase request for online shopping) to
It is transmitted to the content server 6. At that time, the data input by the operator is read from the cookie processing unit 14 and transmitted as a purchase application to the content server 6 via the communication line. In this way, the operator can display the content data received by the receiving device 4 and apply for the purchase of a product or the like.

The operation accepting section 16 can be constituted by a signal receiving section for receiving a signal from the remote controller, and by an operation input button (not shown) provided on the main body of the receiving device 4. Good.

In the above embodiment, the receiving device 4 is described as including the accumulating unit 24, but the accumulating unit 24 may be formed separately from the receiving device 4. The storage of the content data in the transmission device 2 may be realized not only by receiving from the content server but also by using a portable recording medium.

2. [Hardware Configuration of Receiving Device] The hardware configuration of the receiving device 4 shown in FIG. 5 will be described with reference to FIG. 7. The receiving device 4 includes a tuner 32 and a transport stream decoder (TS decoder) 3
4, AV decoder 36, OSD (On Screen Display)
38, ROM 40, RAM 42, CPU 44, hard disk 46, modem 48, and signal receiving unit 50. The signal receiving unit 50 is for receiving a signal or the like from the remote control device.

The received content data is stored in the hard disk 46, which is a storage unit, by a storage process described later. FIG. 13 shows the data structure of the content data stored in the hard disk 46. In FIG. 13, content data related to online shopping is stored in a hierarchical structure. The root directory “ec” of the hard disk 46 has subordinate directories “bank” and “tvshopping”. In the directory "tvshopping", the subordinate directory "sh
There are "op1", "shop2", "shop3", and "shop4".
The directory "shop2" further has a subordinate directory "bargain". A subdirectory “gift” exists in the directory “bargain”. The directory "gift" contains subordinate directories "2000" and "300".
There are "0" and "4000". Resources "coffeecup.bml" and "coffeecupxx.b" are stored in the directory "4000".
ml ”and“ coffeecupyy.bml ”exist.

The directory structure on the hard disk 46 is virtual, and in reality, the data received by one module described later is stored as it is as one file. Since such a file is composed of a resource list and a plurality of resources, as will be described later, each resource substantially has a directory structure as shown in FIG. Hereinafter, for simplicity of explanation, it is assumed that a directory structure exists.

Further, the hard disk 46 stores a cookie table as shown in FIG. In this embodiment, the upper limit of the number of cookie files is set to 300. For each cookie file, its domain name, path name, name, persistent ID, content, and last access time are stored. The persistent ID will be described later.

Further, in the hard disk 46,
A persistent cookie table as shown in FIG. 9 is stored. Persistent cookie table has a persistent ID
The domain name and path name are stored for each.
Such a persistent cookie table is used for facilitating the search as to whether or not the persistent cookie has already been registered. Details will be described later.

In the present embodiment, the case where the storage unit is composed of a hard disk has been described, but any writable recording medium such as a DVDRAM or a semiconductor memory may be used. .

In the present embodiment, the tuner 3
2 and the TS decoder 34 in the receiving unit 12, the hard disk 46 in the storage unit 24, the signal receiving unit 50 in the operation accepting unit 16, the communication processing of the modem 48 and the CPU in the Internet processing unit 13, and the cookie processing of the CPU described later. Corresponds to the cookie processing unit 14, and the control processing to the respective units of the CPU corresponds to the control unit 22.

3. [Outline of Stored Content Reception Processing] The stored content reception processing will be described. The program for the content data reception process is the RO shown in FIG.
It is stored in M40.

Each content data (BML file, image data, etc.) is transmitted as one resource, and as shown in FIG. 10, it is transmitted as one module data in which a plurality of resources are collected. Module data consists of entity header and entity body. The entity body is composed of multiple resources. The header of the resource is given to each resource. The first resource has a resource list of resources that form the module. This module data consists of DDB (Down
It is divided into load Data Block) and sent as DDB message data. In the receiving device, by reading out the block data of a plurality of DDB messages and connecting them,
Resource list and each content data (resource)
Can be reproduced.

In the satellite broadcasting, the above is in carousel format.
DDB messages are repeatedly sent, and data DII (Downloose) is sent to each carousel as management data for the data sent by the carousel.
ad Info Indication) is included. By extracting the necessary information from the data DII, it is possible to selectively obtain only the desired data from the data transmitted by the carousel.

The DDB message data, the data D
The data structure of II is the same as the data structure of storage-type content defined by ordinary satellite broadcasting.

FIG. 11 shows the data structure of the data DII.
Will be explained. The data DII is composed of areas such as DSM-CC message header, download identifier, number of modules, module management data, and private data. Module management data is
It is composed of a module identifier (id), a module size, and module information. In the private data area, a hierarchical structure (directory structure) of each content data shown in FIG. 13 is stored.

It should be noted that such a hierarchical structure is logical, and as described above, each module is stored as one file, and a resource list indicating the directory structure of the resources belonging to the file is stored at the beginning of the file. Exists. That is, in the private data area, the root directory to which each file belongs is stored in the root descriptor storage area (StoreRoot descriptor), and its subdirectory structure is stored in the subdirectory descriptor storage area. In FIG. 13, the directory "ec" is stored in the root descriptor storage area, and "tvshopping" is stored in the subdirectory descriptor storage area.

As described above, in the data DII, the directory structure for each module can be specified, and the data structure of the resource (content data) forming the module is such that the DDB message data is all received and linked to the resource list. Can be specified by referring to. For example, when the resource belonging to the subdirectory “shop2” shown in FIG. 13 is transmitted by one module, the subdirectory “block2” is received by linking all the block data of the DDB message configuring the module. You can get the content data that belongs to "shop2".

As described above, in the present embodiment, the directory structure of each resource is divided into a directory structure for each module and a directory structure within a module, and different areas (a part is in DII and another part is In the DDB message resource list) in a different format. However, the present invention is not limited to this, and the entire directory structure may be stored in the DII or the like.

Mapping data is stored in the resource list of the DDB message data. FIG.
For example, the subdirectory "shop2" is http: //
Mapped to www.shoppingmall.com/shop2.
A method of using such mapping data will be described later. In the present embodiment, as shown in FIG. 12, the mapping data includes provider private information storage area (Provider Privat) of the directory additional information storage area (additional Directory Info) of the resource list directory information storage area (stored Directory Info).
e descriptor) domain mapping descriptor storage area (X
ePF DomainMap subDescriptor).

Further, the provider private information storage area (Provider Private descriptor) has a persistent ID storage area for storing the persistent ID. When a persistent ID is associated with a certain directory, the directory specifying information and the persistent ID are stored. For example,
As shown in FIG. 13, “p” is added to the subdirectory “shop2”.
ersistentID = 199 ”is stored. The process using such a persistent ID will be described later.

The mapping data and / or the persistent ID may be stored in the private data area or module information area of the data DII.

4. [Content Storage Processing] A program for content storage processing is stored in the ROM 40 shown in FIG. The content storage process is performed based on the content storage determination data (not shown) stored in the hard disk 46.

The program may be stored in the hard disk 46, or may be stored in a non-volatile memory or the like.

As described above, for the stored content data, the hierarchical structure of each module is stored in the private data area of the data DII. In addition, a resource list of resources that configure the module is described in each module. Therefore, the CPU
Using this data, the 44 can grasp the logical directory structure of each content data as shown in FIG. Further, the mapping data is also stored together with the hierarchical information.

In this embodiment, the stored content mapping data is stored in the private directory data area (privateDirectoryDataByt) of the stored content resource list (X-aribe-storedResourceList).
It is stored in the directory information area (sto
redDirectoryInfo ()) additional directory data area (ad
It may be inserted in (ditionalDirectoryInfo).

FIG. 14 shows a flowchart of the content storage processing program. First, the CPU 44
Filtering conditions such as DII packet ID (PID) are set in the TS decoder 34 shown in FIG. 7 (FIG. 14).
Step S1). Radio waves from the broadcasting device are captured by the antenna 30 and selected by the tuner 32. The TS decoder 34 selects the data DII from the transport stream selected by the tuner 32 and supplies it to the CPU 44 (step S2). As a result, the resource list in which the directory structure is described can be acquired.

The CPU 44 stores in the RAM 42 shown in FIG.
A work area for storing content data is secured (step S5 in FIG. 14). The CPU 44 shown in FIG.
The filtering condition of the DDB message is set in the S decoder 34 (step S6). As a result, the TS decoder 34 acquires the designated DDB message, and the CPU
44 (step S7 in FIG. 14).

The CPU 44 concatenates the block data of the acquired DDB message, reproduces it in one file, and records it in the hard disk 46 shown in FIG. 7 based on the directory structure shown in the data DII (step S in FIG. 14).
9). In this way, the accumulated data is recorded on the hard disk 46 shown in FIG.

As a result, the content data as shown in FIG. 13 is stored in the hard disk 46. In this example, the subdirectory "shop2" is the directory "http://www.shoppingmall.com" of the communication content server.
It is mapped as "com / shop2".

As already described, one module is recorded as it is as one file.

When the specified service (channel) is specified by the operator, NIT, PMT, PA
Since the method of acquiring T etc. and switching the channel is the same as the usual method, the description thereof is omitted.

In this way, an image is displayed on the monitor 10 based on the received content data.

Note that the designation of each resource for non-storage type content such as ordinary broadcast content is the same as in the conventional BS data broadcasting. For example, each resource is specified in a hierarchical structure as shown in FIG. can do.
In this case, in a certain transport stream, the program with the service id "Time service" has the module id "000
At “0”, the directory “menu” has the module id “000
1 ”directory“ shop1 ”has module id“ 000
2 ", the directory" shop2 "is repeatedly sent in carousel format. Also, the directory "shop2"
As shown in FIG. 10, each of the resources is included in one module and is transmitted in the same manner as the stored content.

Note that the component id of the data broadcast is transmitted as "40" and the stream content "/ 40/0000" is transmitted.
/startup.bml "is original_network_id0001, transpo
When sending with rt_stream_id1001 and service_id1000, if you specify the full path, "arib-dc: //0001.1001.1000
/40/0000/startup.bml ”.

5. [Data Structure of Content Server] FIG. 2 shows the data structure of the content data stored in the content server 6 shown in FIG. In this example, the subdirectory "shop2" exists in the root directory,
In the subdirectory "shop2", the subdirectory "g
"iftset", "coffeecup", "spoon", and "glass" exist. The subdirectory "coffeecup" has a subdirectory "wedge", and the subdirectory "wed".
ge ”, the files“ coffeecupRR1.bml ”and“ co
ffeecupRR2.bml ”exists.

The domain name of the content server is "shoppingmall.com", and the URL of each file is
For example, http: // ww for coffeecupRR2.bml
w.shoppingmall.com/shop2/coffeecup/wedge/coffeecup
It can be uniquely specified in RR1.bml.

6. [Processing of Script Using Mapping Information] Hereinafter, processing of a script using mapping information will be described with reference to the flowchart shown in FIG. In the following, stored data as shown in FIG. 13 is stored in the hard disk 46 shown in FIG. 7, and a product is purchased using this stored data, and stream data as shown in FIG. Next, a description will be given of a process executed when the user purchases a product, and further purchases a product and makes a payment in the content server 6 shown in FIG. It should be noted that it is not known whether the screen display is the one that received the stream data (see FIG. 15) or the screen display that uses the accumulated data just by referring to the displayed screen. Therefore, the process is performed without making the operator aware of which data is used for the display. Further, regarding the screen display by the content server 6, in the case of dial-up connection, it can be recognized by displaying the screen.

First, the operator starts up the browser program, gives a channel switching command to the signal receiving unit 50 (see FIG. 7), and gives a display command for displaying the accumulated data. With the data shown in FIG.
A display instruction to display "arib-file: //ec/tvshopping/menu/startup.bml" is given. As a result, the CPU 44
Displays the screen of the TV shopping time service shown in FIG. 17 on the monitor 10. As the display processing, the first page of the accumulated data may be displayed.

In this state, the operator operates the area 1 shown in FIG.
When 03 is selected and confirmed (hereinafter referred to as “select confirmation confirmation”)
Based on the browser program, the CPU 44 determines that the resource read command has been given (step S21 in FIG. 16), and determines the type of file to be read (step S23). This type of judgment is performed by using B shown in FIG.
This is possible by referring to the head part of the link destination resource of the ML data. In the present embodiment, if the linked resource is stored content, "arib-file:",
For communication (Internet) contents, "htt
Since the resource data storage location is described in BML data such as "p:" and "arib-dc:" for stream content, the above three types can be distinguished.

In this case, the BML data “arib-file: // ec
It is assumed that "/tvshopping/shop2/index.bml" is specified as the linked resource. The CPU 44 determines that the link destination resource is the accumulated data based on the leading character string and sets the accumulated data as a search target (FIG. 1).
6 step S29).

The CPU 44 searches for the target resource based on the resource list and determines whether or not there is mapping data during the search (step S26). That is, it is determined whether or not the mapping information is associated with the upper directory of the target resource.

In this case, for the accumulated data of the directory structure shown in FIG. 13, the resource "arib-file: // ec / tvs
`` hopping / shop2 / index.bml '' is the target resource, so if you search for the target resource by tracing the directory information of the stored contents stored on the hard disk, the resource `` arib-file: // ec / tvshopping / shop2 / index. bm
The directory to which "l" belongs "arib-file: // ec / tvshoppi
As shown in FIG. 13, it can be seen that "http://www.shoppingmall.com/shop2" is set in "ng / shop2" as mapping information. Therefore, the CPU 44
It is determined that the directory in which the target resource exists has mapping information.

If the CPU 44 determines that there is mapping information, it stores that there is mapping information in the directory specified by the mapping information (step S27 in FIG. 16). That is, the directory in which the mapping information exists (corresponds) and the mapping destination directory associated with the directory are stored as the mapping destination directory. Then, the relative path from the directory where the mapping information exists is regarded as the relative path from the mapping destination directory. Than this,
You can map the current directory to another directory in the namespace.

The CPU 44 determines whether or not the read BML data has a script execution instruction (step S3).
7) In this case, since it does not exist, the target resource is displayed (step S41). As a result, the image shown in FIG. 18 is displayed on the monitor 10.

Next, the operator operates the area 104 shown in FIG.
After selecting and confirming, the CPU 44 determines that the resource read command is given (step S21 in FIG. 16),
Determine the type of file to be read (step S2)
3). In this case, the BML data “arib-file: // ec / tvsho
If "pping / shop2 / bargain / bargain-index.bml" is specified as the link destination resource, the CPU 44 can determine that the target resource is accumulated data from the beginning of the resource, and the accumulated data is searched. (Step S25 in FIG. 16). The CPU 44 searches for the target resource based on the directory information and determines whether or not there is mapping data during the search (step S26). In the present embodiment, whether the mapping data exists or not is determined by searching the directory to which the target resource belongs in the direction of the root directory and determining whether the mapping data exists in the first domain mapping descriptor. I did it. In this way, the domain mapping descriptor that exists first when the certain directory is searched toward the root directory is called a domain mapping descriptor that is effective for that directory.

In this case, the resource "arib-file: // ec / tvs
Since "hopping / shop2 / bargain / bargain-index.bml" is the linked resource, the target resource is searched by tracing the directory information. Then the resource "arib -f
ile: //ec/tvshopping/shop2/bargain/bargain-index.bm
The directory "arib-file: // ec / tvshopping" to which "l" belongs
The upper directory of "/ shop2 / bargain""arib-file: // ec
In / tvshopping / shop2, the mapping information is "htt
You can see that "p: //www.shoppingmall.com/shop2" is set. Therefore, the CPU 44 determines that the directory in which the target resource exists has mapping information.

If the CPU 44 determines that there is mapping information, it stores that there is mapping information in the directory specified by the mapping information (step S27 in FIG. 16). Then, when there is no script command, the CPU 44 displays the target resource (step S41). As a result, the image shown in FIG. 19A is displayed on the monitor 1.
Displayed at 0.

Incidentally, in FIG. 13, "/ shop2 / bargain / gif
The "t" is represented as a directory of 1, but it is a virtual one as described above, and if "/ sho
If the resources under "p2 / bargain" are transmitted as one module, "/ shop2 / bargain" is one file (multipart format) that contains multiple resources, and Since the resource list of resources constituting the file is described, the CPU 44 can identify each resource by referring to it.

Similarly, when the image shown in FIG. 19B is displayed on the monitor 10 and the operator selects and confirms the area 107, the image shown in FIG. 19C is displayed on the monitor 10 and when the operator selects and confirms the area 108. , The CPU 44 uses the resource “arib-file: // ec / tvshopp” specified in the area 108.
ing / shop2 / bargain / gift / 4000 / coffeecupxx.bml ”is read. Similarly, the CPU 44 determines that the type of resource is the accumulated data, and steps S29 and S2.
6, Step S27 is executed.

The CPU 44 determines whether or not there is a script execution command (step S37). Area 1 shown in FIG.
If the script for executing the cookie storage (writing) process in which the cookie setting destination directory is the directory "http://www.shoppingmall.com/shop2" is described in 09, the following process is executed. It

6.1 [Persistent Cookie File Storage Processing] A case where the script execution command is cookie processing will be described with reference to FIGS. 21 to 23. First, the storage processing in the persistent cookie file will be described.

First, the CPU 44 determines the current directory as the cookie processing directory (see FIG. 2).
1 step S51). In this case, the directory "arib -f
ile: // ec / tvshopping / shop2 / bargain / gift / 4000 ”is determined as the cookie processing directory.

The CPU 44 determines whether or not the mapping information exists in the domain mapping descriptor which is effective for this cookie processing directory (step S53 in FIG. 21). In this case, the directory "arib-file:
The mapping information "http://www.shoppingmall.com/shop" is stored in the upper directory "arib-file: // ec / tvshopping / shop2" of "/ ec / tvshopping / shop2 / bargain / gift / 4000".
2 ”exists, the CPU 44 determines that there is mapping information in the domain mapping descriptor that is effective for the cookie processing directory, and performs mapping processing (step S55).

Specifically, regarding the cookie processing, the directory "arib-file:" in which mapping information is set.
Each directory belonging to "/ ec / tvshopping / shop2" is a mapping destination directory "http: //www.shoppin
If you belong to "gmall.com/shop2", you will be spoofed. As a result, as described later, regarding the cookie processing, the above-mentioned mapping destination directory "http://www.shoppingmall.co
m / shop2 ”, a subdirectory“ b ”that does not actually exist
"argain" is treated as if it were virtually present.

The CPU 44 determines whether the designated cookie process is a read process or a storage process (step S57). In this case, since it is a storage process, the CPU 44
Determines whether the cookie setting destination directory specified by the script is the cookie processing directory or a higher-level directory thereof (step S61). In this case, in the script, the directory "htt" of the content server 6 is set as the cookie setting destination directory.
p: //www.shoppingmall.com/shop2 "is specified.
Such a directory is determined to be an upper directory of the cookie processing directory by the mapping processing. Therefore, the CPU 44 proceeds to step S63 and proceeds to the cookie processing directory "arib-file: // ec / tvs".
It is determined whether or not the persistent ID is designated in the domain mapping descriptor that is effective for "hopping / shop2 / bargain / gift / 4000" (step S63).

In this case, the cookie processing directory "ar
ib-file: // ec / tvshopping / shop2 / bargain / gift / 4000 ''
If you follow the direction of the root directory, the domain mapping descriptor for the higher-level directory "arib-file: // ec / tvshopping / shop2" has a persistent ID.
"Persistent = 199" is specified (see FIG. 13).
Therefore, the CPU 44 determines whether the mapping destination directory designated by the domain mapping descriptor and the cookie setting destination directory designated by the script match (step S73 in FIG. 22).

In this case, since both are the same, CP
The U44 proceeds to step S75 and determines whether or not a cookie file of another persistent ID having the domain and path designated by the script exists (step S75).

If there is no cookie file of another persistent ID having the domain and path specified by the script, the CPU 44 refers to the cookie table and specifies the persistent ID specified in step S63. It is determined whether or not the domain and path have already been set for the cookie file (step S79). In this case, the persistent ID specified in step S63 is "199", and the domain and path have not yet been set for the cookie file specified by this ID. Therefore, the process proceeds to step S85, and it is determined whether or not a predetermined number (300 in this case) of cookie files are already stored in the cookie table (step S85).

In this case, as shown in FIG. 8, the total cookie files stored are 299, which is less than the total of 300, so the CPU 44 creates a permanent cookie file designated by the script (step S8
8). Note that the name of the cookie file is generally specified by the script, but in the present embodiment, the names of the persistent cookie files are all persistent.

As a result, the cookie table shown in FIG.
One persistent cookie file is added, as shown in. Further, as shown in FIG. 25, the persistent cookie table also stores domain and path combination data for persistent IDs.

Thus, by the mapping process,
The shopping information (purchased store name, product name, etc.) shown in FIG. 26 is recorded in the cookie file for the directory of the content server 6 instead of the local file on the hard disk of the reception device 4, and further for cookie processing. If a persistent ID is set in the domain mapping descriptor that is effective for the directory, the cookie file is a persistent ID.
Is added and stored.

Note that such a cookie file is created as another cookie file if the path is different even in the same domain.

6.2 [Normal Cookie File Storing Process] Next, the normal cookie file storing process will be described. This is a process when a persistent ID is not designated in the domain mapping descriptor that normally has an effect on the cookie processing directory. In this case, the CPU 44 executes steps S63 to FIG.
In step S91, it is determined whether or not a persistent cookie file having the same domain path name (name) exists in the cookie table (step S91).
The name of the persistent cookie file is persistent, and in the case of a cookie file, it is not specified as persistent in the script, so the two do not match. Therefore,
The CPU 44 proceeds to step S94 and determines whether or not there is a normal cookie file that matches the domain path name of the script (step S94). If it exists, the CPU 44 additionally writes the data specified by the script in the normal cookie file (step S).
100).

On the other hand, in step S94, when there is no ordinary cookie file that matches the domain path name of the script, the CPU 44 proceeds to step S95 and stores a predetermined number (in this case) in the cookie table. It is determined whether or not 300 cookie files are stored (step S95). In this case, the stored cookie file is 3 as shown in FIG.
Since there are 00, a total of 300 have been stored, the CPU 4
4 deletes the oldest normal cookie file (step S97). In this embodiment, the oldest normal cookie file is determined by the last access time. This leaves one free space in the cookie table shown in FIG. The CPU 44 creates a new normal cookie file in which the specified data is stored in the cookie file having the name specified by the script (step S99).

If the total number has not been stored in step S95, there is an empty space, so the CPU 44 performs the process of step S99 without performing the process of step S97.

6.3 [Exception Processing] Even when the persistent ID is set in the domain mapping descriptor that is effective for the cookie processing directory, data may be stored in the normal cookie file. If the persistent ID is present in step S63, the CPU 44 proceeds to step S73, in which the mapping destination directory designated by the domain mapping descriptor matches the cookie setting destination directory designated by the script. It is determined whether or not (step S73 in FIG. 22). Here, if the two do not match, the file is not stored as a permanent cookie file, but proceeds to step S91 in FIG. 23, and is processed as a normal cookie file. Even in this case, if a persistent cookie file having the same domain path name exists in the cookie table in step S91, the same procedure as above is performed, and step S93 is performed.
Will be added as a persistent cookie file in.

In the present embodiment, by referring to the permanent cookie table (see FIG. 9), it is possible to speedily perform the determinations in steps S75 and S79. Note that the persistent cookie table can be omitted.

Next, the processing when the cookie file having the domain path specified by the script already exists in the cookie table as a permanent cookie file having another persistent ID will be described. In this case, of the cookie files stored in the cookie table, the cookie file identified by the persistent ID identified in step S63 has the domain and path already set, and the domain path is the domain of the script.・ Match the path. Therefore, the CPU 44 advances the process from step S79 to step S81 in FIG. 22, and further advances to step S89. As a result, the data specified by the script is added to the existing persistent cookie file (step S89).

It should be noted that the step S6 is added to the cookie table.
If there is a persistent cookie file that has the same persistent ID as the domain path with the persistent ID specified in 3, and the domain path of this persistent cookie file and the domain path specified by the script do not match. First, the CPU 44 changes the permanent cookie file into a normal cookie file (step S83).

Note that the permanent cookie file may be deleted in step S83.

Also, when a new permanent cookie file is stored, the process of deleting the oldest normal cookie file because the cookie table is full is the same as when storing a normal cookie file (see FIG. 22 Step S85, Step S87).

Next, a case will be described in which data is additionally written in the permanent cookie file even when the persistent ID is not set in the domain mapping descriptor that is effective for the cookie processing directory. If the persistent ID does not exist in step S63, the CPU 44 proceeds to step S91 and determines whether or not a persistent cookie file having the same domain path name exists in the cookie table (step S91). . Specifically, in the script, the cookie file name is specified as persistent despite the normal cookie file, and the persistent cookie file of the domain path specified in the script exists. In this case, the data specified by the script is added to the permanent cookie file (step S93).

Thus, the storage processing of the cookie file designated by the script is completed.

In step S75, if another persistent ID cookie file having the domain and path specified by the script exists,
Delete the existing cookie file (step S
77). Then, the processing from step S79 onward is executed.

As with the normal cookie file, the cookie expiration date may be stored in the permanent cookie file and deleted when the expiration date elapses.

6.4 [Cookie File Reading Process Using Mapping Information] Next, a cookie file reading process using mapping information will be described. Area 109 shown in FIG.
BML data “arib
If "-file: //ec/tvshopping/shop2/basket.bml" is specified and the reading process from the cookie file is described as a script, CPU4
4 executes the reading process from the cookie file as follows, and displays using the cookie file.

When the BML data "arib-file: //ec/tvshopping/shop2/basket.bml" shown in FIG. 26 is designated as the link destination, the CPU 44 determines that the resource read command has been given (Fig. 16 step S21), similarly, it is determined that the resource type is accumulated data, and step S29, step S26, and step S27 are executed.

The CPU 44 determines whether or not there is a script execution command (step S37). In this case, when a script for reading the cookie file and generating the necessary display data is described as a script in the area 109 shown in FIG. 20, the cookie file reading process is executed as follows (step S39).

The cookie file reading process will be described with reference to FIG. The CPU 44 determines the current directory as the cookie processing directory (step S51 in FIG. 21). In this case, the directory "arib-file: //
"ec / tvshopping / shop2 / bargain" is determined as the cookie processing directory.

The CPU 44 determines whether or not the mapping information exists in the domain mapping descriptor that is effective for this cookie processing directory (step S53 in FIG. 21).

In this case, the directory "arib-file: // ec
The mapping information "http://www.shoppingmall.co" is included in the domain mapping descriptor for "/ tvshopping / shop2".
Since "m / shop2" is set, the CPU 44 performs mapping processing for the cookie processing directory (step S55). Specifically, the current directory "arib-file: // ec / tvshopping / shop2 / bargain" is
Directory "http://www.shoppingmall.com/shop2"
Directory belonging to "http://www.shoppingmall.co
m / shop2 / bargain ”.

The CPU 44 determines whether the designated cookie process is a read process or a storage process (step S5).
7). In this case, since it is the reading process, the CPU 44
Reads all cookie files in the cookie processing directory or its upper directory (step S5).
9). In this case, the directory "http: //www.shoppingm
The cookie file for "all.com/shop2" and the cookie file for its upper directory are read. That is, the cookie file for the directory of the content server 6 is read out and not displayed for the local file on the hard disk of the receiving device 4, and the predetermined display is performed. In this way, by using the mapping information, the cookie file is transferred between the directories having different namespaces, the reading process to the cookie file specified by the script is executed, and the necessary display is performed.

When the image shown in FIG. 26 is displayed on the monitor 10 and the operator continues shopping, the area 12 is displayed.
Select and confirm 0. In the area 120, a script "Refer to history of browser program and return to previous display" is described. Therefore, in FIG.
43, the process proceeds to step S45, and the image shown in FIG. 20 is displayed on the monitor 10.

When the image shown in FIG. 20 is displayed on the monitor 10 and the user wants to see other products, the operator selects the area 11
Select and confirm 1. In the area 111, the resource "arib-fil
e: // ec / tvshopping / shop2 / bargain / gift / 4000 / coffeecu
Since “pyy.bml” is designated as the link destination, the image shown in FIG. 27 is displayed on the monitor 10 in the same manner.

If the operator does not wish to purchase this product and wants to see another product, he or she may select and confirm the area 121. Here, in the area 121, the resource "arib-d
It is assumed that "c: //0001.1001.1000/40/0002/coffeecupzz1.bml" is specified as the link destination. This allows
The image shown in FIG. 28 is displayed on the monitor 10.

When the operator desires to purchase the product shown in FIG. 28, the purchase history is similarly added to the permanent cookie file by the mapping data and the persistent ID.

On the basis of the description of the head portion of the resource, the CPU 44 determines in step S23 in FIG. 16 that the storage location of the resource is stream data (broadcast data), and makes the stream data a search target (see FIG. 16 steps S25). As a result, the CPU 44 searches for the target resource based on the directory structure shown in FIG. 15, and determines whether or not there is mapping data during the search (step S26). In this case, the CPU 44 uses the resource “arib-dc: //0001.1001.1000/40/0002/coffeecupzz.
Since "1.bml" is the linked resource, "arib-dc: /
/0001.1001.1000/40/0002 ”module is received and all modules are reproduced. As a result, the resources belonging to the directory “Timeservice / shop2” shown in FIG. 15 can be acquired. In this case, the target resource "arib-dc: //0001.1
"C identified by 001.1000 / 40/0002 / coffeecupzz1.bml"
directory "timeservice" to which "offeecupzz1.bml" belongs
As shown in FIG. 15, "http://www.shoppingmall.com/shop2" is set in "/ shop2" as mapping information. Therefore, the CPU 44 determines that the directory in which the target resource exists has mapping information.

When the CPU 44 determines that there is mapping information, it stores that there is mapping information in the directory specified by the mapping information (step S27 in FIG. 16). Then, the CPU 44 displays the target resource (step S41). As a result, the image shown in FIG. 28 is displayed on the monitor 10.

When the operator desires to purchase this product, the operator selects and confirms the area 129. `` Arib-dc: //0001.100
If "1000/40/0002 / basket.bml" is described as a link destination when the area 129 is selected and confirmed, an image as shown in FIG. 29 is displayed.

Further, in the area 129, a script for performing a cookie file storing process for storing shopping data is described. Therefore, when the area 129 is selected and confirmed, the CPU 44 proceeds from step S21 of FIG. 16 to step S37, determines that there is an execution command of the script (step S37), and executes the script (step S39).

The cookie process when the stream data has mapping information is the same as that already described for the accumulated data. That is, the CPU 44 sets the current directory as the cookie target directory (step S51) and performs mapping processing because there is mapping information (step S55). In this case, the CPU 44
Is the current directory "arib-dc: //0001.1001.1000
"/ 40/0002" is the directory "http: //www.shoppingmal"
l.com/shop2 "and remember as a persistent cookie file. The same applies to the storage processing as such a permanent cookie file. In this way, the shopping information shown in FIG. 29 is recorded in the cookie file for the directory of the content server 6, not for the broadcast content of the receiving device 4. The data stored in such a cookie file is shown in FIG. 30B.

In this way, the storage and read processing to the cookie file designated by the script is executed, and the necessary display is made (step S41).

When the image shown in FIG. 29 is displayed on the monitor 10 and the operator continues shopping, the area 12 is displayed.
Select and confirm 0. In the area 120, the script "Return to the previous display by referring to the history of the browser program" is described, whereby the image shown in FIG. 28 is displayed on the monitor 10.

If the image shown in FIG. 28 is displayed on the monitor 10 and the operator wants to see another product, the area 13 is displayed.
1 may be selected and confirmed. In the area 131, the resource "http://www.shoppingmall.com/shop2/coffee" shown in FIG. 31 is displayed.
"cup / wedge / coffeecupRR1.bml" is specified as the link destination. Therefore, the CPU 44 displays the image shown in FIG. 31 on the monitor 10 as follows.

6.5 [Cookie File Storage Processing Without Mapping Information] In step S23 of FIG. 16, the CPU 44 determines that the storage location of the resource is the communication content based on the description of the head portion of the resource. , Content server 6
In response, a request to send the file corresponding to the resource is output (step S33 in FIG. 16). The CPU 44
It is determined whether or not there is a response (step S35), and when received, the target resource is displayed (step S4).
1). As a result, the image shown in FIG. 31 is displayed on the monitor 10.

When the operator desires to purchase this product, he / she selects and confirms the area 139 shown in FIG. By selecting and confirming the area 139, the script associated with the area is executed. In this case, the cookie file "http://www.shoppingmall.com/shop2/pers
If the script is stored in "istent", the necessary data is stored in the target cookie file as follows.

In this case, in step S51 of FIG. 21, the current directory "http://www.shoppingmall.com/sh"
"op2 / coffeecup / wedge" is the cookie processing directory. Next, since there is no mapping information in the domain mapping descriptor that is effective for such a directory, it is determined in step S57 whether it is a reading process or a storing process. In this case, since it is a storage process, step S
At 61, it is determined whether the target cookie file is the cookie processing directory or its upper directory (step S61). In this case, since the target cookie file is managed in the upper directory of the cookie processing directory, the process proceeds to step S63, and it is determined whether or not the persistent ID is described in the domain mapping descriptor that is effective in the cookie processing directory. It is determined (step S63). In this case, since the persistent ID is not described, the process proceeds to step S91 in FIG. 23, and it is determined whether or not there is a persistent cookie with the same domain path name matching (step S91).
In this case, since it exists, the necessary data is added to the permanent cookie file (step S93). In this way, even if the persistent ID is not described, it is possible to add to the specified cookie file.

6.6 [Cookie File Reading Process without Mapping Information] In the area 139 shown in FIG. 31, the BML data “basket.bm” belonging to the subdirectory “shop2” in FIG.
The BML command for displaying "l" is described, and thereby the image shown in FIG. 32 is displayed.

The generation of such an image is executed by reading the persistent cookie file. Area 139
Describes a script that performs a cookie file reading process for storing shopping data. Therefore, when the area 139 is selected and confirmed, the CPU 44 proceeds from step S21 in FIG. 16 to step S43 and determines that there is an execution command for the script (step S4).
3) The script is executed (step S45).
This script will read the persistent cookie file that we have already created.

The cookie file reading process is the same as that already described. In this case, since there is no mapping information, the process is the same as the conventional cookie file reading process. That is, the current directory is set as the cookie target directory (step S
51), since there is no mapping information, it is determined whether the reading process or the storage process is performed without performing the mapping process (step S57). In this case, since this is a read process, the CPU 44 reads all cookie files in the cookie processing directory or its upper directory (step S59). In this case, the directory "ht
The cookie file for "tp: //www.shoppingmall.com/shop2/wedge" and the cookie file for its upper directory are read. That is, the cookie file generated with the BML data on the hard disk of the receiving device 4 is read and a predetermined display is performed. In this way, by using the mapping information, the cookie file is transferred between the directories having different namespaces, the reading process to the cookie file specified by the script is executed, and the necessary display is performed.

When the description destination directory is neither the cookie processing directory nor its upper directory in step S61 of FIG. 21, writing to the specified cookie file is prohibited and an error message is displayed (step S69).

The settlement processing using such shopping history data is the same as the conventional one. That is, when the button 145 is selected and confirmed while FIG. 32 is displayed,
The payment processing script is executed. Here, as the payment processing script, the processing of executing the CGI program “account.cgi” of the directory “http://www.shoppingmall.com” of the content server 6 may be described. The CGI program that executes such payment processing can receive the cookie data of the contents in the cookie file set in the directory to which the program belongs or the upper directory thereof, according to the standard of the normal cookie data reading processing. As already mentioned, the directory "http: //www.shoppingmall.
A cookie file as shown in FIG. 30C is associated with "com / shop2". Therefore, the content server 6 can receive the contents of the cookie file stored in the receiving device 4. The input processing of the destination and the payment method in the settlement processing is the same as usual, and thus the description thereof is omitted.

7. [Effects of Processing Using Mapping Information and Persistent ID] As described above, by creating a cookie file related to a mapping destination directory using mapping information, it is possible to identify any of stream content, stored content, and communication content. Also, the shopping history can be recorded in a common cookie file (one), and processing using this can be performed. Further, since the mapping data is stored in the resource list describing the directory structure of each file, the mapping destination can be specified at the time of file search. Therefore, as compared with the case where the mapping information is stored in the correspondence table format of the mapping source directory and the mapping destination directory, there is an effect that the search time becomes unnecessary. A correspondence table can also be used.

In the present embodiment, the mapping information is used to change the cookie processing directory. Therefore, the common cookie file can be used only in the specified range.
As a result, cookie data that exceeds the domain, which is a limitation of conventional cookie processing, can be exchanged only within a specified range, so that safety and convenience can be achieved at the same time.

Further, the shopping information input by displaying the stored content or the stream content can be collectively transferred as cookie data to the Internet content server, so that the shopping can be collectively paid.

If a persistent ID is set in the domain mapping descriptor, it is stored in the cookie table as a permanent cookie file that is highly excluded from deletion. Therefore, the cookie file can be excluded from the deletion target based on the access of the operator.

8. [Other Embodiments] In the above embodiment, the case where the broadcast data is broadcast by including an identifier indicating which cookie file for which directory is the permanent cookie file has been described. The cookie file stored as the cookie file may be specified by the user. For example, the user may be allowed to specify the domain or path of the communication content server.

Further, in the above-described embodiment, depending on whether the mapping data and the persistent ID are described in the domain mapping descriptor which has an effect on the cookie processing directory, the cookie processing directory or a higher-level directory thereof is set to the above-mentioned directory. Although it is determined whether the mapping data and the persistent ID are set, the present invention is not limited to this.

If either or both of the domains of the cookie setting destination directory are omitted in the script, it may be determined that the omitted data match. This simplifies script writing.

In the above embodiment, the case was explained in which the normal cookie file which is an erasable cookie file and the permanent cookie file which is a non-erasable cookie file are divided into two types. The degree of exclusion from the target may be stored.

When storing as a permanent cookie file, it is conceivable that a normal cookie file having the same domain path specified by the script and a name of persistent exists. In this case, the normal cookie file may be changed to a permanent cookie file, and the data specified by the script may be added. This processing is performed between steps S73 and S75, or steps S75 and S7.
You can make a decision between 9 and 9. In this case, the normal cookie file may be deleted and a new permanent cookie file may be generated.

Further, in the above embodiment, the case where the mapping data and the persistent ID are set in the domain mapping descriptor which is effective for the cookie processing directory has been described, but the mapping data and the persistent ID are set. The method of giving the above to the receiving device side is not limited to these, and for example, a directory and a correspondence table between these may be transmitted separately.

If a persistent ID is set in the domain mapping descriptor that has an effect on the cookie processing directory and another name is specified in the script, the permanent The name of the static cookie file may be persistent.

Further, in the above embodiment, the case where the cookie data is managed by the cookie file has been described, but in short, it is only necessary that the cookie data can be stored, and any format that can manage the cookie data may be used. .

It should be noted that a correspondence table of persistent IDs and directories (in the absolute path format) is stored in advance in the receiving device, and whether the cookie setting destination directory designated by the script matches the correspondence table. Whether or not to store the permanent cookie file may be determined depending on whether or not the file is stored. The correspondence table may be rewritten with broadcast data,
Further, it may be rewritten by a rewriting command from the center computer.

Further, in the above embodiment, a certain directory is searched in the direction of the root directory, and the first domain mapping descriptor is set as the domain mapping descriptor effective for the directory.
When the above determination is made, if the first discovered one is not set, it is determined whether it is set in a higher domain mapping descriptor, and if it exists, the directory is The above processing may be performed assuming that the mapping information and the persistent ID are set in the domain mapping descriptor.

The cookie files may be managed as separate files, or may be managed as a single file.

In the above embodiment, the case of online shopping is shown as an example. However, it is similarly applicable to other contents for which interactive processing such as a quiz program, a questionnaire survey, etc., in which cookie data is handed over is preferable. it can.

In this embodiment, the case where the namespaces are different has been described by taking the namespace managing communication contents, the namespace managing storage contents, and the namespace managing stream contents as an example. However, it can be similarly applied to the same series of namespaces, for example, between namespaces that manage the same storage-type content and between namespaces that manage stream content. Thus, in the present embodiment, directories with different namespaces mean that two directories do not belong to exactly the same directory.

In the above embodiment, the wireless broadcasting is explained, but the same can be applied to the case of using the wired broadcasting or the Internet. Further, it can be applied not only in the case of one-to-many (so-called simultaneous broadcasting) but also in the case of transmitting and receiving one-to-one.

Furthermore, the same can be applied to the transfer of cookie files between different domain servers on the Internet, assuming that the name spaces are different.

Further, in the above-described embodiment, the cookie file common to the three parties of the stream content, the stored content and the communication content is created. However, any two parties (stream content and stored content, stream content Any combination of communication contents, between stream contents and communication contents) is possible.

In this case, the mapping destination, that is, the virtual directory for creating the cookie data serves as a bidirectional communication content providing server.

Further, when the display is switched within the range in which the resources belonging to the mapping source and mapping destination directories are displayed, the value of browser.ureg may not be reset.

In the above embodiment, the case where the designation of each resource is the same as that in the conventional BS data broadcasting has been described, but the designation of each resource is not limited to this.

In the above embodiment, the case where the data input by the operator is transferred as cookie data has been described, but any method can be applied as long as it is a normal method of using cookie data. For example, the present invention can be applied to input assistance (support) of a user ID or a password, acquisition of history information of display contents of an operator, and the like. Further, the result data generated corresponding to the user's input can be passed.

Further, in the present embodiment, the case where each content does not have a hierarchical structure within each module of the stream content (broadcast content) like the current BS data broadcasting has been described, but each module has a hierarchical structure. However, the same can be applied.

In the above embodiment, the cookie file for the mapping destination directory is created when the cookie file is created, and the normal cookie file read processing is performed when the cookie file is read. This allows you to, like stored content and stream content,
Even in a namespace that does not perform bidirectional communication processing, data can be passed using cookie processing without creating a special transfer program.

The data input by the user has been described as an example of the data to be stored in the cookie file. However, other than that, it is also preferable to store the data in the normal cookie file as a value. Can be stored in.

In the above embodiment, the case where the cookie file is generated by mapping at the time of storage and the cookie file of the mapping destination is also read at the time of reading has been described, but either one may be used.

In the above embodiment, the case where the mapping destination directory and the directory associated with the mapping destination directory have the same path name and actually exist (/ shop2) has been described. However, the present invention is not limited to this, and the case where it does not exist is possible. FIG. 33A
Shows an example when it does not exist. This example further shows a case where a directory to which the mapping information is added is mapped with another path name. In the broadcast data directory "/ store / root / bcstore", the domain name "www.sh" of the mapping destination directory is used as mapping information.
op1.co.jp/internetshop2 ", path name" internetshop2 "
Is described. As a result, as shown in FIG. 33B, the directory “www.
directory "www.shop1.co.jp/inter" in "shop1.co.jp"
"netshop2" virtually exists, and the directory "ww
w.shop1.co.jp/internetshop2 ”,“ mall1 ”,“ mall ”
If the directories under 2 ”belong, it is possible to process cookie impersonation.

[0200] The directory of the path specified by the mapping information may or may not exist in the mapping destination directory. Even if a directory with the same path name exists virtually,
This is because if there is only cookie processing, there is no particular problem.

Further, in the above embodiment, the case has been described in which the cookie process is performed by assuming that the first directory virtually belongs to the directory one level higher than the second directory. However, the present invention is not limited to this, and the cookie process may be performed assuming that the first directory virtually belongs to the second directory.

Further, in the above embodiment, the first directory and the second directory are associated with each other by the mapping information, but the association of both directories is not particularly limited to this.

Further, in the above embodiment, the case where the communication content is described in BML data as well as the broadcast content has been described, but it is described in other structure description type language description data, for example, HTML or XML. In this case, the receiving device may be equipped with a function capable of interpreting such a language.

In this embodiment, in order to realize the functions shown in FIG. 5, a CPU is used and this is realized by software. However, some or all of it
It may be realized by hardware such as a logic circuit.

The operating system (OS) may be caused to perform a part of the processing of the program.

The computer-readable cookie processing program is a cookie processing program for causing a computer that manages data in a directory structure to execute processing for setting cookie data in the current directory or its upper directory.
When the mapping information that specifies the mapping destination directory exists in either the current directory or the upper directory thereof, it is determined whether the cookie data setting target directory is the mapping destination directory or the upper directory thereof. If the directory is the mapping destination directory or a higher-level directory, the setting of the cookie data is permitted. In this way, when the mapping information exists, it is determined whether the cookie data setting target directory is the mapping destination directory or its upper directory, and the mapping destination directory or its upper directory is determined. By permitting the setting of the cookie data, the setting can be performed from a directory different from the directory for which the cookie data is set or a subordinate directory. Therefore, it is possible to arbitrarily set a directory within a range that can be referenced and stored. Thereby, common cookie data can be set in a desired range.

The computer-readable cookie processing program according to the present invention is a cookie processing program for causing a computer that manages data in a directory structure to execute a reference / storing process only from a specific directory or a subordinate directory thereof. There
When the mapping destination directory exists in the specific directory or any of its upper directories, the reference / storing process is performed as the cookie data for the mapping destination directory instead of the cookie data for the specific directory. Thus, when the mapping destination directory exists, the cookie data for the mapping destination directory is referred to instead of the cookie data for the specific directory.
By performing the storage processing, the cookie data for the specific directory can be referred / stored not only from the directory or its subordinate directory but also from the mapping destination directory or its subordinate directory. Therefore, it is possible to arbitrarily set a directory within a range that can be referenced and stored. As a result, the cookie data can be referred / stored from a desired range.

The computer-readable cookie processing program according to the present invention is a cookie processing program for causing a computer that manages data in a directory structure to execute reference / storage processing only from a specific directory or a subordinate directory thereof. There
When the mapping information for specifying the mapping destination directory exists in the specific directory or any of the upper directories thereof, the mapping is designated for the mapping destination directory instead of the cookie data for the specific directory. If such a directory virtually exists, the cookie data is referred to and stored. Thus, when the mapping information exists, instead of the cookie data for the specific directory, the mapping destination directory is treated as if the mapping-specified directory virtually exists, and the cookie data is handled. By performing the reference / storing process of No. 2, the cookie data for the specific directory can be referred / stored not only from the directory or the subordinate directory thereof but also from the mapping destination directory or the subordinate directory thereof. Therefore, it is possible to arbitrarily set a directory within a range that can be referenced and stored. This allows
The cookie data can be referenced and stored from a desired range.

The image data display device according to the present invention is an image data display device for generating image data to be displayed on the display device based on the structure description type language description data described in the structure description type language. , 1) Structure description type language description data receiving means for receiving the structure description type language description data from the first directory management device that manages the structure description type language description data in a directory structure, 2) The received structure description Image data generation means for generating image data to be displayed on a display device based on the model language description data, 3) when the user inputs data based on the image data displayed on the display device, the structure description language If a script containing a data retention directive exists in the description data, the directory to be passed and specified specified in the script Data holding means for judging whether or not the directory is in the first directory management apparatus, and if the directory is in the first directory management apparatus, holding as passable data for the transfer target directory 4) When a directory of a second directory management device other than the first directory management device is designated in the script as the transfer target directory, the data holding means is configured to display the display device. It is determined whether the structure description type language description data for generating the image data to be displayed in FIG. 2 includes mapping information for specifying any one of the directories of the second directory management device as a mapping destination directory. Is the delivery for the directory of the second directory management device. And keep it as possible data. Thus, when the mapping information exists, the transfer target directory is
It is determined whether or not it is the directory of the second directory management device, and if so, the data is held as the transferable data, so that the transfer request is also sent from the directory of the second directory management device. It will be possible. Therefore, the transfer target directory can be arbitrarily set. As a result, the delivery is possible within a desired range. Further, the cookie processing program according to the present invention uses the first namespace for cookie data processing regarding data managed in the first namespace. The cookie process is performed by assuming the managed data as the data managed in the second namespace. Therefore, between the first namespace and the second namespace, cookie processing can be performed between different namespaces while ensuring security according to the rules for cookie processing. This further improves convenience.

Further, in the cookie processing program according to the present invention, data managed in the first namespace is data managed in the second namespace in the first directory of the first namespace. Are respectively managed in the second directory of the second namespace, and the first directory
And the second directory are associated with each other, the data managed in the first directory is assumed to be managed in the second directory, and cookie processing is performed. . Therefore, it is possible to perform a cookie process that is assumed not to be for the first directory but for the second directory cookie data associated with this.

Further, the cookie processing program according to the present invention performs the cookie processing by pretending that the first directory virtually belongs to the second directory. Therefore, the cookie process in which the first directory virtually belongs to the second directory becomes possible.

Further, the cookie processing program according to the present invention performs the cookie processing by pretending that the first directory virtually belongs to a directory one level above the second directory for managing the second directory. Therefore, the first directory is replaced by the second directory 1
It is possible to process cookies that virtually belong to directories on the hierarchy.

[0213] Further, the cookie processing program according to the present invention, if the mapping information with the second directory exists in the first directory, the first directory
The cookie process is performed on the assumption that the second directory is associated with the second directory. Therefore, if the mapping information is added to the first directory, the pseudo cookie process becomes possible.

Further, the cookie processing program according to the present invention performs the cookie data generation process assuming that the data in the first name space is managed in the second name space. Thus, by generating cookie data for data in the second namespace when generating cookie data,
The cookie process between the different namespaces can be performed only by performing the normal cookie read process.

Further, in the cookie processing program according to the present invention, the cookie processing is a cookie data generation processing which assumes that the data in the first name space is managed in the second name space. When the current directory is managed in the first namespace, in determining whether the generated cookie data corresponds to the upper directory of the current directory, regarding the upper directory of the second directory, Also determines that it is the upper directory and generates cookie data. Therefore, even if the cookie generation rule that the cookie data can be generated only for the current directory or its upper directory is applied, it is possible to generate the cookie data in the associated directory or its upper directory. Become. As a result, at the time of reading the cookie, the cookie processing can be performed between the different namespaces only by performing the normal cookie reading processing.

Further, in the cookie processing program according to the present invention, the cookie processing is a cookie data reading process that assumes that the data in the first namespace is managed in the second namespace. .
Therefore, when the cookie data is generated, the cookie processing can be performed between the different namespaces only by performing the normal cookie data generation processing.

Further, in the cookie processing program according to the present invention, the cookie processing is a read processing which assumes that the data in the first name space is managed in the second name space. In the case where the directory is managed in the second namespace, in determining whether the read cookie data corresponds to the upper directory of the current directory, the upper directory of the first directory is also The cookie data is read, judging that it is a higher-level directory. Therefore, even if the cookie read rule that the cookie data for the current directory or its upper directory can be read is applied, the cookie data for the associated directory or its upper directory can be read. As a result, when the cookie data is generated, the cookie processing can be performed between the different namespaces only by performing the normal cookie data generation processing.

In the cookie processing program according to the present invention, the first namespace is a namespace managed by a receiving device that manages broadcast data, and the second namespace is
Is a namespace managed by a server connected to the Internet. Therefore, cookie data can be substantially exchanged between the broadcast data and the communication data.

The image data display device according to the present invention is an image data display device for generating image data to be displayed on the display device, based on the structure description type language description data described in the structure description type language. , 1) Structure description type language description data receiving means for receiving the structure description type language description data from the first directory management device that manages the structure description type language description data in a directory structure, 2) The received structure description Image data generating means for generating image data for displaying the model language description data on the display device, 3) When the user inputs data based on the image data, the cookie data is held in the structure description language description data. If there is a script that contains a data retention directive that instructs the Is a directory to which the structure description language description data file belongs or an upper directory thereof. If it is a directory to which the structure description language description data file belongs or an upper directory thereof, the input Data holding means for holding data as transferable data for the transfer target directory is provided. When there is mapping information that specifies the mapping target directory, it is determined whether the transfer target directory is the mapping destination directory or its upper directory, and if it is the mapping destination directory or its upper directory. In the case of data, it is held as passable data. Thus, when the mapping information exists, the transfer target directory determines whether or not the mapping destination directory or its upper directory, if the mapping destination directory or its upper directory, By holding as the transferable data, the transfer request can be made from a directory different from the transfer target directory or a subordinate directory thereof. Therefore, the transfer target directory can be arbitrarily set. As a result, the delivery is possible within a desired range.

Further, in the image data display device according to the present invention, the mapping information is contained in the directory management information of the directory structure. Therefore,
Since the mapping destination can be specified at the time of specifying the file, the search processing of the mapping destination becomes unnecessary.

The image data display device according to the present invention is a set-top box, and the first directory management device is a recording unit for storing broadcast data in which contents are transmitted in a directory structure. The second directory management device is a content server connected to the Internet, and each content is managed in a directory structure. Therefore, the transferable data input as the broadcast content can be transferred to the Internet communication content.

Further, in the set-top box according to the present invention, the first directory management device stores in advance in the hard disk the broadcast data whose contents have been transmitted in a directory structure, and at the same time stores the broadcast data currently being received. Store sequentially. Therefore, it is possible to transfer the processing result data between the storage type content, the stream content and the Internet communication content based on the operation of the operator.

Further, in the set top box according to the present invention, when the display screen is switched within the range of the directory associated with the mapping information, the value of browser.ureg is held. Therefore, the value of browser.ureg can be shared within a predetermined range.

[Brief description of drawings]

FIG. 1 is a diagram showing an example of a display screen.

FIG. 2 is a diagram showing a directory structure of a content server.

FIG. 3 is a diagram showing a directory structure of accumulated data.

FIG. 4 is a diagram illustrating the concept of mapping.

FIG. 5 is a schematic diagram of an embodiment according to the present invention.

FIG. 6 is a functional block diagram of a transmission device.

FIG. 7 is a diagram showing a hardware configuration of a receiving device.

FIG. 8 is a diagram showing a structure of a cookie table.

FIG. 9 is a diagram showing the structure of a persistent cookie table.

FIG. 10 is a diagram showing a data structure of a DDB message.

FIG. 11 is a diagram showing a data structure of data DII.

FIG. 12 is a diagram showing a resource list data structure.

FIG. 13 is a diagram showing a directory structure of accumulated data.

FIG. 14 is a diagram showing a flowchart of a content storage processing program.

FIG. 15 is a diagram showing a directory structure of broadcast data.

FIG. 16 is a flowchart of processing for reading and displaying resources.

FIG. 17 is a diagram showing a screen display example.

FIG. 18 is a diagram showing a screen display example.

FIG. 19 is a diagram showing a screen display example.

FIG. 20 is a diagram showing a screen display example.

FIG. 21 is a flowchart of cookie processing.

FIG. 22 is a flowchart of cookie processing.

FIG. 23 is a flowchart of cookie processing.

FIG. 24 is a diagram showing a cookie table after storing a new cookie file.

FIG. 25 shows a persistent cookie table after writing a new cookie file.

FIG. 26 is a diagram showing a screen display example.

FIG. 27 is a diagram showing a screen display example.

FIG. 28 is a diagram showing a screen display example.

FIG. 29 is a diagram showing a screen display example.

FIG. 30 is a diagram showing an example of cookie data stored in a cookie file.

FIG. 31 is a diagram showing a screen display example.

FIG. 32 is a diagram showing a screen display example.

FIG. 33 is a diagram illustrating the concept of mapping.

[Explanation of symbols]

4 ... Receiving device 12 ... Receiver 13 ... Internet processing unit 14 ... Cookie processing unit 22 ... Control unit 24 ... Storage unit

─────────────────────────────────────────────────── ─── Continuation of front page (51) Int.Cl. ⁷ identification code FI theme code (reference) H04N 7/08 H04N 7/08 Z 7/081 (72) Inventor Hideaki Nakaoka 1006 Kadoma, Kadoma, Osaka Prefecture F term in Matsushita Electric Industrial Co., Ltd. (reference) 5B082 CA09 5B085 AA08 BE04 BG01 BG07 5C025 CA09 CB10 DA01 DA04 DA05 5C063 AB03 AB07 AB10 DA07 DA13 EB27

Claims (24)

[Claims] 1. When a permanent cookie identification identifier and a cookie data setting command are given, the cookie data for the directory specified as the cookie setting destination directory in the cookie data setting command is deleted in comparison with the erasable cookie data. A cookie processing program characterized by storing as non-erasable cookie data that is highly excluded from the target. 2. When a permanent cookie specific identifier and a cookie data setting command are given, the cookie data for the directory specified as the cookie setting destination directory by the cookie data setting command is stored in the cookie data storage area as a normal cookie. Stored as special cookie data different from the data, and when another cookie data storage command is given to the cookie data storage area, storing the other cookie data without erasing the special cookie data, A cookie processing program. 3. The cookie processing program according to claim 2, wherein by deleting the normal cookie data, the other cookie data is stored without erasing the special cookie data. 4. The cookie processing program according to claim 1, wherein when the cookie processing program matches a decision rule for determining whether or not to store as the non-erasing target cookie data, the non-erasing target cookie data is stored. What is characteristic. 5. The cookie processing program according to claim 2 or 3, wherein the special cookie data is deleted when the determination rule for deciding whether or not to store the special cookie data is met. Instead, storing the other cookie data. 6. The cookie processing program according to claim 4 or 5, wherein the cookie processing program includes a first directory managed in a first namespace and a second directory managed in a second namespace. When the mapping information with the second directory exists, the data managed in the first directory is assumed to be managed in the second directory, and the cookie processing program performs the cookie processing. In the case where the cookie setting destination directory matches the second directory specified by the mapping information, it is determined that the cookie setting destination directory matches the determination rule. 7. The cookie processing program according to claim 6, wherein when the cookie setting destination directory is a higher-level directory of the second directory, it is determined that the determination rule is met. 8. The cookie processing program according to claim 6, wherein when the cookie setting destination directory is the second directory, it is determined that the determination rule is met. 9. The cookie processing program according to claim 8, wherein when the cookie setting destination directory is omitted in the cookie data setting command, it is determined that the cookie setting destination directory is the second directory. . 10. The cookie processing program according to claim 9, wherein when the path name of the cookie setting destination directory is omitted in the cookie data setting command, the domain name of the cookie setting destination directory is the second directory. To determine if it matches the domain name of. 11. The cookie processing program according to claim 9, wherein when the domain name of the cookie setting destination directory is omitted in the cookie data setting command, the path name of the cookie setting destination directory is the second directory. To determine if it matches the pathname of. 12. The cookie processing program according to claim 9, wherein when the domain name and path name of the cookie setting destination directory are omitted in the cookie data setting command, the cookie setting destination directory is the second directory. What is judged to match. 13. When a cookie data setting command is given when the first directory of the first namespace and the second directory of the second namespace are associated with each other,
A cookie processing program for pretending that the data managed in the first directory is managed in the second directory, and performing a cookie data storing process, wherein a permanent cookie specific identifier is given. In this case, the cookie data to be stored is stored as non-erasable cookie data having a higher degree of exclusion from the erasure target than the erasable cookie data. 14. The cookie processing program according to claim 1, wherein when the directory specified as the cookie setting destination directory is managed by the communication content server determined by the user, the cookie data is set as the non-erasure target cookie. It is characterized by storing as data. 15. A recording medium on which the program according to claim 1 is recorded. 16. A data structure of structure-description language description data, which is described in a structure-description language received by a receiving device, wherein said structure-description language description data includes the following 1) and 2): , 1) Cookie setting command including specification of cookie setting destination directory, 2) Cookie data specified by the cookie setting command is not deleted even if new cookie data is newly stored in the cookie storage unit. A data structure of structure description type language description data characterized by a persistent cookie specific identifier for deciding whether to store as a cookie. 17. When a permanent cookie identification identifier and a cookie data setting command are given, the cookie data for the directory specified as the cookie setting destination directory in the cookie data setting command is deleted in comparison with the erasable cookie data. A cookie processing device characterized by storing as non-erasing target cookie data that is highly excluded from the target. 18. When a permanent cookie identification identifier and a cookie data setting command are given, the cookie data for the directory specified as the cookie setting destination directory in the cookie data setting command is deleted in comparison with the erasable cookie data. A cookie processing method characterized by storing as non-erasable cookie data that is highly excluded from the target. 19. A structure description language description data written in a structure description language to be broadcast, comprising mapping information for sharing cookie data between a directory managing broadcast contents and a directory managing communication contents. Structure description type language description data received by each receiving device in a content fusion method in which a description is acknowledged and thereby a distributor of the communication content can acquire a user who accesses the communication content with a broadcast content as an entrance. If the persistent cookie setting ID and the cookie setting command are present therein, it is determined whether or not the cookie setting destination directory matches the directory for managing the communication content. If they match, the cookie data is ,
A content fusion method characterized by storing as a permanent cookie that is not deleted even when another cookie data is newly stored in the cookie storage unit. 20. The content merging method according to claim 19, wherein whether or not the cookie setting destination directory is managed by a specific namespace is determined by the domain of the cookie setting destination directory. 21. A mapping information for sharing cookie data between a directory managing broadcast contents and a directory managing communication contents, in structure description language description data described in a broadcast structure description language. Structure description type language description data received by each receiving device in a content fusion method in which a description is acknowledged and thereby a distributor of the communication content can acquire a user who accesses the communication content with a broadcast content as an entrance. If there is a persistent cookie setting ID and cookie setting command in it, it is judged whether or not the cookie setting destination directory is managed by a specific namespace, and if they match, the cookie data is stored in the cookie. Permanent cookie that will not be erased even if another part of the cookie data is stored A content fusion method characterized by storing as a sticky. 22. When structure description language description data described in a structure description language including mapping information for sharing cookie data between a directory managing broadcast contents and a directory managing communication contents is broadcast. The user who has received the structure description type language description data accesses the communication content via the broadcast content, and the cookie data generated during the reproduction of the broadcast content is based on the mapping information. In the cookie data processing method capable of being delivered to the server for delivering the cookie data, the cookie data for the directory managed by the server for delivering the communication content is provided to each receiving device regardless of the free space of the cookie data storage unit. Remember as a persistent cookie that you do not delete And a cookie data processing method characterized by: 23. A program for determining deletion target cookie data to be deleted from a cookie data storage area, for determining whether or not to exclude some or all of the cookie data from the deletion target cookie data. A program for determining the cookie data to be deleted, characterized in that the retention level is set. 24. The cookie data is stored in the cookie data storage area separately for the first group and the second group, and one of the cookie data is stored in order to store new cookie data in the cookie data storage area. When deleting, the cookie data belonging to the first group is set as a deletion target.