JP2019121092A - Information processing apparatus, information processing system, and integration method - Google Patents

Abstract

To provide an information processing apparatus, an information processing system, and an integration method capable of easily specifying organization information of an integration source and an integration destination using a device usable for service.SOLUTION: A cloud system 50 includes a tenant integration request reception unit 56 and a tenant integration control unit 55. The tenant integration request reception unit receives a request for integration of organization information from a device belonging to first organization information. The tenant integration control unit refers to device information that associates identification information of the organization information with identification information of the device and acquires identification information of the first organization information associated with the identification information of the device, and then, acquires identification information of second organization information of an integration destination to which the first organization information is integrated based on authentication information of the second organization information transmitted from the device. Thereafter, the tenant integration control unit integrates the first organization information specified by the identification information of the first organization information and the second organization information specified by the identification information of the second organization information.SELECTED DRAWING: Figure 9

Description

  The present invention relates to an information processing apparatus, an information processing system, and an integration method.

  One of the forms of cloud services is a service form called Software as a Service (SAAS). In SAAS, software is not run on the user side, but is run on the cloud side, and users use the functions of the software via the network. And in SAAS, a multi-tenant in which a plurality of tenants share the same system is generally adopted. A tenant is a customer of cloud service. In addition to being a tenant on an enterprise basis, it may be a tenant in organizations of various granularity such as departments and groups. For this reason, a tenant may be called organization information.

  By the way, in the multi-tenant type cloud service, there are cases where the tenant can use the cloud service in free trial. The free trial is to provide a user with services for a certain period of time without charge, mainly to provide opportunities for sales promotion and trial experience. Customers who like the cloud service in the free trial can continue to use the cloud service by performing billing procedures.

  Since the purpose of the free trial is to have users who have never used the cloud service widely use it, the cloud service does not require the user to present identification cards. For this reason, the reliability of the application information (company name, department name, name, etc.) is generally low, so whether or not the same organization (for example, the same company, the same department, etc.) subscribes to the same cloud service when applying for free trial. No decision has been made. Even if it is judged, it is not preferable to integrate a tenant for which a fee-based contract has already been made and a free trial tenant because the application information is not reliable.

  However, if an employee who has applied for a free trial wants to use the cloud service continuously, but another tenant of the same organization has already made a paid contract, multiple tenants have been contracted for the same cloud service. become. In this case, on the customer side, it is necessary to manage devices, pay, and manage contracts for each tenant. Also, from the perspective of the cloud service, it is necessary to manage devices, charge usage fees, collect, and manage contracts for each tenant.

  Therefore, there are cases where the customer or the cloud service wants to integrate multiple tenants. In response to such a request for tenant integration, a technology has been devised to integrate another tenant created within the same company into another tenant for which a for-fee contract has been made (see, for example, Patent Document 1). ). Patent Document 1 discloses a technique for editing a tenant management table of a management server and transferring tenants and deleting unnecessary tenants when transferring data between tenants for integration.

  However, conventionally, there has been a problem that it is not possible to easily identify the integration source and integration destination tenants using devices used for services such as cloud services. That is, conventional tenant integration requires that customer engineers, sales representatives, etc. contact users for tenant integration to obtain information on integration source and integration destination tenants, and both the cloud service side and the customer side The burden of was heavy.

  In addition, there is a problem in that there is no immediacy because it is necessary for a customer engineer or the like to carry out work on integration by bringing back information on the integration source and integration destination tenant.

  This tenant integration issue is not only the integration between the integration source used in the free trial and the integration destination in the paid contract, but also the integration destination used in the free trial as the integration source used in the free trial. It may also occur in the case of integration with a consignee, or in the consignment contractor with a concession contractor.

  In view of the above problems, an object of the present invention is to provide an integration method capable of easily specifying organization information of an integration source and an integration destination using an apparatus used for a service.

  The present invention is an information processing apparatus for providing a service to an apparatus belonging to organization information, wherein the integration request accepting means receives an integration request for the organization information from an apparatus belonging to first organization information, the organization The identification information of the first organization information associated with the identification information of the device is acquired with reference to the device information that associates the identification information of the information with the identification information of the device, and the first organization information is integrated Integrated control means for acquiring identification information of second integrated organization information to be integrated based on the authentication information of the second organization information transmitted from the device, the integrated control means comprising The first organization information specified by the identification information of the first organization information and the second organization information specified by the identification information of the second organization information are integrated.

  It is possible to provide an information processing apparatus capable of easily specifying organization information of integration source and integration destination using an apparatus used for service.

It is an example of the figure explaining the relation of a tenant, a user, and a device. It is an example of the figure explaining the outline of integration of a tenant. It is an example of the figure explaining the registration method of a device. FIG. 8 is an example of a diagram for explaining a confirmation procedure of a device registration state. It is an example of the figure which illustrates integration of a tenant typically. It is an example of the schematic block diagram of an information processing system. It is an example of the schematic hardware block diagram of a cloud system. It is an example of the block diagram showing the rough hardware constitutions of the device. It is an example of the functional block diagram which shows the function of the cloud system which an information processing system has, and a device in block form. It is a figure which shows the example of a screen displayed on the operation panel of a device. It is an example of the sequence diagram which shows the procedure which an information processing system integrates with a tenant. It is an example of the sequence diagram which shows the procedure which an information processing system integrates with a tenant. It is an example of the flowchart figure which shows the procedure which a home screen provision part produces the web page of a home screen. It is an example of the flowchart figure which shows the procedure which the tenant integrated control section limits the person who does integration of the tenant. It is an example of the flowchart figure which shows the procedure which the license management section allocates the license to the user or device of integration source.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<Form of tenant creation>
FIG. 1 is an example of a diagram for explaining the relationship between a tenant 9, a user U, and a device 10. First, the tenant 9 conventionally means a tenant (store child) such as a land or a room, but on the Internet, it means a customer who uses resources in the cloud system 50 for a fee or free of charge. The tenant 9 is, for example, an organization such as a company, a department, or a group, and the tenant 9 may be called organization information. Therefore, the tenant 9 is a unit of charging (when the cloud service is charged).

  The user U is a user (meaning an individual) of the cloud service, and one or more users U belong to one tenant 9. For example, an employee of an organization such as a company may be mentioned. The device 10 is a device used by the user U when the user U uses the cloud service, and one tenant 9 includes one or more devices 10. The device 10 may be, for example, a multifunction peripheral.

  As shown in FIG. 1, the user U and the device 10 are associated with the tenant 9. When the tenant 9 is to be described separately, it is assumed that the tenant is assigned the code of "9 + alphabet". The same applies to the device 10. In addition, the user U is represented by "U + number". The user U and the device 10 are managed in tenant units on the cloud. That is, data for associating the user U with the device 10 in the tenant 9 is managed on the cloud system 50.

  A tenant 9A (an example of first organization information) is generated for the user U1 who has applied for the use of the cloud service in the free trial. On the other hand, in an organization to which the user U1 belongs, there is a tenant 9B (an example of second organization information) to which the user U2 and the device 10B belong. In fact, the user U1 and the user U2 belong to the same organization. There are no major inconveniences in using the cloud service for the users U1 and U2 of the same organization respectively, but inconveniences such as management of equipment, accounting, and management of contracts are likely to occur on both the customer side and the cloud service side .

  When the user U1 applies for a fee-based contract to the organization, the accounting department or the like discovers that the contract has already been made, etc., and the organization side may request that the tenant 9 be integrated. Also, if the same organization is using the same cloud service on the cloud service side, integration may make tenant management easier, so there may be a demand for integration.

  In the information processing system of the present embodiment, since the tenant 9A is integrated with the tenant 9B, the configuration (user and device) of the actual organization and the configuration (user and device) of the tenant 9 can be made similar.

<Overview of Integration>
FIG. 2 is an example of a diagram for explaining an outline of integration of the tenants 9. It is assumed that there is a tenant 9B for which a prepaid contract has been made. The device 10B and the user U2 belong to the tenant 9B. The user U1 of the same organization as the user U2 applies for a cloud service using the device 10A using a free trial.

  A tenant ID is assigned to the tenant 9A, and a device ID is assigned to the device 10A. The tenant ID is also assigned to the tenant 9B, and the device ID is assigned to the device 10B. The tenant 9A is using the cloud service in a free trial, and the tenant 9B is using the cloud service for a fee.

  (1) The user U1 wants to integrate the tenant 9A and the tenant 9B, and starts the integration operation from the screen prepared by the device 10A. First, the cloud system 50 transmits the tenant ID specified based on the device ID of the device 10A to the device 10A.

  (2) Next, the user U1 logs in to the tenant 9B with the login information of the tenant 9B. The login information (password and the like) of the tenant 9B is acquired from the user U2 and the like.

  (3) The cloud system 50 transmits the tenant ID of the tenant 9B identified based on the login information to the device 10A.

  (4) As a result, since the device 10A can acquire the tenant ID of the tenant 9A and the tenant 9B, the tenant 9A and the tenant 9B can be integrated by transmitting each tenant ID to the cloud system 50.

  In this way, by identifying the integration source tenant 9A from the information on the registered device 10 and identifying the integration destination tenant 9B from the login information, the integration source tenant 9A and the integration destination tenant 9B can be identified. , It becomes possible to integrate two tenants 9.

<About terms>
The device is a device that is used for the cloud service and whose ID is registered in the cloud service. Furthermore, it is preferable to have a display device. In this embodiment, the term "device" is used.

  Integration means combining two or more things into one. In tenant consolidation, two tenants become one.

  The authentication information is information that proves that the user has the right to receive the service. This embodiment will be described in terms of login information. It may be called account information or sign-in information.

  Further, although the integration work is described as being performed by the administrator for convenience of explanation, it may be performed by a user who belongs to the tenant.

<Device registration method>
First, a method of registering the device 10 will be described with reference to FIG. FIG. 3 is an example of a diagram for explaining a registration method of the device 10. The user U needs to perform device registration at the start of the cloud service.
(1) First, at the time of applying for a free trial, the user U applies for the cloud system 50 using a PC (Personal Computer) or the like. The user ID is distributed, and a tenant 9 to which the user U belongs is generated. The user ID is associated with the tenant ID. Thus, login information (user ID, password, tenant ID) is issued to the user U. The same is true when applying for a paid cloud service.
(2) The user U inputs login information into the device 10, logs in to the cloud system 50, and performs device registration operation.
(3) Thereby, the device 10 transmits the login information and the device information (an example of the device information) to the cloud system 50. The cloud system 50 associates the device ID with the tenant ID associated with the user ID. Therefore, the device 10 can belong to the tenant 9 to which the user U belongs.

<Confirmation of device registration status>
After device registration, even if the user U does not log in using login information, the device 10 communicates with the cloud system 50, whereby the tenant ID to which the device 10 belongs can be specified. Thus, the user U can confirm the registration status of the device 10.

FIG. 4 is an example of a diagram for explaining the confirmation procedure of the device registration status.
(1) The user U performs an operation for confirming device registration information.
(2) The device 10 acquires tenant information for confirmation of device registration information. The cloud system 50 confirms the legitimacy of the device 10 (the request from the device 10) by device authentication.
(3) If the valid device 10 can be authenticated, the cloud system 50 returns tenant information (tenant ID etc.) associated with the device 10. For example, the device 10 displays a message such as “registered in tenant 9XXX!”.

  In this manner, if there is the device 10, the user U can confirm the tenant 9 in which the device 10 is registered without logging in.

<Integrated tenants>
The integration of the tenants 9 will be described with reference to FIG. FIG. 5 is an example of a diagram for schematically explaining the integration of the tenants 9. In FIG. 5, the case where the tenant 9A is integrated with the tenant 9B will be described as an example. The user U1 and the device 10A belonging to the tenant 9A are made to belong to the tenant 9B by integration. Integration means that the user U of the integration source tenant 9 and the device 10 belong to the integration destination tenant 9. Besides this, information on licenses and information on apps are integrated. The tenant 9A, including the user U1 and the device 10A, is deleted after integration into the tenant 9B. This can suppress waste of resources of the cloud system.

  It should be noted that licenses are not allocated to the migrated device 10 and the user only by integrating the tenant 9A with the tenant 9B. The assignment of a license means that a paid license ID is set (assigned) in device license assignment information and user license assignment information described later. The paid license ID is owned by the integration destination tenant 9B.

<System configuration example>
FIG. 6 is an example of a schematic configuration diagram of the information processing system 100. The information processing system 100 includes a cloud system 50 and one or more devices 10 that can communicate via the network N. Although it is assumed that there are a plurality of devices 10 in one organization 8, each communicates with the cloud system 50. Each device 10 is referred to as device 10A, device 10B, and any device 10 is referred to as device 10.

  The organization 8 is a united body in which people work in cooperation. For example, a company, a department within a company, a group, etc., but the names of business places, branches, etc. may vary depending on the organization 8. Communication is possible as long as it has a function to communicate, and it is not always necessary that the cloud system 50 and the device 10 communicate. Although two devices 10 are arranged in one tissue 8 in FIG. 6, devices 10 of different tissues 8 can be integrated.

  The device 10 is a device used by the user U of the information processing system 100. An example of the device 10 is, for example, a multifunction peripheral. The “multi-function” of the multi-function device means having multiple functions such as printing, fax transmission / reception, scanning of an original, and copying, but it is not necessary for the device to have multiple functions. The device 10 may have only one of these functions, for example, a printer, a printing device, a scanner device, a fax device, a copier, or the like. The multifunction peripheral may be an apparatus called an MFP (Multi-Function Peripheral), a copier, a copier, an image forming apparatus, or an office device.

  Furthermore, the device 10 may be a projector, a head up display (HUD) device, an electronic blackboard, a video conference terminal, digital signage, or the like. The device 10 according to the present embodiment may be any device registered in the tenant 9, having a user interface, and available to the user U.

  The cloud system 50 is an example of one or more information processing apparatuses. In addition, the cloud system 50 is preferably compatible with cloud computing. A cloud is a usage pattern of an information processing apparatus in which resources on a network are used without being aware of specific hardware resources. In this case, the cloud system 50 does not have to be housed in one case or provided as a group of devices, and hardware resources are dynamically connected and disconnected according to the load. Configured Further, it may be constructed in a virtualization environment in one information processing apparatus or may be constructed across a plurality of information processing apparatuses.

  Although the cloud system 50 exists on the Internet, it may exist anywhere as long as it is connected to a network, for example, may exist in an organization. Also, the cloud system 50 may be realized by one information processing apparatus.

  The network N is constructed by a LAN built at a site where the device 10 is installed, a provider network of a provider connecting the LAN to the Internet, and a line provided by a line provider. When the network N has multiple LANs, the network is called WAN or the Internet. The network N may be established by either wired or wireless, and wired and wireless may be combined. When the device 10 has a function of connecting to a mobile phone network such as 3G, LTE (Long Term Evolution), 4G, etc., the LAN may not be necessary and the network N is a mobile phone network and a provider network.

<Hardware configuration>
FIG. 7 is an example of a schematic hardware configuration diagram of the cloud system 50. The cloud system 50 includes a CPU 201 and a memory 202 that enables high-speed access to data used by the CPU 201. The CPU 201 and the memory 202 are connected to other devices 10 or drivers of the cloud system 50, for example, the graphics driver 204 and the network driver (NIC) 205 via the system bus 203.

  The graphics driver 204 is connected to an LCD (display device) 206 via a bus and monitors the processing result of the CPU 201. Also, the network driver 205 connects the cloud system 50 to the network N at the transport layer level and the physical layer level to establish a session with the device 10.

  An I / O bus bridge 207 is further connected to the system bus 203. On the downstream side of the I / O bus bridge 207, a storage device such as a hard disk drive (HDD) 209 by an IDE, ATA, ATAPI, serial ATA, SCSI, USB, etc. via an I / O bus 208 such as PCI. Is connected. The HDD 209 stores a program 209 p that controls the entire cloud system 50. The HDD 209 may be an SSD (Solid State Drive).

  In addition, an input device 210 such as a keyboard and a mouse (referred to as a pointing device) is connected to the I / O bus 208 via a bus such as USB, and receives inputs and commands from an operator such as a system administrator There is.

  The illustrated hardware configuration of the cloud system 50 does not have to be housed in a single case or provided as a group of devices, and it is a hardware element that the cloud system 50 preferably includes. Indicates Also, in order to support cloud computing, the physical configuration of the cloud system 50 of the present embodiment does not have to be fixed, and hardware resources are dynamically connected and disconnected according to the load. It may be configured.

<< About the hardware configuration of the device >>
FIG. 8 is an example of a block diagram showing a schematic hardware configuration of the device 10. The device 10 has a configuration in which a controller 410 and an engine unit (Engine) 415 are connected by a PCI (Peripheral Component Interface) bus 416.

  The controller 410 is a controller that controls the entire device 10 and controls drawing, communication, and input from the operation panel 411. The engine unit 415 is a printer engine or the like connectable to the PCI bus 416, and is, for example, a black and white plotter, a 1-drum color plotter, a 4-drum color plotter, a scanner or a fax unit.

  The engine unit 415 includes an image processing unit such as error diffusion and gamma conversion in addition to a so-called engine unit such as a plotter.

  The controller 410 includes a CPU 401, a north bridge (NB) 403, a system memory (MEM-P) 402, a south bridge (SB) 404, a local memory (MEM-C) 407, and an application specific integrated circuit (ASIC). An AGP (Accelerated Graphics Port) bus 405 is used to connect the north bridge (NB) 403 and the ASIC 406 with a hard disk drive (HDD) 408.

  The MEM-P 402 further includes a read only memory (ROM) 402 a and a random access memory (RAM) 402 b.

  The CPU 401 performs overall control of the device 10, includes a chipset including the NB 403, the MEM-P 402, and the SB 404, and is connected to other devices via the chipset.

  The NB 403 is a bridge for connecting the CPU 401 to the MEM-P 402, the SB 404, and the AGP bus 405, and includes a memory controller that controls reading and writing to the MEM-P 402, a PCI master, and an AGP target.

  The MEM-P 402 is a system memory used as a storage memory for programs and data, a development memory for programs and data, a drawing memory for a printer, and the like, and includes a ROM 402 a and a RAM 402 b.

  The ROM 402 a is a read only memory used as a storage memory for programs and data, and the RAM 402 b is a writable and readable memory used as a development memory for programs and data, a drawing memory for a printer, and the like.

  The SB 404 is a bridge for connecting the NB 403 to PCI devices and peripheral devices. The SB 404 is connected to the NB 403 via the PCI bus, and a network I / F 409 or the like is also connected to the PCI bus. The ASIC 406 is an IC (Integrated Circuit) for image processing applications having hardware elements for image processing, and has a role of a bridge connecting the AGP bus 405, the PCI bus 416, the HDD 408 and the MEM-C 407, respectively.

  The ASIC 406 includes a PCI target and an AGP master, an arbiter (ARB) that forms the core of the ASIC 406, a memory controller that controls the MEM-C 407, and a plurality of DMACs (Direct Memory) that rotate image data by hardware logic. And a PCI unit that transfers data between the engine unit 415 via the PCI bus.

  A network I / F 409 is a communication device for communicating with the cloud system 50 and the like via the network N, and is, for example, a NIC (Network Interface Card).

  The ASIC 406 is connected to an FCU (Facsimile Control Unit) 412, a USB (Universal Serial Bus) 413, and an IEEE 1394 (the Institute of Electrical and Electronics Engineers 1394) interface 414 via a PCI bus.

  The operation panel 411 is directly connected to the ASIC 406. The MEM-C 407 is a local memory used as a copy image buffer and a code buffer. An HDD 408 is a storage for storing image data, programs, font data, and forms.

  The HDD 408 also stores a program 408 p executed by the device 10. The AGP bus 405 is a bus interface for a graphics accelerator card proposed to accelerate graphic processing, and makes the graphics accelerator card faster by directly accessing the MEM-P 402 with high throughput. It is.

  The hardware configuration diagram of the device 10 illustrated is merely an example. For example, there are devices in which the operation panel is realized by an information processing apparatus such as a tablet terminal, and the hardware configuration may differ depending on the device 10.

<About function>
FIG. 9 is an example of a functional block diagram showing the functions of the cloud system 50 and the device 10 that the information processing system 100 has in block form.

<< Cloud system >>
The cloud system 50 includes a home screen providing unit 51, a web application 52, a device registration control unit 53, a device registration request receiving unit 54, a tenant integration control unit 55, a tenant integration request receiving unit 56, and a contract application receiving unit 57. . Furthermore, the cloud system 50 includes an information management unit 60 that manages various types of information, and the information management unit 60 includes a tenant management unit 61, a license management unit 62, a user management unit 63, an application setting management unit 64, and device management. A section 65 and an application management section 66 are included.

  These functions included in the cloud system 50 are functions or means implemented by the CPU 201 executing the program 209p developed from the HDD 209 shown in FIG. 7 to the memory 202. The program 209p may be distributed from a server for program distribution, or may be distributed in a portable storage medium such as a USB memory or an optical storage medium.

  The information management unit 60 has a database constructed by the HDD 209 or the memory 202 shown in FIG. The information management unit 60 includes a tenant management DB 71 managed by the tenant management unit 61, a user management DB 73 managed by the user management unit 63, a device management DB 75 managed by the device management unit 65, and a license management DB 72 managed by the license management unit 62. It has application setting management DB74 which application setting management part 64 manages, and application management DB76 which application management part 66 manages. First, each of these DBs (Data Bases) will be described.

表１はテナント管理ＤＢ７１が記憶するテナント情報の一例を示す。テナント情報はテナント９に関する情報である。テナント情報はテナントＩＤ、テナント名称、国、ロケール、及び、タイムゾーンの各属性を有する。各属性には必須、及び、備考の項目が対応付けられている。

Table 1 shows an example of tenant information stored in the tenant management DB 71. The tenant information is information on the tenant 9. Tenant information has each attribute of tenant ID, tenant name, country, locale, and time zone. Items of mandatory and remarks are associated with each attribute.

  A mandatory item indicates whether the corresponding attribute is information that must be provided to the tenant information. "O" mark shows that it is a required attribute. The remark is a comment on the attribute.

  Also, among the attributes, the tenant ID is identification information for uniquely identifying or specifying the tenant 9. ID is an abbreviation of Identification, and means an identifier or identification information. An ID refers to a name, a code, a character string, a numerical value, or a combination of one or more of them, which is used to uniquely distinguish a specific object from a plurality of objects. The same applies to other IDs.

  The tenant name is the name of the tenant 9 used by a human for management. The country is a country in which an organization (device and user) who has contracted the tenant 9 exists. The locale indicates a different unit of language, country / region, a set of notation rules such as symbols, dates, currencies, etc., or simply designation of a language or country / region to be used. A time zone is an area or division that uses the same standard time. The tenant information may also have other attributes, but the attributes that do not interfere with the description of the present embodiment are omitted. The same is true for other databases.

表２はユーザ管理ＤＢ７３が記憶するユーザ情報の一例を示す。ユーザ情報は、ユーザＵに関する情報でありユーザＵとテナント９を対応付ける情報である。ユーザ情報ＤＢはテナントＩＤ、ユーザＩＤ、パスワード、姓名、メールアドレス、ロケール、タイムゾーン、及び、ロールの各属性を有する。なお、表２の説明においては主に表１との差異について説明する。ユーザＩＤはユーザＵを一意に識別又は特定するための識別情報である。パスワードは利用者本人であることを証明するための秘密の数字、文字等の組み合わせである。姓名はユーザＵの氏名又はニックネームである。メールアドレスはユーザＵの電子メールのアドレスである。メールアドレスはログイン用のＩＤとして利用される場合がある。ロールは、情報処理システム１００におけるユーザＵの権限情報を示す。例えば、管理者又は一般などが登録される。ロールによってユーザＵが情報処理システム１００に対し可能な操作が予め決まっている。例えば、テナント９の統合は管理者しか実行できないことが定められている。

Table 2 shows an example of user information stored in the user management DB 73. The user information is information related to the user U and is information that associates the user U with the tenant 9. The user information DB has the following attributes: tenant ID, user ID, password, last name, mail address, locale, time zone, and role. In the description of Table 2, differences from Table 1 will be mainly described. The user ID is identification information for uniquely identifying or specifying the user U. The password is a combination of secret numbers, letters, etc. for proving that the user is the user. The surname is the name or nickname of the user U. The e-mail address is the address of the user U's e-mail. The email address may be used as a login ID. The role indicates the authority information of the user U in the information processing system 100. For example, a manager or a general is registered. Operations that the user U can perform on the information processing system 100 in advance are determined by the role. For example, it is defined that only the administrator can execute integration of the tenant 9.

表３はデバイス管理ＤＢ７５が記憶するデバイス情報の一例を示す。デバイス情報はデバイス１０に関する情報であり、デバイス１０とテナント９とを対応付ける情報である。デバイス管理ＤＢ７５はテナントＩＤ、デバイスＩＤ、デバイス種別、説明、及び、登録日の各属性を有する。デバイスＩＤはデバイス１０を一意に識別又は特定するための識別情報である。デバイスＩＤはデバイス１０に固有の識別情報であり例えば製造番号など不変の情報が採用される。デバイス種別は、デバイス１０がどのような機能を有する機器であるかを示す。例えば、ＭＦＰ、ＬＰ(Laser Printer)、プロジェクタ、ＨＵＤ装置、電子黒板、テレビ会議端末、デジタルサイネージ等が登録される。説明は、組織８がデバイス１０を管理するためにデバイス１０に関する不定型な情報が設定される項目である。登録日はクラウドサービスへの申込によりデバイス管理ＤＢ７５にデバイス１０が登録された日時である。

Table 3 shows an example of device information stored in the device management DB 75. The device information is information related to the device 10, and is information that associates the device 10 with the tenant 9. The device management DB 75 has attributes of tenant ID, device ID, device type, description, and registration date. The device ID is identification information for uniquely identifying or specifying the device 10. The device ID is identification information unique to the device 10, and unchanged information such as a serial number is adopted. The device type indicates what function the device 10 has. For example, MFP, LP (Laser Printer), projector, HUD device, electronic blackboard, teleconference terminal, digital signage, etc. are registered. The description is an item in which irregular information on the device 10 is set in order for the organization 8 to manage the device 10. The registration date is the date when the device 10 is registered in the device management DB 75 by the application to the cloud service.

表４（ａ）はライセンス管理ＤＢ７２が記憶するライセンス情報の一例を示す。ライセンス情報はテナント９が有する主にアプリのライセンスに関する情報を有する。ライセンス情報はテナントＩＤ、ライセンスＩＤ、アプリＩＤ、ライセンス種別、ボリューム、有償/無償、及び、期間の各属性を有する。まず、ライセンスとは、テナントに与えられたアプリの利用権を意味する。したがって、ライセンスがあることでテナント９に所属するユーザＵはアプリを利用できるようになる。ライセンスＩＤはライセンス情報を一意に識別又は特定するための識別情報である。アプリＩＤはアプリを一意に識別又は特定するための識別情報である。つまり、ライセンス対象のアプリを識別又は特定するＩＤである。アプリＩＤはアプリの種類を特定する機能と同じ種類のアプリからライセンスされたアプリを一意に特定する機能を有している。ライセンス種別は、デバイスライセンス、ユーザライセンス、及び、テナント内フリーなどのライセンスの種別を表す。デバイスライセンスは契約で決まっている数のデバイス１０にアプリの利用を認めるライセンスである（次述するデバイスライセンス割り当て情報で１つのライセンスＩＤに対応付けられるデバイス１０の数に制限がある）。ユーザライセンスは契約で決まっている数のユーザＵにアプリの利用を認めるライセンスである（次述するユーザライセンス割り当て情報で１つのライセンスＩＤに対応付けられるユーザＵの数に制限がある）。テナント内フリーはテナント９に所属する全てデバイス１０及びユーザＵがアプリを利用できるライセンスである。ボリュームは、数量で管理されるライセンス種別（デバイスライセンス、ユーザライセンス）の場合の数量である。有償/無償にはライセンスが有償か無償かが設定される。ここで、無償と設定されている場合、テナント９の契約がフリートライアルの可能性がある。ライセンス情報はアプリごとに作成されるので、アプリごとに有償/無償が異なってよい。期間は、ライセンスでアプリを利用することが認められた暦上の範囲である。フリートライアルの場合も有償契約の場合も期間が設定されることが多い。

Table 4 (a) shows an example of license information stored in the license management DB 72. The license information mainly includes information on the license of the application that the tenant 9 has. The license information has attributes of tenant ID, license ID, application ID, license type, volume, charge / free, and period. First, the license means the usage right of the application given to the tenant. Therefore, with the license, the user U belonging to the tenant 9 can use the application. The license ID is identification information for uniquely identifying or specifying the license information. The application ID is identification information for uniquely identifying or specifying an application. That is, it is an ID for identifying or specifying an application to be licensed. The application ID has a function of uniquely identifying the licensed application from the same type of application as the function of identifying the type of application. The license type indicates the type of license such as a device license, a user license, and a free in-tenant. The device license is a license that permits the use of the application to the number of devices 10 determined by the contract (the number of devices 10 associated with one license ID is limited in the device license allocation information described below). The user license is a license for permitting the number of users U determined by the contract to use the application (the number of users U associated with one license ID is limited in the user license allocation information described below). The intra-tenant free is a license in which all the devices 10 belonging to the tenant 9 and the user U can use the application. The volume is a quantity in the case of a license type (device license, user license) managed by quantity. For paid / free, the license is set to paid or free. Here, if it is set as free of charge, the contract of the tenant 9 may be a free trial. The license information is created for each application, so each application may differ in terms of charge / free. The term is the calendar range in which the license allows the use of the application. The period is often set for both free trial and paid contract.

  Table 4 (b) shows an example of device license assignment information stored in the license management DB 72. The device license assignment information associates the license assigned to the device 10 with the tenant 9 to which the device 10 belongs. The device license assignment information has each attribute of license ID, tenant ID, device ID, and assignment date. The assignment date indicates the date on which the license was assigned.

  Table 4 (c) shows an example of user license assignment information stored in the license management DB 72. The user license assignment information associates the license assigned to the user U with the tenant 9 to which the user U belongs. The user license assignment information has each attribute of license ID, tenant ID, user ID, and assignment date. The assignment date indicates the date on which the license was assigned.

表５はアプリ設定管理ＤＢ７４に記憶されているアプリ設定情報の一例を示す。アプリ設定情報は、アプリの設定に関する情報である。アプリ設定情報は、テナントＩＤ、アプリＩＤ、アプリ設定ＩＤ、アプリ用パラメータ１、及びアプリ用パラメータ２の各属性を有する。アプリ設定ＩＤはアプリの設定を一意に表す。アプリ用パラメータ１，２はアプリ固有のパラメータであり、内容はアプリによって様々である。また、アプリ用パラメータの数はアプリによって可変でよい。

Table 5 shows an example of application setting information stored in the application setting management DB 74. The application setting information is information on setting of the application. The application setting information has attributes of a tenant ID, an application ID, an application setting ID, an application parameter 1, and an application parameter 2. The app setting ID uniquely represents the setting of the app. The application parameters 1 and 2 are application specific parameters, and the contents vary depending on the application. Also, the number of application parameters may be variable depending on the application.

表６はアプリ管理ＤＢ７６に記憶されているアプリ情報の一例を示す。アプリ情報はアプリに関する情報である。アプリ情報はアプリＩＤ、及び開発者情報等を有する。

Table 6 shows an example of application information stored in the application management DB 76. The app information is information on the app. The application information includes an application ID, developer information, and the like.

  Referring back to FIG. First, the home screen providing unit 51 provides the device 10 with a home screen (described later) displayed by the device 10. The home screen is an initial screen displayed by the device 10, and a list of applications is displayed. The home screen is described by HTML, JavaScript (registered trademark), and CSS (Cascade Style Sheet) as an example.

  The web application 52 processes the request from the device 10 and transmits the processing result and the screen. The Web application 52 operates by cooperation of a program based on a script language (for example, JavaScript (registered trademark)) operating on the Web browser and a program on the Web server side, and uses software or its mechanism used on the Web browser. say. Since the web application 52 performs processing according to the application installed in the device 10, there may be a plurality of web applications 52. For example, there is a web application 52 that performs network storage service, OCR (Optical Character Reader), translation, PDF conversion, and the like.

  The device registration request accepting unit 54 transmits a web page necessary for registration of the device 10 to the device 10 according to the operation of the user U, and information required for registration of the device 10 transmitted from the device 10 (set in device information Information) is sent to the device registration control unit 53. The web page is described by, for example, HTML, JavaScript (registered trademark), and CSS (Cascade Style Sheet).

  The device registration control unit 53 requests the information management unit 60 to register the device 10. When the device 10 is registered, tenant information and user information are already registered as described above. At the time of registration of the device 10, license information for free trial is also created. Therefore, the device registration control unit 53 requests the device management unit 65 to register the device information, and requests the license management unit 62 to register the device license assignment information and the user license assignment information. The device registration control unit 53 also reads information from the information management unit 60 as needed.

  The tenant integration request reception unit 56 transmits a web page necessary for integration of the tenant 9 to the device 10 according to the operation of the user U, and performs information required for integration with the tenant 9 transmitted from the device 10 as tenant integration control Send to section 55. The web page is described by, for example, HTML, JavaScript (registered trademark), and CSS (Cascade Style Sheet).

  The tenant integration control unit 55 requests the information management unit 60 to process the integration of the tenant 9 in order to integrate the tenant 9 based on the information acquired from the tenant integration request reception unit 56 in order to integrate the tenant 9.

  The contract application receiving unit 57 receives an application for a contract from the PC 80. By providing a Web page for accepting a free trial application to the PC 80 and sending out the information obtained from the PC 80 to the information management unit 60, the tenant 9 is associated with the user U. The tenant management unit 61 creates tenant information, the user management unit 63 creates user information, and the license management unit 62 creates license information.

<< Device >>
The device 10 includes a communication unit 11, an operation reception unit 12, and a display control unit 13. These functions of the device 10 are realized by the CPU 401 executing a program 408p developed from the HDD 408 to the MEM-P 402 shown in FIG. The program 408p includes browser software or an application having the same function as the browser. The program 408p may be distributed from a server for program distribution, or may be distributed in a state of being stored in a portable storage medium such as a USB memory or an optical storage medium. The program 408p is browser software or software having an equivalent function.

  The communication unit 11 transmits various types of information to the cloud system 50, and receives various types of information from the cloud system 50. The operation accepting unit 12 accepts various operations on the device 10. The display control unit 13 analyzes the Web page received by the communication unit 11 and displays various screens on the operation panel. Further, the screen is transitioned according to the operation accepted by the operation accepting unit 12.

<Screen example>
FIG. 10 is a view showing an example of a screen displayed on the operation panel of the device 10. As shown in FIG. FIG. 10A shows an example of the home screen 301. The home screen 301 has an icon 302 of each application (corresponding to the web application 52). Although three application icons 302 are displayed in FIG. 10, the number of applications is not limited to three. The application is activated when the application icon 302 is selected.

  In addition, on the home screen 301, a button 303 saying "Tenant integration after this contract is here" is displayed. This button is linked to the Web page generated by the tenant integration request reception unit 56. Therefore, when the administrator presses this button, integration of the tenants 9 is started, and the tenant information screen 311 of FIG. 10B is displayed. Since the integration can not be performed without the button 303 "This is the tenant integration after this contract", the button 303 "This is the tenant integration after this contract" is the user interface that accepts the integration.

  FIG. 10 (b) shows an example of the tenant information screen 311. The tenant information screen 311 has a tenant information field 312, a message 313 "Please log in with login information of integration destination to integrate to another tenant", and a login screen button 314. The tenant information column displays device information associated with the device 10 operated by the administrator. This device information is device information of the integration source device 10. When the login screen button 314 is pressed, the login screen 321 is displayed.

  FIG. 10C shows an example of the login screen 321. The login screen 321 is a screen (an example of an authentication information input screen) for the administrator to log in to the integration destination tenant 9. The login screen 321 has a tenant ID field 322, a user ID field 323, a password field 324, and a login button 325. The administrator inputs the tenant ID of the integration destination in the tenant ID column 322, the user ID belonging to the integration destination tenant 9 in the user ID column 323, and the password of the user U in the password column 324. By pressing the login button 325, integration of the tenant 9 is executed.

  FIG. 10D shows an example of the tenant integration completion screen 331. The tenant integration completion screen 331 has a message 333 “Migration to the integration destination tenant is completed.”, An integration destination tenant information column 332, and a home screen button 334. As a result, the administrator can confirm that the integration has been completed, the tenant ID of the integration destination, and the like. When the home screen button 334 is pressed, the home screen 301 of FIG. 10A is displayed, but the home screen 301 of FIG. 10A is the home screen 301 of the tenant 9 before integration, so the integration source after integration is And the application possessed by the integration destination tenant 9 are displayed.

  The screen example shown in FIG. 10 is merely an example. Further, for convenience of explanation, a screen in the middle may be omitted in screen transition. For example, in the transition from FIG. 10 (c) to FIG. 10 (d), a screen may be displayed that asks the user to confirm whether integration may be performed.

<Operation procedure>
FIG. 11A and FIG. 11B are an example of a sequence diagram showing a procedure for integrating the two tenants 9 by the information processing system 100.

  S1: First, the administrator displays the home screen 301 on the operation panel. If the home screen 301 is already displayed, this operation is unnecessary. Thus, the home screen 301 of the integration source tenant 9 shown in FIG. 10A is displayed.

  S2: Next, the administrator presses a button 303 that says "Tenant integration after this contract is here". The operation accepting unit 12 accepts this operation.

  S3: As a result, the communication unit 11 accesses the (linked) URL linked to this button, and requests the tenant integration request reception unit 56 to acquire the tenant information.

  S3.1: The tenant integration request reception unit 56 requests the device management unit 65 to perform device authentication. When device authentication is established, a device authentication ticket is obtained. The device authentication ticket is information certifying that the device 10 is a device registered in the cloud system 50 and has access to information from the device management unit 65 or the like. Device authentication is performed using the device ID and information (such as a secret key) possessed by the device 10, and the administrator does not have to perform an operation for device authentication.

  S3.2: Next, the tenant integration request accepting unit 56 sends the acquisition of the device registration state to the device registration control unit 53 using the device authentication ticket.

  S3.2.1: The device registration control unit 53 requests the device management unit 65 to acquire device information using the device authentication ticket. Thus, the device registration control unit 53 can obtain device information.

  S3.2.2: The device registration control unit 53 requests the tenant management unit 61 to acquire tenant information using the tenant ID included in the device information. Thus, the device registration control unit 53 can obtain the tenant information of the integration source tenant 9.

  S3.3: The tenant integration request reception unit 56 generates a Web page of the tenant information screen 311 and transmits the Web page to the device 10. Thus, the tenant information screen 311 of FIG. 10B is displayed on the device 10.

  S4: When the administrator presses the login screen button 314, the operation accepting unit 12 accepts this operation.

  S4.1: Because the communication unit 11 of the device 10 accesses the URL linked (associated) with this button, the communication unit 11 requests the login page 321 from the tenant integration request reception unit 56. The tenant integration request reception unit 56 generates the login screen 321 and transmits the login screen 321 to the device 10.

  S5: The administrator inputs the tenant ID, the user ID, and the password of the integration destination tenant 9 on the login screen 321. The operation accepting unit 12 accepts this operation. In addition, since the login can not be performed if the administrator inputs the wrong even one of the tenant ID, the user ID, and the password (because the authentication is not established), it is possible to suppress the integration into the wrong integration destination.

  S5.1: Thereby, the communication unit 11 of the device 10 transmits, to the tenant integration request reception unit 56, an integration request for the tenant 9 including the tenant ID, the user ID, and the password.

  S5.2: First, the tenant integration request reception unit 56 transmits, to the user management unit 63, a login request including the tenant ID, the user ID, and the password. By the establishment of the authentication, the tenant integration request reception unit 56 can obtain the user authentication ticket. The user authentication ticket is information certifying that the user U is a user registered in the cloud system 50 and has an authority to access information from the user management unit 63 or the like.

  S5.3: Next, the tenant integration request reception unit 56 sends the tenant integration request including the user authentication ticket and the device authentication ticket to the tenant integration control unit 55.

  S5.3.1: First, the tenant integration control unit 55 sends, to the device management unit 65, an acquisition request for device information including a device authentication ticket. Thereby, the tenant integration control unit 55 acquires device information of the integration source tenant 9. The device information includes the tenant ID.

  S5.3.2: Next, the tenant integration control unit 55 sends, to the user management unit 63, an acquisition request for user information including the user authentication ticket. Thereby, the tenant integration control unit 55 acquires the user information of the user U who belongs to the integrated tenant 9. The user information includes the tenant ID.

  S5.3.3: Next, the tenant integration control unit 55 sends, to the tenant management unit 61, an acquisition request for tenant information including the tenant ID of the integration source. Thereby, the tenant integration control unit 55 acquires the tenant information of the integration source tenant 9.

  S5.3.4: Next, the tenant integration control unit 55 sends, to the tenant management unit 61, an acquisition request for tenant information including the tenant ID of the integration destination. Thereby, the tenant integration control unit 55 acquires the tenant information of the integration destination tenant 9.

  S5.3.5: Next, the tenant integration control unit 55 sends, to the user management unit 63, a migration request of user information including the integration source tenant ID and the integration destination tenant ID. Thus, the integration source user information is integrated into the integration destination user information. Specifically, new user information is created in which the tenant ID included in the user information of the integration source tenant 9 is changed to the integration destination tenant ID.

  S5.3.6: Next, the tenant integration control unit 55 sends, to the device management unit 65, a device information migration request including the integration source tenant ID and the integration destination tenant ID. Thereby, the integration source device information is integrated into the integration destination device information. Specifically, new device information is created in which the tenant ID included in the device information of the integration source tenant 9 is changed to the integration destination tenant ID.

  S5.3.7: Next, the tenant integration control unit 55 sends, to the license management unit 62, a license information transfer request including the integration source tenant ID and the integration destination tenant ID. Thus, the license information of the integration source is integrated into the license information of the integration destination. Specifically, new license information is created in which the tenant ID included in the license information of the integration source tenant 9 has been changed to the integration destination tenant ID. The license management unit also creates new device license assignment information in which the tenant ID included in the device license assignment information of the integration source tenant 9 has been changed to the integration destination tenant ID. Also, new user license assignment information is created in which the tenant ID included in the user license assignment information of the integration source tenant 9 is changed to the integration destination tenant ID.

  S5.3.8: Next, the tenant integration control unit 55 sends a migration request of application setting information including the integration source tenant ID and the integration destination tenant ID to the application setting management DB 74. Thus, the application setting information of the integration source is integrated into the application setting information of the integration destination. Specifically, new application setting information is created in which the tenant ID included in the application setting information of the integration source tenant 9 is changed to the integration destination tenant ID.

  S5.3.9: When steps S5.3.5 to S5.3.8 end, the tenant integration control unit 55 requests the tenant management unit 61 to delete the integration source tenant information. The tenant management unit 61 deletes the integration source tenant information. Further, the user information including the tenant ID of the integration source tenant information, the device information, the license information, the device license assignment information, the user license assignment information, or the application setting information is deleted. This can suppress wasteful use of the resources of the cloud system. The information related to the integration source tenant 9 may be deleted in steps S5.3.5 to S5.3.8, respectively.

  As described above, the tenant integration control unit 55 sends the integration destination tenant information to the tenant integration request reception unit 56 as a response to the process of step S5.3.

  S5.4: The tenant integration request reception unit 56 generates a Web page of the tenant integration completion screen 331 shown in FIG. 10D using the tenant information of the integration destination, and transmits the Web page to the device 10. The communication unit 11 of the device 10 receives the Web page of the tenant integration completion screen 331, and the display control unit 13 displays the tenant integration completion screen 331 on the operation panel.

  Note that the consolidation of paid tenants and the consolidation of free trial tenants can be consolidated in the same manner as in FIG.

<Display processing of home screen>
It supplements about the display process of the home screen 301. FIG. Since the home screen 301 is used by many users U, there is a possibility that the display of the button 303 “Tenant integration after this contract is here” may be bothersome. Therefore, it is preferable that only the device 10 in the free trial display the button 303 "tenant integration after this contract".

  FIG. 12 is an example of a flowchart showing a procedure of the home screen providing unit 51 creating a web page of the home screen 301.

  First, the home screen providing unit 51 acquires a request for the home screen 301 from the device 10 (S101). When activated, the device 10 transmits a request for the home screen 301 to the cloud system 50.

  Next, the home screen providing unit 51 performs device authentication (S102). The procedure of device authentication may be similar to that of FIG.

  When the authentication of the device 10 is established by the device authentication, the home screen providing unit 51 requests the device management unit 65 for the device information by the device authentication ticket, and acquires the device information (S103).

  Next, the home screen providing unit 51 designates the tenant ID included in the device information, requests the license management unit 62 for license information, and acquires the license information from the license management unit 62 (S104). The license information is the same as the number of applications licensed to the integration source tenant 9. For example, when three apps are displayed on the home screen 301, three pieces of license information are acquired.

  Then, the home screen providing unit 51 refers to all acquired license information and determines whether there is only a free application (S105).

  If there is only a free application (Yes in S105), it is determined that the cloud service is likely to be used in a free trial because there is no paid contract, and the home screen providing unit 51 A home screen 301 including a button 303 "Integrate is here" is created (S106).

  If there is only a free application (No in S105), it is determined that the cloud service is not used in a free trial because a paid contract has been made, and the home screen providing unit 51 “here is tenant integration after this contract” The home screen 301 not including the button 303 is created (S107).

  With such control, the cloud system 50 can display a button 303 "Tenant integration after this contract is here" only for the user U who is using the cloud service in free trial.

<Control to allow integration only to persons of a predetermined role>
Although there is a feature that integration of tenant 9 of this embodiment can be performed by the organization side, if any user U performs integration, devices 10 and users U belonging to the tenant 9 increase without the administrator knowing. And other situations may arise. For this reason, it is preferable to limit those who can integrate the tenants 9.

  FIG. 13 is an example of a flowchart showing a procedure for the tenant integration control unit 55 to limit persons who perform integration of the tenant 9. The process of FIG. 13 is performed between steps S3.3.2 and S3.3.3 of FIG.

  The tenant integration control unit 55 determines whether the role included in the user information is a manager (S201). The role is not limited to the administrator, as long as the integration of the tenant 9 is permitted.

  If the role is an administrator (Yes in S201), the operator of the device 10 has the right to integrate, so the tenant integration control unit 55 performs the processing in step S3.3.3 and later in FIG. 10 (S202).

  When the role is the administrator (No in S201), the tenant integration control unit 55 notifies the device 10 that there is no right of tenant integration (S203). That is, a Web page in which the tenant integration request reception unit 56 displays that the user is not authorized is created and displayed on the device 10. Moreover, the process after step S3.3.3 is not performed.

  By the process as described above, it is possible to limit those who can integrate the tenants 9 to only those who have the authority, such as the administrator.

<Allocate license>
Although the user U and the device 10 of the integration source tenant 9 can be migrated to the migration destination tenant 9 by the process of FIG. 11, no license has been assigned yet. The license ID of the integration source user license assignment information remains the license ID of the integration source license information. The license ID of the integration source device license assignment information remains the license ID of the integration source license information. Since the license information of the integration source has already been deleted, the device and the user can not use the app because there is no license.

  Conventionally, the person in charge on the cloud system side has assigned a license, but in the present embodiment, the cloud system 50 can assign a license as follows.

  FIG. 14 is an example of a flowchart showing a procedure for the license management unit 62 to assign a license to the integration source user U or the device 10. The process of FIG. 14 is performed in step S5.3.7 of FIG. 11B.

  First, the license management unit 62 determines whether the license of the integration destination tenant 9 has a limited amount (S301). This determination is made based on the license type of the license information.

  If there is a quantity limit (Yes in S301), the license management unit 62 allocates licenses to the user U and the device 10 within the allowable range of the volume of license information (S302). The user license will be described as an example. For example, when the volume is 10 and licenses are allocated to eight users U in the integration destination tenant 9, the license is allocated to the user U up to two people belonging to the integration source tenant 9. Specifically, the license ID of the user license assignment information integrated into the integration destination is changed to the license ID of the integration destination license information. This process is applied to user license allocation information for two persons. The user license assignment information belonging to the integration source tenant 9 is identified by, for example, a flag indicating the integration source or the license ID of the integration source.

  When three or more users U belong to the integration source tenant 9, unassigned users U remain. Since the license ID of the user license assignment information of this user remains the license ID of the license information of the integration source, the application can not be used when the free trial period is over.

  Although the above describes the user license allocation information, the same applies to the device license allocation information.

  If there is no quantity limit (No in S301), the license management unit 62 assigns a license to the user U and the device 10 (S303). That is, for all the integration source user U, the license ID of the integration source user license assignment information is changed to the license ID of the integration destination license information.

  In this way, licenses are allocated in the range of volumes to the user U and the device 10 migrated to the integration destination tenant 9, and licenses are allocated to the user U and the tenant 9 integrated into the free tenant in the tenant. Therefore, it is possible to reduce the need for the person in charge of the cloud system to allocate a license.

  In the case of consolidation of paid tenants, allocation of licenses becomes unnecessary. In the consolidation of free trial tenants, it is possible to assign a license, but there is no point.

<Summary>
As described above, in the cloud system 50 according to the present embodiment, the customer himself performs tenant integration work by an intuitive and simple operation of “login using the login information of the integration destination from the screen of the integration source device 10 used”. It can be carried out. Conventionally, a customer engineer or the like visits a customer and performs integration work. However, according to the integration method of the present embodiment, since the customer can integrate, cost and time required for integration can be reduced.

<Other application examples>
As described above, the best mode for carrying out the present invention has been described using the examples, but the present invention is not limited to these examples at all, and various modifications can be made without departing from the scope of the present invention. And substitution can be added.

  In the present embodiment, the integration of the tenants 9 of the same organization is described for convenience of explanation, but the integration source and integration destination tenants 9 may not be contracted by the same organization.

  In addition, when three or more tenants are in the same organization, two other tenants may be integrated with any integration destination tenant. Also, tenant A may be integrated with tenant B, and then tenant B may be integrated with tenant C.

  Further, the configuration example of FIG. 9 or the like is divided according to main functions in order to facilitate understanding of the processing by the device 10 and the cloud system 50. The present invention is not limited by the method and name of division of processing units. The processing of the device 10 and the cloud system 50 can be further divided into more processing units according to the processing content. Also, one processing unit can be divided to include more processes.

  The tenant integration request reception unit 56 is an example of integration request reception means, the tenant integration control unit 55 is an example of integration control means, the display control unit 13 is an example of display means, and the operation reception unit 12 is reception It is an example of the means.

8 Organization 9 Tenant 10 Device 50 Cloud System 100 Information Processing System

JP, 2015-204087, A

Claims (10)

An information processing apparatus for providing services to devices belonging to organization information,
Integration request receiving means for receiving a request for integration of the organization information from the device belonging to the first organization information;
The identification information of the first organization information associated with the identification information of the device is acquired with reference to the device information that associates the identification information of the organization information with the identification information of the device.
Integrated control means for acquiring identification information of second organization information of integration destination to which the first organization information is integrated based on the authentication information of the second organization information transmitted from the device And
The integrated control means integrates the first organization information specified by the identification information of the first organization information and the second organization information specified by the identification information of the second organization information.
An information processing apparatus characterized by The integration request reception means causes the device to display an authentication information input screen for inputting authentication information of the second organization information,
The integrated control means is characterized by acquiring identification information of the second organization information to which a user who has been authenticated belongs by the authentication information of the second organization information input on the authentication information input screen. An information processing apparatus according to claim 1. The information processing apparatus performs a free trial to provide the service free of charge.
The first organization information is using a free trial, and the second organization information is using the service for a fee,
The information processing apparatus according to claim 2, wherein the integrated control means integrates the first organization information using a free trial and the second organization information using the service for a fee. . The integrated control means refers to license information given to the device specified based on identification information of the device belonging to the first organization information,
The integration request receiving means causes the device to display a user interface for receiving a request for integration of the organization information only when the license information does not indicate that the device is paid and the service is received. The information processing apparatus according to claim 3. The service is provided by an application executed by the device, and the license information is set to be paid or not for each application.
In the license information given to the device specified based on the identification information of the device, only when there is no description of the purport of charging for all the applications,
5. The information processing apparatus according to claim 4, wherein the integration request reception unit causes the device to display a user interface that receives a request for integration of the organization information. When the authentication of the user is established, the integrated control means refers to user information in which the authority information of the user is registered in the identification information of the user, and the authority of integration of the organization information is recognized in the authority information To determine if it is
The method according to any one of claims 2 to 5, wherein the first organization information and the second organization information are integrated only when the authority to integrate the organization information is recognized. Information processing device. One or more devices and one or more users who use the devices belong to one piece of the organization information,
The integrated control means causes one or more of the devices and one or more users belonging to the first organization information to shift to the second organization information, thereby the first organization information and the second organization information. The information processing apparatus according to any one of claims 1 to 6, wherein organization information is integrated. The integrated control means refers to license information given to the device specified based on identification information of the device belonging to the first organization information,
When the number of devices or users who can use the service is set in the license information:
8. The information according to claim 7, wherein a license included in the second organization information of the integration destination is allocated to the device and the user belonging to the first organization information within a range permitted by the number. Processing unit. An information processing system, comprising: an apparatus belonging to organization information; and an information processing apparatus for providing a service to the organization information,
The device is
Display means for displaying on a display device a user interface for receiving a request for integration of the organization information;
Receiving means for receiving a request for integration of the organization information to the user interface;
The information processing apparatus is
Integration request receiving means for receiving a request for integration of the organization information from the device belonging to the first organization information;
The identification information of the first organization information associated with the identification information of the device is acquired with reference to the device information that associates the identification information of the organization information with the identification information of the device.
Integrated control means for acquiring identification information of second organization information of integration destination to which the first organization information is integrated based on the authentication information of the second organization information transmitted from the device And
The integrated control means integrates the first organization information specified by the identification information of the first organization information and the second organization information specified by the identification information of the second organization information.
An information processing system characterized by An organization information integration method performed by an information processing apparatus for providing a service to a device belonging to organization information, comprising:
A step of the integration request reception means receiving a request for integration of the organization information from the device belonging to the first organization information;
The integrated control means acquires identification information of the first organization information associated with the identification information of the device by referring to the device information associating the identification information of the organization information with the identification information of the device; ,
Acquiring identification information of second organization information of integration destination to which the first organization information is integrated, based on the authentication information of the second organization information transmitted from the device;
The integrated control means integrates the first organization information specified by the identification information of the first organization information and the second organization information specified by the identification information of the second organization information And an integrated method characterized by having.

Images