KR20220160577A - Imaging device, information processing method and program - Google Patents

Abstract

The present disclosure relates to an imaging device, an information processing method, and a program that enable control of imaging by another person. The captured image is associated with signature meta data including imaging device identification information and user identification information, which are identification information of the imaging device, and an electronic signature including a hash value of a captured image generated by imaging a subject. In addition, imaging is controlled based on license information, which is license-related information, including imaging device identification information, which is identification information of an imaging device, user identification information, and imaging parameters, which are parameters related to imaging. The present disclosure can be applied to, for example, an image processing device, an information processing device, an imaging device, an electronic device, an information processing method, or a program.

Description

Imaging device, information processing method and program

The present disclosure relates to an imaging device, an information processing method, and a program, and more particularly, to an imaging device, an information processing method, and a program capable of controlling image capturing by another person.

Conventionally, a method for detecting alteration has been proposed by converting a captured image or the like into a hash value in a digital camera or the like, and adding an electronic signature using the hash value to the captured image (e.g., patent see Literature 1).

Further, in recent years, a service for renting an imaging device to a user has been studied. In such a service, a user who is a stranger from the point of view of a provider providing an imaging device operates an imaging device provided by the provider, so that imaging is performed and a captured image is generated.

Patent Document 1: Japanese Unexamined Patent Publication No. 2008-22372

This disclosure makes it possible to control image capture by a user who is another person in such a service, for example.

An imaging device according to one aspect of the present technology is an imaging device including an association unit for associating a hash value of signature meta data including user identification information and imaging device identification information, which is identification information of the imaging device itself, with a captured image.

An information processing method of one aspect of the present technology is an information processing method of associating a hash value of signature metadata including imaging device identification information and user identification information, which is identification information of the imaging device, with a captured image.

An aspect program of the present technology is a program that causes a computer to function as an association unit that associates a hash value of signature meta data including user identification information and imaging device identification information, which is identification information of the imaging device, with a captured image.

An imaging device according to another aspect of the present technology captures an image based on license information, which is information related to a license, including imaging device identification information, which is identification information of the imaging device itself, user identification information, and imaging parameters, which are parameters related to imaging. An imaging device including an imaging control unit that controls the image capturing device.

An information processing method of another aspect of the present technology is based on license information, which is license-related information, including imaging device identification information, which is imaging device identification information, user identification information, and imaging parameters, which are parameters related to imaging. It is an information processing method that controls.

The program of another aspect of the present technology is based on license information, which is information about a license, including imaging device identification information, which is identification information of the imaging device itself, user identification information, and imaging parameters, which are parameters related to imaging. This is a program that functions as an imaging control unit that controls imaging by performing image capture.

In the imaging device, information processing method, and program of one aspect of the present technology, a hash value of signature meta data including imaging device identification information and user identification information, which is identification information of the imaging device, is associated with a captured image.

In the imaging device, information processing method, and program of another aspect of the present technology, license-related information including imaging device identification information that is identification information of the imaging device, user identification information, and imaging parameters that are parameters related to imaging Imaging is controlled based on the license information.

1 is a diagram explaining an outline of imaging control.
Fig. 2 is a diagram showing an example of a main configuration of a rental system.
3 is a block diagram showing an example of a main configuration of an enterprise terminal device or the like.
4 is a functional block diagram showing functions realized in enterprise terminal devices and the like.
5 is a diagram showing an example of a license key.
Fig. 6 is a block diagram showing an example of a main configuration of a camera.
Fig. 7 is a functional block diagram showing functions realized in the camera.
8 is a flowchart for explaining an example of the flow of processing related to activation.
Fig. 9 is a flowchart continuing from Fig. 8 explaining an example of a flow of processing related to activation.
10 is a flowchart for explaining an example of the flow of processing related to activation.
Fig. 11 is a flowchart continuing from Fig. 10 explaining an example of the flow of processing related to activation.
12 is a flowchart for explaining an example of the flow of processing related to activation.
Fig. 13 is a flowchart continuing from Fig. 12 explaining an example of the flow of processing related to activation.
14 is a flowchart for explaining an example of the flow of processing related to activation.
Fig. 15 is a flowchart continuing from Fig. 10 explaining an example of the flow of processing related to activation.
16 is a flowchart for explaining an example of the flow of processing related to activation.
Fig. 17 is a flowchart continuing from Fig. 10 explaining an example of the flow of processing related to activation.
18 is a flowchart for explaining an example of the flow of imaging control processing.
Fig. 19 is a diagram for explaining an example of a flow of processing related to generation of an electronic signature.
Fig. 20 is a diagram for explaining an example of the flow of processing related to electronic signature verification.

Hereinafter, a mode for implementing the present disclosure (hereinafter referred to as an embodiment) will be described. On the other hand, explanation is performed in the following order.

1. Imaging control

2. First embodiment (rental system)

3. Bookkeeping

<1. Imaging Control>

<Imaging Device Rental Service>

For example, Patent Literature 1 describes a method used for detecting tampering by converting a captured image or the like into a hash value in a digital camera or the like and adding an electronic signature using the hash value to the captured image. For example, information on an imaging device can also be included in this electronic signature.

By the way, in recent years, a service for renting an imaging device to a user has been studied. For example, a case where a business owner rents a camera under his management to an employee or an outsourced person (a cameraman outside the company or a service user) can be considered.

In such a service, from the point of view of the business owner (company), which is the provider of the imaging device, the business owner (company) can control the information of the electronic signature given to the captured image generated by the imaging performed by a user who is another person operating the imaging device. it is desirable

In addition, the business owner (company) can control the usage conditions of the imaging device, for example, allowing only authorized users to use the imaging device or allowing the imaging device to be used only at permitted locations, dates, and the like. It is desirable to have Furthermore, it is desirable that the business owner (company) can control the imaging settings.

<Control of photographing by another person>

Accordingly, it is possible to control image capture by another person. For example, imaging is controlled based on license information, which is information related to a license, including imaging device identification information, which is identification information of an imaging device, user identification information, and imaging parameters, which are parameters related to imaging. By doing in this way, it is possible to control imaging by license information. The license information is given to the imaging device under the approval of the provider of the imaging device. That is, control of imaging by the provider of the imaging device becomes possible.

For example, as shown in FIG. 1 , the company 10 rents the camera 21 to the user 31, rents the camera 22 to the user 32, and rents the camera 23 to the user 33. ) to be rented. It is assumed that license information approved by the camera 21 provider is set in the camera 21 . This license information includes at least the identification information (ID) of the camera 21 itself and the identification information (ID) of the user 31 as the rental destination (legitimate user). By controlling imaging based on these information, it is possible to prevent use of the camera 21 other than legitimate users 31 indicated in the license information. For example, use of the camera 21 by the unauthorized user 34 can be prohibited (the user 34 cannot use the camera 21). That is, the user of the camera can be controlled by the provider of the camera.

The imaging parameters included in the license information may include, for example, information regarding usage conditions of the imaging device. By doing in this way, it is possible to permit use of the imaging device by legitimate users (that is, permit imaging) only when the usage conditions are satisfied.

These conditions of use are arbitrary and may be any, and may be, for example, based on location or time of day or both. For example, use may be permitted only at a predetermined place, use may be permitted only at a predetermined date and time, or use may be permitted only at a predetermined time and place. By doing so, the camera provider can restrict the date and time and location where use of the camera is permitted.

On the other hand, here, the date and time is used as an example of the condition for allowing use, but any time information is used (that is, as long as the time range (period) for allowing use can be indicated). For example, the time zone in which use is allowed may be restricted (ie, start time and end time may be indicated). Of course, only the start time may be indicated, or only the end time may be indicated. In addition, year, half year, quarter, month, week, day, odd month, even month, beginning of month, end of month, day of the week, weekend, weekday, national holiday, morning, afternoon, morning, day, night, hour, minute, second, etc. A time range in which use is allowed may be indicated by an arbitrary unit. For example, use may be allowed only in a specified month, use may be allowed only on a specified day of the week, or use may be allowed only on a specified day of each month (for example, the day ending in 2).

The same applies to the location (place), and any information may be used as long as it is related to location information (ie, as long as the range of the area permitted to be used can be indicated). For example, the range may be indicated by GPS coordinates, etc., may be indicated by administrative districts such as country, prefecture, city, town, or village, address, etc., or may be indicated by postal code or landline phone number, etc. In addition, you may make it show by the name of facilities, venues, etc., such as the name of a park or an amusement facility, for example. Furthermore, for example, a floor (basement floor, ground floor, N floor, etc.) may be designated.

In addition, this use condition may be based on a subject. For example, use may be permitted only when imaging a predetermined subject. By doing this, it is possible to limit the subject, for example. That is, the purpose of imaging can be limited. In addition, for example, a sponsor's product or the like can always be placed within the angle of view. In this way, it is possible to add value to the captured image as an advertisement. Also, for example, a predetermined building or a predetermined landscape may be included in the background. This makes it possible to limit the location and time of imaging.

Incidentally, the imaging parameters included in the license information may also include, for example, imaging setting information that is information related to imaging settings. By doing so, the provider of the camera can control the settings of the camera, for example.

For example, the information related to the setting of the captured image may include information related to the resolution of the captured image. That is, the resolution allowed for the license may be limited. In this case, the camera generates a captured image with a resolution (or lower) specified in the license information. In this way, the camera provider can control the resolution of the captured image generated by the camera according to, for example, a license fee, user authority, purpose of use, and the like.

Further, for example, the information related to the setting of the captured image may include information related to the credit notation of the captured image. For example, information specifying whether or not credits are indicated on a captured image generated by the camera and information specifying the contents of the credits to be indicated may be included as information related to credit notation. In this way, the provider of the camera can control credit notation of captured images generated by the camera.

Also, arbitrary information may be included in this license information. For example, identification information (for example, company name, etc.) of the camera provider (company) may be included. Of course, information other than this may be included.

For example, the license information may further include information indicating the expiration date of the license. That is, imaging may be controlled by license information having an expiration date. By doing in this way, for example, it is possible to limit the period during which activation is possible or to change the usable imaging settings within and outside the period.

Further, for example, a hash value of signature metadata including imaging device identification information and user identification information, which is identification information of the imaging device, is associated with the captured image. In this way, the provider of the imaging device can control signature meta data that is added to a captured image created by a user who is another person using the imaging device. That is, the provider of the imaging device can ensure the authenticity of the imaging device that generated the captured image and its user.

For example, in the case of FIG. 1 , the ID (Cam ID) of the camera 21 is added to the meta data 42 attached to the captured image 41 generated by the user 31 taking an image using the camera 21. Signature meta data such as ID (Mr. A) of the user 31 may be included.

Further, for example, this signature meta data may further include a company name of a company that provides the imaging device to the user. By doing so, authenticity of the provider of the imaging device (eg, the owner of the captured image) can be ensured.

Further, a hash value derived from signature meta data included in license information, which is information related to a license, may be associated with a captured image. That is, the signature meta data included in the license information may be associated with the captured image. By doing this, the provider of the imaging device can ensure the authenticity of the imaging device that generated the captured image and its user.

For example, the hash value of the signature meta data may be associated with the captured image according to the content of the license. For example, this association may be performed only in the case of a license for protecting a captured image. In addition, this association may be performed only for captured images captured under predetermined conditions specified in the license. Furthermore, this association may be performed only for captured images obtained by capturing a predetermined subject specified in the license. In this way, various control becomes possible.

Further, for example, the hash value of the signature meta data may be associated with the captured image according to the expiration date included in the license information. For example, signature metadata (hash value of) may be associated with captured images generated within the expiration date, or signature metadata (hash value of) may be associated with captured images generated outside the expiration date. do. In this way, various controls according to the expiration date are possible.

For example, an electronic signature including a hash value of signature meta data may be generated, and the generated electronic signature may be associated with a captured image. That is, the signature meta data may be included in the electronic signature of the captured image. By doing in this way, the authenticity of the imaging device that generated the captured image and its user can be ensured by using the specifications of the electronic signature. For example, an electronic signature may be generated by converting a captured image into a hash value, converting the hash value of the captured image and signature meta data into a hash value, and encrypting the digital signature. Then, signature meta data may be further associated with the captured image to which the electronic signature is associated.

<2. First Embodiment>

<Rental System>

Fig. 2 is a diagram showing an example of a main configuration of a rental system as an embodiment of an information processing system to which the present technology is applied. The rental system 100 shown in FIG. 2 is a system that manages rental of a camera 140 from a company 10 to a user 30 .

The company 10 is a provider of the camera 140 in this rental system 100. The company 10 may or may not be the owner of the camera 140 . For example, the company 10 may provide the camera 140 owned by another company.

The user 30 is a user who uses the camera 140 rented from the company 10 . That is, the user 30 captures an image of the subject using the camera 140 and generates a captured image.

For example, the user 30 may be an employee of the company 10 . In this case, the user 30 who is an employee captures an image using the shared camera 140 owned by the company 10 and generates a captured image. For example, it is conceivable that a reporter working for a newspaper company conducts interviews (photographing) using a camera owned by the newspaper company. The rental system 100 may manage which camera 140 is to be lent to which employee in such a company. In this case, it is conceivable that the rights of the captured image generated by the camera 140 belong to the company 10. The rental system 100 can also manage such captured images.

Further, for example, the user 30 may be a business consignment destination of the company 10 . For example, a case where the user 30 is a freelance photographer who has been requested to take an image by a newspaper company can be considered. The rental system 100 may manage such a rental outside the company 10 . In this case, it is conceivable that the captured image generated by the camera 140 is delivered to the company 10 . The rental system 100 can also manage such captured images.

Further, for example, the user 30 may be a user of a camera 140 rental service provided by the company 10 . For example, a company 10 provides a camera 140 rental service, a user 30 rents a camera 140 using the service, and uses the rented camera 140 to take an image. If you do, etc., you can think of it. This rental service may be paid or free of charge. For example, the camera 140 may be rented free of charge, and a captured image generated using the camera 140 may be provided for a fee. The rental system 100 may manage which camera 140 is lent to which user in such a service. In this case, it is conceivable that the captured image generated by the camera 140 is provided to the user 30 by printing or transmission. In such a case, it is preferable that the right of the captured image belongs to the company 10. The rental system 100 can also manage such captured images.

As shown in FIG. 2 , the rental system 100 includes a server 110 , an enterprise terminal device 120 , a user terminal device 130 , and a camera 140 . Each device is communicatively connected to each other via the network 150 . However, the camera 140 need not be connected to the network 150 (it may be offline). In addition, the camera 140 may be communicatively connected to the network 150 via another device such as the enterprise terminal device 120 or the user terminal device 130 .

Server 110 performs processing related to management of licenses related to rental of camera 140 contracted between company 10 and user 30 . For example, the server 110 performs processing related to generation of license information and activation of the user 30, and the like.

The company terminal device 120 is a terminal device owned by the company 10, and performs processing related to setting a license for the camera 140 to be rented. The user terminal device 130 is a terminal device owned by the user 30 and performs processing related to registration of user 30 information.

The camera 140 is a rental imaging device, and performs processes such as activating the user 30, controlling imaging, and generating captured images.

On the other hand, in FIG. 2, the server 110, company 10 (corporate terminal device 120), user 30 (user terminal device 130), and camera 140 are shown one by one. In the system 100, the number of each component is arbitrary, and each may be singular or plural. In addition, the network 150 may be constituted by a plurality of networks.

<server>

Fig. 3 is a diagram showing an example of a main configuration of a server 110, which is an embodiment of an information processing device to which the present technology is applied. The server 110 shown in FIG. 3 is a computer that installs and executes an application program (software) that performs processing related to rental management of the camera 140 . Here, the computer includes a computer equipped with dedicated hardware and a general-purpose computer capable of executing various functions by installing various programs. The server 110 executes an application program to perform processing related to camera 140 rental.

In the server 110 shown in FIG. 3 , a central processing unit (CPU) 201, a read only memory (ROM) 202, and a random access memory (RAM) 203 are connected to each other via a bus 204. has been

An input/output interface 210 is also connected to the bus 204 . An input unit 211, an output unit 212, a storage unit 213, a communication unit 214, and a drive 215 are connected to the input/output interface 210.

The input unit 211 includes, for example, a keyboard, a mouse, a microphone, a touch panel, an input terminal, and the like. The output unit 212 includes, for example, a display, a speaker, and an output terminal. The storage unit 213 is made of, for example, a hard disk, RAM disk, non-volatile memory, or the like. The communication unit 214 is composed of, for example, a network interface. The drive 215 drives a removable recording medium 221 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

In the server 110 structured as described above, the CPU 201 transfers, for example, application programs stored in the storage unit 213 to the RAM 203 via the input/output interface 210 and the bus 204. ), the above-described series of processing is performed. The RAM 203 also appropriately stores data necessary for the CPU 201 to execute various processes.

Application programs executed by the server 110 can be applied by being recorded on the removable recording medium 221 as a package medium. In that case, the application program can be installed in the storage unit 213 via the input/output interface 210 by loading the removable recording medium 221 into the drive 215 .

In addition, this application program may be provided through a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting. In that case, this application program can be received by the communication unit 214 and installed in the storage unit 213 .

In addition, this application program may be installed in advance in the ROM 202 or the storage unit 213 .

Meanwhile, the configuration of the server 110 is arbitrary and is not limited to the example of FIG. 3 . For example, the server 110 may be implemented as cloud computing that distributes and jointly processes in a plurality of devices via a network. That is, the server 110 (cloud server) may perform processing related to rental management of the camera 140 or provide a service as a cloud service.

In addition, the enterprise terminal device 120 and the user terminal device 130 also have the same configuration as the server 110 shown in FIG. 3 . That is, the block diagram shown in FIG. 3 can also be used for description of the enterprise terminal device 120 or the user terminal device 130 .

A function realized by executing an application program on the enterprise terminal device 120 is shown in FIG. 4A as a function block. As shown in A of FIG. 4 , the enterprise terminal device 120 executes an application program, so that a device-specific information registration request unit 301, a linking request processing unit 302, an expiration date setting request unit ( 303), an imaging parameter request unit 304, and a license key recording unit 305.

The device-specific information registration request unit 301 performs processing related to a registration request of device-specific information, which is information unique to the camera 140 . For example, the device-specific information registration request unit 301 performs processing related to a registration request of a device-specific ID that is identification information unique to the camera 140 . That is, the device-specific ID is imaging device identification information that is identification information of the imaging device.

The linkage request processing unit 302 processes a linkage request between a device-specific ID of the camera 140 to be rented and a user ID that is identification information of the user 30 to whom the camera 140 is rented. That is, the linkage request processing unit 302 performs processing related to license construction.

The expiration date setting request unit 303 performs processing related to a request for setting an expiration date. The imaging parameter request unit 304 performs processing related to a request for imaging parameters. The license key recording unit 305 performs processing related to license key recording.

Functions realized by executing an application program on the user terminal device 130 are shown in FIG. 4B as functional blocks. As shown in B of FIG. 4 , the user terminal device 130 may have functional blocks such as a user registration request unit 311 by executing an application program. The user registration request unit 311 performs processing related to user registration requests.

Functions realized by executing application programs in the server 110 are shown in FIG. 4C as function blocks. As shown in C of FIG. 4 , the server 110 executes an application program, so that the user registration unit 321, device-specific information registration unit 322, signature meta information generation unit 323, login processing unit 324, It may have functional blocks such as an expiration date setting unit 325, an imaging parameter generation unit 326, a user confirmation unit 327, and a license key issuing unit 328.

The user registration unit 321 performs processing related to user information registration of the user 30 as the rental destination. The device-specific information registration unit 322 performs processing related to registration of device-specific information of the camera 140 to be rented. The signature meta-information generation unit 323 performs processing related to creation of signature meta-information used for generation of an electronic signature. The login processing unit 324 performs processing related to login of the user 30 as the lending destination. The expiration date setting unit 325 performs processing related to setting the expiration date of the license. The imaging parameter generator 326 performs processing related to generation of imaging parameters. The user confirmation unit 327 performs processing related to user confirmation in login processing and the like. The license key issuing unit 328 performs processing related to issuance of a license key, which is an example of license information.

<License Key>

An example of this license key is shown in FIG. 5 . As shown in FIG. 5, the license key 350 issued by the server 110 includes, for example, system-unique information that is unique identification information (ID) for the key in the system. include

In addition, the license key 350 may include information regarding an expiration date used for control of imaging. For example, within the expiration date shown here, activation of the user 30 in the camera 140 may be permitted. Alternatively, an electronic signature may be added to the captured image. Conversely, an electronic signature may not be attached to a captured image. Note that, for example, outside the expiration date indicated here, activation of the user 30 in the camera 140 may be rejected (deactivation). Alternatively, an electronic signature may be added to the captured image. Conversely, an electronic signature may not be attached to a captured image.

Furthermore, the license key 350 may include a device-specific ID. Further, the license key 350 may include a user FIDO (Fast IDentity Online) public key.

In addition, the license key 350 includes signature meta information including a device-specific ID of the camera 140 and a user ID of the user 30 . Further, this signature meta-information may include information (for example, company name) related to the company 10 that is the provider of the camera 140.

Furthermore, the license key 350 may include imaging parameters that are parameters related to imaging. This imaging parameter may be any information as long as it relates to imaging. For example, the imaging parameters may include information related to imaging settings. For example, the imaging parameter may include information related to the resolution of the captured image as information related to the setting of the imaging. For example, control information such as permitting generation of a captured image of HD quality and prohibiting generation of a captured image of 4K quality may be included in the imaging parameter. Also, control information such as permitting generation of captured images of 4K quality only during the license period may be included in the imaging parameters.

Further, for example, the imaging parameters may include information related to context control at the time of imaging (information related to usage conditions). For example, the imaging parameter may include control information for limiting the time and place (position and time) at which imaging is permitted as information related to context control at the time of imaging. Further, for example, the imaging parameter may include control information for permitting imaging (permitting activation) only when a predetermined subject exists as information related to context control at the time of imaging.

Furthermore, for example, the imaging parameters may include control information related to generation of the captured image. For example, the imaging parameter may include control information related to credit notation of the captured image as control information related to generation of the captured image.

<Camera>

6 is a diagram showing an example of a main configuration of a camera 140 as an embodiment of an imaging device to which the present technology is applied. The camera 140 shown in FIG. 6 is a computer that installs and executes an application program (software) that performs processing related to rental of the camera 140 and processing related to imaging. Here, the computer includes a computer equipped with dedicated hardware and a general-purpose computer capable of executing various functions by installing various programs. The camera 140 executes an application program to perform a process related to rental of the camera 140 and a process related to image pickup.

In the camera 140 shown in FIG. 6 , a CPU 401 , a ROM 402 , and a RAM 403 are connected to each other via a bus 404 .

An input/output interface 410 is also connected to the bus 404 . An input unit 411, an output unit 412, a storage unit 413, a communication unit 414, and a drive 415 are connected to the input/output interface 410.

The input unit 411 includes, for example, a keyboard, a mouse, a microphone, a touch panel, and an input terminal. The output unit 412 includes, for example, a display, a speaker, and an output terminal. The storage unit 413 is made of, for example, a hard disk, RAM disk, non-volatile memory, or the like. The communication unit 414 is composed of, for example, a network interface. The drive 415 drives a removable recording medium 421 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

Furthermore, an imaging unit 431 is connected to the input/output interface 410 . The imaging unit 431 has, for example, an optical system such as a lens or a diaphragm and an image sensor, captures an image of a subject, and generates a captured image. On the other hand, the imaging unit 431 may further have configurations other than those described above, such as an image processing unit that performs image processing on the generated captured image and a memory that stores data of the captured image.

In the camera 140 structured as described above, the CPU 401 transfers, for example, an application program stored in the storage unit 413 to the RAM 403 via the input/output interface 410 and the bus 404. ), the above-described series of processing is performed. The RAM 403 also appropriately stores data necessary for the CPU 401 to perform various processes.

An application program executed by the camera 140 can be applied by being recorded on a removable recording medium 421 as a package medium, for example. In that case, the application program can be installed into the storage unit 413 via the input/output interface 410 by loading the removable recording medium 421 into the drive 415 .

In addition, this application program may be provided through a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting. In that case, this application program can be received by the communication unit 414 and installed in the storage unit 413 .

In addition, this application program may be installed in advance in the ROM 402 or the storage unit 413 .

Functions realized by executing an application program in the camera 140 are shown in FIG. 7 as functional blocks. As shown in Fig. 7, the camera 140 executes an application program, so that a login processing unit 441, a device-specific common key generation unit 442, a license key verification unit 443, an activation processing unit 444, a user It may have functional blocks such as an authentication unit 445, a use condition determination unit 446, an imaging setting unit 447, an imaging control unit 448, and an electronic signature processing unit 449.

The login processing unit 441 performs processing related to login. The device-specific common key generation unit 442 performs processing related to generation of a device-specific common key. The license key verification unit 443 performs processing related to verification of the license key supplied from the server 110 . The activation processing unit 444 performs processing related to off-line activation. The user authentication unit 445 performs processing related to user authentication. The usage condition determining unit 446 performs processing related to determining usage conditions based on the license information. The imaging setting unit 447 performs processing related to setting imaging based on the license information. The imaging control unit 448 performs processing related to control of imaging. The electronic signature processing unit 449 performs processing related to the electronic signature associated with the captured image.

<Online processing flow 1>

Next, an example of the flow of activation-related processing executed by the above rental system 100 will be described with reference to flowcharts in FIGS. 8 and 9 . Activation processing in this case is performed in a state in which the camera 140 is online (a state in which communication with the server 110 is possible).

First, a process for registering a user ID or device-specific ID in the server 110 is performed. The user registration request unit 311 of the user terminal device 130 requests the server 110 to register the user in step S111 of FIG. 8 . For example, the user registration request unit 311 supplies user information, which is information about the user, to the server 110 via the communication unit 214 of the user terminal device 130 . When the user registration unit 321 of the server 110 acquires this user information via the communication unit 214 of the server 110 in step S121, in step S122 the user ID corresponding to this user information is created and registered in the database. The user registration unit 321 of the server 110 supplies the registered user ID to the user terminal device 130 via the communication unit 214 of the server 110 in step S123. The user registration request unit 311 of the user terminal device 130 acquires the user ID via the communication unit 214 of the user terminal device 130 in step S112, for example, the user terminal device 130 ) is stored in the storage unit 213.

Further, the device-specific information registration request unit 301 of the enterprise terminal device 120 requests the server 110 to register the device-specific ID in step S101. For example, the device-specific information registration request unit 301 supplies the device-specific ID of the camera 140 to be rented to the server 110 via the communication unit 214 of the enterprise terminal device 120 . When the device-specific information registration unit 322 of the server 110 acquires this device-specific ID via the communication unit 214 of the server 110 in step S124, in step S125, this device-specific ID register in the database.

On the other hand, the processing related to this user registration and the processing related to device-specific ID registration can be performed independently of each other, and either one may be performed first. Also, both processes may be performed in parallel.

When (the user ID) of the user 30 and the device unique ID of the camera 140 are registered in the server 110, processing related to generation of signature meta information corresponding to the license is performed. On the other hand, this processing can be performed at any timing, as long as the user (user ID) and device unique ID are registered. In other words, association between the user ID already registered in the server 110 and the device-specific ID can be performed at any timing.

On the other hand, in this specification, "association" of data means "association" of data. Here, the term "association" means that, for example, when one data is processed, the other data can be used (linked). That is, data associated with each other may be collected as one piece of data, or may be made into separate data. For example, a plurality of pieces of information associated with each other may be transmitted on different transmission paths. Further, for example, a plurality of pieces of information associated with each other may be recorded on different recording media (or different recording areas of the same recording medium). On the other hand, this &quot;association&quot; may be part of the data instead of the entire data. For example, an image and information corresponding to the image may be associated with each other in an arbitrary unit such as a plurality of frames, one frame, or a part within a frame.

On the other hand, in this specification, in addition to the above-mentioned "link", for example, "combine", "multiplex", "add", "integrate", "include", "store", "incorporate" Terms such as ”, “insert”, and “insert” mean grouping a plurality of objects into one, and refer to one method of “associating” described above.

In step S102 of FIG. 8 , the connection request processing unit 302 of the company terminal device 120 transmits, through the communication unit 214 of the company terminal device 120, the device-specific ID of the camera 140 to be rented, Linkage of the user ID of the user 30 to whom the camera 140 is rented is requested.

Based on the request, the signature meta information generation unit 323 of the server 110 generates signature meta information including the designated user ID and device unique ID in step S126, and registers it in the database. This signature meta information is information that can be included in an electronic signature, and includes a device-specific ID indicating a device that generated a captured image to which the electronic signature is added, and a user ID indicating a user who operated the device. That is, the user ID and the device-specific ID are linked by this signature meta information.

Further, this signature meta information may further include a company name (which may be identification information) indicating a company that is a provider that provided the device to the user. That is, the company name may be further linked to the user ID and device unique ID by signature meta information. Incidentally, this company name may indicate the right holder of the captured image. Furthermore, other information may be included in the signature meta information. In the following, it is assumed that the device-specific ID, user ID, and company name are included in the signature meta information. That is, the signature meta information generating unit 323 generates signature meta information including the designated user ID and device unique ID, and the company name of the company 10, and registers it in the database.

After these information are registered, the camera 140 is lent to the user 30 so as to correspond to this license (i.e., the signature meta information generated in step S126). That is, the camera 140 of the device unique ID included in the signature meta information is lent from the company 10 to the user 30 corresponding to the user ID included in the same signature meta information.

After the camera 140 is rented, processing related to activation in FIG. 9 is performed. That is, a procedure for activating himself is performed so that the user 30 to whom the camera 140 is rented can use the camera 140 . In this case, as described above, processing related to activation is performed online. That is, the user 30 operates the rented camera 140 and makes it communicate with the server 110 to perform this activation.

The login processing unit 441 of the camera 140 operated by the user 30 transmits login information, device-specific ID, etc. to the server 110 via the communication unit 414 in step S131 of FIG. 9 . and ask for login. This login information includes information related to login, such as a user ID and password, for example.

The login processing unit 324 of the server 110 acquires this request via the communication unit 214 in step S141, and accepts the login if it is a legitimate user (if the user ID or password matches). In step S142, the login processing unit 324 confirms the association between the logged-in user and the device. That is, the login processing unit 324 checks the registered signature meta information, and confirms whether there is signature meta information linking the user ID supplied from the camera 140 with the device unique ID. That is, the login processing unit 324 checks the association between the login user and the device-specific ID.

When such signature information exists, that is, when association between the logged-in user and the camera 140 is confirmed, the login processing unit 324 transmits the license information of the license corresponding to the user ID and device-specific ID to the communication unit 214 ) is supplied to the camera 140. That is, the login processing unit 324 transmits to the camera 140 license information including signature meta information linking the user ID supplied from the camera 140 with the device-specific ID and the user ID. On the other hand, other information may be included in this license information.

The login processing unit 441 of the camera 140 acquires the license information via the communication unit 414 in step S132, and activates it in step S133.

By executing each process as described above, online activation can be performed.

<Online processing flow 2>

As described above, the license information may include information other than signature meta information and user ID. For example, information regarding the expiration date of the license may be included. An example of the flow of processing related to activation in that case will be described with reference to flowcharts in FIGS. 10 and 11 . Activation processing in this case is performed in the same way as in the case of Figs.

Processing until signature meta information is generated is executed similarly to the case of FIG. 8 . That is, each process of step S151 and step S152 (Fig. 10) executed by the enterprise terminal device 120 is similar to each process of step S101 and step S102 (Fig. 8) described above. It runs. Further, each process of step S161 and step S162 (Fig. 10) executed by the user terminal device 130 is similar to each process of step S111 and step S112 (Fig. 8) described above. It runs. Furthermore, each process of steps S171 to S176 (Fig. 10) executed by the server 110 is executed similarly to each process of steps S121 to S126 (Fig. 8) described above. .

After the signature meta information is generated, the expiration date setting request unit 303 of the company terminal device 120, in step S153, via the communication unit 214 of the company terminal device 120, information about the expiration date is supplied to the server 110, and the setting of the expiration date is requested. The expiration date setting unit 325 of the server 110 acquires the request (information on the expiration date) via the communication unit 214 of the server 110 in step S177, and obtains the request (expiration date). The license expiration date is set based on the information). That is, the expiration date setting unit 325 sets the expiration date of the license to the expiration date specified by information on the expiration date supplied from the enterprise terminal device 120 and registers it in the database.

Processing related to activation executed after the camera 140 is rented is basically performed in the same flow as in the case of FIG. 9 . That is, each process of step S181 to step S183 (Fig. 11) executed by the camera 140 is executed similarly to each process of step S131 to step S133 (Fig. 9) described above. . In addition, each process of steps S191, step S192, and step S194 executed by the server 110 is similar to each process of steps S141 to step S143 described above (FIG. 9). It runs.

However, if the association between the login user and the camera 140 is confirmed in step S192, that is, if the association between the user ID of the login user and the device-specific ID (signature meta information) is confirmed, the login processing unit of the server 110 ( 324) checks the expiration date of the license in step S193. Then, if it is within the expiration date, the login processing unit 441 generates license information and transmits it to the camera 140 in step S194. This license information includes a user ID, signature meta information, expiration date, and the like. The login processing unit 441 of the camera 140 acquires the license information in step S182. Then, the login processing unit 441 activates based on the license information in step S183.

By executing each process as described above, it is also possible to set an expiration date.

<Online processing flow 3>

As described above, the license information may include information other than signature meta information and user ID. For example, information regarding imaging parameters may be included. An example of the flow of processing related to activation in that case will be described with reference to flowcharts in FIGS. 12 and 13 . Activation processing in this case is performed in a state in which the camera 140 is online (in a state in which communication with the server 110 is possible), as in the case of FIGS. 8 and 9 .

Processing until signature meta information is generated is executed similarly to the case of FIG. 8 . That is, each process of step S201 and step S202 (Fig. 12) executed by the enterprise terminal device 120 is similar to each process of step S101 and step S102 (Fig. 8) described above. It runs. Further, each process of step S211 and step S212 (Fig. 12) executed by the user terminal device 130 is similar to each process of step S111 and step S112 (Fig. 8) described above. It runs. Furthermore, each process of steps S221 to S226 (Fig. 12) executed by the server 110 is executed similarly to each process of steps S121 to S126 (Fig. 8) described above. .

After the signature meta information is generated, the imaging parameter request unit 304 of the enterprise terminal device 120 accesses the server 110 via the communication unit 214 of the enterprise terminal device 120 in step S203, , request setting of imaging parameters. The imaging parameter generation unit 326 of the server 110 generates imaging parameters based on the request in step S227 and registers them in the database.

Processing related to activation executed after the camera 140 is rented is basically performed in the same flow as in the case of FIG. 9 . That is, each process of steps S231 to S233 (Fig. 13) executed by the camera 140 is executed similarly to each process of steps S131 to S133 (Fig. 9) described above. . In addition, each process of step S241 to step S243 executed by the server 110 is executed similarly to each process of step S141 to step S143 (Fig. 9) described above.

On the other hand, the license information (steps S243 and S232) supplied from the server 110 to the camera 140 includes the imaging parameters generated as described above in addition to the user ID and signature meta information.

By executing each process as described above, imaging parameters can also be generated.

<Offline processing flow 1>

Next, an example of the flow of processing related to activation, which is performed in a state in which the camera 140 is off-line (a state in which communication with the server 110 is impossible), will be described with reference to flowcharts in FIGS. 14 and 15 . On the other hand, here, an example in which license information does not include information about the expiration date or imaging parameters will be described. That is, the examples in FIGS. 14 and 15 correspond to the examples in FIGS. 8 and 9 .

First, a process for registering a user ID or device-specific ID in the server 110 is performed. The user registration request unit 311 of the user terminal device 130 requests the server 110 to register the user in step S271 of FIG. 14 . For example, the user registration request unit 311 supplies user information, which is information about the user, to the server 110 via the communication unit 214 of the user terminal device 130, and requests registration of the user information. do. When the user registration unit 321 of the server 110 acquires the user information via the communication unit 214 of the server 110 in step S281, in step S282 the user ID corresponding to the user information. is created and registered in the database.

Further, the device-specific common key generation unit 442 of the camera 140 generates a device-specific common key in step S251. In step S252, the device-specific common key generation unit 442 supplies device-specific information, which is device-specific information, including the generated device-specific common key, to the enterprise terminal device 120. For example, the device-specific common key generation unit 442 generates the device-specific ID, the device-specific common key encrypted with the public key of the server 110, and the device-specific ID and device derived using the device-specific common key. The hash value of the unique common key is supplied to the enterprise terminal device 120 as device-specific information.

The device-specific information registration request unit 301 of the company terminal device 120 acquires the device-specific information through the communication unit 214 of the company terminal device 120 in step S261. Further, in step S262, the device-specific information registration request unit 301 supplies the device-specific information to the server 110 via the communication unit 214 of the enterprise terminal device 120. For example, the device-specific information registration request unit 301 supplies the above-described device-specific information and a user ID associated with the device-specific ID to the server 110 . At that time, signature meta information and imaging parameters may also be supplied to the server 110 from the enterprise terminal device 120 .

The device-specific information registration unit 322 of the server 110 acquires the device-specific information, user ID, and the like via the communication unit 214 of the server 110 in step S283. In step S284, the signature meta information generation unit 323 generates signature meta information including device unique ID, user ID, company name and the like based on these information. On the other hand, this signature meta information may be generated in the enterprise terminal device 120 and supplied to the server 110.

The license key issuing unit 328 of the server 110 verifies the hash value in step S285. That is, the license key issuing unit 328 uses the private key of the server 110 to decrypt the device-specific common key encrypted with the public key of the server 110 included in the supplied device-specific information. Then, the license key issuing unit 328 uses the decrypted device-specific common key to derive hash values of the device-specific ID and the device-specific common key. Further, the license key issuing unit 328 compares the derived hash value with the hash value included in the supplied device-specific information (device-specific ID and device-specific common key hash value).

When both hash values match each other and it is confirmed that no alteration has been made, the license key issuing unit 328 issues the license key as license information to the enterprise terminal device 120 . Information included in the license key is as described with reference to FIG. 5 . On the other hand, here, it is assumed that system specific information and signature meta information are included in the license key. The license key issuing unit 328 derives a hash value of the license key using the device-specific common key. Then, the license key issuing unit 328 supplies the license key and its hash value to the enterprise terminal device 120 .

In step S263, the license key recording unit 305 of the enterprise terminal device 120 acquires the issued license key (and its hash value). When the license key recording unit 305 confirms the hash value, it records the license key in a recording medium in step S264.

When the camera 140 is rented to the user 30, the recording medium on which the license key described above is recorded is also rented. The user 30 uses the camera 140 by attaching the recording medium to a predetermined position of the camera 140 . Subsequent processing by the camera 140 is performed in the same flow as that shown in FIG. 15 , for example.

The license key verification unit 443 of the camera 140 checks the mounting of the recording medium on which the license key is recorded, in step S291 of FIG. 15 . When the recording medium is loaded in a predetermined position, the license key verification unit 443 verifies the license key recorded on the recording medium in step S292. That is, the license key verification unit 443 verifies the hash value of the license key, thereby verifying whether or not the license key has been altered. For example, the license key verification unit 443 derives the hash value of the license key recorded on the recording medium using the device-specific common key of the camera 140 . Then, the license key verification unit 443 compares the derived hash value with the hash value of the license key recorded on the recording medium.

If both hash values match and it is proved that no alteration has been made to the license key, the license key verification unit 443 verifies the device unique ID included in the license key in step S293.

If the device-specific ID is correct, the license key verification unit 443 determines, in step S294, whether the license key is an unused key. License keys used in the past cannot be used. The license key verification unit 443 determines whether the license key is an unused key based on system specific information, for example.

If it is determined that the key is unused, the activation processing unit 444 activates it in step S295. In this way, the user 30 can use the camera 140 .

By executing each process as described above, offline activation can be performed using the recording medium.

Meanwhile, in this case, as in the case of online, an expiration date can be set for the license. That is, information indicating the expiration date may be included in the license key issued by the license key issuing unit 328. In that case, as in the online case (Fig. 10), after generating the signature meta information (after the process in step S284 in Fig. 14), the same processing as in steps S153 and S177 (Fig. 10) is performed. Do this and set the expiration date. Then, when the license key verification unit 443 verifies the license key (during the processing of steps S291 to S294 in Fig. 15), it is only necessary to confirm whether or not the license key is within the expiration date included in the license key.

Also in this case, as in the case of online, the imaging parameters may be set, and the imaging parameters may be included in the license key issued by the license key issuing unit 328. In that case, as in the online case (Fig. 12), after generating the signature meta information (after the process in step S284 in Fig. 14), the same processing as steps S203 and S227 (Fig. 12) is performed. By doing so, imaging parameters may be generated.

<Flow of offline processing 2>

On the other hand, FIDO (Fast IDentity Online) may be applied to user authentication. In FIDO, instead of authentication using an ID and password, authentication using, for example, a USB (Universal Serial Bus) key (security token) embedding an encryption key, or biometric information such as a fingerprint or an iris is performed.

An example of the flow of processing related to activation in that case will be described with reference to flowcharts in FIGS. 16 and 17 . On the other hand, it is assumed that processing related to activation is performed offline. It is also assumed that the license information does not include information about the expiration date or imaging parameters. That is, the examples in FIGS. 16 and 17 correspond to the examples in FIGS. 14 and 15 .

Registration and linkage of user IDs and device-specific IDs and issuance of license keys are performed in the same manner as in the case described with reference to the flowcharts in FIGS. 14 and 15 . That is, each process of step S301 and step S302 (Fig. 16) executed by the camera 140 is executed similarly to each process of step S251 and step S252 (Fig. 14) described above. . Further, each process of steps S311 to S313 (Fig. 16) executed by the enterprise terminal device 120 is similar to each process of steps S252 to S263 (Fig. 14) described above. It runs. Furthermore, the processing of step S321 (FIG. 16) executed by the user terminal device 130 is executed similarly to the processing of step S271 (FIG. 14) described above. In addition, each process of steps S331 to S336 (Fig. 16) executed by the server 110 is executed similarly to each process of steps S281 to S286 (Fig. 14) described above. .

However, in this case, the processing unit 332 of the user terminal device 130 registers the user's FIDO public key in addition to user registration. On the other hand, user registration and registration of the user's FIDO public key may be executed simultaneously or independently. The FIDO public key is included in the license key and supplied to the camera 140, and is used for user authentication by FIDO in the user authentication unit 445. That is, the license key issued by the license key issuing unit 328 includes the FIDO public key.

In this case, the license key recording unit 305 of the enterprise terminal device 120 supplies the license key acquired in step S313 to the camera 140 in step S314 and causes it to be recorded. The camera 140 acquires the license key and records it on a recording medium or the like in step S303. The supply of the license key from the enterprise terminal device 120 to the camera 140 can be performed by any method. For example, it may be performed using a removable recording medium or may be performed by communication.

When the camera 140 is rented to the user 30, the license key described above is rented in a state of being recorded in, for example, a removable recording medium mounted in the camera 140 or a built-in memory. The user 30 who has borrowed the camera 140 performs activation using the camera 140 . This process is performed in the flow shown in FIG. 17, for example.

The user authentication unit 445 of the camera 140 detects that a user identity module (UIM) card is mounted in a predetermined position of the camera 140 in step S341 of FIG. 17 .

When the UIM card is mounted, the user authentication unit 445 performs user authentication by FIDO using the FIDO public key included in the license key in step S342.

In step S343, the license key verification unit 443 verifies the device unique ID included in the license key.

If it is determined that the device-specific ID is a legitimate ID, the activation processing unit 444 activates it in step S344. In this way, the user 30 can use the camera 140 .

By executing each process as described above, offline activation can be performed using FIDO.

Meanwhile, in this case, as in the case of online, an expiration date may be set for the license. That is, information indicating the expiration date may be included in the license key issued by the license key issuing unit 328. In that case, as in the case of online (FIG. 10), after generating the signature meta information (after the processing in step S334 in FIG. 16), the same processing as steps S153 and S177 (FIG. 10) is performed. Do this and set the expiration date. Then, when the license key verification unit 443 verifies the license key (before or after the processing in step S343 in Fig. 17), it is sufficient to confirm whether the license key is within the expiration date included in the license key.

Also in this case, as in the case of online, the imaging parameters may be set, and the imaging parameters may be included in the license key issued by the license key issuing unit 328. In that case, as in the online case (Fig. 12), after generating the signature meta information (after the process in step S334 in Fig. 16), the same processing as in steps S203 and S227 (Fig. 12) is performed. By doing so, imaging parameters may be generated.

<Flow of imaging control processing>

As described above, when activation is performed by various methods, the user 30 captures a subject using the camera 140 and generates a captured image. At that time, imaging control, imaging setting, generation of an electronic signature, and the like are performed based on the information included in the license information. An example of the flow of imaging control processing performed by such a camera 140 will be described with reference to a flowchart in FIG. 18 .

When the imaging control process is started, the usage condition determining unit 446 determines, in step S401, whether conditions for usage restriction based on imaging parameters included in the license information (including the license key) are satisfied (usage conditions) do. That is, the usage condition determination unit 446 checks the imaging parameters included in the license information, and determines whether the usage conditions set by the imaging parameters are satisfied.

For example, as described with reference to FIG. 5 , the location and date and time at which use (imaging) is permitted can be set by imaging parameters. For example, if it is determined that these conditions of use are satisfied, that is, if imaging is permitted, the process proceeds to step S402.

In step S402, the imaging setting unit 447 sets the imaging function (specification) based on the imaging parameters included in the license information. For example, the imaging setting unit 447 sets the resolution and the like of the captured image based on the imaging parameters. Thereby, a captured image can be generated with the function (specification) specified by the imaging parameter included in the license information.

In step S403, the imaging control unit 448 controls the imaging unit 431 to image the subject to generate a captured image.

The electronic signature processing unit 449 generates an electronic signature using the license information in step S404, and associates the generated electronic signature with the captured image in step S405. When the process of step S405 ends, the imaging control process ends. In addition, if it is determined in step S401 that the use condition is not satisfied, since imaging is not performed, the imaging control process ends.

By executing the imaging control process as described above, imaging control based on license information can be performed. On the other hand, in the case of imaging of a moving picture, such an imaging control process may be performed for each frame.

<Generation of electronic signature>

An example of a method for generating an electronic signature in step S404 of FIG. 18 will be described with reference to FIG. 19 . When a captured image 501 is generated by capturing a subject (S501), a hash value 502 of the captured image 501 is derived using a device-specific common key (S502).

Then, an electronic signature 504 is generated using the hash value 502 and the signature meta information 503 included in the license information (S503). As described above, the signature meta information 503 includes information such as device-specific ID, user ID, and company name. In addition, the method of generating the electronic signature 504 is arbitrary. For example, the signature meta information 503 is added to the hash value 502 of the image, the device-specific common key of the camera 140 is used to derive these hash values, and the hash value is used as the public key of the server. By encrypting, the electronic signature 504 may be generated. Alternatively, the electronic signature 504 may be generated by encrypting the hash value using a private key. Alternatively, the electronic signature 504 may be generated by encrypting the hash value using a common key.

Then, the signature meta information 503 and the electronic signature 504 are associated with the captured image 501 (S504). On the other hand, whether to associate this electronic signature or signature meta information with the captured image may be controlled according to the content of the license. Further, depending on the expiration date of the license, whether or not to associate this electronic signature or signature meta information with the captured image may be controlled.

<Verification of electronic signature>

An example of a method for verifying an electronic signature associated with a captured image as described above will be described with reference to FIG. 20 . When the captured image 501 as the content, the signature meta information 503 associated with the captured image 501, and the electronic signature 504 are obtained (S551), the captured image is captured using the device-specific common key of the camera 140 The hash value 511 of the image 501 is derived (S552).

Then, the electronic signature 512 is generated using the hash value 511 and the obtained signature meta information 503 (signature meta information 503 associated with the captured image 501) (S553). As described above, the signature meta information 503 includes information such as device-specific ID, user ID, and company name. In addition, the generation method of the electronic signature 504 is arbitrary as long as it is the method similar to the case of FIG.

Then, the electronic signature is verified by comparing the derived electronic signature 512 with the obtained electronic signature 504 (the electronic signature 504 associated with the captured image 501) (S554).

On the other hand, by decrypting the obtained electronic signature 504 using a secret key of the server or the like, the hash value 502 of the image and the hash value of the signature meta information 503 are derived, and the hash value is used as the hash value of the image. The digital signature may be verified by comparing the value 511 with the hash value of the signature meta information 503.

In this way, falsification of the captured image and signature meta-information (device-specific ID, user ID, company name) can be detected (the authenticity of the captured image and signature meta-information (device-specific ID, user ID, company name) can be guaranteed have).

Here, the device-specific ID indicates a device used for generating (imaging) a captured image. Also, the user ID indicates a photographer (a person who created a captured image). Further, the company name indicates the owner of the right to the captured image (the owner of the captured image). That is, by including the signature meta information in the electronic signature, authenticity of the device used for capturing, the photographer, the owner (right holder) of the captured image, etc. can be guaranteed.

<Application example>

On the other hand, in the rental system 100, the description has been made using the company 10 as the provider of the camera 140 (owner of the captured image), but the provider of the camera 140 (owner of the captured image) is the company. It is not limited to, and may be an individual or a group. In addition, the user 30 of the camera 140 has been described as an individual, but is not limited thereto, and may be, for example, a company or an organization.

In addition, the provision method of the camera 140 is arbitrary, and may be other than rental. For example, the camera 140 may be transferred to the user 30 . In addition, it may be a contract in which the camera 140 is lent to the user 30 for a certain period of time and then returned to the company 10, or after the camera 140 is lent to the user 30 for a certain period of time, the user 30 It may be a transferable contract.

In the above, the camera 140 (ie, imaging device) has been described as an example of the provided object, but the provided object is arbitrary and may be other than the imaging device. For example, it may be a recording device or any electronic device.

<3. Bookkeeping>

<hardware>

The series of processing described above can be executed by software (application program) or by hardware.

<Applicability of this technology>

This technique can be applied to any structure. For example, the present technology includes a processor as a system LSI (Large Scale Integration), a module using a plurality of processors, etc., a unit using a plurality of modules, etc., or a set in which other functions are added to a unit, etc. It can also be implemented as part of the configuration of the device.

Further, for example, the present technology can also be applied to a network system composed of a plurality of devices. For example, the present technology may be implemented as cloud computing in which processing is shared and shared by a plurality of devices via a network. For example, the present technology may be implemented in a cloud service in which a computer, a mobile phone-type information processing terminal, an Internet of Things (IoT) device, or the like provides services to arbitrary terminals.

On the other hand, in this specification, a system means a set of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all components are in the same case. Therefore, a plurality of devices housed in a separate case and connected via a network, and a single device in which a plurality of modules are housed in a case are both systems.

<Fields and applications where this technology can be applied>

Systems, devices, processing units, etc. to which the present technology is applied can be used in any field, such as transportation, medical care, crime prevention, agriculture, livestock farming, mining, beauty, factories, home appliances, meteorology, nature monitoring, and the like. Moreover, its use is also arbitrary.

<Others>

The embodiment of the present technology is not limited to the above-described embodiment, and various changes are possible within a range not departing from the gist of the present technology.

For example, the configuration described as one device (or processing unit) may be divided and configured as a plurality of devices (or processing units). Conversely, configurations described above as a plurality of devices (or processing units) may be combined to be configured as one device (or processing unit). In addition, it is of course possible to add configurations other than those described above to the configuration of each device (or each processing unit). Furthermore, as long as the configuration and operation of the system as a whole are substantially the same, a part of the configuration of a certain device (or processing unit) may be included in the configuration of another device (or other processing unit).

Further, for example, the above-described program may be executed in an arbitrary device. In that case, it is only necessary to ensure that the device has necessary functions (function blocks, etc.) and obtains necessary information.

Further, for example, one device may execute each step of one flowchart, or a plurality of devices may divide and execute each step. Furthermore, when a plurality of processes are included in one step, one device may execute the plurality of processes, or a plurality of devices may divide and execute the plurality of processes. In other words, a plurality of processes included in one step may be executed as a plurality of step processes. Conversely, the processing described as a plurality of steps may be integrated and executed as one step.

Further, for example, in a program executed by a computer, the processing of steps describing the program may be executed time-sequentially according to the procedure described in this specification, in parallel, or when a call is made, etc. as necessary. It may be executed individually at the timing. That is, as long as no contradiction occurs, the processing of each step may be executed in an order different from the order described above. Furthermore, the processing of the step describing this program may be executed in parallel with the processing of another program, or may be executed in combination with the processing of another program.

Further, for example, a plurality of techniques related to the present technique can be independently implemented as a single unit as long as no contradiction occurs. Of course, it is also possible to implement by using any plurality of present techniques together. For example, a part or all of the present technology described in one embodiment may be implemented in combination with a part or all of the present technology described in another embodiment. In addition, a part or all of any of the present techniques described above may be implemented in combination with other techniques not described above.

On the other hand, the present technology can also take the following configurations.

(1) As an imaging device,

An imaging device comprising: an associating unit for associating a hash value of signature meta data including user identification information and imaging device identification information, which is identification information of the imaging device itself, with a captured image.

(2) The imaging device according to (1), wherein the signature meta data further includes a company name of a company that provides the imaging device to the user.

(3) The imaging device according to (1) or (2), wherein the associating unit associates the hash value derived from the signature meta data included in license information, which is license-related information, with the captured image.

(4) The imaging device according to (3), wherein the association unit associates the hash value of the signature meta data with the captured image in accordance with the content of the license.

(5) The imaging device according to (3) or (4), wherein the association unit associates the hash value of the signature meta data with the captured image according to the expiration date included in the license information.

(6) The image capture described in any one of (1) to (5), wherein the association unit generates an electronic signature including the hash value of the signature meta data, and associates the generated electronic signature with the captured image. Device.

(7) In (6), the associating unit generates the electronic signature by converting the captured image into a hash value, converting the hash value of the captured image and the signature meta data into a hash value, and encrypting the digital signature. The described imaging device.

(8) The imaging device according to (6) or (7), wherein the association unit further associates the signature meta data with the captured image to which the electronic signature is associated.

(9) As an information processing method,

An information processing method that associates a hash value of signature meta data including imaging device identification information that is identification information of an imaging device and user identification information with a captured image.

(10) a computer;

A program that causes a hash value of signature metadata including imaging device identification information and user identification information, which are identification information of an imaging device, to function as an association unit for associating a captured image with a captured image.

(11) As an imaging device,

An imaging control unit comprising an imaging control unit that controls imaging based on license information, which is information related to a license, including imaging device identification information, which is identification information of the imaging device itself, user identification information, and imaging parameters, which are parameters related to imaging. Device.

(12) The imaging device according to (11), wherein the imaging parameters include information regarding usage conditions of the imaging device.

(13) The imaging device according to (12), wherein the conditions for use are based on position or time of day or both.

(14) The imaging device according to (12) or (13), wherein the usage condition is based on the subject.

(15) The imaging device according to any one of (11) to (14), wherein the imaging parameter includes information related to imaging settings.

(16) The imaging device according to (15), wherein the information related to the imaging setting includes information related to the resolution of the captured image.

(17) The imaging device according to (15) or (16), wherein the information related to setting of the captured image includes information related to credit notation of the captured image.

(18) The imaging device according to any one of (11) to (17), wherein the license information further includes information indicating an expiration date of the license.

(19) As an information processing method,

An information processing method that controls imaging based on license information, which is information related to a license, including imaging device identification information that is identification information of an imaging device, user identification information, and imaging parameters that are parameters related to imaging.

(20) a computer;

A program for functioning as an imaging control unit that controls imaging based on license information, which is information related to a license, including imaging device identification information, which is identification information of the imaging device itself, user identification information, and imaging parameters, which are parameters related to imaging .

10: Enterprise
30~34: User
100: rental system
110: server
120: enterprise terminal device
130: user terminal device
140: camera
301: device unique ID register
302: connection processing unit
311: user ID registration unit
321: user ID generation unit
322 Device unique ID register
323: signature meta information generation unit
324: expiration date setting unit
325: imaging parameter generating unit
326: user confirmation unit
327: license key issuance unit
431: imaging unit
441: login processing unit
442: license key verification unit
443: expiration date confirmation unit
444: use condition determination unit
445: imaging setting unit
446: imaging control unit
447: electronic signature processing unit

Claims (20)

As an imaging device,
An imaging device comprising: an associating unit for associating a hash value of signature meta data including user identification information and imaging device identification information, which is identification information of the imaging device itself, with a captured image. According to claim 1,
The signature metadata further includes a company name of a company that provides the image capture device to a user. According to claim 1,
wherein the associating unit associates the hash value derived from the signature meta data included in license information, which is license information, with a captured image. According to claim 3,
wherein the association unit associates the hash value of the signature meta data with the captured image according to the content of the license. According to claim 3,
and the association unit associates the hash value of the signature meta data with the captured image according to an expiration date included in the license information. According to claim 1,
wherein the associating unit generates an electronic signature including a hash value of the signature meta data, and associates the generated electronic signature with the captured image. According to claim 6,
wherein the association unit generates the electronic signature by converting the captured image into a hash value, converting the hash value of the captured image and the signature meta data into hash values, and encrypting the digital signature. According to claim 6,
wherein the association unit further associates the signature meta data with the captured image to which the electronic signature is associated. As an information processing method,
An information processing method that associates a hash value of signature meta data including imaging device identification information that is identification information of an imaging device and user identification information with a captured image. computer,
A program that causes a hash value of signature metadata including imaging device identification information and user identification information, which are identification information of an imaging device, to function as an association unit for associating a captured image with a captured image. As an imaging device,
An imaging control unit comprising an imaging control unit that controls imaging based on license information, which is information related to a license, including imaging device identification information, which is identification information of the imaging device itself, user identification information, and imaging parameters, which are parameters related to imaging. Device. According to claim 11,
wherein the imaging parameter includes information about conditions of use of the imaging device. According to claim 12,
The imaging device according to the condition of use is based on position or time, or both. According to claim 12,
The image pickup device according to the use condition is based on the subject. According to claim 11,
The imaging device includes information related to setting of imaging. According to claim 15,
The imaging device according to claim 1 , wherein the information on settings for imaging includes information on resolution of a captured image. According to claim 15,
The imaging device, wherein the information related to setting of the captured image includes information related to credit notation of the captured image. According to claim 11,
The license information further includes information indicating an expiration date of the license. As an information processing method,
An information processing method for controlling imaging based on license information, which is information related to a license, including imaging device identification information that is identification information of an imaging device, user identification information, and imaging parameters that are parameters related to imaging. computer,
A program for functioning as an imaging control unit that controls imaging based on license information, which is information related to a license, including imaging device identification information, which is identification information of the imaging device itself, user identification information, and imaging parameters, which are parameters related to imaging .

Images