JP2011209842A - Device and program for packaging pixel - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent DRM information from being altered, and to prevent an image file from being reproduced.SOLUTION: A pixel packaging device 200 generates basic information data 112A for each of the pixels of an image file. The basic information data 112A includes an image file number for identifying an image file, a pixel number for identifying the pixel, the color or luminance of the pixel, and the DRM information or inventory information of the image file. The pixel packaging device 200 generates a pixel package file 110 including the basic information data 112A of all pixels as a file equivalent to an image file. A pixel package file distribution server 300 distributes the pixel package file 110. A pixel package file reproduction terminal 400 determines whether to permit the reproduction of an image based on the DRM information for each basic information data A, and displays the image when the reproduction of the image is permitted with respect to all basic information data 112A.

Description

  The present invention relates to a pixel packaging apparatus and a pixel packaging program for generating a pixel package file corresponding to image data, for example.

  Conventionally, for image files, inventory information and DRM information (DRM: Digital Rights Management) are managed separately from the image file, and whether or not the image file can be reproduced is determined when the image is downloaded or reproduced. ing.

JP-A-7-123392

  An object of the present invention is to prevent, for example, alteration of DRM information and reproduction of an image file.

The pixel packaging device of the present invention is
A pixel value extraction unit that inputs target image data including pixel values of each of a plurality of pixels constituting the target image, and extracts pixel values from the input target image data;
A pixel unit data generation unit that generates pixel unit data for each pixel including pixel values extracted by the pixel value extraction unit and restriction information indicating a predetermined condition for restricting display of the target image;
A pixel package file generation unit that generates a pixel package file including the pixel unit data generated by the pixel unit data generation unit.

The pixel packaging device further includes:
A pixel list data generation unit that generates pixel list data that lists pixel identification values for identifying pixels;
The pixel package file generation unit generates a pixel package file including the pixel unit data and the pixel list data generated by the pixel list data generation unit.

The pixel package file distribution system of the present invention is
The pixel packaging device;
A pixel package file delivery device for delivering a pixel package file generated by the pixel packaging device;
Storing the pixel package file distributed from the pixel package file distribution device, determining whether to permit display of the target image based on the restriction information included in the pixel unit data in the pixel package file; A pixel package file reproducing device for displaying a target image on a display device based on a pixel value included in pixel unit data in the pixel package file.

The pixel packaging program of the present invention is
Pixel value extraction processing for inputting target image data including pixel values of each of a plurality of pixels constituting the target image, and extracting pixel values from the input target image data;
Pixel unit data generation processing for generating pixel unit data for each pixel including pixel values extracted by the pixel value extraction processing and restriction information indicating a predetermined condition for restricting display of the target image;
A computer is caused to execute a pixel package file generation process for generating a pixel package file including the pixel unit data generated by the pixel unit data generation process.

  According to the present invention, for example, it is possible to prevent the DRM information from being altered and the image file from being reproduced.

1 is a configuration diagram of an image distribution system 100 according to Embodiment 1. FIG. 2 is a functional configuration diagram of a pixel packaging device 200 according to Embodiment 1. FIG. 2 is a functional configuration diagram of a pixel package file distribution server 300 according to Embodiment 1. FIG. 2 is a functional configuration diagram of a pixel package file reproduction terminal 400 according to Embodiment 1. FIG. 5 is a flowchart showing package file registration processing in the first embodiment. FIG. 3 is a configuration diagram of a pixel package file 110 in the first embodiment. 5 is a flowchart showing package file delivery processing in the first embodiment. 5 is a flowchart showing package file playback processing in the first embodiment. FIG. 3 is a diagram illustrating an example of hardware resources of the image distribution system 100 according to the first embodiment. FIG. 6 is a schematic diagram of an image distribution method of the image distribution system 100 according to the second embodiment. 10 is a table showing reproduction conditions for the pixel package file 110 according to the second embodiment.

Embodiment 1 FIG.
An image distribution system having an apparatus for packaging pixel information of a plurality of pixels constituting an image and generating a package file, an apparatus for distributing the package file, and an apparatus for reproducing an image based on the package file will be described. .

FIG. 1 is a configuration diagram of an image distribution system 100 according to the first embodiment.
The configuration of the image distribution system 100 according to Embodiment 1 will be described below with reference to FIG.

The image distribution system 100 (an example of a package file distribution system) includes a pixel packaging device 200, a pixel package file distribution server 300, and a pixel package file reproduction terminal 400.
The pixel packaging device 200, the pixel package file distribution server 300, and the pixel package file playback terminal 400 communicate via the network 101.

The pixel packaging device 200 generates a pixel package file 110 including pixel values of each of a plurality of pixels constituting an image, and provides the generated pixel package file 110 to the pixel package file distribution server 300.
The pixel package file distribution server 300 registers the pixel package file 110 provided from the pixel packaging device 200.

The pixel package file distribution server 300 distributes the pixel package file 110 to the pixel package file reproduction terminal 400.
The pixel package file reproduction terminal 400 reproduces image data included in the pixel package file 110 when the user who reproduces the pixel package file 110 matches the user who downloaded the pixel package file 110.

FIG. 2 is a functional configuration diagram of the pixel packaging device 200 according to the first embodiment.
A functional configuration of the pixel packaging device 200 according to Embodiment 1 will be described below with reference to FIG.

  The pixel packaging apparatus 200 includes a package file generation unit 210, a package file transmission unit 220, an image file storage unit 280, and a pixel package file storage unit 290.

  The package file generation unit 210 includes a pixel data extraction unit 211, a pixel number conversion unit 212, a pixel basic data generation unit 213, a basic information file generation unit 214, and a package processing unit 215, and generates a pixel package file 110.

  A pixel data extraction unit 211 (an example of a pixel value extraction unit) receives target image data including pixel values of a plurality of pixels constituting the target image, and extracts pixel values from the input target image data.

  The pixel number conversion unit 212 specifies a pixel number for identifying a pixel based on the two-dimensional coordinate value of the pixel for each pixel.

  The pixel basic data creation unit 213 (an example of a pixel list data generation unit) generates pixel list data that lists pixel identification values for identifying pixels.

  The basic information file creation unit 214 (an example of the pixel unit data generation unit) includes pixel unit data including the pixel value extracted by the pixel data extraction unit 211 and restriction information indicating a predetermined condition for restricting display of the target image. For each pixel.

The package processing unit 215 (an example of a pixel package file generation unit) generates the pixel package file 110 including the pixel unit data generated by the basic information file generation unit 214.
For example, the package processing unit 215 generates the pixel package file 110 including the pixel unit data and the pixel list data generated by the pixel basic data creation unit 213.

  The package file transmission unit 220 transmits the pixel package file 110 to the pixel package file distribution server 300.

  The image file storage unit 280 stores target image data.

  The pixel package file storage unit 290 stores the pixel package file 110 generated by the package processing unit 215.

“Color” and “luminance” are examples of pixel values.
An “image file” to be described later is an example of target image data.
“Pixel basic data 111” to be described later is an example of pixel list data.
“Basic information data 112A” to be described later is an example of pixel unit data.

“DRM information” is an example of restriction information.
For example, the DRM information includes user authentication information used for user authentication and copy permission information indicating whether or not copying of a package file is permitted.
The user authentication information includes authentication necessity information indicating whether or not user authentication is necessary, authentication device information specifying a user authentication device that performs user authentication, and authentication method information indicating a user authentication method.

“Allowed authentication data” to be described later is an example of user authentication information.
“Browsing permission / non-permission”, “permission confirmation destination”, and “permission confirmation method” to be described later are examples of authentication necessity information, authentication device information, and authentication method information.
“Copy permission data” to be described later is an example of copy permission information.

FIG. 3 is a functional configuration diagram of the pixel package file distribution server 300 according to the first embodiment.
A functional configuration of the pixel package file distribution server 300 according to the first embodiment will be described below with reference to FIG.

  The pixel package file distribution server 300 includes a file reception / storage unit 310, an access processing unit 320, a package file access unit 330, a login inquiry unit 331, a package file distribution unit 332, a package file storage unit 390, and a login information storage unit 391. .

  The file receiving / saving unit 310 receives the pixel package file 110 from the pixel packaging device 200 and stores the received pixel package file 110 in the package file storage unit 390.

The access processing unit 320 receives server login data from the pixel package file reproduction terminal 400 as user login data for the pixel package file distribution server 300.
The access processing unit 320 determines whether or not to permit user login based on the received server login data and the registered user data stored in the login information storage unit 391.

  The package file access unit 330 receives from the pixel package file playback terminal 400 a package file distribution request that designates the pixel package file 110 to be distributed as a distribution request file.

The login inquiry unit 331 inputs a distribution request file from the package file storage unit 390 based on the package file distribution request.
The login inquiry unit 331 determines whether to permit distribution of the distribution request file based on the user authentication information included in the pixel unit data in the distribution request file and the server login data received by the access processing unit 320. .
For example, the login inquiry unit 331 refers to the user authentication information included in the pixel unit data in the distribution request file, and the user authentication device specified in the authentication device information when the authentication necessity information indicates that user authentication is required. Server login data and authentication method information are transmitted to the server. The login inquiry unit 331 receives an authentication result indicating whether or not to allow the user to be authenticated from the user authentication device, and determines whether or not to permit distribution of the distribution file based on the received authentication result.

When distribution is permitted by the login inquiry unit 331, the package file distribution unit 332 generates a file obtained by adding server login data (an example of permitted user identification data) to the pixel unit data in the distribution request file as a distribution file.
The package file distribution unit 332 distributes the generated distribution file to the pixel package file reproduction terminal 400.

  The package file storage unit 390 stores a plurality of pixel package files 110 provided from the pixel packaging device 200.

  The login information storage unit 391 stores data of each of a plurality of users permitted to use the pixel package file distribution server 300 as registered user data.

  A “distribution login ID” to be described later is an example of server login data (permitted user identification data).

FIG. 4 is a functional configuration diagram of the pixel package file playback terminal 400 according to the first embodiment.
The functional configuration of the pixel package file playback terminal 400 according to Embodiment 1 will be described below with reference to FIG.

  The pixel package file reproduction terminal 400 includes a package file distribution server access unit 410, a package file distribution request unit 420, a package file reception unit 421, a package file reproduction unit 430, a DRM information confirmation unit 431, and a terminal storage unit 490.

The package file delivery server access unit 410 inputs server login data as user login data for the pixel package file delivery server 300.
The package file distribution server access unit 410 transmits the input server login data to the pixel package file distribution server 300.

  The package file distribution request unit 420 transmits to the pixel package file distribution server 300 a package file distribution request that designates a package file to be distributed as a distribution request file.

  The package file receiving unit 421 receives a distribution file including a distribution request file and server login data from the pixel package file distribution server 300.

The package file playback unit 430 (an example of a user identification data input unit) inputs terminal login data (an example of specific user identification data) as user login data for the pixel package file playback terminal 400.
The package file reproduction unit 430 inputs a distribution file reproduction request that designates a distribution file to be reproduced as a reproduction request file.
When the DRM information confirmation unit 431 permits display of the target image for all pixel unit data, the package file reproduction unit 430 (an example of an image display unit) applies to all the pixel unit data in the pixel package file 110, respectively. The target image is displayed on the display device based on the included pixel information.
For example, the package file playback unit 430 displays the target image when the server login data matches the terminal login data in all pixel unit data.
Further, the package file playback unit 430 displays the target image when copying of the target image is permitted for all pixel unit data.

The DRM information confirmation unit 431 (an example of a display permission determination unit) determines, for each pixel unit data, whether or not to permit display of the target image based on the restriction information included in the pixel unit data in the pixel package file 110. .
For example, the DRM information confirmation unit 431 determines whether or not the terminal login data and the server login data (an example of restriction information) match for each pixel unit data as a display permission determination for determining whether or not to permit display of the target image. Judgment.
Further, the DRM information confirmation unit 431 determines, for each pixel unit data, whether or not to permit copying of the target image based on the copy permission information (an example of restriction information).

  The terminal storage unit 490 (an example of a distribution file storage unit) stores the distribution file received by the package file reception unit 421.

  “Reproduction login ID” described later is an example of terminal login data (specific user identification data).

  Next, as an image distribution method (an example of a package file distribution method) of the image distribution system 100, a package file registration process, a package file distribution process, and a package file reproduction process will be described.

FIG. 5 is a flowchart showing the package file registration process in the first embodiment.
The package file registration process in the first embodiment will be described below with reference to FIG.

  In S111, the pixel data extraction unit 211 acquires an image file to be packaged from the image file storage unit 280, and extracts pixel data for each pixel from the acquired image file.

  For example, an image file to be packaged is designated by a package file provider using an input device (keyboard, mouse, etc.).

The image file is stored in advance in the image file storage unit 280 and is identified by the image file number.
The image file includes data (pixel data) of each of a plurality of pixels constituting the image and represents a specific image.
The pixel data indicates pixel values such as color (for example, RGB values), luminance, and coordinate values in the image.

Also, DRM information and inventory information are defined for each image file. It is assumed that the DRM information and inventory information are stored in the image file storage unit 280 in association with the image file number.
The DRM information and inventory information will be described later.

  It progresses to S112 after S111.

  In S112, the pixel number conversion unit 212 converts the coordinate values included in the pixel data into pixel numbers for all the pixel data extracted in S111.

For example, if the size of the image is “640 × 480” pixels, the pixel number conversion unit 212 calculates the pixel number (= (v × 640) + (u + 1)) of the pixel having the coordinate value (u, v). .
The pixel number of the pixel with the coordinate value (0,0) is “1”, the pixel number of the pixel with the coordinate value (639,0) is “640”, and the pixel number of the pixel with the coordinate value (0,1) is “641”. It becomes.

  It progresses to S113 after S112.

In S113, the pixel basic data creation unit 213 generates the pixel basic data 111 using the pixel number generated in S112.
It progresses to S114 after S113.

FIG. 6 is a configuration diagram of the pixel package file 110 according to the first embodiment.
As shown in FIG. 6, the basic pixel data 111 is data in which pixels are listed by “image file number” and “pixel number”.
One pixel is specified by a combination of “image file number” and “pixel number”.

  Returning to FIG. 5, the description of the package file registration process will be continued.

In S114, the basic information file creation unit 214 generates the basic information file 112 using the pixel data extracted in S111, the pixel number generated in S112, and inventory information and DRM information corresponding to the image file. Inventory information and DRM information are stored in advance in the image file storage unit 280 in association with image file numbers.
It progresses to S115 after S114.

As shown in FIG. 6, the basic information file 112 has basic information data 112A for each of all the pixels constituting the image file.
The basic information data 112A is data including an image file number, a pixel number, pixel data (luminance, color, etc.), inventory information, and DRM information. The image file number, inventory information, and DRM information are common to the basic information data 112A of all the pixels, and the pixel number and pixel data differ depending on the pixel corresponding to the basic information data 112A.

  The inventory information indicates information about the image file such as the generation time and the creator of the image file. The inventory information is referred to by the user who reproduces the image file.

The DRM information is information related to the copyright of the image file.
The DRM information includes permission authentication data and copy permission data.

The permission authentication data includes “viewing permission / inhibition”, “permission confirmation destination”, and “permission confirmation method” as information.
The presence / absence of browsing permission is information indicating whether or not browsing of an image is necessary.
The permission confirmation destination is information indicating a device (for example, a user authentication device) that confirms browsing permission.
The permission confirmation method is information indicating items for confirming the user such as age and authority.

  The duplication permission data indicates whether or not copying of an image is permitted.

  Returning to FIG. 5, the description of the package file registration process will be continued.

In S115, the package processing unit 215 generates the pixel package file 110 using the pixel basic data 111 generated in S113 and the basic information file 112 generated in S114. The package processing unit 215 stores the generated pixel package file 110 in the pixel package file storage unit 290.
It progresses to S120 after S115.

  As shown in FIG. 6, the pixel package file 110 is data including pixel basic data 111 and a basic information file 112.

  The pixel package file 110 is identified by a package ID.

  Returning to FIG. 5, the description of the package file registration process will be continued.

In S120, the package file transmission unit 220 transmits the pixel package file 110 generated in S115 to the pixel package file distribution server 300.
The file reception / storage unit 310 of the pixel package file distribution server 300 receives the pixel package file 110 and registers the received pixel package file 110 in the package file storage unit 390.
By S120, the package file registration process ends.

FIG. 7 is a flowchart showing the package file distribution process in the first embodiment.
The package file distribution process in the first embodiment will be described below with reference to FIG.

In S210, the access processing unit 320 of the pixel package file distribution server 300 receives login data for the image distribution service from the pixel package file reproduction terminal 400, and performs a user login process for the image distribution service.
Hereinafter, the login data for the image distribution service received in S210 is referred to as “distribution login data”.

For example, the package file delivery server access unit 410 of the pixel package file playback terminal 400 displays a login screen (WEB page) of the image delivery service on the display device, and the user uses his input device to enter his / her user ID and password on the login screen. Enter.
The package file distribution server access unit 410 transmits the user ID and password input on the login screen to the pixel package file distribution server 300 as distribution login data. The access processing unit 320 of the pixel package file distribution server 300 receives the distribution login data.
The access processing unit 320 searches for a plurality of registered user data registered in the login information storage unit 391. The registered user data indicates the user ID and password of a user registered in the image distribution service.
When the user ID and password included in the distribution login data match any registered user data, the access processing unit 320 permits login to the image distribution service and returns a distribution request screen. The package file distribution server access unit 410 displays a distribution request screen.
If the user ID and password included in the distribution login data do not match any registered user data, the access processing unit 320 rejects the login to the image distribution service and returns a login error screen. The package file delivery server access unit 410 displays a login error screen. In this case, the user returns to the login screen, re-enters the user ID and password, and tries to log in to the image distribution service again.

  After login to the image distribution service is permitted in S210, the process proceeds to S220.

In S220, the package file access unit 330 of the pixel package file distribution server 300 receives the package file distribution request from the pixel package file reproduction terminal 400.
The package file distribution request is data specifying a pixel package file 110 (hereinafter referred to as “distribution request file”) that the user wants to download.

For example, the package file distribution request unit 420 of the pixel package file reproduction terminal 400 displays a distribution request screen. The distribution request screen is a screen listing the package IDs of the pixel package file 110 distributed from the pixel package file distribution server 300. The user selects a pixel package file 110 to be downloaded from the list on the distribution request screen.
The package file distribution request unit 420 transmits a package file distribution request specifying the selected pixel package file 110 as a distribution request file, and the access processing unit 320 receives the package file distribution request.

  It progresses to S230 after S220.

In S230, the login inquiry unit 331 acquires the distribution request file specified in the package file distribution request from the package file storage unit 390.
The login inquiry unit 331 refers to the basic information data 112A in the distribution request file, and determines whether or not to permit distribution based on the permission authentication data included in the DRM information in the basic information data 112A. Since the DRM information is common to all the basic information data 112A included in the distribution request file, any basic information data 112A may be referred to.

For example, the login inquiry unit 331 permits distribution when the permission authentication data indicates “no browsing permission”.
In addition, when the permission authentication data indicates “browsing permission exists”, the login inquiry unit 331 issues a user authentication request including the user ID of the distribution login data and the “permission confirmation method” included in the permission authentication data. Send to. The user authentication device is designated as “permission confirmation destination” in the permission authentication data.
The user authentication device stores attribute information such as age and type (free user, paid user) in association with a user ID for each registered user.
The user authentication device determines whether to permit distribution based on the attribute information of the registered user corresponding to the user ID included in the user authentication request and the “permission confirmation method”. For example, if the age of the registered user is 20 and the “permission confirmation method” is “18 years old or older” and the age is restricted, distribution is permitted. If the type of registered user is “free user” and the “permission confirmation method” restricts free users, distribution is rejected.
The user authentication device returns a determination result, and the login inquiry unit 331 uses the determination result of the user authentication device.

After the authentication is permitted in S230, the process proceeds to S240.
If the authentication is not permitted in S230, the package file delivery unit 332 returns a delivery error screen, and the package file delivery request unit 420 of the pixel package file playback terminal 400 displays the delivery error screen. In this case, the user returns to the distribution request screen and designates the pixel package file 110 again.

In S240, the package file distribution unit 332 adds the user ID of the distribution login data to the DRM information of all the basic information data 112A for the distribution request file. Hereinafter, the user ID added to the DRM information is referred to as “distribution login ID”.
The package file distribution unit 332 transmits the distribution request file to which the distribution login ID is added to the pixel package file reproduction terminal 400 as a distribution file.
The package file receiving unit 421 of the pixel package file reproduction terminal 400 receives the distribution file, and stores the received distribution file (pixel package file 110) in the terminal storage unit 490.
By S240, the package file distribution process ends.

FIG. 8 is a flowchart showing package file playback processing in the first embodiment.
The package file reproduction process in the first embodiment will be described below with reference to FIG.

  In S310, the package file reproduction unit 430 of the pixel package file reproduction terminal 400 inputs the package ID of the pixel package file 110 that the user wants to reproduce and the user ID for the image distribution service.

For example, the user activates the package file reproduction unit 430 to reproduce the pixel package file 110.
The package file playback unit 430 displays a login screen for inputting a user ID, and the user inputs the user ID for the image distribution service on the login screen.
The package file reproduction unit 430 displays the pixel package file 110 stored in the terminal storage unit 490 as a list, and the user selects the pixel package file 110 (package ID) from the list.

  When the user designates the pixel package file 110 first and the pixel package file 110 is designated, the package file reproduction unit 430 is activated, and then the package file reproduction unit 430 may request the user ID on the login screen. Absent.

Hereinafter, the user ID input in S310 is referred to as “reproduction login ID”.
The pixel package file 110 designated in S310 is referred to as a “reproduction request file”.

  It progresses to S320 after S310.

  In S320, the DRM information confirmation unit 431 acquires the reproduction request file from the terminal storage unit 490, and determines whether or not reproduction of the reproduction request file is permitted as follows.

For each basic information data 112A in the reproduction request file, the DRM information confirmation unit 431 compares the distribution login ID included in the DRM information in the basic information data 112A with the reproduction login ID. The DRM information confirmation unit 431 can know the number of basic information data 112A by referring to the pixel basic data 111 in the reproduction request file.
When the distribution login ID of all the basic information data 112A matches the reproduction login ID, the DRM information confirmation unit 431 permits the reproduction of the reproduction request file.
If the distribution login ID of at least one of the basic information data 112A does not match the reproduction login ID, the DRM information confirmation unit 431 copies the basic information data 112A included in the DRM information in the basic information data 112A for each basic information data 112A in the reproduction request file. Refer to permission data.
When the copy permission data of all the basic information data 112A indicates “copy permission”, the DRM information confirmation unit 431 permits the playback of the playback request file.
When the copy permission data of at least one of the basic information data 112A does not indicate “copy permission”, the DRM information confirmation unit 431 does not permit the playback of the playback request file. When “duplication permission” is not indicated, when the duplication permission data indicates “duplication not permitted”, when the DRM information does not include duplication permission data, the duplication permission data indicates “duplication permitted” and “duplication not permitted”. This is the case when an unspecified value that is neither of the above is shown. This is because there are cases where the DRM information has been tampered with and the copy permission data is not included in the DRM information, or the copy permission data shows an unspecified value.

  If the number of pixels indicated in the basic pixel data 111 in the reproduction request file does not match the number of basic information data 112A in the reproduction request file, the DRM information confirmation unit 431 determines that the reproduction request file has been falsified. However, playback of the playback request file is not permitted.

  Further, the DRM information confirmation unit 431 determines whether or not the DRM information matches in all the basic information data 112A. If the DRM information does not match, the DRM information confirmation unit 431 does not permit the playback of the playback request file regardless of the determination result. May be. This is because it is considered that the reproduction request file has been tampered with.

  It progresses to S321 after S320.

If reproduction is permitted in S321 (YES), the process proceeds to S330.
When reproduction is not permitted in S321 (NO), the package file reproduction unit 430 displays a reproduction error screen, and the package file reproduction process ends. At this time, the reproduction request file may be destroyed so that the pixel package file 110 cannot be reproduced.

In S330, the package file reproduction unit 430 specifies the color and luminance of the pixel based on the pixel data (color, luminance, etc.) indicated in the basic information data 112A for each basic information data 112A in the reproduction request file.
The package file reproduction unit 430 identifies coordinates in the image based on the pixel number indicated in the basic information data 112A, and identifies dots in the display device corresponding to the identified coordinates.
The package file reproduction unit 430 displays pixels on the display device by displaying pixels with the color and brightness specified for the dots in the specified display device.
By S330, the package file reproduction process ends.

By the above image distribution method, for example, the reproduction of the pixel package file 110 can be restricted as follows.
If “18 years or older” is set as the permission authentication method in the DRM information of the pixel package file 110 and “duplication not permitted” is set as the copy permission data, the pixel package file 110 delivered to the user 18 years or older is 18 years old. It can be prevented from being played by fewer users.
If “duplication permission” is set as copy permission data in the DRM information of the pixel package file 110, a plurality of users using the pixel package file playback terminal 400 can play back the pixel package file 110.

  Further, since all the pixels (basic information data 112A) include DRM information and permission of reproduction is determined based on the DRM information of all pixels, it is possible to prevent a part of the pixels from being tampered with and reproducing an image. Can do.

FIG. 9 is a diagram illustrating an example of hardware resources of the image distribution system 100 according to the first embodiment.
In FIG. 9, the pixel packaging device 200, the pixel package file distribution server 300, and the pixel package file playback terminal 400 include a CPU 911 (Central Processing Unit) (also referred to as a microprocessor or a microcomputer). The CPU 911 is connected to the ROM 913, the RAM 914, the communication board 915, the display device 901, the keyboard 902, the mouse 903, the drive device 904, and the magnetic disk device 920 via the bus 912, and controls these hardware devices. The drive device 904 is a device that reads and writes a storage medium such as an FD (Flexible Disk Drive), a CD (Compact Disc), and a DVD (Digital Versatile Disc).

  The communication board 915 is wired or wirelessly connected to a communication network such as a LAN (Local Area Network), the Internet, or a telephone line.

  The magnetic disk device 920 stores an OS 921 (operating system), a window system 922, a program group 923, and a file group 924.

  The program group 923 includes programs that execute the functions described as “units” in the embodiment. The program is read and executed by the CPU 911. That is, the program causes the computer to function as “to part”, and causes the computer to execute the procedures and methods of “to part”.

  The file group 924 includes various data (input, output, determination result, calculation result, processing result, etc.) used in “˜part” described in the embodiment.

  In the embodiment, arrows included in the configuration diagrams and flowcharts mainly indicate input and output of data and signals.

  In the embodiment, what is described as “to part” may be “to circuit”, “to apparatus”, and “to device”, and “to step”, “to procedure”, and “to processing”. May be. That is, what is described as “to part” may be implemented by any of firmware, software, hardware, or a combination thereof.

Embodiment 2. FIG.
A case will be described in which a package file is copied from a distribution destination terminal device to another terminal device, and image data is reproduced on the copy destination terminal device.

FIG. 10 is a schematic diagram of the image distribution system 100 according to the second embodiment.
The image distribution system 100 according to the second embodiment will be described below with reference to FIG.

  First, the configuration of the image distribution system 100 will be described.

The configuration of the image distribution system 100 is the same as that of the first embodiment (see FIG. 1). However, two pixel package file playback terminals 400A and 400B are connected to the network 101.
The functional configurations of the pixel packaging device 200 and the pixel package file distribution server 300 are the same as those in the first embodiment (see FIGS. 2 and 3).

The pixel package file reproduction terminals 400A and 400B include a package file destruction unit 432 in addition to the configuration described in the first embodiment (see FIG. 4).
However, the pixel package file reproduction terminal 400B that is the copy destination of the pixel package file 110 may not include the package file distribution server access unit 410, the package file distribution request unit 420, and the package file reception unit 421.
The package file destruction unit 432 will be described later.

  Next, an image distribution method of the image distribution system 100 will be described.

When the pixel package file distribution server 300 distributes the pixel package file 110, for each basic information data 112A in the pixel package file 110, the DRM information included in the basic information data 112A includes “distribution destination device ID” in addition to the distribution login ID. "Is added (FIG. 7, S240).
The distribution destination device ID is a device ID (for example, a MAC address) that identifies the distribution destination pixel package file reproduction terminal 400A. For example, the device ID of the pixel package file playback terminal 400A is notified to the pixel package file distribution server 300 together with the distribution login data when the user logs in to the image distribution service.

Here, it is assumed that the pixel package file 110 distributed to the pixel package file reproduction terminal 400A is copied to the pixel package file reproduction terminal 400B.
For example, the pixel package file 110 is copied between the pixel package file reproduction terminals 400A and 400B by communication via the network 101 or using a storage medium (for example, a CD-ROM).

  The DRM information confirmation unit 431 of the pixel package file playback terminal 400B is different from a user who plays the pixel package file 110 and a user who downloads the pixel package file 110, and when the pixel package file 110 is copy-restricted, 110 is not permitted to be played (FIG. 8, S320).

Since the package file destruction unit 432 differs between the device ID of the pixel package file playback terminal 400B and the distribution destination device ID (device ID of the pixel package file playback terminal 400A) included in the DRM information of the pixel package file 110, the pixel package file Destroy 110.
The destruction (discarding) of the pixel package file 110 means that the pixel package file 110 cannot display an image such as erasing (deleting) the pixel package file 110 or deleting or rewriting the basic information data 112A in the pixel package file 110. It is.

FIG. 11 is a table showing playback conditions for the pixel package file 110 according to the second embodiment.
The reproduction conditions of the pixel package file 110 in the second embodiment will be described below based on FIG.
When the distribution login ID of all the basic information data 112A matches the reproduction login ID, the DRM information confirmation unit 431 permits the pixel package file 110 to be reproduced (item numbers 1 to 4).
When the copy permission data of all the basic information data 112A indicates “copy permission”, the DRM information confirmation unit 431 permits the reproduction of the pixel package file 110 (item numbers 5 and 6).
If the copy permission data of at least one of the basic information data 112A does not indicate “copy permission”, the DRM information confirmation unit 431 does not allow the pixel package file 110 to be played back (item number 7).
If the copy permission data of at least one of the basic information data 112A does not indicate “copy permission” and the distribution destination device ID of at least one of the basic information data 112A does not match the terminal ID of the own playback terminal device, the package file The destruction unit 432 destroys the pixel package file 110 (item number 8).

In the reproduction conditions of No. 4 and No. 7, the DRM information confirmation unit 431 rejects reproduction of the pixel package file 110 because the duplication permission data is “no duplication”, and the package file destruction unit 432 The package file 110 may be destroyed.
In the reproduction condition of item number 7, reproduction of the pixel package file 110 may be permitted because the own reproduction terminal device and the distribution destination device match.

  Also, the DRM information confirmation unit 431 determines whether or not the DRM information matches in all the basic information data 112A, and the package file destruction unit 432 determines that the pixel package file does not match if the DRM information does not match in all the basic information data 112A. 110 may be destroyed. This is because it is considered that the pixel package file 110 has been tampered with.

According to the reproduction condition of FIG. 11, for example, the reproduction of the pixel package file 110 can be restricted as follows.
If “paid user” is set as the permission confirmation method in the DRM information of the pixel package file 110 and “copy not allowed” is set as the copy permission data, the paid pixel package file 110 is illegally copied between the terminal devices. However, the copy of the pixel package file 110 is destroyed and cannot be used.

The DRM information confirmation unit 431 may determine whether or not to permit reproduction for each basic information data 112A based on the DRM information of the basic information data 112A in the pixel package file 110 (FIG. 8, S320).
The package file playback unit 430 displays an image using the basic information data 112A that is permitted to be played out of the basic information data 112A included in the pixel package file 110 (S330 in FIG. 8). For example, the package file reproduction unit 430 displays the pixels corresponding to the basic information data 112A that is not permitted to be reproduced in a mosaic. That is, pixels that are permitted to be reproduced are displayed and pixels that are not permitted to be reproduced are mosaicked.
Thereby, for example, all the pixels in the image can be displayed for a paying user, and an image can be displayed by mosaicing some pixels for a free user.
In this case, the package file provider defines DRM information for each pixel, and the pixel packaging apparatus 200 sets the DRM information of the pixel corresponding to the basic information data 112A for each basic information data 112A in the pixel package file 110 ( FIG. 5, S114).
Further, the pixel package file distribution server 300 determines distribution permission for each basic information data 112A in the distribution request file based on the DRM information included in the basic information data 112A (FIG. 7, S230). The pixel package file distribution server 300 adds the distribution login ID to only the DRM information of the basic information data 112A that is permitted to distribute and distributes the distribution request file (S240 in FIG. 7).

  In the first and second embodiments, for example, the following package file distribution system has been described.

  The pixel package file distribution system (image distribution system 100) includes a pixel packaging device 200, a pixel package file distribution server 300, and a pixel package file reproduction terminal 400.

  The pixel packaging device 200 includes a pixel basic data creation unit 213, a basic information file creation unit 214, and a package processing unit 215.

By holding related information such as DRM information in pixel units (basic information data 112A) in the pixel package file 110, reproduction of the pixel package file 110 can be restricted.
Without the basic information file 112, the basic data (color, brightness, etc.) of each pixel cannot be acquired, so that the image cannot be reproduced. Even if the basic information file 112 exists, the reproduction of images is restricted if there is no reproduction authority based on the DRM information.

  100 image distribution system, 101 network, 110 pixel package file, 111 pixel basic data, 112 basic information file, 112A basic information data, 200 pixel packaging device, 210 package file generation unit, 211 pixel data extraction unit, 212 pixel number conversion Unit, 213 pixel basic data creation unit, 214 basic information file creation unit, 215 package processing unit, 220 package file transmission unit, 280 image file storage unit, 290 pixel package file storage unit, 300 pixel package file distribution server, 310 file reception Storage unit, 320 access processing unit, 330 package file access unit, 331 login inquiry unit, 332 package file distribution unit, 390 package file storage Unit, 391 login information storage unit, 400, 400A, 400B pixel package file playback terminal, 410 package file delivery server access unit, 420 package file delivery request unit, 421 package file reception unit, 430 package file playback unit, 431 DRM information confirmation , 432 package file destruction unit, 490 terminal storage unit, 901 display device, 902 keyboard, 903 mouse, 904 drive device, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board, 920 magnetic disk device, 921 OS , 922 window system, 923 programs, 924 files.

Claims (4)

A pixel value extraction unit that inputs target image data including pixel values of each of a plurality of pixels constituting the target image, and extracts pixel values from the input target image data;
A pixel unit data generation unit that generates pixel unit data for each pixel including pixel values extracted by the pixel value extraction unit and restriction information indicating a predetermined condition for restricting display of the target image;
A pixel packaging apparatus comprising: a pixel package file generation unit configured to generate a pixel package file including pixel unit data generated by the pixel unit data generation unit. The pixel packaging device further includes:
A pixel list data generation unit that generates pixel list data that lists pixel identification values for identifying pixels;
The pixel packaging apparatus according to claim 1, wherein the pixel package file generation unit generates a pixel package file including the pixel unit data and the pixel list data generated by the pixel list data generation unit. . A pixel packaging device according to claim 1 or 2,
A pixel package file delivery device for delivering a pixel package file generated by the pixel packaging device;
Storing the pixel package file distributed from the pixel package file distribution device, determining whether to permit display of the target image based on the restriction information included in the pixel unit data in the pixel package file; And a pixel package file reproduction device for displaying a target image on a display device based on a pixel value included in pixel unit data in the pixel package file when display of the pixel package file is permitted. Pixel value extraction processing for inputting target image data including pixel values of each of a plurality of pixels constituting the target image, and extracting pixel values from the input target image data;
Pixel unit data generation processing for generating pixel unit data for each pixel including pixel values extracted by the pixel value extraction processing and restriction information indicating a predetermined condition for restricting display of the target image;
A pixel packaging program for causing a computer to execute a pixel package file generation process for generating a pixel package file including the pixel unit data generated by the pixel unit data generation process.

Images