JP2003316636A - Computer resource management device and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To operate the computer resources of another user by using the name space of each user by bringing at least a part of the name space peculiar to the other user under the name space peculiar to the user. <P>SOLUTION: Name management services 10 and 20 are respectively constituted of authentication means 11 and 21, name management means 12 and 22, name space combining means 13 and 23, external service linking means 14 and 24 and automatic name operation means 15 and 25. Resource management services 30, 40 and 50 are respectively constituted of resource operation means 31, 41 and 51, resource monitoring means 32, 42 and 52 and user interface means 33, 43 and 53. The external service linking means 14 and 24 notify combining parts to each other and prepare a naming context sharing table and the name space combining means utilize it and operate external computer resources. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technique for transparently managing computer resources in a distributed environment.
In particular, it allows multiple name management services to work together. The present invention can be applied to a distributed name service, a distributed file system, and a peer-to-peer type communication service.

[0002]

2. Description of the Related Art Users are free to manage computer resources such as electronic documents related to their activities.
When a plurality of users collaborate, it is effective to share the computer resources managed by each user among the users involved in the collaborative work. Further, in some cases, not only the computer resources managed by each user, but also the public computer resources not under the control of the user, such as the computer resources in the conference room, may be temporarily shared.

As described above, the computer resource group in the shared state can be collectively treated as one computer resource. Hereinafter, the above-mentioned group of computer resources is referred to as a collaborative workshop for convenience. The collaborative work space is a computer resource, so it is managed again by name.

In single namespace management, the collaborative workplace must be located somewhere within the single namespace. This means that from the viewpoint of each user, it is necessary to always properly associate the personal computer resource that he or she has arbitrarily managed with the name corresponding to the joint workshop.

As a first problem of managing with a single namespace, related computer resources are globally dependent on a single namespace throughout the life cycle of collaboration.
It can be mentioned that there is a cost for managing the dependency.

For example, in the conventional server-centric architecture, in collaborative work, users need to upload a file to a file server designated by a predetermined URL, or place the file on a Web server and have the user access the URL. And each time the resource is updated, the user has to repeat these procedures.

[0007] A second problem of management by a single namespace is the life cycle management of the collaborative workshop itself. When moving from individual work to collaborative work, it is necessary to remap the resources under personal management to the collaborative work space. Where to set up the co-workplace and how to map it is always a question. Similarly, when the collaborative work ends and the individual work is returned to, it is necessary to remap necessary resources from the collaborative work place under personal management.

[0008] For example, in the conventional server-centric architecture, at the start of joint work, it has to be decided which file server, who sets and how to manage the file server, and once decided, it is easy to change it during joint work. is not. Also, when the operation of the file server is finished, each person must bring back the necessary files.

As a non-server-centric system, there is a distributed file system. In the distributed file system, each computer can share part of the file system with each other.

NFS (Network File System)
Distributed file systems developed by Sun Microsystems, Inc., Coda (file systems developed at Carnegie Mellon University), etc., assume a single global namespace. The former means a dependency on the DNS name space called the host name.
oda means a mapping for a single tree.

As a pioneering technology for distributed management of computer resources by a local name space, distributed OS To
There is an M (Threads on Modules) file system. In ToM's file system, different views can be assigned to different users and groups to configure a unique namespace.

The group view corresponds to the collaborative work space here. However, in order to manage the life cycle of collaboration, group view
A mechanism for managing users and groups must be added as well as a mechanism for easily creating.

Another non-server-centric method is peer-to-peer type file sharing. In peer-to-peer file sharing, the file sharing services that are connected to each other aim to share the usable files with each other, and cannot handle the resource of a joint workshop with a life cycle as a joint workshop. . For this reason, in a scene of collaborative work, only a very temporary connection can be established between users.

As another problem, the dynamic aspect of collaboration must be considered. Various resources are constantly updated in the collaborative work that is actually in progress, rather than in the archive of work results that have already been completed.
The volatility of individual resources is high, and the fluctuation of resource groups is severe. If we can not respond appropriately to such characteristics,
Collaborative work spaces are less often used, and collaborative work is stagnant and slower, or conversely, it is overutilized and overwhelmed by unnecessary resources.

Prior art related to the present invention is as follows. Note that most of the conventional techniques related to the name management mechanism aim to deal with load distribution in the entire system, name resolution in a distributed environment, and response to local changes. Therefore, there are few conventional techniques from the viewpoint of dynamic configuration of resource space in a collaborative work environment.

[JP-A-8-292910] In the method proposed in this document, a namespace for resource access reflecting the preference and intention of the access method is provided for each individual user. The system analyzes the resource name input by the user, accesses the resource predicted to best reflect the user's taste and intention, and presents it to the user. In this conventional method, namespaces are prepared according to individual users, but the namespaces are not integrated with each other.

[JP-A-11-134231] In the method proposed in this document, when exchanging personal information (electronic business card), a person who exchanges personal information in a directory managed by an individual in the past. Information is recorded, and in response to inquiries from other people, if the corresponding personal information is in your directory, it will be answered, and if there is not, it will be decentralized by inquiring to other directories. A simple directory. In this conventional method,
Without managing information in one directory,
Although each directory has a feature of communicating with each other and providing an access route to necessary information, it is focused on exchanging personal profile information and based on the history of past information exchange. It differs from the present invention in that it is taken out.

[US Pat. No. 6,078,929] The technique proposed in this document enables transparent access to resources managed by individual users via the Internet. By allowing any directory node in the file directory (namespace tree) of the computer managed by an individual to be assigned to an access point on the Internet, the resources on the Internet are as if they were managed by themselves. It enables you to manage as if you were. This conventional method makes it possible to virtually put network resources (resources on a server accessible via HTTP or FTP) in a namespace managed by an individual, and others. File sharing is not done by dynamically integrating the namespace with other users.

[US Pat. No. 6,033,479] The method proposed in this document provides a name service capable of managing both volatile objects and persistent objects in a name management service of a distributed object system. . In name resolution for hierarchically structured resource names such as domains, rather than performing name resolution while directly accessing the name servers of each domain, the name servers are indirectly referenced by referring to the naming context. While referring to the name resolution. In this conventional method, name services distributed over a network work together to specify an object, and the name spaces associated with each user are not dynamically integrated.

[US Pat. No. 5,842,214] In the method proposed in this document, a distributed file system is dynamically constructed by connecting domains as units. A logical path name and a real address are associated with each object, and a distributed file system is realized by integrating the name space of the name server that manages the logical name assigned to each domain. This conventional method constructs a virtual file system by dynamically integrating the files distributed on the network, and does not dynamically integrate the name space associated with each user.

[US Pat. No. 5,991,777] In the method proposed in this document, the name tree of the namespace of one device and the name tree of the namespace of another device are integrated to create a logical Form a namespace.
This enables consistent information access when integrating and using a plurality of devices. This conventional method integrates the namespaces when a plurality of devices are dynamically linked, and does not dynamically integrate the namespaces associated with each user.

[0022]

[Problems to be Solved by the Invention] The above-mentioned problems will be summarized here. First problem: Throughout the life cycle of collaborative work, the associated computer resources are globally dependent on a single namespace, and there is a cost to manage that dependency. Second problem: The life cycle management of the joint workshop itself is required. Third problem: Collaborative resources need to be dynamically managed and updated.

[0023] These problems are barriers to collaborative work. The present invention aims to solve the following problems from such a point. (1) Making computer resources involved in collaborative work globally independent of a single namespace. (2) The collaborative workshop itself should be able to autonomously manage the resources in the collaborative workshop.

[0024]

According to the present invention, in order to achieve the above-mentioned object, the structure as described in the claims is adopted. Here, before describing the invention in detail, the description of the claims will be supplementarily described.

In the principle aspect of the present invention, for the first problem, a resource management method of "bringing" named resources under personal management to each other according to a joint work is adopted.

To avoid problems with server-centric architectures (where you have to decide where to bring them), you should not centrally manage the resources but keep them under personal control and reference to those resources. A collaborative workshop is constructed by synthesizing between the group members.
Even in its synthesis, it does not have a centralized management mechanism. In such a management model, a mechanism for notifying and setting the compositing target parts to each other is necessary in the joint workshop.

That is, according to the first aspect of the present invention, one or more computers are connected by a network, each computer manages computer resources, and a plurality of name management services are provided on the network. In the computer system provided, the computer resource management device manages the computer resources using the name management service. Then, for each of at least two linked name management services: name management means for managing and operating the correspondence between computer resources and names; the name management means and the names of other linked name management services. A name space synthesizing means for synthesizing respective parts of the correspondence relationship between the computer resources and the names managed by the managing means, and positioning them in the corresponding relationship of the respective name managing means; between the name management services to be linked External service coordinating means that cooperates with each other to set a composition target part in the name space compositing means; associates computer resources with names in cooperation with the name managing means, and further Computer resource operating means for operating computer resources in cooperation with each other; The external service coordinating means (A) of the name management service replaces the composition target part of the name space compositing means (B) of the name management service of the above-mentioned 1 coordinating target with the service coordinating means of other name management services (coordinating target) C), and the corresponding composition target portion notified from the service cooperation means (C) of the other name management service to be linked, the name space composition means (B) of the name management service to be linked (1). Perform the procedure to set to.

In this structure, the plurality of affiliated name management services notify each other of the composite parts to be brought into the mutual namespace by the external service linking means, and set the composite partial space in the mutual namespace. .

From a practical point of view, control of operation authority is important in collaborative work, and an authentication mechanism and control based on it are necessary. In order not to have a centralized management mechanism, it is preferable to provide a mechanism for notifying each other of authentication information and setting each other.

That is, an authentication means for authenticating an operation subject registered in advance is further provided for each of the name management services to be linked, and the name management means and the computer resource operation means have the authentication means. The operation for the correspondence relationship between the computer resource and the name is controlled for each operation subject authenticated by, and the external service linking means (A) of the name management service of the above-mentioned 1 link is the name management service of the above-mentioned other link target. External Service Coordination Means (C)
To the authentication means, the authentication information related to the operation subject is notified to the authentication means, and the authentication information related to the operation subject notified from the external service cooperation means (C) of the other name management service to be linked is sent to the authentication means. It is preferable to execute the setting procedure.

Further, in the principle aspect of the present invention, the second aspect
For the problem of, monitor the state change of computer resources,
A mechanism for changing the correspondence between the name and the resource based on that is provided.

That is, a computer resource monitoring means for monitoring the state change of the computer resource and a name automatic operating means for changing the correspondence between the computer resource and the name based on the monitoring result of the computer resource monitoring means are provided. preferable.

According to the present invention, the dependency management cost between the related computer resources in the joint work is reduced, and the joint work becomes easier to proceed.

The cost of managing computer resources in collaborative work has decreased. For example, it is not worthwhile to justify the cost of sharing because of high volatility such as an electronic memo for writing, operation log and execution status of information equipment. It can facilitate the sharing of various new types of computer resources and bring more abundant computer resources on the co-workplace. It can be expected that this will lead to more creative collaboration.

As a side effect, the user can directly operate the computer resources related to the joint work between the related computers, so that the computer resources can be efficiently used.

As a side effect, if each user has an operation form in which he or she has a dedicated name management service, it becomes possible to share their own computer resources while keeping them within a range where the users can manage themselves. It is expected that the users themselves will be able to control the privacy of operation logs and other information, and that they will be able to use activity information that could not be collected due to psychological barriers.

In the above description, a plurality of linked name management services share a synthesis part with each other, but only one name management service shares the other name management service with its own name space. May be incorporated into.

The present invention can be realized not only as an apparatus or system, but also as a method. Further, it goes without saying that a part of such an invention can be configured as software. Further, it goes without saying that a software product used for causing a computer to execute such software is also included in the technical scope of the present invention.

The above-mentioned aspects of the present invention and the other aspects of the present invention are described in the claims and will be described in detail with reference to the following embodiments.

[0040]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below.

[Principle of the Embodiment] FIG. 1 is a conceptual diagram of the embodiment of the present invention. In this embodiment, there is one name management server 100 that manages the personal name space of user A, and there is also one or more resource management server groups 300 that operate in conjunction with this.
The resource management server group 300 cooperates with the name management server 100 to arrange computer resources on individual computers in the personal name space of the user A so that they can be operated through the name space.

As a result, the computer resources distributed to a plurality of computers owned by the user A can be placed in a state in which the computer resources can be centrally referred to by a name, and a user's unique individual name is globally independent. All user personal resources are integrated under the namespace of.

The same applies to user B. User B
One name management server 200 that manages an individual name space
Exists, and further, one or more resource management servers 400 that operate in conjunction with this exist.

Furthermore, the name management server 100 of the user A
The name management server 200 of the user B and the name management server 200 of the user B can extract a part of the namespace from each other and combine them, and can take in the resources used by the group of the user A and the user B to the namespace unique to each user. Also, user A,
Resources on a public computer that neither user B owns nor manages can be included in the management target. The resources on the public computer are managed by the management server 500.

FIG. 2 shows an example of the name space in this embodiment. The namespace is roughly composed of two types of objects, a naming context and a resource.

The naming context collects a plurality of objects and names each object. Naming context is "file folder"
It is also a generalization of "file directory" and provides an effective unit of information organization for gathering related resources. Naming contexts can be recursively combined, and hierarchical names can be constructed along the naming contexts.

A resource represents a specific resource on a computer, such as an electronic document or an execution state of an application program.

In the following, a graph composed of a naming context and resources is called a namespace.

The computer resources are, for example, electronic files stored in an external storage device (hard disk, CD-ROM, ...), a calculation process being executed, and an operating system. The running process is
For example, an application program, a program / operating system for acquiring various sensor information, and a program / operating system for controlling various external devices.

Computer resources are roughly classified into two types: a non-volatile object stored in an external storage device and a volatile object stored in the main memory and changing according to the calculation. A typical example of the former is an ordinary electronic file. The latter could be different, but could be a specific computational process running under the operating system,
It can be classified as the operating system itself. The application program is a specific calculation process, but the calculation process is responsible for the sensor information and external devices connected to the computer, the operating system is responsible, or both. For example, if the operating system is responsible, issuing a specific system call to the operating system will return sensor information or change the state of peripherals. When the calculation process is responsible, a specific service program, driver program, etc. will provide similar functions on behalf of the operating system.

In FIG. 2, there are two namespaces, which are constructed by using the naming contexts corresponding to the two roots of "namespace of user A" and "namespace of user B" as base points, respectively. B is personally configured.

In FIG. 2, the naming contexts of “/ focus activity / project A steering” of user A and “/ observer participation / meeting by Mr. A” of user B are in a state of being combined with each other. At this time, the resources gathered in the above naming contexts of the user A and the user B can be accessed by the relative name viewed from the namespace of each user. For example, “/ focused activity / project A steering / memo X” seen from user A is “/ observer participation / meeting sponsored by Mr. A / memo X” seen from user B even though they are the same entity. So they have different names.

The resources themselves involved in the joint activity are called by the same name, but the positioning of the resources differs depending on the user. In this example, user A
"Memo X" is "Project A" in "Priority Activities"
While the important meaning as "steering" is put in the name, the user B puts in the name relatively meaningless as "Meeting by Mr. A" in "Observer participation".

The present embodiment makes it possible to share computer resources in group work while organizing computer resources from the viewpoint of each individual by combining such individual namespaces.

[Device Configuration] FIG. 3 is a device configuration diagram in the present embodiment.

The name management services 10 and 20 include authentication means 11 and 21 and name management means 12 and 22, respectively.
, Name space synthesizing means 13, 23, external service linking means 14, 24, and automatic name operating means 15, 25.

Resource management service 30, 40, 50
Are resource operating means 31, 41 and 51, respectively.
It comprises resource monitoring means 32, 42, 52 and user interface means 33, 43, 53.

The name management services 10 and 20 correspond to the name management servers 100 and 200 in FIG. The resource management services 30, 40, 50 correspond to the resource management servers (group) 300, 400, 500 in FIG.

Each of the name management services 10, 20 and the resource management services 30, 40, 50 has a service I.
It has an identifier of D and is identified by this.

The service ID is a pan-system unique identifier that can be generated by each service. Various types of such identifiers are known, but in the present embodiment, a UUID (Universal Unique Ide) is used.
(ntifier) is used. The UUID is, for example, "h
http: // www. opengroup. org / o
nlinepubs / 009629399 / apdx
a. Htm ”has a detailed description. GUID (Glob
You may use ally Unique Identifier).

In the present embodiment, each service in FIG. 3 is constructed on a network-transparent distributed processing infrastructure, and it is possible to operate cooperatively across the network by referring to the other service.

Prior to the collaborative operation, it is necessary to obtain a reference to the partner service, but the infrastructure function is used for the processing. For example, as shown in FIG. 4, a bootstrap service 80 is prepared, and the location of the service is registered and inquired in the bootstrap service 80 to obtain a reference to the other service, or as shown in FIG. 5, broadcast to the network. By doing so, it is possible to use the method of notifying the other service.

[Authentication means] Next, each part will be described in detail.

The authentication means 11 and 21 perform authentication based on the authentication key with respect to the operation subject registered in advance. In this embodiment, a password is used as the authentication key, and authentication is performed by collating the password. The authentication means 11 and 21 are
It manages the data structures of FIGS. 6 and 7.

FIG. 6 is used to store the correspondence relationship between the operation subject registered in advance and the authentication key. The user ID is a pan-system unique identifier, and UUID is used in the present embodiment.

The authenticating means 11 and 21 start a session for the authenticated user and issue a session object which is a special object representing the session. Each session object is identified by a session ID. The session ID is a pan-system unique identifier, and in the present embodiment, the session ID is configured by combining a service ID and a session number generated by a strong random number.

The clients of the respective services 10 and 20 are
A session object is presented to each service, and each service 10, 20 checks whether the session has been authenticated by the authentication means 11, 21 and determines whether or not an operation on an object under management is possible.

FIG. 7 is used to store the session ID of the authenticated session for the above inspection.

[Name Management Means] Name Management Means 12, 22
Manages naming context objects,
Furthermore, the namespace is managed by managing the graph information of the naming context. Name management means 12, 22
Manages the data structures of FIGS. 8 and 9.

FIG. 8 is used to manage a graph of naming contexts. Each naming context is identified by an object ID. The object ID is a system-wide unique identifier, and in the present embodiment, the service ID of the service and the serial number of the object assigned when the service creates the object are combined.

The naming context has a name list and an access control list as elements. The name list is
Associate a name with a naming context or resource that the naming context has put together.

In the name list, naming contexts and resources are represented by a combination of the service ID of the service managing each object and the object ID of the object itself. The access control list specifies the operations that can be performed on the naming context for each operating subject. In the present embodiment, for the sake of simplicity of explanation, in the following, only the operation of inquiring a naming context is permitted to any operation subject including the operation subject not appearing in the access control list, and the operation subject appearing in the access control list is allowed. Has an implicit setting that all operations are possible.

FIG. 9 shows the service ID appearing in FIG. 8 and the reference relationship to the corresponding service. References are made to this table when "connecting" a service in the manner described below. The connected services are resource management services and other name management services. This allows the name management means to reach the resource managed by the external service.

The name management means 12 and 22 can inquire the object indicated by the name by executing the processing of FIG. In the process shown in FIG. 15, for hierarchically structured names, the hierarchy is descended from the top of the hierarchy of names, with the corresponding object being acquired from the query starting point.

If a correspondence relationship with an object exists when the name (primitive name) indicating the end of the hierarchy is reached, a reference to the object is returned.

As described with reference to FIGS. 8 and 9, the corresponding objects are not managed by the name management means 12, 22 themselves, but the other name management means 12, 22 or the resource operation means 31, 41 ,. Although it may be managed by 51, it is possible to return a reference to the object because the means of the infrastructure can cooperate with those means in a network transparent manner.

Other operations that can be performed by the name management services 10 and 20 are associating an object with a name by a name, deleting the corresponding relationship of the already associated objects, and creating a new naming context. And to associate it with other naming contexts by name.

It is possible to directly obtain the corresponding naming context by designating the object ID.

It should be noted that all the processing is executed within the range of the authority of the operation subject based on the authentication information by the authentication means.

[Namespace Composition Means] Namespace Composition Means 1
3 and 23 perform name space composition between a plurality of name management services. The namespace synthesizing means 13 and 23 manage the data structure of FIG. FIG. 10 shows another naming context that is in a shared state with the naming context represented by the object ID as a shared list. In the shared list, another naming context in the shared state is represented by a set of the service ID of the external name management service that manages the naming context and its own object ID.

The naming context group in the shared state handles not only the names associated with individual naming contexts but also the names associated with other naming contexts equally.

By executing the processing shown in FIG. 16, the name space synthesizing means 13 and 23 can inquire the object indicated by the name across other name management services in the shared state. The process of FIG. 16 calls the process of FIG. 15 as a subroutine.

In the process of FIG. 16, name resolution is performed for each naming context in the shared state based on the data structure of FIG. In this embodiment, if there is only one corresponding name, the process succeeds,
Returns a reference to the resolved object.

When duplicate names exist, conflict resolution is performed. There are various ways to resolve conflicts,
As long as it can be guaranteed that two or more objects do not correspond to a name, the specific method does not matter in the present embodiment. Just make it fail. Get the object that is directly associated with your namespace. Get the object with the most recent update time (need to add attribute fields).

[External Service Linking Means] The external service linking means 14, 24 are composed of a plurality of name management services 10, 2.
Responsible for establishing and breaking the linkage between 0s. The external service linking means 14 and 24 manage the data structure shown in FIG. 11 and update the data structure shown in FIGS. 9 and 10.

FIG. 11 is used to store an authentication key for using the external name management service as an operating entity of the name management service itself. Actually, in the present embodiment, each user owns a dedicated name management service, so the operation subject of the name management service itself is
It is represented by the owner's user ID. Of course, an operating subject having an ID different from that of the user may be used.

FIG. 12 shows the correspondence between the owned user ID and the owned user name of the external name management service. This is information used by the user interface units 33 and 43 to form a display that is easy for the user to understand, and is not related to the external service linking process.

The external service linking means 14 and 24 drive each procedure of FIGS. 19 to 23 according to each stage of linking between services.

First, the external linkage is roughly divided into two levels, that is, connection between name management services and sharing of naming context. There are four bindings between name management services: "no binding", "waiting for permission to use", "disconnecting", and "connecting".
Take a state. Naming context sharing takes four states: "no sharing", "waiting for sharing", "disconnecting", and "connecting".

First, the procedure for linking name management services will be described.

FIG. 19 shows a procedure for making a transition from the “no binding” state to the “waiting for usage permission” in coupling between name management services. Authenticated users get references to each other's name management services they want to join,
Issue "Name Management Service Registration". In response to this request, the external service linking means acquires the ID from the partner service and sets it in FIG. As a result, it becomes possible to receive the notification of the external authentication key from the partner name management service.

FIG. 20 shows a procedure for making a transition from the "waiting for use permission" state to the "disconnecting" state. Authenticated users issue "name management service permission".
In response to this request, the external service linking means acquires a reference to the partner name management service, generates an external service authentication key, and notifies the partner name management service. As a result, the self name management service becomes ready for operation by the partner name management service.

FIG. 21 shows a procedure for making a transition from the "disconnecting" state to the "connecting" state. As shown in FIG. 21, in this state, the session started by the user A is not only authenticated by the name management service 10 but also confirmed by the name management service 20, so that the name management is performed by the authority of the user A. The resources of the service 20 become available, and the user A can manage both names 1
It is possible for 0 and 20 to be connected to each other. The confirmation of the session is performed by the name management service 10 on behalf of the user using the authentication key notified from the name management service 20. Along with the connection processing, the mutual name management services update FIG. 9 and hold references to each other. As a result, mutual objects can be used mutually.

Since the external authentication key has been acquired,
The state transition in the opposite direction in the connection between name management services is
All can be executed by one user, and a user who wants to leave the combined state can freely return to the non-combined state.

Next, the procedure for sharing the naming context will be described.

FIG. 22 shows a procedure for making a transition from the “no sharing” state to the “shared waiting” state. Each user simply specifies a sharer for the naming context they want to share. Actually, the service ID of the name management service managed by the sharer is set. At this time, FIG.
Is set to the service ID, and the sharing target naming context can be associated.

FIG. 23 shows a state of "connecting" from "waiting for sharing".
It is a procedure for making a transition to a state. As shown in FIG. 23, in this state, the session started by the user A is not only authenticated by the name management service 10 but also confirmed by the name management service 20, so that the name management is performed by the authority of the user A. The resources of the service 20 can be used, and the user A can share the target naming context with each other. The confirmation of the session is performed by the name management service 10 on behalf of the user using the authentication key notified from the name management service 20. Along with the sharing setting process, the mutual name management services update FIG. 10 and have mutual references. As a result, mutual naming contexts can be used mutually.

The "disconnecting" state in naming context sharing is when the name management service that manages the naming context once in the "connecting" state is in the "disconnecting" state (when there is no reference in FIG. 9). ).

Since the external authentication key has been acquired,
The state transitions in the opposite direction in naming context sharing can all be executed by one user, and a user who wants to leave the shared state can freely return to the non-shared state.

[Name Automatic Operation Means] Name automatic operation means 1
5, 25 dynamically operate the name in response to the event notification from the resource monitoring means 32, 42, 52. The automatic name operating means 15 and 25 manage the data structure shown in FIG.

FIG. 13 shows the relationship of activating a predetermined event handler when an event of a designated type arrives in the naming context indicated by the object ID. One object may be associated with multiple types of events.

FIG. 17 shows the event handler starting process. In this process, an appropriate event handler is activated with reference to FIG. As a result, the user can change the association dynamically according to the situation, such as a naming context that holds at most n latest resources and a naming context that holds at most m most frequently accessed resources. You can set a different naming context.

[Computer Resource Operating Means] The computer resource operating means 31, 41, 51 manage the computer resources on the individual computers as resource objects and make correspondence with the namespace. Furthermore, based on the authentication information,
The resource object can be directly operated from other computer resource operation means. Computer resource operating means 3
Reference numerals 1, 41 and 51 manage the data structure shown in FIG.

FIG. 14 shows computer resource operating means 31, 4
It consists of the object ID of the resource managed by 1, 51 (the configuration is the same as the naming context), the type of the resource, and the set of external references to the resource. For example, a normal file has a path name on the local file system as an external reference, and a running process has a communication channel name for inter-process communication as an external reference. As a result, the name management means and each computer resource can be associated with each other.

Computer resource operating means 31, 41, 51
Allows the authenticated operation subject to directly operate the computer resource. The authentication information is inquired to the authentication means 11, 21 or the like.

In this embodiment, the following computer resources are handled.

Electronic file: 1. The contents of electronic files can be acquired via the network. 2. Electronic file attribute values (update time, size) can be acquired via the network. Sensor: 1. The sensor value can be acquired via the network. Application program: 1. The internal status of the application program can be acquired via the network. 2. The application program can be operated via the network.

Of course, various computer resources other than the above computer resources may be used.

[Computer Resource Monitoring Means] The computer resource monitoring means 32, 42, 52 monitor the status changes of the computer resources, operate the names themselves, and notify the name automatic operation means of the event.

FIG. 18 shows computer resource monitoring means 32, 4
2, 52 is a resource monitoring process executed. In this processing, when an operation is performed on a computer resource to be monitored on the local host, a resource change event is notified to the name management service. If the resource is not yet in the computer resource inquiry table, that is, if it is a new resource, it is added to the table on the left.

Note that "monitoring" is enabled / disabled,
The "current context" is specified by the user.

In this embodiment, the following handling is performed for the appearance of a new resource.

Electronic file: Register with a local file name in the current context. Sensor: Do nothing. Application program: Register with the application program name in the current naming context.

[User Interface Means] The user needs to be authenticated before use. The user interface means 33, 43, 53 are used for login / login processing shown in FIG.
A dialog is displayed to prompt the user to enter the password.

The resource management services 30 and 40 are the name management services 10 and 2 owned and managed by the user in advance.
Although it is set to refer to 0, the setting can be changed as necessary, for example, when temporarily renting a public computer.

FIG. 24 shows the computer resource management service connection procedure at the time of login. When the user is properly authenticated, the computer resource management service is connected to the name management service, and the resource managed by the computer resource management service becomes reachable from the namespace.

FIG. 26 is a main window for providing main functions. The main window is composed of a context view, a resource view, some command buttons, and a monitoring function display / selection switch.

The context view displays the user's personal namespace in the form of a tree view. The user can add a new naming context, delete a naming context, and rename the naming context by pressing the "Create", "Delete", and "Change" buttons, respectively.

One of the naming contexts can be set as the "current context". The current context sets the one corresponding to the work the user is going to do. For example, "/
When performing work related to "Priority activity / Project A steering", the corresponding naming context is selected as the current context.

As described above, the resources operated by the user are automatically associated with the current naming context by the computer resource monitoring means 32, 42, 52, so that the resources related to the work are automatically organized and Managed. Furthermore, if the current naming context is in a shared state, it will immediately be shared in the collaborative work.

In the resource view, the resources collected in the current context are listed. The resources are a normal file named "Document 1", sensor information named "B meeting room temperature", and "Presse".
The execution state of the application named "NationApp" is available.

On the resource view, a resource operation menu pops up by a predetermined user operation. The resource operation menu describes processing for resources according to the type of each resource. For example, a normal file can be “downloaded”, and the resource management service 30 of its own and the resource operating means 41 or 51 of the resource management service 40 or 50 managing the substance of the normal file cooperate to form a network. Download the file via. In this way, the user is independent of the computer in which the file entity exists, and only needs to be aware of it in the user's personal name space.

In the main window, the user can switch valid / invalid of monitoring. As described above, this is done by the computer resource monitoring means.
Controls whether the resource operated by the user is automatically associated with the current naming context.

FIG. 27 is an external name service management window that appears when the "group setting" button is pressed from the main window. In this window, you can operate the connection status of name management services.

The name management services are connected to each other in four states of "no connection", "waiting for permission of use", "disconnecting" and "connecting". In this embodiment, since the name management service is provided for each individual user, it is represented by a user name on the user interface as shown in FIG. This window lists external name management services that have a status other than "no binding".

First, the user presses the "add registration" button and uses the dialog that appears to obtain a reference to the name management service of the other party.

The name management service can be uniquely designated by the service ID, but for the convenience of the user, the user name and service name can also be searched. However, there may be a case where a plurality of name management services exist with duplicate user names and service names, and in that case, a plurality of corresponding service ID candidates are indicated, so one is selected.

In this way, when the reference to the name management service of the other party can be obtained, the state becomes "waiting for permission for use".

The other user also performs the same process, and when the mutual registration is completed, the user presses the "use permission" button.

As a result, the name management service generates an authentication key for the partner name management service and notifies it to the partner name management service. When the other party also performs the same operation and exchanges the authentication keys with each other, both name management services can use each other's resources and enter the "disconnecting" state.

The partner name management service in the "disconnecting" state is switched to the connected state by pressing the "connect" button on the window shown in FIG. In this case, either user may do it. "Disconnect" button and "Delete registration"
The buttons perform disconnection processing and registration deletion processing, respectively. Similar to the connection processing, this processing may be performed by either user.

FIG. 28 is a naming context sharing management window that appears when the "share setting" button is pressed from the main window. This window manages the shared state of naming contexts.

As for the sharing of naming contexts, there are four states of "no sharing", "waiting for sharing", "disconnecting", and "connecting" as in the case of the connection state between the name management services. In this embodiment, since the name management service is provided for each individual user, it is represented by a user name on the user interface as shown in FIG. 28 so that the user can easily understand. In the naming context sharing setting window, users who own external naming contexts other than the "no sharing" state are listed.

The user first presses the "Add" button to add a user who shares the naming context.
The user can choose from among the owners of external name management services that are in a disconnected or connected state.

At this point, the state is "waiting for sharing". The other user also performs the same processing, and when the mutual registration is completed, the user presses the "set" button.

As a result, a dialog for specifically designating the partner naming context to be brought into a shared state with the naming context is displayed.

As a result, the naming context sharing table of the mutual name management services is updated, and the naming contexts become in a shared state with each other. This procedure may be performed by either one of the users.

The "delete" button cancels the sharing state and deletes the registration. This process is the same as shared context setting,
It can be done by one of the owners of the naming context in the shared state.

The present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit of the invention. For example, in the above description, a plurality of linked name management services share a composite part with each other, but only one name management service incorporates a part of the other name management service into its own namespace. You may The linked name management service and resource management service may be executed on a single computer. Further, it goes without saying that the operation subject may log in to the resource management server (service) from another terminal.

[0140]

As described above, according to the present invention, during the correspondence between the name managed by each operating entity by one name management service and the computer resource, each operating entity by another name management service Incorporating at least a part of the correspondence relationship between the names managed in the above and the computer resources, and thereby sharing a part of the namespace between the operating entities that use different name management services, and using this to share the computer resources Available.

[Brief description of drawings]

FIG. 1 is a conceptual diagram of an embodiment of the present invention.

FIG. 2 is a conceptual diagram of name space composition for each user in the above embodiment.

FIG. 3 is a configuration diagram showing a specific configuration of the above embodiment.

FIG. 4 is a diagram illustrating acquisition of a reference using an external reference inquiry service.

FIG. 5 is a diagram illustrating acquisition of a reference by broadcast communication.

FIG. 6 is a diagram illustrating an example of a user authentication information table used by the authentication means in FIG.

FIG. 7 shows an authenticated session used by the authentication means of FIG.
It is a figure explaining the example of a table.

8 is a diagram illustrating an example of a naming context table used by the name management means of FIG.

9 is a diagram illustrating an example of an external service inquiry table used by the name management means of FIG.

10 is a diagram illustrating an example of a naming context sharing table managed by the namespace synthesizing unit of FIG.

11 is a diagram illustrating an example of an external service authentication information table managed by the external service linking unit in FIG.

FIG. 12 is a diagram illustrating an example of an external service owner information table used by the user interface unit of FIG. 3 to display an owner user of an external name management service.

FIG. 13 is a diagram illustrating an example of a name search processing inquiry table used by the external service linking unit of FIG.

FIG. 14 is a diagram illustrating an example of a computer resource inquiry table managed by the computer resource operating means of FIG.

FIG. 15 is a flowchart illustrating an inquiry process in the personal name space of the name management means of FIG.

16 is a flowchart for explaining an inquiry process in the shared namespace of the namespace synthesizing means of FIG.

FIG. 17 is a flowchart for explaining name automatic operation processing of the name automatic operation means of FIG.

FIG. 18 is a flow chart illustrating a computer resource monitoring process of the computer resource monitoring means of FIG.

FIG. 19 is a diagram illustrating an external name management service registration procedure according to the above embodiment.

FIG. 20 is a diagram illustrating an external name management service permission procedure according to the above embodiment.

FIG. 21 is a diagram illustrating an external name management service connection procedure according to the above embodiment.

FIG. 22 is a diagram illustrating a naming context sharing registration procedure according to the above embodiment.

FIG. 23 is a diagram illustrating a naming context sharing setting procedure according to the above embodiment.

FIG. 24 is a diagram illustrating a resource management service connection procedure according to the above embodiment.

FIG. 25 is a diagram illustrating an example of a login dialog according to the above embodiment.

FIG. 26 is a diagram illustrating an example of a main window of the above-described embodiment.

FIG. 27 is a diagram illustrating an example of an external name service management window according to the above embodiment.

FIG. 28 is a diagram illustrating an example of a naming context sharing management window according to the above embodiment.

[Explanation of symbols]

10,20 Name management service 11,21 Authentication means 12,22 Name management means 13,23 Name space synthesis means 14,24 External service coordination means 40 On resource management service 15,25 Name automatic operation means 30, 40, 50 resource management service 31, 41, 51 Computer resource operating means 32, 42, 52 Computer resource monitoring means 33,43,53 User interface means 80 Bootstrap service 100,200 name management server 300,400 resource management server group 500 Public Resource Management Server

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Yasuyuki Furukawa             430 Green, Sakai, Nakai-cho, Ashigaragami-gun, Kanagawa Prefecture             Inside of Fuji Xerox Co., Ltd. (72) Inventor Masakazu Fujimoto             430 Green, Sakai, Nakai-cho, Ashigaragami-gun, Kanagawa Prefecture             Inside of Fuji Xerox Co., Ltd. F-term (reference) 5B045 BB28 BB42 EE06 GG01                 5B082 HA01

Claims (13)

[Claims] 1. A computer system in which one or more computers are connected by a network, each computer manages computer resources, and a plurality of name management services are provided on the network, the name management service is provided. A computer resource management device for managing the computer resource by using the name management means for managing and operating the correspondence relationship between the computer resource and the name for each of the at least two name management services to be linked, A name that is placed in the correspondence relationship between each of the above-mentioned name management means by synthesizing the respective parts of the correspondence relationship between the computer resources managed by the name management means and the name management means of the other linked name management service respectively. The space synthesizing means and the name management service to be linked work in cooperation with each other. External service cooperation means for setting a composition target part in the name space composition means, and the name management means in association with the computer resources to correspond to the names, and further, the name management services of the cooperation objects cooperate with each other. A computer resource operating means for operating a computer resource, wherein the external service linking means (A) of the name management service of the linking target is a namespace synthesizing means (1) of the name management service of the linking target (1). Correspondence of notifying the synthesis target part of B) to the service cooperation means (C) of the other name management service of the cooperation target and the service cooperation means (C) of the other name management service of the cooperation target. A computer resource manager characterized by executing a procedure for setting the composition target part in the namespace composition means (B) of the name management service of the above-mentioned 1 cooperation target. Apparatus. 2. The name managing service and the computer resource operating means are further provided with an authenticating means for authenticating an operation subject registered in advance for each of the name management services to be linked. The operation for the correspondence between the computer resource and the name is controlled for each operation subject authenticated by, and the external service cooperation means (A) of the name management service of the above-mentioned 1 is the name management service of the above-mentioned other cooperation. To the external service linking means (C) of the third party, and to the operating body notified from the external service linking means (C) of the other name management service to be linked. The computer resource management device according to claim 1, which executes a procedure for setting authentication information to be set in the authentication means. 3. A computer resource monitoring means for monitoring a change in the status of a computer resource, and an automatic name operating means for changing a correspondence relationship between a computer resource and a name based on a monitoring result of the computer resource monitoring means. The computer resource management device according to item 1 or 2. 4. A computer resource operating means of each computer can handle an electronic file on a storage device of each computer, and
4. The computer resource management device according to claim 1, 2 or 3, which transfers the contents of the electronic file in response to a request from another computer resource operating means. 5. The computer resource management device according to claim 3, wherein the computer resource monitoring means can handle an electronic file on a storage device of each computer and operates the correspondence relationship between the electronic file and the name on the name management means. . 6. A computer resource operating means of each computer can handle a program executed on a storage device of each computer, and transfer the state of the program in response to a request from another computer resource operating means, and The computer resource management apparatus according to claim 1, 2 or 3, which operates the status of. 7. The computer resource management according to claim 3, wherein said computer resource monitoring means can handle a program executed on a storage device of each computer and operate a correspondence relationship between the program and name on the name management means. apparatus. 8. The computer resource management apparatus according to claim 1, further comprising a user interface unit for receiving an input from an operation subject. 9. A computer resource management device that provides a plurality of name management services on a network and manages computer resources distributed on the network using the name management service, wherein at least two names to be linked are provided. For each management service, the name management means that manages the correspondence relationship between computer resources and names and controls the operation of the correspondence relationship for each operator, and the name management means and other linked name management services Between the name space synthesizing means that synthesizes each part of the correspondence relationship between the computer resource and the name managed by the name managing means and positions it in the corresponding relationship of each name managing means, and the name management service to be linked above External service coordinating means that cooperates with each other to set a synthesis target portion in the namespace synthesizing means, and A computer resource operating unit that associates a computer resource with a name in cooperation with the name managing unit, and further cooperates with each other between the name management services to be linked to operate the computer resource for each operating subject. A computer resource management device comprising: 10. A computer resource management apparatus which provides a plurality of name management services on a network and manages computer resources distributed on the network using the name management service, wherein at least two names to be linked are provided. For each of the management services, an authentication means that authenticates the operation subject registered in advance and the correspondence relationship between the computer resource and the name are managed, and the operation of the correspondence relationship described above is performed for each operation subject authenticated by the authentication means. At least a part of the correspondence relationship between the name management means to be controlled and the name and the computer resource managed by the name management means of the other name management service to be linked, It operates under the authentication by the name space synthesizing means positioned at and the authentication means of the other name management service to be linked, External service linking means for setting in the space synthesizing means at least a part of the correspondence relationship between the computer resources managed by the name managing means of the other name management service to be linked with the name, and linking with the name managing means. A computer resource operating means for associating a computer resource with a name and further operating in cooperation with each other between the name management services to be linked with each other for each operating subject authenticated by the authenticating means with respect to the computer resource. A computer resource management device comprising: 11. A computer resource management apparatus which provides a plurality of name management services on a network and manages computer resources distributed on the network using the name management service, wherein at least one name management service is provided. On the other hand, the correspondence between the name management means that manages the correspondence between computer resources and names and controls the operation of the above correspondence for each operating entity, and the correspondence between computer resources and names managed by the name management means of other name management services. Name space composition means for locating at least a part of the relationship in the correspondence relationship of the name management means of the device main body, the name management means of the device main body and the name management means of the other name management service, and computer resources are used. And a computer resource operating means for operating the above computer resources for each operating subject. Computer resources management apparatus characterized by obtaining. 12. A computer resource management method for providing a plurality of name management services on a network and managing computer resources distributed on the network using the name management service, wherein at least two names to be linked are provided. For each management service, a name management step that manages the correspondence relationship between computer resources and names and controls the operation of the above correspondence relationship for each operator, and the name management step and other linked name management services A name space synthesis step of synthesizing each part of the correspondence relationship between the computer resource and the name managed by the name management step and positioning it in the correspondence relationship managed by each name management step; The management services cooperate with each other in the namespace synthesis step described above. The external service linking step of setting the composition target portion, the computer resource is associated with the name in cooperation with the name management step, and further, the name management services of the linking target operate in cooperation with each other as computer resources. On the other hand, a computer resource management method for operating a computer resource for each operating subject. 13. A computer program for computer resource management, wherein a plurality of name management services are provided on a network, and which manages computer resources distributed on the network using the name management service, wherein at least two links are provided. A name management step of managing a correspondence relationship between a computer resource and a name for at least one name management service of the target name management services and controlling the operation of the correspondence relationship for each operation subject; And a name to be placed in the correspondence managed by each name management step by synthesizing each part of the correspondence between the computer resource and the name managed by the name management step of the other name management service Spatial composition step and name management server External service coordination step for setting the composition target part to be composed in the name space composition step in cooperation with each other, and associating the computer resource with the name in cooperation with the name management step, A computer resource management computer program, which is used for causing a computer to execute a computer resource operation step in which target name management services cooperate with each other to operate a computer resource for each operator. .