Information processing system, server, and program

Abstract

To avoid assigning, to a device, a license that cannot be used by the device.SOLUTION: An information processing system with at least one server and a device connected to the server via a network comprises: a license management unit that manages a service and device types that can use the service in association with each other; a device management unit that manages the devices and the device types in association with each other; and a determination unit that, in assigning a license to a device, compares the device type associated with an assignment target device with the device type associated with the service to determine if the license of the service can be assigned to the assignment target 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 Art

[0002] Conventionally, in dedicated devices such as MFPs, IWBs, and projectors, there are new service provision forms. The new service provision form is a form in which a user uses only the functions necessary when needed. In order to use the service of such a service provision form, a company or the like needs to purchase a license for the service from a service sales company (selling company). After purchasing the license, a company or the like assigns the license to a device, a user, or the like. Licenses for services include a device license that specifies a device that can be used and a user license that specifies a user who can be used.

[0003] Patent Document 1 (Japanese Patent No. 5670167) discloses a technique for controlling so that a plurality of licenses of the same user are not assigned when there are a plurality of licenses for one application.

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, services (applications, packages, functions, web services, etc.) often have a fixed target device. Therefore, in license management, if the service and the target device are simply associated, a license may be assigned to a device of a type that is not intended for the service. This tendency becomes more prominent as the types of devices increase.

[0005] The present invention has been made in view of the above, and an object thereof is to avoid assigning a license that a device cannot use to the device.

Means for Solving the Problems

[0006] In order to solve the above-described 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 by associating a service with a device type that can use the service; a device management unit that manages by associating the device with the device type; and a determination unit that determines whether a license of the service can be assigned to a device to be assigned by comparing a device type associated with the device to be assigned with a device type associated with the service when assigning a license to the device. 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 which is an output function different from the printing function.

Effect of the Invention

[0007] According to the present invention, it is possible to avoid assigning a license that the device cannot use to the device.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4-1

Figure 4-2

Figure 4-3

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Embodiments for Carrying Out the Invention

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

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

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

[0012] As an example of various devices 10 connected to the cloud system 2, a multifunction peripheral (MFP) 11 which is an aspect of an image forming apparatus, an information processing apparatus 12 such as a notebook PC (Personal Computer) or a tablet terminal, a PJ (Projector) 13, and an IWB (Interactive White Board: an electronic whiteboard having an electronic blackboard function capable of mutual communication) 14 will be described as examples. However, it is not limited thereto, and any device capable of receiving services such as a copier, a scanner, a FAX, a camera, and a remote conference terminal may be used. Note that the multifunction peripheral 11 is a device having a plurality of different functions such as a copying function, a scanning function, a printing function, and a fax function.

[0013] The information processing device 12 is a notebook PC, a tablet terminal, or the like as described above. The information processing device 12 installs a browser 120 that functions as a display unit. Note that 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, an office, or a store can use the browser 120 (or dedicated software) to edit the "license setting information" of various devices 10 (such as granting or revoking licenses). A tenant is a unit in which a tenant administrator manages various devices 10. Also, the tenant administrator may be two or more users.

[0014] The cloud system 2 has a server device group composed 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. In the example of FIG. 1, as devices 10 included in the system 1 that becomes a client when viewed from the cloud system 2 side, an MFP 11, an information processing device 12, a projector 13, and an IWB 14 are exemplified, but it is not limited thereto, and the number and types of devices 10 included in the system 1 are arbitrary.

[0015] Although details will be described later, when a license for each package is granted to each device 10, the user of each device 10 can use the package in the server 5 (cloud system 2). Also, the "license setting information" indicating which package license is assigned to which device 10 is managed in the server 5 (cloud system 2). Hereinafter, the specific configuration of the server 5 will be described.

[0016] FIG. 2 is a diagram showing an example of the 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, an HD 504, an 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] Among these, the CPU 501 controls the operation of the entire server 5. The ROM 502 stores programs used for driving the CPU 501 such as IPL. The RAM 503 is used as a work area for the CPU 501.

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

[0020] The display 506 displays various information such as a cursor, menu, window, characters, or images.

[0021] The external device connection I / F 508 is an interface for connecting various external devices. The external devices in this case are, for example, a USB (Universal Serial Bus) memory, a printer, etc.

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

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

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

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

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

[0027] Next, the functions exhibited by the CPU 501 of the server 5 by executing the programs stored in the ROM 502 and the HD 504 will be described. Here, descriptions of functions known in the art will be omitted, and the characteristic functions exhibited by the CPU 501 of the server 5 of the present embodiment will be described in detail.

[0028] Here, FIG. 3 is a diagram showing an example of the functions of the server 5. As shown in FIG. 3, the server 5 includes 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 the modules related to the present embodiment are illustrated, but the modules included in the server 5 are not limited to these. Also, each part of the server 5 may be configured by one device as in the present embodiment, or may be configured by two or more devices. For example, the license management unit, the device management unit, and the application management unit may be provided in separate devices respectively.

[0029] The application management unit 210 manages the management information and entities of packages and applications. Here, a package is a collection of a plurality of 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 the unit of product sales is sometimes generally called an application, the package may be called an application. In that case, an application means, in addition to a collection of an executable program that can operate on a device and its configuration file, a collection of a plurality of the applications themselves. In order to use the applications 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 operates on the device 10. Note that the application is not limited to this, and may be a web application or the like in which the application operates on a server device such as the server 5 by requesting processing from the server device such as the server 5 from a browser or the like of the device 10.

[0030] FIG. 4-1 is a diagram showing the basics of a data model of data stored in a server. Associated with the relationship between the device 10 and the application is an "application license granting right" that represents information on whether an application license can be granted. The value of the "application license granting right" is determined by whether the type (category) of the device 10 such as the MFP 11 and the IWB 14 matches the device type of the service. A service is information that defines what services an application can operate on which device 10.

[0031] FIG. 4-2 is a diagram showing in more detail the data model of the data stored in the server 5. For each device, management information of the device definition described later and the package licensed for the device is associated, and for each package, management information of the application and the service definition described later is associated. Further, management information of the license definition described later is associated with this service definition.

[0032] Note that in FIG. 4-2, the device definition and the service type are associated with the package, but as shown in FIG. 4-3, the device definition and the service type may be associated with the application. In this case, the sales unit is still the package, but the license granting authority can be determined in units of applications finer than FIG. 4-2.

[0033] FIG. 5 is a diagram showing an example of the management information of the 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, an explanation of the package, a service class, an application list, and the like.

[0034] The package ID is an ID for identifying the package. The package name is the name of the package. The explanation of the package is an explanation about the package. The service class is information for associating the package with the service definition described later. 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 the device types of various devices 10. Further, the license management unit 220 determines whether a license can be granted in the relationship between the device 10 and the package. Further, the license management unit 220 performs a process of assigning a license to the device 10.

[0036] Here, the service definition is information on what services a package provides, such as device type / name / URL / available languages, etc. The device type indicates on which devices 10 this service can operate.

[0037] The license definition is information that determines the method of buying and selling. By inputting specific values such as the start date of use and the scheduled cancellation date into the license definition, license information is issued. The license information is the entity of the purchased license.

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

[0039] The service class is an ID for specifying the service definition. The service name is the name of the service, and the same value as the package is set. The service description is an explanation of the service, and the same value as the package description is set. The service type is the type of the service, which is information indicating what kind of service it is.

[0040] The presence or absence of the license granting authority sets whether a license can be granted. When a license can be granted, "Yes" is set, and when a license cannot be granted, "No" is set. When "Yes" is set, the creation of the license definition described later becomes essential.

[0041] The device type allows at least one or more devices available for this service, such as MFP 11, projector 13, IWB 14, etc., to be set.

[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, as license definitions, a license code, a license name, a license type, an expiration date, a service class, a device type, and the like.

[0043] The license code is an ID for specifying a license definition. The license name is the name of the license definition.

[0044] The license type indicates what kind of license it is. There are a user license (a license that restricts the number of users who can use the service) and a device license (a license that restricts the number of devices that can use the service). Note that the restricted number is set when issuing the license and is not included in the license definition.

[0045] The expiration date is the expiration date of the license. It is set either indefinitely, in months, or in days.

[0046] The service class is information for associating the license definition with the service definition.

[0047] The device type allows at least one or more devices available for this service, such as MFP11, projector 13, IWB14, etc. to be set.

[0048] The device management unit 230 registers and manages the device information of all devices 10 under license management. The device information is information regarding the device 10 to be managed, such as a serial ID and a device type.

[0049] Note that 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 device definitions managed by the device management unit 230. As shown in FIG. 8, the device management unit 230 manages, as device definitions, a serial ID, a device type, and the like.

[0051] The serial ID is a solid identification ID held by the device body. The device type is the type of devices such as MFP, projector, IWB14, etc.

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

[0053] When allocating a license to a device, the determination unit 250 determines whether a license for the service can be allocated to the device to be allocated by comparing the device type associated with the device to be allocated with the device type associated with the service.

[0054] Next, the registration process of various information (package, service definition, license definition) at the time of package creation will be described.

[0055] Here, FIG. 9 is a sequence diagram showing the registration process of various information (package, service definition, license definition) at the time of package creation. As shown in FIG. 9, when there is a request from the package creator to obtain a package creation screen, the browser 120 of the information processing apparatus 12 obtains the package creation screen from the server 5 and displays the package creation screen obtained 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 apparatus 12. For the package creation screen P1, the package creator inputs various definition information. The various definition information input by the package creator to the package creation screen P1 is the service name, service outline, package name, license control, and 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 summary is an explanation about the service.

[0059] The package name is the product name used when selling a product (package) containing one or more services.

[0060] License control can be selected with a radio button as either valid or invalid. If valid is selected, the license control shall be such that the service cannot be used without granting a license. Also, if invalid is selected, the license control shall be such that the service can be used without license grant.

[0061] The device type is an item for accepting selection of the type of device (MFP, IWB, projector, video conferencing system, camera, tablet) that can operate the package. That is, for the device of the type selected here, a license for the package to be set on the screen of FIG. 10 can be assigned. Also, if "All" is selected, the device type shall be treated as being checked for the types of all current devices as well as the types of devices newly added in the future. Therefore, even for the type of a newly added device, it is assumed that the package to be set can be used, and license assignment to the type of the newly added device is also made possible.

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

[0063] Specifically, the package creator selects and inputs, as the device type, the devices on which the target package can operate. The package creator can select multiple device types. If the device type is not input, either the ability to operate on all device types or the inability to operate on all device types may be set as the default value. Also, if the package is created assuming an MFP, the device type may be set as MFP by default. Also, the device type information can have elements added after registration (for example, adding an IWB in addition to the MFP).

[0064] When the "Next" button B1 on the package creation screen P1 is pressed, the browser 120 of the information processing apparatus 12 transitions to the 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 apparatus 12. The package creator inputs various information for 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 provided on the package information input screen P2 is an area for inputting characters to be searched. The package creator inputs the characters to be searched in the application name area and presses the "Search" button B5. Thereby, the applications to be included in the target package can be searched.

[0068] After the package creator searches for the apps to be included in the target package, the package creator presses the "Register" button B2 for the apps to be included in the target package. By doing so, the apps to be included in the target package can be registered. Note that when the registration of the apps to be included in the target package is completed, the registration button B2 will show "Registered". Note that after the information regarding the package is registered, if the "Cancel" button B4 provided on the package information input screen P2 is pressed, the registration of the package associated with the "Cancel" button B4 will be cancelled and the "Register" button B2 will be displayed. Note that the method for specifying the apps to be included in the target package is not necessarily limited to searching by app name, and any method is acceptable as long as the PC browser accepts the specification of the apps from the package creator. For example, the PC browser 120 may accept the specification of the apps by accepting the input of the app identification numbers from the user.

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

[0070] After the information regarding the package is registered, if the "Next" button B3 on the package information input screen P2 is pressed, the browser 120 of the information processing apparatus 12 will transition to the 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 apparatus 12. The package creator inputs various types of information to the license definition information input screen P3. The various definition information that the package creator inputs to the license definition information input screen P3 includes the package name, license name, expiration date, license form, billing category, and unit price for each device type.

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

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

[0074] The validity period is the period during which the license becomes valid from the start date after purchasing the license. With the radio button, unlimited is also selectable.

[0075] The license form is to select the form of license assignment (device, user). For example, if the license assignment target is a device, the usage license is assigned to each device that runs the app. Note that if the license assignment target is a user, the usage license is assigned to each user who uses the app from the device.

[0076] The billing category can be selected with a radio button between sales (with billing) and demo (without billing). When sales (with billing) is selected, enter the unit price (billing information) such as the unit price for each device type and the user unit price.

[0077] After the package creator inputs the license definition information (step S4) for the license definition information input screen P3, the "Register" button B6 on the license definition information input screen P3 is pressed (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 related to the package (package name, etc.) 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] Note that in this embodiment, the device type is registered in the service definition and the license definition, but it is not limited to this, and it 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, the license definition may not be necessary.

[0083] This is the role of the package creator.

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

[0085] Here, FIG. 13 is a sequence diagram showing the license assignment process. As shown in FIG. 13, a person who wants to use the application (tenant administrator, user) displays a UI for license purchase (license purchase screen) on the browser 120 of the information processing apparatus 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 apparatus 12. The license purchase screen P4 is a screen for inputting the product name, license, unit price, quantity, and start date. For the license purchase screen P4, a person who wants to use the application (tenant administrator, user) selects the product name (package name) and the license and inputs the quantity. Note that the unit price is displayed when the license is selected.

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

[0088] After the sequence of the registration process shown in FIG. 9, when the license for each package is purchased, "license information" is generated. The license information is the entity of the purchased license. For example, if volume=5 is shown in the license information, the license can be granted to up to 5 devices.

[0089] Although not described in the sequence of the registration process shown in FIG. 9, the tenant administrator registers a list of devices to be managed with the device management unit 230 in addition to the information regarding the package, the service definition, and the license definition information. Thereby, the device management unit 230 can manage the 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 apparatus 12 to obtain the license allocation screen (step S11), the browser 120 obtains a license information list from the license management unit 220 (step S12). Here, the license information list is a list of license information including the package name, the volume number, the device type, and the like.

[0092] In addition, 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 of the device 10 (for example, MFP_001, etc.), the model name, the installation location, and the like.

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

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

[0095] Here, FIG. 15 is a diagram showing an input example for the license allocation screen P5. As shown in FIG. 15, the license allocation screen P5 displays a list of services based on the license information of the licenses purchased in step S10 for each tenant and the device types that can use the services, in association with each other. The license allocation screen P5 has a table-shaped input area A1 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 license is to be granted for each package by checking the combination of the desired package and the device 10.

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

[0097] When there is a license allocation request, the determination unit 250 compares the device types corresponding to each package stored in the server 5 with the device types of each device to determine whether the license can be allocated (step S18), and notifies the browser 120 of the allocation result (step S19).

[0098] Note that, in the present embodiment, the determination unit 250 determines whether a license can be assigned based on the device type (step S18). However, the present invention is not limited to this, and the browser 120 of the information processing apparatus 12 may determine whether a license can be assigned based on the device type.

[0099] Here, FIG. 16 is a diagram showing an example of an instance with respect to a data model. In the example shown in FIG. 16, in an environment (tenant) to which the MFP 11 and the IWB 14 belong as the device 10, it is assumed that the 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 the MFP, since the device type of the device information of the MFP 11 and the device type of the service definition of the print package for the MFP match as 'MFP', the license granting authority is 'permitted'.

[0101] On the other hand, in the relationship between the MFP 11 and the camera package for the IWB, since the types are different as 'MFP' and 'IWB', the license granting authority is 'not permitted'.

[0102] Conversely, in the relationship between the IWB 14 and the camera package for the IWB, the license granting authority is 'permitted', but in the relationship with the print package for the MFP, the license granting authority is 'not permitted'.

[0103] As described above, in the license assignment determination, if there is an item for which the assignment result is 'no' because the license granting authority is 'not permitted', the license management unit 220 notifies including the reason.

[0104] When the assignment result is 'permitted', the browser 120 displays a completion notice of the assignment (step S20).

[0105] On the other hand, when there is an item with an allocation result of "no", the browser 120 displays a non-allocation notice including the reason. Here, FIG. 17 is a diagram showing an example of the non-allocation notice. As shown in FIG. 17, the item with an allocation result of "no" is emphasized and displayed (for example, shaded display), and a reason such as "The license of Package B cannot be set in the IWB" is displayed.

[0106] As described above, according to this embodiment, it is possible to avoid allocating a license that the device cannot use to the device. That is, when the tenant administrator registers the package license for the device in a lump using a PC browser or the like, it is possible to prevent the problem that the license resource is wasted by allocating the license to a device that cannot use the package.

[0107] Further, according to this embodiment, it is possible to avoid accidentally installing a service such as an app package on a device of an unexpected type and prevent malfunction, thereby avoiding having an adverse impact on the device or the cloud system.

[0108] Note that in this embodiment, a package is applied as a service, but needless to say, it is not limited to this, and it is also applicable to various apps, various functions, web services, and the like.

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

[0110] When the tenant administrator selects a package as the target for license settings, the system transitions to the license allocation screen P7. The license allocation screen P7 is displayed by the PC browser 120 and includes a tabular input area X2 with 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 licenses are to be granted for each app included in the package by checking the combinations of the apps included in the desired package and the devices 10.

[0111] Also, the PC browser 120 can display the remaining license display 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 allocated. The remaining license display has the number of licenses that can be granted as the denominator and the number of licenses already granted as the numerator. When "Specify for each device type" is selected at the time of license purchase, it is also possible to display the remaining license display for each device type.

[0112] In the app_A3 in the input area X2 shown in FIG. 18, the remaining licenses (MFP) and the remaining licenses (IWB) are displayed together, which means that at the time of license purchase in step S10, the quantity of licenses was not specified for each device type, and the licenses for MFP and IWB were purchased together.

[0113] On the other hand, when the tenant administrator selects an app as the target for license settings, the browser 120 transitions to the license allocation screen P8. The license allocation screen P8 displays a tabular input area X3 with a list of the selected apps on the horizontal axis and a list of device IDs of the devices 10 on the vertical axis on the license allocation screen. The tenant administrator can select the devices 10 to which licenses are to be granted for each app by checking the combinations of the desired apps and the devices 10.

[0114] Also, in the input area X3 of the license allocation screen P8, the browser 120 can also display the remaining license display. When "specified for each device type" is selected at the time of license purchase, the browser 120 can also display the remaining license display for each device type.

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

[0116] The second embodiment is different from the first embodiment in that the browser 120 executes the allocation availability determination in the license allocation process. That is, the browser 120 functions as a determination unit. Hereinafter, in the description of the second embodiment, the description of the same parts as those in the first embodiment will be omitted, and 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 for the license allocation screen (step S31).

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

[0119] Here, FIG. 20 is a diagram showing an example of a license allocation screen P9. As shown in FIG. 20, the license allocation screen P9 includes a pull-down menu M for selecting device types such as MFPs and IWBs, and a tabular input area A1 with 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 the device 10. Note that multiple device types can be selected in the pull-down menu M.

[0120] Here, as shown in FIG. 20, the browser 120 extracts and displays only the packages of the device type that matches the device type of the device 10 selected in the pull-down menu M. If there is no package of the 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". Also, even when the server determines whether allocation is possible as in the first embodiment, the browser 120 may provide a pull-down menu as shown in FIG. 20 and display only the selected devices.

[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 the combination of the package for which license granting settings are not possible and the device 10 is grayed out. In this case, before displaying the screen of FIG. 21, the browser 120 determines the device type of each device, and performs the allocation availability determination by comparing the device type of each device with the device type corresponding to each package. As the devices subject to the determination of device allocation availability, only the devices corresponding to the tenant specified by associating tenant information for identifying the tenant to which each device belongs with the management information of the device definition in advance and receiving an input such as a tenant ID from the tenant administrator by the browser may be targeted, or all the devices included in the management information of the device definition of the device management unit 230 may be targeted.

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

[0123] Also, in the present embodiment, the device type is selected in S31, but instead of the type, the selection of one device such as MFP_001 or MFP_002 may be accepted. 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] For the license allocation screen filtered in this way, the tenant administrator sets the device license by checking the combination of the desired package and the device 10 (step S15), and after the setting is completed, 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 allocate a license (step S17).

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

[0127] In this embodiment, the package license is allocated to each device, but the present invention is not limited to this. What is allocated to each device is not limited to the package license, and any service may be used. For example, the present invention is also applicable to a process of allocating a license of a single application to each device instead of a package including a plurality of applications. In this case, the application information in which the application information is associated with the device type is stored in the server 5, and it is only necessary to compare the device type associated with the application information with the device type of the target device to determine whether the application license can be allocated. Similarly, it is also possible to determine whether a license for a Web service or a specific function of a service can be allocated instead of a package. In this case, the device type may be associated with Web service information related to the Web service or function information related to the function instead of the above application information and stored on the server, and the same process may be performed.

[0128] In addition, since the license information includes the maximum number of licenses, the browser 120 may perform a check such as issuing a warning when the upper limit (Volume) of the number of licenses of the target package is exceeded.

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

[0130] In the third embodiment, in the license assignment process, the tenant administrator logs in to the cloud system and obtains a user authentication ticket (or access token) before obtaining the license assignment screen, which is different from the first embodiment or the second embodiment. Hereinafter, in the description of the second embodiment, the description of the same parts as those in the first embodiment or the second embodiment will be omitted, and the parts different from the first embodiment or the second embodiment will be described.

[0131] Here, FIG. 22 is a diagram showing an example of the functions of the server 5 according to the third embodiment. As shown in FIG. 22, the server 5 includes an application management unit 210, a license management unit 220, a device management unit 230, a control unit 240, a determination unit 250, and in addition, an authentication unit 260. In the example of FIG. 22, only the modules related to this embodiment are illustrated, but the modules included in the server 5 are not limited to these. Also, each part 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 be provided in separate devices respectively.

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

[0133] FIG. 23 is a sequence diagram showing a part of the license assignment process. As shown in FIG. 23, before obtaining the license assignment screen, when the tenant administrator inputs login information via the browser 120 of the information processing device 12 (step S41) and logs in to 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] After that, when the tenant administrator requests the browser 120 of the information processing apparatus 12 to acquire the 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) to which the user authentication ticket pertains (step S12). Here, the license information list is a list of license information including the package name, the number of volumes, the device type, and the like.

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

[0136] After that, the browser 120 displays a license allocation screen including a list of multiple types of devices associated with the organization (step S14). After this, in the same manner as in the first embodiment and the second embodiment, the processes from step S15 and subsequent steps shown in FIG. 13, or the processes from step S31 and subsequent steps shown in FIG. 19 are performed.

[0137] As described above, according to the present embodiment, since the user authentication ticket (or an access token by which the user can be identified) is sent at the time of request, the cloud system 2 side can determine which user (tenant administrator) has performed the operation. Therefore, the cloud system 2 can acquire a list of license information and device information registered in association with the organization managed by the user (tenant administrator). Accordingly, the user (tenant administrator) can allocate licenses to multiple types of devices of the tenant to which the user belongs all at once. Furthermore, it is possible to avoid being erroneously installed on a device of a type for which services such as an application package are not assumed, and prevent malfunction. Thereby, it is possible to avoid adversely affecting the device and the cloud system.

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

[0139] Note that the device group described in the embodiments merely shows one of a plurality of computing environments for implementing the embodiments disclosed in this specification.

[0140] In the embodiment, the server 5 includes a plurality of computing devices such as a server cluster. The plurality of computing devices are configured to communicate with each other via an arbitrary type of communication link including a network, a shared memory, etc., and implement the processing disclosed in this specification.

[0141] Note that the device 10 is not limited to an image forming apparatus as long as it is a device having a communication function. The device 10 may be, for example, an output device such as a PJ (Projector), an IWB (Interactive White Board), a digital signage, a HUD (Head Up Display) device, an industrial machine, an imaging device, a sound collection device, a medical device, a network home appliance, a 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, or a desktop PC.

Description of Reference Numerals

[0142] 1 Information Processing System 5 Server 10 Device 120 Judgment Unit, Display Unit 220 License Management Unit 230 Device Management Unit 250 Judgment Unit

Prior Art Documents

Patent Documents

[0143]

Patent Document 1

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 by associating a service with a device type for which the service is available, a device management unit that manages by associating the device with a device type, a determination unit that determines whether a license for the service can be assigned to a device to be assigned by comparing the device type associated with the device to be assigned with the device type associated with the service when assigning a license to the device, comprising, 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 which is an output function different from the printing function, characterized in that it is an information processing system.

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

3. When the determination unit determines that the assignment of the license for the service is impossible, it notifies the reason for determining that the assignment of the license for the service is impossible. The information processing system according to claim 1 or 2, characterized in that.

4. The determination unit enables selection of a device to be assigned from among devices for which the assignment of the license for the service is possible. The information processing system according to claim 1 or 2, characterized in that.

5. The determination unit causes a license assignment screen to be displayed in which combinations of services and devices for which the assignment of the license for the service is impossible are grayed out. The information processing system according to claim 1 or 2, characterized in that.

6. The license management unit enables specification of the quantity of devices to which the license for the service is to be assigned for each device type or collectively regardless of the device type. The information processing system according to any one of claims 1 to 5, characterized in that.

7. A display unit that displays a license assignment screen for receiving an assignment of a license for the service from a list of a plurality of types of devices associated with a tenant, which is a unit in which a tenant administrator who requests the assignment of the license manages various devices. The license management unit manages, for each tenant, by associating the service with the device type that can use the service, according to the allocation of the license received on the license allocation screen. The information processing system according to any one of claims 1 to 6, characterized in that.

8. The display function is an electronic blackboard function. The information processing system according to claim 1, characterized in that.

9. A server connected to a device via a network, A license management unit that manages by associating a service with a device type that can use the service, A device management unit that manages by associating the device with the device type, When allocating a license to a device, a determination unit that determines whether the license of the service can be allocated to the device to be allocated by comparing the device type associated with the device to be allocated with the device type associated with the service, Comprising, 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 which is an output function different from the printing function. A server characterized in that.

10. The determination unit determines whether the license of the service can be allocated to the device to be allocated after selecting the device to be allocated. The server according to claim 9, characterized in that.

11. When the determination unit determines that the allocation of the license of the service is impossible, it notifies the reason why the allocation of the license of the service is impossible. The server according to claim 9 or 10, characterized in that.

12. The determination unit enables the selection of the device to be allocated from among the devices to which the license of the service can be allocated. The server according to claim 9 or 10, characterized in that.

13. The determination unit displays a license allocation screen in which combinations of services and devices for which the allocation of the license of the service is impossible are grayed out. The server according to claim 9 or 10, characterized in that.

14. The license management unit enables the specification of the quantity of devices to which the license of the service is to be allocated, either for each device type or collectively regardless of the device type. The server according to any one of claims 9 to 13, characterized in that.

15. The license management unit manages by associating the service with the device type that can use the service for each tenant, which is a unit for a tenant administrator to manage various devices. The server according to any one of claims 9 to 14, characterized in that.

16. A computer that controls a server connected to a device via a network, A license management unit that manages by associating a service with a device type that can use the service, A device management unit that manages by associating the device with the device type, When assigning a license to a device, a determination unit that determines whether the license of the service can be assigned to the device to be assigned by comparing the device type associated with the device to be assigned with the device type associated with the service, Function as, 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, which is an output function different from the printing function. Program.

17. A license granting method in an information processing system including at least one server and a device connected to the server via a network, A license management step of managing by associating a service with a device type that can use the service, A device management step of managing by associating the device with the device type, A determination step of determining whether the license of the service can be assigned to the device to be assigned by comparing the device type associated with the device to be assigned with the device type associated with the service when assigning a license to the device, 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, which is an output function different from the printing function. A license granting method, characterized in that.

Images