Patent Description:
Conventionally, it has been proposed to manage an expiration time of encapsulated software (hereinafter, referred to as a capsule) provided from a server, using an integrated chip (IC) card (see, for example, Patent Document <NUM>).

Specifically, a personal computer (PC) transmits expiration time authentication data including an expiration time start time and an expiration time end time to the IC card at the time of start-up of the capsule. In a case where an IC card time is before the expiration time start time, the IC card rewrites the IC card time to the expiration time start time. Furthermore, the IC card permits the use of the capsule in a case where the IC card time is before the expiration time end time, and does not permit the use of the capsule in a case where the IC card time is after the expiration time end time. Therefore, period management of the capsule can be performed offline without connecting the PC to the server.

However, in the invention described in Patent Document <NUM>, for example, in a case where the IC card time before being rewritten is not accurate, period management of a license cannot be appropriately performed. For example, when the IC card time proceeds, the capsule may be unusable even though an actual time is before the expiration time end time. Furthermore, when the IC card time is delayed, the capsule may be usable even though the actual time has passed the expiration time end time.

The present technology has been made in view of such a situation, and is to appropriately perform period management of a license provided by an information processing apparatus such as a server or the like in a case where the license is used in an electronic device that does not directly communicate with the information processing apparatus.

<CIT> relates to a digital copyright management apparatus and program.

The invention is set out in the attached claims.

The license communication information is generated using the device information, the device information being the information including the reference date and time and the device unique key, the reference date and time being the date and time set using the hardware clock of the electronic device and being the date and time used for the period management of the license, the device unique key being the key unique to the electronic device, and the license communication information being the information including at least one of the effective term or the expiration time of the license and the reference date and time and used for installing the license in the electronic device.

The device information that is the information including the reference date and time and the device unique key and used for issuing the license in the information processing apparatus is generated, the reference date and time being the date and time set using the hardware clock and being the date and time used for the period management of the license provided by the information processing apparatus, and the device unique key being the key unique to the electronic device.

The device information that is the information including the reference date and time and the device unique key is generated by the electronic device, the reference date and time being the date and time set using the hardware clock and the date and time used for the period management of the license, and the device unique key being the key unique to the electronic device; the device information is transmitted to the second information processing apparatus by the first information processing apparatus; the device information is received from the first information processing apparatus by the second information processing apparatus, the license communication information that is the information including at least one of the effective term or the expiration time of the license and the reference date and time is generated using the device information, and the license communication information is transmitted to the first information processing apparatus by the second information processing apparatus; the license communication information is received from the second information processing apparatus by the first information processing apparatus; and the license is installed using the license communication information by the electronic device.

The license provided by the information processing apparatus can be used in the electronic device. It is possible to appropriately perform period management of a license provided by an information processing apparatus in a case where the license is used in an electronic device that does not directly communicate with the information processing apparatus.

Note that an effect described here is not necessarily limited, and may be any effect described in the present disclosure.

Hereinafter, an embodiment for carrying out the present technology will be described. A description will be given in the following order.

First, an embodiment of the present technology will be described with reference to <FIG>.

<FIG> illustrates a configuration example of an information processing system <NUM> to which the present technology is applied.

The information processing system <NUM> includes a server <NUM>, a client <NUM>, and a network <NUM>. The client <NUM> includes a personal computer (PC) <NUM>, a removable medium <NUM>, and an electronic device <NUM>.

The server <NUM> and the PC <NUM> are connected to each other and communicate with each other, via the network <NUM>.

The server <NUM> performs provision and management of a license of a function used in the electronic device <NUM>, provision of software for realizing the function of the electronic device <NUM>, and the like.

The PC <NUM> exchanges various data with the server <NUM> by communicating with the server <NUM> via the network <NUM>. For example, the PC <NUM> receives data regarding the license of the function used in the electronic device <NUM> and various data such as software and the like used in the electronic device <NUM>, from the server <NUM>. Furthermore, the PC <NUM> transmits various data such as data and the like regarding the electronic device <NUM> to the server <NUM>.

The removable medium <NUM> includes a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, and is used to exchange various data between the PC <NUM> and the electronic device <NUM>.

Note that the removable medium <NUM> will hereinafter be simply referred to as a medium <NUM>.

The electronic device <NUM> is difficult to connect to the network <NUM>, basically does not directly communicate with the server <NUM>, and is used offline. Furthermore, the electronic device <NUM> can use a function corresponding to the installed license by installing the license provided from the server <NUM> via the medium <NUM>.

Note that a type of the electronic device <NUM> is not particularly limited. Hereinafter, a case where the electronic device <NUM> is a camera will be mainly described by way of example.

Furthermore, a type of a function that becomes a target of the license provided by the server <NUM> is not particularly limited. For example, the function may not be necessarily a function using software, and may be a function realized only by hardware.

Moreover, the server <NUM> may also provide software for realizing the function that becomes the target of the license. In this case, the license of the function is also a license of the software for realizing the function.

Furthermore, only one client <NUM> has been illustrated in <FIG> for making it easy to understand the drawing and the description, but a plurality of clients <NUM> is actually provided. Moreover, only one server <NUM> has also been illustrated, but a plurality of servers <NUM> may be provided. Furthermore, the number of at least one of the PC <NUM>, the medium <NUM>, or the electronic device <NUM> included in one client <NUM> may be plural.

<FIG> illustrates a configuration example of the server <NUM>.

The server <NUM> includes an input unit <NUM>, a control unit <NUM>, a communication unit <NUM>, an output unit <NUM>, a real time clock (RTC) <NUM>, and a storage unit <NUM>. The input unit <NUM>, the control unit <NUM>, the communication unit <NUM>, the output unit <NUM>, the RTC <NUM>, and the storage unit <NUM> are connected to each other via a bus <NUM>.

The input unit <NUM> includes, for example, input devices such as a switch, a button, a key, a microphone, an imaging element, and the like, and is used to input various data. The input unit <NUM> supplies the input data to each unit of the server <NUM> via the bus <NUM>.

The control unit <NUM> includes, for example, a processor such as a central processing unit (CPU) and the like, and controls processing of each unit of the server <NUM>.

The communication unit <NUM> includes, for example, a communication device and the like, and communicates with the PC <NUM> via the network <NUM>. Note that a communication manner of the communication unit <NUM> is not particularly limited, and may be any one of a wired communication manner or a wireless communication manner. Furthermore, for example, the communication unit <NUM> may correspond to a plurality of communication manners.

The output unit <NUM> includes, for example, output devices such as a display, a speaker, a lighting device, a vibrator, and the like, and outputs various data by an image, a sound, light, vibrations, and the like.

The RTC <NUM> is a hardware clock that continues to operate by a backup battery (not illustrated) and the like even though a power supply of the server <NUM> is turned off. The RTC <NUM> is managed so that a user cannot change the date and time (a date and a time).

The storage unit <NUM> includes at least a nonvolatile storage medium, and stores various data or software necessary for processing of the server <NUM>.

Note that, hereinafter, in a case where the respective units of the server <NUM> exchange data and the like with each other via the bus <NUM>, a description of the bus <NUM> will be appropriately omitted. For example, in a case where the control unit <NUM> and the communication unit <NUM> exchange data with each other via the bus <NUM>, it is simply said that the control unit <NUM> and the communication unit <NUM> exchange data with each other.

<FIG> illustrates a configuration example of a function of the control unit <NUM> of the server <NUM>. The control unit <NUM> realizes a function including a license management unit <NUM>, a data generation unit <NUM>, a user interface (UI) control unit <NUM>, a communication control unit <NUM>, and a storage control unit <NUM> by executing, for example, a control program.

The license management unit <NUM> manages a license of a function used in the electronic device <NUM>.

The data generation unit <NUM> generates various data to be transmitted to the PC <NUM>.

The UI control unit <NUM> controls user interfaces in the PC <NUM> and the electronic device <NUM>. For example, the UI control unit <NUM> controls a user interface in the PC <NUM> by generating a display control file for displaying various information on a screen of the PC <NUM> and transmitting the display control file to the PC <NUM>.

The communication control unit <NUM> controls communication processing by the communication unit <NUM>. Furthermore, the communication control unit <NUM> also acquires data to be transmitted to the PC <NUM> from each unit of the server <NUM> or supplies data received from the PC <NUM> to each unit of the server <NUM>.

The storage control unit <NUM> controls the storage unit <NUM> to store data and the like regarding the license of the function used in the electronic device <NUM>.

<FIG> illustrates a configuration example of the electronic device <NUM>.

The electronic device <NUM> includes an input unit <NUM>, a function execution unit <NUM>, a control unit <NUM>, a communication unit <NUM>, an output unit <NUM>, a real time clock (RTC) <NUM>, a storage unit <NUM>, and a drive <NUM>. The input unit <NUM>, the function execution unit <NUM>, the control unit <NUM>, the communication unit <NUM>, the output unit <NUM>, the RTC <NUM>, the storage unit <NUM>, and the drive <NUM> are connected to each other via a bus <NUM>.

The input unit <NUM> includes, for example, input devices such as a switch, a button, a key, a microphone, an imaging element, and the like, and is used to input various data. The input unit <NUM> supplies the input data to each unit of the electronic device <NUM> via the bus <NUM>.

The function execution unit <NUM> includes various hardware and software for executing the function of the electronic device <NUM>. For example, in a case where the electronic device <NUM> is a camera, the function execution unit <NUM> includes a lens, an imaging element, and the like.

The control unit <NUM> includes, for example, a processor such as a central processing unit (CPU) and the like, and controls processing of each unit of the electronic device <NUM>.

The communication unit <NUM> includes, for example, a communication device and the like, and communicates with another electronic device (not illustrated) (for example, a smartphone or the like). Note that a communication manner of the communication unit <NUM> is not particularly limited, and may be any one of a wired communication manner or a wireless communication manner. Furthermore, for example, the communication unit <NUM> may correspond to a plurality of communication manners.

The RTC <NUM> is a hardware clock that continues to operate by a backup battery and the like even though a power supply of the electronic device <NUM> is turned off. The RTC <NUM> is managed so that the user cannot change the date and time (a date and a time).

The storage unit <NUM> includes at least a nonvolatile storage medium, and stores various data or software necessary for processing of the electronic device <NUM>.

The drive <NUM> can attach and detach the medium <NUM>, and drives the connected medium <NUM>.

Note that, hereinafter, in a case where the respective units of the electronic device <NUM> exchange data and the like with each other via the bus <NUM>, a description of the bus <NUM> will be appropriately omitted. For example, in a case where the control unit <NUM> and the communication unit <NUM> exchange data with each other via the bus <NUM>, it is simply said that the control unit <NUM> and the communication unit <NUM> exchange data with each other.

<FIG> illustrates a configuration example of a function of the control unit <NUM> of the electronic device <NUM>. The control unit <NUM> realizes a function including a license management unit <NUM>, a key generation unit <NUM>, a data generation unit <NUM>, a UI control unit <NUM>, a communication control unit <NUM>, and a storage control unit <NUM> by executing, for example, a control program.

The license management unit <NUM> manages the license of the function used in the electronic device <NUM>.

The key generation unit <NUM> generates a device unique key, which is a unique secret key different for every electronic device <NUM>.

The data generation unit <NUM> generates various data to be transmitted to the server <NUM> via the medium <NUM> and the PC <NUM>.

The UI control unit <NUM> controls the output unit <NUM> to control a user interface in the electronic device <NUM>.

The communication control unit <NUM> controls communication processing by the communication unit <NUM>. Furthermore, the communication control unit <NUM> acquires data to be transmitted to the outside via the communication unit <NUM> from each unit of the electronic device <NUM> or supplies data received from the outside via the communication unit <NUM> to each unit of the electronic device <NUM>.

Next, processing of the information processing system <NUM> will be described with reference to <FIG>.

First, license acquisition processing executed by the client <NUM> will be described with reference to a flowchart of <FIG>.

In step S1, the PC <NUM> requests a device information acquisition file.

For example, the PC <NUM> accesses the server <NUM> via the network <NUM> according to an operation of the user to display a screen for acquiring the license of the function used in the electronic device <NUM>. For example, a window <NUM> of <FIG> is displayed on the screen of the PC <NUM>.

The window <NUM> is divided into a device information field 301A and a license information field 301B.

At a left end of the device information field 301A, an image and a type name of the electronic device <NUM> are displayed laterally side by side.

At a left end of the license information field 301B, a function that becomes a target acquiring a license and a type of the license are shown. In this example, it is shown that a license of an imaging function of a <NUM> image during an effective term of one week is an acquisition target.

Note that the user sets at least one of an effective term or an expiration time of the license at the time of acquiring the license.

In a case where only one of the effective term or the expiration time is set, the start date and time of the license is not particularly set, and the license can be used from a point in time when the license is acquired. On the other hand, in a case where both of the effective term and the expiration time are set, the date and time obtained by subtracting the effective term from the expiration time is the start date and time of the license. Note that, for example, the setting of the expiration time and the effective term is limited so that the start date and time is after the current date and time.

Furthermore, the expiration time is set based on the RTC <NUM> of the server <NUM>. However, as described later, the expiration time is converted into the date and time based on the RTC <NUM> of the electronic device <NUM> in the server <NUM>, and is given in notification to the electronic device <NUM>.

Note that, hereinafter, in a case of distinguishing between the expiration time based on the RTC <NUM> of the server <NUM> and the expiration time based on the RTC <NUM> of the electronic device <NUM>, the former is referred to as a server expiration time and the latter is referred to as a client expiration time.

At a right end of the license information field 301B, an installation button <NUM> is displayed. When the installation button <NUM> is pressed, for example, a window <NUM> of <FIG> is displayed on the screen of the PC <NUM>.

In the window <NUM>, a message for prompting the user to download the device information acquisition file, store the device information acquisition file in the medium <NUM>, and insert the medium <NUM> into the camera (electronic device <NUM>) and a download button <NUM> are displayed. When the download button <NUM> is pressed, the PC <NUM> requests the server <NUM> to transmit the device information acquisition file, via the network <NUM>.

In response to this request, the server <NUM> transmits the device information acquisition file to the PC <NUM> via the network <NUM> in step S31 of <FIG> as described later.

In step S2, the PC <NUM> receives the device information acquisition file transmitted from the server <NUM>. Furthermore, the PC <NUM> stores the received device information acquisition file in the medium <NUM> according to, for example, an operation of the user.

In step S3, the electronic device <NUM> executes a command in the device information acquisition file.

Specifically, the user detaches the medium <NUM> in which the device information acquisition file is stored from the PC <NUM>, and connects the medium <NUM> to the drive <NUM> of the electronic device <NUM>.

The drive <NUM> reads the device information acquisition file stored in the medium <NUM> and supplies the read device information acquisition file to the control unit <NUM>. The control unit <NUM> executes a device information acquisition command included in the device information acquisition file. Therefore, acquisition processing of device information is started.

Note that, for example, the processing of steps S1 to S3 may be omitted, and the acquisition processing of the device information may be started by operating the electronic device <NUM> by the user without using the device information acquisition command.

In step S4, the key generation unit <NUM> determines whether or not the device unique key has been generated. The key generation unit <NUM> determines that the device unique key has not been generated in a case where the device unique key is not stored in the storage unit <NUM>, and the processing proceeds to step S5.

In step S5, the key generation unit <NUM> generates the device unique key. A generation method of the device unique key is not particularly limited. The storage control unit <NUM> causes the storage unit <NUM> to store the device unique key.

That is, the electronic device <NUM> generates the device unique key, which is a secret key unique to the electronic device <NUM>, before generating a device information file for the first time after factory shipment. Therefore, it is not necessary to generate the device unique key at the time of the factory shipment and store the device unique key in the electronic device <NUM>, such that a risk of leakage or the like of the device unique key is reduced. Furthermore, for example, by changing firmware of the electronic device <NUM>, it is possible to change a generation method, a generation timing, or the like, of the device unique key, such that flexibility is improved.

Thereafter, the processing proceeds to step S6.

On the other hand, in step S4, the key generation unit <NUM> determines that the device unique key has been generated in a case where the device unique key is stored in the storage unit <NUM>, the processing of step S5 is skipped, and the processing proceeds to step S6.

In step S6, the data generation unit <NUM> sets the current date and time of the RTC <NUM> as a device RTC. The device RTC is the date and time of the RTC <NUM> at the time of generating the device information file, and indicates the date and time of the RTC <NUM> of the electronic device <NUM> at the time of requesting the license. Furthermore, the device RTC is the reference date and time used for period management of a license to be acquired.

In step S7, the data generation unit <NUM> encrypts the device unique key with a server public key. Specifically, the data generation unit <NUM> reads the device unique key and the server public key from the storage unit <NUM>. Note that the server public key is a public key corresponding to a server secret key possessed by the server <NUM>, and is distributed to the electronic device <NUM> in advance. The data generation unit <NUM> encrypts the device unique key using the server public key. Therefore, security of the device unique key is ensured, such that tampering, eavesdropping, and the like, of the device unique key are prevented.

In step S8, the data generation unit <NUM> generates storage data including a device unique identification (ID), the device RTC, and the device unique key. Specifically, the data generation unit <NUM> reads the device unique ID from the storage unit <NUM>. The device unique ID is an ID uniquely allocated to each electronic device <NUM>, and includes, for example, a type name and a serial number of the electronic device <NUM>. The data generation unit <NUM> generates storage data including the device unique ID, the device RTC, and the encrypted device unique key.

In step S9, the data generation unit <NUM> calculates a hash value of the storage data using the device unique key. Note that a hash function used to calculate the hash value is not particularly limited.

In step S10, the data generation unit <NUM> generates a device information file including the storage data and the hash value. Therefore, security of the storage data is ensured using the device unique key.

This device information file is used by the server <NUM> to issue a license as a license request file for requesting issuance of the license.

In step S11, the data generation unit <NUM> stores the device information file in the medium <NUM> via the drive <NUM>.

At this time, for example, the output unit <NUM> displays a window <NUM> of <FIG> under the control of the UI control unit <NUM>. In the window <NUM>, a message for notifying the user that the device information file has been written out and an OK button <NUM> are displayed. When the OK button <NUM> is pressed, the window <NUM> is closed.

In step S12, the PC <NUM> transmits the device information file to the server <NUM>.

For example, the user detaches the medium <NUM> from the electronic device <NUM>, and connects the medium <NUM> to the PC <NUM>. The PC <NUM> displays, for example, a window <NUM> of <FIG> on the screen.

In the window <NUM>, a message for prompting the user to upload the device information file acquired from the camera (electronic device <NUM>) and an upload button <NUM> are displayed. When the upload button <NUM> is pressed, the PC <NUM> reads the device information file from the medium <NUM> and transmits the read device information file to the server <NUM> via the network <NUM>.

In response to this transmission, the server <NUM> receives the device information file in step S32 of <FIG> as described later.

In step S13, the PC <NUM> determines whether or not to acquire a license communication file.

The server <NUM> transmits a display control file for finally confirming execution of installation of the license via the network <NUM> in step S34 of <FIG> as described later, in a case where it is determined that the device information file received from the PC <NUM> is valid.

The PC <NUM> displays a window <NUM> of <FIG> on the screen on the basis of the display control file.

In the window <NUM>, a device unique ID of the camera (electronic device <NUM>), a message for confirming the execution of the installation of the license in the camera, and an installation button <NUM> are displayed. When the installation button <NUM> is pressed, for example, a window <NUM> of <FIG> is displayed on the screen of the PC <NUM>.

In the window <NUM>, a message for prompting the user to download the license communication file, store the license communication file in the medium <NUM>, and insert the medium <NUM> into the camera (electronic device <NUM>) and a download button <NUM> are displayed. Then, when the download button <NUM> is pressed, the PC <NUM> determines to acquire the license communication file and requests the server <NUM> to transmit the license communication file via the network <NUM>. Thereafter, the processing proceeds to step S14.

In response to this request, the server <NUM> transmits the license communication file including an installation key and the like in step S40 of <FIG> as described later.

In step S14, the PC <NUM> receives the license communication file from the server <NUM> via the network <NUM>.

In step S15, the PC <NUM> stores the license communication file in the medium <NUM> according to, for example, an operation of the user.

Thereafter, the license acquisition processing ends.

On the other hand, in step S13, the PC <NUM> determines not to acquire the license communication file in a case where the display control file for finally confirming the execution of the installation of the license has not been received or in a case where an instruction on the acquisition of the license communication file has not been given. Thereafter, the processing of steps S14 and S15 is skipped, such that the license acquisition processing ends without acquiring the license communication file.

Next, license issuance processing executed by the server <NUM>, corresponding to the license acquisition processing by the client <NUM> of <FIG> will be described with reference to a flowchart of <FIG>.

Note that this processing is started, for example, when the server <NUM> has received the request for the device information acquisition file from the PC <NUM> in step S1 of <FIG> described above.

In step S31, the server <NUM> transmits the device information acquisition file. Specifically, the data generation unit <NUM> generates the device information acquisition file including the device information acquisition command. The communication unit <NUM> transmits the device information acquisition file to the PC <NUM> via the network <NUM> under the control of the communication control unit <NUM>.

Note that the processing of step S31 can be omitted by omitting the processing of steps S1 to S3 of <FIG> of the electronic device <NUM> as described above.

In step S32, the server <NUM> receives the device information file. Specifically, the communication control unit <NUM> receives the device information file transmitted from the PC <NUM> in the processing of step S12 of <FIG> described above, via the communication unit <NUM>.

In step S33, the license management unit <NUM> determines whether or not the device information file is valid. Specifically, the license management unit <NUM> reads the server secret key corresponding to the server public key used to encrypt the device unique key included in the device information file, from the storage unit <NUM>. The license management unit <NUM> decrypts the device unique key using the read server secret key.

Next, the license management unit <NUM> calculates a hash value of the storage data included in the device information file using the same hash function as that of the electronic device <NUM> and the decrypted device unique key. Then, the license management unit <NUM> determines that the device information file is valid in a case where the calculated hash value coincides with a hash value in the device information file, and the processing proceeds to step S34.

Therefore, tampering or the like of the device unique ID, the device RTC, and the device unique key in the storage data is prevented.

In step S34, the license management unit <NUM> determines whether or not to transmit the license communication file.

Specifically, the UI control unit <NUM> generates the display control file for finally confirming the execution of the installation of the license. The communication unit <NUM> transmits the display control file to the PC <NUM> via the network <NUM> under the control of the communication control unit <NUM>.

Then, the license management unit <NUM> determines to transmit the license communication file in a case where the PC <NUM> requests the server to transmit the license communication file in step S13 of <FIG> described above, and the processing proceeds to step S35.

In step S35, the license management unit <NUM> generates an installation key.

A to C of <FIG> illustrate examples of formats of installation keys.

A of <FIG> illustrates a format example of an installation key in a case where only an effective term is set. This installation key includes a function ID, system unique information, a device unique ID, and an effective term.

The function ID is an ID for identifying a function that becomes a target of a license.

The system unique information is a serial number including alphanumeric characters generated by the server <NUM>, and is different for every installation key.

The device unique ID is a device unique ID of the electronic device <NUM> that becomes a target to which the license is to be provided, and the device unique ID of the electronic device <NUM> included in the device information file is used.

The effective term indicates an effective term of the license. For example, the effective term is set in units of hours. Note that the effective term is set to, for example, a value obtained by adding a grace time to an actual effective term of the license. For example, in a case where the actual effective term of the license is <NUM> days and the grace time is <NUM> hour, this effective term is set to <NUM> hours (= <NUM> hours × <NUM> days + <NUM> hour).

Here, the grace time is a time set on the assumption that a time is required to install the license in the electronic device <NUM>. That is, since the electronic device <NUM> does not directly communicate with the server <NUM> via the network <NUM>, the electronic device <NUM> exchanges data with the PC <NUM> via the medium <NUM>, and the PC <NUM> communicates with the server <NUM>. Therefore, as compared with a case where the electronic device <NUM> directly communicates with the server <NUM>, it takes time to install the license. Therefore, a predetermined grace time is added, in addition to the actual effective term of the license.

B of <FIG> illustrates a format example of an installation key in a case where only an expiration time is set. This installation key is different from that of the example of A of <FIG> in that it includes an expiration time instead of the effective term.

The expiration time indicates the date and time when the license expires, and is represented by, for example, year, month, day, hour, minute, and second. Furthermore, the expiration time is set on the basis of the device RTC included in the device information file, that is, the RTC <NUM> of the electronic device <NUM>. For example, when the expiration time based on the RTC <NUM> of the server <NUM> is a server expiration time and the current date and time of the RTC <NUM> is the server current date and time, an expiration time (client expiration time) of the installation key is calculated by the following Equation (<NUM>).

The expiration time is converted from the date and time based on the RTC <NUM> of the server <NUM> to the date and time based on the RTC <NUM> of the electronic device <NUM> by Equation (<NUM>).

C of <FIG> illustrates a format example of an installation key in a case where both of an expiration time and an effective term are set. The expiration time of this example is also set on the basis of the device RTC included in the device information file. Furthermore, in this example, the start date and time of the license is calculated by subtracting the effective term from the expiration time. That is, this license is effective from the start date and time until the expiration time.

Note that in this example, the grace time does not necessarily need to be added to the effective term on the assumption that the license is installed by the start date and time. That is, the grace time may be added to the effective term or may not be added to the effective term.

In step S36, the data generation unit <NUM> generates storage data including the device RTC and the installation key.

In step S37, the data generation unit <NUM> calculates a hash value of the storage data using the device unique key. That is, the data generation unit <NUM> calculates a hash value of the storage data using the same hash function as that of the electronic device <NUM> and the device unique key included in the device information file.

In step S38, the data generation unit <NUM> generates a license communication file including the storage data and the hash value. Specifically, the data generation unit <NUM> generates a signature by encrypting the hash value using the server secret key. Then, the data generation unit <NUM> generates a license communication file including the storage data and the signature (encrypted hash value). Therefore, security of the storage data is ensured using the device unique key.

Note that the license communication file is also an installation file used to install the license in the electronic device <NUM>.

In step S39, the server <NUM> stores license information. For example, the storage control unit <NUM> causes the storage unit <NUM> to store license information including a combination of the current date and time of the RTC <NUM>, the device unique ID, the device unique key, the installation key, the device RTC, and the server expiration time of the license.

Note that in a case where only the effective term is set in the installation key as illustrated in A of <FIG>, the license management unit <NUM> calculates the server expiration time by adding the effective term (including the grace time) to the current date and time of the RTC <NUM>. Furthermore, for example, in a case where the expiration time is set in the installation key as illustrated in B or C of <FIG>, the license management unit <NUM> uses a server expiration time before conversion of the expiration time (client expiration time) of the installation key as the license information.

Furthermore, an approximate deviation between the RTC <NUM> of the server <NUM> and the RTC <NUM> of the electronic device <NUM> is grasped on the basis of a difference between the current date and time of the RTC <NUM> and the device RTC.

In step S40, the communication unit <NUM> transmits the license communication file to the PC <NUM> under the control of the communication control unit <NUM>.

Thereafter, the license issuance processing ends.

On the other hand, in step S34, the license management unit <NUM> determines not to transmit the license communication file in a case where the PC <NUM> does not request the server to transmit the license communication file in step S13 of <FIG> described above, the processing of steps S35 to S40 is skipped, and the license issuance processing ends. That is, the generation of the installation key and the transmission of the license communication file are not performed.

Furthermore, in step S33, the license management unit <NUM> determines that the device information file is not valid in a case where the calculated hash value does not coincide with the hash value in the device information file, the processing of steps S34 to S40 is skipped, and the license issuance processing ends. That is, the generation of the installation key and the transmission of the license communication file are not performed.

Next, license management processing executed by the electronic device <NUM> will be described with reference to flowcharts of <FIG> and <FIG>.

For example, when the medium <NUM> in which the license communication file is stored is connected to the drive <NUM> of the electronic device <NUM>, the output unit <NUM> displays a window <NUM> of <FIG> under the control of the UI control unit <NUM>, for example.

In the window <NUM>, a type name of the electronic device <NUM>, a type of function and a license type, and a message for confirming whether or not to enable the function are displayed. Furthermore, a YES button <NUM> and a NO button <NUM> are displayed in the window <NUM>. Then, in a case where the YES button <NUM> is pressed, the license management processing is started. On the other hand, in a case where the NO button <NUM> is pressed, the license management processing is not started.

In step S61, the license management unit <NUM> determines whether or not the license communication file is valid. Specifically, the license management unit <NUM> reads the license communication file from the medium <NUM> via the drive <NUM>. Furthermore, the license management unit <NUM> reads the device unique key and the server public key from the storage unit <NUM>.

The license management unit <NUM> decrypts the signature included in the license communication file using the server public key. Therefore, the hash value of the storage data included in the license communication file is obtained. Furthermore, the license management unit <NUM> calculates the hash value of the storage data of the license communication file using the same hash function as that of the server <NUM> and the device unique key. Then, the license management unit <NUM> determines that the license communication file is valid in a case where the calculated hash value coincides with a hash value in the license communication file, and the processing proceeds to step S62.

Therefore, tampering or the like of the device RTC and the installation key in the storage data is prevented.

In step S62, the license management unit <NUM> determines whether or not the installation key is an installation key that has been installed in the past. The license management unit <NUM> determines that the installation key is not the installation key that has been installed in the past in a case where an installation key coinciding with the installation key included in the license communication file is not stored in the storage unit <NUM>, and the processing proceeds to step S63.

Therefore, it is prevented that the license is installed doubly using the installation key that has been installed in the past.

In step S63, the license management unit <NUM> determines whether or not the device unique ID in the installation key coincides with that of an own device. The license management unit <NUM> determines that the device unique ID in the installation key coincides with that of the own device in a case where the device unique ID in the installation key coincides with the device unique ID of the electronic device <NUM> stored in the storage unit <NUM>, and the processing proceeds to step S64.

Therefore, it is prevented that the license is installed using an installation key for another electronic device <NUM>.

In step S64, the license management unit <NUM> determines whether or not the device RTC is on and after the current date and time. In a case where the license management unit <NUM> determines that the device RTC included in the license communication file is before the current date and time of the RTC <NUM>, the processing proceeds to step S65.

In step S65, the license management unit <NUM> determines whether or not an expiration time of the license has expired.

Specifically, the license management unit <NUM> calculates the expiration time (client expiration time) of the license by adding the effective term to the device RTC in a case where only the effective term is included in the installation key as illustrated in A of <FIG>. Then, the license management unit <NUM> compares the calculated expiration time with the current date and time of the RTC <NUM>.

On the other hand, the license management unit <NUM> compares the expiration time with the current date and time of the RTC <NUM> in a case where the expiration time (client expiration time) is included in the installation key as illustrated B or C of <FIG>.

Then, the license management unit <NUM> determines that the expiration time of the license has not expired in a case where the expiration time of the license is after the current date and time of the RTC <NUM>, and the processing proceeds to step S66.

In step S66, the license management unit <NUM> determines whether or not an interval between the device RTC and the current date and time is equal to or longer than the grace time. In a case where the license management unit <NUM> compares the device RTC with the current date and time of the RTC <NUM> to determine that the interval between the device RTC and the current date and time is less than the grace time, the processing proceeds to step S67.

This is, for example, a case where installation of the license in the electronic device <NUM> has been performed within the grace time (for example, one hour) since the device RTC was set in the processing of step S6 of <FIG> described above.

In step S67, the license management unit <NUM> determines whether or not the start date and time of the license has been designated. The license management unit <NUM> determines that the start date and time of the license has been designated in a case where the expiration time and the effective term are included in the installation key as illustrated in C of <FIG>, and the processing proceeds to step S68.

In step S68, the license management unit <NUM> determines whether or not the start date and time of the license has been reached. Specifically, the license management unit <NUM> calculates the start date and time of the license by subtracting the effective term from the expiration time of the installation key. The license management unit <NUM> determines that the start date and time of the license has not been reached in a case where the calculated start date and time of the license is after the current date and time of the RTC <NUM>, and the processing proceeds to step S69.

In step S69, the license management unit <NUM> determines whether or not the RTC <NUM> has been in an unset status. In a case where it is determined that the RTC <NUM> has not been in the unset status, the processing returns to step S68.

Thereafter, the processing of steps S68 and S69 is repeatedly executed until it is determined in step S68 that the start date and time of the license has been reached or it is determined in step S69 that the RTC <NUM> has been in the unset status.

On the other hand, in a case where it is determined in step S69 that the RTC <NUM> has been in the unset status, the license management processing ends.

This is, for example, a case where the RTC <NUM> has been in the unset status due to a reason such as run-out of the backup battery, or the like, before the start date and time of the license is reached. That is, when the RTC <NUM> is in the unset status, period management of the license cannot be performed, and thus, the license management processing ends without activating the license.

Furthermore, in step S68, the license management unit <NUM> determines that the start date and time of the license has been reached in a case where the calculated start date and time of the license is before the current date and time of the RTC <NUM>, and the processing proceeds to step S70.

Moreover, in step S67, the license management unit <NUM> determines that the start date and time of the license has not been designated in a case where only one of the expiration time or the effective term is included in the installation key as illustrated in A or B of <FIG>, and the processing proceeds to step S70.

In step S70, the license management unit <NUM> activates the license. That is, the license management unit <NUM> makes a function whose license is given by the installation key usable.

Note that software realizing the function may be installed in the electronic device <NUM> in advance or may be installed at this time.

In step S71, the electronic device <NUM> stores the license information. Specifically, the license management unit <NUM> obtains the client expiration time of the license by processing similar to that of step S65. The storage control unit <NUM> causes the storage unit <NUM> to store the license information including a combination of the current date and time of the RTC <NUM>, the installation key, and the client expiration time of the license. Note that the current date and time of the RTC <NUM> is the date and time when the license is started to be used.

In step S72, the license management unit <NUM> determines whether or not the expiration time of the license has expired. The license management unit <NUM> determines that the expiration time of the license has not expired in a case where the expiration time of the license stored in the storage unit <NUM> is after the current date and time of the RTC <NUM>, and the processing proceeds to step S73.

In step S73, it is determined whether or not the RTC <NUM> has been in an unset status, similarly to the processing of step S69. In a case where it is determined that the RTC <NUM> has not been in the unset status, the processing returns to step S72.

Thereafter, the processing of steps S72 and S73 is repeatedly executed until it is determined in step S72 that the expiration time of the license has expired or it is determined in step S73 that the RTC <NUM> has been in the unset status.

On the other hand, in a case where it is determined in step S73 that the RTC <NUM> has been in the unset status, the processing proceeds to step S74. This is a case when the RTC <NUM> has been in the unset status during the effective term of the license.

Furthermore, in step S72, the license management unit <NUM> determines that the expiration time of the license has expired in a case where the expiration time of the license stored in the storage unit <NUM> is before the current date and time of the RTC <NUM>, and the processing proceeds to step S74.

In step S75, the license management unit <NUM> deactivates the license.

Specifically, the license management unit <NUM> makes a function whose expiration time of the license has expired unusable, in a case where the expiration time of the license has expired.

On the other hand, the license management unit <NUM> cannot perform period management of the license in a case where the RTC <NUM> has been in the unset status, and thus, makes the function unusable. Note that in a case where there is a plurality of functions whose licenses are managed by a similar method, all of those functions are made unusable.

Note that when a condition for deactivating the license is satisfied in a case where the power supply of the electronic device <NUM> is turned on, it is desirable to deactivate the license, for example, at a timing when the power supply of the electronic device <NUM> is turned off next or at a timing when the power supply of the electronic device <NUM> is turned on again after the power supply of the electronic device <NUM> is turned off next. This is because when the license is deactivated in a case where the power supply of the electronic device <NUM> is turned on, there is a possibility that a function cannot be suddenly used while the electronic device <NUM> is being used, such that there is a possibility that convenience of the user will be impaired.

Thereafter, the license management processing ends.

On the other hand, in step S66, in a case where the license management unit <NUM> determines that the interval between the device RTC and the current date and time of the RTC <NUM> is equal to or longer than the grace time, the processing proceeds to step S75.

This is, for example, a case where installation of the license in the electronic device <NUM> has been performed after the grace time (for example, one hour) has elapsed since the device RTC was set in the processing of step S6 of <FIG> described above.

Furthermore, in step S65, the license management unit <NUM> determines that the expiration time of the license has expired in a case where the expiration time of the license is before the current date and time of the RTC <NUM>, and the processing proceeds to step S75.

This is, for example, a case where the installation of the license in the electronic device <NUM> has been performed after the expiration time of the license has expired.

In step S75, license re-acquisition processing is executed, and thereafter, the license management processing ends.

Note that details of the license re-acquisition processing will be described later with reference to <FIG>.

On the other hand, in a case where it is determined in step S64 that the device RTC is on and after the current date and time of the RTC <NUM>, the license management processing ends.

This is, for example, a case where tampering of the device RTC, abnormality of the RTC <NUM>, or the like, has occurred.

Furthermore, in a case where it is determined in step S63 that the device unique ID in the installation key does not coincide with that of the own device, the license management processing ends.

This is, for example, a case where it has been attempted to connect the medium <NUM> to a different electronic device <NUM> to install the license, a case where an erroneous license communication file has been received, a case where the installation key has been tampered with, or the like.

Moreover, in step S62, the license management unit <NUM> determines that the installation key is the installation key that has been installed in the past in a case where the installation key coinciding with the installation key included in the license communication file is stored in the storage unit <NUM>, and the license management processing ends.

This is a case where it has been attempted to install the previously installed license again.

Furthermore, in step S61, the license management unit <NUM> determines that the license communication file is not valid in a case where the calculated hash value does not coincide with the hash value in the license communication file, and the license management processing ends.

This is a case where tampering or the like of the license communication file has been performed.

In such a manner, even though the server <NUM> and the electronic device <NUM> do not directly communicate with each other, the license can be installed in the electronic device <NUM> in a safe status to make the function of the electronic device <NUM> usable.

Furthermore, even though a deviation is generated between the RTC <NUM> of the server <NUM> and the RTC <NUM> of the electronic device <NUM>, the period management of the license can be appropriately performed using the RTC <NUM> of the electronic device <NUM>.

Moreover, by adding the grace time to the effective term of the license, it is prevented that a term in which the license can be used is shortened even though it takes time to install the license because the server <NUM> and the electronic device <NUM> do not directly communicate with each other.

Furthermore, even though the server <NUM> and the electronic device <NUM> do not communicate directly with each other, a deviation between an expiration time (server expiration time) of the license grasped by the server <NUM> and an actual expiration time (client expiration time) of the license is suppressed within the grace time. Therefore, for example, a promotion such as update of the license, or the like, can be performed at an appropriate timing.

Next, details of the license re-acquisition processing of step S75 of <FIG> will be described with reference to a flowchart of <FIG>.

In step S101, the PC <NUM> requests a license re-issuance file.

For example, the PC <NUM> accesses the server <NUM> via the network <NUM> according to an operation of the user to display a screen for requesting re-issuance of the license. For example, a window <NUM> of <FIG> is displayed on the screen of the PC <NUM>.

The window <NUM> is divided into a device information field 501A, a license information field 501B, and a license detailed information field 501C.

At a left end of the device information field 501A, an image and a type name of the electronic device <NUM> are displayed laterally side by side.

At a left end of the license information field 501B, a function that becomes a target re-issuing the license and a type of the license are shown. In this example, it is shown that a license of an imaging function of a <NUM> image during an effective term of one week is a re-issuance target.

In the license detailed information field 501C, a detailed status of the license of the function that becomes the target is shown. In this example, a device unique ID of the electronic device <NUM>, a current status of the license, and an expiration time of the license are displayed. Note that the current status of the license is "Installed" regardless of whether or not the license has been actually installed in the electronic device <NUM>, at a point in time of downloading the license communication file.

At a right end of the license detailed information field 501C, a re-issuance button <NUM> is displayed. When the re-issuance button <NUM> is pressed, license re-issuance processing is started. For example, when the re-issuance button <NUM> is pressed, the PC <NUM> requests the server <NUM> to transmit the license re-issuance file, via the network <NUM>.

In response to this request, the server <NUM> transmits the license re-issuance file to the PC <NUM> via the network <NUM> in step S131 of <FIG> as described later.

In step S102, the PC <NUM> receives the license re-issuance file transmitted from the server <NUM>. Furthermore, the PC <NUM> stores the received license re-issuance file in the medium <NUM> according to, for example, an operation of the user.

At this time, for example, a window <NUM> of <FIG> is displayed on the screen of the PC <NUM>.

In the window <NUM>, a message for prompting the user to upload the device information file acquired from the camera (electronic device <NUM>) after selecting a "re-issuance" button in the camera (electronic device <NUM>), and an upload button <NUM> are displayed.

In step S103, the electronic device <NUM> executes a command in the license re-issuance file.

Specifically, the user detaches the medium <NUM> in which the license re-issuance file is stored from the PC <NUM>, and connects the medium <NUM> to the drive <NUM> of the electronic device <NUM>.

The drive <NUM> reads the license re-issuance file stored in the medium <NUM> and supplies the read license re-issuance file to the control unit <NUM>. The control unit <NUM> executes a license re-issuance command included in the license re-issuance file.

Therefore, for example, the output unit <NUM> displays a screen including a "re-issuance" button under the control of the UI control unit <NUM>. Then, when the "re-issuance" button is pressed, acquisition processing of device information is started.

Note that, for example, the processing of steps S101 to S103 may be omitted, and processing of step S104 and subsequent steps may be started by operating the electronic device <NUM> by the user without using the license re-issuance command or automatically.

In step S104, the current date and time of the RTC <NUM> is set as the device RTC, similarly to the processing of step S6 of <FIG>.

In step S105, the device unique key is encrypted with the server public key, similarly to the processing of step S7 of <FIG>.

In step S106, the data generation unit <NUM> generates storage data including a device unique ID, the device RTC, the device unique key, and a canceled installation key. Specifically, the data generation unit <NUM> reads the device unique ID and an installation key for a license whose installation has been canceled (canceled installation key) from the storage unit <NUM>. The data generation unit <NUM> generates storage data including the device unique ID, the device RTC, the encrypted device unique key, and the canceled installation key.

In step S107, a hash value of the storage data is calculated using the device unique key, similarly to the processing of step S9 of <FIG>.

In step S108, a device information file including the storage data and the hash value is generated, similarly to the processing of step S10 of <FIG>. This device information file is used by the server <NUM> to reissue a license as a license re-request file for requesting re-issuance of the license.

In step S109, the device information file is stored in the medium <NUM>, similarly to the processing of step S11 of <FIG>.

In step S110, the PC <NUM> transmits the device information file to the server <NUM>.

For example, the user detaches the medium <NUM> from the electronic device <NUM>, and connects the medium <NUM> to the PC <NUM>. Then, for example, when the upload button <NUM> in the window <NUM> of <FIG> described above is pressed, the PC <NUM> reads the device information file from the medium <NUM> and transmits the read device information file to the server <NUM> via the network <NUM>.

In response to this transmission, the server <NUM> receives the device information file in step S132 of <FIG> as described later. Then, the server <NUM> notifies the PC <NUM> that the license can be re-issued, via the network <NUM> in step S134, if the device information file includes the canceled installation key and is valid.

In step S111, the PC <NUM> determines whether or not to request re-issuance of the license. For example, in a case where the PC <NUM> has been notified from the server <NUM> that the license can be re-issued, the PC <NUM> displays a window <NUM> of <FIG> on the screen.

In the window <NUM>, a message to cancel installation and perform re-issuance of the installation key and a re-issuance button <NUM> are displayed. Furthermore, information regarding the license whose installation is canceled is displayed in the message. The information regarding the license includes, for example, a type name of the electronic device <NUM>, a function name, and a type of the license.

Then, when the re-issuance button <NUM> is pressed, the PC <NUM> determines to request the re-issuance of the license, and requests the server <NUM> to re-issue the license, via the network <NUM>. Thereafter, the processing proceeds to step S112.

In step S112, the PC <NUM> determines whether or not to acquire a license communication file.

Specifically, when the re-issuance of the license is requested, the server <NUM> discards a current installation key of the license in step S136 of <FIG> as described later, and then, transmits a display control file including a message for notifying the PC <NUM> that the installation key can be re-issued, to the PC <NUM>.

In response to this transmission, the PC <NUM> displays, for example, a window <NUM> of <FIG> on the screen. In the window <NUM>, a message for prompting the user to cancel the installation of the license and installing the license again, and an OK button <NUM> are displayed. When the OK button <NUM> is pressed, a window <NUM> of <FIG> is displayed on the screen of the PC <NUM>.

The window <NUM> is divided into a device information field 541A, a license information field 541B, and a license detailed information field 541C, similarly to the window <NUM> of <FIG>, and has display contents substantially similar to those of the window <NUM>. However, the window <NUM> is different from the window <NUM> in that the re-issuance button <NUM> disappears and an installation button <NUM> is displayed at a right end of the license information field 501B. Furthermore, the window <NUM> is different from the window <NUM> in that nothing is displayed with respect to a current status of the license and an expiration time.

Then, when the installation button <NUM> is pressed, the PC <NUM> determines to acquire the license communication file and requests the server <NUM> to transmit the license communication file via the network <NUM>. Thereafter, the processing proceeds to step S113.

In response to this request, the server <NUM> transmits the license communication file including an installation key and the like in step S143 of <FIG> as described later.

In step S113, the license communication file is received, similarly to the processing of step S14 of <FIG>.

In step S114, the license communication file is stored in the medium <NUM>, similarly to the processing of step S15 of <FIG>.

Thereafter, the license re-acquisition processing ends.

Next, license re-issuance processing executed by the server <NUM>, corresponding to the license re-acquisition processing by the client <NUM> of <FIG> will be described with reference to a flowchart of <FIG>.

Note that this processing is started, for example, when the server <NUM> has received the request for the license re-issuance file from the PC <NUM> in step S101 of <FIG> described above.

In step S131, the server <NUM> transmits the license re-issuance file. Specifically, the data generation unit <NUM> generates the license re-issuance file including the license re-issuance command. The communication unit <NUM> transmits the license re-issuance file to the PC <NUM> via the network <NUM> under the control of the communication control unit <NUM>.

Note that the processing of step S131 can be omitted by omitting the processing of steps S101 to S103 of <FIG> of the electronic device <NUM> as described above.

In step S132, the server <NUM> receives the device information file. Specifically, the communication control unit <NUM> receives the device information file transmitted from the PC <NUM> in the processing of step S110 of <FIG> described above, via the communication unit <NUM>.

In step S133, it is determined whether or not the device information file is valid, similarly to the processing of step S33 of <FIG>. In a case where it is determined that the device information file is valid, the processing proceeds to step S134.

In step S134, the license management unit <NUM> determines whether or not the canceled installation key is included in the device information file. In a case where it is determined that the canceled installation key is included in the device information file, the processing proceeds to step S135. At this time, the communication unit <NUM> notifies the PC <NUM> that the license can be re-issued, via the network <NUM> under the control of the communication control unit <NUM>.

In step S135, the license management unit <NUM> determines whether or not the re-issuance of the license has been requested. The license management unit <NUM> determines that the re-issuance of the license has been requested in a case where the re-issuance of the license has been requested from the PC <NUM> in step S111 of <FIG> described above, and the processing proceeds to step S136.

In step S136, the license management unit <NUM> discards the installation key. For example, the license management unit <NUM> updates the information with the installation key as the installation key for the license whose installation has been canceled, in the license information including the installation key included in the device information file among the license information stored in the storage unit <NUM>.

Furthermore, the UI control unit <NUM> also generates a display control file including a message for notifying the PC <NUM> that the installation key can be re-issued. The communication unit <NUM> transmits the display control file to the PC <NUM> via the network <NUM> under the control of the communication control unit <NUM>.

In step S137, the license management unit <NUM> determines whether or not to transmit the license communication file. The license management unit <NUM> determines to transmit the license communication file in a case where the PC <NUM> requests the server to transmit the license communication file in step S112 of <FIG> described above, and the processing proceeds to step S138.

In step S138, the installation key is generated, similarly to the processing of step S35 of <FIG> described above. At this time, in a case where the installation key includes an expiration time, the expiration time (client expiration time) is set on the basis of the device RTC included in the device information file received in the processing of step S132. That is, the license expiration time is updated on the basis of the newly acquired device RTC.

Thereafter, in steps S139 to S143, processing similar to that of steps S36 to S40 of <FIG> described above is performed. Therefore, a license communication file including the device RTC in the device information file received in step S132 and the regenerated installation key is generated and transmitted to the PC <NUM>.

Thereafter, the license re-issuance processing ends.

On the other hand, in step S137, the license management unit <NUM> determines not to transmit the license communication file in a case where the PC <NUM> does not request the server to transmit the license communication file in step S112 of <FIG> described above, the processing of steps S138 to S143 is skipped, and the license re-issuance processing ends.

That is, the regeneration of the installation key and the transmission of the license communication file are not performed. However, by again requesting the re-issuance of the license from the PC <NUM> later, it is possible to cause the server <NUM> to regenerate the installation key and transmit the license communication file including the regenerated installation key.

Furthermore, in step S135, the license management unit <NUM> determines that the re-issuance of the license has not been requested in a case where the re-issuance of the license has not been requested from the PC <NUM> in step S111 of <FIG> described above, the processing of steps S136 to S143 is skipped, and the license re-issuance processing ends. That is, the regeneration of the installation key and the transmission of the license communication file are not performed.

Moreover, in a case where it is determined in step S134 that the canceled installation key is not included in the device information file, the processing of steps S135 to S143 is skipped, and the license re-issuance processing ends. That is, the regeneration of the installation key and the transmission of the license communication file are not performed.

Furthermore, in a case where it is determined in step S133 that the device information file is not valid, the processing of steps S134 to S143 is skipped, and the license re-issuance processing ends. That is, the regeneration of the installation key and the transmission of the license communication file are not performed.

In such a manner, even though the server <NUM> and the electronic device <NUM> do not directly communicate with each other, the re-issuance of the license whose installation has been canceled can be performed and the re-issued license can be installed in the electronic device <NUM> in a safe status to make the function of the electronic device <NUM> usable.

Furthermore, since the expiration time of the license is updated on the basis of the new device RTC, it is prevented that the effective term of the license is shortened due to the re-issuance of the license. Moreover, even though a deviation is generated between the RTC <NUM> of the server <NUM> and the RTC <NUM> of the electronic device <NUM>, period management of the re-issued license can be appropriately performed using the RTC <NUM> of the electronic device <NUM>.

Hereinafter, a modification of the embodiment of the present technology described above will be described.

For example, another information processing apparatus (for example, a smartphone, a tablet, and the like) that can communicate with the server <NUM> and can read and write data from and to the medium <NUM> may be used, instead of the PC <NUM>.

Furthermore, for example, the server <NUM> and the electronic device <NUM> may exchange data with each other via another information processing apparatus (for example, a smartphone, a tablet, or the like) without using the medium <NUM>.

<FIG> illustrates an example of a case where the server <NUM> and the electronic device <NUM> exchange data with each other via a smartphone <NUM>.

For example, the server <NUM> and the smartphone <NUM> perform communication based on a 4th generation (<NUM>) mobile communication standard (hereinafter, referred to as <NUM> communication). The electronic device <NUM> and the smartphone <NUM> perform communication with each other via Wi-Fi.

In this case, since the smartphone <NUM> cannot perform the <NUM> communication and the Wi-Fi communication at the same time, exchange of data is sequentially performed, similarly to a case of using the medium <NUM> described above.

Specifically, first, the electronic device <NUM> and the smartphone <NUM> are connected to each other by the Wi-Fi, and the electronic device <NUM> transmits a device information file to the smartphone <NUM>.

Next, the server <NUM> and the smartphone <NUM> are connected to each other by the <NUM> communication, and the smartphone <NUM> transmits the device information file to the server <NUM>. The server <NUM> generates a license communication file using the received device information file and transmits the license communication file to the smartphone <NUM>.

Next, the electronic device <NUM> and the smartphone <NUM> are reconnected to each other by the Wi-Fi, and the electronic device <NUM> transmits the license communication file to the smartphone <NUM>. Then, the electronic device <NUM> installs a license using the license communication file.

In such a manner, the license provided by the server <NUM> can be installed in the electronic device <NUM> without using the media <NUM> and without performing direct communication between the server <NUM> and the electronic device <NUM>. Furthermore, since security of a communication path between the server <NUM> and the electronic device <NUM> is secured using a device unique key, tampering or the like of data is prevented.

Note that in this case, a series of installation processing is limited so as to be performed within a grace time, similarly to a case where the medium <NUM> is used. That is, unless the installation processing of the license is performed within the grace time since the electronic device <NUM> has transmitted the device information file to the smartphone <NUM>, the license is not installed, and needs to be re-issued.

Furthermore, for example, short-range wireless communication such as Bluetooth (registered trademark), near field communication (NFC), and the like may be used as communication between the electronic device <NUM> and the smartphone <NUM>. Therefore, it becomes possible for the server <NUM> and the electronic device <NUM> to directly communicate with each other via the smartphone <NUM>. However, in this case, the electronic device <NUM> needs to support the short-range wireless communication.

Moreover, an example in which the installation of the license is prohibited and the license is re-acquired and installed in a case where the installation of the license in the electronic device <NUM> is not performed within a predetermined grace time has been described in the above description. On the other hand, for example, the installation of the license may be permitted even after a lapse of the grace time. For example, in step S66 of <FIG>, in a case where it is determined that the interval between the device RTC and the current date and time is equal to or longer than the grace time, the processing proceeds to step S70, and the license may be immediately activated in step S70. Note that in this case, for example, an effective term of the license is shortened by a lapse time of the grace time.

Furthermore, the formats of the installation keys of <FIG> are examples, and can be appropriately changed. For example, some of the data included in the installation key are not stored in the installation key, and may be stored in a file such as the license communication file or the like for transmitting the installation key.

Moreover, an example in which the information is transmitted and received mainly in a file format between the server <NUM> and the client <NUM> has been described in the above description, but any other format can also be used as a format of information to be transmitted and received.

The series of processing described above can be executed by hardware or can be executed by software. In a case where the series of processing is executed by the software, programs configuring the software are installed in a computer. Here, the computer includes a computer incorporated in dedicated hardware, or, for example, a general-purpose personal computer that can execute various functions by installing various programs, or the like.

<FIG> is a block diagram illustrating a configuration example of hardware of a computer that executes the series of processing described above by a program.

In the computer <NUM>, a central processing unit (CPU) <NUM>, a read only memory (ROM) <NUM>, and a random access memory (RAM) <NUM> are connected to each other by a bus <NUM>.

An input/output interface <NUM> is further connected to the bus <NUM>. An input unit <NUM>, an output unit <NUM>, a recording unit <NUM>, a communication unit <NUM>, and a drive <NUM> are connected to the input/output interface <NUM>.

The input unit <NUM> includes an input switch, a button, a microphone, an imaging element, and the like. The output unit <NUM> includes a display, a speaker, and the like. The recording unit <NUM> includes a hard disk, a nonvolatile memory, or the like. The communication unit <NUM> includes a network interface and the like. The drive <NUM> drives a removable recording medium <NUM> such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like.

In the computer <NUM> configured as described above, the CPU <NUM> performs the series of processing described above by loading, for example, a program recorded in the recording unit <NUM> into the RAM <NUM> via the input/output interface <NUM> and the bus <NUM> and executing the program.

The program executed by the computer <NUM> (CPU <NUM>) can be provided by being recorded on the removable recording medium <NUM> as, for example, a package medium and the like. Furthermore, the program can be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.

In the computer <NUM>, the program can be installed in the recording unit <NUM> via the input/output interface <NUM> by mounting the removable recording medium <NUM> on the drive <NUM>. Furthermore, the program can be received by the communication unit <NUM> via the wired or wireless transmission medium and be installed in the recording unit <NUM>. In addition, the program can be installed in the ROM <NUM> or the recording unit <NUM> in advance.

Note that the program executed by the computer may be a program by which processing is performed in time series according to the order described in the present specification or may be a program by which processing is performed in parallel or at a necessary timing such as a timing when a call is made, or the like.

Furthermore, in the present specification, the system means a set of a plurality of components (apparatuses, modules (parts), or the like), and it does not matter whether or not all the components are in the same housing. Therefore, both of a plurality of apparatuses housed in separate housings and connected to each other via a network and one apparatus in which a plurality of modules is housed in one housing are systems.

Moreover, the embodiment of the present technology is not limited to the embodiment described above, and various modifications can be made without departing from the scope of the present technology.

For example, the present technology can have a configuration of cloud computing in which one function is shared and jointly processed by a plurality of apparatuses via a network.

Furthermore, the respective steps described in the abovementioned flowcharts can be executed by one apparatus or can be executed in a shared manner by a plurality of apparatuses.

Moreover, in a case where a plurality of processing is included in one step, the plurality of processing included in one step can be executed by one apparatus or can be executed in a shared manner by a plurality of apparatuses.

Claim 1:
An information processing apparatus (<NUM>) comprising:
a data generation unit (<NUM>) configured to generate first license communication information using first device information, the first device information being information including a first reference date and time and a device unique key, the first reference date and time being a date and time set using a hardware clock (<NUM>) of an electronic device (<NUM>) and being a date and time used for period management of a license, the device unique key being a key unique to the electronic device, and the first license communication information being information including an expiration time of the license and the first reference date and time and used for installing the license in the electronic device; and
a license management unit (<NUM>) configured to set the expiration time on a basis of the first reference date and time.