Information processing device and information processing system

Abstract

Simplifies license management. [Solution] An information processing device that manages licenses for a package containing one or more applications used by a device, which is connected to a terminal via a network, and is characterized by comprising: display means that, in response to a first request from the terminal, displays on the terminal a first screen containing a list of devices to which licenses for the package can be assigned or unassigned; and license management means that, in response to the selection of a device from the list of devices contained on the first screen and an operation for assigning or unassigning, assigns the license to the selected device or unassigns the license from the selected device.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus and an information processing system.

Background Art

[0002] In recent years, due to the progress of technologies such as cloud computing, various applications have been provided as cloud services for devices such as multifunction peripherals (MFPs). For example, applications such as an application for storing an image file scanned by a multifunction printer in an external storage and an application for printing an electronic file downloaded from an external storage using a multifunction printer are provided as cloud services. Such an application can be used, for example, by allocating a license for using the application to the device.

[0003] Also, a technique for issuing an updated license to an image forming apparatus after replacement when replacement of the image forming apparatus occurs after the start of a license contract is known (see, for example, Patent Document 1).

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the above prior art, it was necessary for the user to input identification information (for example, a serial number) for identifying the replacement image forming apparatus. For this reason, the user had to, for example, operate the replacement image forming apparatus to display the serial number or check a sticker (a sticker on which a serial number or the like is described) attached to the replacement image forming apparatus.

[0005] Therefore, it has been troublesome to manage licenses when replacement of an image forming apparatus or the like occurs.

[0006] Embodiments of the present invention have been made in view of the above points, and aim to facilitate license management. [Means for solving the problem]

[0007] To achieve the above objective, an embodiment of the present invention is an information processing device connected to a terminal via a network and for managing licenses for a package containing one or more applications used by a device, comprising: display means for displaying a first screen on the terminal that includes a list of devices to which licenses for the package can be assigned or unassigned in response to a first request from the terminal; and license management means for assigning the license to the selected device or unassigning the license from the selected device in response to the selection of a device from the list of devices included on the first screen and an operation for assigning or unassigning the license. [Effects of the Invention]

[0008] License management can be made easier. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of the overall configuration of the cloud system according to this embodiment. [Figure 2] This figure shows an example of a computer hardware configuration. [Figure 3] This figure shows an example of the hardware configuration when the device according to this embodiment is an image forming apparatus. [Figure 4] This figure shows an example of the functional configuration of the cloud system according to this embodiment. [Figure 5] This diagram shows an example of the relationship between package information, app information, app settings information, service information, and device information. [Figure 6] This figure shows an example of package information. [Figure 7] This figure shows an example of app information. [Figure 8]It is a diagram showing an example of application setting information. [Figure 9] It is a diagram showing an example of service information. [Figure 10] It is a diagram showing an example of license information. [Figure 11] It is a diagram showing an example of device information. [Figure 12] It is a sequence diagram showing an example of license management processing. [Figure 13] It is a diagram showing an example of a menu screen, a device management screen, and a package management screen. [Figure 14] It is a sequence diagram showing an example of license cancellation processing from the device management screen. [Figure 15] It is a diagram showing an example of a pending package screen and a cancellation result screen. [Figure 16] It is a sequence diagram showing an example of license allocation processing from the device management screen. [Figure 17] It is a diagram showing an example of an allocable package screen. [Figure 18] It is a sequence diagram showing an example of license cancellation processing from the package management screen. [Figure 19] It is a diagram showing an example of a pending device screen and a cancellation result screen. [Figure 20] It is a sequence diagram showing an example of license allocation processing from the package management screen. [Figure 21] It is a diagram showing an example of an allocable device screen.

Mode for Carrying Out the Invention

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

[0011] <Overall Configuration> First, the overall configuration of the cloud system 1 according to the present embodiment will be described with reference to FIG. 1. FIG. 1 is a diagram showing an example of the overall configuration of the cloud system 1 according to the present 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 the system environment E of the user who uses the device 30, and are communicably connected via a network N2 such as a LAN (Local Area Network). Further, the cloud server 10 and the system environment E are communicably connected via a network N1 such as the Internet. Note that the network N1 and the network N2 may be either wired or wireless, or may be a mixture of wired and wireless.

[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 an "application".

[0014] Specific examples of cloud applications include, for example, an application that stores image data generated by scanning with a device 30 such as a multifunction device in an external storage, and an application that prints an electronic file acquired from an external storage with the device 30.

[0015] Note that the application provided by the cloud server 10 according to this embodiment is described as a cloud-type application, but is not limited thereto. 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] Further, the cloud server 10 manages the applications provided to the device 30, the licenses of the applications, and the like.

[0017] Terminal device 20 is an information processing device (computer) used, for example, by the administrator of system environment E. Specific examples of terminal device 20 include PCs (personal computers), smartphones, tablet devices, etc.

[0018] For example, the administrator of system environment E can use terminal device 20 to manage application licenses (e.g., assigning licenses to equipment 30 or removing licenses assigned to equipment 30). Therefore, for example, if equipment 30 is replaced, the administrator can use terminal device 20 to remove the licenses assigned to the original equipment 30 and assign licenses to the replacement equipment 30.

[0019] Device 30 is, for example, an image forming apparatus such as a multifunction printer (MFP). Device 30 can provide various services to users by utilizing applications provided from the cloud server 10. Device 30 becomes able to use an application once it is assigned a license for that application.

[0020] Note that the configuration of cloud system 1 shown in Figure 1 is just one example, and other configurations are also possible. For example, the cloud server 10 may be an information processing system (computer system) composed of multiple information processing devices. Also, the system environment E may include multiple terminal devices 20. Furthermore, the device 30 is not limited to a multifunction printer, but may be, for example, a digital camera, a printer, a copier, a projector, a facsimile, an electronic conferencing terminal, an electronic whiteboard, an audio device, an in-car 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, the hardware configuration of the cloud server 10 and terminal device 20 according to this embodiment will be described. The cloud server 10 according to this embodiment is implemented by one or more information processing devices and the terminal device 20 according to this embodiment, for example, by the computer 400 shown in Figure 2. Figure 2 is a diagram showing an example of the hardware configuration of the computer 400.

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

[0023] The input device 401 includes a keyboard, mouse, touch panel, etc., and is used by the user to input various operations. The display device 402 includes a display, etc., and displays the processing results from 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] External I / F 403 is an interface to external devices. External devices include recording media 403a, etc. Computer 400 can read from and write to recording media 403a via external I / F 403. Examples of recording media 403a include flexible disks, CDs, DVDs, SD memory cards, USB memory, etc.

[0025] RAM404 is a volatile semiconductor memory that temporarily holds programs and data. ROM405 is a non-volatile semiconductor memory that can retain programs and data even when the power is turned off. ROM405 stores programs and data such as the BIOS (Basic Input / Output System), OS (Operating System) settings, and network settings that are executed when the computer 400 starts up.

[0026] The CPU 406 is an arithmetic unit that controls and implements the overall functions of the computer 400 by reading programs and data from storage devices such as the ROM 405 and auxiliary storage device 408 onto the RAM 404 and executing processing.

[0027] Communication I / F 407 is an interface that connects computer 400 to network N1 and network N2. Computer 400 can communicate data with other devices via communication I / F 407.

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

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

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

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

[0032] ROM33 is a non-volatile semiconductor memory that can retain programs and data even when the power is turned off. RAM32 is a volatile semiconductor memory that temporarily holds programs and data. NVRAM34 is a non-volatile semiconductor memory that stores, for example, configuration information. The auxiliary storage device 35 is a non-volatile storage device that stores programs and data, such as an HDD or SSD.

[0033] The CPU 31 is a computing device that controls and implements the functions of the entire device 30 by reading programs, data, and setting information from ROM 33, NVRAM 34, auxiliary storage device 35, etc., onto RAM 32 and executing processing.

[0034] The control panel 22 is an input / output device equipped with an input section for receiving user input and a display section for displaying information. The external I / F 23 is an interface to an external device. The external device is a recording medium 23a, etc. Device 30 can read from and write to the recording medium 23a via the external I / F 23.

[0035] Examples of recording media 23a include IC cards, flexible disks, CDs, DVDs, SD memory cards, USB memory sticks, etc.

[0036] Communication I / F24 is an interface that connects device 30 to network N2. Device 30 can communicate data with other devices via communication I / F24.

[0037] The plotter 25 is a printing device for printing print data onto a printing medium. The printing medium is not limited to paper; it may also be, for example, an OHP sheet, plastic film, or copper foil. The scanner 26 is a reading device that reads a document and creates image data.

[0038] The device 30 according to this embodiment has the hardware configuration shown in Figure 3, which enables various processes as described later.

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

[0040] ≪Terminal device 20≫ As shown in Figure 4, the terminal device 20 according to this embodiment has a general-purpose web browser 210 (hereinafter simply referred to as "browser 210"). Users of the terminal device 20 (for example, administrators of system environment E) can use browser 210 to manage application licenses.

[0041] ≪Equipment 30≫ As shown in Figure 4, the device 30 according to this embodiment has a general-purpose web browser 310 (hereinafter simply referred to as "browser 310"). Users of the device 30 can use the browser 310 to access applications provided by the cloud server 10.

[0042] ≪Cloud Server 10≫ As shown in Figure 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 implemented by one or more programs installed on the cloud server 10, for example, by having the CPU 406 execute the process.

[0043] Furthermore, the cloud server 10 according to this embodiment includes an authentication information storage unit 110, a package information storage unit 120, an application information storage unit 130, an application configuration 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 implemented using, for example, an auxiliary storage device 408. At least one of these storage units may be implemented using a storage device (for example, a DB server) connected to the cloud server 10 via the network N1.

[0044] The Web service unit 101 generates and returns various screens for the user of the terminal device 20 to manage licenses in response to various requests from the browser 210 of the terminal device 20.

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

[0046] A login request is a request from a user of terminal device 20 to log in to the cloud server 10. By logging in to the cloud server 10, the user of terminal device 20 will be able to manage licenses such as licenses 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 refers to information that indicates a package, which is the sales unit of a product (application). A package contains one or more applications. Application information refers to information that indicates the applications provided to device 30. Application information includes, for example, the name of the application and a description of the application. Application setting information refers to information that indicates the default settings when a user of device 30 uses the application. Application setting information includes, for example, the default settings for print settings and the default settings 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] Service information refers to information that describes the services introduced through the purchase of a package or other means. This service information includes, for example, the service name and a description of the service.

[0051] License information refers to information that indicates the license for each tenant on a package basis. License information includes, for example, identification information that identifies the tenant who purchased the package (e.g., Tenant ID) and identification information that identifies the device 30 that can use the application included in this package (e.g., Device ID).

[0052] A tenant is an organization or group that purchases a package or otherwise uses an application. Specifically, examples of tenants include companies, departments, sections, teams, etc.

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

[0054] Device information refers to information that identifies a device 30 registered on the cloud server 10. Device information includes, for example, identification information that identifies the device 30 and identification information that identifies the tenant that owns or uses the device 30.

[0055] Furthermore, if 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 implemented using different information processing devices.

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

[0057] As shown in Figure 5, there is a one-to-many (one or more) relationship between package information and application information. This indicates that one package contains one or more applications. Furthermore, there is a one-to-one relationship between application information and application settings information. This indicates that for each application, there is one default setting for using that application.

[0058] Furthermore, there is a one-to-one relationship between package information and service information. This indicates that one service is implemented by an application included in one package. Also, there is a one-to-many (zero or more) relationship between service information and license information. This indicates that for a service implemented by an application included in a package purchased by a particular tenant, there are zero or more licenses for the application included in the package that implements this service (including licenses that have expired, and cases where no license exists).

[0059] Furthermore, there is a many-to-many relationship (zero or more) between license information and device information. This means 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 no license is 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 that device 30).

[0060] As described above, in this embodiment, there is a one-to-one relationship between package information and service information, and a one-to-one relationship between service information and license information. This means that when a tenant purchases a package, they are granted a license that allows them to use all the applications included in that package. In other words, in this embodiment, licenses are on a package basis. Therefore, hereafter, the license for using the applications included in a package will also be simply referred to as the "package license."

[0061] Furthermore, the number of devices (30) to which one license can be assigned is predetermined for each package.

[0062] Package information, application information, application settings 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, application information storage unit 130, application settings information storage unit 140, and service information storage unit 150. Device information is created, for example, when a device 30 is newly installed, by a terminal device 20, etc., and is stored in the device information storage unit 170. Furthermore, license information is created, for example, when the administrator of system environment E purchases a package, etc., and is stored in the license information storage unit 160.

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

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

[0065] "Package ID" is an identifier that identifies the package information. "Package Name" is the name of the package.

[0066] In the example shown in Figure 6, the package information for package ID "P001" has "Storage A Package" set as the "Package Name". This indicates that the package information refers to a package that contains an application that interacts with an external storage service, such as "Storage A".

[0067] Similarly, in the package information for package ID "P002," the "Package Name" is set to "Storage B Package." This indicates that the package information refers to a package containing an application that interacts with an external storage service, such as "Storage B."

[0068] The "Package Description" is a description of the package (for example, what applications are included in the package). The "Service ID" is an identifier (for example, a service ID) that identifies the service information associated with the package information. The "App ID List" is a list of identifiers (app IDs) that identify the application information indicating the applications included in the package.

[0069] In the example shown in Figure 6, the package information for package ID "P001" has "APP001", "APP002", etc. set as the "App ID List". This indicates that the package information contains applications identified by App ID "APP001" and applications identified by App ID "APP002", etc.

[0070] Furthermore, package information is not limited to the data items listed above; it 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 explained with reference to Figure 7. Figure 7 is a diagram showing an example of application information.

[0072] As shown in Figure 7, the application information stored in the application information storage unit 130 includes the following data items: "Application ID", "Application Name", "Application Description", "Creation Date", and "Developer Information".

[0073] The "App ID" is an identifier that identifies the application information. The "App Name" is the name of the application.

[0074] In the example shown in Figure 7, the application information for application ID "APP001" has "Scan to Email" set as the "Application Name". This indicates that the application indicated by this application information is, for example, an application that sends image data generated by scanning with device 30 to a specified email address.

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

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

[0077] "App Description" is a description of the application (for example, what kind of application it is). "Creation Date" is the date the application was created. "Developer Information" is information about the developer who created the application (for example, developer name, development department, contact information, etc.).

[0078] Furthermore, the app information may include various data items, not limited to the data items listed above, such as "Release Date" indicating the date the application was released or "Update Date" indicating the date the application was updated.

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

[0080] As shown in Figure 8, the app setting information stored in the app setting information storage unit 140 includes the following data items: "App Setting ID", "App ID", and "Default Setting".

[0081] The "App Settings ID" is an identifier that identifies the app settings information. The "App ID" is an app ID that identifies the app information associated with the app settings information. The "Default Settings" are the default settings when using the application.

[0082] In the example shown in Figure 8, the application settings information for application setting ID "SET001" includes "Resolution = 300dpi" as the "Default setting." This indicates that "Resolution = 300dpi" will be applied as the default setting when using the application indicated by application ID "APP001."

[0083] Furthermore, the app settings information is not limited to the data items listed above; it may also include various other data items, such as a "creation date" indicating the date the app settings information was created.

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

[0085] As shown in Figure 9, the service information stored in the service information storage unit 150 includes the following data items: "Service ID", "Service Name", "Service Description", and "Service Type".

[0086] The "Service ID" is an identifier that identifies the service information. The "Service Name" is the name of the service.

[0087] In the example shown in Figure 9, the service information for service ID "S1111" has "Storage A Integration Service" set as the "Service Name". This indicates that a service that integrates with Storage A is installed by the package indicated by the package information associated with the service information for service ID "S1111".

[0088] Similarly, in the service information for service ID "S2222", "Storage B Integration Service" is set as the "Service Name". This indicates that a service that integrates with Storage B is installed by the package indicated by the package information associated with the service information for service ID "S2222".

[0089] "Service Description" is a description of the service (for example, what kind of service it is). "Service Type" is the type of service. For example, a service type could be "Cloud Service," indicating that it is a cloud-based service. In addition to "Cloud Service," other service types such as "Web Service," indicating that it is a service provided by a web application, may also be set.

[0090] Furthermore, service information is not limited to the data items listed above; it may also include various other data items, such as "price," which is used to determine the price of the package indicated in the package information associated with the service information.

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

[0092] As shown in Figure 10, the license information stored in the license information storage unit 160 includes the following data items: "License ID", "License Name", "Tenant ID", "Start Date", "Scheduled End Date", "End Date", "Status", "Number of Available Devices", "Device ID in Use", and "Service ID".

[0093] The "License ID" is an identifier that identifies the license information. The "License Name" is the name of the license. For example, if the package name is "Storage A Package," the license name for this package would be "Storage A Package License."

[0094] The "Tenant ID" is identification information that identifies the tenant to whom the license has been granted through the purchase of the package or other means.

[0095] The "Start Date" is the date the license became valid (for example, the date the package was purchased or the date the license was activated). The "Expected End Date" is the expected date the license will expire. The "End Date" is the actual date the license expires. If the license has not yet expired, the "End Date" will be set to blank, for example.

[0096] The "Status" refers to the status of the license. The "Status" can be set to, for example, "In Use," indicating that the license is valid, or "Expired," indicating that the license has expired. Note that if the license becomes invalid due to termination of the license agreement before the scheduled expiration date, the "Status" may be set to "Terminated," etc.

[0097] The "Number of Available Devices" is the maximum number of devices (30) on which the application included in the purchased package can be used. If the data item "Status" is set to a value indicating that the application is unavailable, such as "Ended" or "Cancelled," then the "Number of Available Devices" will be set to, for example, a hyphen "-".

[0098] "Device IDs in Use" is a list of device IDs for devices 30 (i.e., devices 30 to which a license has been assigned) that are using the application included in the purchased package. A device ID is identification information that identifies device 30, and can be, for example, the device's unique manufacturing number or serial number. If the data item "Status" is set to a value indicating that the application is unavailable, such as "Ended" or "Cancelled," then "Device IDs in Use" will be set to, for example, a hyphen "-".

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

[0100] Furthermore, license information is not limited to the data items listed above; it may also include other data items such as "Purchase Date," which indicates the date the package was purchased, and "Purchaser Information," which indicates information about the package's purchaser.

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

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

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

[0104] Note that device information is not limited to the data items listed above; it may also include data items such as "device name" indicating the name of the device 30.

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

[0106] ≪Overall License Management Process≫ In the following section, the process for license management when a user of terminal device 20 (for example, an administrator of system environment E) uses browser 210 will be explained with reference to Figure 12. Figure 12 is a sequence diagram showing an example of license management processing. In the following section, the process will be explained as an example when the user uses browser 210 on terminal device 20, but browser 310 on device 30 may also be used.

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

[0108] When the browser 210 receives a request to enter login information, it sends 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 a login request, it sends the login request to the authentication unit 102 (step S103).

[0110] When the authentication unit 102 receives a login request, it 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, for example, whether the authentication information identical to the user ID and password set included in the login information is stored in the authentication information storage unit 110.

[0111] The authentication unit 102 then sends the authentication result of the login authentication back to the web service unit 101. Hereafter, we will assume that the authentication unit 102 has sent an authentication result back to the web service unit 101 indicating that the login authentication was successful.

[0112] When the authentication unit 102 returns an authentication result indicating successful login authentication, the web service unit 101 generates a menu screen, which is the first screen displayed after the user logs into the cloud server 10 (step S105). On the menu screen, the screen to be displayed on the browser 210 is defined using, for example, HTML (HyperText Markup Language) or CSS (Cascading Style Sheets).

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

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

[0115] The device management screen G200 is used to assign licenses to devices 30 associated with a given device ID, or to remove licenses that have been assigned to devices 30 associated with a given device ID. On the other hand, the package management screen G300 is used to remove licenses from devices 30 associated with a given license ID, or to assign licenses to devices 30 associated with a given license ID, starting from a given license ID.

[0116] From this point forward, it will be assumed that the user has either selected the device management icon G110 or the package management icon G120.

[0117] The menu screen G100 shown in Figure 13 includes both an administrator menu and a general user menu. For example, if a user has administrator privileges, both the administrator menu and the general user menu are displayed, while if a user has general privileges, 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 must log in to the cloud server 10 using a user ID that has at least administrator privileges.

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

[0119] If the browser 210 receives a selection operation for the device management icon G110, the processes described in steps S108 to S112 are executed. On the other hand, if the browser 210 receives a selection operation for the package management icon G120, the processes described in steps S113 to S117 are executed.

[0120] If the browser 210 receives the selection operation for the device management icon G110 in step S107 above, it sends a request to display the device management screen to the cloud server 10 (step S108). The request to display the device management screen includes the tenant ID entered by the user. However, if, for example, the tenant ID included in the login information sent in step S102 above is already stored on 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 a request to display the device management screen, it sends a request to the device management unit 105 to retrieve the device list (step S109). The request to retrieve the device list includes the tenant ID.

[0122] When the device management unit 105 receives a request to obtain a device list, it obtains a list of device information (hereinafter also referred to as the "device list") in which the tenant ID included in the acquisition request is set (step S110). In other words, the device management unit 105 obtains the device information that includes the tenant ID from the device information stored in the device information storage unit 170 as the device list.

[0123] Then, the device management unit 105 returns the acquired list of devices to the web service unit 101.

[0124] When the Web service unit 101 receives a list of devices from the device management unit 105, it generates a device management screen based on that list of devices (step S111). The device management screen defines the screen that will be displayed on the browser 210, for example, using HTML or CSS.

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

[0126] When the browser 210 receives a device management screen as a response from the web service unit 101, it displays, for example, the device management screen G200 shown in Figure 13 (step S112). On the device management screen G200 shown in Figure 13, the user can deactivate and assign licenses starting from the device ID.

[0127] The device management screen G200 shown in Figure 13 includes a device list display area G210, which displays a list of device IDs of devices 30 owned or used by the tenant with the relevant tenant ID as "device IDs in use". The device list display area G210 also displays a "device description," which indicates information such as which building and on which floor the device 30 is located. The list of device IDs in use displayed in the device list display area G210 is generated based on the device list obtained in step S110 described above.

[0128] Furthermore, the device management screen G200 shown in Figure 13 includes a checkbox G220 for selecting the currently used device ID from the device list display area G210.

[0129] The user can select the desired active device ID from checkbox G220 and then select the delete button G230 to release the license assigned to the device 30 indicated by the selected active device ID, and then delete the device information for that 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, by selecting the edit button G240, the user can partially deactivate the license for device 30 indicated by the device ID corresponding to the edit button G240. This allows the user to easily deactivate only a portion of the licenses assigned to the selected device 30.

[0131] Furthermore, by selecting the additional button G250, the user can assign a license to the device 30 indicated by the currently used device ID corresponding to that additional button G250. This allows the user to easily assign a license to the replacement device 30, for example, when replacing a device 30.

[0132] Details regarding the process of assigning a license from the device management screen G200 shown in Figure 13, and the process of revoking a license from the device management screen G200 shown in Figure 13, will be described later.

[0133] Return to Figure 12. If the browser 210 receives the selection operation for the package management icon G120 in step S107 above, it sends a request to display the package management screen to the cloud server 10 (step S113). The request to display the package management screen includes the tenant ID entered by the user. However, if, for example, the tenant ID included in the login information sent in step S102 above is held by 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 a request to display the package management screen, it sends a request to the License Management Unit 104 to retrieve a list of packages currently in use (step S114). The request to retrieve a list of packages currently in use includes the tenant ID.

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

[0136] In this embodiment, the license information containing the tenant ID indicates the license for a package that the tenant with that tenant ID has purchased or otherwise made available for use. Therefore, in this embodiment, a list of such license information is referred to as the "List of Packages in Use." However, this is merely a convenient notation, and such a list of license information may also be referred to as the "List of Licenses in Use," etc.

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

[0138] When the Web Service Unit 101 receives a list of packages currently in use from the License Management Unit 104, it generates a package management screen based on that list of packages (step S116). The package management screen defines the screen that will be displayed on the browser 210, for example, using HTML, CSS, etc.

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

[0140] When the browser 210 receives a package management screen as a response from the web service unit 101, it displays, for example, the package management screen G300 shown in Figure 13 (step S117). On the package management screen G300 shown in Figure 13, the user can deactivate and assign licenses, starting with the package name (license name).

[0141] The package management screen G300 shown in Figure 13 includes a "List of Packages in Use" display area G310, which displays a list of license names for packages purchased by the tenant with the relevant tenant ID as "Packages in Use". The package management screen G300 also includes a checkbox G320 for selecting a package in use from the "List of Packages in Use" display area G310. The list of package names in use (i.e., license names) displayed in the "List of Packages in Use" display area G310 is generated based on the list of packages in use obtained in step S115 described above.

[0142] In the G310 list of packages in use, the license name is displayed as "Package Name in Use" because users purchase applications on a package basis, and displaying the license name as "Package Name in Use" is more convenient for users. For example, if the package name of a package purchased by a user is "Storage A Package," the license name for this package will be "Storage A Package License," etc.

[0143] However, this is not limited to displaying the license names included in the license information as the active package names in the active package list display area G310. For example, in step S115 above, 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 the active package names in the active package list display area G310. Alternatively, for example, in step S115 above, 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 the active package names in the active package list display area G310.

[0144] The user can remove the license for the selected package from the device 30 to which it is assigned by selecting the desired package name from the checkbox G320 and then selecting the release button G330. This allows the user to easily remove all licenses assigned to the devices 30 using a particular package, for example, if they decide to stop using that package.

[0145] Furthermore, by selecting the edit button G340, the user can deactivate the licenses for some of the devices 30 to which the license indicated by the currently used package name corresponding to the edit button G340 is assigned. This allows the user to easily deactivate the licenses assigned to certain devices 30 that are using a particular package, for example, if they want to stop using that package on only some of the devices 30.

[0146] Furthermore, by selecting the additional button G350, the user can assign the license indicated by the name of the currently used package corresponding to that additional button G350 to the device 30. This allows the user to easily assign licenses, for example, if they want to assign a license for a particular package to a particular device 30.

[0147] Details regarding the process of assigning licenses from the package management screen G300 shown in Figure 13, and the process of revoking licenses from the package management screen G300 shown in Figure 13, will be described later.

[0148] ≪Process to deactivate the license from the device management screen G200≫ In the following section, the process of deactivating a license from the device management screen G200 shown in Figure 13 will be explained with reference to Figure 14. Figure 14 is a sequence diagram showing an example of the license deactivation process from the device management screen G200.

[0149] Browser 210 accepts the selection operation of either the delete button G230 or the edit button G240 (step S201). Before selecting the delete button G230, the user selects the desired device ID currently in use from the checkbox G220.

[0150] When the browser 210 receives a selection operation for the delete button G230, the processes described in steps S202 to S209 are executed. At this time, the user can also select multiple active device IDs from the checkbox G220. In this case, the processes in steps S202 to S206 should be executed for each selected active device ID, followed by the processes in steps S207 to S209.

[0151] On the other hand, if the browser 210 accepts the selection operation of the edit button G240, the processing of steps S210 to S221 described later will be executed.

[0152] If the browser 210 receives a selection operation for the delete button G230 in step S201 above, it sends a request to delete device information to the cloud server 10 (step S202). The request to delete device information includes the device ID (device ID in use) selected from checkbox G220 and the tenant ID.

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

[0154] When the device management unit 105 receives a request to delete device information, it sends 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 a license deactivation request, it deactivates all licenses assigned to the device 30 indicated by the device ID included in the deactivation request (step S205). Specifically, the license management unit 104 identifies the license information containing the device ID and tenant ID from 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. The license management unit 104 then sends the deactivation result back to the device management unit 105.

[0156] This will deactivate all licenses assigned to device 30 with the corresponding device ID.

[0157] Furthermore, if the same device ID is not used across different tenants (specifically, if a serial number or the like is used as the device ID), the above license release request does not need to include the tenant ID. In this case, in step S205 above, the license information stored in the license information storage unit 160 that includes the device ID is identified, and the device ID is removed from the "device ID in use" of the identified license information.

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

[0159] Next, the device management unit 105 obtains a list of devices for which the tenant ID included in the device information deletion request is set (step S207). This obtains a list of devices excluding the device information deleted in step S206 above.

[0160] Then, the device management unit 105 returns the acquired list of devices to the web service unit 101.

[0161] When the Web service unit 101 receives a list of devices from the device management unit 105, it generates a device management screen based on that list of devices (step S208). Then, the Web service unit 101 sends the generated device management screen back to the browser 210.

[0162] When the browser 210 receives a device management screen from the web service unit 101, it displays, for example, the device management screen G200 shown in Figure 13 (step S209). However, in the device list display section G210 of this device management screen G200, the device IDs that are currently in use are listed, excluding the device IDs included in the device information deleted in step S206 above.

[0163] As described above, the user can remove all licenses assigned to device 30 with the device ID selected on the device management screen G200 shown in Figure 13. Moreover, the user can easily remove the licenses by simply selecting the desired device ID from the device list display area G210 while referring to the "device description" and pressing the delete button G230. For this reason, for example, when replacing device 30, the effort required to identify the device ID of the original device 30 can be reduced, and errors such as incorrect input due to manual entry of the device ID can be prevented.

[0164] Return to Figure 14. Meanwhile, if the browser 210 receives the selection operation of the edit button G240 in step S201 above, it sends a request to display the assigned package screen to the cloud server 10 (step S210). The request to display the assigned package screen includes the device ID (device ID in use) corresponding to the selected edit button G240 and the tenant ID.

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

[0166] When the device management unit 105 receives a request to retrieve a list of assigned packages, it sends the request to the license management unit 104 (step S212).

[0167] When the license management unit 104 receives a request to obtain a list of assigned packages, it obtains a list of license information (hereinafter also referred to as the "list of assigned packages") in which the tenant ID, device ID, and "in use" status are set (step S213). In other words, the license management unit 104 obtains the license information stored in the license information storage unit 160 that includes the tenant ID and device ID and whose license status is "in use" as the list of assigned packages.

[0168] The license management unit 104 then returns the acquired list of assigned packages to the device management unit 105. Subsequently, the device management unit 105 returns the list of assigned packages returned by the license management unit 104 to the web service unit 101.

[0169] When the Web service unit 101 receives a list of assigned packages from the device management unit 105, it generates an assigned package screen based on that list of assigned packages (step S214). The Web service unit 101 then sends the generated assigned package screen back to the browser 210.

[0170] When the browser 210 receives a response from the Web service unit 101 regarding the allocated package screen, it displays, for example, the allocated package screen G400 shown in Figure 15 (step S215).

[0171] The assigned package screen G400 shown in Figure 15 includes an assigned package name list display field G410, which displays a list of assigned package names as "assigned package names" for the license assigned to device 30 with the corresponding device ID. The list of assigned package names displayed in the assigned package name list display field G410 is generated based on the assigned package list obtained in step S213 above.

[0172] The user can remove the license indicated by the selected assigned package name from the device 30 by selecting the desired assigned package name from the checkbox G420 and then selecting the release button G430. This allows the user to remove the license for a package, for example, if they want to stop using a particular package assigned to a particular device 30. Hereafter, we will assume that the user has performed the operation of selecting the desired assigned package name from the checkbox G420 and then selecting the release button G430 (package removal operation). In this case, the user can also select multiple assigned package names from the checkbox G420. In this case, the processes in steps S216 to S220 should be executed for each selected assigned package name, followed by the processes in steps S221 to S222.

[0173] Browser 210 accepts the package unfreezing operation (step S216). Upon receiving the package unfreezing operation, Browser 210 sends a package unfreezing request to Web service unit 101 (step S217). The package unfreezing request includes the device ID of the device 30, the tenant ID, and the service ID corresponding to the assigned package name selected from checkbox G420. The service ID corresponding to the assigned package name is the service ID included in the license information where the license name displayed as the assigned package name is set.

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

[0175] When the device management unit 105 receives a package deactivation request, it sends a license deactivation request to the license management unit 104 (step S219). The license deactivation request includes the device ID, tenant ID, and 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 indicated by the device ID included in the release request (step S220). That is, the license management unit 104 identifies the license information containing the device ID, tenant ID and service ID from 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 selected by the user (the license corresponding to the assigned package name) from among the licenses assigned to the device 30 of the device ID is released.

[0177] The license management unit 104 then sends the deactivation result back to the device management unit 105. Subsequently, the device management unit 105 sends the deactivation result received from the license management unit 104 back to the web service unit 101.

[0178] When the Web service unit 101 receives a deactivation result from the device management unit 105, it generates a deactivation result screen (step S221). The Web service unit 101 then sends the generated deactivation result screen back to the browser 210.

[0179] When the browser 210 receives a deactivation result screen from the web service unit 101, it displays, for example, the deactivation result screen G500 shown in Figure 15 (step S222).

[0180] The release result screen G500 shown in Figure 15 displays information indicating that the license corresponding to the assigned package name selected in the assigned package screen G400 shown in Figure 15 has been released from device 30 with the device ID selected in the device management screen G200 shown in Figure 13. The release result screen G500 shown in Figure 15 also includes a "Yes" button G510 and a "No" button G520 to select whether or not to proceed with assigning the package.

[0181] If the user selects the "Yes" button G510, the browser 210 displays a screen for assigning a license to device 30 with that device ID (the assignable package screen G600, described later). On the other hand, if the user selects the "No" button G520, the browser 210 displays the device management screen G200 shown in Figure 13.

[0182] As described above, the user can revoke the license for device 30 with the device ID selected on the device management screen G200 shown in Figure 13, for the assigned package name (license name) selected on the assigned package screen G400 shown in Figure 15. Therefore, for example, if a user wants to revoke only a specific license assigned to a particular device 30, they can easily revoke the license without having to manually enter the license ID, device ID, etc.

[0183] ≪Process for assigning licenses from the device management screen G200≫ In the following section, the process of assigning licenses from the device management screen G200 shown in Figure 13 will be explained with reference to Figure 16. Figure 16 is a sequence diagram showing an example of the license assignment process from the device management screen G200.

[0184] Browser 210 accepts the selection operation for add button G250 (step S301). Upon accepting the selection operation for add button G250, Browser 210 sends a request to display the assignable package screen to the cloud server 10 (step S302). The request to display the assignable package screen includes the device ID (device ID in use) corresponding to the selected add button G250 and the tenant ID.

[0185] When the Web service unit 101 receives a request to display the assignable package screen, it sends a request to the device management unit 105 to retrieve the list of assignable packages (step S303). The request to retrieve the list of assignable packages includes the device ID and the tenant ID.

[0186] When the device management unit 105 receives a request to obtain a list of assignable packages, it sends the request to the license management unit 104 (step S304).

[0187] When the license management unit 104 receives a request to obtain a list of assignable packages, it obtains a list of license information (hereinafter also referred to as the "list of assignable packages") in which the tenant ID included in the acquisition request is set, and the device ID included in the acquisition request is not set (step S305). In other words, the license management unit 104 obtains the license information stored in the license information storage unit 160 that includes the tenant ID and does not include the device ID, as the list of assignable packages.

[0188] The license management unit 104 then returns the acquired list of assignable packages to the device management unit 105. Subsequently, the device management unit 105 returns the list of assignable packages returned by the license management unit 104 to the web service unit 101.

[0189] When the Web service unit 101 receives a list of assignable packages from the device management unit 105, it generates an assignable package screen based on that list (step S306). The Web service unit 101 then sends the generated assignable package screen back to the browser 210.

[0190] When the browser 210 receives a response from the Web service unit 101 regarding the assignable package screen, it displays, for example, the assignable package screen G600 shown in Figure 17 (step S307).

[0191] The assignable package screen G600 shown in Figure 17 includes an assignable package list display field G610, which displays a list of assignable package names for licenses that can be assigned to device 30 with the corresponding device ID, as "assignable package names". The list of assignable package names displayed in the assignable package list display field G610 is generated based on the list of assigned packages obtained in step S305 above.

[0192] The user can assign the license indicated by the selected assignable package name to the device 30 by selecting the desired assignable package name from checkbox G620 and then selecting the assign button G630. This allows the user to assign a license for a specific package, for example, if they want to use a specific package on a specific device 30. Hereafter, we will assume that the user has performed the operation of selecting the desired assignable package name from checkbox G620 and then selecting the assign button G630 (package assignment operation). In this case, the user can also select multiple assignable package names from checkbox G620. In this case, the processes in steps S309 to S312 should be executed for each selected assignable package name, followed by the processes in steps S313 to S316.

[0193] Browser 210 accepts the package assignment operation (step S308). Upon accepting the package assignment operation, Browser 210 sends a package assignment request to Web service unit 101 (step S309). The package assignment request includes the device ID of the device 30, the tenant ID, and the service ID corresponding to the assignable package name selected from checkbox G620. The service ID corresponding to the assignable package name is the service ID included in the license information where the license name displayed as the assignable package name is set.

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

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

[0196] When the license management unit 104 receives a license assignment request, it assigns the license specified by the tenant ID and service ID included in the assignment request to the device 30 indicated by the device ID included in the assignment request (step S312). That is, the license management unit 104 identifies the license information containing the tenant ID and service ID from the license information stored in the license information storage unit 160, and then 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 assignable package name) is assigned to the device 30 of that device ID. The license management unit 104 then returns the assignment result to the device management unit 105.

[0197] When the device management unit 105 receives the allocation result from the license management unit 104, it sends a request to the license management unit 104 to retrieve the list of allocated packages (step S313). The request to retrieve the list of allocated packages includes the device ID and the tenant ID.

[0198] When the license management unit 104 receives a request to retrieve a list of assigned packages, it retrieves a list of assigned packages that include the tenant ID, device ID, and status of "in use" that are set in the request (step S314). In other words, the license management unit 104 retrieves the license information stored in the license information storage unit 160 that includes the tenant ID and device ID and whose license status is "in use" as the list of assigned packages.

[0199] The license management unit 104 then returns the acquired list of assigned packages to the device management unit 105. Subsequently, the device management unit 105 returns the list of assigned packages returned by the license management unit 104, along with the assignment results, to the web service unit 101.

[0200] When the Web service unit 101 receives a list of assigned packages from the device management unit 105, it generates an assigned package screen based on that list of assigned packages (step S315). The Web service unit 101 then sends the generated assigned package screen back to the browser 210.

[0201] The Web service unit 101 may also use the assignment result returned from the device management unit 105 to generate a screen indicating that the license assignment is complete (assignment completion screen) and send it back to the browser 210. As a result, the assignment completion screen will be displayed to the browser 210.

[0202] When the browser 210 receives a response from the Web service unit 101 regarding the assigned package screen, it displays, for example, the assigned package screen G400 shown in Figure 15 (step S316). However, in the assigned package name list display field G410 of this assigned package screen G400, the license name indicating the license assigned in step S312 above is also displayed as an assigned package name in the list.

[0203] As described above, the user can assign a license of the assignable package name (license name) selected on the assignable package screen G600 shown in Figure 17 to the device 30 selected on the device management screen G200 shown in Figure 13. Therefore, for example, when replacing device 30, the effort required to identify the device ID of the replacement device 30 can be reduced, and errors such as manual input of device IDs and license IDs can be prevented.

[0204] ≪Process to deactivate a license from the package management screen G300≫ In the following section, the process of deactivating a license from the package management screen G300 shown in Figure 13 will be explained with reference to Figure 18. Figure 18 is a sequence diagram showing an example of the license deactivation process from the package management screen G300.

[0205] Browser 210 accepts the selection operation of either the release button G330 or the edit button G340 (step S401). Before selecting the release button G330, the user selects the desired currently used package name from the checkbox G320.

[0206] If the browser 210 receives a selection operation for the edit button G340, the processes described in steps S402 to S415 are executed.

[0207] On the other hand, if the browser 210 accepts the selection operation of the deactivation button G330, the processes of steps S416 to S420 described later will be executed. At this time, the user can also select multiple active package names from the checkbox G320. In this case, the processes of steps S416 to S418 should be executed for each selected active package, followed by the processes of steps S419 to S420.

[0208] If the browser 210 receives the selection operation for the edit button G340 in step S401 above, it sends a request to the cloud server 10 to display the assigned device screen (step S402). The request to display the assigned device screen includes the tenant ID and the service ID corresponding to the selected edit button G340. The service ID corresponding to the edit button G340 is the service ID included in the license information where the license name displayed as the package name in use corresponding to the edit button G340 is set.

[0209] When the Web service unit 101 receives a request to display the assigned devices screen, it sends a request to the device management unit 105 to retrieve the list of assigned devices (step S403). The request to retrieve the list of assigned devices includes the tenant ID, the service ID, and the status of the license, which indicates that it is in use.

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

[0211] When the license management unit 104 receives a request to acquire license information, it acquires the license information containing the service ID and tenant ID from the license information storage unit 160 (step S405).

[0212] The license management unit 104 then sends the acquired license information back to the device management unit 105.

[0213] When the device management unit 105 receives license information from the license management unit 104, it obtains a list of device information (hereinafter also referred to as the "assigned device list") from the device information storage unit 170 that includes the device ID set in the "device ID in use" field of the license information (step S406). In other words, the device management unit 105 obtains the device information stored in the device information storage unit 170 that includes the device ID set in the "device ID in use" field of the license information as the assigned device list.

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

[0215] When the Web service unit 101 receives a list of assigned devices from the device management unit 105, it generates an assigned device screen based on that list of assigned devices (step S407). The Web service unit 101 then sends the generated assigned device screen back to the browser 210.

[0216] When the browser 210 receives a response from the Web service unit 101 regarding the assigned device screen, it displays, for example, the assigned device screen G700 shown in Figure 19 (step S408).

[0217] The assigned device screen G700 shown in Figure 19 includes an assigned device list display area G710, which displays a list of device IDs for devices 30 to which the license indicated by the license information has been assigned, as "assigned device IDs". The assigned device list display area G710 also displays a "device description". The list of assigned device IDs displayed in the assigned device list display area G710 is generated based on the assigned device list obtained in step S406 above.

[0218] Furthermore, the assigned device screen G700 shown in Figure 19 includes a checkbox G720 for selecting the assigned device ID from the assigned device list display area G710.

[0219] The user can select a device to deactivate by selecting the desired assigned device ID from the checkbox G720 and then selecting the deactivation button G730. By performing this deactivation device selection operation, the license indicated by the license information for the device 30 corresponding to the selected assigned device ID can be deactivated. This allows the user to easily deactivate the license for a particular device 30, for example, if they wish to discontinue the use of a specific device 30 that is assigned a license for a particular package.

[0220] Browser 210 accepts the operation to select a release device (step S409). At this time, the user can also select multiple assigned device IDs from checkbox G720. In this case, after the processes in steps S410 to S413 are executed for each selected assigned device ID, the processes in steps S414 to S415 should be executed.

[0221] When the browser 210 receives the operation to select a release device, it sends a package release request to the Web service unit 101 (step S410). The package release request includes the device ID (assigned device ID) selected from the checkbox G720, the tenant ID, and the service ID corresponding to the name of the package in use selected on the package management screen G300 shown in Figure 13.

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

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

[0224] 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 indicated by the device ID included in the release request (step S413). That is, the license management unit 104 identifies the license information containing the device ID, tenant ID and service ID from 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 for the package corresponding to the service ID is released from the device 30 selected by the user.

[0225] The license management unit 104 then sends the deactivation result back to the device management unit 105. Subsequently, the device management unit 105 sends the deactivation result received from the license management unit 104 back to the web service unit 101.

[0226] When the Web service unit 101 receives a deactivation result from the device management unit 105, it generates a deactivation result screen (step S414). The Web service unit 101 then sends the generated deactivation result screen back to the browser 210.

[0227] When the browser 210 receives a deactivation result screen from the web service unit 101, it displays, for example, the deactivation result screen G800 shown in Figure 19 (step S415).

[0228] The release result screen G800 shown in Figure 19 displays information indicating that the license corresponding to the currently used package name selected in the package management screen G300 shown in Figure 13 has been released from device 30 with the device ID selected in the assigned device screen G700 shown in Figure 19. The release result screen G800 also includes a "Yes" button G810 and a "No" button G820 to select whether or not to proceed with assigning the package.

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

[0230] As described above, a user can remove a license for a currently used package (license name) selected on the package management screen G300 shown in Figure 13 from device 30 with the device ID selected on the assigned device screen G700 shown in Figure 19. Therefore, for example, if a user wants to remove a license for a specific package from only a specific device 30, they can easily remove the license without manually entering the license ID, device ID, etc.

[0231] Return to Figure 18. Meanwhile, if the browser 210 receives the selection operation of the release button G330 in step S401 above, it sends a package release request to the cloud server 10 (step S416). The package release request includes the service ID corresponding to the name of the package in use selected from the checkbox G320, and the tenant ID.

[0232] When the Web Service Unit 101 receives a package deactivation request, it sends the deactivation request to the License Management Unit 104 (step S417).

[0233] When the license management unit 104 receives a license deactivation request, it deactivates the license from the device 30 to which the license corresponding to the service ID and tenant ID included in the deactivation request is assigned (step S418). Specifically, the license management unit 104 identifies the license information containing the service ID and tenant ID from the license information stored in the license information storage unit 160, and then deletes all device IDs from the "device ID in use" of the identified license information. As a result, the license is deactivated from the device 30 to which the license is assigned. The license management unit 104 then sends the deactivation result back to the Web service unit 101.

[0234] When the Web service unit 101 receives a deactivation result from the device management unit 105, it generates a deactivation result screen (step S419). The Web service unit 101 then sends the generated device management screen back to the browser 210.

[0235] When the browser 210 receives a deactivation result screen from the Web service unit 101, it displays, for example, the deactivation result screen G800 shown in Figure 19 (step S420).

[0236] As described above, the user can remove the license for the currently used package name (license name) selected on the package management screen G300 shown in Figure 13 from all devices 30 to which the license is assigned. Therefore, for example, if a user decides to stop using a particular package, they can easily remove the license for all devices 30 using that package at once without having to manually enter the license ID, device ID, etc.

[0237] ≪Process for assigning licenses from the package management screen G300≫ In the following section, the process of assigning licenses from the package management screen G300 shown in Figure 13 will be explained with reference to Figure 20. Figure 20 is a sequence diagram showing an example of the license assignment process from the package management screen G300.

[0238] Browser 210 accepts the selection operation for add button G350 (step S501). Upon accepting the selection operation for add button G350, Browser 210 sends a request to display the assignable devices screen to the cloud server 10 (step S502). The request to display the assignable devices screen includes the service ID and tenant ID corresponding to the selected add button G350. The service ID corresponding to add button G350 is the service ID of the service information corresponding to the license information which includes the name of the package in use (license name) corresponding to the add button G350.

[0239] When the Web service unit 101 receives a request to display the assignable devices screen, it sends a request to the device management unit 105 to retrieve the list of assignable devices (step S503). The request to retrieve the list of assignable devices includes the service ID and the tenant ID.

[0240] When the device management unit 105 receives a request to obtain a list of assignable devices, it sends a request to obtain license information to the license management unit 104 (step S504). The request to obtain license information includes the service ID and the tenant ID.

[0241] When the license management unit 104 receives a request to acquire license information, it acquires the license information containing the service ID and tenant ID from the license information storage unit 160 (step S505).

[0242] The license management unit 104 then sends the acquired license information back to the device management unit 105.

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

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

[0245] When the Web service unit 101 receives a list of assignable devices from the device management unit 105, it generates an assignable device screen based on that list (step S507). The Web service unit 101 then sends the generated assignable device screen back to the browser 210.

[0246] When the browser 210 receives a reply from the Web service unit 101 with an assignable device screen, it displays, for example, the assignable device screen G900 shown in Figure 21 (step S508).

[0247] The assignable device screen G900 shown in Figure 21 includes an assignable device list display field G910, which displays a list of device IDs of devices 30 to which the license indicated by the license information can be assigned (i.e., devices to which the license has not been assigned) as "assignable device IDs". The list of assignable device IDs displayed in the assignable device list display field G910 is generated based on the assignable device list obtained in step S506 above.

[0248] The user can assign the license to the device 30 indicated by the selected assignable device ID by selecting the desired assignable device ID from checkbox G920 and then selecting the assign button G630. This allows the user to assign the license for a specific package to a specific device 30, for example, if they want to use a particular package on that device 30. Hereafter, we will assume that the user has performed the operation of selecting the desired assignable device ID from checkbox G920 and then selecting the assign button G930 (the operation of selecting an assignable device). In this case, the user can also select multiple assignable device IDs from checkbox G920. In this case, the processes from steps S510 to S513 should be executed for each selected assignable device ID, followed by the processes from steps S514 to S516.

[0249] The browser 210 accepts the operation to select an assignment device (step S509). Upon accepting the operation to select an assignment device, the browser 210 sends a package assignment request to the Web service unit 101 (step S510). The package assignment request includes the device ID (assignable device ID) selected from the checkbox G920, the tenant ID, and the service ID corresponding to the name of the package currently in use selected on the package management screen G300 shown in Figure 13.

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

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

[0252] When the license management unit 104 receives a license assignment request, it assigns the license identified by the tenant ID and service ID included in the assignment request to the device 30 indicated by the device ID included in the assignment request (step S513). That is, the license management unit 104 identifies the license information containing the tenant ID and service ID from the license information stored in the license information storage unit 160, and then adds the device ID to the "device ID in use" of the identified license information. As a result, the license is assigned to the device 30 selected by the user (the device 30 indicated by the assignable device ID). The license management unit 104 then returns the assignment result to the device management unit 105.

[0253] When the device management unit 105 receives the assignment result from the license management unit 104, it obtains a list of assigned devices from the device information storage unit 170 (step S514). The device management unit 105 then sends the obtained list of assigned devices and the assignment result back to the web service unit 101.

[0254] When the Web service unit 101 receives a list of assigned devices from the device management unit 105, it generates an assigned device screen based on that list of assigned devices (step S515). The Web service unit 101 then sends the generated assigned device screen back to the browser 210.

[0255] The Web service unit 101 may also generate an assignment completion screen using the assignment result returned from the device management unit 105 and send it back to the browser 210. As a result, the assignment completion screen will be displayed to the browser 210.

[0256] When the browser 210 receives a reply from the Web service unit 101 with the assigned device screen, it displays, for example, the assigned device screen G700 shown in Figure 19 (step S516). However, in the assigned device list display section G710 of this assigned device screen G700, the device ID of the device 30 to which the license was assigned in step S513 is also displayed as an assigned device ID in the list.

[0257] As described above, the user can assign the license for the currently used package name (license name) selected on the package management screen G300 shown in Figure 13 to the device 30 with the device ID selected on the assignable device screen G900 shown in Figure 21. Therefore, for example, when a user wants to allow a particular package to be used only on a particular device 30, the user can easily assign the license without manually entering the license ID, device ID, etc.

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

[0259] 1. Cloud System 10 Cloud Servers 20 Terminal devices 30 equipment 101 Web Services Department 102 Certification Department 103 App 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 App settings information storage unit 150 Service Information Storage Unit 160 License Information Storage Unit 170 Device Information Storage Unit 210 Browsers 310 Browser [Prior art documents] [Patent Documents]

[0260] [Patent Document 1] Japanese Patent Publication No. 2017-083982

Claims

1. An information processing device that is connected to a terminal via a network and manages licenses for packages containing one or more applications used by the device, Display means that causes the terminal to display a first screen containing a list of devices to which the license of the package can be assigned or unassigned in response to a first request from the terminal, A license management means that, in response to the selection of a device from the list of devices included in the first screen and the operation for assigning or unassigning the license, assigns the license to the selected device or removes the license from the selected device, An information processing device characterized by having the following features.

2. The aforementioned license management means is The information processing device according to claim 1, characterized in that, in response to the selection of a device from the list of devices included in the first screen and the operation to deactivate all licenses assigned to the device, all licenses assigned to the selected device are deactivated.

3. The aforementioned display means is In response to selecting a device from the list of devices included in the first screen and performing an operation to deactivate a portion of the licenses assigned to that device, a second screen is displayed on the terminal containing a list of packages available with the licenses assigned to the selected device. The aforementioned license management means is The information processing device according to claim 1 or 2, characterized in that, in response to the selection of a package from the list of packages included in the second screen, the license for the package selected on the second screen is released from the device selected on the first screen.

4. The aforementioned display means is In response to the selection of a device from the list of devices included in the first screen and the operation to assign a license to the device, a third screen is displayed on the terminal, which includes a list of packages corresponding to licenses that the selected device can be assigned to. The aforementioned license management means is The information processing apparatus according to any one of claims 1 to 3, characterized in that, in accordance with the selection of a package from the list of packages included in the third screen, a license for the package selected on the third screen is assigned to the device selected on the first screen.

5. The aforementioned display means is In response to a second request from the terminal, a fourth screen is displayed on the terminal, which includes a list of packages corresponding to licenses that can be assigned to or removed from the device. The aforementioned license management means is The information processing apparatus according to any one of claims 1 to 4, characterized in that, in response to the selection of a package from the list of packages included in the fourth screen and the operation for assigning or unassigning, the license of the selected package is assigned to the device or the license of the selected package is unassigned from the device.

6. The aforementioned license management means is The information processing device according to claim 5, characterized in that, in accordance with the selection of a package from the list of packages included in the fourth screen and the operation to deactivate all licenses for said package, the license for the selected package is deactivated from all devices to which the license for said package is assigned.

7. The aforementioned display means is In response to the selection of a package from the list of packages included in the fourth screen and the operation to remove the license from some of the devices to which the package is assigned, a fifth screen is displayed on the terminal, which includes a list of devices from which the license for the selected package can be removed. The aforementioned license management means is The information processing apparatus according to claim 5 or 6, characterized in that, in accordance with the selection of a device from the list of devices included in the fifth screen, the license of the package selected on the fourth screen is released from the device selected on the fourth screen.

8. The aforementioned display means is In response to the selection of a package from the list of packages included in the fourth screen and the operation to assign the license of said package to a device, a sixth screen is displayed on the terminal, which includes a list of devices to which the license of the selected package can be assigned. The aforementioned license management means is The information processing device according to any one of claims 5 to 7, characterized in that, in accordance with the selection of a device from the list of devices included in the sixth screen, the license of the package selected on the fourth screen is assigned to the device selected on the sixth screen.

9. An information processing system that manages licenses for packages containing one or more applications used by terminals and devices, connected via a network, Display means that causes the terminal to display a first screen containing a list of devices to which the license of the package can be assigned or unassigned in response to a first request from the terminal, A license management means that, in response to the selection of a device from the list of devices included in the first screen and the operation for assigning or unassigning the license, assigns the license to the selected device or removes the license from the selected device, An information processing system characterized by having the following features.

Images