Image forming apparatus and method for setting license information

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to license setting for an application operating on an image forming apparatus.

2. Description of the Related Art

In conventional systems, specific applications are widely installed in an image forming apparatus such as a digital multifunction peripheral (MFP) placed in an office, to provide various services. When installing an application in an image forming apparatus, identification of a model of an operable image forming apparatus, valid license code input processing, and activation processing are required to prevent unauthorized operations.

There has been proposed a method for storing data including a license code in the image forming apparatus and after that performing the following license authentication. <ul><li id="ul0001-0001" num="0006">(a) Display a license input screen on an input screen of the image forming apparatus, and prompt a user to input a license code.</li><li id="ul0001-0002" num="0007">(b) Transmit data stored in the image forming apparatus to an external server, have the external server determine the validity of the data, and validate the data based on a response therefrom (Japanese Patent Application Laid-Open No. 2010-186376).</li></ul>

However, when a method for inputting a license code from an operation unit of the image forming apparatus is employed, it is necessary to activate the image forming apparatus and input a license code from the operation unit. Depending on the image forming apparatus, it is necessary to turn OFF the power of the image forming apparatus and then turn ON again to activate a program. There has been a problem that license setting takes time in a case where the image forming apparatus needs to be reactivated repeatedly, for example, if a license code is incorrectly input or if there are many licenses to be set when the image forming apparatus is initially installed.

When a method for connecting with an external server via a network and inputting a license code to the image forming apparatus is employed, there is a problem that license code input is not possible unless a network for connecting the image forming apparatus with the external server is established.

SUMMARY OF THE INVENTION

The present invention is directed to providing a mechanism for shortening the time of setting a license code to install an application in an image forming apparatus and improving the operability of a license setting operation.

According to an aspect of the present invention, an image forming apparatus having a function of validating a license by inputting license information includes: a storage unit configured to be accessible from an external device even if the power of the image forming apparatus is OFF; and a control unit configured to, when the power of the image forming apparatus is turned ON, if license information is has been written in the storage unit from an external device while the power of the image forming apparatus was OFF, validate a function of the image forming apparatus corresponding to the license information by using the license information.

Further features and aspects of the present invention will become apparent from the following specific description of exemplary embodiments with reference to the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the invention and, together with the description, serve to explain the principles of the invention.

<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an example configuration of a license management system to which an image forming apparatus according to an exemplary embodiment of the present invention is applicable.

<figref idrefs="DRAWINGS">FIG. 2</figref> is a block diagram schematically illustrating a structure of a digital MFP.

<figref idrefs="DRAWINGS">FIG. 3</figref> is a block diagram illustrating an example detailed configuration of a dual interface (I/F) memory unit.

<figref idrefs="DRAWINGS">FIG. 4</figref> is a flowchart illustrating license validation processing for the digital MFP according to the present invention.

<figref idrefs="DRAWINGS">FIG. 5</figref> illustrates an example device management table managed by a license server.

<figref idrefs="DRAWINGS">FIG. 6</figref> illustrates an example application management table managed by the license server.

<figref idrefs="DRAWINGS">FIG. 7</figref> illustrates an example license access number management table managed by the license server.

<figref idrefs="DRAWINGS">FIG. 8</figref> illustrates example functions set in the digital MFP based on a license.

<figref idrefs="DRAWINGS">FIG. 9</figref> is a flowchart illustrating example license setting processing according to the present invention.

<figref idrefs="DRAWINGS">FIG. 10</figref> illustrates an example configuration of a license database stored in a hard disk drive (HDD).

<figref idrefs="DRAWINGS">FIG. 11</figref> illustrates an example configuration of access rights and storage data in each block of the dual I/F memory unit.

<figref idrefs="DRAWINGS">FIG. 12</figref> is a flowchart illustrating example license deletion processing according to the present invention.

DESCRIPTION OF THE EMBODIMENTS

Various exemplary embodiments, features, and aspects of the invention will be described in detail below with reference to the drawings.

<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an example configuration of a license management system to which an image forming apparatus according to an exemplary embodiment of the present invention is applicable.

A license server <b>101</b> is an information processing apparatus for generally managing the license management processing. A portable terminal <b>102</b> is an information processing apparatus managed by a user, an administrator, or a service engineer. A digital MFP <b>103</b> is used and managed by a user, an administrator, or a service engineer.

A network <b>104</b> is, for example, the Internet. The portable terminal <b>102</b> is connected with the license server <b>101</b> via the network <b>104</b>. Each of the portable terminal <b>102</b> and the digital MFP <b>103</b> is provided with a radio frequency identification (RFID) interface, enabling non-contact data transmission and reception even if the power of the digital MFP <b>103</b> is OFF. The digital MFP <b>103</b> will be described in detail below.

(Configuration of MFP)

<figref idrefs="DRAWINGS">FIG. 2</figref> is a block diagram schematically illustrating a structure of the digital MFP <b>103</b>. As illustrated in <figref idrefs="DRAWINGS">FIG. 2</figref>, the digital MFP <b>103</b> is connected to a local area network (LAN) and capable of performing data printing and data transmission and reception in response to an instruction from a personal computer (PC) connected to the LAN.

The digital MFP <b>103</b> includes four units: a controller unit <b>201</b>, a reader unit <b>202</b>, a printer unit <b>203</b>, and an operation unit <b>204</b>. The controller unit <b>201</b> is connected with the reader unit <b>202</b> (an image input device) and the printer unit <b>203</b> (an image output device). The controller unit <b>201</b>operation unit <b>20</b> is connected with the operation unit <b>204</b>, and detects a user instruction input from the operation unit <b>204</b> and performs various processing. The controller unit <b>201</b> is further connected with the LAN to enable flexibly inputting and outputting image data and device information.

In the controller unit <b>201</b>, a main controller <b>211</b> (a controller integrated circuit (IC)) includes a central processing unit (CPU) core and an image processing block, and controls the entire information processing apparatus. A random access memory (RAM) <b>212</b> serves not only as a system work memory for enabling the operation of the main controller <b>211</b> but also as an image memory for temporarily storing image data. A read-only memory (ROM) <b>213</b> is a boot ROM for storing a boot program of the system.

A system bus <b>214</b>, such as a peripheral component interconnect (PCI) bus, enables high-speed transmission and reception of communication data and image data. The main controller <b>211</b> is connected to an input/output (I/O) controller <b>215</b> and a network controller <b>217</b> via the system bus <b>214</b>.

The network controller <b>217</b> makes wired and wireless connection with an external network. The I/O controller <b>215</b> controls various I/O devices. The main controller <b>211</b> can access a HDD <b>216</b>, the operation unit <b>204</b>, and a dual interface memory unit (hereinafter referred to as dual I/F memory unit) <b>218</b> via the I/O controller <b>215</b>.

The HDD <b>216</b> (a mass storage) stores system software, image data, system management data, and box management data. The operation unit <b>204</b> includes a display (not illustrated) for displaying data via the I/O controller <b>215</b>. The operation unit <b>204</b> includes a touch panel and keys (not illustrated) for accepting various settings and operations for the digital MFP <b>103</b> input by the user. Upon detection of a user key input, the operation unit <b>204</b> notifies the main controller <b>211</b> of the user operation. Depending on the operation notified from the operation unit <b>204</b>, the main controller <b>211</b> changes the screen displayed on the above-described display and executes processing.

The dual I/F memory unit <b>218</b> includes a dual I/F memory <b>219</b> and an antenna <b>220</b> for the RFID (hereinafter simply referred to as antenna). The dual I/F memory <b>219</b> includes two interfaces, the Inter-Integrated Circuit (I2C) bus and the RFID, each enabling data write and read operations. The I2C bus is a serial bus developed by Phillips. The two interfaces included in the dual I/F memory <b>219</b> are not limited to the I2C bus and the RFID, and may be other interfaces as long as they can be similarly accessed by devices inside or outside the digital MFP <b>103</b>.

The I/O controller <b>215</b> can access the dual I/F memory unit <b>218</b> via the I2C bus. External devices can access the dual I/F memory unit <b>218</b> via the antenna <b>220</b> based on the RFID.

The dual I/F memory <b>219</b> is provided with a power supply and communication control function. Even if the internal power of the digital MFP <b>103</b> is turned OFF, with this control function the dual I/F memory <b>219</b> can be supplied with the power via the antenna <b>220</b> and accessed from outside.

Image data read by the reader unit <b>202</b> is input to the main controller <b>211</b>, and temporarily stored in the RAM. <b>212</b>. The main controller <b>211</b> includes a block for applying compression, decompression, and rotation processing to images, and enables accessing the image data stored in the RAM <b>212</b> to apply various processing thereto.

The image data compressed by the main controller <b>211</b> is stored in the HDD <b>216</b>. The compressed image data stored in the HDD <b>216</b> can be read and decompressed by the main controller <b>211</b>. Then, a relevant image can be formed on paper by the printer unit <b>203</b>.

The printer unit <b>203</b> mainly includes a printer <b>231</b> for converting image data into an image on paper. Printing methods for the printer <b>231</b> include the electrophotographic method using photosensitive drums and a photosensitive belt, and the ink jet method in which ink is discharged from a minute nozzle array to print an image directly on paper. Either printing method may be used in the present invention.

The printer unit <b>203</b> includes a power control unit <b>232</b> for performing power control for the entire digital MFP <b>103</b>. The power control unit <b>232</b> performs minute power control based on an instruction from the main controller <b>211</b>.

(Dual I/F Memory Detailed Block Diagram)

<figref idrefs="DRAWINGS">FIG. 3</figref> is a block diagram illustrating an example detailed configuration of the dual I/F memory unit <b>218</b>.

The dual I/F memory <b>219</b> having two interfaces, the I2C bus and a passive type RFID, enables data write and read operations. The portable terminal <b>102</b> has an active type RFID interface.

The I2C bus from the I/O controller <b>215</b> is connected to an I2C protocol unit <b>301</b>. The I2C protocol unit <b>301</b> converts I2C protocol data received from the I/O controller <b>215</b> into internal access data, and transmits it to a power and communication control unit <b>302</b>.

Communication data received from the portable terminal <b>102</b> having the active type RFID interface is transmitted to the power and communication control unit <b>302</b> via a radio frequency (RF) protocol unit <b>304</b> connected to the antenna <b>220</b> for RFID. A power generation unit <b>305</b> extracts the electric power from an induced electromagnetic field generated near the antenna <b>220</b>, and supplies the electric power to the power and communication control unit <b>302</b>.

The power and communication control unit <b>302</b> performs arbitration processing for power supply and communication input via the I2C interface and the passive type RFID interface. The arbitration processing enables read and write operations without collision in power supply and access processing from both interfaces.

The power and communication control unit <b>302</b> is provided with a password block function for preventing access to a memory <b>303</b> if communication does not conform to the predetermined communication protocol, thus protecting data in the memory <b>303</b>. The memory <b>303</b> is a nonvolatile memory such as an electrically erasable programmable ROM (EEPROM).

In this configuration, even if the digital MFP <b>103</b> enters the power saving mode and the power supply via the I2C is turned OFF, the above-described configuration enables supplying the power by the induced electromagnetic field via the antenna <b>220</b>, thus enabling access to the dual I/F memory <b>219</b> from outside. Specifically, the dual I/F memory <b>219</b> is a storage device wirelessly accessible from an external device such as the portable terminal <b>102</b> even if the power of the digital MFP <b>103</b> is OFF. In the dual I/F memory <b>219</b>, the memory <b>303</b> can be divided into blocks according to the use, and access right via the I2C and RFID can be set for each block, as described below with reference to <figref idrefs="DRAWINGS">FIG. 11</figref>.

(License Validation Processing, Entire Flowchart)

<figref idrefs="DRAWINGS">FIG. 4</figref> is an entire flowchart illustrating license validation processing for the digital MFP <b>103</b> according to the present invention.

In step S<b>401</b>, in response to a user operation, the portable terminal <b>102</b> reads the serial number of the digital MFP <b>103</b> from the dual I/F memory unit <b>218</b> of the digital MFP <b>103</b> via the RFID interface. The serial number is a unique number (individual unit identification information) for identifying an individual unit of the digital MFP <b>103</b>, and is stored before shipment in the dual I/F memory unit <b>218</b> so as to be unchangeable from outside. At this time, the power of the digital MFP <b>103</b> is OFF.

In step S<b>402</b>, the portable terminal <b>102</b> receives a user-input license access number for validating an application from an operation unit (not illustrated) of the portable terminal <b>102</b>. When the user inputs a license access number from the operation unit of the portable terminal <b>102</b>, the portable terminal <b>102</b> acquires the license access number in response to the operation. The license access number (an access number issued for each license) is set to the digital MFP <b>103</b> by the license server. For example, the license access number is supplied together with a shipped product (application) as printed paper, or notified by E-mail to a user who is licensed for the application.

In step S<b>403</b>, the portable terminal <b>102</b> notifies via the network <b>104</b> the license server <b>101</b> of the serial number of the digital MFP <b>103</b> (hereinafter referred to as device serial number) acquired in step S<b>401</b> and the license access number acquired in step S<b>402</b>.

In step S<b>404</b>, the license server <b>101</b> determines whether the serial number and the license access number notified from the portable terminal <b>102</b> in step S<b>403</b> are correct with reference to a database. The license server <b>101</b> stores information in various tables (see <figref idrefs="DRAWINGS">FIGS. 5 to 7</figref>) described below to manage the digital MFP <b>103</b> and applications, and makes the above-described determination based on these pieces of information (details will be described below).

The license server <b>101</b> first determines whether the device serial number is a correct serial number. The license server <b>101</b> further determines that an already existing license access number is not incorrectly used. When the license server <b>101</b> determines that both of these numbers are correct (not used incorrectly), the license server <b>101</b> calculates the license number (issues a license) based on the device serial number and the license access number, generates license data including the calculated license number and information for identifying functions to be used by a relevant application (abbreviated names of specific functions described below), and notifies the portable terminal <b>102</b> of the license data.

In step S<b>405</b>, the portable terminal <b>102</b> stores in the dual I/F memory unit <b>218</b> of the digital MFP <b>103</b> via the RFID interface the license data notified from the license server <b>101</b> in step S<b>404</b>.

When the power of the digital MFP <b>103</b> is turned ON, in step S<b>406</b>, the digital MFP <b>103</b> reads through the I2C bus the data stored in the memory <b>303</b> of the dual I/F memory unit <b>218</b>.

In step S<b>407</b>, the digital MFP <b>103</b> confirms the license data read in step S<b>406</b>.

In step S<b>408</b>, after confirming the license data in step S<b>407</b>, the digital MFP <b>103</b> sets the relevant application by using the confirmed license data to validate the license of the relevant application.

In step S<b>409</b>, the digital MFP <b>103</b> stores in the dual I/F memory unit <b>218</b> the information about the license validated in step S<b>408</b> so that the information can be confirmed from the portable terminal <b>102</b>.

(Device Management Table)

<figref idrefs="DRAWINGS">FIG. 5</figref> illustrates an example device management table managed by the license server <b>101</b>.

The license server <b>101</b> manages the information about the digital MFP <b>103</b> based on the device management table as illustrated in <figref idrefs="DRAWINGS">FIG. 5</figref>. The information in the device management table is stored in a database configured in a storage device (not illustrated), such as the hard disk in the license server <b>101</b>.

As illustrated in <figref idrefs="DRAWINGS">FIG. 5</figref>, the device management table stores a device management number <b>501</b>, a device identifier (ID) <b>502</b>, one or a plurality of function IDs <b>503</b>, and a serial number <b>504</b> for each element.

The device management number <b>501</b> is a unique number assigned to each element of the device management table. The device ID <b>502</b> is unique information assigned to each individual model of the digital MFP <b>103</b>.

The function ID <b>503</b> is unique information assigned to each device function. The function ID <b>503</b> is stored within each element of the device management table. A number of the stored functions is the number provided in a device corresponding to the element. In the present exemplary embodiment, information about a function (for example, the abbreviated name illustrated in <figref idrefs="DRAWINGS">FIG. 8</figref>) is stored as the function ID <b>503</b>.

The serial number <b>504</b> is a unique number for identifying an individual unit of the digital MFP <b>103</b>, corresponding to the serial number read in step S<b>401</b> (see <figref idrefs="DRAWINGS">FIG. 4</figref>). The information managed by the device management table is input in advance by an administrator, or acquired through communication with the digital MFP <b>103</b> via the network <b>104</b> and registered in the database by the license server <b>101</b>.

(Application Management Table)

<figref idrefs="DRAWINGS">FIG. 6</figref> illustrates an example application management table managed by the license server <b>101</b>.

The license server <b>101</b> manages various information about an application based on the application management table as illustrated in <figref idrefs="DRAWINGS">FIG. 6</figref>. The information of the application management table is in a database stored on a storage device (not illustrated), such as the hard disk in the license server <b>101</b>.

As illustrated in <figref idrefs="DRAWINGS">FIG. 6</figref>, the application management table stores an application management number <b>601</b>, an application ID <b>602</b>, one or a plurality of operation codes <b>603</b>, a license access number, <b>604</b>, and a device ID <b>605</b> for each element.

The application management number <b>601</b> is a unique number assigned to each element of the application management table. The application ID <b>602</b> is a unique number assigned to each application. The operation code <b>603</b> indicates a function to be used by the relevant application. The operation code <b>603</b> is defined through a logical operation for specific functions. Specifically, the operation code <b>603</b> is represented by the logical sum of bits corresponding to functions (specific functions illustrated in <figref idrefs="DRAWINGS">FIG. 8</figref>) of the digital MFP <b>103</b> to be validated for the relevant application.

The license access number <b>604</b> is packaged with an application and notified to the user, and corresponds to the license access number input by the user in step S<b>402</b> (see <figref idrefs="DRAWINGS">FIG. 4</figref>). The device ID <b>605</b> is unique information assigned to each individual model for identifying an image forming apparatus adaptable to the relevant application. When there is a plurality of models adaptable to the relevant application, a plurality of device IDs <b>605</b> may be stored in the application management table.

Although not illustrated, the number of licenses permitted by the license access number may also be stored in the application management table. The information managed by the application management table is registered in the database when the license access number is issued.

(Application Management Number)

<figref idrefs="DRAWINGS">FIG. 7</figref> illustrates an example license access number management table managed by the license server <b>101</b>. The license access number management table associates the information of the device management table (see <figref idrefs="DRAWINGS">FIG. 5</figref>) with the information of the application management table (see <figref idrefs="DRAWINGS">FIG. 6</figref>). The license access number management table is in a database stored in a storage device (not illustrated), such as the hard disk in the license server <b>101</b>.

As illustrated in <figref idrefs="DRAWINGS">FIG. 7</figref>, the license access number management table stores a license access number <b>701</b>, one or a plurality of device management numbers <b>702</b>, and an application management number <b>703</b> for each element. The license access number <b>701</b> is identical to the license access number <b>604</b> illustrated in <figref idrefs="DRAWINGS">FIG. 6</figref>. The device management number <b>702</b> is identical to the device management number <b>501</b> illustrated in <figref idrefs="DRAWINGS">FIG. 5</figref>. A plurality of device management numbers <b>702</b> can be stored in each element of the license access number management table. When a plurality of licenses is permitted by one license access number, a plurality of device management numbers <b>702</b> is stored in each element of the license access number management table.

The application management number <b>703</b> is identical to the application management number <b>601</b> illustrated in <figref idrefs="DRAWINGS">FIG. 6</figref>. The license access number <b>701</b> and the application management number <b>703</b> out of the information managed by the license access number management table are registered in the database when the license access number is issued. The device management number <b>702</b> is registered in the database when a license is issued, i.e., when step S<b>911</b> (see <figref idrefs="DRAWINGS">FIG. 9</figref>) described below is executed.

(Functions Set on the Basis of License)

<figref idrefs="DRAWINGS">FIG. 8</figref> illustrates example functions set in the digital MFP <b>103</b> based on license.

As illustrated in <figref idrefs="DRAWINGS">FIG. 8</figref>, the digital MFP <b>103</b> according to the present exemplary embodiment is provided with a scanning function, a print function, a transmission function, a data storage function, an interface function, and a security function as functions based on license (as optional functions).

The scanning function specifically includes a scanning function (abbreviated name SC<b>1</b>). The print function specifically includes two different functions: a 2-color print function (abbreviated name PR<b>1</b>) and a color print function (abbreviated name PR<b>2</b>).

The transmission function specifically includes three different functions: an e-mail transmission function (abbreviated name SD<b>1</b>), a FAX transmission function (abbreviated name SD<b>2</b>), and a USB memory/SD card transmission function (abbreviated name SD<b>3</b>).

The data storage function specifically includes two different functions: an MFP storage function (abbreviated name DA<b>1</b>) and a server storage function (abbreviated name DA<b>1</b>). The interface function specifically includes two different functions: a USB I/F function (abbreviated name IF<b>1</b>) and a card reader function (abbreviated name IF<b>2</b>). The security function specifically includes one function: a storage data encryption function (abbreviated name SR<b>1</b>).

(License Setting Flowchart)

<figref idrefs="DRAWINGS">FIG. 9</figref> is a flowchart illustrating example license setting processing according to the present invention. This flowchart indicates operations of the digital MFP <b>103</b>, the dual I/F memory unit <b>218</b> in the digital MFP <b>103</b>, the portable terminal <b>102</b>, and the license server <b>101</b>.

Processing in steps S<b>914</b>, S<b>915</b>, and S<b>917</b> to S<b>919</b> by the digital MFP <b>103</b> is implemented when the main controller <b>211</b> of the digital MFP <b>103</b> executes a relevant program computer-readably stored in the ROM <b>213</b>. Processing in steps S<b>902</b>, S<b>903</b>, S<b>913</b>, S<b>916</b>, and S<b>920</b> by the dual I/F memory unit <b>218</b> is implemented when the power and communication control unit <b>302</b> of the dual I/F memory unit <b>218</b> executes a relevant program computer-readably stored in an internal storage unit (not illustrated). Processing insteps S<b>901</b>, S<b>904</b>, S<b>905</b>, S<b>912</b>, and S<b>921</b> by the portable terminal <b>102</b> is implemented when a CPU (not illustrated) of the portable terminal <b>102</b> executes a relevant program computer-readably stored in a storage unit (not illustrated) of the portable terminal <b>102</b>. Processing in steps S<b>906</b> to S<b>911</b> by the license server <b>101</b> is implemented when a CPU (not illustrated) of the license server <b>101</b> executes a relevant program computer-readably stored in a storage unit (not illustrated) of the license server <b>101</b>.

Upon detection of a license setting operation input by a user from the operation unit (not illustrated) of the portable terminal <b>102</b>, the CPU of the portable terminal <b>102</b> executes the processing in step S<b>901</b>.

In step S<b>901</b>, the CPU of the portable terminal <b>102</b> accesses the dual I/F memory unit <b>218</b> of the digital MFP <b>103</b> via the RFID. The portable terminal <b>102</b> is an active type RFID, and the dual I/F memory unit <b>218</b> is a passive type RFID.

In step S<b>902</b>, in the dual I/F memory unit <b>218</b>, the antenna <b>220</b> receives an access from the portable terminal <b>102</b> (an active type RFID), the power generation unit <b>305</b> generates the power, and the power and communication control unit <b>302</b> receive a request (signal) from the portable terminal <b>102</b>.

In step S<b>903</b>, in response to the request (a request for reading the serial number) from the portable terminal <b>102</b>, the power and communication control unit <b>302</b> of the dual I/F memory <b>219</b> reads the serial number of the digital MFP <b>103</b> from memory block “<b>0</b>” of the memory <b>303</b> (see <figref idrefs="DRAWINGS">FIG. 11</figref>) and then notifies the portable terminal <b>102</b> of the serial number via the RFID.

In step S<b>904</b>, the CPU of the portable terminal <b>102</b> receives (acquires) the serial number of the digital MFP <b>103</b> from the dual I/F memory unit <b>218</b> via the RFID.

In step S<b>905</b>, the CPU of the portable terminal <b>102</b> receives from the operation unit (not illustrated) of the portable terminal <b>102</b> the license access number packaged with an application and input by the user. Upon detection of a license access number input by the user from the operation unit, the CPU of the portable terminal <b>102</b> executes processing for notifying the license server <b>101</b> of the serial number and the license access number. In this notification processing, the CPU of the portable terminal <b>102</b> notifies, via the network <b>104</b>, the license server <b>101</b> of the serial number of the digital MFP <b>103</b> acquired in step S<b>904</b> and the input license access number.

In step S<b>906</b>, the CPU of the license server <b>101</b> confirms in the device management table (see <figref idrefs="DRAWINGS">FIG. 5</figref>) the serial number received from the portable terminal <b>102</b>. In this step, specifically, the CPU of the license server <b>101</b> searches for the received serial number in the serial number list in the device management table to confirm whether the serial number is registered in the list. If the received serial number is not registered in the license server <b>101</b>, the CPU of the license server <b>101</b> executes error processing, notifies the portable terminal <b>102</b> of the relevant error, and terminates the processing of this flowchart (not illustrated). Otherwise, if the received serial number is confirmed to be registered in the license server <b>101</b>, the CPU of the license server <b>101</b> identifies an element of the device management table of which the serial number has been confirmed, and advances processing to step S<b>907</b>.

In step S<b>907</b>, the CPU of the license server <b>101</b> acquires the device ID <b>502</b> and the device management number <b>501</b> from the element of the device management table identified in step S<b>906</b>.

In step S<b>908</b>, the CPU of the license server <b>101</b> confirms the application management table (see <figref idrefs="DRAWINGS">FIG. 6</figref>) based on the license access number received from the above-described portable terminal <b>102</b>. In this step, specifically, the CPU of the license server <b>101</b> searches for the received license access number in the license access number list in the application management table to confirm whether the license access number is registered in the list. If the received license access number is not registered in the license server <b>101</b>, the CPU of the license server <b>101</b> executes error processing, notifies the portable terminal <b>102</b> of the relevant error, and terminates the processing of this flowchart (not illustrated). Otherwise, if the received license access number is confirmed to be registered in the license server <b>101</b>, the CPU of the license server <b>101</b> identifies an element of the application management table of which the license access number has been confirmed, and advances processing to step S<b>909</b>.

In step S<b>909</b>, the CPU of the license server <b>101</b> acquires the application ID <b>602</b>, the application management number <b>601</b>, the operation code <b>603</b>, and the device ID <b>605</b> based on the element of the application management table identified in step S<b>908</b>.

In step S<b>910</b>, the CPU of the license server <b>101</b> confirms a relation between the device ID <b>502</b> acquired in step S<b>907</b> and the application ID <b>602</b> acquired in step S<b>909</b>. In this step, specifically, the CPU of the license server <b>101</b> confirms whether the device ID <b>502</b> acquired in step S<b>907</b> is associated with the application ID <b>602</b> acquired in step S<b>909</b> in the application management table (see <figref idrefs="DRAWINGS">FIG. 6</figref>), i.e., whether the device ID <b>502</b> is included in the device ID <b>605</b>). If the device ID <b>502</b> is not associated with the application ID <b>602</b>, the CPU of the license server <b>101</b> executes error processing, notifies the portable terminal <b>102</b> of the relevant error, and terminates the processing of this flowchart (not illustrated). Otherwise, if the device ID <b>502</b> is confirmed to be associated with the application ID <b>602</b>, the CPU of the license server <b>101</b> identifies the confirmed element of the application management table, and advances processing to step S<b>911</b>.

In step S<b>911</b>, the CPU of the license server <b>101</b> calculates the license number (issues a license) by using the above-described serial number and the license access number received from the portable terminal <b>102</b>, and transmits to the portable terminal <b>102</b> via the network <b>104</b> license data including the abbreviated names of the specific functions (for example, SC<b>1</b> and PR<b>1</b> illustrated in <figref idrefs="DRAWINGS">FIG. 8</figref>) corresponding to the operation code <b>603</b> acquired in step S<b>909</b>. In step S<b>911</b>, the CPU of the license server <b>101</b> also executes processing for registering the device management number <b>501</b> acquired in step S<b>907</b> in an element of the license access management table (see <figref idrefs="DRAWINGS">FIG. 7</figref>) corresponding to the above-described received license access number.

In step S<b>912</b>, upon reception of the license data transmitted from the license server <b>101</b> via the network <b>104</b>, the CPU of the portable terminal <b>102</b> stores in the dual I/F memory <b>219</b> via the RFID an instruction for validating the specific functions included in the license data, the serial number acquired in step S<b>904</b>, and the license number included in the above-described license data. For example, the CPU of the portable terminal <b>102</b> stores data (“SD<b>2</b> validated, license access number, license number”, and “IF<b>1</b> validated, license access number, license number”) in memory block “<b>2</b>” (see <figref idrefs="DRAWINGS">FIG. 11</figref>) described below.

In step S<b>913</b>, the power and communication control unit <b>302</b> of the dual I/F memory unit <b>218</b> stores in memory block “<b>2</b>” of the memory <b>303</b> of the dual I/F memory <b>219</b> such information as the license data to be stored from the portable terminal <b>102</b> by instruction via the RFID. Since the power is generated by electromagnetic induction in the dual I/F memory unit <b>218</b> and supplied to the dual I/F memory <b>219</b> in response to a storage access from the portable terminal <b>102</b>, the license data can be stored in the memory <b>303</b> even in a state where the power of the digital MFP <b>103</b> is OFF.

Executing the processing in steps S<b>901</b> to S<b>913</b> or the processing in steps S<b>905</b> to S<b>913</b> for a plurality of license access numbers enables storing in the dual I/F memory unit <b>218</b> of the digital MFP <b>103</b> a plurality of license data corresponding to the plurality of license access numbers even in the power OFF state. In step S<b>905</b>, the CPU of the portable terminal <b>102</b> may receive a plurality of input license access numbers and transmit the plurality of received license access numbers to the license server <b>101</b>. In this case, the license server <b>101</b> executes the processing in steps S<b>908</b> to S<b>911</b> for each license access number.

In step S<b>914</b>, an operator presses a power switch (not illustrated) of the digital MFP <b>103</b> to turn ON the power of the digital MFP <b>103</b>. When the main controller <b>211</b> starts activation processing according to a program stored in the ROM <b>213</b>, the main controller <b>211</b> advances processing to step S<b>915</b>.

In step S<b>915</b>, according to an activation program executed when the power of the controller unit <b>201</b> is turned ON, the main controller <b>211</b> reads data from the memory <b>303</b> of the dual I/F memory unit <b>218</b> via the I2C bus and stores the data in the RAM <b>212</b>.

In step S<b>916</b>, in response to an access via the I2C bus, the power and communication control unit <b>302</b> of the dual I/F memory unit <b>218</b> reads the data from the memory <b>303</b> and transmits it to the I/O controller <b>215</b>.

In step S<b>917</b>, the main controller <b>211</b> compares the license data (see <figref idrefs="DRAWINGS">FIG. 10</figref>) stored in the HDD <b>216</b> of the digital MFP <b>103</b> with the license data read from the dual I/F memory unit <b>218</b> of the digital MFP <b>103</b> to confirm update data.

The license data stored in the HDD <b>216</b> of the digital MFP <b>103</b> is specifically stored in the license database (see <figref idrefs="DRAWINGS">FIG. 10</figref>) described below. The main controller <b>211</b> compares the data in the license database with the above-described license data read from the dual I/F memory unit <b>218</b> to confirm whether there is update data. If there is no update data, the main controller <b>211</b> terminates the processing of this flowchart (not illustrated). Otherwise, if there is update data, the main controller <b>211</b> advances processing to step S<b>918</b>.

In step S<b>918</b>, the main controller <b>211</b> validates the license according to the update data, decompresses the compressed data stored in the HDD <b>216</b> to install a program corresponding to the license, and activates the program. The main controller <b>211</b> stores in a record corresponding to the update data in the license database in the HDD <b>216</b> the license access number and the license number included in the update data, and sets the valid/invalid status field to “VALID”, thus validating the license.

In step S<b>919</b>, the main controller <b>211</b> confirms whether the program validated and activated in step S<b>918</b> is normally operating. When the main controller <b>211</b> determines that the program is normally operating, the main controller <b>211</b> updates the operating status of the record corresponding to the license data to “NORMAL”, and stores in the dual I/F memory unit <b>218</b> via the I2C bus the information about the license which has been confirmed to be validated (valid license information). In this case, the main controller <b>211</b> deletes via the I2C bus the license data in the memory <b>303</b> of the dual I/F memory unit <b>218</b> confirmed in step S<b>917</b>.

Otherwise, when the main controller <b>211</b> determines that the program is not normally operating, the main controller <b>211</b> may execute error processing, invalidate the corresponding license, and store information about the invalidated license in the dual I/F memory unit <b>218</b> via the I2C bus (not illustrated).

In step S<b>920</b>, the power and communication control unit <b>302</b> of the dual I/F memory unit <b>218</b> stores in memory block “<b>1</b>” of the memory <b>303</b> of the dual I/F memory <b>219</b> the above-described valid license information to be stored by instruction via the I2C bus. For example, the power and communication control unit <b>302</b> stores data (“SC<b>1</b> valid”, “PR<b>1</b> valid”, “SD<b>1</b> valid”, and “DA<b>1</b> valid”) in memory block “<b>1</b>” (see <figref idrefs="DRAWINGS">FIG. 11</figref>) described below. The power and communication control unit <b>302</b> delete from memory block “<b>2</b>” of the memory <b>303</b> of the dual I/F memory <b>219</b> the license data to be deleted by instruction via the I2C bus.

In step S<b>921</b>, the CPU of the portable terminal <b>102</b> accesses the dual I/F memory <b>219</b>, reading via the RFID to acquire and confirm the above-described valid license information.

Although not illustrated in the above-described flowchart, error detection processing is executed in each processing. If an error is detected, retry processing is executed a predetermined number of times. If an error continues, error processing is executed and processing is terminated.

(License Data)

<figref idrefs="DRAWINGS">FIG. 10</figref> illustrates an example configuration of the license database stored in the HDD <b>216</b>.

One record of the license data stored in the HDD <b>216</b> of the digital MFP <b>103</b> corresponds to one specific function. Specifically, each record includes data of a function name, a specific function, and an abbreviated name illustrated in <figref idrefs="DRAWINGS">FIG. 8</figref>. When validating the license for each specific function, the license access number packaged with an application and the license number issued by the license server <b>101</b> are input and stored in the corresponding record. The valid/invalid status of the license is also input as data and stored in the corresponding record. When the license is normally operating, data indicating “normal” is input in the operating status field and stored in the corresponding record. As long as the present exemplary embodiment can be implemented, the table configuration is not limited to that illustrated in <figref idrefs="DRAWINGS">FIG. 10</figref>. The license access number may not be stored, and information about the date of license validation may be additionally stored.

(Dual I/F Memory Data)

<figref idrefs="DRAWINGS">FIG. 11</figref> illustrates an example configuration of access rights and data stored in each block of the dual I/F memory <b>219</b>.

In the dual I/F memory <b>219</b>, under control of the main controller <b>211</b> via the I2C bus, areas in the memory <b>303</b> can be handled as memory blocks through merge and division processing. Referring to <figref idrefs="DRAWINGS">FIG. 11</figref>, the memory <b>303</b> is divided into four memory blocks (storage areas) “<b>0</b>” to “<b>3</b>.” However, the number of memory blocks is not limited to four.

The main controller <b>211</b> can set an access right for each memory block via the I2C bus. Specifically, the main controller <b>211</b> can set the right to access (right to read/right to write) via the I2C and the right to access via the RFID for each memory block.

Referring to <figref idrefs="DRAWINGS">FIG. 11</figref>, as the right to access via the I2C, both the right to read and the right to write are set for all memory blocks “<b>0</b>” to “<b>3</b>.” As the right to access via the RFID, only the right to read is set for memory blocks “<b>0</b>” and “<b>1</b>”, and both the right to read and the right to write are set for memory blocks “<b>2</b>” and “<b>3</b>.”

In memory block “<b>0</b>”, for example, by the time of shipment of the digital MFP <b>103</b>, the serial number of the digital MFP <b>103</b> is stored via the I2C so as to be unchangeable from outside. Specifically, the serial number in memory block “<b>0</b>” is read in step S<b>903</b> (see <figref idrefs="DRAWINGS">FIG. 9</figref>).

In memory block “<b>1</b>”, information about valid licenses for the digital MFP <b>103</b> (valid license information) is to be stored via the I2C so as to be confirmable from outside.

Memory block “<b>2</b>” is a block for storing data (license data) of the license validated via the RFID. When making license setting, the abbreviated name of the license, the license access number, and the license number are stored in memory block “<b>2</b>.”

Specifically, as illustrated in <figref idrefs="DRAWINGS">FIG. 9</figref>, the license data is stored in memory block “<b>2</b>” in step S<b>913</b> and read instep S<b>916</b>, and the information about the license validated based on the license data is stored in memory block “<b>1</b>” in step S<b>920</b> and confirmed in step S<b>921</b>. When storing the valid license information in memory block “<b>1</b>”, the main controller <b>211</b> deletes the license data in memory block “<b>2</b>.”

The main controller <b>211</b>, via the I2C bus, may make setting of the dual I/F memory <b>219</b> before the power of the digital MFP <b>103</b> is turned OFF under predetermined conditions, so that memory block “<b>2</b>” is writable from an external device while the power of the digital MFP <b>103</b> is OFF.

(License Deleting Flowchart)

Procedures for canceling a set license and deleting an unnecessary license will be described below with reference to <figref idrefs="DRAWINGS">FIG. 12</figref>.

<figref idrefs="DRAWINGS">FIG. 12</figref> is a flowchart illustrating example license deletion processing according to the present invention. This flowchart illustrates operations of the digital MFP <b>103</b>, the dual I/F memory unit <b>218</b> of the digital MFP <b>103</b>, the portable terminal <b>102</b>, and the license server <b>101</b>.

Processing in steps S<b>1210</b>, S<b>1211</b>, S<b>1213</b> to S<b>1215</b> in the digital MFP <b>103</b> is implemented by the main controller <b>211</b> of the digital MFP <b>103</b> executing a relevant program computer-readably stored in the ROM <b>213</b>. Processing in steps S<b>1202</b>, S<b>1203</b>, S<b>1205</b>, S<b>1209</b>, S<b>1212</b> and S<b>1216</b> in the dual I/F memory unit <b>218</b> is implemented by the power and communication control unit <b>302</b> of the dual I/F memory unit <b>218</b> executing a relevant program computer-readably stored in an internal storage unit (not illustrated). Processing in steps S<b>1201</b>, S<b>1204</b>, S<b>1206</b> to S<b>1208</b>, S<b>1217</b>, S<b>1218</b> and S<b>1222</b> in the portable terminal <b>102</b> is implemented by the CPU (not illustrated) of the portable terminal <b>102</b> executing a relevant program computer-readably stored in the storage unit (not illustrated) of the portable terminal <b>102</b>. Processing in steps S<b>1219</b> to S<b>1221</b> in the license server <b>101</b> is implemented by the CPU (not illustrated) of the license server <b>101</b> executing a relevant program computer-readably stored in the storage unit (not illustrated) of the license server <b>101</b>.

Upon detection of a license deletion operation input by a user from the operation unit (not illustrated) of the portable terminal <b>102</b>, the CPU of the portable terminal <b>102</b> executes the processing in step S<b>1201</b>.

In step S<b>1201</b>, the CPU of the portable terminal <b>102</b> accesses the dual I/F memory unit <b>218</b> of the digital MFP <b>103</b> via the RFID to issue a request. The portable terminal <b>102</b> is an active type RFID, and the dual I/F memory unit <b>218</b> is a passive type RFID.

In step S<b>1202</b>, in the dual I/F memory unit <b>218</b>, the internal antenna <b>220</b> receives an access from the portable terminal <b>102</b> (an active type RFID), the power generation unit <b>305</b> generates the power, and the power and communication control unit <b>302</b> receives the request (signal) from the portable terminal <b>102</b>.

In step S<b>1203</b>, in response to the request (a request for reading the serial number) from the portable terminal <b>102</b>, the power and communication control unit <b>302</b> of the dual I/F memory <b>219</b> reads the serial number of the digital MFP <b>103</b> from memory block “<b>0</b>” of the memory <b>303</b> (see <figref idrefs="DRAWINGS">FIG. 11</figref>), and notifies the portable terminal <b>102</b> of the serial number via the RFID.

In step S<b>1204</b>, the CPU of the portable terminal <b>102</b> receives (acquires) the serial number of the digital MFP <b>103</b> from the dual I/F memory unit <b>218</b> via the RFID.

In step S<b>1205</b>, in response to the request (a request for reading information about the licenses set to the digital MFP <b>103</b>) from the portable terminal <b>102</b>, the power and communication control unit <b>302</b> of the dual I/F memory <b>219</b> reads information about the licenses set to the digital MFP <b>103</b> from memory block “<b>1</b>” of the memory <b>303</b> (see <figref idrefs="DRAWINGS">FIG. 11</figref>), and notifies the portable terminal <b>102</b> of the information via the RFID. Specifically, the power and communication control unit <b>302</b> reads information about valid licenses (valid license information) in the digital MFP <b>103</b> stored in memory block “<b>1</b> of the memory <b>303</b> (see <figref idrefs="DRAWINGS">FIG. 11</figref>), and notifies the portable terminal <b>102</b> of the information via the RFID.

In step S<b>1206</b>, the CPU of the portable terminal <b>102</b> receives (acquires) information about the licenses set in the digital MFP <b>103</b> from the dual I/F memory unit <b>218</b> via the RFID, and displays the information on a display (not illustrated) of the portable terminal <b>102</b> to present the information to the user for confirmation.

In step S<b>1207</b>, the CPU of the portable terminal <b>102</b> receives from the operation unit (not illustrated) of the portable terminal <b>102</b> a user-selected license to be deleted out of the licenses displayed in step S<b>1206</b>. Upon detection of a user-selected license to be deleted from the operation unit, the CPU of the portable terminal <b>102</b> advances processing to step S<b>1208</b>. If a user input for canceling the processing is received from the operation unit, the CPU of the portable terminal <b>102</b> terminates the processing of this flowchart (not illustrated).

In step S<b>1208</b>, the CPU of the portable terminal <b>102</b> stores in the dual I/F memory <b>219</b> via the RFID the license data subject to deletion including the abbreviated name and invalidation setting of the function corresponding to the license to be deleted selected in step S<b>1207</b>.

In step S<b>1209</b>, the power and communication control unit <b>302</b> of the dual I/F memory unit <b>218</b> stores in memory block “<b>2</b>” of the memory <b>303</b> of the dual I/F memory <b>219</b> the license data subject to deletion specified to be deleted from the portable terminal <b>102</b> via the RFID. For example, the power and communication control unit <b>302</b> stores such information as “SC<b>1</b> invalidated” and “PR<b>1</b> invalidated” in memory block “<b>2</b>” (see FIG. <b>11</b>) as license data subject to deletion.

In step S<b>1210</b>, the operator presses the power switch (not illustrated) of the digital MFP <b>103</b> to turn ON the power of the digital MFP <b>103</b>. When the main controller <b>211</b> starts the activation processing according to the program stored in the ROM <b>213</b>, the main controller <b>211</b> advances processing to step S<b>1211</b>.

In step S<b>1211</b>, according to the activation program executed when the power of the controller unit <b>201</b> is turned ON, the main controller <b>211</b> reads data (including the above-described license data subject to deletion) from the memory <b>303</b> of the dual I/F memory unit <b>218</b> via the I2C bus and stores the data in the RAM <b>212</b>. Then, the main controller <b>211</b> confirms whether the license data subject to deletion is included in the data.

In step S<b>1212</b>, in response to an access via the I2C bus, the power and communication control unit <b>302</b> of the dual I/F memory unit <b>218</b> reads the data (including the above-described license data subject to deletion) in the memory <b>303</b> and transmits it to the I/O controller <b>215</b>.

In step S<b>1213</b>, based on the above-described license data subject to deletion, the main controller <b>211</b> displays information about the license to be deleted (for example, the function name and specific functions as illustrated in <figref idrefs="DRAWINGS">FIG. 10</figref>) on the operation unit <b>204</b> and receives from the operation unit <b>204</b> a user-input confirmation for deletion. Then, upon reception of a user-input confirmation for deletion from the operation unit <b>204</b>, the main controller <b>211</b> advances processing to step S<b>1214</b>. If a user input is received specifying that the license is not to be deleted, the main controller <b>211</b> terminates the processing of this flowchart (not illustrated).

In step S<b>1214</b>, the main controller <b>211</b> deletes the license. Specifically, the main controller <b>211</b> deletes the installed relevant program.

In step S<b>1215</b>, the main controller <b>211</b> makes sure that the program deleted in step S<b>1214</b> cannot be actually executed, deletes the license access number, the license number, and the information about the operating status from a corresponding record in the license database (see <figref idrefs="DRAWINGS">FIG. 10</figref>), and changes the valid/invalid status of the license to “INVALID.” In this case, the main controller <b>211</b> stores the license access number to be deleted in the RAM <b>212</b>, and stores in the dual I/F memory unit <b>218</b> via the I2C bus the information about the license which has been confirmed to be deleted (license deletion information including the license access number). In this case, the main controller <b>211</b> further deletes via the I2C bus the above-described license data subject to deletion stored in the memory <b>303</b> of the dual I/F memory unit <b>218</b> confirmed in step S<b>1213</b>.

In step S<b>1216</b>, the power and communication control unit <b>302</b> of the dual I/F memory unit <b>218</b> stores in memory block “<b>1</b>” of the memory <b>303</b> of the dual I/F memory <b>219</b> the above-described license deletion information specified to be stored via the I2C bus. For example, the power and communication control unit <b>302</b> stores such information as “SC<b>1</b> invalid, license access number”, “PR<b>1</b> invalid, license access number” in memory block “<b>1</b>” (see <figref idrefs="DRAWINGS">FIG. 11</figref>) as the license deletion information. The power and communication control unit <b>302</b> further deletes from memory block “<b>2</b>” of the memory <b>303</b> of the dual I/F memory <b>219</b> the license data subject to deletion specified via the I2C bus.

In step S<b>1217</b>, the CPU of the portable terminal <b>102</b> accesses the dual I/F memory <b>219</b> to read via the RFID and acquire the above-described license deletion information, and displays the information on the display (not illustrated) of the portable terminal <b>102</b> to present the information to the user.

In step S<b>1218</b>, after confirming that the license of the digital MFP <b>103</b> has been deleted, the CPU of the portable terminal <b>102</b> notifies the license server <b>101</b> of the above-described license deletion information and the device serial number acquired in step S<b>1204</b>.

In step S<b>1219</b>, the CPU of the license server <b>101</b> confirms using the device management table (see <figref idrefs="DRAWINGS">FIG. 5</figref>) and the license access management table (see <figref idrefs="DRAWINGS">FIG. 7</figref>) the license access number and serial number included in the license deletion information received from the portable terminal <b>102</b>. In this step, specifically, the CPU of the license server <b>101</b> searches for the received serial number in the serial number list in the device management table (see <figref idrefs="DRAWINGS">FIG. 5</figref>) to acquire the device management number of the element in which the received serial number is registered. The CPU of the license server <b>101</b> further searches for the license access number in the license access number list in the license access management table (see <figref idrefs="DRAWINGS">FIG. 7</figref>) to confirm the element in which the received license access number is registered. Then, the CPU of the license server <b>101</b> confirms whether the device management number acquired from the above-described device management table is included in the device management number of the element.

In step S<b>1220</b>, the CPU of the license server <b>101</b> deletes the confirmed device management number from the element in the license access management table (see <figref idrefs="DRAWINGS">FIG. 7</figref>) confirmed in step S<b>1219</b>.

In step S<b>1221</b>, the CPU of the license server <b>101</b> transmits to the portable terminal <b>102</b> a notification (a license deletion completion notification) notifying that the license deletion processing is completed.

In step S<b>1222</b>, upon reception of the license deletion completion notification transmitted from the license server <b>101</b> via the network <b>104</b>, the CPU of the portable terminal <b>102</b> displays a message indicating that the license deletion processing is completed on the display (not illustrated) of the portable terminal <b>102</b>.

As described above, the present invention enables storing license data in the dual I/F memory unit <b>218</b> from the external portable terminal <b>102</b> via the RFID even when the power of the digital MFP <b>103</b> is OFF. Then, when the power of the digital MFP <b>103</b> is turned ON, the digital MFP <b>103</b> can read the license data from the dual I/F memory unit <b>218</b> and validate the corresponding license. This remarkably improves the operability in license setting and shortens the time of license validation.

Further, even when the power of the digital MFP <b>103</b> is OFF, the license data subject to deletion can be stored in the dual I/F memory unit <b>218</b> from the external portable terminal <b>102</b> via the RFID. Then, when the power of the digital MFP <b>103</b> is turned ON, the digital MFP <b>103</b> can read the license data subject to deletion from the dual I/F memory unit <b>218</b> and delete the corresponding license. This remarkably improves the operability in license deletion and shortens the time of license deletion.

The above-described configuration enables setting and deleting a license from outside even when the power of an image forming apparatus is OFF, thus shortening an operation time for installing and deleting an application to/from the image forming apparatus, and improving the operability in license setting and license deletion.

While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all modifications, equivalent structures, and functions.

This application claims priority from Japanese Patent Application No. 2011-191186 filed Sep. 2, 2011, which is hereby incorporated by reference herein in its entirety.