JP2006011652A - Multiple service provision spaces integration method, computer system for integration of multiple service provision spaces, management server and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a means for integrating a plurality of service provision spaces to allow use of service. <P>SOLUTION: This method for integrating the plurality of service provision spaces includes a step wherein a space management server (SS) managing information about a user capable of using the space and information about the service provided inside the service provision space (A) logs in a space management server (SS) of the other service provision space (B). The service spaces (A, B) are integrated during the login, and the user of one service provision space (A) can use the service of the other service provision space (B) within prescribed use authority. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a plurality of service providing space integration methods and the like.

Patent Document 1 discloses a resource identification mechanism having communication means attached to various devices and resource information management means, communication means communicating with communication means of the resource identification mechanism, local space management means, and belonging resource management means, A resource management system has been disclosed that has a local management mechanism having local usage right management means and application management means, and allows a user to use resources existing in a local space.
According to this resource management system, it is possible to dynamically provide usage rights for various devices, services, and contents existing on the network to individual users. In addition, it is possible to issue an immediate usage right without going through every single process until the authorization of the person and the issuance of the usage right.
JP-A-2003-162464

According to the method described in Patent Document 1, when a user uses a service in another space, the service usage right for the other space is registered, and the user can use the service in another space. Need to log in to the other space.
However, Patent Document 1 does not describe that the spaces are integrated and used.
An object of the present invention is to provide means for integrating a plurality of service providing spaces to make a service available.

  The present invention is a method for integrating a plurality of service providing spaces, and a space management server that manages information on services provided in the service providing space and information on users who can use the space is provided by other services. Including a step of logging in to a space management server of the provision space, wherein the service spaces are integrated during the login, and a user of one service provision space uses the service of the other service provision space within a predetermined use authority It is possible to feature.

According to the above method, when a space management server in a certain space logs in to a space management server in another space and the spaces are integrated, the user can log in to one service providing space, Even without direct login to the other service providing space, the service of the other service providing space can be used within a predetermined use authority.
That is, even if an individual user does not log in to another space, the space management server logs in to the other space and performs space integration, so that services in other spaces can be used.

The login is a spatial connection that allows a user of the space management server who has logged into the space management server of another service providing space to use the service of the other service providing space within the usage authority acquired by the space management server. It is preferable to log in.
Further, the login may be a login for space fusion that allows the management information of the space management server and the user information to be managed by the space management server of another service providing space.

  The present invention relating to a computer system is a computer system for integrating a plurality of service providing spaces, and each service providing space includes information on services provided in the space and information on users who can use the space. A space management server that is managed by a managing space management server and manages information on services provided in the service providing space and information on users who can use the space is a space management server in another service providing space. Means that the service spaces are integrated during the login, and the user of one service providing space can use the service of the other service providing space within a predetermined use authority. It is a feature.

  The present invention relating to a space management server is a space management server for managing space, means for managing information on services provided in the space, means for managing information on users who can use the space, and Means for a user of one service providing space to log in to a space management server of another service providing space in order to obtain a spatial integration state in which the service of the other service providing space can be used within a predetermined use authority; It is characterized by having.

  The present invention relating to a computer program is a computer program for causing a computer to function as a space management server, a function for managing information on services provided in the space, and a function for managing information on users who can use the space Log in to the space management server of the other service provision space, integrate the spaces, so that the user of one service provision space can use the service of the other service provision space within the predetermined use authority This function is for causing a computer to execute the function to perform.

  According to the present invention, since the space management server logs in to another space and space integration is performed, if the user logs in to one service providing space, the user logs in directly to the other service providing space. Even if the service is not performed, the service in the other service providing space can be used within a predetermined use authority.

Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.
[Outline of Spatial Management Server]
FIG. 1 shows the main functions of a space management server (Space Server) SS used for space management / integration of a service providing space (hereinafter referred to as “space”). The space management server SS has a function of performing space user management and a function of performing space service management.
The spatial server includes a computer and a computer program for causing the computer to execute each function. One computer may have a function as a plurality of spatial servers.

The space has user management information and service management information as space management information.
The space management server SS includes a user directory adapter UDA and an integrated user directory IUD for space user management.
The space management server SS includes a service directory adapter SDA and an integrated service directory ISD for space service management.
The space refers to a range managed by the space management server SS, and specifically refers to a range managed by the integrated user directory IUD and the integrated service directory ISD as shown in FIG.
Note that space is not limited by physical constraints. For example, on a computer network, a space is constructed across rooms, constructed in only one room, constructed only with a notebook PC, or constructed across countries. May be.

Here, authenticating in order to use the service provided by the space is called “login”, and the service provided by the space can be used only when the login is successful.
The subject of login to the space is a user or space. As shown in FIG. 2, when a user logs in to a space, the user can use a service provided in the space.
In the present invention, a user can log in to a space, and a certain space A can log in to another space B as shown in FIG.
That is, the space has a function of accepting login from the user or other space and a function of logging in to another space.

[User management]
The space user management is performed by the user directory adapter UDA and the integrated user directory IUD of the space management server SS.
Here, the user information is defined as user-specific information possessed by each individual user. The user information is held, for example, in record units with the user name as the primary key.
Examples of user information include Unix (registered trademark) user account information, NIS (Network Information Service) user account information, information managed by LDAP (Lightweight Directory Access Protocol), information managed by MySQL, There is information managed by a general DBMS (DataBase Management System). The user information preferably includes a user name and password necessary for login, but may be information for biometric authentication such as iris information or other information.

Since there are various media (mounting environments) in which user information is held as described above, the user directory adapter UDA absorbs and conceals differences between media holding user information. , To be used uniformly.
Further, the user directory adapter UDA has a login processing function for accepting login from a user or another space management server SS via the integrated service directory ISD as necessary.

The login to the space is performed by presenting a key or key-ring for logging in to the user directory adapter to the space. As shown in FIG. 4, the key includes information for specifying a login target user directory adapter UDA in the space (target UDA specification information) and information for logging in to the user directory adapter UDA (login information). It is configured to include.
The login information corresponds to the user information. For example, the login information for the user directory adapter UDA having the user name and the password as the user information is the user name and the password.
When a key is presented to the space management server SS from the login main body (user or space to log in), the space management server SS tries to log in to the subordinate user directory adapter UDA and specifies the target UDA of the key. Attempt to log in to the user directory adapter UDA specified by the information.

  The key ring is a collection of a plurality of keys (key1, key2, key3) (see FIG. 5). The key ring is a specialized key ring processed so that only a specific space to be logged in can be used, and the login main body logs in by presenting this specialized key ring to the space management server SS to be logged in. . The login process using the key ring will be described later.

The user directory adapter UDA also has a function of issuing a capability object to a login source that has successfully logged in.
The capability object is a temporary object that is generated when the login process is successful in the user directory adapter UDA and is given to the user or the space that has logged in. This capability object includes information (such as an address) that identifies the adapter UDA that generated the object, and can be used for the adapter UDA that generated the object.
The capability object is used to make the service of the space S available by the user or the space management server SS presenting the capability object to the space management server SS of the issued space, It is used for authentication between the logged-in space and the logged-in space.
Since the user directory adapter only provides a unified method for login and the like, it is not a general one such as NIS, but if a user directory adapter having a function of UDA is adopted. There is no need to use a separate user directory adapter UDA.

The integrated user directory IUD has a function of integrating and managing a plurality of user directory adapters. As shown in FIG. 1, the integrated user directory IUD can manage a plurality of user directory adapters by integrating them hierarchically.
When the integrated user directory IUD is hierarchically constructed as shown in FIG. 1, the lower integrated user directory IUD is also recognized as one user directory adapter UDA from the upper integrated user directory IUD.
That is, it is recognized from the upper integrated user directory IUD in FIG. 1 that there are three user directory adapters UDA (UDA connected to LDAP, UDA connected to MySQL, and lower IUD regarded as UDA). Even if there is UDA, it is only necessary to perform processing in consideration of these three adapters UDA, and the processing of the upper integrated user directory is reduced.
The processing for the user directory adapter UDA connected to the two NISs is performed by the lower integrated user directory IUD.

The integrated user directory IUD has a composite login function that attempts to log in to all connected adapters UDA during the login process. That is, when a login request is made from the login main body to the space management server SS with the key presentation to the space, the integrated user directory IUD sequentially tries the login processing to the connected adapter UDA. . As described above, the integrated user directory IUD can control the order of use among the connected user directory adapters UDA.
When a key ring is presented from the login subject to the space management server SS, the space management server SS tries to log in the user directory adapter UDA connected to the integrated user directory IUD under control of the integrated user directory IUD. Login to each user directory adapter UDA specified by each target UDA specifying information of each key included is successful.

The integrated user directory IUD receives the capability object from the adapter UDA that has been successfully logged in.
When login to a plurality of adapters UDA is successful and the integrated user directory IUD receives capability objects from the plurality of adapters UDA, the integrated user directory IUD is capability-ring as a collection of a plurality of capability objects (see FIG. 6). ) Is generated. This capability-ring is sent to the space management server SS of the user or other space in the same manner as a normal user capability object.
The capability-ring is handled as one capability object, and by combining a plurality of capability objects into one, the number of capability objects handled at a time is suppressed. Thus, the integrated user directory IUD has a function of integrating information obtained from a plurality of adapters UDA.
The capability-ring is processed into a specialized state so that it can be used only in the space by including information specifying the space in which the capability-ring is generated, and then the space- Sent to S.

  The integrated user directory IUD also has a function of controlling access to user information.

[About service management]
Spatial service management is performed by the service directory adapter SDA of the space management server SS and the integrated service directory ISD.
Here, the service is the smallest unit of processing provided by the space, and examples thereof include file system mounting and illumination illumination adjustment service by WebDAV (Distributed Authoring and Versioning protocol for the WWW). . Further, when a plurality of services are integrated to provide a single service, the combined service is also handled as a single service.
Services are controlled by Jini Lookup service, SOAP (Simple Object Access Protocol), CORBA (Common Object Request Broker Architecture), etc., but the service directory adapter SDA conceals the implementation of such services and makes it uniform. The service can be used.

Similar to the integrated user directory IUD, the integrated service directory ISD has a function of hierarchically integrating and managing the service directory SDA (see FIG. 1).
The integrated service directory ISD has a function of providing information on services that can be provided in the space, types of services, access control for services, and the like.

[Space recognition function of the space management server]
The space management server SS has a function of recognizing other existing spaces on the computer network. Each space (space management server SS) has an address, and the space is specified by the address on the network.
As space recognition, broadcast-based space search for neighboring addresses, multicast for a specific range, and unicast-based inquiry to a recognized space can be performed. With such a space recognition function, it is possible to search and recognize a partner space for space integration (joining / fusion) described later.

[About spatial integration]
Here, when there are two spaces A and B, one of the spaces (space A) has the login authority for the other space (space B), and the login is successful. “Space A and Space B are integrated”.
Each space A and B may have a different management entity. Spatial integration is for securely coordinating spaces that may have different management subjects.

In order for the space A to log in to the space B, the space management server SS-A in the space A has a key or key ring for logging in to the space B. In addition, the space B has “space A” as user information. It should be noted that all user directory adapters UDA in space B may be able to accept a login for space A, or only some user directory adapters UDA in space B may be able to accept a login for space A.
When space A logs into space B, both spaces A and B are integrated. As described below, space integration includes space coupling and space fusion.

[About spatial coupling]
As shown in FIG. 7, the space management server SS-A in the space A logs in to the space management server SS-B in the space B for space connection, and if the login is successful, the space B changes to the space A. On the other hand, a capability object indicating the authority to use the space B is issued, and a combined space AB is configured.
As shown in FIG. 8, when the space combination is performed, all users of the space A can use the service of the space B within the range of “use authority of the space B” that the space A has. At this time, the user in the space A does not need to log in to the space B. That is, since the combined space AB is configured, the user of the space A can use the service of the space B simply by logging into the space A.
In the space combination, the user in the space A uses the service in the space B using the right to use the space B acquired in the space combination. Therefore, the service in the space B that can be used by the user in the space A is Same for all users.

In such a space combination, when there is an organization A1 that manages the space A and an organization B1 that manages the space B, and the user management is different between the two organizations, a service that coordinates the services of both spaces (for example, This is suitable for executing a remote conference service between the two organizations A1 and B1. In the case of the remote conference service, the user of the organization A1 can perform the service on the side of the space B (operation of a TV camera, a microphone, a shared whiteboard, etc.) simply by logging into the space A.
Spatial coupling can also be used in such a way that services on mobile networks owned by mobile phone carriers and services on security and security computer systems are linked. For example, a space management server SS that manages services in a mobile network is provided to construct a space A, a space management server SS that manages services in a security and security computer system is provided to construct a space B, and space coupling is performed. It is also possible to combine both spaces so that services in both spaces can be used cooperatively.
In this way, by constructing a space by the space management server SS, it is possible to link different spaces of the management subject, that is, the mobile network and the security computer system.
The spatial fusion described later is suitable for subordinately integrating a small space into a large space, whereas the spatial combination is suitable for equalizing a space (of the same scale). .

Here, the spatial coupling includes a bidirectional coupling in which the spaces A and B are logged in to each other and a unidirectional coupling in which only one of them is logged in. When two-way coupling is performed, a user in either space can use the service in the other space. On the other hand, in the case of unidirectional coupling, for example, when space A is unidirectionally coupled to space B (in the case of FIGS. 7 and 8), users in space A can use services in space B, but users in space B Cannot use the service in space A.
For this reason, in the case of a teleconferencing service, it is preferable to use it in a bidirectionally coupled state.

FIG. 9 shows a processing operation at the time of space combination in which the space A logs into the space B. The combination of spaces occurs when an administrator of a space (space management server SS) (who has administrator authority in space A) tries to perform a service in which services in both spaces are coordinated.
First, the space management server SS-A in the space A logs in to the space management server SS-B in the space B (1: login). Then, the space management server SS-B of the space B performs a login process entrustment to the integrated user directory IUD of the space B (1.1: login process entrustment). The integrated user directory IUD sequentially performs login processing for the space A with respect to the connected user directory adapter UDA.
For example, when the first user directory adapter UDA-1 does not permit the login of the space A, the login process (1.1.1: login process) for the first user directory adapter UDA-1 fails and fails. Is returned to the integrated user directory IUD.

Subsequently, the integrated user directory IUD shifts to a login process (1.1.2: login process) for the second user directory adapter UDA-2. When the second user directory adapter UDA-2 permits the login of the space A, the login process for the adapter UDA-2 is successful, and the capability object is passed to the integrated user directory IUD.
The integrated user directory IUD performs the same login process for all user directory adapters UDA in the space B. When the obtained capability object is one, the capability object is directly passed to the space management server SS-A in the space A via the space management server SS-B.
When there are a plurality of obtained capability objects, a capability-ring (a bundle of capability objects) is created, and this is used as one capability object, and the space management server SS- of the space A via the space management server SS-B. Passed to A.

Through the above processing, the space A is connected to the space B (unidirectional connection), and the user of the space A can use not only the service of the space A but also the service of the space B.
In order to realize bidirectional coupling, the same login as described above may be performed for the space B with respect to the space A, and thus the space B can acquire the capability object from the space A.

FIG. 10 shows a processing operation when the user of the space A uses the service of the space B in the space coupling state.
First, the user (user terminal) in space A makes a service use request for space B to the space management server SS-A in space A (1: space B service use request). Upon receiving the usage request from the user, the space management server SS-A in the space A makes a service use request to the space management server SS-B in the space B, and the capability object (space B in the space B) obtained by the login process. (Usage authority) is presented (1.1).

Then, when it is confirmed that the request is a service use request from a space with usage authority, the space management server SS-B in space B searches the integrated service directory ISD in space B for the requested service. Is executed (1.1.1). When the requested service is found, the integrated service directory ISD performs a service acquisition process within the usage authority of the space A for the service directory adapter SDA that manages the service (1.1.1.1). .
In the service acquisition process, the service directory adapter SDA generates a service control handler (proxy) for the user in the space A to use the service, and the space management server SS-B in the space B and the space management server SS in the space A. -Send to user (user terminal) in space A via A. The user in the space A who has obtained the service control handler can use the service in the space B using the service control handler (2: control using the service control handler (proxy)).
The above is the service use processing in the case of unidirectional connection, but in the case of bidirectional connection, the user in space B can also use the service in space A by the same processing.

[About spatial fusion]
As shown in FIG. 11, space fusion is also performed when the space A logs into the space B, similarly to the space connection.
The space management server SS-A in the space A logs in to the space management server SS-B in the space B for space fusion, and if the login is successful, the space B merges with the space A. A capability object for authentication is issued, and a fusion space B-A is formed. The login process for the fusion is the same as the login process for the combination shown in FIG. 9 except that the purpose of the combination and the fusion is different.

  The fusion space B-A is an expansion of the space B by integrating the space A as a part of the space B. That is, at the time of space fusion, the user information and service information of the space A are also managed by the space management server SS of the space B, and the space A becomes a part of the space B and substantially disappears. The space B (fusion space B-A) is enlarged by the space A.

  In such space fusion, communication in another relatively large space B (such as a building or a room) in which a computer (such as a notebook PC) that constitutes one space A and can be carried by wireless communication is possible. When entering the possible area, the space A by the notebook PC is merged with the other space B to form a merged space A-B including the notebook PC. Suitable for including services by PC.

In the fusion space B-A, both users of the space A and users of the space B use the service of the fusion space B-A (the service of the space B plus the service of the space A) under certain restrictions. it can. For fusion, “complete fusion” in which space B integrates all service information and all user information in space A and “partial fusion” in which some services and / or some user information are integrated. There exists.
The integration of service information and / or user information is performed when space A logs into space B.

In the merged state, the user in space A and the user in space B can use the services in both spaces A and B with at least the guest authority. The user information differs depending on how the user is already described.
This point will be described with reference to an example in which a small space A by a notebook PC is merged with another large space as shown in FIG. Here, it is assumed that the user U1 of the small space A configured by the notebook PC is an administrator of the space A (a user having administrator authority). The user U1 is also assumed to be a general user in a large space B.
The user information of the space A describes that the user U1 is an administrator of the space A (referred to as “manager @ space A”), and the user U1 is a general user of the space B ( General user @ space B) is also described. Normally, “administrator @ space A” is described as the user information of the user directory adapter UDA in the space A, and “general user @ space B” is described as the user information of the other user directory adapter UDA in the space A. .
Further, in the user information of the space B, as with the space A, “general user @ space B” and “manager @ space A” are described.

When the user U1 logs in to the fusion space B-A, the user U1 actually logs in to the enlarged space B. And since the user U1 is described in the user information as “general user @ space B” and “administrator @ space A” in the space B, (a) login to the space B with the authority of the general user in the space B (B) login with the authority of the administrator of the space A, and (c) login with the authority of both the “general user @ space B” and the “administrator @ space A”.
The authority to log in is specifically determined by selecting a user directory adapter UDA in which user information is described.
That is, if only the adapter UDA in the space B in which “general user @ space B” is described and logged in, the above login (a) is made. In this case, the service in the space B (before fusion) is general. It can be used with user authority, and the service of space A can be used with guest authority.
In addition, if only the adapter UDA in the space B in which “administrator @ space A” is described and logged in, the login of the above (b) is performed. In this case, the service in the space B (before fusion) is a guest The service in space A can be used with administrator authority.
As described above, in the fusion space, there is a case where the use authority is not set in any of the spaces (spaces A and B) even after logging in, but even in this case, it can be used with the guest authority.
Services that can be used with guest authority are set in advance in each space as services that can be disclosed to the outside through integration.

  In many cases, the user U1 wants to use the space A, which is an administrator, and the space B, which is a general user, in an integrated manner. Log in by selecting both the adapter UDA in which “@space B” is described and the adapter UDA in which “administrator @ space A” is described. In this case, the service in space B (before fusion) can be used with general user authority, and the service in space A can be used with administrator authority.

By performing the login in (c) above, for example, the administrator U1 of the small space A by the notebook PC merges the space A with the large space B of the building to form the fused space B-A, and the fused A notebook PC (space A) can be used in the space B-A.
More specifically, when the space B includes a display display as a service, the U1 accesses an image database that is a service of the notebook PC (space A) with administrator authority in the fusion space B-A. It is possible to perform cooperative processing such as displaying an image on a display.

  When the general user U2 of the space B who is not the administrator (user) of the space A logs in to the fusion space B-A, the login is the same as the above (b), and the service of the space B (before the fusion) is general. It can be used with user authority, and the service in space A can be used with guest authority.

  In addition, before the space A and the space B are merged, the administrator U1 logs in to the space A. After that, when the space A and the space B merge, U1 can only enter the space A with the administrator authority of the space A. When logged in, U1 can use the administrator authority for the service in space A, but can use the service in space B (before fusion) only with the guest authority. However, if U1 is logged in with administrator authority of space A and general user authority of space B in advance, the service of space B (before fusion) can also be used with general user authority.

FIG. 13 shows a process for requesting a service list of the merged space B-A by a general user in the space B at the time of space merge. When the user of the space B makes a service list acquisition request to the space management server SS-B of the fusion space B-A (space B) (1: service list acquisition request), the space management server SS-B Service list acquisition is performed for the integrated service directory ISD in space B and the integrated service directory ISD in space A (1.1: service list acquisition, 1.2: service list acquisition).
When the service list is returned from each directory ISD, the space management server SS-B combines the service list acquisition results (1.3: combine the acquisition results) and returns it to the user in the space B. Thus, from the user's point of view, the merged space B-A is recognized as a space in which the service is expanded by the space B.
Therefore, the user of the space B can use the service of the space A captured by the fusion in the same manner as the service originally provided in the space B. At this time, when viewed from the user of the space B, the presence of the space A is concealed and the service of the space A can be used. That is, the service in the space A is regarded as a part of the service in the space B.

[About spatial separation]
Spatial separation is a process for separating spaces that are joined together or fused together. For example, when the space A logs into the space B and the space A is merged with the space B, the space merged state is canceled when a logout request is made from the space A side as shown in FIG.
The logout request can be made when the cooperative service between the two spaces that have been operated by the spatial combination is terminated and such a service is not used for a while.
Further, a computer (such as a notebook PC) that constitutes one space A and can be carried enters a communicable area of another relatively large space B that is configured to be communicable wirelessly, so that the space A becomes a space. When it is merged with B, it is possible to make a logout request even when it is recognized that the notebook PC leaves the communication area outside the space B.
Even if there is no explicit logout request from the space A side as described above, space A keep alive confirmation is performed from the space B side (1: keep alive confirmation) as shown in FIG. The presence of the logged-in space A can be confirmed by obtaining a response from the side, but if there is no response from the space A for a certain period of time, the space B can be forced to separate the space A as a timeout. (2: forced separation).

  When the fusion / separation is performed, the space management server SS-B of the space B deletes the user information and service information of the separated space A, and only the services that can be used in the original space B can be used ( Consistency maintenance processing after separation). In addition, the administrator or user authority of the space A cannot log in to the space B.

  The present invention is not limited to the above embodiment, and various modifications can be made without departing from the spirit of the present invention.

It is a block diagram of space. It is a figure which shows the login to the space by a user. It is a figure which shows the login from space to space. It is a data structure figure of a key. It is a figure which shows a key ring and its utilization. It is a figure which shows capability-ring and its utilization. It is a figure which shows the login for space coupling | bonding. It is a figure which shows a space coupling | bonding state. It is a figure which shows the procedure of the login process for space coupling | bonding. It is a figure which shows the service utilization procedure at the time of space combination. It is a figure which shows the login for space fusion. It is a figure which shows a space fusion state. It is a figure which shows the service list request | requirement processing procedure at the time of space fusion. It is a figure which shows a separation process (logout). It is a figure which shows a forced separation process.

Explanation of symbols

A Service providing space B Service providing space SS Space management server

Claims (6)

A method for integrating a plurality of service providing spaces,
A space management server that manages information on services provided in the service providing space and information on users who can use the space, and logs into a space management server in another service providing space;
A plurality of service provisions characterized in that the service spaces are integrated during the log-in, and a user in one service provision space can use the service in the other service provision space within a predetermined use authority. Spatial integration method.   The login is a spatial connection that allows a user of the space management server who has logged into the space management server of another service providing space to use the service of the other service providing space within the usage authority acquired by the space management server. The method according to claim 1, wherein the log-in is for login.   3. The method according to claim 1, wherein the login is a login for space fusion that allows management of service information and user information of a space management server by a space management server of another service providing space. . A computer system for integrating multiple service provision spaces,
Each service providing space is managed by a space management server that manages information on services provided in the space and information on users who can use the space.
A space management server for managing information on services provided in the service providing space and information on users who can use the space comprises means for logging in to space management servers in other service providing spaces,
A plurality of service provisions characterized in that the service spaces are integrated during the log-in, and a user in one service provision space can use the service in the other service provision space within a predetermined use authority. Computer system for space integration. A space management server for managing space,
Means for managing information of services provided in the space;
Means for managing information of users who can use the space;
Means for a user of one service providing space to log in to a space management server of another service providing space in order to obtain a spatial integration state in which the service of the other service providing space can be used within a predetermined use authority;
A space management server characterized by comprising: A computer program for causing a computer to function as a space management server,
A function to manage information on services provided in the space,
A function to manage information on users who can use the space,
Log in to the space management server in another service providing space, integrate the spaces, and allow users in one service providing space to use the services in the other service providing space within the prescribed usage rights. function,
A computer program for causing a computer to execute.

Images