JP2018136852A - Application providing system and user management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To cause an application providing system to operate, even when users use applications on a second platform system that integrally manages user information via a first platform system that manages user information individually for every application, as if the application providing system provides the applications from the first platform system.SOLUTION: A user management part 340 forms a second platform 310 and integrally manages user information, and when receiving a user information registration request or a user list acquisition request related to applications 330a and 330b via a first platform 210, registers the user information for every application and returns a user list for every application.SELECTED DRAWING: Figure 3

Description

  The present invention relates to an application providing system and a user management method.

There is known an application providing system in which a plurality of platforms that provide an application are linked with each other so that an application operating on the first platform can be used from the second platform. According to such an application providing system, variations of applications provided from the second platform can be increased.
Patent Document 1 describes a system that enables applications on different software platforms to operate in a coordinated manner without any barrier. Specifically, service information (eg, class name) provided by a Java (registered trademark) application operating on the first platform is converted into information (eg, URL) that can be used on the second platform in advance. And register it in the conversion data table. When a Web application that operates on the second platform calls a URL, the specified URL is converted into a class name by the conversion data table, so a service is provided by a Java (registered trademark) application on the second platform. Is possible.

Some platforms that provide an application have a function of managing information of a user who uses the application. The user management system includes a system that manages user information individually for each application, and a system that manages user information in a unified manner using a user management function common to all applications.
In the former case, it is necessary to perform processing for linking an application and a user (user registration for the application) for each application. In the latter case, if a user is linked to a certain application, it is automatically performed for other related applications. It is also possible to link users. If you register a user by calling an application on the second platform that centrally manages user information from the first platform that manages user information individually, you can also register users on other applications on the second platform. Will be.
However, the user of the first platform has a problem that user registration is arbitrarily performed for an application that he / she does not understand, which causes confusion in use.
The present invention has been made in view of the above-described circumstances, and uses an application on a second platform system that centrally manages user information via a first platform system that individually manages user information for each application. Even if it is a case, it aims at making it operate | move like the application is provided from the 1st platform system.

  In order to solve the above-mentioned problem, the invention according to claim 1 is provided with a plurality of first user management means for individually managing user information related to users of a plurality of first applications to be provided for each application. An application providing system in which one platform system and a second platform system having second user management means for managing user information related to users of a plurality of second applications to be provided are connected. The two-user management means processes the user information for each application when a processing request for the user information related to the second application is received via the first platform system.

  According to the present invention, even when using an application on the second platform system that manages user information centrally via the first platform system that manages user information individually for each application, the first platform It can be operated as if an application is provided from the system.

1 is an overall configuration diagram of an application providing system according to an embodiment of the present invention. It is a block diagram which shows an example of the hardware constitutions of a client terminal. It is a block diagram which shows an example of a function structure of an application provision system. It is the sequence diagram which showed an example of the process performed when starting utilization of an application provision system. (A), (b) is a figure which shows an example of organization information. (A)-(c) is a figure which shows the example of a screen displayed on a client terminal, and a screen transition. It is the sequence diagram which showed an example of the procedure which manages user information from the application A which a 1st platform provides. It is the sequence diagram which showed an example of the procedure which manages user information from the application B which a 1st platform provides. It is the sequence diagram which showed an example of the procedure which manages user information from the application a which a 2nd platform provides. It is the sequence diagram which showed an example of the procedure which manages user information from the application b which a 2nd platform provides.

An embodiment of the present invention will be described. The present invention relates to an application providing system that provides an application on a second platform that manages user information in a unified manner in common to all applications from a first platform that manages user information individually for each application. Have. In short, the feature is that the user information on the second platform can be processed for each application from the first platform by associating the application name (unique application ID) on the second platform with the user ID. .
The features of the present invention described above will be described in detail with reference to the following drawings. However, the components, types, combinations, shapes, relative arrangements, and the like described in this embodiment are merely illustrative examples and not intended to limit the scope of the present invention only unless otherwise specified. .

〔overall structure〕
FIG. 1 is an overall configuration diagram of an application providing system according to an embodiment of the present invention.
The application providing system 1 includes a client terminal 100 (100A, 100B...), A first cloud server 200, and a second cloud server 300. The client terminal 100 and the first cloud server 200 are connected to each other via a network N1 so that data can be transmitted and received. The first cloud server 200 and the second cloud server 300 are connected to each other via a network N2 so that data can be transmitted and received. The client terminal 100 and the second cloud server 300 can transmit and receive data via the first cloud server 200.

The client terminal 100 is a device that can be operated by the user, such as a personal computer, a mobile terminal such as a smartphone, or a multifunction peripheral (MFP).
The first cloud server 200 is a server that provides a cloud service to the client terminal 100 via the network N1 based on a request from the client terminal 100. The second cloud server 300 is a server that provides a cloud service to the client terminal 100 via the networks N1 and N2 and the first cloud server 200 based on a request from the client terminal 100.
Here, the client terminal 100 is a terminal that is authenticated by each cloud server as a device associated with an organization that uses the cloud service when receiving a cloud service provided by each cloud server.

[Hardware configuration]
FIG. 2 is a block diagram illustrating an example of a hardware configuration of the client terminal.
The client terminal 100 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, an HDD (Hard Disk Drive) 104, an operation unit 105, a display unit 106, and a communication IF 107. Configured.
The CPU 101 is an arithmetic device that controls the client terminal 100 in an integrated manner. The ROM 102 is a nonvolatile memory that stores a BIOS, a boot program, and the like. The RAM 103 is a volatile memory serving as a work area for programs executed by the CPU 101. The HDD 104 is a non-volatile storage unit that stores programs, data, and the like different from the ROM 102. The CPU 101 realizes various functions by expanding and executing data read from the ROM 102 or the HDD 104 in the RAM 103.
The operation unit 105 is a unit that receives an operation from the user. The display unit 106 is an interface that displays operation results and the like to the user. The operation unit 105 is constituted by, for example, a keyboard and a mouse, and the display unit 106 is constituted by a display or the like. The operation unit 105 and the display unit 106 may be integrated to form a touch panel display.
The communication IF 107 is a communication interface for connecting to the network N1.
Note that the hardware configurations of the first cloud server 200 and the second cloud server 300 shown in FIG. 1 are the same as the hardware configuration of the client terminal 100, and thus the description thereof is omitted.

[Function configuration]
FIG. 3 is a block diagram illustrating an example of a functional configuration of the application providing system.

<Client terminal>
The client terminal 100 includes a browser 110. The browser 110 displays an HTML (Hyper Text Markup Language) document downloaded from the first cloud server 200 or from the second cloud server 300 via the first cloud server 200. In addition, the browser 110 receives an input from the user and issues a request according to the instruction content input from the user to the first cloud server 200 or the second cloud server 300. The browser 110 is application software (hereinafter simply referred to as “application”) installed in the client terminal 100, and the CPU 101 shown in FIG. 2 loads the browser application program read from the HDD 104 into the RAM 103 and executes it. Realized.

<First cloud server>
The first cloud server 200 includes a first platform 210 (first platform system), a launcher application 220, apps 230A and 230B (first application), user management units 240A and 240B (first user management means), and an organization management unit 250. (First organization information management means) and an initial introduction application 260 (organization information registration means). Each of the functional configurations described above is realized by the CPU loading a program read from the HDD into the RAM and executing it. The first cloud server 200 also includes a user information storage unit 241A, a user information storage unit 241B, and an organization information storage unit 251 that are realized by an HDD.
The first platform 210 is an application providing platform. That is, the first platform 210 is means for executing an application stored in the HDD of the first cloud server 200 on the first cloud server 200 and providing a function realized by the application to the user via the network.
The launcher application 220 displays a list of the applications 230A, 230B, 330a, and 330b executed on the first cloud server 200 and the second cloud server 300 on the browser 110 with icons, and each application can be performed by a mouse click or a touch operation. Is a software that can be called from each cloud server.
The application 230A and the application 230B are software that operates on the first platform 210. The application 230A and the application 230B are, for example, a printing application that causes a printer to print document data, a scanner application that causes a scanner to read an original image, and obtains original image data.

The user management units 240A and 240B are means for storing and managing data (user information) related to users who use the applications 230A and 230B in the user information storage units 241A and 241B, respectively. In the first cloud server 200, a user management unit and a user information storage unit are prepared for each application, and user information is individually managed for each application. Each user management unit 240A, 240B has an organization name of an organization to which the user belongs for a unique user ID (user name, user identification information for identifying the user) that identifies a user who uses each of the applications 230A, 230B. (Or organization code, organization identification information for identifying organization), address information of the user, etc. are stored in association with each other.
The organization management unit 250 is means for storing and managing data (organization information) related to the organization to which the user who uses each application belongs in the organization information storage unit 251. The organization management unit 250 provides, for each organization name (or organization code) uniquely set for each organization, administrator information (administrator name, administrator address information, etc.), and a cloud service provider as an organization And the information related to the application with which the user is contracted for use are stored in the organization information storage unit 251 in association with each other.
The initial introduction application 260 is software for causing the organization management unit 250 and the tenant management unit 350 to create data related to the organization when a certain organization starts using the application providing system 1. A person who operates the initial introduction application 260 is a person who has administrator authority, for example, a person who manages the first platform 210.

<Second cloud server>
The second cloud server 300 includes a second platform 310 (second platform system), apps 330a and 330b (second application), a user management unit 340 (second user management means), and a tenant management unit 350 (second organization information). Management means). Each of the functional configurations described above is realized by the CPU loading a program read from the HDD into the RAM and executing it. In addition, the second cloud server 300 includes a user information storage unit 341 and a tenant information storage unit 351 realized by an HDD.
The second platform 310 is a platform for providing applications. That is, the first platform 210 executes an application stored in the HDD of the second cloud server 300 on the second cloud server 300, and performs functions realized by the application via the network via the first cloud server 200. Means provided to the user.
The application 330 a and the application 330 b are software that operates on the second platform 310. The application 330a and the application 330b are, for example, a printing application that causes a printer to print document data, a scanner application that causes a scanner to read an original image, and obtains original image data.

The user management unit 340 is a means for managing data related to users who use the applications 330 a and 330 b by storing the data in the user information storage unit 341. The second cloud server 300 has a single user management unit 340 common to each application, and user information is managed in an integrated manner. The user management unit 340, for a unique user ID (user name) identifying a user who uses the application, the organization name (or organization code) of the organization to which the user belongs, the address information of the user, and the user The application name to be used (unique application ID, application identification information for identifying the application) and the like are stored in association with each other.
The tenant management unit 350 is means for storing and managing data (tenant information) related to the organization (tenant) to which the user who uses each application belongs in the tenant information storage unit 351, and the organization management unit of the first cloud server 200 It is the same as 250. The tenant management unit 350, for the organization name (or organization code) uniquely set for each organization, provides administrator information (administrator name, administrator address information, etc.), and the cloud service provider as the organization And associated information related to the application that is subscribed to.

[Initial sequence]
FIG. 4 is a sequence diagram illustrating an example of processing executed when starting use of the application providing system. Note that the operation subject of the client terminal 100 in this sequence is a user having administrator authority, specifically, for example, an administrator of the first platform 210.
This process is a process for making it possible to use each application 230A, 230B, 330a, 330b provided by each platform from the launcher application 220 provided by the first platform 210. It is assumed that the initial installation application 260 of the first platform 210 is called from the browser 110 of the client terminal 100 and the screen of the initial installation application 260 is displayed on the browser 110.

In step S <b> 1, the user inputs organization name and administrator information (administrator name and administrator email address) as organization information from the browser 110 to instruct execution of registration of organization information.
In step S <b> 3, the browser 110 transmits the organization information and the organization information registration request to the initial introduction application 260.
In step S <b> 5, the initial introduction application 260 outputs organization information and a registration request for organization information to the organization management unit 250.
In step S7, the organization management unit 250 executes organization information registration processing, that is, processing for storing the organization information in the organization information storage unit 251, and returns the processing result to the initial introduction application 260 (step S9).
In step S <b> 11, the initial introduction application 260 outputs organization information and a registration request for organization information to the tenant management unit 350.
In step S13, the tenant management unit 350 executes organization information registration processing, that is, processing for storing the tenant information in the tenant information storage unit 351, and returns the processing result to the initial introduction application 260 (step S15).
In step S <b> 17, the initial introduction application 260 responds to the browser 110 with the processing result.
In step S19, the browser 110 displays the processing result.

In step S <b> 21, the user inputs an application name used by the organization from the browser 110 and instructs execution of registration of application information. For example, the user inputs the apps A, B, a, and b from the browser as apps used by the organization.
In step S <b> 23, the browser 110 transmits an organization name, an application name used by the organization (applications A, B, a, and b), and an application information registration request to the initial introduction application 260.

In step S <b> 25, the initial introduction application 260 determines the organization name, the application name provided by the first platform 210 (applications A and B), and the application among the input application names to the organization management unit 250 of the first platform 210. Output information registration request. That is, the initial introduction application 260 extracts information on the application to be registered in each platform from the application names acquired from the browser 110, distributes the information to each platform, and outputs the extracted information.
In step S <b> 27, the organization management unit 250 executes application information registration processing, that is, processing for storing the application name used by the organization in the organization information storage unit 251 in association with the organization name, and the initial installation application 260. (Step S29).
In step S31, the initial introduction application 260 determines the organization name, the application name provided by the second platform 310 (applications a and b), and the application among the input application names to the tenant management unit 350 of the second platform 310. Send an information registration request.
In step S33, the tenant management unit 350 executes a process for registering application information, that is, a process for storing the application name used by the organization in the tenant information storage unit 351 in association with the organization name, and the initial installation application 260. (Step S35).
In step S37, the initial introduction application 260 responds to the browser 110 with the processing result.
In step S39, the browser 110 displays the processing result.

  As described above, the organization management unit 250 and the tenant management unit 350 store the organization name and the application name used by the organization in the organization information storage unit 251 and the tenant information storage unit 351 in association with each other.

[Example of organization information]
FIGS. 5A and 5B are diagrams illustrating an example of organization information. FIG. 5A shows organization information stored in the organization information storage unit 251 of the first platform 210, and FIG. 5B shows organization information stored in the tenant information storage unit 351 of the second platform 310.
Each organization information is associated with an organization name, an administrator name in each organization, an administrator email address, and the name of the application used in the organization among the applications provided by each platform. Stored in the format. For example, for organization 1, applications A and B provided by the first platform 210 and applications a, b, and c provided by the second platform 310 are registered as applications to be used.

[Screen transition example]
Hereinafter, use of an application by a general user will be described.
FIG. 6 is a diagram illustrating a screen displayed on the client terminal and a transition example of the screen.
FIG. 6A is an example of a launcher screen 400 that the launcher application 220 of the first platform 210 provides via the browser 110. This figure is an example of a screen displayed on the client terminal 100 used by a general user belonging to the organization 2 shown in FIG. For the organization 2 shown in FIG. 5, since the applications A, B, a, and b are linked as the applications to be used, the launcher screen 400 has the activation icons 401A, A, B for the applications A, B, a, and b. 401B, 401a, and 401b are respectively displayed. When the user presses the activation icon 401B of the application B, the screen transitions to the application screen 410B shown in FIG. 6B, and when the user presses the startup icon 401b of the app b, the screen transitions to the application screen 410b shown in FIG.

The apps B and b have a common user management function, and the app screens 410B and 410b are related to user management in addition to the unique screens 411B and 411b for realizing the functions unique to the apps B and b. A common screen 413 is provided.
The common screen 413 includes a user list button 415, a registration button 417, and a back button 419. The user list button 415 is a button for displaying a user list, the registration button 417 is a button for registering an application with a user ID, and the return button 419 is a button for transitioning to the launcher screen 400 It is. Since each application screen 410B, 410b includes a common screen 413, user registration and display of a user list can be performed from each application.
The application screen 410B in FIG. 6B shows the print application as the application B, and the application screen 410b in FIG. 6C shows the scanner application as the application b. However, the type and content of the application are not particularly limited. .

[Main sequence 1]
An example of a procedure for managing user information from an application provided by the first platform will be described. As a premise, the client terminal 100 is connected (logged in) to the first platform 210 in a state linked to the organization, and the browser 110 of the client terminal 100 displays the launcher screen 400 shown in FIG. It shall be.

<App A>
FIG. 7 is a sequence diagram illustrating an example of a procedure for managing user information from the application A provided by the first platform.
First, the startup procedure of application A will be described.
In step S <b> 101, the user instructs activation of the application A by pressing the activation icon 401 </ b> A of the application A from the launcher screen 400.
In step S <b> 103, the browser 110 transmits an activation request for the application A to the launcher application 220.
In step S105, the launcher application 220 calls the application 230A.
In step S <b> 107, the application 230 </ b> A outputs content data (HTML data) for generating the initial application screen (see FIGS. 6B and 6C) of the application 230 </ b> A to the launcher application 220.
In step S109, the launcher application 220 outputs an initial application screen to the browser 110.
In step S110, the browser 110 displays an initial application screen.

Next, a user registration procedure for the application A will be described.
In step S111, the user presses the registration button 417 on the common screen 413 (see FIGS. 6B and 6C) to instruct to call the user registration screen.
In step S113, the browser 110 requests the application 230A to call a user registration screen.
In step S115, the application 230A outputs content data for generating a user registration screen to the browser.
In step S116, the browser 110 displays a user registration screen.

In step S117, the user inputs user information (user ID, organization name, address information, etc.) of the user 1 from the browser 110, and instructs registration of information related to the user 1.
In step S119, the browser 110 transmits the user information of the user 1 and a user registration request (user information processing request) to the application 230A.
In step S121, the application 230A outputs the user information of the user 1 and the user registration request to the user management unit 240A.
In step S123, the user management unit 240A executes user information registration processing. That is, the user management unit 240A associates the organization name, address information, and the like with the user ID and stores them in the user information storage unit 241A.
In step S125, the user management unit 240A returns the processing result to the application 230A.
In step S133, the application 230A returns the processing result to the browser 110.
In step S134, the browser 110 displays the processing result.

Finally, a user list acquisition procedure will be described.
In step S135, the user presses the user list button 415 on the common screen 413 to instruct acquisition of the user list of the user associated with the application 230A.
In step S137, the browser 110 transmits a user list acquisition request (user information processing request) to the application 230A.
In step S139, the application 230A outputs a user list acquisition request to the user management unit 240A.
In step S141, the user management unit 240A creates a user list.
In step S143, the user management unit 240A returns the created user list to the application 230A.
In step S145, the application 230A returns the acquired user list to the browser 110.
In step S146, the browser 110 displays a user list.

<App B>
FIG. 8 is a sequence diagram illustrating an example of a procedure for managing user information from the app B provided by the first platform.
The application B activation procedure (steps S151 to S160), the user registration procedure (steps S161 to S184), and the user list acquisition procedure (steps S185 to S196) are the procedures related to the application A (steps S101 to S110, S111 to S134). , S135 to S146), the description thereof is omitted.
As described above, in the first platform 210, the applications 230A, 230B. . . For each user management unit 240A, 240B. . . Is prepared, each user needs to perform user registration for each application. In addition, since the user management units 240A and 240B individually include user information storage units 241A and 241B, user information is not mixed between different applications and is independent.

[Main sequence 2]
An example of a procedure for managing user information from an application provided by the second platform will be described. As a premise, the client terminal 100 is connected (logged in) to the first platform 210 in a state linked to the organization, and the browser 110 of the client terminal 100 displays the launcher screen 400 shown in FIG. It shall be.

<App a>
FIG. 9 is a sequence diagram illustrating an example of a procedure for managing user information from the application a provided by the second platform. Note that description of steps similar to those in FIG. 7 is omitted as appropriate.
The activation procedure for the application a (steps S201 to S210) is the same as the activation procedure for the application A (steps S101 to S110).
A user registration procedure (steps S211 to S234) for the application a will be described.
Steps S211 to S219 are the same as the user registration procedure for the application A (steps S111 to S119).
In step S221, the application 330a outputs the user information of the user 1 and a user registration request (user information processing request) to the user management unit 340.

In step S <b> 222, the user management unit 340 executes processing for confirming whether or not user information related to the user 1 is stored in the user information storage unit 341. In this example, it is assumed that the user information of the user 1 is not stored in the user information storage unit 341.
In step S223, the user management unit 340 executes user information registration processing. That is, the user management unit 340 stores the organization name, address information, and the like in the user information storage unit 341 in association with the user ID.
In step S225, the user management unit 340 returns the processing result to the application 330a.
In step S227, the application 330a outputs to the user management unit 340 a request for registering the application 330a as a use application of the user 1 in association with the user ID (use application registration request, user information processing request).

In step S229, the user management unit 340 executes use application registration processing. That is, the user management unit 340 associates the user ID with the name of the application used by the user and stores it in the user information storage unit 341.
In step S231, the user management unit 340 returns the processing result to the application 330a.
In step S233, the application 330a returns a processing result to the browser 110.
In step S234, the browser 110 displays the processing result.

  Next, a user list acquisition procedure (steps S235 to S246) related to the application a will be described.

In step S235, the user presses the user list button 415 on the common screen 413 to instruct acquisition of the user list of the user associated with the application 330a.
In step S237, the browser 110 transmits a user list acquisition request (user information processing request) to the application 330a.
In step S239, the application 330a instructs the user management unit 340 to acquire a user list related to the application 330a. That is, the application 330 a outputs an application name (application a) and a user list acquisition request to the user management unit 340.
In step S241, the user management unit 340 creates a user list for the application 330a.
In step S243, the user management unit 340 returns the created user list to the application 330a.
In step S245, the application 330a returns the acquired user list to the browser 110.
In step S246, the browser 110 displays a user list.

<App b>
FIG. 10 is a sequence diagram illustrating an example of a procedure for managing user information from the application b provided by the second platform. Note that description of steps similar to those in FIG. 9 is omitted as appropriate.
The activation procedure for the application b (steps S251 to S260) is the same as the procedure for the application a (steps S201 to S210).

A user registration procedure (steps S261 to S284) for the application a will be described.
Steps S261 to S269 are the same as the user registration procedure (steps S211 to S219) for the application a.
In step S271, the application 330b outputs the user information of the user 1 and the user registration request to the user management unit 340.
In step S <b> 272, the user management unit 340 executes processing for confirming whether or not user information related to the user 1 is stored in the user information storage unit 341. In this example, since the user information of the user 1 is stored in the user information storage unit 341, the user management unit 340 skips the user information registration process corresponding to step S223.
In step S275, the user management unit 340 returns the processing result to the application 330b.
Since the subsequent processing (steps S277 to S284) is the same as steps S227 to S234, description thereof is omitted.

  The user list acquisition procedure (steps S285 to S296) related to the app b is the same as the user list acquisition procedure (steps S235 to S246) related to the app a, and thus the description thereof is omitted.

  As described above, the user management unit 340 receives a user registration request from each application. The user management unit 340 executes user information registration processing when user information is not registered, and skips user information registration processing when user information (user ID) is already registered. Execute.

  In addition, since the user management unit 340 manages the user ID and the application name used by the user in association with each other, when the user list acquisition request specifying the application name is received, the user management unit 340 uses the application. A list of registered users can be returned. When the user management unit 340 receives a user list acquisition request without specifying an application name, the user management unit 340 returns a list including all registered users.

  When registering user information in the second platform that centrally manages user information via the launcher application provided by the first platform that manages user information individually for each application, the user management unit of the second platform The application name is associated with the ID and stored. By executing such processing, user management similar to that of the first platform can be realized on the second platform.

[Example of user information]
User information managed by the user management unit 340 will be described. Table 1 is an example of correspondence information between user IDs stored in the user information storage unit 341 and applications registered for use.

When the user performs user registration and use application registration via the application, the user ID and the application name to be used are associated with each other and stored in the user information storage unit 341 (steps S221 to S231. Also, the user ID is already set. If registered, the application to be used is additionally associated with the user ID and stored in the user information storage unit 341 (S271 to S281).
In the case of Table 1, when the user list of the application b is requested, the user management unit 340 responds with “User1, User2, User5” as the user list.
Further, when a user list is requested without specifying an application name, the user management unit 340 responds with “User1, User2, User3, User4, User5” as a user list. When there is a user ID that is not associated with any application (for example, User3), such as when application registration is canceled, the user ID has received a request for a user list that does not specify an application name. When only included in the user list.

In the above embodiment, each function included in each server may be arranged in a single server, or may be distributed in different devices. In addition, each server may be provided with each function constituting the system.
A program that realizes each function by being executed by each device of the above embodiment is a file in an installable or executable format, such as a CD-ROM, a CD-R, a memory card, a DVD (Digital Versatile Disk), The program is stored in a computer-readable storage medium such as a flexible disk (FD).
Further, the program may be provided by being stored on a computer connected to a network such as the Internet and downloaded via the network. The program may be provided or distributed via a network such as the Internet. Further, the program may be provided by being incorporated in advance in a ROM or the like.

[Summary of Embodiments, Actions, and Effects of the Present Invention]
<First embodiment>
This aspect includes a plurality of first user management means (user management units 240A and 240B) that individually manage user information related to users of a plurality of first applications (applications 230A and 230B) to be provided for each application. A first platform system (first platform 210) and a second user management means (user management unit 340) that collectively manages user information related to users of a plurality of second applications (applications 330a and 330b) to be provided. The invention relates to an application providing system 1 to which a two-platform system (second platform 310) is connected.
In the application providing system according to this aspect, the second user management means processes the user information for each application when the user information processing request for the second application is received via the first platform system. And
In this aspect, since the second user management means processes user information for each application, even if the application on the second platform system is used via the first platform system, the application is sent from the first platform system. It can be operated as provided.

<Second and third embodiments>
In the application providing system 1 according to the second aspect, each platform system (first platform 210, second platform 310) includes an organization information management unit (organization management unit) that manages organization information related to an organization to which each user belongs. 250, tenant management unit 350), and one platform system (first platform 210) includes organization information registration means (initial introduction application 260) for outputting the inputted organization information to each organization information management means. It is characterized by that.

In the application providing system 1 according to the third aspect, the organization information management means manages the organization identification information for identifying the organization in association with the application identification information for identifying the application used by the organization. .
In a business application platform, a service use contract is made in an organizational unit to which individual users belong. In such a case, if the organization information input at the time of service introduction can be linked between two platforms having different user management methods, the cost at the time of service introduction can be reduced. According to this aspect, since the organization information input from one platform system is also provided to the other platform system, the labor for registering the organization information can be reduced.

<Fourth embodiment>
In the application providing system 1 according to this aspect, the second user management means (user management unit 340) is a user from one second application (application 230a) called through the first platform system (first platform 210). When receiving an information registration request (steps S221 and S227), executing a process (step S229) for associating the second application identification information for identifying one second application with the user identification information for identifying the user. It is characterized by.
In this aspect, since the second application identification information (eg, application name) on the second platform is associated with the user identification information (eg, user name), the user management function for each application can be provided from the second platform. . Accordingly, even when an application on the second platform is provided via the first platform, the same operation as that of the first platform can be realized.

<Fifth embodiment>
In the application providing system 1 according to this aspect, the second user management means (user management unit 340) is a user from one second application (application 230a) called through the first platform system (first platform 210). When a list acquisition request (step S239) is received, a process of creating a list of users associated with one second application (step S241) is executed.
In this aspect, application identification information (eg, application name) on the second platform is associated with user identification information (eg, user name). For this reason, when a user list is requested by specifying an application name, a list of users associated with the application can be acquired. According to this aspect, even when an application on the second platform is provided via the first platform, the same operation as that of the first platform can be realized.

<Sixth embodiment>
This aspect includes a plurality of first user management means (user management units 240A and 240B) that individually manage user information related to users of a plurality of first applications (applications 230A and 230B) to be provided for each application. A first platform system (first platform 210) and a second user management means (user management unit 340) that collectively manages user information related to users of a plurality of second applications (applications 330a and 330b) to be provided. The invention relates to a user management method in a system (application providing system 1) in which a two-platform system (second platform 310) is connected.
In the user management method according to this aspect, the second user management means executes a step of processing the user information for each application when the user information processing request for the second application is received via the first platform system. It is characterized by doing.
This aspect has the same effect as the first embodiment.

  DESCRIPTION OF SYMBOLS 1 ... Application provision system, N1, N2 ... Network, 100 ... Client terminal, 101 ... CPU, 102 ... ROM, 103 ... RAM, 104 ... HDD, 105 ... Operation part, 106 ... Display part, 107 ... Communication IF, 110 ... Browser 200, first cloud server 210, first platform (first platform system), 220, launcher application, 230A, 230B, application (first application), 240A, 240B, user management unit (first user management means) , 241A, 241B ... User information storage unit, 250 ... Organization management unit (organization information management unit), 251 ... Organization information storage unit, 260 ... Initial introduction application (organization information registration unit), 300 ... Second cloud server, 310 … Second platform (second platform System), 330a, 330b ... application (second application), 340 ... user management unit (second user management unit), 341 ... user information storage unit, 350 ... tenant management unit (organization information management unit), 351 ... tenant information Storage unit 400 ... Launcher screen 401 ... Activation icon 410 ... Application screen 411 ... Unique screen 413 ... Common screen 415 ... User list button 417 ... Registration button 419 ... Back button

JP 2016-004318 A

Claims (6)

A first platform system comprising a plurality of first user management means for individually managing user information related to users of a plurality of first applications to be provided for each application;
A second platform system comprising second user management means for managing user information related to users of a plurality of second applications to be provided, and an application providing system connected thereto,
The second user management means processes the user information for each application when receiving a processing request for the user information related to the second application via the first platform system. system. Each platform system includes organization information management means for managing organization information related to an organization to which each user belongs,
The application providing system according to claim 1, wherein the one platform system includes an organization information registration unit that outputs the input organization information to each organization information management unit.   3. The application providing system according to claim 2, wherein each of the organization information management means manages application identification information for identifying an application used by the organization in association with organization identification information for identifying the organization. .   When the second user management means accepts a registration request for the user information from the one second application called through the first platform system, the second user management means executes the first user identification information for identifying the user. The application providing system according to any one of claims 1 to 3, wherein a process of associating second application identification information for identifying the second application is executed.   When the second user management means receives a user list acquisition request from the one second application called through the first platform system, the list of users associated with the one second application The application providing system according to any one of claims 1 to 4, wherein a process for creating the application is executed. A first platform system comprising a plurality of first user management means for individually managing user information related to users of a plurality of first applications to be provided for each application;
A user management method in a system connected to a second platform system including a second user management unit that centrally manages user information relating to users of a plurality of second applications to be provided;
The second user management means executes a step of processing user information for each application when a processing request for user information related to the second application is received via the first platform system. User management method.

Images