Information processing device, information processing system, information processing method, and program

Abstract

To facilitate license management.SOLUTION: An information processing device that is connected with a terminal via a network and manages a license for a package that contains one or more applications used by devices, includes: display means for displaying a first screen containing a list of devices for which the license of the package can be allocated or deallocated in response to a first request from the terminal; and license management means for, in response to a selection of a device from the list of devices contained in the first screen and an operation for allocating or deallocating the license, allocating the license to the selected device or deallocating the license from the selected device.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] The present invention relates to an information processing device and an information processing system. [Background technology]

[0002] In recent years, advances in technologies such as cloud computing have led to the provision of a wide variety of applications as cloud services for devices such as multifunction peripherals (MFPs). For example, applications that store image files scanned by a multifunction peripheral in external storage, and applications that print electronic files downloaded from external storage by a multifunction peripheral are provided as cloud services. Such applications can be used, for example, by assigning a license for using the application to the device.

[0003] Furthermore, there is known a technique for issuing an updated license to an image forming apparatus after the image forming apparatus is replaced after the license contract has commenced (see, for example, Japanese Patent Laid-Open No. 2003-233663). Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the above conventional technology, the user needs to input identification information (e.g., a serial number) for identifying the image forming apparatus to be replaced. For this reason, the user needs to operate the image forming apparatus to be replaced to display the serial number or check a sticker (a sticker with a serial number or the like) attached to the image forming apparatus to be replaced.

[0005] Therefore, when an image forming apparatus is replaced, license management requires a lot of work.

[0006] The embodiment of the present invention has been made in consideration of the above points, and has an object to facilitate license management. [Means for solving the problem]

[0007] In order to achieve the above-mentioned object, an embodiment of the present invention is an information processing device that is connected to a terminal via a network and manages licenses of a package including one or more applications used by the device, and is characterized in having: a display means that causes the terminal to display a first screen including a list of devices to which the license of the package can be assigned or released in response to a first request from the terminal; and a license management means that assigns the license to the selected device or releases the license from the selected device in response to a selection of a device from the list of devices included in the first screen and an operation for the assignment or release. Effect of the Invention

[0008] License management can be made easier. [Brief description of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of an overall configuration of a cloud system according to an embodiment of the present invention. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of a computer. [Diagram 3] FIG. 2 is a diagram illustrating an example of a hardware configuration when the device according to the present embodiment is an image forming apparatus. [Figure 4] FIG. 2 is a diagram illustrating an example of a functional configuration of a cloud system according to the present embodiment. [Diagram 5] 11 is a diagram showing an example of a relationship between package information, application information, application setting information, service information, and device information. FIG. [Figure 6] FIG. 11 is a diagram illustrating an example of package information. [Figure 7] FIG. 11 is a diagram illustrating an example of application information. [Figure 8]FIG. 11 is a diagram illustrating an example of application setting information. [Figure 9] FIG. 11 is a diagram illustrating an example of service information. [Figure 10] FIG. 4 is a diagram illustrating an example of license information. [Figure 11] FIG. 11 is a diagram illustrating an example of device information. [Figure 12] FIG. 11 is a sequence diagram illustrating an example of a license management process. [Figure 13] 11A and 11B are diagrams illustrating an example of a menu screen, a device management screen, and a package management screen. [Figure 14] 13 is a sequence diagram illustrating an example of a license release process from a device management screen. FIG. [Figure 15] 13A and 13B are diagrams illustrating an example of an allocated package screen and a release result screen. [Figure 16] 13 is a sequence diagram illustrating an example of a license allocation process from a device management screen. [Figure 17] FIG. 13 is a diagram showing an example of an allocatable package screen. [Figure 18] FIG. 13 is a sequence diagram illustrating an example of a license release process from a package management screen. [Figure 19] 13A and 13B are diagrams illustrating an example of an assigned device screen and a release result screen. [Figure 20] 13 is a sequence diagram illustrating an example of a license allocation process from a package management screen. [Figure 21] FIG. 13 is a diagram illustrating an example of an allocatable device screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0011] <Overall composition> First, the overall configuration of a cloud system 1 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the overall configuration of a cloud system 1 according to this embodiment.

[0012] As shown in Fig. 1, the cloud system 1 according to this embodiment includes a cloud server 10, a terminal device 20, and one or more devices 30. The terminal device 20 and the one or more devices 30 are installed in a system environment E of a user who uses the devices 30, and are communicatively connected via a network N2 such as a LAN (Local Area Network). The cloud server 10 and the system environment E are communicatively connected via a network N1 such as the Internet. The network N1 and the network N2 may be either wired or wireless, or may be a mixture of wired and wireless networks.

[0013] The cloud server 10 is an information processing device (computer) that provides a cloud-type application to the device 30 via the network N1. Hereinafter, the cloud-type application is also referred to as a "cloud application" or simply as an "application."

[0014] Specific examples of cloud applications include an application that stores image data generated by scanning on a device 30 such as a multifunction printer in external storage, and an application that prints electronic files obtained from external storage on the device 30.

[0015] The application provided by the cloud server 10 according to the present embodiment will be described as a cloud-type application, but is not limited to this. The application provided by the cloud server 10 may be, for example, a Web application or an application provided by an ASP (Application Service Provider).

[0016] Furthermore, the cloud server 10 manages applications provided to the devices 30 and the licenses of the applications.

[0017] The terminal device 20 is, for example, an information processing device (computer) used by an administrator of the system environment E. Specific examples of the terminal device 20 include, for example, a PC (personal computer), a smartphone, and a tablet terminal.

[0018] For example, an administrator of the system environment E can use the terminal device 20 to manage the licenses of applications (for example, assigning a license to the device 30 and canceling a license assigned to the device 30). Therefore, for example, when the device 30 is replaced, the administrator can use the terminal device 20 to cancel the license assigned to the original device 30 and assign a license to the new device 30.

[0019] The device 30 is, for example, an image forming device such as a multifunction peripheral (MFP). The device 30 can provide various services to the user by using an application provided by the cloud server 10. Note that the device 30 is assigned a license for the application, thereby becoming able to use the application.

[0020] The configuration of the cloud system 1 shown in Fig. 1 is an example, and other configurations may be used. For example, the cloud server 10 may be an information processing system (computer system) composed of a plurality of information processing devices. Furthermore, the system environment E may include a plurality of terminal devices 20. Furthermore, the device 30 is not limited to a multifunction device, and may be, for example, a digital camera, a printing device, a copy machine, a projector, a facsimile machine, an electronic conference terminal, an electronic whiteboard device, an audio device, an in-vehicle device (e.g., a car navigation system), a home appliance (e.g., a refrigerator), etc.

[0021] <Hardware configuration> Cloud Server 10, Terminal Device 20 Next, a description will be given of the hardware configuration of the cloud server 10 and the terminal device 20 according to the present embodiment. One or more information processing devices that realize the cloud server 10 according to the present embodiment and the terminal device 20 according to the present embodiment are realized, for example, by a computer 400 shown in Fig. 2. Fig. 2 is a diagram showing an example of the hardware configuration of the computer 400.

[0022] 2 includes an input device 401, a display device 402, an external I / F 403, and a RAM (Random Access Memory) 404. The computer 400 also includes a ROM (Read Only Memory) 405, a CPU (Central Processing Unit) 406, a communication I / F 407, and an auxiliary storage device 408. Each of these pieces of hardware is connected to a bus B.

[0023] The input device 401 includes a keyboard, a mouse, a touch panel, etc., and is used by a user to input various operations. The display device 402 includes a display, etc., and displays the results of processing by the computer 400. Note that the computer 400 does not necessarily have to have at least one of the input device 401 and the display device 402.

[0024] The external I / F 403 is an interface with an external device. The external device may be a recording medium 403a. The computer 400 can read and write data from and to the recording medium 403a via the external I / F 403. The recording medium 403a may be, for example, a flexible disk, a CD, a DVD, an SD memory card, or a USB memory.

[0025] The RAM 404 is a volatile semiconductor memory that temporarily stores programs and data. The ROM 405 is a non-volatile semiconductor memory that can store programs and data even when the power is turned off. The ROM 405 stores programs and data such as a basic input / output system (BIOS) that is executed when the computer 400 is started, operating system (OS) settings, and network settings.

[0026] The CPU 406 is a calculation device that reads out programs and data from storage devices such as the ROM 405 and the auxiliary storage device 408 onto the RAM 404 and executes processing, thereby realizing overall control and functions of the computer 400 .

[0027] The communication I / F 407 is an interface that connects the computer 400 to the network N1 or the network N2. The computer 400 can perform data communication with other devices via the communication I / F 407.

[0028] The auxiliary storage device 408 is, for example, a hard disk drive (HDD) or a solid state drive (SSD), and is a non-volatile storage device that stores programs and data. The programs and data stored in the auxiliary storage device 408 include an OS, which is basic software that controls the entire computer 400, and software that provides various functions on the OS. The auxiliary storage device 408 manages the stored programs and data using a predetermined file system, DB (database), etc.

[0029] One or more information processing devices that realize the cloud server 10 of this embodiment and the terminal device 20 of this embodiment have the hardware configuration of a computer 400 shown in Figure 2, and can realize various processes as described below.

[0030] ≪Equipment 30≫ Next, a hardware configuration when the device 30 according to the present embodiment is an image forming device will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of a hardware configuration when the device 30 according to the present embodiment is an image forming device.

[0031] 3 includes a controller 21, an operation panel 22, an external I / F 23, a communication I / F 24, a plotter 25, and a scanner 26. The controller 21 also includes a CPU 31, a RAM 32, a ROM 33, a NVRAM 34, and an auxiliary storage device 35.

[0032] The ROM 33 is a non-volatile semiconductor memory that can hold programs and data even when the power is turned off. The RAM 32 is a volatile semiconductor memory that temporarily holds programs and data. The NVRAM 34 is a non-volatile semiconductor memory that stores, for example, setting information. The auxiliary storage device 35 is, for example, an HDD or SSD, and is a non-volatile storage device that stores programs and data.

[0033] The CPU 31 is a calculation device that realizes the overall control and functions of the device 30 by reading programs, data, setting information, etc. from the ROM 33, NVRAM 34, auxiliary storage device 35, etc. onto the RAM 32 and executing processes.

[0034] The operation panel 22 is an input / output device that includes an input unit that accepts input from a user and a display unit that displays information. The external I / F 23 is an interface with an external device. The external device may include a recording medium 23a. The device 30 can read and write data from and to the recording medium 23a via the external I / F 23.

[0035] The recording medium 23a may be, for example, an IC card, a flexible disk, a CD, a DVD, an SD memory card, or a USB memory.

[0036] The communication I / F 24 is an interface that connects the device 30 to the network N2. The device 30 can perform data communication with other devices and the like via the communication I / F 24.

[0037] The plotter 25 is a printing device for printing print data on a print medium. The print medium is not limited to paper. The print medium may be, for example, an overhead projector sheet, a plastic film, or copper foil. The scanner 26 is a reading device for reading an original document and creating image data.

[0038] The device 30 according to this embodiment has the hardware configuration shown in FIG. 3 and can thereby realize various processes as described below.

[0039] <Functional configuration> Next, the functional configuration of the cloud system 1 according to this embodiment will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the functional configuration of the cloud system 1 according to this embodiment.

[0040] <Terminal device 20> 4, the terminal device 20 according to the present embodiment has a general-purpose Web browser 210 (hereinafter, simply referred to as the "browser 210"). A user of the terminal device 20 (e.g., an administrator of the system environment E) can use the browser 210 to manage the licenses of applications.

[0041] ≪Equipment 30≫ 4, the device 30 according to the present embodiment has a general-purpose web browser 310 (hereinafter simply referred to as the "browser 310"). A user of the device 30 can use the browser 310 to utilize applications provided by the cloud server 10.

[0042] Cloud Server 10 4, the cloud server 10 according to this embodiment includes a Web service unit 101, an authentication unit 102, an application management unit 103, a license management unit 104, and a device management unit 105. Each of these units is realized by a process executed by one or more programs installed in the cloud server 10, for example, by the CPU 406.

[0043] Moreover, the cloud server 10 according to this embodiment has an authentication information storage unit 110, a package information storage unit 120, an application information storage unit 130, an application setting information storage unit 140, a service information storage unit 150, a license information storage unit 160, and a device information storage unit 170. Each of these storage units can be realized, for example, by using the auxiliary storage device 408. Note that at least one of these storage units may be realized by using a storage device or the like (for example, a DB server or the like) connected to the cloud server 10 via the network N1.

[0044] In response to various requests from the browser 210 of the terminal device 20, the Web service unit 101 generates and returns various screens for the user of the terminal device 20 to perform license management.

[0045] In response to a login request from the browser 210 of the terminal device 20, the authentication unit 102 performs login authentication by referring to the authentication information stored in the authentication information storage unit 110. The authentication information is information for performing login authentication, and is, for example, a set of a user ID and a password for logging in to the cloud server 10.

[0046] The login request is a request for the user of the terminal device 20 to log in to the cloud server 10. By logging in to the cloud server 10, the user of the terminal device 20 can perform license management of licenses and the like managed by the cloud server 10.

[0047] The application management unit 103 manages the package information stored in the package information storage unit 120 , the application information stored in the application information storage unit 130 , and the application setting information stored in the application setting information storage unit 140 .

[0048] Package information is information indicating a package, which is a sales unit of a product (application). A package includes one or more applications. App information is information indicating an application to be provided to device 30. App information includes, for example, the name of the application and a description of the application. App setting information is information indicating default settings when a user of device 30 uses an application. App setting information is, for example, default setting values ​​for print settings and default setting values ​​for scan settings.

[0049] The license management unit 104 manages the service information stored in the service information storage unit 150 and the license information stored in the license information storage unit 160 .

[0050] The service information is information that indicates a service that is introduced by purchasing a package, etc. The service information includes, for example, the name of the service and a description of the service.

[0051] The license information is information indicating a license for each package for each tenant. The license information includes, for example, identification information (e.g., a tenant ID) for identifying a tenant that has purchased a package, and identification information (e.g., a device ID) for identifying a device 30 that can use an application included in the package.

[0052] A tenant is an organization or group that uses an application by purchasing a package, etc. Specifically, examples of a tenant include a company, a department, a section, a team, and the like.

[0053] The device management unit 105 manages the device information stored in the device information storage unit 170 .

[0054] The device information is information indicating the device 30 registered in the cloud server 10. The device information includes, for example, identification information for identifying the device 30, identification information for identifying a tenant that owns or uses the device 30, and the like.

[0055] In addition, when the cloud server 10 is composed of multiple information processing devices, the Web service unit 101, the authentication unit 102, the application management unit 103, the license management unit 104, and the device management unit 105 may each be realized in a different information processing device.

[0056] Here, the relationships between the various pieces of information (package information, application information, application setting information, service information, and device information) managed by the cloud server 10 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the relationships between the package information, application information, application setting information, service information, and device information.

[0057] As shown in FIG. 5, package information and application information have a one-to-many (one or more) relationship. This indicates that one package contains one or more applications. Also, application information and application setting information have a one-to-one relationship. This indicates that for one application, there is one default setting for when using this application.

[0058] Furthermore, there is a one-to-one relationship between package information and service information. This indicates that one service is realized by an application included in one package. Furthermore, there is a one-to-many (0 or more) relationship between service information and license information. This indicates that for a service realized by an application included in a package purchased by a certain tenant, there are zero or more licenses (including licenses whose validity period has expired and also including cases where no license exists) for an application included in the package that realizes this service.

[0059] Furthermore, the license information and the device information have a many-to-many (0 or more) relationship, which indicates that there are zero or more devices 30 to which a license for an application included in a certain package is assigned (including cases where the license is not assigned to a device 30), and there are zero or more licenses assigned to a certain device 30 (including cases where no license is assigned to the device 30).

[0060] As described above, in this embodiment, there is a one-to-one relationship between package information and service information, and there is a one-to-one relationship between service information and license information. This means that when a tenant purchases a package, a license to use all applications included in the package is granted. That is, in this embodiment, a license is on a package basis. Therefore, hereinafter, a license to use an application included in a package is also simply referred to as a "package license."

[0061] Furthermore, the number of devices 30 to which one license can be assigned is determined in advance for each package.

[0062] The package information, app information, app setting information, and service information are created, for example, when a package (and application) is created and released, and are stored in the package information storage unit 120, the app information storage unit 130, the app setting information storage unit 140, and the service information storage unit 150. The device information is created, for example, when the device 30 is newly installed, by the terminal device 20, etc., and is stored in the device information storage unit 170. The license information is created, for example, when an administrator of the system environment E, etc., purchases a package, and is stored in the license information storage unit 160.

[0063] Here, the package information stored in package information storage unit 120 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of package information.

[0064] As shown in FIG. 6, the package information stored in package information storage unit 120 includes the following data items: “Package ID”, “Package Name”, “Package Description”, “Service ID”, and “Application ID List”.

[0065] The "package ID" is identification information for identifying package information. The "package name" is the name of the package.

[0066] 6, in the package information of package ID "P001", "Storage A Package" is set as the "Package Name". This indicates that the package indicated by the package information is, for example, a package including an application that works with "Storage A", which is an external storage service.

[0067] Similarly, in the package information for package ID "P002," "Storage B Package" is set as the "Package Name." This indicates that the package indicated by the package information is, for example, a package that includes an application that works with "Storage B," an external storage service.

[0068] "Package Description" is a description of the package (e.g., an explanation of what applications are included in the package). "Service ID" is identification information (e.g., a service ID) that identifies service information associated with package information. "App ID List" is a list of identification information (app IDs) that identify app information indicating applications included in the package.

[0069] 6, in the package information with a "Package ID" of "P001", "APP001", "APP002", etc. are set as the "Application ID List". This indicates that the package indicated by the package information contains an application identified by the application ID "APP001" and an application identified by the application ID "APP002".

[0070] In addition, the package information is not limited to the above data items, but may also include various other data items, such as a "release date" indicating the date the package was released (the date sales began), and an "update date" indicating the date the package was updated.

[0071] Next, the application information stored in the application information storage unit 130 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the application information.

[0072] As shown in FIG. 7, the application information stored in the application information storage unit 130 includes, as data items, an “application ID,” an “application name,” an “application description,” a “creation date,” and “developer information.”

[0073] The "application ID" is identification information for identifying application information indicating an application. The "application name" is the name of the application.

[0074] 7, in the application information of the application ID "APP001," "Scan to Email" is set as the "application name." This indicates that the application indicated by the application information is, for example, an application that transmits image data generated by scanning with the device 30 to a specified email address.

[0075] Similarly, in the application information of the application ID "APP002," "Application Name" is set to "Scan to Me." This indicates that the application indicated by the application information is, for example, an application that sends image data generated by scanning with the device 30 to the user's own email address.

[0076] Similarly, in the application information of the application ID "APP003," "Application Name" is set to "Scan to Storage A." This indicates that the application indicated by the application information is, for example, an application that stores (uploads) image data generated by scanning with the device 30 to "Storage A," which is an external storage service.

[0077] "App description" is a description of the application (e.g., an explanation of what kind of application it is, etc.). "Creation date" is the date the application was created. "Developer information" is information about the developer who developed the application (e.g., developer name, development department, contact information, etc.).

[0078] In addition, the app information is not limited to the above data items, but may also include various other data items such as a "release date" indicating the date on which the application was released and an "update date" indicating the date on which the application was updated.

[0079] Next, the application setting information stored in the application setting information storage unit 140 will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of the application setting information.

[0080] As shown in FIG. 8, the application setting information stored in application setting information storage unit 140 includes, as data items, an "application setting ID", an "application ID", and a "default setting".

[0081] The "application setting ID" is identification information for identifying application setting information. The "application ID" is an application ID for identifying application information associated with the application setting information. The "default setting" is a default setting when using an application.

[0082] 8, in the application setting information of the application setting ID "SET001", "resolution=300 dpi" or the like is set as the "default setting". This indicates that "resolution=300 dpi" or the like is applied as the default setting when using the application indicated by the application ID "APP001".

[0083] Note that the application setting information is not limited to the above data items, and may include various other data items such as a "creation date" indicating the date on which the application setting information was created.

[0084] Next, the service information stored in the service information storage unit 150 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the service information.

[0085] As shown in FIG. 9, the service information stored in the service information storage unit 150 includes, as data items, a "service ID," a "service name," a "service description," and a "service type."

[0086] The "service ID" is identification information for identifying the service information. The "service name" is the name of the service.

[0087] 9, in the service information of the service ID "S1111," "storage A linked service" is set as the "service name." This indicates that a service linked with storage A is introduced by the package indicated by the package information associated with the service information of the service ID "S1111."

[0088] Similarly, in the service information of the service ID "S2222," "Storage B Linkage Service" is set as the "Service Name." This indicates that a service linking with Storage B is introduced by the package indicated by the package information associated with the service information of the service ID "S2222."

[0089] "Service description" is a description of the service (e.g., an explanation of what kind of service it is, etc.). "Service type" is the type of service. An example of the service type is "cloud service," which indicates that it is a cloud-based service. In addition to "cloud service," the service type may also be set to, for example, "web service," which indicates that it is a service provided by a web application.

[0090] In addition, the service information is not limited to the above data items, but may also include various data items such as ``price'', which sets the price of the package indicated by the package information associated with the service information.

[0091] Next, the license information stored in the license information storage unit 160 will be described with reference to Fig. 10. Fig. 10 is a diagram showing an example of the license information.

[0092] As shown in FIG. 10, the license information stored in the license information storage unit 160 includes, as data items, a "license ID," a "license name," a "tenant ID," a "start date of use," a "scheduled end date," an "end date," a "status," a "number of available devices," a "device ID in use," and a "service ID."

[0093] "License ID" is identification information that identifies license information. "License name" is the name of the license. For example, in the case of a package with a package name of "Storage A Package", the license name of this package would be "Storage A Package License" or the like.

[0094] The "tenant ID" is identification information that identifies a tenant to which the license has been granted by purchasing a package or the like.

[0095] The "usage start date" is the date on which the license became valid (for example, the date on which the package was purchased or the date on which the license was activated). The "planned end date" is the date on which the license is scheduled to end. The "end date" is the date on which the license actually ends. If the license has not yet ended, the "end date" is set to blank, for example.

[0096] "Status" is the status of the license. For example, "Status" may be set to "In Use" indicating that the license is valid, or "Terminated" indicating that the license has become invalid due to expiration. For example, if the license has become invalid due to termination of the license contract before the scheduled expiration date of the license, "Status" may be set to "Cancelled".

[0097] The "number of available devices" is the upper limit number of devices 30 that can use the application included in the package that has been purchased, etc. If a value indicating that the application is not available, such as "terminated" or "cancelled," is set in the data item "status," a hyphen "-," for example, is set in the "number of available devices."

[0098] "Device ID in use" is a list of device IDs of devices 30 that are using an application included in a package that has been purchased or the like (i.e., devices 30 to which a license has been assigned). The device ID is identification information that identifies the device 30, and may be, for example, the manufacturing specific number or serial number of the device 30. Note that if a value indicating that the application is not available, such as "Ended" or "Cancelled," is set in the data item "Status," a hyphen "-," for example, is set in the "Device ID in use."

[0099] The "service ID" is a service ID that identifies the service information associated with the license information. The license information of the license ID "L12346" and the license information of the license ID "L12347" are set with the same service ID "S22222". This indicates that after the license indicated by the license information of the license ID "L12346" expired, the license was updated by the license information of the license ID "L12347". In this way, when the license of the package indicated by the package information corresponding to certain service information expires and the license of this package is updated, the same service ID is set in the data item "service ID" of the license information indicating the license.

[0100] In addition, the license information is not limited to the above data items, but may also include data items such as a "purchase date" indicating the date on which the package was purchased, and "purchaser information" indicating information regarding the purchaser of the package.

[0101] Next, the device information stored in the device information storage unit 170 will be described with reference to Fig. 11. Fig. 11 is a diagram showing an example of device information.

[0102] As shown in FIG. 11, the device information stored in the device information storage unit 170 includes, as data items, a "device ID," a "device description," a "tenant ID," and a "registration date."

[0103] "Device ID" is identification information for identifying device 30. "Device description" is a description of device 30 (e.g., what model it is, which floor of which building it is installed on, etc.). "Tenant ID" is identification information for identifying the tenant who owns or uses device 30. "Registration date" is the date on which the device information was stored in device information storage unit 170.

[0104] It should be noted that the device information is not limited to the above data items, and may include, for example, a data item such as a “device name” indicating the name of the device 30.

[0105] <Processing details> Next, the details of the processing of the cloud system 1 according to this embodiment will be described.

[0106] <Overall license management process> Hereinafter, a process in which a user of the terminal device 20 (e.g., an administrator of the system environment E) uses the browser 210 to perform license management will be described with reference to Fig. 12. Fig. 12 is a sequence diagram showing an example of a license management process. Note that, hereinafter, as an example, a case in which a user uses the browser 210 of the terminal device 20 will be described, but the browser 310 of the device 30 may also be used.

[0107] The browser 210 accepts an input operation of login information on, for example, a login screen for the user to log in to the cloud server 10 (step S101). The login information is information input by the user on the login screen, and includes, for example, a set of a user ID and a password input by the user, and a tenant ID input by the user.

[0108] When the browser 210 accepts the input operation of the login information, the browser 210 transmits a login request to the cloud server 10 (step S102). The login request includes the login information.

[0109] When the Web service unit 101 receives the login request, it transmits the login request to the authentication unit 102 (step S103).

[0110] When the authentication unit 102 receives the login request, the authentication unit 102 performs login authentication by referring to the authentication information stored in the authentication information storage unit 110 (step S104). That is, the authentication unit 102 performs login authentication by determining whether or not the same authentication information as a pair of a user ID and a password included in the login information is stored in the authentication information storage unit 110, for example.

[0111] Then, authentication unit 102 returns the authentication result of the login authentication to Web service unit 101. Hereinafter, it is assumed that authentication unit 102 has returned to Web service unit 101 the authentication result indicating that login authentication was successful.

[0112] When the authentication result indicating that the login authentication was successful is returned from the authentication unit 102, the Web service unit 101 generates a menu screen which is the first screen to be displayed after the user logs in to the cloud server 10 (step S105). In the menu screen, the screen to be displayed on the browser 210 is defined by, for example, HTML (HyperText Markup Language) or CSS (Cascading Style Sheets), etc.

[0113] Then, the Web service unit 101 returns the generated menu screen to the browser 210.

[0114] When the menu screen is returned from the Web service unit 101, the browser 210 displays, for example, the menu screen G100 shown in Fig. 13 (step S106). The menu screen G100 shown in Fig. 13 includes a device management icon G110 and a package management icon G120. The user can transition to the device management screen G200 shown in Fig. 13 by selecting the device management icon G110. The user can transition to the package management screen G300 shown in Fig. 13 by selecting the package management icon G120.

[0115] The device management screen G200 is a screen for assigning a license to a device 30 having a device ID as a starting point, or releasing a license assigned to a device 30 having a device ID as a starting point. On the other hand, the package management screen G300 is a screen for assigning a license having a license ID as a starting point, or releasing a license having a license ID from a device 30 to which the license has been assigned as a starting point, or assigning a license having a license ID to a device 30 as a starting point.

[0116] Hereinafter, it is assumed that the user has performed a selection operation of either the device management icon G110 or the package management icon G120.

[0117] The menu screen G100 shown in Fig. 13 includes an administrator menu and a general user menu. For example, if the user has administrator authority, the administrator menu and the general user menu are displayed, whereas if the user has general authority, only the general user menu is displayed. Therefore, in order to select the device management icon G110 or the package management icon G120, the user needs to log in to the cloud server 10 using a user ID or the like having at least administrator authority.

[0118] The browser 210 accepts a selection operation of the device management icon G110 or a selection operation of the package management icon G120 (step S107).

[0119] When the browser 210 receives a selection operation of the device management icon G110, the processes of steps S108 to S112 described below are executed. On the other hand, when the browser 210 receives a selection operation of the package management icon G120, the processes of steps S113 to S117 described below are executed.

[0120] When the browser 210 receives a selection operation of the device management icon G110 in the above step S107, the browser 210 transmits a display request for a device management screen to the cloud server 10 (step S108). The display request for the device management screen includes the tenant ID input by the user. Note that, for example, in a case where the tenant ID included in the login information transmitted in the above step S102 is held in the cloud server 10, it is not necessary to include the tenant ID in the display request.

[0121] When the Web service unit 101 receives the display request for the device management screen, the Web service unit 101 transmits a request for acquiring a device list to the device management unit 105 (step S109). The request for acquiring the device list includes the tenant ID.

[0122] When the device management unit 105 receives a request to acquire a device list, the device management unit 105 acquires a list of device information in which the tenant ID included in the acquisition request is set (hereinafter, also referred to as a "device list") (step S110). That is, the device management unit 105 acquires, as the device list, device information in which the tenant ID is included among the device information stored in the device information storage unit 170.

[0123] Then, the device management unit 105 returns the obtained device list to the Web service unit 101.

[0124] When the device list is returned from the device manager 105, the Web service unit 101 generates a device management screen based on the device list (step S111). In the device management screen, a screen to be displayed on the browser 210 is defined by, for example, HTML, CSS, etc.

[0125] Then, the Web service unit 101 returns the generated device management screen to the browser 210.

[0126] When the device management screen is returned from the Web service unit 101, the browser 210 displays, for example, the device management screen G200 shown in Fig. 13 (step S112). On the device management screen G200 shown in Fig. 13, the user can release and assign licenses using the device ID as a starting point.

[0127] 13 includes a device list display field G210 in which the device IDs of devices 30 owned or used by the tenant of the tenant ID are displayed in a list as "device IDs in use". The device list display field G210 also displays a "device description" indicating information such as which floor of which building the device 30 is installed. The list of device IDs in use displayed in the device list display field G210 is generated based on the device list acquired in step S110.

[0128] Furthermore, the device management screen G200 shown in FIG. 13 includes a check box G220 for selecting an in-use device ID from the device list display field G210.

[0129] The user can select a desired in-use device ID from the check box G220 and then select the delete button G230 to release the license assigned to the device 30 indicated by the selected in-use device ID and delete the device information of the device 30. This allows the user to easily release the license assigned to the original device 30 when, for example, replacing the device 30.

[0130] Furthermore, the user can select the edit button G240 to release some of the licenses of the device 30 indicated by the in-use device ID corresponding to the edit button G240. This allows the user to easily release only some of the licenses assigned to the selected device 30.

[0131] Furthermore, by selecting the add button G250, the user can assign a license to the device 30 indicated by the in-use device ID corresponding to the add button G250. This allows the user to easily assign a license to the replacement device 30 when, for example, replacing the device 30.

[0132] The process of assigning a license from the device management screen G200 shown in FIG. 13 and the process of releasing a license from the device management screen G200 shown in FIG. 13 will be described in detail later.

[0133] Returning to Fig. 12, when the browser 210 accepts the selection operation of the package management icon G120 in the above step S107, it transmits a display request for the package management screen to the cloud server 10 (step S113). The display request for the package management screen includes the tenant ID entered by the user. Note that, for example, in a case where the tenant ID included in the login information transmitted in the above step S102 is held in the cloud server 10, it is not necessary to include the tenant ID in the display request.

[0134] When the Web service unit 101 receives the display request for the package management screen, it transmits a request for acquiring a list of packages in use to the license management unit 104 (step S114). The request for acquiring a list of packages in use includes the tenant ID.

[0135] When the license management unit 104 receives the request to acquire the list of packages in use, it acquires a list of license information in which the tenant ID included in the acquisition request is set (hereinafter, also referred to as the "list of packages in use") (step S115). That is, the license management unit 104 acquires, as the list of packages in use, license information that includes the tenant ID from among the license information stored in the license information storage unit 160. At this time, the license management unit 104 may acquire, as the list of packages in use, license information that includes the tenant ID and at least one device ID.

[0136] Since the license information including the tenant ID is information indicating the license of a package that the tenant of the tenant ID has purchased and become available for use, in this embodiment, a list of such license information is expressed as a "list of packages in use." However, this is a notation for convenience, and such a list of license information may also be expressed as a "list of licenses in use," etc.

[0137] The license management unit 104 then returns the acquired list of packages in use to the Web service unit 101.

[0138] When the list of packages in use is returned from the license management unit 104, the Web service unit 101 generates a package management screen based on the list of packages in use (step S116). In the package management screen, the screen to be displayed on the browser 210 is defined by, for example, HTML, CSS, etc.

[0139] Then, the Web service unit 101 returns the generated package management screen to the browser 210.

[0140] When the package management screen is returned from the Web service unit 101, the browser 210 displays, for example, a package management screen G300 shown in Fig. 13 (step S117). On the package management screen G300 shown in Fig. 13, the user can release and assign licenses starting from a package name (license name).

[0141] The package management screen G300 shown in Fig. 13 includes a package-in-use list display field G310 in which the license names of packages purchased by the tenant of the tenant ID are displayed in a list as "package-in-use names". The package management screen G300 shown in Fig. 13 also includes a check box G320 for selecting a package-in-use name from the package-in-use list display field G310. The list of package-in-use names (i.e., license names) displayed in the package-in-use list display field G310 is generated based on the package-in-use list acquired in step S115 above.

[0142] The reason why the license name is displayed as "Package in Use Name" in the package in use list display field G310 is that it is more convenient for the user to display the license name as "Package in Use Name" since the user purchases applications on a package-by-package basis. For example, if the package name of the package purchased by the user is "Storage A Package", the license name for this package will be "Storage A Package License" or the like.

[0143] However, this is not limited to the case where the license names included in the license information are displayed as in-use package names in the package-in-use list display field G310. For example, in the above step S115, package information corresponding to the acquired license information may also be acquired, and the package names included in the acquired package information may be displayed as in-use package names in the package-in-use list display field G310. Also, for example, in the above step S115, service information corresponding to the acquired license information may also be acquired, and the service names included in the acquired service information may be displayed as in-use package names in the package-in-use list display field G310.

[0144] The user can select a desired in-use package name from the check box G320 and then select the release button G330 to release the license indicated by the selected in-use package name from the device 30 to which the license is assigned. This allows the user to easily release all licenses assigned to devices 30 that use a particular package at once, for example, when discontinuing the use of that package.

[0145] Furthermore, by selecting the edit button G340, the user can release the license of some of the devices 30 to which the license indicated by the in-use package name corresponding to the edit button G340 is assigned. This allows the user to easily release the license assigned to the devices 30 that are using a particular package, for example, when the user wants to stop using only some of the devices 30.

[0146] Furthermore, by selecting the Add button G350, the user can assign the license indicated by the in-use package name corresponding to the Add button G350 to the device 30. This allows the user to easily assign the license when, for example, he / she wishes to assign a license for a certain package to a certain device 30.

[0147] The process of assigning a license from the package management screen G300 shown in FIG. 13 and the process of releasing a license from the package management screen G300 shown in FIG. 13 will be described later in detail.

[0148] <<Process to cancel license from the device management screen G200>> The process of releasing a license from the device management screen G200 shown in Fig. 13 will be described below with reference to Fig. 14. Fig. 14 is a sequence diagram showing an example of the license release process from the device management screen G200.

[0149] The browser 210 accepts a selection operation of the delete button G230 or a selection operation of the edit button G240 (step S201). Note that, before selecting the delete button G230, the user selects a desired device ID in use from the check box G220.

[0150] When the browser 210 accepts the selection operation of the delete button G230, the processing of steps S202 to S209 described below is executed. At this time, the user can also select multiple in-use device IDs from the check boxes G220. In this case, the processing of steps S202 to S206 is executed for each selected in-use device ID, and then the processing of steps S207 to S209 is executed.

[0151] On the other hand, when the browser 210 accepts a selection operation of the edit button G240, the processes of steps S210 to S221, which will be described later, are executed.

[0152] When the browser 210 receives a selection operation of the delete button G230 in step S201, the browser 210 transmits a request to delete the device information to the cloud server 10 (step S202). The request to delete the device information includes the device ID (device ID in use) selected from the check box G220 and the tenant ID.

[0153] When the Web service unit 101 receives the request to delete the device information, the Web service unit 101 transmits the request to delete the device information to the device management unit 105 (step S203).

[0154] When the device management unit 105 receives the request to delete the device information, the device management unit 105 transmits a license release request to the license management unit 104 (step S204). The license release request includes the device ID and the tenant ID.

[0155] When the license management unit 104 receives the license release request, it releases all licenses assigned to the device 30 indicated by the device ID included in the release request (step S205). That is, the license management unit 104 identifies license information that includes the device ID and tenant ID from among the license information stored in the license information storage unit 160, and deletes the device ID from the "device ID in use" of the identified license information. Then, the license management unit 104 returns the release result to the device management unit 105.

[0156] As a result, all licenses assigned to the device 30 with that device ID are released.

[0157] For example, if the same device ID is not used between different tenants (specifically, for example, if a serial number or the like is used as the device ID), the license release request does not need to include the tenant ID. In this case, in step S205, among the license information stored in the license information storage unit 160, license information including the device ID is identified, and the device ID is deleted from the "device ID in use" of the identified license information.

[0158] When the device management unit 105 receives the release result from the license management unit 104, the device management unit 105 deletes the device information including the device ID from the device information storage unit 170 (step S206).

[0159] Next, the device management unit 105 acquires a list of devices in which the tenant ID included in the request to delete the device information is set (step S207). As a result, the device list excluding the device information deleted in step S206 is acquired.

[0160] Then, the device management unit 105 returns the obtained device list to the Web service unit 101.

[0161] When the device list is returned from the device manager 105, the Web service unit 101 generates a device management screen based on the device list (step S208). Then, the Web service unit 101 returns the generated device management screen to the browser 210.

[0162] When the device management screen is returned from the Web service unit 101, the browser 210 displays, for example, the device management screen G200 shown in Fig. 13 (step S209). However, in the device list display field G210 of this device management screen G200, device IDs excluding the device IDs included in the device information deleted in step S206 above are displayed as a list of currently used device IDs.

[0163] As a result, the user can release all licenses assigned to the device 30 with the device ID selected on the device management screen G200 shown in Fig. 13. Moreover, the user can easily release the licenses by simply selecting a desired device ID from the device list display field G210 while referring to the "Device Description" and pressing the Delete button G230. Therefore, for example, when replacing the device 30, it is possible to reduce the effort required to identify the device ID of the device 30 to be replaced, and also to prevent erroneous input of the device ID manually.

[0164] Returning to Fig. 14, on the other hand, when the browser 210 receives a selection operation of the edit button G240 in the above step S201, it transmits a display request for the allocated package screen to the cloud server 10 (step S210). The display request for the allocated package screen includes the device ID (device in use ID) corresponding to the selected edit button G240 and the tenant ID.

[0165] When the Web service unit 101 receives the request to display the allocated package screen, it transmits a request to acquire the allocated package list to the device management unit 105 (step S211). The request to acquire the allocated package list includes the device ID, the tenant ID, and "in use" which indicates that the license status is valid.

[0166] When the device management unit 105 receives the request to obtain the allocated package list, the device management unit 105 transmits the request to the license management unit 104 (step S212).

[0167] When the license management unit 104 receives the request to acquire the allocated package list, it acquires a list of license information in which the tenant ID and device ID included in the acquisition request and In Use are set (hereinafter, also referred to as an "allocated package list") (step S213). That is, the license management unit 104 acquires, from the license information stored in the license information storage unit 160, license information that includes the tenant ID and device ID and has a license status of In Use, as the allocated package list.

[0168] The license management unit 104 then returns the acquired list of currently allocated packages to the device management unit 105. Thereafter, the device management unit 105 returns the list of currently allocated packages returned from the license management unit 104 to the Web service unit 101.

[0169] When the allocated package list is returned from the device management unit 105, the Web service unit 101 generates an allocated package screen based on the allocated package list (step S214). Then, the Web service unit 101 returns the generated allocated package screen to the browser 210.

[0170] When the allocated package screen is returned from the Web service section 101, the browser 210 displays, for example, the allocated package screen G400 shown in FIG. 15 (step S215).

[0171] 15 includes an allocated package name list display field G410 in which the license names of the licenses allocated to the device 30 with the device ID are displayed in a list as "allocated package names." Note that the list of allocated package names displayed in the allocated package name list display field G410 is generated based on the allocated package list acquired in step S213 above.

[0172] The user can select a desired allocated package name from the check box G420 and then select the release button G430 to release the license indicated by the selected allocated package name from the device 30. This allows the user to release the license of a particular package, for example, when stopping the use of the particular package allocated to a particular device 30. Hereinafter, it is assumed that the user has selected a desired allocated package name from the check box G420 and performed an operation of selecting the release button G430 (package release operation). Note that at this time, the user can also select multiple allocated package names from the check box G420. In this case, the processes of steps S216 to S220 are performed for each selected allocated package name, and then the processes of steps S221 to S222 are performed.

[0173] Browser 210 accepts the package release operation (step S216). Upon accepting the package release operation, browser 210 transmits a package release request to Web service unit 101 (step S217). The package release request includes the device ID of device 30, the tenant ID, and the service ID corresponding to the allocated package name selected from check box G420. Note that the service ID corresponding to the allocated package name is the service ID included in the license information in which the license name displayed as the allocated package name is set.

[0174] When the Web service unit 101 receives the package release request, it transmits the release request to the device management unit 105 (step S218).

[0175] When the device management unit 105 receives the package release request, it transmits a license release request to the license management unit 104 (step S219). The license release request includes the device ID, the tenant ID, and the service ID.

[0176] When the license management unit 104 receives a license release request, it releases the license identified by the tenant ID and service ID from among the licenses assigned to the device 30 identified by the device ID included in the release request (step S220). That is, the license management unit 104 identifies license information including the device ID, tenant ID, and service ID from among the license information stored in the license information storage unit 160, and deletes the device ID from the "device ID in use" of the identified license information. As a result, the license selected by the user (the license corresponding to the assigned package name) from among the licenses assigned to the device 30 with the device ID is released.

[0177] Then, the license management unit 104 returns the release result to the device management unit 105. After that, the device management unit 105 returns the release result returned from the license management unit 104 to the Web service unit 101.

[0178] When the release result is returned from the device manager 105, the Web service unit 101 generates a release result screen (step S221). Then, the Web service unit 101 returns the generated release result screen to the browser 210.

[0179] When the cancellation result screen is returned from the Web service section 101, the browser 210 displays, for example, the cancellation result screen G500 shown in FIG. 15 (step S222).

[0180] The release result screen G500 shown in Fig. 15 displays information indicating that the license corresponding to the allocated package name selected on the allocated package screen G400 shown in Fig. 15 has been released from the device 30 having the device ID selected on the device management screen G200 shown in Fig. 13. The release result screen G500 shown in Fig. 15 also includes a "Yes" button G510 and a "No" button G520 for selecting whether or not to continue with package allocation.

[0181] When the user selects the "Yes" button G510, a screen for assigning a license to the device 30 having the device ID (an allocatable package screen G600, described below) is displayed on the browser 210. On the other hand, when the user selects the "No" button G520, the device management screen G200 shown in FIG. 13 is displayed on the browser 210.

[0182] As a result, the user can release the license of the assigned package name (license name) selected on the assigned package screen G400 shown in Fig. 15 for the device 30 with the device ID selected on the device management screen G200 shown in Fig. 13. Therefore, for example, when the user wants to release only a specific license assigned to a specific device 30, the user can easily release the license without manually inputting the license ID, device ID, etc.

[0183] <<Process to assign licenses from the device management screen G200>> The process of allocating a license from the device management screen G200 shown in Fig. 13 will be described below with reference to Fig. 16. Fig. 16 is a sequence diagram showing an example of the license allocation process from the device management screen G200.

[0184] The browser 210 accepts a selection operation of the Add button G250 (step S301). When the browser 210 accepts the selection operation of the Add button G250, it transmits a display request for an allocatable package screen to the cloud server 10 (step S302). The display request for the allocatable package screen includes the device ID (device in use ID) corresponding to the selected Add button G250 and the tenant ID.

[0185] When the Web service unit 101 receives the request to display the allocatable package screen, it transmits a request to acquire an allocatable package list to the device management unit 105 (step S303). The request to acquire an allocatable package list includes the device ID and the tenant ID.

[0186] When the device management unit 105 receives the request to obtain the allocatable package list, the device management unit 105 transmits the request to the license management unit 104 (step S304).

[0187] When the license management unit 104 receives a request to acquire an allocatable package list, it acquires a list of license information in which the tenant ID included in the acquisition request is set and the device ID included in the acquisition request is not set (hereinafter, also referred to as an allocatable package list) (step S305). That is, the license management unit 104 acquires, from among the license information stored in the license information storage unit 160, license information in which the tenant ID is included and the device ID is not included, as the allocatable package list.

[0188] Then, the license management unit 104 returns the acquired list of allocatable packages to the device management unit 105. Thereafter, the device management unit 105 returns the list of allocatable packages returned from the license management unit 104 to the Web service unit 101.

[0189] When the allocatable package list is returned from the device management unit 105, the Web service unit 101 generates an allocatable package screen based on the allocatable package list (step S306). Then, the Web service unit 101 returns the generated allocatable package screen to the browser 210.

[0190] When the allocable package screen is returned from the Web service section 101, the browser 210 displays, for example, the allocable package screen G600 shown in FIG. 17 (step S307).

[0191] 17 includes an allocatable package list display field G610 in which the license names of licenses that can be assigned to the device 30 of the device ID are displayed in a list as "allocable package names." Note that the list of allocatable package names displayed in the allocatable package list display field G610 is generated based on the currently-allocated package list acquired in step S305 above.

[0192] The user can assign the license indicated by the selected allocable package name to the device 30 by selecting a desired allocable package name from the check box G620 and then selecting the assign button G630. This allows the user to assign the license of a specific package when, for example, the user wants to use the specific package in a specific device 30. Hereinafter, it is assumed that the user has performed an operation of selecting a desired allocable package name from the check box G620 and selecting the assign button G630 (package assignment operation). Note that at this time, the user can also select multiple allocable package names from the check box G620. In this case, the processes of steps S309 to S312 are performed for each selected allocable package name, and then the processes of steps S313 to S316 are performed.

[0193] Browser 210 accepts the package allocation operation (step S308). Upon accepting the package allocation operation, browser 210 transmits a package allocation request to Web service unit 101 (step S309). The package allocation request includes the device ID of device 30, the tenant ID, and the service ID corresponding to the allocatable package name selected from check box G620. Note that the service ID corresponding to the allocatable package name is the service ID included in the license information in which the license name displayed as the allocatable package name is set.

[0194] When the Web service unit 101 receives the package allocation request, it transmits the package allocation request to the device management unit 105 (step S310).

[0195] When the device management unit 105 receives the package allocation request, the device management unit 105 transmits a license allocation request to the license management unit 104 (step S311). The license allocation request includes a device ID, a tenant ID, and a service ID.

[0196] When the license management unit 104 receives the license allocation request, it allocates the license identified by the tenant ID and service ID included in the allocation request to the device 30 indicated by the device ID included in the allocation request (step S312). That is, the license management unit 104 identifies license information including the tenant ID and service ID from among the license information stored in the license information storage unit 160, and adds the device ID to the "device ID in use" of the identified license information. As a result, the license selected by the user (the license corresponding to the allocatable package name) is allocated to the device 30 with the device ID. Then, the license management unit 104 returns the allocation result to the device management unit 105.

[0197] When the allocation result is returned from the license management unit 104, the device management unit 105 transmits an acquisition request for an allocated package list to the license management unit 104 (step S313). The acquisition request for an allocated package list includes the device ID and the tenant ID.

[0198] When the license management unit 104 receives the request to acquire the allocated package list, it acquires the allocated package list in which the tenant ID, device ID, and "In Use" are set, which are included in the acquisition request (step S314). That is, the license management unit 104 acquires, from among the license information stored in the license information storage unit 160, the license information in which the tenant ID and device ID are included and the license status is "In Use," as the allocated package list.

[0199] The license management unit 104 then returns the acquired list of currently allocated packages to the device management unit 105. Thereafter, the device management unit 105 returns the list of currently allocated packages returned from the license management unit 104 and the allocation result to the Web service unit 101.

[0200] When the allocated package list is returned from the device management unit 105, the Web service unit 101 generates an allocated package screen based on the allocated package list (step S315). Then, the Web service unit 101 returns the generated allocated package screen to the browser 210.

[0201] The Web service unit 101 may use the allocation result returned from the device management unit 105 to generate a screen (allocation completion screen) that displays that the license allocation has been completed, and return the screen to the browser 210. As a result, the allocation completion screen is displayed on the browser 210.

[0202] When the allocated package screen is returned from Web service unit 101, browser 210 displays, for example, an allocated package screen G400 as shown in Fig. 15 (step S316). However, in an allocated package name list display field G410 of this allocated package screen G400, the license names indicating the licenses allocated in step S312 above are also displayed as a list of allocated package names.

[0203] As a result, the user can assign a license of the allocatable package name (license name) selected on the allocatable package screen G600 shown in Fig. 17 to the device 30 selected on the device management screen G200 shown in Fig. 13. Therefore, for example, when replacing the device 30, it is possible to reduce the effort required to identify the device ID of the replacement device 30 and also to prevent erroneous input of the device ID, license ID, etc., when they are manually entered.

[0204] <Process to release license from the package management screen G300> The process of releasing a license from the package management screen G300 shown in Fig. 13 will be described below with reference to Fig. 18. Fig. 18 is a sequence diagram showing an example of the license release process from the package management screen G300.

[0205] The browser 210 accepts a selection operation of the release button G330 or a selection operation of the edit button G340 (step S401). Note that, before selecting the release button G330, the user selects a desired in-use package name from the check box G320.

[0206] When the browser 210 accepts a selection operation of the edit button G340, the processes of steps S402 to S415 described below are executed.

[0207] On the other hand, when the browser 210 accepts the selection operation of the release button G330, the processing of steps S416 to S420 described below is executed. At this time, the user can also select multiple in-use package names from the check boxes G320. In this case, the processing of steps S416 to S418 is executed for each selected in-use package, and then the processing of steps S419 to S420 is executed.

[0208] When the browser 210 receives a selection operation of the edit button G340 in step S401, the browser 210 transmits a display request for an allocated device screen to the cloud server 10 (step S402). The display request for the allocated device screen includes the tenant ID and the service ID corresponding to the selected edit button G340. Note that the service ID corresponding to the edit button G340 is the service ID included in the license information in which the license name displayed as the in-use package name corresponding to the edit button G340 is set.

[0209] When the Web service unit 101 receives the request to display the allocated device screen, it transmits a request to acquire the allocated device list to the device management unit 105 (step S403). The request to acquire the allocated device list includes the tenant ID, the service ID, and "in use" which indicates that the license status is valid.

[0210] When the device management unit 105 receives the request to obtain the list of allocated devices, the device management unit 105 transmits a request to obtain license information to the license management unit 104 (step S404).

[0211] When the license management unit 104 receives the license information acquisition request, the license management unit 104 acquires the license information in which the service ID and tenant ID included in the acquisition request are set from the license information storage unit 160 (step S405).

[0212] Then, the license management unit 104 returns the acquired license information to the device management unit 105 .

[0213] When the license information is returned from the license management unit 104, the device management unit 105 acquires a list of device information including the device ID set in the "device ID in use" of the license information from the device information storage unit 170 (hereinafter also referred to as "allocated device list") (step S406). That is, the device management unit 105 acquires, from the device information stored in the device information storage unit 170, device information including the device ID set in the "device ID in use" of the license information as the allocated device list.

[0214] Then, the device management unit 105 returns the acquired list of allocated devices to the Web service unit 101.

[0215] When the allocating device list is returned from the device management unit 105, the Web service unit 101 generates an allocating device screen based on the allocating device list (step S407). Then, the Web service unit 101 returns the generated allocating device screen to the browser 210.

[0216] When the allocated device screen is returned from the Web service unit 101, the browser 210 displays, for example, the allocated device screen G700 shown in FIG. 19 (step S408).

[0217] 19 includes an assigned device list display field G710 in which the device IDs of the devices 30 to which the license indicated by the license information is assigned are displayed in a list as "assigned device IDs." The assigned device list display field G710 also displays a "device description." The list of assigned device IDs displayed in the assigned device list display field G710 is generated based on the assigned device list acquired in step S406 above.

[0218] The allocated device screen G700 shown in FIG. 19 also includes a check box G720 for selecting an allocated device ID from the allocated device list display field G710.

[0219] The user can select a desired assigned device ID from the check box G720 and then select the release button G730 to select a release device. By selecting a release device, it is possible to release the license indicated by the license information among the licenses assigned to the device 30 indicated by the selected assigned device ID. This allows the user to easily release the license of the device 30 when, for example, the user wishes to stop using a particular device 30 among the devices 30 to which a license of a particular package is assigned.

[0220] The browser 210 accepts a selection operation for a release device (step S409). At this time, the user can select multiple assigned device IDs from the check boxes G720. In this case, the processes of steps S410 to S413 are executed for each selected assigned device ID, and then the processes of steps S414 to S415 are executed.

[0221] When the browser 210 accepts the selection operation of the release device, it transmits a package release request to the Web service unit 101 (step S410). The package release request includes the device ID (allocated device ID) selected from the check box G720, the tenant ID, and the service ID corresponding to the in-use package name selected on the package management screen G300 shown in FIG.

[0222] When the Web service unit 101 receives the package release request, it transmits the release request to the device management unit 105 (step S411).

[0223] When the device management unit 105 receives the package release request, it transmits a license release request to the license management unit 104 (step S412). The license release request includes the device ID, the tenant ID, and the service ID.

[0224] When the license management unit 104 receives the license release request, it releases the license identified by the tenant ID and service ID from among the licenses assigned to the device 30 identified by the device ID included in the release request (step S413). That is, the license management unit 104 identifies license information that includes the device ID, tenant ID, and service ID from among the license information stored in the license information storage unit 160, and then deletes the device ID from the "device ID in use" of the identified license information. As a result, the license of the package corresponding to the service ID is released from the device 30 selected by the user.

[0225] Then, the license management unit 104 returns the release result to the device management unit 105. After that, the device management unit 105 returns the release result returned from the license management unit 104 to the Web service unit 101.

[0226] When the release result is returned from the device manager 105, the Web service unit 101 generates a release result screen (step S414). Then, the Web service unit 101 returns the generated release result screen to the browser 210.

[0227] When the cancellation result screen is returned from the Web service section 101, the browser 210 displays, for example, the cancellation result screen G800 shown in FIG. 19 (step S415).

[0228] The release result screen G800 shown in Fig. 19 displays information indicating that the license corresponding to the in-use package name selected on the package management screen G300 shown in Fig. 13 has been released from the device 30 having the device ID selected on the assigned device screen G700 shown in Fig. 19. The release result screen G800 shown in Fig. 19 also includes a "Yes" button G810 and a "No" button G820 for selecting whether or not to continue with package allocation.

[0229] If the user selects the "Yes" button G810, a screen for assigning the license to the device 30 (an allocatable device screen G900, described later) is displayed on the browser 210. On the other hand, if the user selects the "No" button G820, the browser 210 displays the package management screen G300 shown in FIG.

[0230] As a result, the user can release the license of the in-use package name (license name) selected on the package management screen G300 shown in Fig. 13 from the device 30 with the device ID selected on the assigned device screen G700 shown in Fig. 19. Therefore, for example, when the user wants to release the license of only a specific device 30 for a specific package, the user can easily release the license without manually inputting the license ID, device ID, etc.

[0231] Returning to Fig. 18, on the other hand, when the browser 210 receives a selection operation of the release button G330 in the above step S401, the browser 210 transmits a package release request to the cloud server 10 (step S416). The package release request includes the service ID corresponding to the in-use package name selected from the check box G320, and the tenant ID.

[0232] When the Web service unit 101 receives the package release request, it transmits the release request to the license management unit 104 (step S417).

[0233] When the license management unit 104 receives a license release request, it releases the license from the device 30 to which the license corresponding to the service ID and tenant ID included in the release request is assigned (step S418). That is, the license management unit 104 identifies license information that includes the service ID and tenant ID from among the license information stored in the license information storage unit 160, and deletes all device IDs from the "device ID in use" of the identified license information. This releases the license from the device 30 to which the license is assigned. Then, the license management unit 104 returns the release result to the Web service unit 101.

[0234] When the release result is returned from the device management unit 105, the Web service unit 101 generates a release result screen (step S419). Then, the Web service unit 101 returns the generated device management screen to the browser 210.

[0235] When the cancellation result screen is returned from the Web service section 101, the browser 210 displays, for example, the cancellation result screen G800 shown in FIG. 19 (step S420).

[0236] In this way, the user can release the license of the in-use package name (license name) selected on the package management screen G300 shown in Fig. 13 from all devices 30 to which the license is assigned. Therefore, for example, when discontinuing the use of a certain package, the user can easily release the licenses of all devices 30 using the package at once without manually inputting the license ID, device ID, etc.

[0237] <Process to assign licenses from the Package Management Screen G300> The process of allocating a license from the package management screen G300 shown in Fig. 13 will be described below with reference to Fig. 20. Fig. 20 is a sequence diagram showing an example of the license allocation process from the package management screen G300.

[0238] The browser 210 accepts the selection operation of the Add button G350 (step S501). When the browser 210 accepts the selection operation of the Add button G350, it transmits a display request of an allocatable device screen to the cloud server 10 (step S502). The display request of the allocatable device screen includes the service ID corresponding to the selected Add button G350 and the tenant ID. The service ID corresponding to the Add button G350 is the service ID of the service information corresponding to the license information including the in-use package name (license name) corresponding to the Add button G350.

[0239] When the Web service unit 101 receives the request to display the allocatable device screen, it transmits a request to acquire the allocatable device list to the device management unit 105 (step S503). The request to acquire the allocatable device list includes the service ID and the tenant ID.

[0240] When the device management unit 105 receives the request to acquire the allocatable device list, the device management unit 105 transmits a request to acquire license information to the license management unit 104 (step S504). The request to acquire license information includes the service ID and the tenant ID.

[0241] When the license management unit 104 receives the license information acquisition request, the license management unit 104 acquires the license information in which the service ID and tenant ID included in the acquisition request are set from the license information storage unit 160 (step S505).

[0242] Then, the license management unit 104 returns the acquired license information to the device management unit 105 .

[0243] When the license information is returned from the license management unit 104, the device management unit 105 acquires a list of device information of devices 30 to which the license indicated by the license information can be assigned (hereinafter also referred to as an "assignable device list") from the device information storage unit 170 (step S506). That is, the device management unit 105 acquires, from the device information storage unit 170, device information that includes the tenant ID and that includes a device ID that is not set as "device ID in use" in the license information, as the allocatable device list.

[0244] Then, the device management unit 105 returns the acquired list of allocatable devices to the Web service unit 101.

[0245] When the allocatable device list is returned from the device management unit 105, the Web service unit 101 generates an allocatable device screen based on the allocatable device list (step S507). Then, the Web service unit 101 returns the generated allocatable device screen to the browser 210.

[0246] When the allocatable device press screen is returned from the Web service unit 101, the browser 210 displays, for example, the allocatable device screen G900 shown in FIG. 21 (step S508).

[0247] 21 includes an allocatable device list display field G910 in which the device IDs of devices 30 to which the license indicated by the license information can be allocated (i.e., to which the license has not been allocated) are displayed in a list as "allocatable device IDs." Note that the list of allocatable device IDs displayed in the allocatable device list display field G910 is generated based on the allocatable device list acquired in step S506 above.

[0248] The user can assign the license to the device 30 indicated by the selected allocatable device ID by selecting a desired allocatable device ID from the check box G920 and then selecting the assign button G630. In this way, when the user wants to use a certain package in a certain device 30, the user can assign the license of the package to the device 30. Hereinafter, it is assumed that the user selects a desired allocatable device ID from the check box G920 and performs an operation of selecting the assign button G930 (allocation device selection operation). Note that at this time, the user can also select multiple allocatable device IDs from the check box G920. In this case, the processes of steps S510 to S513 are performed for each selected allocatable device ID, and then the processes of steps S514 to S516 are performed.

[0249] The browser 210 accepts the operation of selecting the device to be allocated (step S509). When the browser 210 accepts the operation of selecting the device to be allocated, it transmits a package allocation request to the Web service unit 101 (step S510). The package allocation request includes the device ID (allocatable device ID) selected from the check box G920, the tenant ID, and the service ID corresponding to the in-use package name selected on the package management screen G300 shown in FIG.

[0250] When the Web service unit 101 receives the package allocation request, it transmits the package allocation request to the device management unit 105 (step S511).

[0251] When the device management unit 105 receives the package allocation request, it transmits a license allocation request to the license management unit 104 (step S512). The license allocation request includes the device ID, the tenant ID, and the service ID.

[0252] When the license management unit 104 receives the license allocation request, it allocates the license identified by the tenant ID and service ID included in the allocation request to the device 30 identified by the device ID included in the allocation request (step S513). That is, the license management unit 104 identifies license information including the tenant ID and service ID from among the license information stored in the license information storage unit 160, and adds the device ID to the "device ID in use" of the identified license information. As a result, the license is allocated to the device 30 selected by the user (the device 30 identified by the allocatable device ID). Then, the license management unit 104 returns the allocation result to the device management unit 105.

[0253] When the allocation result is returned from the license management unit 104, the device management unit 105 acquires a list of allocated devices from the device information storage unit 170 (step S514). Then, the device management unit 105 returns the acquired list of allocated devices and the allocation result to the Web service unit 101.

[0254] When the allocating device list is returned from the device management unit 105, the Web service unit 101 generates an allocating device screen based on the allocating device list (step S515). Then, the Web service unit 101 returns the generated allocating device screen to the browser 210.

[0255] The Web service unit 101 may generate an allocation completion screen using the allocation result returned from the device management unit 105, and return the screen to the browser 210. As a result, the allocation completion screen is displayed on the browser 210.

[0256] When the allocating device screen is returned from the Web service unit 101, the browser 210 displays, for example, an allocating device screen G700 as shown in Fig. 19 (step S516). However, in an allocating device list display field G710 of this allocating device screen G700, the device IDs of the devices 30 to which the license was allocated in step S513 above are also displayed as a list of allocating device IDs.

[0257] As a result, the user can assign the license of the in-use package name (license name) selected on the package management screen G300 shown in Fig. 13 to the device 30 with the device ID selected on the allocatable device screen G900 shown in Fig. 21. Therefore, for example, when a certain specific package is to be used only by a certain specific device 30, the user can easily assign the license without manually inputting the license ID, device ID, etc.

[0258] The present invention is not limited to the above-described embodiments specifically disclosed, and various modifications and variations are possible without departing from the scope of the claims. [Explanation of symbols]

[0259] 1. Cloud System 10. Cloud Server 20 Terminal Equipment 30 equipment 101 Web Services Department 102 Authentication Department 103 Application Management Department 104 License Management Department 105 Device Management Department 110 Authentication information storage unit 120 Package information storage unit 130 Application information storage unit 140 Application setting information storage unit 150 Service information storage unit 160 License information storage unit 170 Device information storage unit 210 Browser 310 Browser [Prior art documents] [Patent documents]

[0260] [Patent Document 1] JP 2017-083982 A

Claims

1. An information processing device that is connected to a terminal via a network and manages licenses of a package including one or more applications used by the device, a display means for displaying, in response to a first request from the terminal, a first screen including a list of devices to which a license of the package can be assigned or released; a license management means for allocating the license to the selected device or releasing the license from the selected device in response to a selection of a device from the list of devices included in the first screen and an operation for the allocation or release; 13. An information processing device comprising:

2. The license management means 2. The information processing device according to claim 1, further comprising: a device selection unit that selects a device from the list of devices included on the first screen and a user operation for canceling all licenses assigned to the selected device, the device selection unit releasing all licenses assigned to the selected device.

3. The display means includes: displaying on the terminal a second screen including a list of packages available under the licenses assigned to the selected device in response to a selection of the device from the list of devices included in the first screen and an operation for releasing a part of the licenses assigned to the selected device; The license management means 3. The information processing device according to claim 1, further comprising: a device selected on the first screen that is provided with a package and a license for the package selected on the second screen is released from the device selected on the first screen in response to a selection of the package from the list of packages included on the second screen.

4. The display means includes: displaying, on the terminal, a third screen including a list of packages corresponding to licenses that can be assigned to the selected device in response to a selection of a device from the list of devices included in the first screen and an operation for assigning a license to the selected device; The license management means 4. The information processing device according to claim 1, further comprising: a device selected on the first screen that is provided with a license for a package selected on the third screen, the device selected on the first screen being assigned a license for the package selected on the third screen in response to a selection of the package from the list of packages included on the third screen.

5. The display means includes: displaying, in response to a second request from the terminal, a fourth screen including a list of packages corresponding to licenses that can be assigned to the device or released from the device, on the terminal; The license management means An information processing device as described in any one of claims 1 to 4, characterized in that a license for the selected package is assigned to the device or the license for the selected package is released from the device in response to a selection of a package from the list of packages included in the fourth screen and an operation for the allocation or release.

6. The license management means 6. The information processing device according to claim 5, wherein, in response to a selection of a package from the list of packages included in the fourth screen and an operation method for releasing all licenses of the selected package, the licenses are released from all devices to which the licenses of the selected package are assigned.

7. The display means includes: displaying on the terminal a fifth screen including a list of devices from which the license of the selected package can be released in response to a selection of a package from the list of packages included in the fourth screen and an operation for releasing the license from a portion of devices to which the package is assigned; The license management means 7. The information processing apparatus according to claim 5, further comprising: a device selection unit that selects a device from the list of devices included in the fifth screen, and releases a license for the package selected on the fourth screen from the device selected on the fourth screen.

8. The display means includes: displaying on the terminal a sixth screen including a list of devices to which a license of the selected package can be assigned in response to a selection of a package from the list of packages included in the fourth screen and an operation for assigning a license of the selected package to a device; The license management means 8. The information processing device according to claim 5, further comprising: a device selection unit that selects a device from the list of devices included in the sixth screen, and assigns a license for a package selected on the fourth screen to the device selected on the sixth screen.

9. An information processing system that is connected to a terminal via a network and manages licenses for a package including one or more applications used by the device, comprising: a display means for displaying, in response to a first request from the terminal, a first screen including a list of devices to which a license of the package can be assigned or released; a license management means for allocating the license to the selected device or releasing the license from the selected device in response to a selection of a device from the list of devices included in the first screen and an operation for the allocation or release; An information processing system comprising:

Images