JP6919561B2 - Information processing equipment, information processing system, integration method - Google Patents

Description

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

One of the cloud service forms is a service form called SAAS (Software as a Service). In SAAS, the software does not run on the user side, but runs on the cloud side, and the user uses the software functions via the network. Then, in SAAS, a multi-tenant in which the same system is shared by a plurality of tenants is generally adopted. A tenant is a cloud service customer. Not only in the case of becoming a tenant on a company-by-company basis, but also in the case of becoming a tenant in organizations of various particle sizes such as departments and groups. For this reason, tenants are sometimes referred to as organizational information.

By the way, in a multi-tenant cloud service, a tenant may be able to use the cloud service in a free trial. A free trial is an opportunity to serve users free of charge for a period of time, primarily for promotional and trial experiences. Customers who like the cloud service in the free trial can continue to use the cloud service by completing the billing procedure.

Since the purpose of the free trial is to have users who have never used the cloud service use it widely, the cloud service does not require the user to show an ID card. For this reason, the reliability of application information (company name, department name, name, etc.) is generally low, so whether or not the same organization (for example, the same company or the same department) has the same cloud service contract when applying for a free trial. No judgment has been made. Even if it is judged, it is not preferable to integrate the tenants who have already made a paid contract with the tenants of the free trial because the reliability of the application information is unreliable.

However, if the employee who applied for the free trial wants to continue using the cloud service, 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, the customer needs to manage equipment, pay, and manage contracts for each tenant. Also, from the cloud service side, it is necessary to manage equipment, bill and collect usage fees, and manage contracts for each tenant.

Therefore, the customer or the cloud service side may want to integrate a plurality of tenants. In response to such a request for tenant integration, a technique has been devised to integrate another tenant created within the same company into another tenant with which a paid contract has been concluded (see, for example, Patent Document 1). ). Patent Document 1 discloses a technique of editing a tenant management table of a management server to integrate tenants and delete 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 tenant of the integration source and the integration destination by using the device used in the service such as the cloud service. In other words, in the conventional tenant integration, it is necessary for the customer engineer, sales staff, etc. to inquire the user and grasp the information of the tenant of the integration source and the integration destination in order to integrate the tenant, and both the cloud service side and the customer side. The burden was heavy.

In addition, there is a problem that the customer engineer or the like needs to bring back the information of the tenant of the integration source and the integration destination to perform the work related to the integration, and there is no immediacy.

The issue regarding the integration of tenants is not only the integration of the integration source used in the free trial and the integration destination under the paid contract, but also the integration destination used in the free trial as well as the integration source used in the free trial. It can also occur in the integration with, or in the integration of the integration source under the paid contract and the integration destination under the paid contract.

In view of the above problems, an object of the present invention is to provide an integration method that can easily identify the organizational information of the integration source and the integration destination by using the device used in the service.

The present invention is an information processing device that provides a service to a device belonging to organizational information, and is an integrated request receiving means for receiving a request for integration of the organizational information from a device belonging to the first organizational information, and the organization. By referring to the device information that associates the identification information of the information with the identification information of the device, the identification information of the first organization information associated with the identification information of the device is acquired, and the first organization information is integrated. The integrated control means includes an integrated control means for acquiring the identification information of the second organization information of the integration destination based on the authentication information of the second organization information transmitted from the device. It is characterized in that 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 device that can easily identify the organizational information of the integration source and the integration destination by using the equipment used in the service.

It is an example of the figure explaining the relationship between a tenant, a user, and a device. This is an example of a diagram illustrating the outline of tenant integration. It is an example of the figure explaining the device registration method. This is an example of a diagram illustrating a procedure for checking the device registration status. This is an example of a diagram schematically explaining the integration of tenants. This is an example of a schematic configuration diagram of an information processing system. This is an example of a schematic hardware configuration diagram of a cloud system. This is an example of a block diagram showing a schematic hardware configuration of a device. This is an example of a functional block diagram showing the functions of the cloud system and the device of the information processing system in a block shape. It is a figure which shows the screen example displayed on the operation panel of a device. This is an example of a sequence diagram showing the procedure for integrating an information processing system with a tenant. This is an example of a sequence diagram showing the procedure for integrating an information processing system with a tenant. This is an example of a flowchart showing a procedure for the home screen providing unit to create a Web page of the home screen. This is an example of a flowchart showing a procedure in which the tenant integration control unit limits the persons who integrate tenants. This is an example of a flowchart showing a procedure in which the license management unit assigns a license to an integration source user or device.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

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

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

As shown in FIG. 1, the user U and the device 10 are associated with the tenant 9. When the tenant 9 is explained separately, the tenant is given a code of "9 + alphabet". The same applies to the device 10. Further, the user U is represented by "U + number". User U and device 10 are managed on a tenant-by-tenant basis on the cloud. That is, the data that associates the user U and the device 10 with the tenant 9 is managed on the cloud system 50.

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

When the user U1 applies for a paid contract to the organization, the accounting department or the like discovers that the contract has already been made, and the organization may request that the tenant 9 be integrated. Also, on the cloud service side, when the same organization uses multiple same cloud services, tenant management becomes easier due to the integration, so there may be a request for integration.

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

<Outline of integration>
FIG. 2 is an example of a diagram for explaining the outline of the integration of the tenant 9. It is assumed that there is a tenant 9B who has a paid contract in advance. Device 10B and user U2 belong to tenant 9B. User U1 of the same organization as user U2 applied for a cloud service using 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. A tenant ID is also assigned to the tenant 9B, and a device ID is assigned to the device 10B. Tenant 9A is using the cloud service in a free trial, and tenant 9B is using the cloud service for a fee.

(1) User U1 wants to integrate tenant 9A and tenant 9B, and starts the integration operation from the screen prepared by device 10A. First, the cloud system 50 transmits a 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, etc.) of tenant 9B is acquired from user U2, etc.

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

(4) As a result, the device 10A can acquire the tenant IDs of the tenant 9A and the tenant 9B, so that the tenant 9A and the tenant 9B can be integrated by transmitting the respective tenant IDs to the cloud system 50.

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

<Terminology>
A device is a device that is used for a cloud service and whose ID is registered in the cloud service. Further, it is preferable to have a display device. In this embodiment, the term “device” will be used.

Integration means combining two or more things into one. Tenant integration brings two tenants into one.

The authentication information is information certifying that the user has the authority to receive the service. In this embodiment, the term login information will be used. It may be called account information or sign-in information.

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

<How to register the device>
First, a method of registering the device 10 will be described with reference to FIG. FIG. 3 is an example of a diagram illustrating a method of registering the device 10. User U needs to register the device when the cloud service starts.
(1) First, when applying for a free trial, user U applies to the cloud system 50 using a PC (Personal Computer) or the like. The user ID is distributed, and the tenant 9 to which the user U belongs is generated. The user ID is associated with the tenant ID. As a result, login information (user ID, password, tenant ID) is issued to user U. The same applies when applying for a paid cloud service.
(2) The user U inputs the login information into the device 10 and logs in to the cloud system 50 to perform the device registration operation.
(3) As a result, the device 10 transmits login information and device information (an example of 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 registering the device, the user U can identify the tenant ID to which the device 10 belongs by communicating with the cloud system 50 without logging in with the login information. As a result, the user U can confirm the registration status of the device 10.

FIG. 4 is an example of a diagram illustrating a procedure for checking the device registration status.
(1) The user U performs an operation for confirming the device registration information.
(2) The device 10 acquires tenant information for confirming the device registration information. The cloud system 50 confirms the validity of the device 10 (the request comes from the device 10) by device authentication.
(3) If it can be authenticated that the device 10 is legitimate, the cloud system 50 returns the 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 way, if the device 10 is present, the user U can confirm the tenant 9 in which the device 10 is registered without logging in.

<Integration of tenants>
The integration of tenant 9 will be described with reference to FIG. FIG. 5 is an example of a diagram schematically illustrating the integration of tenants 9. In FIG. 5, a case where the tenant 9A is integrated into the tenant 9B will be described as an example. User U1 and device 10A belonging to tenant 9A are made to belong to tenant 9B by integration. The integration means that the user U and the device 10 of the tenant 9 of the integration source belong to the tenant 9 of the integration destination. In addition to this, information on licenses and information on apps will be integrated. Tenant 9A, including user U1 and device 10A, will be deleted after integration into tenant 9B. As a result, it is possible to prevent the resources of the cloud system from being wasted.

It should be noted that the licenses are not assigned to the migrated device 10 and the user just by integrating the tenant 9A into the tenant 9B. License allocation means that a paid license ID is set (assigned) in the device license allocation information and the user license allocation information, which will be described later. The paid license ID is owned by the integrated 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 capable of communicating via the network N and one or more devices 10. It is assumed that there are a plurality of devices 10 in one organization 8, but each of them communicates with the cloud system 50. Each device 10 is referred to as a device 10A and a device 10B, and any device 10 is referred to as a device 10.

Organization 8 refers to a unified body in which people work together. For example, a company, a department within a company, a group, etc., but the names such as a place of business and a branch office may vary depending on the organization 8. Communicatable means that it only needs to have a communication function, and it is not necessary for the cloud system 50 and the device 10 to always communicate with each other. Although two devices 10 are arranged in one organization 8 in FIG. 6, devices 10 of different organizations 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 a multifunction device. "Composite" of a multifunction device means that it has a plurality of functions such as printing, fax transmission / reception, document scanning, and copying, but it is not necessary for the device to have a plurality of 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. Further, the multifunction device may be a device called an MFP (Multi-Function Peripheral), a copying machine, a copying machine, an image forming device, an office device, or the like.

Further, the device 10 may be a projector, a HUD (Head Up Display) device, an electronic blackboard, a video conferencing terminal, digital signage, or the like. The device 10 of the present embodiment may be any device that is registered in the tenant 9, has a user interface, and can be used by the user U.

The cloud system 50 is an example of one or more information processing devices. Further, it is preferable that the cloud system 50 supports cloud computing. The cloud is a form of use of an information processing device in which resources on a network are used without being aware of specific hardware resources. In this case, the cloud system 50 does not need to be housed in one housing or provided as a group of devices, and hardware resources are dynamically connected / disconnected according to the load. It is composed. Further, it may be built in a virtual environment in one information processing device, or may be built across a plurality of information processing devices.

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

The network N is constructed by a LAN constructed at a base where the device 10 is installed, a provider network of a provider that connects the LAN to the Internet, a line provided by a line operator, and the like. When the network N has a plurality of LANs, the network is called a WAN or the Internet. The network N may be constructed either wired or wireless, and may be a combination of wired and wireless. Further, when the device 10 has a function of connecting to a mobile phone network such as 3G, LTE (Long Term Evolution), or 4G, the network N does not have to be a LAN, 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, such as the graphics driver 204 and the network driver (NIC) 205, via the system bus 203.

The graphics driver 204 is connected to the LCD (display device) 206 via a bus to monitor the processing result by the CPU 201. In addition, 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 an HDD (hard disk drive) 209 is used by IDE, ATA, ATAPI, serial ATA, SCSI, USB, etc. via an I / O bus 208 such as PCI. Is connected. HDD 209 stores a program 209p that controls the entire cloud system 50. HDD 209 may be SSD (Solid State Drive).

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

The hardware configuration of the cloud system 50 shown in the figure does not have to be housed in one housing or provided as a group of devices, and it is preferable that the cloud system 50 has a hardware element. Is shown. Further, in order to support cloud computing, the physical configuration of the cloud system 50 of this embodiment does not have to be fixed, and hardware resources are dynamically connected / 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 the controller 410 and the 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 that can be connected 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, a fax unit, or the like.

In addition to the so-called engine portion such as a plotter, the engine portion 415 includes an image processing portion such as error diffusion and gamma conversion.

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 ASIC (Accelerated Graphic Integrated Circuit). It has a 406 and a hard disk drive (HDD) 408, and the north bridge (NB) 403 and the ASIC 406 are connected by an AGP (Accelerated Graphics Port) bus 405.

Further, the MEM-P402 further includes a ROM (Read Only Memory) 402a and a RAM (Random Access Memory) 402b.

The CPU 401 controls the entire device 10, has a chipset including NB403, MEM-P402, and SB404, and is connected to other devices via this chipset.

The NB 403 is a bridge for connecting the CPU 401 and the MEM-P402, SB404, and AGP bus 405, and has a memory controller that controls reading and writing to the MEM-P402, a PCI master, and an AGP target.

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

The ROM 402a is a read-only memory used as a memory for storing programs and data, and the RAM 402b is a writeable and readable memory used as a memory for expanding programs and data, a memory for drawing a printer, and the like.

The SB404 is a bridge for connecting the NB403 to a PCI device and peripheral devices. The SB404 is connected to the NB403 via a PCI bus, and a network I / F409 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-C407, respectively.

This 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-C407, and a plurality of DMACs (Direct Memory) that rotate image data by hardware logic or the like. It has an Access Controller) and a PCI unit that transfers data between the engine unit 415 and the engine unit 415 via the PCI bus.

The network I / F409 is a communication device for communicating with the cloud system 50 or 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) interface 14 Engineering via the PCI bus.

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

The HDD 408 also stores a program 408p executed by the device 10. The AGP bus 405 is a bus interface for a graphics accelerator card proposed to speed up graphics processing, and accelerates the graphics accelerator card by directly accessing the MEM-P402 with high throughput. Is.

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

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

<< Cloud system >>
The cloud system 50 has 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 integrated control unit 55, a tenant integrated request receiving unit 56, and a contract application receiving unit 57. .. Further, the cloud system 50 has 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. It has a unit 65 and an application management unit 66.

Each of these functions possessed by the cloud system 50 is a function or means realized by the CPU 201 executing the program 209p expanded from the HDD 209 to the memory 202 shown in FIG. 7. The program 209p 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 information management unit 60 has a database constructed by the HDD 209 or the memory 202 shown in FIG. 7. 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 an application setting management DB 74 managed by the application setting management unit 64 and an application management DB 76 managed by the application management unit 66. 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. Tenant information is information about tenant 9. Tenant information has tenant ID, tenant name, country, locale, and time zone attributes. Required and remarks items are associated with each attribute.

The required item indicates whether or not the corresponding attribute is essential information for tenant information. The "○" mark indicates that it is an essential attribute. The remarks are comments on attributes.

Further, among the attributes, the tenant ID is identification information for uniquely identifying or identifying the tenant 9. ID is an abbreviation for 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 these, 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 humans for management. The country is the country where the organization (device and user) that has contracted the tenant 9 exists. Locale indicates a set of notation rules such as units, symbols, dates, and currencies that differ for each language and country / region, or simply specifies the language or country / region to be used. A time zone is a region or division that uses the same standard time. The tenant information may have other attributes, but the attributes that do not interfere with the description of the present embodiment are omitted. The same applies to other databases.

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

Table 2 shows an example of user information stored in the user management DB 73. The user information is information about the user U and is information for associating the user U with the tenant 9. The user information DB has attributes such as tenant ID, user ID, password, first and last name, email address, locale, time zone, and role. In the description of Table 2, the differences from Table 1 will be mainly described. The user ID is identification information for uniquely identifying or identifying the user U. A password is a combination of secret numbers, characters, etc. to prove that the user is the person himself / herself. The first and last name is the user U's first and last name or nickname. The e-mail address is the e-mail address of the user U. 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, an administrator or the general public is registered. Depending on the role, the operations that the user U can perform on the information processing system 100 are predetermined. For example, it is stipulated that the integration of tenant 9 can only be performed by the administrator.

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

Table 3 shows an example of device information stored in the device management DB 75. The device information is information about the device 10, and is information for associating the device 10 with the tenant 9. The device management DB 75 has attributes of a tenant ID, a device ID, a device type, a description, and a registration date. The device ID is identification information for uniquely identifying or identifying the device 10. The device ID is identification information unique to the device 10, and invariant information such as a serial number is adopted. The device type indicates what kind of function the device 10 has. For example, MFPs, LPs (Laser Printers), projectors, HUD devices, electronic whiteboards, video conferencing terminals, digital signage and the like are registered. The description is an item in which atypical information about the device 10 is set in order for the organization 8 to manage the device 10. The registration date is the date and time when the device 10 is registered in the device management DB 75 by applying for the cloud service.

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

Table 4 (a) shows an example of the license information stored in the license management DB 72. The license information mainly has information about the license of the application that the tenant 9 has. The license information has attributes such as tenant ID, license ID, application ID, license type, volume, paid / free, and period. First, the license means the right to use the application given to the tenant. Therefore, the license allows the user U belonging to the tenant 9 to 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 identifying the application. That is, it is an ID that identifies or identifies the licensed application. The application ID has a function of uniquely specifying a licensed application from the same type of application as a function of specifying the type of the application. The license type represents the type of license such as device license, user license, and free in tenant. The device license is a license that allows the number of devices 10 determined in the contract to use the application (the number of devices 10 associated with one license ID in the device license allocation information described below is limited). The user license is a license that allows the number of user Us determined in the contract to use the application (the number of user Us associated with one license ID in the user license allocation information described below is limited). In-tenant free is a license that allows all devices 10 and user U belonging to tenant 9 to 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, whether the license is paid or free is set. Here, if it is set to be free of charge, there is a possibility that the contract of tenant 9 is a free trial. Since the license information is created for each application, the paid / free fee may be different for each application. The period is the calendar range in which the license allows you to use the app. The period is often set for both free trials and paid contracts.

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

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

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

Table 5 shows an example of the application setting information stored in the application setting management DB 74. The application setting information is information related to the setting of the application. The application setting information has each attribute of a tenant ID, an application ID, an application setting ID, an application parameter 1, and an application parameter 2. The application setting ID uniquely represents the application setting. The parameters 1 and 2 for the application are parameters unique to the application, and the contents vary depending on the application. In addition, the number of parameters for the application may be variable depending on the application.

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

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

It will be described 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 coordinating a program in a script language (for example, JavaScript (registered trademark)) that operates on a Web browser and a program on the Web server side, and software or a mechanism thereof used on the Web browser. To tell. Since the Web application 52 performs processing according to the application installed on the device 10, there may be a plurality of the Web application 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 receiving unit 54 transmits a Web page required for registration of the device 10 to the device 10 in response to the operation of the user U, and the information (set in the device information) required for the registration of the device 10 transmitted from the device 10. Information to be sent) to the device registration control unit 53. Web pages are 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. At the time of registration of the device 10, the tenant information and the user information are already registered as described above. Also, when registering the device 10, license information for a 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 allocation information and the user license allocation information. Further, the device registration control unit 53 reads information from the information management unit 60 as needed.

The tenant integration request receiving unit 56 transmits the Web page required for the integration of the tenant 9 to the device 10 in response to the operation of the user U, and the tenant integration control controls the information required for the integration with the tenant 9 transmitted from the device 10. It is sent to the unit 55. Web pages are 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 perform processing related to the integration of the tenant 9 in order to integrate the tenant 9 based on the information acquired from the tenant integration request receiving unit 56 in order to integrate the tenant 9.

The contract application reception unit 57 accepts a contract application from the PC 80. The tenant 9 and the user U are associated with each other by providing the PC 80 with a Web page for accepting a free trial application and sending the information obtained from the PC 80 to the information management unit 60. 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 has a communication unit 11, an operation reception unit 12, and a display control unit 13. Each of these functions possessed by the device 10 is realized by the CPU 401 executing the program 408p developed from the HDD 408 shown in FIG. 8 to the MEM-P402. The program 408p has browser software or an application having a function equivalent to that of a 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. Program 408p is browser software or software having equivalent functions.

The communication unit 11 transmits various information to the cloud system 50 and receives various information from the cloud system 50. The operation reception unit 12 receives 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. In addition, the screen is changed according to the operation received by the operation reception unit 12.

<Screen example>
FIG. 10 is a diagram showing an example of a screen displayed on the operation panel of the device 10. FIG. 10A shows an example of the home screen 301. The home screen 301 has an icon 302 for each application (corresponding to the Web application 52). In FIG. 10, three application icons 302 are displayed, but the number of applications is not limited to three. The application is started by selecting the application icon 302.

Further, on the home screen 301, a button 303 "Click here for tenant integration after this contract" 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, the integration of the tenant 9 is started, and the tenant information screen 311 of FIG. 10B is displayed. Since the integration cannot be performed without the button 303 "Click here for tenant integration after this contract", the button 303 "Click here for tenant integration after this contract" becomes the user interface that accepts the integration.

FIG. 10B 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 the login information of the integration destination in order to integrate with another tenant", and a login screen button 314. In the tenant information column, device information associated with the device 10 operated by the administrator is displayed. This device information is the device information of the integration source device 10. The login screen 321 is displayed by pressing the button to the login screen button 314.

FIG. 10C shows an example of the login screen 321. The login screen 321 is a screen for the administrator to log in to the tenant 9 of the integration destination (an example of the authentication information input screen). 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 field 322, the user ID belonging to the tenant 9 of the integration destination in the user ID field 323, and the password of the user U in the password field 324. When the login button 325 is pressed, the tenant 9 is integrated.

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

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

<Operation procedure>
11A and 11B are examples of sequence diagrams showing a procedure in which the information processing system 100 integrates two tenants 9.

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

S2: Next, the administrator presses the button 303 "Click here for tenant integration after this contract". The operation reception unit 12 accepts this operation.

S3: As a result, the communication unit 11 accesses the (associated) URL linked to this button, and therefore 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 for device authentication. When the device authentication is established, the 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 an authority to access information such as the device management unit 65. Device authentication is performed using the device ID and the information (private key, etc.) possessed by the device 10, and the administrator does not need to perform an operation for device authentication.

S3.2: Next, the tenant integration request receiving unit 56 sends the acquisition of the device registration status 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 the device information by using the device authentication ticket. As a result, 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 the tenant information using the tenant ID included in the device information. As a result, the device registration control unit 53 can obtain the tenant information of the tenant 9 of the integration source.

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

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

S4.1: As a result, the communication unit 11 of the device 10 accesses the (associated) URL linked to this button, so that the tenant integration request reception unit 56 is requested to log in screen 321. The tenant integration request reception unit 56 generates a login screen 321 and transmits it to the device 10.

S5: The administrator inputs the tenant ID, user ID, and password of the tenant 9 of the integration destination on the login screen 321. The operation reception unit 12 accepts this operation. If the administrator makes a mistake in entering even one of the tenant ID, user ID, and password, he / she will not be able to log in (because authentication will not be established), so integration into the wrong integration destination can be suppressed.

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

S5.2: First, the tenant integration request reception unit 56 transmits a login request including a tenant ID, a user ID, and a password to the user management unit 63. Upon establishment of authentication, the tenant integration request reception unit 56 can obtain a 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 the authority to access information such as the user management unit 63.

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

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

S5.3.2: Next, the tenant integrated control unit 55 sends a request for acquiring user information including the user authentication ticket to the user management unit 63. As a result, the tenant integration control unit 55 acquires the user information of the user U belonging to the tenant 9 after the integration. The user information includes the tenant ID.

S5.3.3: Next, the tenant integration control unit 55 sends a request for acquisition of tenant information including the tenant ID of the integration source to the tenant management unit 61. As a result, 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 a request for acquisition of tenant information including the tenant ID of the integration destination to the tenant management unit 61. As a result, 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 a transfer request for user information including the integration source tenant ID and the integration destination tenant ID to the user management unit 63. As a result, the user information of the integration source is integrated with the user information of the integration destination. Specifically, new user information is created by changing the tenant ID included in the user information of the integration source tenant 9 to the integration destination tenant ID.

S5.3.6: Next, the tenant integration control unit 55 sends a transfer request for device information including the integration source tenant ID and the integration destination tenant ID to the device management unit 65. As a result, the device information of the integration source is integrated with the device information of the integration destination. Specifically, new device information is created by changing the tenant ID included in the device information of the integration source tenant 9 to the integration destination tenant ID.

S5.3.7: Next, the tenant integration control unit 55 sends a transfer request for license information including the integration source tenant ID and the integration destination tenant ID to the license management unit 62. As a result, the license information of the integration source is integrated with the license information of the integration destination. Specifically, new license information is created by changing the tenant ID included in the license information of the integration source tenant 9 to the integration destination tenant ID. In addition, the license management unit creates new device license allocation information in which the tenant ID included in the device license allocation information of the integration source tenant 9 is changed to the integration destination tenant ID. In addition, new user license allocation information is created by changing the tenant ID included in the user license allocation information of the integration source tenant 9 to the integration destination tenant ID.

S5.3.8: Next, the tenant integration control unit 55 sends a transfer request for application setting information including the tenant ID of the integration source and the tenant ID of the integration destination to the application setting management DB 74. As a result, the application setting information of the integration source is integrated with the application setting information of the integration destination. Specifically, new application setting information is created by changing the tenant ID included in the application setting information of the integration source tenant 9 to the integration destination tenant ID.

S5.3.9: When the tenant integration control unit 55 completes steps S5.3.5 to S5.3.8, the tenant integration control unit 55 requests the tenant management unit 61 to delete the tenant information of the integration source. The tenant management unit 61 deletes the tenant information of the integration source. In addition, the user information including the tenant ID of the tenant information of the integration source, the device information, the license information, the device license allocation information, the user license allocation information, or the application setting information is deleted. As a result, it is possible to prevent the resources of the cloud system from being wasted. The information about the tenant 9 of the integration source may be deleted in steps S5.3.5 to S5.3.8, respectively.

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

S5.4: The tenant integration request receiving 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 it 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.

The integration of paid tenants and the integration of free trial tenants can also be integrated by the same procedure as in FIG.

<Home screen display processing>
The display process of the home screen 301 is supplemented. Since the home screen 301 is used by many users U, the display of the button 303 "Click here for tenant integration after this contract" may be annoying. Therefore, it is preferable that the button 303 "Click here for tenant integration after this contract" is displayed only by the device 10 during the free trial.

FIG. 12 is an example of a flowchart showing a procedure in which the home screen providing unit 51 creates 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 the device 10 is activated, the request of the home screen 301 is transmitted to the cloud system 50.

Next, the home screen providing unit 51 authenticates the device (S102). The procedure for device authentication may be the same as in FIG.

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

Next, the home screen providing unit 51 specifies the tenant ID included in the device information, requests the license information from the license management unit 62, and acquires the license information from the license management unit 62 (S104). There are as many license information as there are apps licensed to the integration source tenant 9. For example, when three applications are displayed on the home screen 301, three license information is acquired.

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

If there is only a free application (Yes in S105), it is highly likely that the cloud service is being used in a free trial because no paid contract has been made, and the home screen provider 51 said, "Tenant after this contract. Create a home screen 301 including a button 303 that says "Click here for integration" (S106).

If there is only a free application (No in S105), it is judged that the cloud service is not used in the free trial because a paid contract has been made, and the home screen provider 51 says, "Click here for tenant integration after this contract." A home screen 301 that does not include the button 303 is created (S107).

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

<Control that allows only those with a predetermined role to integrate>
There is a feature that the tenant 9 of this embodiment can be integrated on the organization side, but if any user U integrates, the number of devices 10 and user U belonging to the tenant 9 increases without the administrator's knowledge. Situations such as are occurring. Therefore, it is preferable to limit the persons who can integrate the tenant 9.

FIG. 13 is an example of a flowchart showing a procedure in which the tenant integration control unit 55 limits the persons who integrate the tenant 9. The process of FIG. 13 is performed between steps S3.3.2 and S3.3.3 of FIG.

The tenant integrated control unit 55 determines whether or not the role included in the user information is an administrator (S201). Not limited to the administrator, any role may be used as long as the integration of tenant 9 is permitted.

When the role is an administrator (Yes in S201), since the operator of the device 10 has the authority to integrate, the tenant integration control unit 55 performs the processes after step S3.3.3 in FIG. 10 (S202).

When the role is an administrator (No in S201), the tenant integration control unit 55 notifies the device 10 that the tenant integration authority is not available (S203). That is, the tenant integration request receiving unit 56 is made to create a Web page indicating that there is no authority, and the device 10 is made to display it. In addition, the processing after step S3.3.3 is not performed.

By the above processing, the person who can integrate the tenant 9 can be limited to the person who has the authority such as the administrator.

<License allocation>
By the process of FIG. 11, the user U and the device 10 of the integration source tenant 9 can be migrated to the migration destination tenant 9, but the license has not been assigned yet. The license ID of the user license allocation information of the integration source remains the license ID of the license information of the integration source. The license ID of the device license allocation information of the integration source remains the license ID of the license information of the integration source. Since the license information of the integration source has already been deleted, the device and the user cannot use the application because there is no license as it is.

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

FIG. 14 is an example of a flowchart showing a procedure in which the license management unit 62 allocates 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 or not there is a quantity limit on the license of the tenant 9 to be integrated (S301). This judgment is judged by the license type of the license information.

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

If there are three or more users U belonging to the integration source tenant 9, unassigned users U remain. Since the license ID of the user license allocation information of this user remains the license ID of the license information of the integration source, the application cannot be used after the free trial period ends.

The user license allocation information has been described above, but the same applies to the device license allocation information.

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

By doing so, the license is assigned to the user U and the device 10 migrated to the integration destination tenant 9 within the volume range, and the license is assigned 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 on the cloud system side to allocate the license.

In addition, license allocation is not required for integration between paid tenants. In the integration of free trial tenants, licenses may be assigned, but it is meaningless.

<Summary>
In this way, in the cloud system 50 of the present embodiment, the customer himself / herself performs the tenant integration work by an intuitive and simple operation of "login from the screen of the integration source device 10 that was being used with the login information of the integration destination". It can be carried out. Conventionally, a customer engineer or the like visits a customer to perform integration work, but in the integration method of this embodiment, the customer side can integrate, so that the cost and time required for integration can be reduced.

<Other application examples>
Although the best mode for carrying out the present invention has been described above with reference to examples, the present invention is not limited to these examples, and various modifications are made without departing from the gist of the present invention. And substitutions can be made.

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

Further, when three or more tenants are in the same organization, the other two tenants may be integrated into an arbitrary integration destination tenant. Further, the tenant A may be integrated into the tenant B, and then the tenant B may be integrated into the tenant C.

Further, the configuration examples shown in FIG. 9 and the like are divided according to the main functions in order to facilitate the understanding of the processing by the device 10 and the cloud system 50. The present invention is not limited by the method of dividing the processing unit or the name. The processing of the device 10 and the cloud system 50 can be divided into more processing units according to the processing content. It is also possible to divide one processing unit so as to include more processing.

The tenant integrated request receiving unit 56 is an example of the integrated request receiving means, the tenant integrated control unit 55 is an example of the integrated control means, the display control unit 13 is an example of the display means, and the operation receiving unit 12 receives. This is an example of means.

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

Japanese Unexamined Patent Publication No. 2015-204807

Claims (10)

An information processing device that provides services to devices that belong to organizational information.
An integration request receiving means for receiving a request for integration of the organization information from a device belonging to the first organization information,
By referring to the device information that associates the identification information of the tissue information with the identification information of the device, the identification information of the first tissue information associated with the identification information of the device is acquired.
It has an integrated control means for acquiring the identification information of the second organization information of the integration destination to which the first organization information is integrated based on the authentication information of the second organization information transmitted from the device. death,
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 device characterized by this. The integrated request receiving means causes the device to display an authentication information input screen for inputting the authentication information of the second organization information.
The integrated control means is characterized in that the identification information of the second organization information to which the user who has been authenticated belongs is acquired by the authentication information of the second organization information input to the authentication information input screen. The information processing device according to claim 1. The information processing device is conducting a free trial to provide the service free of charge.
The first organization information is using the 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 the free trial and the second organization information using the service for a fee. .. The integrated control means refers to the license information given to the device specified based on the identification information of the device belonging to the first organizational information.
Only when the license information does not state that the device receives the service for a fee, the integrated request receiving means causes the device to display a user interface for receiving a request for integration of the organizational information. 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 free for each application.
Only when there is no description to the effect that there is a charge in all the applications in the license information given to the device specified based on the identification information of the device.
The information processing device according to claim 4, wherein the integrated request receiving means causes the device to display a user interface for receiving a request for integrating the organizational information. When the user's authentication is established, the integrated control means refers to the user information in which the user's authority information is registered in the user's identification information, and the authority to integrate the organization information is recognized in the authority information. Judge whether it is done or not,
The invention according to any one of claims 2 to 5, wherein the first organizational information and the second organizational information are integrated only when the authority to integrate the organizational information is granted. Information processing device. One or more devices and one or more users who use the devices belong to one organization information.
The integrated control means transfers the one or more devices and one or more users belonging to the first organization information to the second organization information, thereby causing the first organization information and the second organization information. The information processing apparatus according to any one of claims 1 to 6, wherein the organization information is integrated. The integrated control means refers to the license information given to the device specified based on the identification information of the device belonging to the first organizational information.
When the number of the devices or users who can use the service is set in the license information,
The information according to claim 7, wherein the equipment and the user who belonged to the first organization information are assigned the license possessed by the second organization information of the integration destination to the extent permitted by the number. Processing equipment. An information processing system having a device belonging to the organization information and an information processing device that provides a service for the organization information.
The device is
A display means for displaying a user interface that accepts a request for integration of organizational information on a display device, and
It has a receiving means for receiving a request for integration of the organization information with respect to the user interface.
The information processing device
An integration request receiving means for receiving a request for integration of the organization information from a device belonging to the first organization information,
By referring to the device information that associates the identification information of the tissue information with the identification information of the device, the identification information of the first tissue information associated with the identification information of the device is acquired.
It has an integrated control means for acquiring the identification information of the second organization information of the integration destination to which the first organization information is integrated based on the authentication information of the second organization information transmitted from the device. death,
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 this. It is a method of integrating organizational information performed by an information processing device that provides services to devices belonging to organizational information.
A step in which the integrated request receiving means receives a request for integration of the organizational information from a device belonging to the first organizational information.
A step in which the integrated control means refers to the device information that associates the identification information of the organization information with the identification information of the device, and acquires the identification information of the first organization information associated with the identification information of the device. ,
The step of acquiring the identification information of the second organization information of the 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 step in which 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 integration method characterized by having.

Images