U.S. patent application number 14/332579 was filed with the patent office on 2014-11-13 for information processing apparatus, system management method, and recording medium.
This patent application is currently assigned to RICOH COMPANY, LTD.. The applicant listed for this patent is Noriaki Nakagawa. Invention is credited to Noriaki Nakagawa.
Application Number | 20140338005 14/332579 |
Document ID | / |
Family ID | 43428474 |
Filed Date | 2014-11-13 |
United States Patent
Application |
20140338005 |
Kind Code |
A1 |
Nakagawa; Noriaki |
November 13, 2014 |
INFORMATION PROCESSING APPARATUS, SYSTEM MANAGEMENT METHOD, AND
RECORDING MEDIUM
Abstract
In an information processing apparatus, software is installed to
build a system providing a predetermined function. The information
processing apparatus includes a generating unit configured to
generate system identification information for identifying the
system built by installing the software, the system identification
information being generated from authentication information
obtained by performing license authentication on the software; and
a registering unit configured to send the system identification
information generated by the generating unit to a management device
that manages a plurality of the systems via a predetermined data
transmission line, to register the system identification
information in the management device as management information.
Inventors: |
Nakagawa; Noriaki;
(Kanagawa, JP) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Nakagawa; Noriaki |
Kanagawa |
|
JP |
|
|
Assignee: |
RICOH COMPANY, LTD.
Tokyo
JP
|
Family ID: |
43428474 |
Appl. No.: |
14/332579 |
Filed: |
July 16, 2014 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
12825748 |
Jun 29, 2010 |
8819854 |
|
|
14332579 |
|
|
|
|
Current U.S.
Class: |
726/30 |
Current CPC
Class: |
G06F 21/105 20130101;
G06F 21/73 20130101; H04L 63/12 20130101; G06F 2221/0768 20130101;
G06F 2221/0735 20130101; G06F 21/121 20130101; G06F 21/10 20130101;
H04L 63/0428 20130101; G11B 20/00086 20130101 |
Class at
Publication: |
726/30 |
International
Class: |
G06F 21/12 20060101
G06F021/12; G06F 21/10 20060101 G06F021/10 |
Foreign Application Data
Date |
Code |
Application Number |
Jul 8, 2009 |
JP |
2009-162169 |
Claims
1-20. (canceled)
21. A device management apparatus in which software is installed to
build a system providing a predetermined function, the device
management apparatus comprising: a generating unit configured to
generate system identification information for identifying the
system built by installing the software, the system identification
information being generated from authentication information
obtained by performing license authentication on the software; a
registration request generating unit configured to generate a
registration request to be registered in a remote management device
connected via a network, based on at least the system
identification information generated by the generating unit; and a
sending unit configured to send the registration request generated
by the registration request generating unit, to the remote
management device.
22. The device management apparatus according to claim 21, wherein
the registration request generating unit generates the registration
request, in which the system identification information, and
registration request identification information by which the remote
management device can identify the registration request using the
system identification information, are associated with each
other.
23. The device management apparatus according to claim 22, wherein
the registration request generating unit associates the system
identification information and the registration request
identification information, by defining in data described in a
predetermined structured description language.
24. The device management apparatus according to claim 21, wherein
the registration request generating unit generates the registration
request, in which the system identification information, and device
identification information by which the remote management device
can identify a device having the system identification information,
are associated with each other.
25. The device management apparatus according to claim 24, wherein
the registration request generating unit associates the system
identification information and the device identification
information, by defining in data described in a predetermined
structured description language.
26. The device management apparatus according to claim 21, wherein
the registration request generating unit generates the registration
request, in which the system identification information,
registration request identification information by which the remote
management device can identify the registration request using the
system identification information, and device identification
information by which the remote management device can identify a
device having the system identification information, are associated
with each other.
27. The device management apparatus according to claim 26, wherein
the registration request generating unit associates the system
identification information, the registration request identification
information and the device identification information, by defining
in data described in a predetermined structured description
language.
28. A device management method performed by a device management
apparatus in which software is installed to build a system
providing a predetermined function, the device management method
comprising: generating system identification information for
identifying the system built by installing the software, the system
identification information being generated from authentication
information obtained by performing license authentication on the
software; generating a registration request to be registered in a
remote management device connected via a network, based on at least
the generated system identification information; and sending the
generated registration request to the remote management device.
Description
BACKGROUND OF THE INVENTION
[0001] 1. Field of the Invention
[0002] The present invention relates to an information processing
apparatus connected to an internal system built in a local area,
and more particularly, to a technology of identifying and managing
a system built by installing software in an information processing
apparatus, from an external system.
[0003] 2. Description of the Related Art
[0004] With the advancement of the information processing
technology such as network communications, there is known a
technology of remotely managing an internal system built in a local
area, from an external system.
[0005] For example, patent document 1 (Japanese Laid-Open Patent
Application No. 2008-35444) discloses a system environment
including one or more management target systems and a remote
management system for remotely managing the management target
systems via the Internet. The management target system may be a
device management system for managing image processing apparatuses
such as an MFP (multifunction peripheral) and a printer, via a
predetermined data transmission line, as described in patent
document 2 (Japanese Laid-Open Patent Application No. 2005-182701).
The device management system manages the image processing apparatus
that is a management target, with the use of a device management
apparatus having device management functions such as collecting
information from the image processing apparatus and updating the
software of the image processing apparatus.
[0006] In such a system environment, manufacturers can provide
various support services to devices installed in a user
environment.
[0007] However, the conventional system does not consider a method
of building systems by providing users with only software for
implementing the device management functions, and installing the
software in existing information processing apparatuses that are
already provided in the user environments.
[0008] In the remote management system, device management systems
installed in the user environments need to be identified, for the
purpose managing the management target systems. For this reason,
manufacturers provide users with device management apparatuses, and
identify the installed device management systems based on
information unique to each device management apparatus for example,
a "serial number" or a "MAC address"). That is to say, the
conventional system is based on the premise that device management
apparatuses are installed in user environments to build device
management systems.
[0009] However, in recent years and continuing, user environments
are typically already provided with information processing
apparatuses that have sufficient processing capabilities for
implementing device management functions. In such a case, the user
environment does not need to have a new apparatus provided from the
manufacturer to implement such functions; the user environment only
needs to be provided with the software for implementing the
functions.
[0010] When device management systems are built by providing only
software to user environments, the manufacture needs to provide
software including information that can be used by the remote
management system to identify the device management system built in
the user environment. However, there is a vast variety of methods
for providing software, such as distributing the software in
various types of recording media or downloading the software. Thus,
it is unrealistic for the manufacturer to provide software
including information that can be used by the remote management
system to identify the device management system.
SUMMARY OF THE INVENTION
[0011] The present invention provides an information processing
apparatus, a system management method, and a recording medium, in
which one or more of the above-described disadvantages are
eliminated.
[0012] A preferred embodiment of the present invention provides an
information processing apparatus, a system management method, and a
recording medium, with which a system, which is built by installing
software into an apparatus, can be identified from a remote
external system.
[0013] According to an aspect of the present invention, there is
provided an information processing apparatus in which software is
installed to build a system providing a predetermined function, the
information processing apparatus including a generating unit
configured to generate system identification information for
identifying the system built by installing the software, the system
identification information being generated from authentication
information obtained by performing license authentication on the
software; and a registering unit configured to send the system
identification information generated by the generating unit to a
management device that manages a plurality of the systems via a
predetermined data transmission line, to register the system
identification information in the management device as management
information.
[0014] According to an aspect of the present invention, there is
provided a system management method performed by an information
processing apparatus in which software is installed to build a
system providing a predetermined function, the system management
method including a generating step of generating system
identification information for identifying the system built by
installing the software, the system identification information
being generated from authentication information obtained by
performing license authentication on the software; and a
registering step of sending the system identification information
generated at the generating step to a management device that
manages a plurality of the systems via a predetermined data
transmission line, to register the system identification
information in the management device as management information.
[0015] According to an aspect of the present invention, there is
provided a computer-readable recording medium that stores therein a
system management program that causes a computer to execute a
procedure in an information processing apparatus in which software
is installed to build a system providing a predetermined function,
the procedure including a generating step of generating system
identification information for identifying the system built by
installing the software, the system identification information
being generated from authentication information obtained by
performing license authentication on the software; and a
registering step of sending the system identification information
generated at the generating step to a management device that
manages a plurality of the systems via a predetermined data
transmission line, to register the system identification
information in the management device as management information.
[0016] According to one embodiment of the present invention, an
information processing apparatus, a system management method, and a
recording medium are provided, with which a system, which is built
by installing software into an apparatus, can be identified from a
remote external system.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Other objects, features and advantages of the present
invention will become more apparent from the following detailed
description when read in conjunction with the accompanying
drawings, in which:
[0018] FIG. 1 illustrates a device management system according to
an embodiment of the present invention;
[0019] FIG. 2 illustrates a hardware configuration of a device
management apparatus according to an embodiment of the present
invention;
[0020] FIG. 3 illustrates a software configuration of the device
management apparatus according to an embodiment of the present
invention;
[0021] FIG. 4 illustrates a functional configuration of the device
management apparatus according to an embodiment of the present
invention;
[0022] FIG. 5 illustrates an example of data for managing license
codes according to an embodiment of the present invention;
[0023] FIGS. 6A and 6B are for describing the operation of
generating system identification information according to an
embodiment of the present invention;
[0024] FIGS. 7A and 7B illustrate an example of data used for
remote system management according to an embodiment of the present
invention;
[0025] FIG. 8 is a sequence diagram of a process of issuing/saving
a license code according to an embodiment of the present invention;
and
[0026] FIG. 9 is a sequence diagram of a process of system
registration according to an embodiment of the present
invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0027] A description is given, with reference to the accompanying
drawings, of embodiments of the present invention.
[0028] <System Configuration>
[0029] FIG. 1 illustrates a device management system 1 according to
an embodiment of the present invention.
[0030] As shown in FIG. 1, the device management system 1 includes
one or more image processing apparatuses (management target
devices) 200 (hereinafter, "devices 200") and a device management
apparatus 100, which are connected to each other via an internal
network N such as LAN (Local Area Network).
[0031] The device management system 1 is connected to a remote
management system 2 via an external network I such as the Internet.
The remote management system 2 includes a license authentication
apparatus (activation server) 300 and a remote management apparatus
(center server) 400, which are connected to each other by an
internal network N. The device management system 1 and the remote
management system 2 are typically connected to the external network
I via firewall (not shown).
[0032] In such a system configuration, the device management
apparatus 100 monitors/manages the devices 200 based on device
information (for example, "operation status information") obtained
from the devices 200. The remote management apparatus 400 collects
device information of the devices 200 obtained by the device
management apparatus 100, and remotely manages the devices 200 by
providing support services such as maintenance and operations. The
device management apparatus 100 manages various software items
installed in the devices 200 by sending, to the license
authentication apparatus 300, license authentication requests
(activation) for software (function implementation program) to be
operated in the devices 200.
[0033] In the following descriptions, the device management system
1 built in the user environment corresponds to an internal system,
and the remote management system 2 built at the manufacturer
corresponds to an external system.
[0034] <Hardware Configuration>
[0035] Next, a description is given of a hardware configuration of
the device management apparatus 100 according to the present
embodiment.
[0036] FIG. 2 illustrates a hardware configuration of the device
management apparatus 100 according to the present embodiment.
[0037] As shown in FIG. 2, the device management apparatus 100
includes an input device 101, a display device 102, a drive device
103, a RAM (Random Access Memory) 104, a ROM (Read Only Memory)
105, a CPU (Central Processing Unit) 106, an interface device 107,
and a HDD (Hard Disk Drive) 108, which are connected to each other
by a bus B.
[0038] The input device 101 includes a keyboard and a mouse, and is
used for inputting various operation signals to the device
management apparatus 100. The display device 102 includes a
display, and displays processing results (for example, "device
information" and "system management information") obtained by the
device management apparatus 100.
[0039] The interface device 107 is an interface for connecting the
device management apparatus 100 to a predetermined data
transmission line N such as a network. Thus, the device management
apparatus 100 can perform data communications with the devices 200
and the external system 7 via the interface device 107.
[0040] The HDD 108 is a nonvolatile storage device storing various
programs and data. The stored programs and data include an
information processing system for controlling the entire device
management apparatus 100 (for example, basic software which is an
OS (Operating System) such as "Windows (registered trademark)" and
"UNIX (registered trademark)"), and applications for providing
various functions in the information processing system (for
example, "device management function" and "system management
function"). The HDD 108 manages the stored programs and data with a
predetermined file system and/or a DB (Data Base).
[0041] The drive device 103 is an interface between the device
management apparatus 100 and a removable recording medium 103A.
Accordingly, the device management apparatus 100 can write in/read
from the recording medium 103A via the drive device 103.
[0042] The ROM 105 is a nonvolatile semiconductor memory (storage
device) that can hold internal data even after the power is turned
off. The ROM 105 stores BIOS (Basic Input/Output System) that is
executed when the device management apparatus 100 is activated, and
data relevant to system settings and network settings of the device
management apparatus 100.
[0043] The RAM 104 is a volatile semiconductor memory (storage
device) for temporarily holding programs and data read from the
storage devices described above. The CPU 106 executes the programs
loaded in the RAM 104 to implement operations of controlling the
entire device management apparatus 100 and various functions
installed in the device management apparatus 100.
[0044] The device management apparatus 100 has substantially the
same configuration as that of a PC (Personal Computer), based on
the above description of the hardware configuration. Therefore, the
device management apparatus 100 can be replaced by an information
processing apparatus.
[0045] <Software Configuration>
[0046] Next, a description is given of a software configuration of
the device management apparatus 100 according to the present
embodiment.
[0047] FIG. 3 illustrates a software configuration of the device
management apparatus 100 according to the present embodiment.
[0048] As shown in FIG. 3, there are one or more software SW items
(function implementation programs) in the device management
apparatus 100. The device management apparatus 100 requires a
license code LC issued by the license authentication apparatus 300
in order to cause these software SW items to operate (to function).
That is to say, the software SW items cannot operate (function)
unless there are corresponding license codes LC in a predetermined
storage inside the device management apparatus 100. Thus, in the
device management apparatus 100, one or more license codes LC
corresponding to software SW items issued by the license
authentication apparatus 300 are managed in a predetermined file
system.
[0049] The device management apparatus 100 has a common module CM
provided between the software SW and the license code LC. The
common module CM is for implementing comprehensive functions
relevant to license management. For example, functions implemented
by the common module CM include a function for determining the
authenticity/validity of the license code LC based on information
relevant to the software SW (authenticity/validity determination
function) and a function for responding to information relevant to
the software SW included in the license code LC (relevant
information responding function).
[0050] Accordingly, in the device management apparatus 100, the
software SW confirms the authenticity/validity of the corresponding
license code LC through the common module CM, and operates
(functions) if the confirmation result (determination result from
the common module CM) is normal. For example, in the software
configuration shown in FIG. 3, software (A) SWA determines the
authenticity/validity of a license code (soft A) LCA based on the
common module CM. The software (N) SWN determines the
authenticity/validity of a license code (soft N) LCN based on the
common module CM.
[0051] As described above, in the device management apparatus 100
according to the present embodiment, the software SW cannot operate
unless its license has been authenticated. That is to say, with the
device management apparatus 100, in order to implement the internal
system 1 such as a device management system (device management
function), the license of the corresponding software SW needs to be
authenticated.
[0052] <System Management Function>
[0053] A description is given of a system management function
according to the present embodiment.
[0054] The device management apparatus 100 according to the present
embodiment generates system identification information for
identifying the internal system 1 that is built by installing
software. The system identification information is generated from
authentication information (license code LC) obtained by performing
license authentication on the software SW. Subsequently, the device
management apparatus 100 transmits the generated system
identification information to the external system 2 through a
predetermined data transmission line, and registers the system
identification information as management information. The device
management apparatus 100 according to the present embodiment
includes the above-described system management function.
[0055] As described above, instead of installing a dedicated
apparatus (for device management) in the user environment, software
SW can be installed in an existing information processing apparatus
that is already provided in the user environment, to build the
internal system 1 for implementing various functions. Furthermore,
the manufacturer would like to identify the internal systems 1 with
the external system 2 built at the manufacturer, and provide
appropriate maintenance/operations according to the user
environments.
[0056] In the conventional technology, the internal systems 1 are
identified based on information unique to the dedicated devices
(device-unique information) collected from the dedicated devices
(for example, a "serial number" or a "MAC address"). However, as
described above, when the internal system 1 is built by installing
software, the internal system 1 may be in a Virtual Machine (VM)
environment, and therefore the external system 2 may not always be
able identify the internal system 1 based on the device-unique
information of the device having the software SW installed. For
example, in a virtual machine environment, the user can change the
MAC address. If the device-unique information is changed, the
external system 2 cannot identify the internal system 1 that is
built by installing software. Furthermore, the device into which
the software is installed, i.e., the device in which the internal
system 1 is built, belongs to the user. Thus, the user may not want
the external system 2 at the manufacturer to collect information
from the device.
[0057] Therefore, the device management apparatus 100 according to
the present embodiment generates information, which is used for
identifying the internal system 1 built by installing software,
based on the authentication information of the software SW, and
registers the generated information in the external system 2.
[0058] Accordingly, with the device management apparatus 100
according to the present embodiment, the system built in the device
management apparatus 100 by installing software can be identified
by the external system 2 that is located remote from the device
management apparatus 100. As a result, even if the device
management system 1 is built by installing software, the remote
management system 2 at the manufacturer can manage the system built
in the user environment.
[0059] The configuration and operations of the system management
functions are described below.
[0060] FIG. 4 illustrates a functional configuration of the device
management apparatus 100 according to the present embodiment.
[0061] As shown in FIG. 4, the device management apparatus 100 is
mainly configured with a license authentication control unit 20 and
a system management control unit 30.
[0062] The license authentication control unit 20 is a function
unit for managing/controlling license authentication of the
software SW installed in the device management system 1. The system
management control unit 30 is a function unit for
managing/controlling the internal system 1 built by installing the
software SW.
[0063] A description is given of the license authentication control
unit 20. The license authentication control unit 20 includes a
license authentication request unit 21 that sends a license
authentication request for the software SW, from the device
management apparatus 100 to the license authentication apparatus
300.
[0064] The license authentication apparatus 300 includes a license
authentication unit 50 for generating a license code LC in response
to an authentication request, and returns the license code LC to
the request source. The license code LC is generated based on a
product key provided from the vendor to the user in association
with the software SW, and device-unique information of the device
200 into which the software SW has been installed (the
software-installed device).
[0065] Thus, when the license authentication request unit 21 makes
an authentication request, the license authentication request unit
21 sends the product key and the device-unique information to the
license authentication apparatus 300. Communications between the
device management apparatus 100 and the license authentication
apparatus 300 are performed by a communications unit 40A (in the
device management apparatus 100) and a communications unit 40B (in
the license authentication apparatus 300).
[0066] The license authentication control unit 20 stores, in a
license code saving unit 10, the license code LC that is returned
from (issued by) the license authentication apparatus 300. The
license code saving unit 10 corresponds to a predetermined storage
area in a storage device (for example, the HDD 108) provided in the
device management apparatus 100.
[0067] FIG. 5 illustrates an example of data for managing license
codes according to the present embodiment.
[0068] The license code saving unit 10 manages license codes LC
corresponding to software SW in a directory structure as shown in
FIG. 5. In the directory structure in FIG. 5, under each layer (in
each folder) of product identification information SN such as a
character string or a code for identifying the software SW, a
corresponding license code LC is saved. According to this data
structure, a license code LC corresponding to software SW can be
identified based on the product identification information SN.
[0069] The license authentication control unit 20 confirms the
authenticity/validity of the license code LC with the use of the
common module CM, before saving the license code in the license
code saving unit 10.
[0070] The common module CM can determine the authenticity/validity
of the license code LC based on information relevant to software SW
(has an authenticity/validity determination function). The license
authentication control unit 20 passes, to the common module CM, the
license code LC returned from the license authentication apparatus
300 together with the product identification information SN and
version information of the software SW that is the target of
authenticity/validity determination. Accordingly, the license
authentication control unit 20 can confirm whether the license is
normal based on the authenticity/validity determination results
made by the common module CM.
[0071] The license authentication control unit 20 saves the license
code LC that is confirmed as being normal, in the license code
saving unit 10.
[0072] Next, a description is given of the system management
control unit 30. The system management control unit 30 includes a
license validity confirmation unit 31, a license obtaining unit 32,
a system identification information generating unit 33, and a
system registration unit 34. The system management control unit 30
operates these function units in coordination with each other to
register, in the remote management apparatus 400 installed at the
manufacturer, the internal system 1 built by installing software SW
in the device management system 1.
[0073] The license validity confirmation unit 31 is a function unit
for confirming the authenticity/validity of the license code LC
corresponding to the software SW for implementing functions of the
internal system 1 to be registered.
[0074] The common module CM can determine the authenticity/validity
of the license code LC based on information relevant to software SW
(has a authenticity/validity confirmation function). The license
validity confirmation unit 31 passes, to the common module CM, the
product identification information SN anti version information of
the software SW that is the target of authenticity/validity
determination. Accordingly, the license validity confirmation unit
31 can confirm whether the license is normal based on the
authenticity/validity determination results made by the common
module CM.
[0075] The license obtaining unit 32 is a function unit for
obtaining a license code LC from the license code saving unit 10.
The license obtaining unit 32 obtains a license code LC that is
confirmed as being normal (authentic/valid) by the license validity
confirmation unit 31. The license obtaining unit 32 accesses the
license code saving unit 10 and obtains a corresponding license
code LC based on the product identification information SN of the
software SW.
[0076] The system identification information generating unit 33 is
a function unit for generating system identification information
based on the obtained license code LC. The system identification
information is used by the external system 2 at the manufacturer
for identifying the internal system 1 of the user. The system
identification information generating unit 33 generates the system
identification information as follows.
[0077] FIGS. 6A and 6B are for describing the operation of
generating system identification information SID according to an
embodiment of the present invention.
[0078] The system identification information generating unit 33
decodes an obtained license code LC with the use of the common
module CM.
[0079] The common module CM can return information relevant to
software SW included in the license code LC (has a relevant
information responding function). As shown in FIG. 6A, the system
identification information generating unit 33 passes the license
code LC to the common module CM, and obtains information relevant
to the software SW from the common module CM. Accordingly, the
license code LC is decoded.
[0080] The system identification information generating unit 33 can
obtain information such as the product identification information
SN, the version information, and the product key information of the
software SW. Furthermore, the system identification information
generating unit 33 may obtain device identification information for
identifying the software-installed device 200, the license issue
date, the license expiration date, the license type (for example,
"permanent/trial", "exclusive/additional", and in the case of a
common license, "number of retained licenses",
"standalone/network"). The information that can be obtained depends
on the specification of the common module CM and the license
authentication apparatus 300.
[0081] Next, as shown in FIG. 6B, the system identification
information generating unit 33 obtains system identification
information SID from product key information GPK (product key
information obtained by decoding the license code) from the common
module CM.
[0082] FIG. 6B illustrates an operation of generating the system
identification information SID. The obtained product key
information GPK is relevant to a product key that is embedded when
the license authentication apparatus 300 generates the license code
LC. Thus, the obtained product key information GPK includes random
numbers of certain digits for the purpose of enhancing the
confidentiality of the code.
[0083] The system identification information generating unit 33
extracts, from the obtained product key information GPK, a formal
product key provided for the software SW from the vendor, and uses
the extracted product key as the system identification information
SID. Specifically, a software identification information extracting
unit 33A deletes the random numbers from the product key
information GPK, and extracts the product key. The product key is
software identification information for identifying the software
SW. Thus, the product key (software identification information) is
appropriate for the function implemented by operating the software
SW, i.e., for identifying the internal system 1.
[0084] As described above, the system identification information
generating unit 33 uses the license code LC corresponding to the
software SW to generate system identification information SID for
identifying the internal system 1 built by installing software.
[0085] The system registration unit 34 is a function unit for
sending the generated system identification information SID to the
remote management apparatus 400, to perform system
registration.
[0086] The remote management apparatus 400 includes an information
management unit 60, and uses the information management unit 60 to
manage information (hereinafter, "management information") relevant
to the internal system 1 built in the user environment that is a
remote management target, in order to provide a service. The
information management unit 60 performs various data operations on
the management information held by a management information holding
unit 70. The management information holding unit 70 is a
predetermined storage area of the storage device provided in the
remote management apparatus 400. The management information holding
unit 70 holds the management information in association with the
system identification information SID, information relevant to the
software SW (software information), and information relevant to the
devices 200 managed in the internal system 1 (management target
device information). A specific example of a data configuration of
the management information held by the management information
holding unit 70 is described below.
[0087] The system registration unit 34 stores the generated system
identification information as management information, and generates
registration data to be registered in the remote management
apparatus 400.
[0088] FIGS. 7A and 7B illustrate an example of data used for
remote system management according to the present embodiment.
[0089] For example, the system registration unit 34 generates
registration data 80 as shown in FIG. 7A. FIG. 7A illustrates an
example of the registration data 80 described in XML (eXtensible
Markup Language). The registration data 80 is mainly formed by
registration request identification information RID, system
identification information SID, and device identification
information DID.
[0090] The registration request identification information RID is
used by the external system 2 to determine which of the internal
systems 1 made the registration request and when the registration
request was made. The system identification information SID is
generated by the system identification information generating unit
33. The device identification information DID is for identifying
the device 200 (management target device) managed in the internal
system 1 to be registered.
[0091] These information items are defined in the data with
predetermined tags. For example, in the registration data 80 in
FIG. 7A, the registration request identification information RID is
defined by <requestID> tags. The system identification
information SID is defined by <boxID> tags. The device
identification information DID is defined by <deviceID> tags.
There may be cases where the internal system 1 to be registered
includes plural devices 200. Therefore, in the registration data
80, a single system identification information SID item may be
associated with plural device identification information DID
items.
[0092] The system registration unit 34 sends the registration data
80 to the remote management apparatus 400 to perform system
registration. Communications between the device management
apparatus 100 and the remote management apparatus 400 are performed
by the communications unit 40A (in the device management-apparatus
100) and a communications unit 40C (in the remote management
apparatus 400).
[0093] Thus, in the remote management apparatus 400, the
information management unit 60 stores corresponding data in the
management information items held by the management information
holding unit 70, based on the received registration data 80. FIG.
7B illustrates an example of a data configuration of management
information 71 held by the management information holding unit 70.
As described above, the management information holding unit 70
stores data obtained from various information items included in the
registration data 80.
[0094] Accordingly, with the device management apparatus 100
according to the present embodiment, the external system 2 that is
remotely located (for example, a remote management system at the
manufacturer) can identify a system (for example, a device
management system at the user's site) built by installing software
in the device management system 1.
[0095] As described above, the system management function according
to the present embodiment can be implemented as the above function
units operate in coordination with each other.
[0096] Next, detailed operations of the system management functions
(operations of function units performed in coordination with each
other) are described with reference to a sequence diagram.
[0097] The system management function is implemented as the CPU 106
loads a system management program (software component) installed in
the device management apparatus 100 into the RAM 104 from a storage
destination (for example, the ROM 105), and executes the loaded
system management program.
[0098] In the following descriptions, operations of the system
management functions are divided into the process of
"issuing/saving a license code" and the process of "system
registration". The process of "system registration" is performed on
condition that the process of "issuing/saving a license code" has
already been performed.
[0099] FIG. 8 is a sequence diagram of the process of
"issuing/saving a license code" according to the present
embodiment.
[0100] <Issuing a License Code>
[0101] The device management apparatus 100 receives, with the
license authentication control unit 20, a product key provided by
the vendor and input by the user when the user makes an
authentication request via a predetermined GUI (Graphical User
Interface) relevant to license authentication (step S101).
[0102] The license authentication request unit 21 of the license
authentication control unit 20 sends an authentication request for
the software SW to the license authentication apparatus 300 (step
S102). Specifically, the license authentication request unit 21
sends an input product key and device-unique information (device
information of the device 200 in which the software SW is
installed) to the license authentication apparatus 300 to make the
authentication request.
[0103] The license authentication unit 50 of the license
authentication apparatus 300 performs license authentication for
the software SW (step S103). Specifically, the license
authentication unit 50 generates a license code LC of the software
SW based on the product key and device-unique information input
when the request is made.
[0104] The license authentication apparatus 300 sends the generated
license code LC as an authentication result to the request source,
to respond to the authentication request. As a result, the license
authentication control unit 20 obtains a license code.
[0105] <Saving a License Code>
[0106] The device management apparatus 100 receives, with the
license authentication control unit 20, the license code LC (the
license code LC obtained as an authentication result) input by the
user when the user makes a license code saving request via a
predetermined GUI relevant to license authentication (step
S201).
[0107] The license authentication control unit 20 requests the
common module CM to determine the authenticity/validity (check) of
the input license code LC (step S202). Specifically, the license
authentication control unit 20 passes the input license code LC,
the product identification information SN, and version information
of the software SW to the common module CM, and makes a check
request.
[0108] The common module CM checks the authenticity/validity of the
input license code LC based on the product identification
information SN and version information given with the request
(S203).
[0109] The common module CM responds to the check request by
passing the check result to the request source. As a result, the
license authentication control unit 20 obtains the check result of
the authenticity/validity of the input license code LC that has
been requested to be saved.
[0110] When the check result of the input license code LC indicates
normal (OK), the license authentication control unit 20 accesses
the license code saving unit 10 and saves the input license code LC
that has been checked (determined normal) (step S204). In the
license code saving unit 10, the input license code LC is stored
and saved in a predetermined storage area (step S205).
[0111] As described above, the device management apparatus 100
performs the process of "issuing/saving a license code"
corresponding to the software SW installed for implementing a
function of the internal system 1.
[0112] FIG. 9 is a sequence diagram of the process of system
registration according to the present embodiment.
[0113] <System Registration (Register Internal System to
External System)>
[0114] When the device management apparatus 100 receives a
registration request from a user via a predetermined GUI relevant
to system registration, a pertinent report is sent to the license
validity confirmation unit 31 included in the system management
control unit 30 (step S301). The registration request is made for
registering the internal system (device management system 1 at a
user's site), which is built by installing software SW, with the
external system 2 (remote management system 2 at the
manufacturer).
[0115] The license validity confirmation unit 31 requests the
common module to determine (check) the authenticity/validity of an
input license code LC (step S302). Specifically, the license
validity confirmation unit 31 passes the product identification
information SN and version information of the software SW to the
common module CM to make the check request.
[0116] The common module CM accesses the license code saving unit
10 (step S303), and refers to a corresponding license code LC that
is saved in the license code saving unit 10, based on the product
identification information SN and version information given with
the request (step S304). Accordingly, the common module CM checks
the authenticity/validity of the license code LC corresponding to
the software SW.
[0117] The common module CM responds to the check request by
passing the check result to the request source. As a result, the
license validity confirmation unit 31 obtains the check result
indicating the authenticity/validity of the input license code LC
corresponding to the software SW for implementing a function of the
internal system 1 for which the registration request has been
made.
[0118] When the check result of the input license code LC indicates
normal (OK), the license validity confirmation unit 31 requests the
license obtaining unit 32 included in the system management control
unit 30 to obtain the license code LC corresponding to the software
SW (step S401).
[0119] The license obtaining unit 32 accesses the license code
saving unit 10 (step S402), and refers to the corresponding license
code LC that has been saved (step S403). The license obtaining unit
32 identifies the corresponding license code LC based on the
product identification SN and version information. Accordingly, the
license obtaining unit 32 obtains the license code LC corresponding
to the software SW as a reference result.
[0120] When the license code LC is normally obtained, the license
obtaining unit 32 requests the system identification information
generating unit 33 included in the system management control unit
30 to generate system identification information SID based on the
obtained license code LC (step S501).
[0121] The system identification information generating unit 33
requests the common module CM to decode the obtained license code
LC (step S502). When making the decode request, the system
identification information generating unit 33 passes the obtained
license code LC to the common module CM.
[0122] The common module CM decodes the obtained license code LC in
response to the request (step S503). As a result, the common module
CM obtains the information relevant to the software SW included in
the obtained license code LC (for example, "product identification
information" and "product key information").
[0123] The common module CM responds to the decode request by
passing the above information obtained by decoding the license code
LC (information relevant to the software SW) as the decode result
to the request source. As a result, the system identification
information generating unit 33 obtains the decode result
(information relevant to the software SW) of the License code LC
corresponding to the software SW for implementing the function of
the internal system 1 for which the registration request has been
made.
[0124] The system identification information generating unit 33
generates the system identification information SID for identifying
the internal system 1 for which the registration request has been
made, from the obtained product key information GPK included in the
information relevant to the software SW obtained as a result of
decoding (step S504). The software identification information
extracting unit 33A of the system identification information
generating unit 33 performs predetermined data processing on the
obtained product key information GPK.
[0125] Specifically, the software identification information
extracting unit 33A extracts and deletes random numbers (needless
data) from the obtained product key information GPK. The software
identification information extracting unit 33A extracts, from the
obtained product key information GPK, a product key (software
identification information) provided for the software SW by a
vendor. The system identification information generating unit 33
uses the extracted product key as the system identification
information SID. As described above, the system identification
information generating unit 33 generates the system identification
information SID.
[0126] When the system identification information generating unit
33 has generated the system identification information SID, the
system identification information generating unit 33 requests the
system registration unit 34 included in the system management
control unit 30 to perform system registration to register the
internal system in the external system 2 (step S601). When making
the registration request, the system identification information
generating unit 33 passes the generated system identification
information SID to the system registration unit 34.
[0127] The system registration unit 34 registers, in the external
system 2, the internal system 1 for which the registration request
has been made. Specifically, the system registration unit 34
generates the registration data 80 based on the generated system
identification information SIP (step S602). The system registration
unit 34 generates the registration data 80 that is associated with
registration request identification information RID, system
identification information SID, and one or more device
identification information DID items. The system registration unit
34 may associate the above information items with each other by
using predetermined data tags to describe definitions in the
registration data 80. Accordingly, based on system identification
information SID, the system registration unit 34 generates the
registration data 80 described in XML, for example.
[0128] The system registration unit 34 requests the remote
management apparatus 400 to register the registration data 80 (step
S603) Specifically, the system registration unit 34 sends the
generated registration data 80 to the remote management apparatus
400 to make the registration request.
[0129] In the remote management apparatus 400, the information
management unit 60 registers the internal system 1 based on the
registration data (step S604). Specifically, the information
management unit 60 analyzes the registration data 80 (analyzes the
registration data 80 with a description language analyzing function
such as an XML parser), and obtains definition data of the
information items defined in the data. The information management
unit 60 accesses the management information holding unit 70, and
stores the obtained data in association with the corresponding
items in the management information 71.
[0130] The management information holding unit 70 saves the data of
the internal system 1 defined in the registration data 80, as the
management information 71 (step S605).
[0131] The information management unit 60 in the remote management
apparatus 400 responds to the registration request by passing the
registration result to the request source. As a result, the device
management apparatus 100 can report to the user as to whether the
internal system 1, for which the registration request has been
made, has been normally registered in the external system 2.
[0132] As described above, the device management apparatus 100
performs the process of "generating/registering the system
identification information" for the internal system. 1 built by
installing the software SW.
SUMMARY
[0133] As described above, the device management apparatus 100
according to the present embodiment generates system identification
information SID for identifying the internal system 1 that has been
built by installing software. The system identification information
SID is generated based on authentication information (license code
LC) obtained by performing license authentication on the software
SW. The device management apparatus 100 extracts software
identification information (product key) from the authentication
information, and generates the system identification information
SID based on the extracted software identification information.
Subsequently, the device management apparatus 100 sends the
generated system identification information SID to the external
system 2 via a predetermined data transmission line, to register
the system identification information SID as the management
information 71. The device management apparatus 100 sends the
registration data 80 including the generated system identification
information SID to the remote management apparatus 400 of the
external system 2, and saves the registration data 90 as the
management information 71 in a storage device included in the
remote management apparatus 400.
[0134] Accordingly, the system built by installing software in the
device management system 1 can be identified by the external system
2 that is located remote from the device management system 1.
[0135] The "system management function" of the device management
apparatus 100 according to the above-described embodiment may be
implemented by performing the processes described with reference to
the figures, by having the CPU 106 execute a program that is coded
in a programming language corresponding to the operating
environment (platform).
[0136] The program may be stored in the computer-readable recording
medium 103A. The recording medium 103A may be, for example, a
floppy (registered trademark) disk, a CD (Compact Disk), a DVD
(Digital Versatile Disk), an SD memory card (SD Memory Card), and a
USB (Universal Serial Bus) memory.
[0137] The program may be stored in the recording medium 103A and
installed in the device management apparatus 100 via the drive
device 103 or an external storage I/F (not shown) that can read the
recording medium 103A. The device management apparatus 100 includes
the interface device 107, and therefore the program may be
installed by downloading the program via an electronic
communications line such as the Internet.
[0138] In the above embodiment, the internal system 1, which is
built in the user environment by installing software, can be
identified by the external system 2 at the manufacturer; however,
the present invention is not so limited. For example, the present
invention is applicable to a case where a system is identified by
another system within the same user environment including plural
systems.
[0139] In the above embodiment, the registration data 80 is
described in XML; however, the present invention is not so limited.
The registration data 80 need not be in an XML format as long as it
is in a format that can be analyzed by the information management
unit 60 (a format described in a language corresponding to the
description language analyzing function).
[0140] In the above embodiment, the registration data 80 associates
the system identification information SID with device
identification information DID; however, the present invention is
not so limited. The device identification information DID is
described as an example when the system to be registered is the
device management system 1.
[0141] In the above embodiment, the system identification
information generating unit 33 performs data processing by deleting
random numbers from the product key information GPK that is
obtained as a decoded result of the common module CM; however, the
present invention is not so limited. The product key information
GPK that is obtained as a decode result may or may not include
random numbers depending on the specification of the license code
issuing operation in the license authentication apparatus 300.
Thus, the data processing method described above may vary according
to the specification of the license code issuing operation.
[0142] The present invention is not limited to the specific
embodiments described herein, and variations and modifications may
be made without departing from the scope of the present
invention.
[0143] The present application is based on Japanese Priority Patent
Application No. 2009-162169, filed on Jul. 8, 2009, the entire
contents of which are hereby incorporated herein by reference.
* * * * *