Information processing system, server, program, and license granting method

Abstract

To avoid that a license, which cannot be used by a device, may be allocated to the device.SOLUTION: An information processing system comprising at least one server, and a device connected through a network to the server comprises: a license management unit that associates a service with a device type which is able to use the service to manage; a device management unit that associates the device with the device type to manage; and a determination unit that determines whether it is possible to allocate a license of the service to the allocation target device by comparing the device type associated with the allocation target device with the device type associated with the service when the license is allocated to the device.SELECTED DRAWING: Figure 4-2

Description

[Technical field]

[0001] The present invention relates to an information processing system, a server, a program, and a license granting method. [Background technology]

[0002] Traditionally, there are new service provision formats for dedicated devices such as MFPs, IWBs, and projectors. The new service provision format allows users to use only the functions they need, when they need them. To use a service in this type of service provision format, a company or the like must purchase a license for that service from the service sales company (distributor). After purchasing the license, the company or the like assigns the license to a device, user, etc. Licenses for a service include device licenses, which specify devices that can be used, and user licenses, which specify users that can be used.

[0003] Patent Document 1 (Japanese Patent No. 5670167) discloses a technique for controlling the allocation of multiple licenses to the same user when multiple licenses exist for one application. Summary of the Invention [Problem to be solved by the invention]

[0004] By the way, services (applications, packages, functions, web services, etc.) often have a specific target device. Therefore, when managing licenses, simply linking a service to a target device may result in assigning a license to a type of device that is not intended for that service. This tendency becomes more pronounced as the number of device types increases.

[0005] The present invention has been made in view of the above, and has an object to avoid allocating to a device a license that the device cannot use. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides an information processing system including at least one server and a device connected to the server via a network, the information processing system including a license management unit that manages services in association with device types that can use the services, a device management unit that manages the devices in association with the device types, and a determination unit that, when allocating a license to a device, determines whether a license for the service can be allocated to the device to be allocated by comparing a device type associated with the device to be allocated and a device type associated with the service, the device types being a first device type having a printing function and a second device type having an output function different from the printing function. A projection or display function and a second device type having the Effect of the Invention

[0007] According to the present invention, it is possible to avoid allocating to a device a license that cannot be used by that device. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of a configuration of a system according to the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the server. [Diagram 3] FIG. 3 is a diagram illustrating an example of functions that the server has. [Figure 4-1] FIG. 4-1 shows the basic data model for data stored in a server. [Figure 4-2] FIG. 4-2 shows in more detail the data model of the data stored in the server. [Figure 4-3] FIG. 4-3 shows in more detail the data model of the data stored in the server. [Diagram 5]FIG. 5 is a diagram illustrating an example of management information of a package managed by the application management unit. [Figure 6] FIG. 6 is a diagram showing an example of management information of a service definition managed by the license management unit. [Figure 7] FIG. 7 is a diagram showing an example of management information of license definitions managed by the license management unit. [Figure 8] FIG. 8 is a diagram showing an example of management information of device definitions managed by the device management unit. [Figure 9] FIG. 9 is a sequence diagram showing a process of registering various pieces of information when creating a package. [Figure 10] FIG. 10 is a diagram showing an example of the package creation screen. [Figure 11] FIG. 11 is a diagram showing an example of a package information input screen. [Figure 12] FIG. 12 is a diagram showing an example of the license definition information input screen. [Figure 13] FIG. 13 is a sequence diagram showing the license allocation process. [Figure 14] FIG. 14 is a diagram showing an example of the license purchase screen. [Figure 15] FIG. 15 is a diagram showing an example of input to the license allocation screen. [Figure 16] FIG. 16 is a diagram showing an example of an instance for a data model. [Figure 17] FIG. 17 is a diagram illustrating an example of the notification of non-allocation. [Figure 18] FIG. 18 is a diagram showing another example of input to the license allocation screen. [Figure 19] FIG. 19 is a sequence diagram illustrating a license assignment process according to the second embodiment. [Figure 20] FIG. 20 is a diagram showing an example of the license allocation screen. [Figure 21] FIG. 21 is a diagram showing another example of the license allocation screen. [Figure 22]FIG. 22 illustrates an example of functions of the server according to the third embodiment. In FIG. [Figure 23] FIG. 23 is a sequence diagram illustrating a part of the license assignment process according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of an information processing system, a server, a program, and a license granting method will be described in detail with reference to the accompanying drawings.

[0010] (First embodiment) Fig. 1 is a diagram showing an example of a configuration of a system 1 according to a first embodiment. As shown in Fig. 1, a system (information processing system) 1 realizes a cloud computing type service.

[0011] The system 1 includes a cloud system 2 and various devices 10. A network 3 such as the Internet and a local network 4 such as a LAN (Local Area Network) connect the various devices 10 to the cloud system 2.

[0012] As examples of various devices 10 connected to the cloud system 2, a multifunction peripheral (MFP) 11, which is one type of image forming device, an information processing device 12 such as a notebook PC (Personal Computer) or a tablet terminal, a projector (PJ) 13, and an interactive white board (IWB: an electronic whiteboard with a blackboard function capable of mutual communication) 14 will be described. However, the present invention is not limited to these, and any device capable of receiving services, such as a copy machine, a scanner, a fax, a camera, or a remote conference terminal, may be used. The multifunction peripheral 11 is a device having a plurality of different functions such as a copy function, a scanner function, a printer function, and a fax function.

[0013] The information processing device 12 is a notebook PC or a tablet terminal as described above. The information processing device 12 has a browser 120 installed therein, which functions as a display unit. Instead of the browser 120, dedicated software for managing "license setting information" may be installed in the information processing device 12. Although details will be described later, a tenant administrator who manages various devices 10 in a tenant such as a company, office, or store can use the browser 120 (or the dedicated software) to edit the "license setting information" of the various devices 10 (such as granting or revoking a license). A tenant is a unit in which the tenant administrator manages various devices 10. The tenant administrator may be two or more users.

[0014] The cloud system 2 has a server device group consisting of a plurality of servers 5. The number of servers 5 shown in Fig. 1 is an example, and the number of servers 5 to be used is not limited to this. Note that in the example of Fig. 1, an MFP 11, an information processing device 12, a projector 13, and an IWB 14 are shown as devices 10 included in the system 1 that are clients when viewed from the cloud system 2 side, but the number and types of devices 10 included in the system 1 are not limited to these, and are arbitrary.

[0015] Although details will be described later, once a license for each package is granted to each device 10, the user of each device 10 can use that package stored in the server 5 (cloud system 2). In addition, "license setting information" indicating which package license is assigned to which device 10 is managed within the server 5 (cloud system 2). The specific configuration of the server 5 will be described below.

[0016] 2 is a diagram showing an example of a hardware configuration of the server 5. Here, the hardware configuration of the server 5 will be described.

[0017] As shown in FIG. 2, the server 5 is constructed by a computer and includes a CPU 501, a ROM 502, a RAM 503, a HD 504, a HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I / F (Interface) 508, a network I / F 509, a bus line 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disc Rewritable) drive 514, and a media I / F 516.

[0018] Of these, the CPU 501 controls the overall operation of the server 5. The ROM 502 stores programs, such as an IPL, used to drive the CPU 501. The RAM 503 is used as a work area for the CPU 501.

[0019] The HD 504 stores various data such as programs, etc. The HDD controller 505 controls reading and writing of various data from and to the HD 504 under the control of the CPU 501.

[0020] The display 506 displays various types of information such as a cursor, a menu, a window, a character, or an image.

[0021] The external device connection I / F 508 is an interface for connecting various external devices, such as a USB (Universal Serial Bus) memory or a printer.

[0022] The network I / F 509 is an interface for performing data communication using the network 3 and the local network 4. The bus line 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG.

[0023] The keyboard 511 is a type of input means having a plurality of keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc.

[0024] A DVD-RW drive 514 controls reading and writing of various data from and to a DVD-RW 513 as an example of a removable recording medium. Note that the medium is not limited to a DVD-RW, and may be a DVD-R or the like. A media I / F 516 controls reading and writing (storing) of data from and to a recording medium 515 such as a flash memory.

[0025] The program executed by the server 5 in this embodiment may be configured to be provided by recording it on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD in the form of an installable or executable file.

[0026] Furthermore, the program executed by the server 5 of this embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the program executed by the server 5 of this embodiment may be provided or distributed via a network such as the Internet.

[0027] Next, a description will be given of functions that are realized by the CPU 501 of the server 5 executing the programs stored in the ROM 502 and the HD 504. Note that, here, a description of conventionally known functions will be omitted, and only characteristic functions realized by the CPU 501 of the server 5 of this embodiment will be described in detail.

[0028] Here, FIG. 3 is a diagram showing an example of functions possessed by the server 5. As shown in FIG. 3, the server 5 has an application management unit 210, a license management unit 220, a device management unit 230, a control unit 240, and a determination unit 250. In the example of FIG. 3, only modules related to this embodiment are illustrated, but the modules possessed by the server 5 are not limited to these. Furthermore, each unit of the server 5 may be configured from one device as in this embodiment, or may be configured from two or more devices. For example, the license management unit, the device management unit, and the application management unit may each be provided in a separate device.

[0029] The application management unit 210 manages management information and entities of packages and applications. Here, a package is a bundle of multiple applications, and is a unit of product sales. Note that the number of applications included in a package may be one (one or more). Here, since a unit of product sales is generally called an application, a package may be called an application. In this case, an application means a bundle of an executable program that can run on a device and its setting file, and also means a bundle of multiple applications themselves. In order to use an application included in a package on the device 10, it is necessary to grant a license for each package to the device 10. An application is an application that runs on the device 10. Note that the application is not limited to this, and may be a web application or the like in which an application runs on a server device such as the server 5 by requesting processing from a browser of the device 10 to the server device.

[0030] FIG. 4-1 is a diagram showing the basic data model of data stored in a server. The relationship between a device 10 and an application is linked with "application license grant authority" that indicates information on whether an application license can be granted. The value of the "application license grant authority" is determined by whether the type (category) of the device 10, such as the MFP 11 or IWB 14, matches the device category of the service. A service is information that defines what service an application can run on which device 10.

[0031] 4-2 is a diagram showing in more detail the data model of the data stored in the server 5. A device definition (to be described later) and management information of a package to which a license is granted to the device are associated with each device, an application and management information of a service definition (to be described later) are associated with each package, and further, management information of a license definition (to be described later) is associated with this service definition.

[0032] In Figure 4-2, device definitions and service types are associated with packages, but as shown in Figure 4-3, device definitions and service types may be associated with apps. In this case, the sales unit is still the package, but the license granting authority can be determined on a more detailed app-by-app basis than in Figure 4-2.

[0033] Fig. 5 is a diagram showing an example of management information of a package managed by the application management unit 210. As shown in Fig. 5, the application management unit 210 manages, for each package, a package ID, a package name, a package description, a service class, an application list, and the like.

[0034] The package ID is an ID for identifying a package. The package name is the name of the package. The package description is a description of the package. The service class is information for linking the package with the service definition described below. The application list is a list of applications included in the package.

[0035] The license management unit 220 sets and holds service definitions and license definitions including device types of various devices 10. The license management unit 220 also determines whether a license can be granted in relation to the device 10 and a package. The license management unit 220 also performs processing to assign licenses to the devices 10.

[0036] Here, the service definition is information about what kind of service the package provides, and includes device type / name / URL / available languages, etc. The device type indicates on which device 10 this service can operate.

[0037] The license definition is information that determines the method of purchase and sale. License information is issued by inputting specific values, such as the usage start date and the planned termination date, into the license definition. The license information is the substance of the purchased license.

[0038] Fig. 6 is a diagram showing an example of management information of a service definition managed by the license management unit 220. As shown in Fig. 6, the license management unit 220 manages, as a service definition, a service class, a service name, a service description, a service type, the presence or absence of license granting authority, a device type, etc. The license granting authority is information on whether or not a license can be granted in the relationship between the device 10 and a package.

[0039] The service class is an ID for identifying the service definition. The service name is the name of the service, and is set to the same value as the package. The service description is a description of the service, and is set to the same value as the package description. The service type is the type of service, and is information that indicates what kind of service it is.

[0040] The presence or absence of license grant authority sets whether or not a license can be granted. If a license can be granted, "Yes" is set, and if a license cannot be granted, "No" is set. If "Yes" is set, it is necessary to create a license definition, which will be described later.

[0041] The device type can be set to at least one device that can use this service, such as the MFP 11, the projector 13, the IWB 14, etc.

[0042] Fig. 7 is a diagram showing an example of management information of license definitions managed by the license management unit 220. As shown in Fig. 7, the license management unit 220 manages license codes, license names, license types, expiration dates, service classes, device types, and the like as license definitions.

[0043] The license code is an ID for identifying the license definition, and the license name is the name of the license definition.

[0044] The license type indicates the type of license. There are user licenses (licenses that limit the number of users who can use the service) and device licenses (licenses that limit the number of devices that can use the service). Note that the limit number is set when the license is issued, so it is not included in the license definition.

[0045] The expiration date is the expiration date of the license, and can be set to unlimited, in months, or in days.

[0046] The service class is information for linking a license definition with a service definition.

[0047] The device type can be set to at least one device that can use this service, such as the MFP 11, the projector 13, the IWB 14, etc.

[0048] The device management unit 230 registers and manages device information of all devices 10 that are license-managed. The device information is information about the devices 10 to be managed, such as serial IDs and device types.

[0049] In this embodiment, the device type is included in the management information of the service definition and the management information of the license definition, but the device type information may also be included in the management information of the package.

[0050] Fig. 8 is a diagram showing an example of management information of a device definition managed by the device management unit 230. As shown in Fig. 8, the device management unit 230 manages a serial ID, a device type, and the like as the device definition.

[0051] The serial ID is an individual identification ID that is possessed by the device itself. The device type is the type of device, such as MFP, projector, IWB14, etc.

[0052] The control unit 240 transmits various information to the browser 120 installed in the information processing device 12, and the browser 120 displays a license allocation screen, which will be described later.

[0053] When allocating a license to a device, the determination unit 250 compares the device type associated with the device to be allocated with the device type associated with the service to determine whether the license of the service can be allocated to the device to be allocated.

[0054] Next, the registration process of various information (package, service definition, license definition) when creating a package will be described.

[0055] 9 is a sequence diagram showing a registration process of various information (package, service definition, license definition) when creating a package. As shown in Fig. 9, when a package creator requests acquisition of a package creation screen, the browser 120 of the information processing device 12 acquires the package creation screen from the server 5 and displays the package creation screen acquired from the server 5 (step S1).

[0056] Here, Fig. 10 is a diagram showing an example of the package creation screen P1. The package creation screen P1 shown in Fig. 10 is displayed on the browser 120 of the information processing device 12. The package creator inputs various definition information into the package creation screen P1. The various definition information input by the package creator into the package creation screen P1 includes a service name, a service overview, a package name, license control, and a device type.

[0057] The service name is the name of the service. The service name is a unique value on the system.

[0058] The service overview is a description of the service.

[0059] The package name is the name of a product (package) that includes one or more services.

[0060] The license control allows the user to select either "enabled" or "disabled" using a radio button. When "enabled" is selected, the license control means that the service cannot be used unless a license is granted. When "disabled" is selected, the license control means that the service can be used without granting a license.

[0061] The device type is an item for accepting the selection of the type of device (MFP, IWB, projector, video conference system, camera, tablet) that can run the package. In other words, the license of the package to be set on the screen of FIG. 10 can be assigned to the device type selected here. Also, when "All" is selected, the device type is treated as being checked not only for all current device types, but also for device types that will be newly added in the future. Therefore, it is possible to assign a license to newly added device types as well, since the package to be set can be used even for newly added device types.

[0062] The package creator inputs service definition information along with the device type to the package creation screen P1 (step S2).

[0063] Specifically, the package creator selects and inputs the device type on which the target package can operate. The package creator can select multiple device types. If the device type is not input, the default value may be set to either "operable on all device types" or "inoperable on all device types." If the package is created with the assumption that it will be used on an MFP, the device type may be set to MFP as the default value. Elements can be added to the device type information after registration (for example, adding an IWB in addition to an MFP).

[0064] When the "Next" button B1 on the package creation screen P1 is pressed, the browser 120 of the information processing device 12 transitions to a package information input screen.

[0065] Here, Fig. 11 is a diagram showing an example of the package information input screen P2. The package information input screen P2 shown in Fig. 11 is displayed on the browser 120 of the information processing device 12. The package creator inputs various pieces of information into the package information input screen P2.

[0066] The package creator registers the applications to be included in the target package on the package information input screen P2.

[0067] The application name area on the package information input screen P2 is an area for inputting characters to be searched for. The package creator inputs characters to be searched for in the application name area and presses the "Search" button B5. This allows the creator to search for applications to be included in the target package.

[0068] After searching for an app to be included in the target package, the package creator presses the "Register" button B2 of the app to be included in the target package. This allows the app to be registered. When the registration of the app to be included in the target package is completed, the Register button B2 becomes "Registered". When the "Cancel" button B4 on the package information input screen P2 is pressed after the package information is registered, the package associated with the "Cancel" button B4 is cancelled and the "Register" button B2 is displayed. The method of specifying the app to be included in the target package is not necessarily limited to searching for the app name, and any method may be used as long as the PC browser can accept the designation of the app from the package creator. For example, the PC browser 120 may accept the designation of the app by accepting the input of the app's identification number from the user.

[0069] The package creator inputs information about the package on the package information input screen P2 (step S3).

[0070] After registering the information about the package, when the "Next" button B3 on the package information input screen P2 is pressed, the browser 120 of the information processing device 12 transitions to a license definition information input screen.

[0071] Here, Fig. 12 is a diagram showing an example of the license definition information input screen P3. The license definition information input screen P3 shown in Fig. 12 is displayed on the browser 120 of the information processing device 12. The package creator inputs various information into the license definition information input screen P3. The various definition information input by the package creator into the license definition information input screen P3 includes the package name, license name, validity period, license type, charging category, and unit price for each device type.

[0072] The package name is the name of the package entered on the package creation screen P1.

[0073] The license name is the name of the license. If multiple license definitions are defined for a package, the license name is a string that is unique within a package.

[0074] The validity period is the period that is valid from the start date after purchasing the license. Unlimited can also be selected using the radio button.

[0075] The license type selects the type of license allocation (device, user). For example, if the license allocation target is a device, the license type assigns a usage license to each device that executes the app. If the license allocation target is a user, the license type assigns a usage license to each user that uses the app from the device.

[0076] The charge category can be selected using a radio button between sales (charged) and demo (no charge). If sales (charged) is selected, the unit price (charge information) such as the unit price for each device type and the unit price for each user is entered.

[0077] After inputting the license definition information on the license definition information input screen P3 (step S4), the package creator presses the "Register" button B6 on the license definition information input screen P3 (step S5).

[0078] When the "Register" button B6 on the license definition information input screen P3 is pressed, the license management unit 220 registers the service definition (device type, service name, etc.) input via the browser 120 (step S6).

[0079] When the "Register" button B6 on the license definition information input screen P3 is pressed, the license management unit 220 registers the information about the package (such as the package name) input via the browser 120 (step S7).

[0080] When the "Register" button B6 on the license definition information input screen P3 is pressed, the license management unit 220 registers the license definition (device type, license name, expiration date, etc.) input via the browser 120 (step S8).

[0081] In this embodiment, the device type is registered in the service definition and the license definition, but this is not limiting, and the device type may be registered only in the service definition.

[0082] Note that there may be multiple license definitions. Also, if the package can be used without a license, there may be no license definition.

[0083] This is the end of the package creator's role.

[0084] Next, the license allocation process will be described.

[0085] Here, Fig. 13 is a sequence diagram showing the license allocation process. As shown in Fig. 13, a person who wants to use an application (tenant administrator, user) displays a UI for license purchase (license purchase screen) on the browser 120 of the information processing device 12 (step S9), and purchases a license (step S10).

[0086] Here, Fig. 14 is a diagram showing an example of the license purchase screen P4. The license purchase screen P4 shown in Fig. 14 is displayed on the browser 120 of the information processing device 12. The license purchase screen P4 is a screen for inputting a product name, license, unit price, quantity, and start date. On the license purchase screen P4, a person who wants to use an application (tenant administrator, user) selects a product name (package name) and a license, and inputs the quantity. The unit price is displayed when a license is selected.

[0087] The quantity may be selected by radio button between specifying each device type (device type) and specifying all at once regardless of device type. In this case, a person who wants to use the app (tenant administrator, user) may set each device type (device type) or specify all at once (regardless of device type). When specifying each device type (device type) is selected, the browser 120 of the information processing device 12 displays input items that can be specified for each device, as shown in FIG. 14. Furthermore, a person who wants to use the app (user) inputs the start date of the license to be purchased and presses the "Purchase" button B7.

[0088] After the registration process sequence shown in Figure 9, when you purchase a license for each package, "license information" is generated. License information is the actual content of the purchased license. For example, if the license information shows volume=5, the license can be granted to up to five devices.

[0089] 9, the tenant administrator registers a list of devices to be managed in the device management unit 230, in addition to package-related information, service definitions, and license definition information. This enables the device management unit 230 to manage a device list for each tenant.

[0090] Next, the license allocation process will be described.

[0091] When the tenant administrator requests the browser 120 of the information processing device 12 to acquire a license allocation screen (step S11), the browser 120 acquires a license information list from the license management unit 220 (step S12). Here, the license information list is a list of license information including package names, the number of volumes, device types, etc.

[0092] Additionally, the browser 120 acquires device list information including the device type from the device management unit 230 (step S13). The device list information is a list of devices associated with the tenant to which the tenant administrator belongs, and includes the device ID (e.g., MFP_001, etc.) of the device 10, the model name, the installation location, etc.

[0093] After that, the browser 120 displays the license allocation screen P5 (see FIG. 15) (step S14).

[0094] The tenant administrator sets the device license on the license allocation screen P5 (step S15), and after completing the settings, presses the "Save" button B8 on the license allocation screen P5 (step S16).

[0095] Here, Fig. 15 is a diagram showing an example of input to the license allocation screen P5. As shown in Fig. 15, the license allocation screen P5 displays, for each tenant, a list of services based on the license information of the license purchased in step S10 and the device types that can use the services in association with each other. The license allocation screen P5 has an input area A1 in the form of a table, with a package list on the horizontal axis and a list of device IDs of the devices 10 on the vertical axis. The tenant administrator can select the devices 10 to which the licenses are to be granted for each package by checking the combination of the desired package and device 10.

[0096] When the setting of the device license is completed, the browser 120 requests the license management unit 220 to assign the license (step S17).

[0097] When a license allocation request is received, the judgment unit 250 compares the device type corresponding to each package stored in the server 5 with the device type of each device to determine whether or not to allocate the license (step S18), and notifies the browser 120 of the allocation result (step S19).

[0098] In this embodiment, the judgment unit 250 judges whether or not a license can be assigned based on the device type (step S18), but this is not limited to the above, and the judgment whether or not a license can be assigned based on the device type may also be made in the browser 120 of the information processing device 12.

[0099] Here, Fig. 16 is a diagram showing an example of an instance for a data model. In the example shown in Fig. 16, in an environment (tenant) to which an MFP 11 and an IWB 14 belong as devices 10, a user can use a print package for the MFP and a camera package for the IWB.

[0100] In the relationship between the MFP 11 and the print package for MFP, the device type in the device information of the MFP 11 matches the device type in the service definition of the print package for MFP, which is 'MFP', so the license assignment authority is "Yes."

[0101] On the other hand, in the relationship between the MFP11 and the camera package for IWB, the types are different, 'MFP' and 'IWB', so the license grant authority is "not allowed."

[0102] Conversely, in the relationship between the IWB 14 and the camera package for IWBs, the license granting authority is "Yes", but in the relationship with the print package for MFPs, the license granting authority is "No".

[0103] As described above, if there is an item in which the license allocation result is "not allowed" because the license granting authority is "not allowed" in the license allocation permission determination, the license management unit 220 notifies the user of the reason as well.

[0104] If the allocation result is "OK", the browser 120 displays an allocation completion notice (step S20).

[0105] On the other hand, if there is an item with an allocation result of "No", the browser 120 displays a notification of non-allocation including the reason. Fig. 17 is a diagram showing an example of a notification of non-allocation. As shown in Fig. 17, the item with an allocation result of "No" is displayed in an emphasized manner (e.g., shaded), and the reason such as "The license for package B cannot be set in the IWB" is displayed.

[0106] In this way, according to this embodiment, it is possible to avoid assigning to a device a license that the device cannot use. In other words, when a tenant administrator collectively registers package licenses for devices using a PC browser or the like, it is possible to prevent the problem of license resources being wasted due to licenses being assigned to devices that cannot use the package.

[0107] Furthermore, according to this embodiment, it is possible to prevent services such as apps and packages from being installed erroneously on devices of unintended types, thereby preventing malfunctions and thereby avoiding adverse effects on devices and cloud systems.

[0108] In this embodiment, a package is applied as a service, but the present invention is not limited to this and can be applied to various applications, various functions, web services, and the like.

[0109] Here, Fig. 18 is a diagram showing another example of input to the license allocation screen P6. The license allocation screen P6 in the example shown in Fig. 18 has a tabular list X1 that displays, for each tenant, a package list on the horizontal axis and a list of apps included in the package on the vertical axis. The tenant administrator selects a package or app for which he or she wishes to set a license from the list X1.

[0110] When the tenant administrator selects a package as the target for setting a license, the screen transitions to a license allocation screen P7. The license allocation screen P7 is displayed by the PC browser 120, and includes an input area X2 in the form of a table showing a list of apps included in the selected package on the horizontal axis and a list of device IDs of the devices 10 on the vertical axis. The tenant administrator can select the devices 10 to which a license is to be granted for each app included in the package by checking a combination of the app and device 10 included in the desired package.

[0111] Furthermore, the PC browser 120 can also display the remaining licenses in the input area X2 of the license allocation screen P6 based on the license information of the license purchased in step S10 and the number of licenses assigned. The remaining licenses display has the number of licenses that can be granted as the denominator and the number of licenses that have already been granted as the numerator. If "Specify by device type" is selected when purchasing a license, the remaining licenses display can also be displayed by device type.

[0112] In addition, in app_A3 in input area X2 shown in Figure 18, the remaining licenses (MFP) and remaining licenses (IWB) are displayed together. This means that when purchasing the licenses in step S10, the quantity of licenses is not specified for each device type, and the MFP and IWB licenses are purchased together.

[0113] On the other hand, when the tenant administrator selects an app as the target for setting a license, the browser 120 transitions to a license allocation screen P8. The license allocation screen P8 displays an input area X3 in a table format in which the horizontal axis lists the selected apps and the vertical axis lists the device IDs of the devices 10. The tenant administrator can select, for each app, the device 10 to which the license is to be granted by checking the combination of the desired app and device 10.

[0114] Furthermore, in the input area X3 of the license allocation screen P8, the browser 120 can also display the remaining licenses. If "Specify by device type" is selected when purchasing a license, the browser 120 can also display the remaining licenses by device type.

[0115] (Second embodiment) Next, a second embodiment will be described.

[0116] The second embodiment differs from the first embodiment in that in the license allocation process, the browser 120 executes the allocation permission determination. That is, the browser 120 functions as a determination unit. In the following description of the second embodiment, the description of the same parts as in the first embodiment will be omitted, and only the parts different from the first embodiment will be described.

[0117] Here, Fig. 19 is a sequence diagram showing the license allocation process according to the second embodiment. As shown in Fig. 19, when the browser 120 displays the license allocation screen (step S14), the tenant administrator selects a device type such as an MFP or an IWB on the license allocation screen (step S31).

[0118] When the tenant administrator selects a device type, the browser 120 filters the package list by available devices (step S32). That is, the package list is filtered using the selected device type as a filtering key to extract packages available to the device 10 corresponding to the selected device type.

[0119] Here, Fig. 20 is a diagram showing an example of the license allocation screen P9. As shown in Fig. 20, the license allocation screen P9 has a pull-down menu M for selecting a device type such as an MFP or an IWB, and also has an input area A1 in the form of a table showing a package list on the horizontal axis and a list of devices 10 corresponding to the device type selected in the pull-down menu M on the vertical axis. The tenant administrator can select the device 10 to which the license is to be granted for each package by checking the combination of the desired package and device 10. Note that multiple device types can be selected in the pull-down menu M.

[0120] Here, the browser 120 extracts and displays only packages of a device type that matches the device type of the device 10 selected in the pull-down menu M, as shown in Fig. 20. If there is no package of a device type that matches the device type of the device 10 selected in the pull-down menu M, the browser 120 may display "No target device." Even if the server determines whether or not to allocate the device as in the first embodiment, the browser 120 may provide a pull-down menu as shown in Fig. 20 and display only the selected device.

[0121] FIG. 21 is a diagram showing another example of the license allocation screen P10. As shown in FIG. 21, the browser 120 may display the license allocation screen P10 in which a combination of a package and a device 10 for which license assignment cannot be set is grayed out. In this case, the browser 120 determines the device type of each device before displaying the screen of FIG. 21, and compares the device type of each device with the device type corresponding to each package to determine whether or not the device can be allocated. The devices to be subject to the device allocation determination may be only devices corresponding to a tenant identified by previously associating the management information of the device definition with tenant information identifying the tenant to which each device belongs and receiving an input of a tenant ID or the like from a tenant administrator by the browser, or may be all devices included in the management information of the device definition of the device management unit 230.

[0122] In this embodiment, only packages of a device type that matches the device type of the device 10 selected in the pull-down menu M are extracted, but this is not limited to this. The browser 120 may extract only devices of a device type that matches the device type of the package selected in the pull-down menu M.

[0123] In addition, in this embodiment, the device type is selected in S31, but the selection of one device such as MFP_001 or MFP_002 may be accepted instead of the type. In this case, the PC browser 120 determines the type of the selected device according to the management information of the device definition acquired from the device management unit 230, and then performs the package filtering process in step S32.

[0124] On the license allocation screen filtered in this manner, the tenant administrator sets the device license by checking the combination of the desired package and device 10 (step S15), and after completing the settings, presses the Save button on the license allocation screen (step S16).

[0125] When the setting of the device license is completed, the browser 120 requests the license management unit 220 to assign the license (step S17).

[0126] In this manner, according to this embodiment, it is possible to avoid allocating to a device a license that the device cannot use.

[0127] In this embodiment, the license of the package is assigned to each device, but the present invention is not limited to this. The license to be assigned to each device is not limited to the license of the package, and may be any service. For example, the present invention may be applied to a process of assigning the license of a single application to each device, instead of a package including multiple applications. In this case, the server 5 stores application information in which the application information and the device type are linked, and the device type linked to the application information and the device type of the target device are compared to determine whether the license of the application can be assigned. Similarly, it is also possible to determine whether the license of a Web service or a specific function of a service can be assigned instead of a package. In this case, instead of the application information, the Web service information related to the Web service or the function information related to the function can be linked to the device type and stored on the server, and the same process can be performed.

[0128] Furthermore, since the license information includes a maximum number of licenses, the browser 120 may check by issuing a warning or the like when the upper limit (volume) of the number of licenses for the target package is exceeded.

[0129] (Third embodiment) Next, a third embodiment will be described.

[0130] The third embodiment differs from the first or second embodiment in that in the license allocation process, the tenant administrator logs in to the cloud system and acquires a user authentication ticket (or access token) before acquiring the license allocation screen. In the following explanation of the second embodiment, the explanation of the same parts as the first or second embodiment will be omitted, and only the parts that differ from the first or second embodiment will be explained.

[0131] Here, FIG. 22 is a diagram showing an example of functions of the server 5 according to the third embodiment. As shown in FIG. 22, the server 5 has an authentication unit 260 in addition to an application management unit 210, a license management unit 220, a device management unit 230, a control unit 240, and a determination unit 250. In the example of FIG. 22, only modules related to the present embodiment are illustrated, but the modules of the server 5 are not limited to these. Each unit of the server 5 may be composed of one device as in the present embodiment, or may be composed of two or more devices. For example, the license management unit, the device management unit, and the application management unit may be provided in different devices.

[0132] The authentication unit 260 transmits a user authentication ticket (or an access token) to the browser 120 in response to a login from the browser 120 of the information processing device 12.

[0133] Fig. 23 is a sequence diagram showing a part of the license allocation process. As shown in Fig. 23, before acquiring the license allocation screen, when the tenant administrator inputs login information via the browser 120 of the information processing device 12 (step S41) and logs into the cloud system (step S42), the authentication unit 260 issues a user authentication ticket (or an access token that can identify the user) (step S43).

[0134] Thereafter, when the tenant administrator requests the browser 120 of the information processing device 12 to acquire a license allocation screen together with the user authentication ticket (step S11), the browser 120 acquires from the license management unit 220 a license information list registered in the organization managed by the user (tenant administrator) related to the user authentication ticket (step S12). Here, the license information list is a list of license information including package names, the number of volumes, device types, etc.

[0135] Additionally, the browser 120 acquires, from the device management unit 230, device list information registered in the organization (tenant) managed by the user (tenant administrator) related to the user authentication ticket (step S13).

[0136] Then, the browser 120 displays a license allocation screen including a list of multiple types of devices associated with the organization (step S14). After this, similar to the first and second embodiments, the process from step S15 onwards shown in Fig. 13 or the process from step S31 onwards shown in Fig. 19 is performed.

[0137] As described above, according to this embodiment, since a user authentication ticket (or an access token that can identify a user) is sent at the time of a request, the cloud system 2 side can determine which user (tenant administrator) performed the operation. Therefore, the cloud system 2 can acquire license information and a list of device information that are associated with an organization managed by the user (tenant administrator) in question. Therefore, the user (tenant administrator) can collectively assign licenses to multiple types of devices of the tenant to which the user belongs. Furthermore, it is possible to prevent services such as app packages from being erroneously installed on devices of types that are not intended for such services, and to prevent malfunctions. This makes it possible to prevent adverse effects on devices and cloud systems.

[0138] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and a device such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or a conventional circuit module designed to execute each function described above.

[0139] It should be noted that the devices described in the example are merely representative of one of several computing environments for implementing the embodiments disclosed herein.

[0140] In an embodiment, the server 5 includes a plurality of computing devices, such as a server cluster, configured to communicate with each other over any type of communications link, including a network, shared memory, etc., to perform the processes disclosed herein.

[0141] In addition, the device 10 is not limited to an image forming device as long as it is a device equipped with a communication function. The device 10 may be, for example, a PJ (Projector), an IWB (Interactive White Board: a white board having an electronic blackboard function capable of mutual communication), an output device such as a digital signage, a HUD (Head Up Display) device, an industrial machine, an imaging device, a sound collecting device, a medical device, a network home appliance, an automobile (Connected Car), a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game machine, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, a desktop PC, or the like. [Explanation of symbols]

[0142] 1. Information Processing Systems 5 Server 10 Devices 120 Judgment section, display section 220 License Management Department 230 Device Management Department 250 Judgment Department [Prior art documents] [Patent documents]

[0143] [Patent Document 1] Patent No. 5670167

Claims

1. An information processing system comprising at least one server and a device connected to the server via a network, a license management unit that manages services in association with device types that can use the services; a device management unit that manages the device in association with a device type; a determination unit that, when allocating a license to a device, determines whether a license for the service can be allocated to the device by comparing a device type associated with the device to which the license is to be allocated and a device type associated with the service; Equipped with the device type includes a first device type having a printing function and a second device type having a projection function or a display function that is an output function different from the printing function; An information processing system comprising:

2. the determination unit, after selecting a device to be allocated, determines whether a license for the service can be allocated to the device to be allocated; 2. The information processing system according to claim 1 .

3. When the determination unit determines that it is impossible to assign a license for the service, the determination unit notifies the user of a reason why it is impossible to assign a license for the service.

3. The information processing system according to claim 1, wherein the information processing system is a data processing system.

4. the determination unit enables selection of a device to which a license for the service can be assigned from among devices to which the license can be assigned; 3. The information processing system according to claim 1, wherein the information processing system is a data processing system.

5. the determination unit displays a license allocation screen in which a combination of a service and a device to which a license for the service cannot be allocated is grayed out; 3. The information processing system according to claim 1, wherein the information processing system is a data processing system.

6. the license management unit is capable of specifying the number of devices to which the license for the service is to be assigned for each device type, or of specifying the number of devices collectively regardless of device type; 6. The information processing system according to claim 1, wherein the information processing system comprises:

7. a display unit that displays a license allocation screen for accepting allocation of the license for the service from a list of a plurality of types of devices associated with a tenant, the tenant being a unit for managing various devices by a tenant administrator requesting the allocation of the license; the license management unit manages, for each tenant, the services in association with device types that can use the services in accordance with the license allocation accepted on the license allocation screen; 7. The information processing system according to claim 1, wherein the information processing system comprises:

8. The display function is an electronic blackboard function.

2. The information processing system according to claim 1 .

9. A server connected to a device via a network, a license management unit that manages services in association with device types that can use the services; a device management unit that manages the device in association with a device type; a determination unit that, when allocating a license to a device, determines whether a device type associated with the device to which the license is to be allocated and a device type associated with the service can be allocated to the device to which the license is to be allocated; Equipped with the device type includes a first device type having a printing function and a second device type having a projection function or a display function that is an output function different from the printing function; A server comprising:

10. the determination unit, after selecting a device to be allocated, determines whether a license for the service can be allocated to the device to be allocated; 10. The server according to claim 9.

11. When the determination unit determines that the license for the service cannot be assigned, the determination unit notifies the user of a reason why the license for the service cannot be assigned.

11. The server according to claim 9 or 10.

12. the determination unit enables selection of a device to which a license for the service can be assigned from among devices to which the license can be assigned; 11. The server according to claim 9 or 10.

13. the determination unit displays a license allocation screen in which a combination of a service and a device to which a license for the service cannot be allocated is grayed out; 11. The server according to claim 9 or 10.

14. the license management unit is capable of specifying the number of devices to which the license for the service is to be assigned for each device type, or of specifying the number of devices collectively regardless of device type; 14. The server according to any one of claims 9 to 13, characterized in that

15. the license management unit manages the services in association with device types that can use the services for each tenant, which is a unit for managing various devices by a tenant administrator; 15. The server according to any one of claims 9 to 14, characterized in that

16. A computer that controls a server that is connected to a device via a network a license management unit that manages services in association with device types that can use the services; a device management unit that manages the device in association with a device type; a determination unit that, when allocating a license to a device, determines whether a device type associated with the device to which the license is to be allocated and a device type associated with the service can be allocated to the device to which the license is to be allocated; Function as a the device type includes a first device type having a printing function and a second device type having a projection function or a display function that is an output function different from the printing function; program.

17. A method for granting a license in an information processing system including at least one server and a device connected to the server via a network, comprising: a license management step of managing a service in association with a device type that can use the service; a device management step of managing the device in association with a device type; a determination step of, when allocating a license to a device, determining whether a license for the service can be allocated to the device to be allocated by comparing a device type associated with the device to be allocated with a device type associated with the service; Including, the device type includes a first device type having a printing function and a second device type having a projection function or a display function that is an output function different from the printing function; A method of granting a license.

Images