JP2746218B2 - Resource management device and resource management method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for managing resources handled by a computer system in a network information system in which a plurality of computer systems for performing information processing are connected via a network.

[0002]

2. Description of the Related Art As one of conventional resource management methods, for example, Akihiro Uetani, "Overview of Local Area Network Ethernet", 2nd revised edition, Maruzen Co., Ltd. has a resource management method of Xerox Corporation's clearinghouse service. Is described. This clearinghouse service is a distributed database based on a resource management method for managing an arbitrary number of attributes in association with the names of resources in a distributed system.

In this clearinghouse service, attributes such as a resource type, a password, an alias, a file server name, a mailbox name, a printer name, a group, and a distribution list can be handled as attributes. However, in addition to the global name, a function to assign and handle names based on a plurality of local naming rules according to the use and needs for each user is provided for the resources of the distributed system. Not.

Further, as another resource management method, for example,
Kentaro Shimizu, Mamoru Maekawa, Comment by Ashihara, "What Comes After Distributed Operating System UNIX", Kyoritsu Shuppan, pp. 243-264 and "Computer Software", Vol. 6, no. 3 (1989), p. 1
There is a resource management method of the GALAXY operating system shown in 9-34 and the like. This is a method in which a plurality of contexts for interpreting names are provided, and the contexts are configured as a set of directories including an external name, a conversion name, and an attribute list.

This resource management method uses a hash table or Bt
The correspondence from the external name to the converted name is held and managed by a table using ree or the like. For this reason, it is possible to assign a uniform external name to the resources in the distributed system and handle them, thereby improving operability. Furthermore, since different external names can be assigned to the same resource for each context, it is possible to assign and handle multiple local names to the resources of the distributed system according to the application and needs. It is possible to provide a local namespace where possible. However, the naming and interpretation rules are the same in all contexts, so different naming conventions should be defined for each user to provide flexible local names for resource uses and needs. Cannot handle the resources of a distributed system.

As another resource management method, Doug
las E.C. Comer, Larry L .; Pet
erson, "A Model of Name R
esolution in Distributed
Systems ", Proceedings The The
6th International Conference
sense on Distributed Computing
ing Systems, (1986) pp. 523
There is a name resolution mechanism in the distributed system indicated by -530. When a client process requests a name corresponding to a given resource, the name resolution mechanism starts from an initial context in which the client process is running, and converts it into another context and a name determined there. Is repeated. By this repetition, the context is moved one after another, and finally, the final context that actually manages the resource determined according to the name requested by the client process,
Convert to a resource identifier that can be interpreted in that context.

By using this name resolution mechanism, a resource management system manages resources, names, and contexts in which the names can be interpreted, and assigns a local name that is local to each context to resources of the distributed system. The scheme can be realized. At this time, the resource management method resolves the name by operating the name on the context, and performs the resolution recursively and converts it into the final context and resource identifier. Has a function. The mechanism of this name resolution function is to parse the first name to extract the second name, and to look up the table using the second name as a key, and combine the second context with the third name. And move the process to the second context.

In the above-described resource management system, a plurality of naming rules can be introduced into the system because each context has a unique name analysis function and name conversion function.
Therefore, it is possible to prepare a plurality of contexts according to uses and needs, and to provide a local and flexible namespace for each context. However, since the name conversion function of this resource management method only converts one name to one name or a set of names, the name conversion function is not required to operate on the resource represented by the third name and the second context. It does not mention how to change the action taken from context to context. To change the operation performed on such a resource operation for each context, the name resolution mechanism may be changed for each context. However, the name resolution mechanism of the resource management method uses a common name resolution system for the entire system. Since functions are used, the behavior of resources cannot be changed for each context.

In this document, the name resolution mechanism is the first
Is extended to resolve to a set of identifiers. The name resolution mechanism is described such that the first name corresponds to multiple groups of names in different contexts, and acts to apply the same operation to multiple identifiers, for example, using broadcast communication. I have.
However, in this name resolution mechanism, an operation on the first name cannot be realized by combining different operations on a plurality of identifiers resolved by the name resolution mechanism, and a mechanism for implementing such a mechanism is mentioned. Not.

A name management system disclosed in Japanese Patent Application Laid-Open No. Hei 5-216799 discloses a name management system that automatically converts a name in one namespace to a name in another namespace while avoiding duplication of names. It is a method. This name management method is basically based on Douglas E. Comer,
Larry L. It is based on the same mechanism as Peterson's name resolution mechanism and has similar problems.

A method for connecting a large-scale distributed computer system having a hierarchical structure disclosed in Japanese Patent Laid-Open No. Hei 5-189389 is based on the identification of an object in a local namespace having a hierarchical structure and other local namespaces. Of the object identifiers constituting the object identifiers in the above. The management method of the identifier of this object is basically the same as that of Douglas described above.
E. FIG. Comer, Larry L .; Peterso
n based on the same mechanism as the name resolution mechanism and has the same problems.

An apparatus and method for a federated naming system capable of decomposing a compound name composed of names by several different naming systems disclosed in Japanese Patent Application Laid-Open No. 5-274274 is disclosed. References are made to devices and methods for resolving names. This device and method are basically based on Douglas E. Com
er, Larry L .; It has the same problems, based on the same mechanism as Peterson's name resolution mechanism, because it merely describes how disparate naming systems associate and split names and interfaces.

The name resolution apparatus disclosed in Japanese Patent Application Laid-Open No. 5-342134 is determined as a result of name resolution depending on parameter setting means for defining reliability and the degree of reliability specified by parameters. It refers to a name resolution device that automatically creates or deletes a copy of a directory and, when a copy exists, operates to resolve names to the copied directory.
This apparatus and method is essentially as described by Douglas E.
Comer, Larry L .; Based on the same mechanism as Peterson's name resolution mechanism, it simply creates a directory copy automatically based on the parameters given by the user, and if a copy exists, does not request other contexts to resolve it. Has only the same problem because it only describes a name resolution device that operates to perform name resolution.

Further, none of the above-described resource management methods mentions a mechanism for providing a context as a resource representing a group in which a part or all of a name resolvable by the context is a member. Since this mechanism is not provided, it is not possible to locally realize a group resource having a desired member by defining a context in which a member intended by the user is a resolvable name.

Further, the resource management system or the resource management system using the name service system or the name resolution mechanism described above names a resource in which a user's intention is reflected based on a different naming rule for each context. In addition, by providing local resources based on realization rules with different resource behavior for each context, local names that define the realization of resources or resource groups having the properties desired by individual users can be created. No reference is made to a resource management method that enables the realization of local resources.

In addition, by providing local resources based on realization rules in which the behavior of resources for each context is determined from the behavior of a plurality of resources, resources and resource groups having characteristics desired by individual users can be freely set. No reference is made to a resource management scheme that enables the realization of local resources with local names that can be defined in degrees.

The above-described conventional resource management system or a system employing the conventional resource management system includes: (a) managing the resource name and the physical location information of the resource in a resource management table or a resource management database; A resource management method or a system employing a resource management method for outputting physical location information of a corresponding resource from an input resource name, (b)
Multiple contexts that interpret the name of the resource and output the translated name of the resource, and a single that handles the translated name by translating the name into a single translated name over and over multiple contexts. (C) In addition to the above (b), a plurality of resources for interpreting a resource name and outputting a translated name of the resource in order to reach the context of The system is classified into either a context or a system that employs a resource management method having a unique name resolution mechanism that converts a name into a plurality of conversion names by repeating one or more times over a plurality of contexts.

In the system (a), an identifier in the system for realizing the first resource or a context for realizing the first resource is used for the first name, which is the name of the first resource. The first position considered to be the identifier of the first position is managed in association with the first position. However, it has only one naming rule or grammar and name parsing means for interpreting names throughout the distributed system. Therefore, in addition to the first name globally determined for the first resource, a plurality of different contexts are prepared according to the use of the first resource, the needs of the user, and the use time. Cannot provide a local namespace that provides local resources that operate differently for each context, in addition to different naming conventions for each context. Therefore, it is inconvenient to provide a flexible distributed system that meets various users' intentions and usage situations.

Since the system (b) has independent name analysis means for each context, a plurality of naming rules or a plurality of name interpretation grammars are introduced into the distributed system for names assigned to the first resource. Not only the first name for the first resource, but also
According to each naming convention or name interpretation grammar,
Independent second and third names can be assigned and handled for different contexts. Therefore, according to the intended use of the first resource, the needs of the user, and the timing of use,
Different contexts can be provided to provide multiple local names valid in each context.

However, in this resource management system, the name resolution mechanism for processing the converted name resulting from the name conversion is unique to the distributed system, and the processing method of the converted name is changed for each context. Does not provide a method for realizing, for each context, a local second resource having a predetermined property in addition to the first resource corresponding to the first name.

For example, it is assumed that, in the first context, a first converted name and a second context are output for the first name. Next, a predetermined process defined in the first context is performed on the first conversion name and the first resource provided in the second context, and the user is given the first name. It is conceivable to define the first name so as to locally realize a second resource derived from the first resource having the desired properties. However, this resource management method cannot provide such a function. Further, for example, in the third context, it is assumed that the first converted name and the second context are output for the second name. Next, a second predetermined process defined in a third context is performed on the first conversion name and the first resource provided in the second context, and the second name is It is also conceivable to define a third name so as to locally realize a third resource derived from a first resource having a second property desired by the user. However, such a function is not provided.

That is, in the system of (b), by providing a first context and a third context, a local name for the first resource as a first name and a third name for the context is provided. But does not provide the function of providing local realization of resources, such as second and third resources, derived from the first resource and having the properties desired by individual users. .

In the system (c), the name given to the first resource in addition to (b) is associated with another plurality of resources as a result of name resolution, but the operation on the first resource is It is possible to correspond to a plurality of same operations by broadcast-type communication typified by multicast communication for a plurality of resources resulting from the solution. Therefore, the operation on the first resource provides a function of duplicating and applying the same operation to a plurality of resources that are the solution results.

However, in this resource management method, the resource corresponding to the first name is a plurality of resources, and the processing applied to the resource represented by the first name is a result of the name resolution. As a result, it is not possible to implement different predetermined processes for a plurality of resources in a plurality of contexts, and to realize a local resource having such a property as to accumulate the results.

For example, in the system (c), the first name includes a plurality of contexts and a plurality of conversion names X, Y, and Z.
And predetermined procedures x, y, and z applied to a plurality of resources, respectively. The operation on the first name is performed by using the procedures x, y, z to convert the converted names X, Y, Z.
It is desired to provide a name resolution mechanism and a resource realization mechanism that operate on resources corresponding to each of the above and collectively realize the results. However, no such name resolution mechanism or resource realization mechanism is provided. Therefore,
The fourth resource represented by the first name has a fourth local name such that the fourth resource is realized from a plurality of resources and has a desired property by performing predetermined processing on the plurality of resources. Local resources cannot be freely realized by individual users.

In any of the systems (a), (b), and (c), the context itself operates as a group resource having, as members, a part or all of a set of names that can be resolved by the context. Since no mechanism is provided, even if the user realizes a context reflecting the user's intention by specifying a set of names that can be resolved by the context, the group resource that has some or all of the set as a member will not be configured. Can not.

Summarizing the above, according to the conventionally known resource management method, a locally managed resource can be assigned a global name and handled globally. It provides a function that gives a group a plurality of names determined for each context, and treats the group as a local name for each context. However, a resource having a different operation for each context, such as a predetermined process performed on a global resource, is defined, and a local name based on a different naming rule is assigned to each context. No function can be provided. Also, by performing different processing on each of multiple resources,
Aggregating the results does not provide the ability to treat as if a local resource with a single local name with the properties desired by individual users exists. In addition, it is not possible to provide a mechanism in which a context operates as a group resource having some or all of a set of resolvable names in its members. As a result, it is inconvenient to implement a highly flexible distributed system that provides a name space for local resource access for each user reflecting the preferences and intentions of each user's access method.

[0028]

SUMMARY OF THE INVENTION The present invention provides a highly flexible distributed system that provides a name space for local resource access for each user, reflecting the preference and intention of each user for the access method. It is an object of the present invention to provide a resource management device and a resource management method that can be embodied.

[0029]

According to a first aspect of the present invention, there is provided a resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected via a network. Context holding means having an identifier, and name resolution means, wherein the context holding means receives a resource name, which is a name given to the resource, as input, and analyzes the name of the resource name; The analysis result by the analysis means is represented by a first resource element sequence having a resource identifier inherent to a real resource previously realized in the computer system as an element and procedure information for processing the first resource element sequence. A first resource realization expression composed of a set of a certain first realization element sequence or a second resource element sequence having a set of a context identifier and a resource name as an element Name conversion means for converting the second resource element sequence into a second resource realization expression comprising a set of a second realization element sequence which is procedural information for processing the second resource element sequence; The resource name of the second resource element string included in the second resource realization expression converted by the name conversion means in the context holding means is output to the context holding means indicated by the corresponding context identifier. It is assumed that.

According to the second aspect of the present invention, in a resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected via a network, a context holding means having a context identifier, Means, and a resource realizing means, wherein the context holding means receives a resource name, which is a name given to the resource, as input, analyzes the name of the resource name, and an analysis result by the name analyzing means. Is a first resource element sequence having only resource identifiers unique to real resources previously realized in the computer system, and first information which is procedure information for processing the first resource element sequence. A first resource realization expression composed of a set of a realization element sequence or a second resource element sequence having a set of a context identifier and a resource name as elements; Name conversion means for converting into a second resource realization expression which is a set with a second realization element sequence, which is procedural information for processing the resource element sequence, wherein the name resolution means The resource name of the second resource element string included in the second resource realization expression converted by the name conversion means is output to the context holding means indicated by the corresponding context identifier, or in the context holding means. And outputs the first resource realization expression converted by the name conversion means. The resource realization means interprets a first realization element sequence included in the first resource realization expression output by the name resolution means. A resource is generated by executing the interpretation result on a real resource realized in advance corresponding to the first resource element sequence.

According to a third aspect of the present invention, in a resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected by a network, a first context holding unit having a context identifier and First context analysis means having a second context retention means, wherein the first context retention means receives a resource name, which is a name given to the resource, as input, and analyzes the name of the resource name; First name conversion means for converting an analysis result by the first name analysis means into a first resource element sequence having only resource identifiers unique to real resources previously realized in the computer system as elements; A first resource element string converted by the first name conversion means and a first information set which is a set of procedure information for processing the first resource element string; First name resolution means for converting the result into a pre-resolution result, and procedure information included in the first name resolution result converted by the first name resolution means; The first resource realizing means for executing a real resource corresponding to the second resource to generate a resource and outputting handle information for operating the resource;
Is a second name analysis means for inputting a resource name and analyzing the name of the resource name, and a result of analysis by the second name analysis means using a set of a context identifier and a resource name as an element. Second to convert to second resource element string
And outputs the resource name of the second resource element string converted by the second name conversion means to the first context holding means corresponding to a context identifier, and stores the first context. A second name resolution means for converting a handle information obtained by the means and a procedure information for processing a resource corresponding to the handle information into a second name resolution result; and a second name resolution means. A second resource realizing means for interpreting procedural information included in the converted second name resolution result and executing the interpreted result on a resource corresponding to the handle information to generate a resource. Is what you do.

According to a fourth aspect of the present invention, in a resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected by a network, a first context holding unit having a context identifier and First context analysis means for inputting a resource name, which is a name given to the resource, and analyzing the name of the resource name; First name conversion means for converting the result of analysis by the first name analysis means into a first resource element sequence having a resource identifier inherent to a real resource previously realized in the computer system as an element;
A first name resolution unit that outputs a name resolution result that is a set of the first resource element string converted by the first name conversion unit and procedure information for processing the first resource element string; The second context holding means receives the resource name as input and analyzes the name of the resource name, and the analysis result by the second name analysis means as the context identifier and the resource name. A second name conversion means for converting the set into a second resource element string having the set as an element, and the resource name of the second resource element string converted by the second name conversion means being indicated by a corresponding context identifier. A second name resolution means is provided for outputting to the first context storage means and receiving the name resolution result from the first context storage means.

According to a fifth aspect of the present invention, in a resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected by a network, a first context holding unit having a context identifier and A second context holding unit, and a resource realizing unit, wherein the first context holding unit receives a resource name, which is a name given to the resource, as input, and analyzes the name of the resource name Analyzing means for converting a result of analysis by the first name analyzing means into a first resource element sequence having only resource identifiers unique to real resources previously realized in the computer system as elements; Name conversion means, a first resource element string converted by the first name conversion means, and procedure information for processing the first resource element string First name resolution means for outputting a first name resolution result as a set, wherein the second context holding means receives a resource name as input and performs second name analysis for analyzing the name of the resource name Means, a second name conversion means for converting the result of analysis by the second name analysis means into a second resource element string having a set of a context identifier and a resource name as elements, and a second name conversion means. The resource name of the converted second resource element string is output to the first context holding unit indicated by the corresponding context identifier, and the first name resolution result received from the first context holding unit is used. A second name resolution unit configured to output a second name resolution result which is a set of a resource identifier and procedure information for processing a real resource corresponding to the resource identifier; Context Interprets the procedural information included in the second name resolution result output by the second name resolution means in the storage means, and executes the interpretation result on the realized real resource corresponding to the resource identifier. To generate resources.

According to a sixth aspect of the present invention, in the resource management method, a resource name, which is a name given to a resource, is inputted, the name of the resource is analyzed, and the result of the name analysis is entered into the resource name. Is converted into a first resource element string as an element, the name of the resource name included in the converted first resource element string is analyzed, and the result of the analysis is converted into a real resource realized in advance in the computer system. It is converted into a second resource element sequence consisting only of a unique resource identifier, procedure information for processing the converted second resource element string is obtained, and the procedure information is interpreted. A resource generated by applying the resource to the real resource corresponding to the second resource element string, obtaining handle information for operating the generated resource, obtaining procedure information for processing the resource corresponding to the handle information, The procedure information Interpret, and is characterized in that to generate another resource by applying the interpretation result to the resource corresponding to the handle information.

According to a seventh aspect of the present invention, in a resource management apparatus used in a computer system for performing information processing, a resource name, which is a name assigned to a resource in association with an attribute, is input and the name of the resource name is changed. One or more name analyzing means for performing an analysis, and a first resource having as an element a resource identifier uniquely associated with an actual resource previously realized in the computer system, wherein the result of the analysis by the name analyzing means is associated with an attribute. A first resource realization expression comprising a set of an element sequence and a first realization element sequence which is procedural information for processing the first resource element sequence, or a search expression for directly or indirectly specifying the attribute And a second resource element string having a set of a resource name and a second realization element string as procedure information for processing a resource obtained from the second resource element string. One or more name conversion means for converting to a source realization expression, name analysis means and the name based on the search expression or the input search expression included in the second resource realization expression converted by the name conversion means Selecting means for selecting a name conversion means for receiving a name analysis result from the analysis means; and a resource name of a second resource element string included in the second resource realization expression converted by the name conversion means or an input resource name Is passed to the name analyzing means selected by the selecting means.

According to an eighth aspect of the present invention, in the resource management apparatus according to the seventh aspect, the name conversion means comprises at least one name conversion information associated with the attribute, and Means for selecting the name conversion means by specifying one or more name conversion information, and further, a name conversion structure for configuring the name conversion means based on the one or more name conversion information specified by the selection means Means, and the name analysis means selected by the selection means transfers the name analysis result to the name conversion means constituted by the name conversion configuration means.

According to a ninth aspect of the present invention, in the resource management apparatus of the seventh aspect, a plurality of the name resolution means are associated with the attribute, and the selection means further includes the name resolution means. The name conversion means selected by the selection means transfers the first resource realization expression or the second resource realization expression to the name resolution means selected by the selection means. It is a feature.

According to a tenth aspect of the present invention, in the resource management device according to any one of the seventh to ninth aspects, the first realization element sequence of the first resource realization expression obtained by the name conversion means. And a resource realizing means for generating a resource based on a real resource previously realized corresponding to the first resource element sequence from the result of the interpretation.

According to an eleventh aspect of the present invention, in the resource management device according to the ninth aspect, a plurality of the resource realizing means are associated with the attribute, and the selecting means further selects the resource realizing means. Wherein the name resolution means transfers the first resource realization expression to the resource realization means selected by the selection means.

[0040]

According to the first aspect of the present invention, a plurality of context holding units each having a context identifier are provided. When a resource name is input to a certain context holding unit, the name of the input resource name is analyzed by the name analysis unit and then input to the name conversion unit. In the name conversion means, the analysis result by the name analysis means is converted into a first resource element string having a resource identifier as an element, and a first realization element string which is procedural information for processing the first resource element string. Or a second resource element string having a set of a context identifier and a resource name as elements, and procedure information for processing the second resource element string Is converted into a second resource realization expression composed of a set with a second realization element sequence, which is then output. When the output from the name conversion means is the second resource realization expression, the name resolution means outputs the resource name of the second resource element string included therein to the context holding means indicated by the corresponding context identifier. I do. In this manner, the analysis and conversion of the name by the context holding means are performed in a chained manner.

In addition, according to the second aspect of the present invention, the resource realizing means interprets the first realizing element sequence included in the first resource realizing expression output by the name resolving means, and interprets the result of the interpretation. The process is executed on the real resource corresponding to the first resource element sequence to generate a resource.

According to the third aspect of the present invention, the resource name input to the second context holding means is analyzed by the second name analyzing means, and the analysis result is converted by the second name converting means into the context identifier and the resource name. Is converted to a second resource element sequence having a set of And the second name resolution means is the second name resolution means.
Is output to the first context holding means corresponding to the context identifier. First
In the context holding means, the received resource name is
The analysis result is converted to a first resource element string having only the resource identifier as an element by the first name conversion means. Then, in the first name resolution means,
Is converted into a first name resolution result which is a set of a resource element string and a procedure information for processing the first resource element string. Is interpreted, the interpretation result is executed on the real resource corresponding to the first resource element sequence to generate a resource, and handle information for operating the generated resource is returned. The second name resolution means in the second context holding means is a set of the handle information returned from the first context holding means and the procedure information for processing the resource corresponding to the handle information. Converted to a second name resolution result, the resource realizing means interprets the procedure information included in the second name resolution result, and executes the interpretation result on the resource corresponding to the handle information to generate a resource. .

According to the fourth aspect of the present invention, the resource name input to the second context holding means is analyzed by the second name analyzing means, and the analysis result is converted by the second name converting means into the context identifier and the resource name. Is converted to a second resource element sequence having a set of And the second name resolution means is the second name resolution means.
Is output to the first context holding means indicated by the corresponding context identifier.
In the first context holding means, the received resource name is analyzed by the first name analysis means, and the analysis result is converted by the first name conversion means into a first resource element sequence having a resource identifier as an element. Then, in the first name resolution means,
Is converted to a name resolution result, which is a set of resource element sequence of
Is returned to the second name resolution means in the context holding means, and the name resolution result is output from the second name resolution means.

Further, according to the fifth aspect of the present invention, there is provided a resource realizing means, which is included in the second name resolution result output from the second name solving means in the second context holding means. It interprets the procedural information and executes the interpretation result on the real resource corresponding to the resource identifier to generate a resource.

According to the above configuration, it is possible to provide a valid local resource name in each context, and associate the procedure information with the resource name and context identifier for each context. So
Resources obtained by performing processing on a plurality of resources can be handled by local resource names. As a result, it is possible to provide a function of handling a local resource having a local name having a property desired by each user. In addition, in the configuration having the resource realizing means, by performing different processing on a plurality of resources and accumulating the results, for example, a single local name having a property desired by each user can be obtained. It is possible to provide a function of treating local resources as if they existed. These functions provide a flexible distributed system by providing a namespace for local resource access that reflects the preferences and intentions of access methods that differ for each user, group, or job, for example. To provide a resource management device.

Further, as a resource management method in such a resource management device, as in the invention according to claim 6, the name of the input resource name is analyzed, and the analysis result of the name is used as the element of the resource name. To the first resource element sequence to be executed. Further, the name of the resource name included in the converted first resource element string is analyzed, and the analysis result is converted to a second resource consisting of only a resource identifier unique to a real resource previously realized in the computer system. Convert to element sequence. On the basis of the converted second resource element sequence, procedural information for processing the second resource element sequence is obtained, the obtained procedural information is interpreted, and the interpretation result corresponds to the second resource element sequence. Generate resources by applying them to real resources. Further, handle information for operating the generated resource is obtained, and procedural information for processing the resource corresponding to the handle information is obtained,
Interpret the obtained procedure information, apply the interpretation result to the resource corresponding to the handle information, and generate another resource. Each user can obtain a virtual resource by applying the respective procedure information to a plurality of real resources by a unique local name, and can obtain a virtual resource according to the corresponding handle information. And access to virtual resources.

According to the seventh aspect of the present invention, there are provided name analysis means and name conversion means each associated with an attribute. When a search expression that directly or indirectly specifies an attribute is given to the selection unit, the name analysis unit and the name conversion unit that receives a name analysis result from the name analysis unit are selected based on the search expression. Thereby, for example, if the attribute is a context identifier, the operation is the same as the selection of the context holding unit in the first aspect. Since the attribute is not limited to the context identifier, the name analyzing means and the name converting means can be selected by various search expressions. Subsequent operations are the same as those of the first aspect. After the name of the input resource name is analyzed by the selected name analysis means, the name is input to the selected name conversion means. In the name conversion means, the analysis result by the name analysis means is converted into a first resource element string having a resource identifier as an element, and a first realization element string which is procedural information for processing the first resource element string. Is converted to a first resource realization expression consisting of
A second resource element string having a set of a search expression and a resource name as an element;
The second resource element sequence is converted into a second resource realization expression composed of a set with a second realization element sequence, which is procedural information for processing, and output. When the output from the name conversion means is the second resource realization expression, the name resolving means selects the resource name of the second resource element sequence included in the second resource realization expression by a search expression in the second resource realization expression. Output to the selected name analysis means. In this way, name analysis and conversion are performed in a chain.

According to the invention described in claim 8, the name conversion means is constituted by one or more name conversion information associated with the attribute. The selecting means specifies the name conversion information based on the search formula, and the name conversion configuring means configures the name conversion means based on the specified name conversion information. Thus, the selection means selects the name conversion means. With such a configuration, more flexible name conversion processing can be realized. Further, even if a plurality of similar name conversion means are not prepared, the name conversion means can be configured by the name conversion configuration means from the attribute, so that a more compact system can be configured.

According to the ninth aspect of the present invention, there are a plurality of name resolution means associated with attributes. Then, the selecting means selects the name solving means as well as the name analyzing means and the name converting means based on the retrieval formula. The name conversion means selected by the selection means transfers the first resource realization expression or the second resource realization expression to the name resolution means also selected by the selection means. The selected name resolution method is
When the second resource realization expression is received, the resource name of the second resource element sequence included in the second resource realization expression is output to the name analysis means selected by the selection means by the search expression in the second resource realization expression. . In this way, name analysis, conversion, and resource name delivery are performed in a chained manner.

According to a tenth aspect of the present invention, in addition to the configuration of the resource management device according to any one of the seventh to ninth aspects, a resource realizing means is provided, and A resource is generated from one resource realization expression based on a real resource.

According to an eleventh aspect of the present invention, in the resource management device of the ninth aspect, a plurality of resource realizing means are provided in association with the attributes together with the name analyzing means, the name converting means, and the name resolving means. I have. The selecting means selects the resource realizing means as well as the name analyzing means, the name converting means and the name resolving means. When the name resolution means selected by the selection means receives the first resource realization expression, it passes it to the resource realization means selected by the selection means. This generates resources.

[0052]

BEST MODE FOR CARRYING OUT THE INVENTION In each of the embodiments described below, a plurality of computer systems for performing information processing are distributed and arranged on a network, and are managed locally or globally for each individual computer system. With respect to the resources handled in the above, a resource management method that can handle resources having properties desired by individual users as resources local to individual users is shown. Each embodiment includes a description of an operation when a file system as a resource, in particular, a group or a file represented by a directory is localized for each user. Resources are not limited to files and groups in the file system. For example, the resource is SGML (ISO 8879:
Standard Generalized Mark
HTML (Hyp) which is an extension of “up Language”
It may be a hypertext document expressed by a grammar well known as er Text Markup Language.

In general, the resource management method according to the present invention provides a computer system such as a host, a memory, a file, a group, a port, a process, a user, or a database. It may be realized to handle a resource whose handle can be applied to the resource indicated by the name. For example, an operation on a file resource may be open, read, write, or close, which is a file operation, but is not limited to this. Some of these may be used, or seek may be possible.

It is assumed that the operation on the group resource is a member display, but the operation is not limited to this. It may be possible to add or delete members. The operation for HTML is HTTP (Hyper Text Transf).
er Protocol) may be possible.

The handle is, for example, a file ID obtained by opening a file in the case of a file resource, but may be a pointer to a file structure storing the attributes of the opened file. Also,
It may be a socket ID or a pointer to a socket structure to which an operation on the file can be applied. In general, anything can be used to apply an operation to a resource.

The following embodiment includes a description of a resource management method realized as a single process of a single computer system, but it is not essential to realize it as a single process. In general, the resource management system of the present invention may be realized as a plurality of processes operating by communicating with each other on a single or a plurality of computer systems.

Although the following embodiments include a procedure-oriented resource management system, it is not essential to implement them in a procedure-oriented manner. It may be realized by object orientation. In general, the resource management method of the present invention may use any realization method including procedure-oriented and object-oriented.

Further, in the following embodiments, the communication includes a resource management method realized as a message communication using a port, but it is not essential to realize the communication as a message communication using a port. In general, the resource management scheme of the present invention may be implemented using communication between any processes including remote programs, remote procedures, sockets, and shared memory.

Further, the following embodiment includes a resource management system having a cache for accessing a resource, but it is not essential to have a cache.

FIG. 1 is a block diagram showing a first embodiment of the resource management device of the present invention. In the figure, 1-1 to 1-
n is a context holding unit, 2-1 to 2-n are name analysis units, 3-1 to 3-n are name conversion units, 4 is a name resolution unit, 5
Is a resource realizing unit, 6-1 to 6-n, 7-1 to 7-n, 8 to
12 is a terminal. In the first embodiment, n context holding units from the context holding unit 1-1 to the context holding unit 1-n and one name resolution unit 4
And one resource realizing unit 5. The number of context holding units may be one, and generally, any number of context holding units may be used. Similarly, the number of name resolution units may be one or more, and may generally be composed of any number of name resolution units. Similarly, the number of resource realizing units may be one or more, and may generally be configured by any number of resource realizing units.

Each of the context holding units 1-1 to 1-n has a unique context identifier, and has terminals 6-1 to 6-n and terminals 7-1 to 7-n, respectively. . The terminals 6-1 to 6-n are input terminals of the context holding units 1-1 to 1-n, respectively. Terminal 6
In 1 to 6-n, the names of the resources are input. The terminals 7-1 to 7-n are respectively connected to the context holding unit 1-.
Output terminals 1 to 1-n. Terminals 7-1 to 7-n are
Each outputs a resource realization expression corresponding to the name of the resource input to terminals 6-1 to 6-n.

The context holding units 1-1 to 1-n
Are name analysis units 2-1 to 2-n and name conversion units 3-1 to
3-n are provided. Name analyzer 2-1
2-n analyzes the names of the resources input from the terminals 6-1 to 6-n, respectively. Also, the name conversion units 3-1 to 3-3
-N receives the results analyzed by the name analysis units 2-1 to 2-n, and converts the analysis results into the first or second resource realization expression. The first resource realization expression is composed of a set of a first resource element sequence having a resource identifier as an element and a first realization element sequence which is procedural information for processing the first resource element sequence. You. Here, the resource identifier is an identifier inherent to a real resource realized in advance in the computer system. The second resource realization expression is a second resource element sequence having a set of a context identifier and a resource name as elements, and a second realization element which is procedural information for processing the second resource element sequence. Consists of a set of columns. The converted first or second resource realization expressions are connected to terminals 7-1 to 7-1.
7-n is output to the name resolution unit 4.

The name resolution section 4 has terminals 8 to 10. The terminal 8 is an output terminal of the name resolution unit 4 and outputs the name of the resource to one of the context holding units 1-1 to 1-n. Terminal 9 is an input terminal of name resolution unit 4,
The first or second resource realization expression corresponding to the name of the resource output from the terminal 8 to the context holding units 1-1 to 1-n is input. The terminal 10 is an output terminal of the name resolution unit 4. The terminal 10 outputs a name resolution result corresponding to one of the first resource realization expressions input to the terminal 9. That is, the name resolution unit 4 is configured to execute the context holding units 1-1 to 1-1.
The first or second resource realization expression output from the terminals 7-1 to 7-n of 1-n is received from the terminal 9. At this time,
When the second resource realization expression is received, the resource name of the second resource element sequence included in the second resource realization expression is sent to the context holding unit indicated by the context identifier corresponding to the resource name. 8 to output. The first or second resource realization expression is returned to the terminal 9 from the context holding unit that outputs the resource name. In this way, a first resource realization expression is obtained by applying the context holding unit in a chain. A name resolution result corresponding to all or any of the obtained first resource realization expressions is output from the terminal 10.

The resource realizing section 5 has terminals 11 and 12. The terminal 11 is an input terminal for inputting a name resolution result output from the name resolution unit 4. The terminal 12 is an output terminal, and outputs a handle of a resource corresponding to the name resolution result output from the name resolution unit 4. By using the handle output from the terminal 12 of the resource realizing unit 5, the user can access and process a virtual resource corresponding to the input local resource name.

FIG. 2 is a block diagram showing a first specific example of the resource management device according to the first embodiment of the present invention. In the figure, the same parts as those in FIG. 21-1 to 21-n are resource holding units, 22 is a resource management unit, 23 is a communication unit, and 24 is a context management unit. The resource management device described in this specific example includes M resource holding units 21-1 to 21 -M, a resource management unit 22, and a communication unit 2.
3, a context management unit 24, N context holding units 1-1 to 1-N, a name resolution unit 4, and a resource realization unit 5.

The resource holding units 21-1 to 21-n respectively hold real resources and have a resource identifier res-1.
To res-M. The resource management unit 22 manages resources held by the resource holding units 21-1 to 21-M globally or locally in a specific computer system. The communication unit 23 performs communication between the resource management unit 22 and the context management unit 24, and communication with other computer systems.

The context management unit 24 manages the context holding units 1-1 to 1-N, and resolves names and obtains handles using the name resolution unit 4 and the resource realization unit 5. In this specific example, the context holding unit 1
-1 to 1-N context identifiers ctxt-1 to ct
xt-N and a port number which is a handle for communicating with the context holding units 1-1 to 1-N are paired and managed in a table. When performing a search, the entire table is scanned to find an entry in the table that matches the context identifier of the context holder to be searched, and a handle for communicating with the context holder having the context identifier of the context holder is searched. Realize to return. The search may use a search method known as a hash search using a hash table instead of a simple table. Here, the context management unit 24 only needs to obtain a handle for communicating with the context holding unit from the context identifier. For example, the context management unit 24 manages a character string or a number as a context identifier in association with a number as a handle identifier, and manages them. Any database may be used as long as it provides a search function using a context identifier.

The context holding units 1-1 to 1-N also have context identifiers ctxt-1 to ctxt-N, respectively.
And is composed of name analysis units 2-1 to 2-N and name conversion units 3-1 to 3-N.

The name analysis units 2-1 to 2-N can be configured to perform, for example, lexical analysis and syntax analysis of names, and output a parse tree as a name analysis result. Algorithms for lexical analysis and syntax analysis are described in, for example, A.A. V. A
ho, R .; Sethi, J. et al. D. Ullman, "C
ompliers ", Addison-WesleyP
This is described in Chapters 1 to 4 of publishing, 1986. Alternatively, all the input names may be directly output to the name conversion unit as a name analysis result. In the following description of the specific operation, description will be made assuming that it has the latter configuration.

The name conversion units 3-1 to 3-N output a resource realization expression which is a pair of a resource element sequence and a realization element sequence for the input name. As a configuration of the name conversion units 3-1 to 3 -N, for example, a set of a name, a resource element sequence, and a realization element sequence is managed as a table, and the table is subtracted from the input name to obtain the resource element sequence and the realization element sequence. It can be configured to take a sequence, generate a set of resource realization representations, and output them.

The elements of the realization element sequence of the resource realization expression generate a handle of a predetermined type of resource, receive a predetermined operation instruction from the handle of the resource, and input data from the handle of the resource. Or a procedure that can output. Furthermore, the input of the procedure is given a resource identifier given by the resource realization expression, and performs a predetermined operation on the resource determined by the resource identifier, and inputs or outputs data on the resource given by the resource identifier. It may be the name or identifier of a procedure realized by referring to the contents of a predetermined memory, changing the contents of the predetermined memory, or combining any one or a plurality of processes of arbitrary data.

FIG. 3 shows a first embodiment of the present invention.
It is explanatory drawing of an example of the correspondence table of the resource element string and resource realization expression used by the name conversion part in the specific example. In FIG. 3, name1, name2, name3, name4
4 shows a correspondence table in which the four names are used as table entries. In this table, the name name1 is the resource identifier res
-1 resource and resource identifier res-2 resource and procedure co
ncat. Similarly, the name name2 is realized by the resource of the resource identifier res-1 and the resource of the resource identifier res-3 and the procedure concat, and the name name3 is realized by the resource of the resource identifier res-1 and the procedure archive and the procedure unarchive. The name “name4” indicates that the resource identifier is realized by the resource “res-2”, the procedure “crypt”, and the procedure “decrypt”.

In the following description, the name conversion unit 3-1 converts the resource name string {res
-1, res-2} and the realization element sequence {concat}, a resource realization expression <{concat}, {res-
1, res-2}>, and the input name is the name n
If it is other than ame1, an empty resource realization expression 返 す is returned. Here, concat is the name of the procedure for performing concatenation.

The above resource realization expression <{concat},
{Res-1, res-2}> indicates that the resource for the name name1 is a resource identifier res-1 and a resource identifier res
The resources given in each of the -2 procedures concat
Means a resource obtained by giving the first argument and the second argument.

For example, the resource indicated by the resource identifiers res-1 and res-2 is a normal file, the handle is a UNIX operating system socket, and the procedure concat stores data obtained by reading and writing two files. It can be realized as a process that communicates using sockets. In this example, the procedure con
cat implements to create a socket as a handle corresponding to the resource with the name name1. Also, as a result of the name resolution being performed in response to the open instruction for the resource with the name name1, the procedure conc
At creates a handle.

In addition, when, for example, a read operation is applied to the handle generated by the procedure concat, the procedure concat concatenates the contents of the file given as the first argument and the contents of the second file. Works to read the contents. In addition, when the procedure concat applies, for example, a write operation to the handle,
Data of a predetermined number of bytes from the beginning is stored in the resource identifier re.
write to the resource with s-1 and the rest the resource identifier re
Operate to write to the resource having s-2. In this example, the contents of the two files of the argument are simply connected as the first half and the second half, but a plurality of files may be connected in any form.

FIGS. 4 to 6 are flowcharts showing an example of the operation of the procedure concat. First, S31
In, all the argument files are opened, and if the opening is successful, one socket is created. In S32, data is read into the array R as a cache for all files in order from the file of the first argument. S
At 33, a pointer P for accessing an element of the array R is initialized to point to the first element of the array R.
In step S34, the pointer Q is initialized to indicate the last element of the array R.

At S35, an operation on the socket is awaited. When the operation has been performed, in S36, the performed operation is determined, and each process is performed. If the operation on the socket is a read, a read process is performed in S37. This reading process is shown in FIG. In S51 of FIG. 5, it is determined whether or not the pointer P points to the end of the file. If the pointer P points to the end of the file, the fact that there is no data to be read is output to the socket in S52. If the pointer P is not the end of the file in S51, the data of the element of the array R indicated by the pointer P is output to the socket in S53. And FIG.
To S41.

If the operation on the socket is a write,
In S38, a writing process is performed. This writing process is shown in FIG. In S54 of FIG. 6, it is further determined whether or not the pointer P points to the end of the file. If the pointer P points to the end of the file, an empty element is provided next to the last element of the array R in S55, and the pointer P and the pointer Q point to the newly provided last element. Then, in S56, the data written from the socket is written to the element of the array indicated by the pointer P. When it is determined in S54 that the pointer P is not the end of the file, in S57,
The data written from the socket is written to the element of the array indicated by the pointer P. Then, the process proceeds to S41 of FIG.

Operation on socket is completed (closed)
Then, in S39, data is written in order from the first element of the array R, starting from the file of the first argument for each predetermined amount, and in the order of appearance in the argument,
Flush the cache. Then, in S40, all files are closed, and the process ends.

In S41, the pointer P is changed to the pointer Q
Is determined, and if they are equal, a value indicating the end of the file is set in the pointer P in S42. If they are not equal, the pointer P is set to indicate the next element in S43. Then, the process returns to S35 and the process is repeated.

In this embodiment, the handle generated by concat has been described as being capable of both reading and writing operations, but it may be realized so that only one of the handles can be performed. Also, file operations other than reading and writing may be allowed. For example,
In addition to the open processing and the close processing, a seek processing may be realized.

The name resolution unit 4 inputs the resource realization expression, and if the input resource realization expression includes a set of the context holding unit identifier and the name, the name is determined by the identifier of the context holding unit constituting the set. The names constituting the set are output to the context holding unit to obtain a second resource realization expression for the names constituting the set. Next, the obtained second
Replace the set with the resource realization representation of. In this way,
Repeatedly or recursively replace the second set with the third resource realization expression for the identifier and name pair of the context storage part included in the resource realization expression, until the resource realization expression no longer contains any context holding means identifier. ,
Further, the third set is replaced with a fourth resource realization expression..., The (n-1) th set is sequentially replaced with an nth resource realization expression, and finally does not include the identifier-name pair of the context holding means. Get name resolution result.

FIG. 7 shows a first embodiment of the present invention.
9 is a flowchart showing an example of the operation of the name resolution unit 4 in the specific example of FIG. First, in S61, a combination of a context identifier C and a name N <C; N
It is determined whether or not> is included, and if it is included, the following processes of S62 to S66 are performed. In S62, the context identifier C is input to the context manager 24, and a handle HC of the identifier C is obtained. And S
At 63, the name N is input to the obtained handle HC, and at S64, a resource realization expression RN corresponding to the name N is obtained from the handle HC. The obtained resource realization expression RN
In step S65, the processing of the name resolution unit 4 is recursively executed. In S66, the set <C;N> is replaced with the name resolution result I obtained in S65.

At S67, the resource realization expression obtained as a result of the replacement at S66 is returned as a name resolution result. If the set <C;N> is not included in S61,
That is, if there is no replacement, the resource realization expression of the argument is directly returned as the name resolution result.

Hereinafter, an example of the operation of the first specific example in the first embodiment will be described. Here, an operation in the case where a context identifier ctxt-1 is specified and a resolution request for the name name1 is issued to the communication unit 23 will be described. The communication unit 23 uses the context identifier ctxt
When the request for resolution of the name name1 at -1 is received, the context management unit 24 is
Requests to search for a context holding unit whose context identifier is ctx-1 from among the context holding units 1-1 to 1-N held and managed by.

The context management unit 24 searches for a context holding unit that holds cttxt-1 as a context identifier. As described above, the context management unit 24 manages the set of the context identifier of the context holding unit and the number of the port that is a handle for communicating with the context holding unit in a table. By referring to this table, the context identifier ctxt
-1 is held in correspondence with -1
The number of the port, which is a handle for communication, is obtained at 1. In the following description, the obtained port number may be called a handle.

Thus, the communication unit 23 inputs the name “name1” to the context management unit 24 and obtains a handle for the context holding unit 1-1. Next, using the obtained handle, the context holding unit 1-1 is requested to perform a name resolution process. The context holding unit 1-1 inputs the name name1 to the name analysis unit 2-1 and requests the name analysis unit 2-1 to analyze the name. Name n input to name analysis unit 2-1
ame1 is output to the name conversion unit 3-1 as it is.

The name conversion unit 3-1 converts the input name na
Resource element string {res-1, res-2} for me1
And a resource realization expression <{concat}, {res-1, res-2} which is a pair of the real element sequence {concat}.
> Is output and returned to the context management unit 24.

The context management unit 24 includes a name conversion unit 3-
Resource realization expression returned from 1 <{concat}, {r
es-1, res-2}> is input to the name resolution unit 4.
In this example, the resource realization expression <{concat}, @ re
Since the context identifier is not included in s-1, res-2｝>, the name resolution unit 4 returns the input resource realization expression as a name resolution result.

The resource realizing unit 5 determines that the name resolution result <$ con
cat}, {res-1, res-2}>, starts the procedure concat as a process, and executes the procedure co
handle identifier h for the handle generated by ncat
1 and outputs the handle identifier h1 to the context management unit 24. The context management unit 24 associates the name name1 with the handle h1 via the communication unit 23, and returns the handle h1 to the client that issued the resolution request for the name name1. The client uses the handle h1
Is used to perform operations such as data reading and writing.

As described above, for the name name1, the user assigns a local resource having properties equivalent to those of a fictitious file obtained by combining the files res-1 and res-2. Given the local name name1, name1 can be treated as if it were a single real file.

As described above, in the resource management device according to the first embodiment, the name conversion unit is configured to output the resource realization expression including the realization element sequence. For example, in the context holding unit 1, "nam
e1 converts res-1 and res-2 into the procedure conca
t can be set as a resource obtained by concatenation. As described above, since a resource having a property desired by the user can be locally realized, the resource management device according to the first embodiment solves the above-described problem.

Next, a second specific example according to the first embodiment of the present invention will be described. The configuration of the second specific example is the same as that of the first specific example except that the second specific example includes a second context holding unit in addition to the first specific example.
The second context holding unit has the same configuration as the context holding units 1-1 to 1-N in the configuration shown in FIG. 2 and is managed by the context management unit 24. That is, the context holding units 1-1 to 1--1 shown in FIG.
Some of the context holding units of N may be used as the second context holding units. Here, a description will be given assuming that the context holding unit 1-2 is a second context holding unit. Specifically, the name name2 is "nam
e1. Z ", and" name1. When read access is performed with Z ", the result obtained by expanding the resource having the name name1 by the predetermined compression / expansion method is read out.
An example will be described in which, when a write access is made under the name “name1.Z”, the result compressed by the predetermined compression / expansion method is written into the resource having the name “name1”.

The name analysis unit 2-2 of the context holding unit 1-2, which is the second context holding unit, analyzes the input second name name2 by lexical analysis or syntax analysis, and uses the symbol "." “Z” and name “name1”
Divided into And the name “Z” and the name “name1”
Is output to the name conversion unit 3-2.

FIG. 8 shows a second embodiment of the first embodiment of the present invention.
FIG. 18 is an explanatory diagram of an example of a correspondence table used in the name conversion unit of the second context holding unit in the specific example of FIG. The name conversion unit 2-2 has a correspondence table as shown in FIG. The correspondence table shown in FIG. 8 includes the name “Z” and the procedure compr.
a resource realization element {compress} consisting of ess,
The context identifier ctxt-1 is associated.

The name conversion unit 3-2 looks up the correspondence table shown in FIG. 8 with the name “Z” input from the name analysis unit 2-2,
The resource realizing element {compress} and the context identifier cntx-1 are obtained, and the resource realizing expression <{compr
ess}, {<ctxt-1, name1>}> is output. By this resource realization expression, the name “name1.
Z "is the local name na of the context identifier cntx-1.
It can indicate the local resource realized by the resource represented by me1 and the procedure compress.

The resource realization expression <{compress},
{<Ctx-1, name1>} is the name resolution unit 4
Passed to. The name resolution unit 4 operates in the same manner as in the first specific example. That is, it operates according to the flowchart shown in FIG. In this case, the resource realization expression has a pair of a context identifier and a name. Therefore, S6 in FIG.
Steps 2 to S66 are executed. In this process, the context holding unit 1-1 having the context identifier ctxt-1 is called, and the name name1 is resolved. For example, when the context holding unit 1-1 executes the resource realization expression <{concat},
Assuming that {res-1, res-2} is returned, {<ctx-1, name1>} in the resource realization expression is replaced with this resource realization expression, and the name resolution result of the name resolution unit 4 is <{ compress｝, ｛<｛conca
t}, {res-1, res-2}>｝> are output. Further, the resource realizing unit 5 receives the name resolution result,
Invoke procedure compress. The operation of the resource realizing unit 5 is based on the procedure concat in the first specific example described above.
Is the same as in the first specific example, except that the procedure compress is started instead of.

As described above, the user reads out the data expanded by the predetermined method for the data of the resource indicated by the name name1 at the time of reading, and reads the written data at the time of writing by the predetermined method. To a local resource having the property of writing into the data of the resource represented by the name name1
Given the local name e2, the name name2 can be treated as if it were a single real file.

As described above, in the resource management device according to the first embodiment, since a plurality of context holding units can be provided, the name nam which is a character string including the name name1
The context holding unit that can resolve e2 is named name
By resolving the portion not including “1” and resolving the rest by the context holding unit that can resolve the name “name1”, it is possible to configure so that name resolution is performed hierarchically. As a result, for example, the name “name2 is assigned to the context identifier cntx-
1 can be set as a resource obtained by compressing the name name1 by the procedure compress. In this way, resources having the properties desired by the user can be designed hierarchically and realized locally, so that the problems of the resource management method as described above can be solved. Further, in this configuration, the name resolution can be designed hierarchically, so that the name space can be easily designed, a new context holding unit can be configured to use the existing context holding unit, and the namespace can be easily reused. .

Next, a third specific example according to the first embodiment of the present invention will be described. The configuration and operation of the third specific example are substantially the same as those of the first specific example. In this specific example, an example will be described in which names are resolved by combining procedures for performing interpolation and extrapolation processing. Here, it is assumed that the name is represented by "data name-resolution". It is assumed that the resolution is a character string representing an arbitrary positive real number.

In the following description, the data name is name3 and represents image data. The resolution of this image data is 175.1. That is, the input resource name is “name3-175.1”. The resource res-1 is image data, and is assumed to be scanned and input at a resolution of 400 pixels per inch (= 25.4 mm; the same applies hereinafter). Furthermore, resources res-
2 is also image data, and the resolution is 10 per inch.
It is assumed that scan input is performed at 0 pixel.

In the third specific example, it is assumed that the context holding unit 1-3 is called. The name analysis unit 2-3 in the context holding unit 1-3 analyzes the input name by lexical analysis or syntax analysis, as in the second specific example. Here, the character string is separated into a character string on the left side and a character string on the right side of the symbol "-" instead of the delimiter "."

FIG. 9 shows a third embodiment according to the first embodiment of the present invention.
It is explanatory drawing of an example of the correspondence table used by the name conversion part in the specific example of. The name conversion unit 3-3 has, for example, a correspondence table as shown in FIG. In the correspondence table shown in FIG. 9, the resource realization element sequence interpo is associated with the name name1.
rate_300_100 and the resource element sequence res3
res2 corresponds to the name name2, and the resource realization element sequence interpolate_800_100, and the resource element sequences res4, res2 correspond to the name name3, the resource realization element sequence interpolate_400_10.
0 and resource element strings res1, res2 are registered, respectively.

The name conversion unit 3-3 receives the set of the name “name3” and the character string “175.1” representing the real number, and uses the correspondence table as shown in FIG. 9 to convert the procedure “intermediate_400_100” An identifier res-1 and a resource identifier res-2 are obtained. As a result, the name conversion unit 3-3 determines that the resource identification expression <$ in
terpolate_400_100 (175.
1)｝, res-1, res-2> are output. Here, interpolate_400_100 (175.
1) is a procedure for constructing an image having a resolution of 175.1 pixels per inch by interpolation from an image of 400 pixels per inch and 100 pixels per inch. Since the character string "175.1" representing the resolution is a character string determined from the input name, the procedure interpolate_40
Procedure interpolate as argument of 0_100
_400_100. In addition, a character string representing a resolution such as “400” or “100” in the procedure name is also stored in the procedure interpolat.
You may comprise so that it may be input into the procedure interpolate as an argument of e.

The name resolution section 4 operates in the same manner as in the first specific example. In addition, the resource realizing unit 5 executes the procedure interpo
When starting late_400_10, 1
The operation is the same as that of the resource realization unit 5 of the first specific example, except that 75.1 is input.

As described above, in the third specific example, since a part of the name is given to the procedure as an argument, the context holding unit can resolve an infinite number of different names. Therefore, a group having an infinite number of members or a group that handles names having continuity corresponding to real numbers approximately as members can be configured as long as the expression precision of data in the computer permits. Here, a member having a name having continuity means, for example, a name A constituted by a resolution x satisfying 100.1 <x <100.2 between A-100.1 and A-100.2. -100. It also has x as a member, which means that it can be solved.

As a result, the conventional problem that a group having an infinite number of members cannot be realized when managing a combination of names and procedures is solved. In addition, by configuring names that have the properties necessary for each user from among the names with continuity, it is possible to resolve each user by reflecting the preference and intention of each user's access method. It implements a flexible distributed system that provides a namespace for resource access, including generic group resources.

At the end of the third specific example, the procedure inter
13 shows an example of the process of portate_400_100. FIG. 10 shows the procedure interpolate_400_10
11 is a flowchart illustrating an example of a process of 0. here,
The procedure interpolate_400_100 is
“Interpolate_400_100 (Para
m1) (ARG1, ARG2) ".

At S71, the argument file ARG
1 and ARG2 are all opened, and if the opening is successful, one socket is created. In S72, data is read into the two-dimensional arrays R400 [x] [y] and R100 [X] [Y] as caches for all the files in order from the file of the first argument.

In S73 to S76, the sequence D [u]
Generate [v]. First, in S73, u = 0, v
= 0, and for u and v, every u1 and int (v * 100 / param1) for which int (u * 100 / Param1) +1 does not exceed the maximum value of X for each Param1 step
Param1) All v for which +1 does not exceed the maximum value of Y
, According to the value of Param1, S7
4-Select the calculation of D [u] [v] in S76.
Where int (x) is the integer part of x, frac (x)
Is the fractional part of x.

When 100 <Param1 <400, in step S74, D [u] [v] = (1- (Param1-100) /
(400-100)) ｛(1-frac (u * 100 /
Param1)) * (1-frac (v * 100 / Pa
ram1)) * R100 [int (u * 100 / Par
am1)] [int (v * 100 / Param1) +
1] + frac (u * 100 / Param1) * (1-
frac (v * 100 / Param1)) * R100
[Int (u * 100 / Param1) +1] [int
(V * 100 / Param1)] + (1-frac (u
* 100 / Param1) * frac (v * 100 / P
aram1) * R100 [int (u * 100 / Par
am1)] [int (v * 100 / Param1) +
1] + frac (u * 100 / Param1) * fra
c (v * 100 / Param1) * R100 [int
(U * 100 / Param1) +1] [int (v * 1
00 / Param1) +1] + (Param1-10
0) / (400-100) * ｛(1-frac (u * 4
00 / Param1)) * (1-frac (v * 400
/ Param1)) * R400 [int (u * 400 /
Param1)] [int (v * 400 / Param
1) +1] + frac (u * 400 / Param1) *
(1-frac (v * 400 / Param1)) * R4
00 [int (u * 400 / Param1) +1] [i
nt (v * 400 / Param1)] + (1-frac
(U * 400 / Param1)) * frac (v * 40
0 / Param1) * R400 [int (u * 400 /
Param1)] [int (v * 400 / Param
1) +1] + frac (u * 400 / Param1) *
frac (v * 400 / Param1) * R400 [i
nt (u * 400 / Param1) +1] [int (v
* 400 / Param1) +1] is calculated.

When Param1 ≧ 400, in step S75, D [u] [v] = (1-frac (u * 400 / Par)
am1)) * (1-frac (v * 400 / Param)
1)) * R400 [int (u * 400 / Param)
1)] [int (v * 400 / Param1) +1] +
frac (u * 400 / Param1) * (1-fra
c (v * 400 / Param1)) * R400 [int
(U * 400 / Param1) +1] [int (v * 4
00 / Param1)] + (1-frac (u * 400
/ Param1)) * frac (v * 400 / Para
m1) * R400 [int (u * 400 / Param)
1)] [int (v * 400 / Param1) +1] +
frac (u * 400 / Param1) * frac (v
* 400 / Param1) * R400 [int (u * 4
00 / Param1) +1] [int (v * 400 / P
aram1) +1] is calculated.

When 0 <Param1 ≦ 100, S76
D [u] [v] = (1-frac (u * 100 / Par)
am1)) * (1-frac (v * 100 / Param)
1)) * R100 [int (u * 100 / Param
1)] [int (v * 100 / Param1) +1] +
frac (u * 100 / Param1) * (1-fra
c (v * 100 / Param1) * R100 [int
(U * 100 / Param1) +1] [int (v * 1
00 / Param1)] + (1-frac (u * 100
/ Param1)) * frac (v * 100 / Para
m1) * R100 [int (u * 100 / Param
1)] [int (v * 100 / Param1) +1] +
frac (u * 100 / Param1) * frac (v
* 100 / Param1) * R100 [int (u * 1
00 / Param1) +1] [int (v * 100 / P
aram1) +1] is calculated.

In S77, u = 0 and v = 0, and S
At 78, an operation on the socket is awaited. In S79, it is determined what the operation is for the socket. If the operation on the socket is read, in step S80, if u exceeds the maximum value of u, u is set to 0 and v is advanced by one. If v exceeds the maximum value of v in S81, an end of file (EOF) is generated, and the process returns to S78 to repeat the processing. Further, in S82, D [u] [v] is output to the socket, and u is set to 1
Proceed. Then, the process returns to S78 to repeat the processing.

If the operation on the socket is a write,
In S83, a write-disabled error is output and the processing ends. If the operation on the socket is completed (closed), the process is terminated.

FIG. 11 is a block diagram showing a second embodiment of the resource management device of the present invention. In the figure, the same parts as those in FIG. 4-1
4-n is a name resolution unit, 5-1 to 5-n are resource realization units, 8
-1 to 8-n and 9-1 to 9-n are terminals. This second
In the second embodiment, the name resolution unit 4 and the resource realization unit 5 in the first embodiment are provided in respective context holding units. In the second embodiment, n context holding units from a context holding unit 1-1 to a context holding unit 1-n are configured. The number of context holding units may be one, and generally, any number of context holding units may be used.

Each of the context holding units 1-1 to 1-n has a unique context identifier, and has terminals 6-1 to 6-n and terminals 7-1 to 7-n, respectively. . The terminals 6-1 to 6-n are input terminals of the context holding units 1-1 to 1-n, respectively. Terminal 6
In 1 to 6-n, the names of the resources are input. The terminals 7-1 to 7-n are respectively connected to the context holding unit 1-.
Output terminals 1 to 1-n. In the second embodiment, terminals 6-1 to 7-n are respectively connected to terminals 6-1 to 7-n.
The handle of the resource corresponding to the name of the resource input to .about.6-n is output.

Further, the context holding units 1-1 to 1-n in the second embodiment include the name analyzing units 2-1 to 1-n.
2-n, name conversion units 3-1 to 3-n, and name resolution unit 4
-1 to 4-n and resource realizing units 5-1 to 5-n are provided, respectively. The name analyzers 2-1 to 2-n and the name converters 3-1 to 3-n are the same as in the first embodiment.

The name resolution units 4-1 to 4-n are connected to the terminal 8-1.
-N and terminals 9-1 to 9-n. Terminals 8-1 to 8-n are respectively connected to name resolution units 4-1 to 4-n.
Output terminals of the context holding units 1-1 to 1-n
Output the resource name to one of Terminals 9-1 to 9-
n is an input terminal of each of the name resolution units 4-1 to 4-n, and corresponds to the name of a resource output from each of the output terminals 8-1 to 8-n to the context holding units 1-1 to 1-n. Enter the handle of the resource. That is, when the resource realization expressions received from the name conversion units 3-1 to 3-n include the context identifier, the name resolution units 4-1 to 4-n hold the context indicated by the context identifier. The resource names are output from the output terminals 8-1 to 8-n to the unit, and the corresponding handles are received from the terminals 9-1 to 9-n. In this way, the context holding unit is applied in a chain until the context realization is not included in the resource realization expression. The name resolution result corresponding to all or any of the obtained resource realization expressions is stored in the resource realization unit 5.
-1 to 5-n.

The resource realizing units 5-1 to 5-n receive the name resolution results output from the name resolution units 4-1 to 4-n,
The handle of the resource corresponding to the input name resolution result is output from terminals 7-1 to 7-n. The user can use the terminals 7-1 to 7-1.
By using the handle output from 7-n,
It is possible to access and process a virtual resource corresponding to the input local resource name.

FIG. 12 is a configuration diagram showing a first specific example according to the second embodiment of the present invention. In the figure, the same parts as those in FIG. 91
Is a resource management unit, 92-1 to 92-n are resource attribute holding units,
93 is a group management unit, and 94-1 to 94-m are group attribute holding units. In this specific example, an example is given in which a local file system that reflects the user's orientation and intention is provided by providing a local group with a local name according to a correspondence table determined by each user. explain.

The local group described in this example is a local directory. The file system having a local directory includes a resource management unit 91 and a group management unit 93. In this embodiment, the resources are files and directories. The file is provided by the resource attribute holding units 92-1 to 92-n. Each of the resource attribute holding units 92-1 to 92-n holds a resource identifier that can be uniquely identified and resource data that is the content of a file. The resource identifier is a handle to which an operation on the resource can be applied. Resource attribute holding unit 92
Since the resources provided in -1 to 92-n are files, for example, file open, read, write, and close operations can be provided to the file handle.

In this specific example, the resources are managed by the resource management unit 91 globally or locally to a specific computer system. The resource management unit 91 includes n resource attribute holding units 92-
1 to 92-n and a procedure application unit (not shown), and communicates with the outside and the group management unit 93.

M group attribute holding units 94-1 to 94
-M is the context holding unit 1-1 to 1 in FIG.
-N, a group identifier-1 to m, a name analyzer 2-1 to 2-m, and a name converter 3-
1-3-m, name resolution units 4-1 to 4-m, resource realization unit 5
-1 to 5-m. Group identifier-1 to m
Corresponds to the context identifier. Each of the group attribute holding units 94-1 to 94-n is uniquely identified by the group management unit 93. Group management unit 93
Identifies the group attribute holding units 94-1 to 94-m,
Retain and manage.

The group identifiers -1 to n indicate that a group having a subset of the names resolvable by the context as members is generated from these group identifiers, and that a local group is realized. I have. Here, a procedure for acting as a group by a handle that applies an operation to the group is included. However, the present invention is not limited to this, and it may be realized such that the group identifier also serves as a handle for applying an operation to the group. For a list member applied to the handle represented by the group identifier, extract the name from the entry in the name conversion table and output a list of resolvable names, or a string based on a language representing a set of resolvable names May be realized by a group attribute holding unit.

An example of a specific operation will be described below. Here, in the file system configuring the tree structure,
An operation in the case where a local tree structure having a local name is generated and provided for each user will be described.

FIG. 13 is an explanatory diagram of a local file system. Now, consider a directory having a tree structure as shown in FIG. For example, "/ G-specific / 1G
A resource stored under the path name “/ monthly report” and “/
The resource stored under the path name "G / 2G / monthly report" is usually clearly distinguished, and cannot be handled as one resource in the conventional file system.
However, in some cases, there is a case where it is desired to treat these resources as one resource. This first
In the specific example, in such a case, an example is shown in which resources are grouped and handled.

FIG. 14 is a configuration diagram showing an example of the resource management unit in the first specific example of the second embodiment of the present invention. The resource management unit 91 corresponding to the example shown in FIG.
It is shown in FIG. Resource attribute holding units 92-1 to 92-4
Are resource identifiers “1G monthly report”, “1G plan”, “2G monthly report”, “2G patent”, and resource data DA, respectively.
TA1G monthly report, DATA1G plan, DATA2G monthly report,
He holds the DATA2G patent.

FIG. 15 is a block diagram showing an example of a group management unit in the first specific example of the second embodiment of the present invention, and FIG. 16 is an example of a correspondence table similarly held in the name conversion unit. FIG. FIG. 15 shows a group management unit 93 corresponding to the example shown in FIG. The group management unit 93 has group attribute holding units 94-0 to 94-3. The group attribute holding units 94-0 to 94-3 respectively store "/" and "G"
Other "," 1G "," 2G ", and the name resolution units 2-0 to 2-
3. Name conversion units 3-0 to 3-3, name resolution units 4-0 to 4
-3, holding the resource realizing units 5-0 to 5-3.

The name analysis units 2-0 to 2-3 are provided with the symbol "/"
When the name of a character string including the symbol “/” is input, the character string is divided into a character string on the left side of an appropriate symbol “/” and a character string on the right side including the symbol “/”.

The name conversion unit 3-1 holds a correspondence table as shown in FIG. The name is converted by referring to the correspondence table. This correspondence table outputs a group identifier “1G” when a name “1G” is input, and outputs a group identifier “2G” when a name “2G” is input.

Similarly, the name conversion unit 3-2 operates as shown in FIG.
A correspondence table as shown in FIG. 3B is held, and the name is converted by referring to the correspondence table. This correspondence table outputs a group identifier “1G monthly report” when the name “monthly report” is input, and outputs a group identifier “1G plan” when the name “plan” is input.

The name conversion unit 3-3 holds a correspondence table as shown in FIG. 16C, and performs name conversion by referring to the correspondence table. When the name “monthly report” is input, the correspondence table includes the group identifier “2G
Monthly report ", and when the name" patent "is entered,
The group identifier “2G patent” is output.

The name conversion unit 3-0 holds a correspondence table as shown in FIG. 16D, and performs name conversion by referring to this correspondence table. This correspondence table is "G
, The group identifier “G distinct” is output.

The name conversion unit in this specific example is realized to output a name resolution expression by referring to the correspondence table.
Name conversion may be performed using a hash table, an associative array, a linked list, or a relational database.
In general, the correspondence between a character string and a number may be held, and the search may be implemented using any search means.

When the user accesses the resource specified by the path name “/ G-specific / 1G / monthly report”, the group identifier “/” indicating the group attribute holding unit 94-0 and the name “/
Set generated from “G / 1G / monthly report” <“/”, “/ G
The group management unit 93 is requested to input "/ 1G / monthly report"> to the group attribute holding unit 94-0.

The name analysis unit 2-0 of the group attribute holding unit 94-0 analyzes the name "/ G / 1G / monthly report", and converts the name "G / 1G" and the remaining converted name "/ 1G / monthly report". Divided into
Parsing of names is performed depending on naming rules.
Here, it is assumed that the path name is a sequence of element names separated by the symbol “/”. Therefore, name analysis can be realized by examining the character string until the next delimiter "/" appears. In general, name parsing is performed, for example, as described in A.
V. Aho, R .; Sethi, J. et al. D. Ullman
Written, "Compilers", Addison-Wes
This may be realized by lexical analysis or syntax analysis described in chapters 1 to 4 of ley Publishing, 1986.

The name conversion unit 3-0 converts the name “G” to obtain a group identifier “G”. In addition, the conversion name “/ 1G / monthly report” output from the name analysis unit 2-0 is paired with the group identifier, and a resource element string か ら <one G><“1G / monthly report”> Output｝.

The name resolution unit 4-0 determines that the resource element string {<“G
, “/ 1G / monthly report”>｝ includes a group identifier and name set <“G distinct”, “/ 1G / monthly report”>, and thus a group attribute holding unit having a group identifier “G distinct” 94-1 is requested to resolve the name "/ 1G / monthly report".

The group attribute holding unit 94-1 combines the name analysis unit 2-1, the name conversion unit 3-1 and the name resolution unit 4-1 with the name analysis unit 2-0 and the name conversion unit 3-0. Part 4-0
Operate in the same way as. As a result, the name resolution unit 4-1
A second resource element sequence {<“1G”, “/ monthly report”>} is obtained. Since this second resource element string includes a group identifier and name set <“1G”, “/ monthly report”>, the group attribute holding unit 94 having the group identifier “1G”
-2 is requested to resolve the name “/ monthly report”.

The group attribute holding unit 94-2 includes a name analysis unit 2-2, a name conversion unit 3-2, and a name resolution unit 4-2.
Name analysis unit 2-0, name conversion unit 3-0, and name resolution unit 4-
Operate in the same way as 0. As a result, the name resolution unit 4-2
Obtains a resource element sequence {“1G monthly report”} composed of one resource identifier “1G monthly report”. Since this resource element string does not include a set of a group identifier and a name, there is no further request for a solution to another group attribute holding unit.

In the above operation, it is assumed that the resource identifier and the group identifier are distinguishable. For example, a special column for distinguishing the resource identifier may be included in the table, and if the identifier is a number or a character string, a number larger than a specific number or a character string starting with a specific alphabet is used as the resource identifier. , May be realized so as to be distinguished.

The name resolution unit 4-2 outputs the resource identifier “1G monthly report”, which is the handle of the file resource, to the resource realizing means 5-2 as a name resolution expression. In this case, since the procedure is empty, the description in the name resolution expression is omitted.

When the name resolution unit 4-2 inputs a name resolution expression including a procedure, the resource realizing means 5-2 adds a new handle so that the result of the procedure is applied to the handle of the file resource. Generate In this case, since the name resolution expression whose procedure is empty is input, the resource identifier “1G monthly report” is output as it is.

The name resolving unit 4-1 checks the group identifier “1”.
The group attribute holding unit 94-2 having “G” was requested to resolve the name “/ monthly report”. As a result of the request, the name resolution unit 4-1 receives a resource identifier "1G monthly report" which is a handle of the resource. The name resolution unit 4-1 replaces the group identifier and name pair <“1G”, “/ monthly report”> with the resource identifier “1G monthly report”, and a name resolution expression that does not include any group identifier and name pair. Get “1G monthly report”｝. The resource realizing means 5-1 is a resource realizing means 5
Similarly to -2, the name resolution expression {“1G monthly report”} is input, and the resource identifier “1G monthly report” is output as it is.

Similarly, the name resolution unit 4-0 requests the group attribute holding unit 94-1 having the group identifier "G" to resolve the name "1G / monthly report". As a result, a resource identifier "1G monthly report" which is a handle of the resource is received. The name resolving unit 4-0 converts the group identifier / name pair <“G”, “/ 1G / monthly report”> into the resource identifier “1”.
The name resolution expression {“1G monthly report”} that does not include any combination of group identifier and name is replaced with “G monthly report”. The resource realizing unit 5-0, similarly to the resource realizing unit 5-2, inputs the name resolution expression {“1G monthly report”} and outputs the resource identifier “1G monthly report” as it is.

As a result, the user obtains the resource identifier “1G monthly report” from the group attribute storage unit 94-0 as a result of resolving the name “/ G / 1G / monthly report”. Since the resource identifier “1G monthly report” is a handle of the file, the user can operate the file for the resource data DATA1G monthly report by using the resource identifier “1G monthly report”.

Next, the process of resolving the name "/ G / 1G" will be described. The name analysis unit 2-0 of the group attribute holding unit 94-0 analyzes the name “/ G / 1G” and divides the name into “G” and the remaining conversion name “/ 1G”. The name conversion unit 3-0 determines that the resource element string {<“G distinct”, “/ 1G”>}
Is output. The name resolution unit 4-0 outputs the group identifier “G
The group attribute holding unit 94-1 having “other” is requested to resolve the name “/ 1G”.

The name analysis section 2-1 of the group attribute holding section 94-1 sets the name to "1G" and the conversion name to "". The name conversion unit 3-1 converts the resource element string {<“1G”, “”>}
Is output. The name resolution unit 4-1 determines that the group identifier “1”
The group attribute holding unit 94-2 having "G" is requested to resolve the name "".

The name analysis section 2-2 of the group attribute holding section 94-2 sets the name of an empty character string and the conversion name "" of the empty character string. The name conversion unit 3-2 outputs an empty resource element sequence for an empty character string name. The name resolution unit 4-2,
Get the name resolution expression {group}.

Here, the procedure group is a procedure for making the operation of the group resource applicable. Here, the identifier of the group attribute holding unit is used as an argument, and a name resolvable by the group attribute holding unit specified by the argument is used as a member. Then, when an operation list member is applied, a handle of a group resource for outputting a list of members is generated. For example, the procedure group generates one socket as a handle of a resource group that can be handled as a directory. Next, a name list is calculated from the items of the names of all the rows in the name-resource element column correspondence table managed by the name conversion unit of the group attribute holding unit indicated by the argument. The procedure group may be different for each context, or in the case of a common member management method, the same procedure may be used for a plurality of contexts. Outputs a namelist when an operation list member is applied to a socket.

As described above, in this specific example, a procedure for realizing that a context behaves as a group resource is realized as a conversion table of a name conversion unit in combination with a local name representing a group resource. Resolves name. Thereby, each user defines a name that can be converted in the name conversion unit, thereby forming a local group having resources desired by the user as members.

Therefore, the above-mentioned specific example solves the problem that the structure of the existing filing group cannot be changed, and the local group resource for each user reflecting the preference and intention of the access method of each user. It embodies a flexible distributed system that provides a namespace for resource access with the following.

Next, a second specific example of the present invention will be described. Consider the directory having the tree structure shown in FIG. Now, in a directory having a tree structure as shown in FIG. 13 (A), for example, the resource data DAT stored under the path name “/ G-specific / 1G / monthly report”.
Considering a directory having a tree structure as shown in FIG. 13B for the A1G monthly report, "/ document-specific / monthly report / 1
It is conceivable that access is made using a local path name of “G.” In this case, a certain user may access “/ G-specific / 1G / monthly report”.
The resource accessed with the path name of "
The resources accessed by the local path name of "document / monthly report / 1G" are the same resources, only the structure of the directory is different. In this specific example, in this specific example, the local resources are different for each individual user. A directory having a simple tree structure.

Here, the first user and the second user access the same resource under different path names. For example, FIG.
In the example shown in FIG. 2, the second user is the first user “/
The resources specified by the path name "G-specific / 1G / monthly report"
Access is made with a path name of "\ Documents \ Monthly report \ 1G". Similarly, the resource specified by the path name “/ G / 1G / plan” is “{document / plan / 1G”, and the resource specified by the path name “/ G / 2G / monthly report” is The resource specified by the path name "/ G / 2G / patent" in "\ Document / monthly report 2G" is "\ Document / patent 2G".
Then, access each. For this purpose, local directories having local names to the second user, “＼”, “＼ document”, “＼document＼plan”, “と document＼monthly report”, and “＼document＼ Achieve a “patent”. Specifically, "@", "by document", "plan", "patent", and "monthly report" may be prepared as group attribute holding units.

FIG. 17 is a block diagram showing an example of a group management unit in the second specific example of the second embodiment of the present invention. FIG. 18 is an example of a correspondence table similarly held in the name conversion unit. FIG. In addition to the group attribute holding unit shown in FIG. 15, group attribute holding units 94-4 to 94-8 are added. These group attribute holding units 94-4 to
94-8 are “@” as group identifiers,
It has "by document", "monthly report", "plan", and "patent". FIG. 18 shows a correspondence table held by each of the name conversion units 3-0 to 3-8. (A) to (I) shown in the name conversion units 3-0 to 3-8 in FIG.
(A) to (I).

The name analysis units 2-4 to 2-8 use the symbol "@"
If the name of a character string containing
It operates so as to be decomposed into a character string on the right side including the character string on the left side and “＼”.

In this specific example, the group attribute holding unit that gives a name first is realized as being different between the first user and the second user, but the group attribute holding unit that gives the name first is shared, A different name may be used to access the same resource. For example, by sharing "/", the resources accessed by the path name of "/ G / 1 / G / monthly report" and the path name of "/ document / monthly report / 1G" are the same. The resources accessed by the path name of “/ G / 1G / plan” and the path name of “/ document / plan / 1G” are the same, and the path name of “/ G / 2G / monthly report” and “/ document” The resources accessed with the path name “/ monthly report / 2G” are assumed to be the same, and “/ G
The resource accessed by the path name “/ patent” and the path name “/ document / patent / 2G” may be the same.

Hereinafter, the second user is referred to as “{Monthly report by document}
FIG. 1 shows the operation when accessing with the path name “1G”.
7 and FIG. First, the second user requests the group management unit 93 to create a new group attribute holding unit. The group management unit 93
A new group attribute holding unit 94-4 is created, the group identifier is set to “$”, and the group identifier “$” is returned. Next, the group management unit 93 creates a new group attribute holding unit 94-5, sets the group identifier to “for each document”, and returns the group identifier “for each document”. In addition, a request is made to the group attribute holding unit 94-4 having the group identifier "$" to register the group identifier "by document" with the name "by document". As a result, FIG.
The correspondence table shown in (B) is created in the name conversion unit 3-4 of the group attribute holding unit 94-4. Repeat the same process,
The new group attribute holding units 94-6 to 94-8 are configured.

The name resolving unit 4-5 of the group attribute holding unit 94-5 having the group identifier "by document" is a group having the group identifiers "1G" and "2G" resolved by the group attribute holding unit 94-1. Attribute holding unit 94-
2, 94-3 calculate the elements of the union of names that can be resolved. Group attribute holding unit 94-6 newly created for the element
識別 子 94-8 are stored in the correspondence table of the name conversion unit 3-5 of the group attribute holding unit 94-5 in association with each other. Here, the calculated names are “monthly report”, “plan”, and “patent”, and the associated group attribute holding unit 94-6.
The identifiers -94-8 are "monthly report", "plan", and "patent", respectively. The correspondence table created in this way is shown in FIG. Do the same process,
A correspondence table of the name conversion units of the group attribute holding units 94-6 to 94-8 is created. These correspondence tables are shown in FIGS.
This is shown in (I).

The correspondence table is created in the following procedure in advance of the name resolution. FIGS. 19 and 20 are flowcharts showing an example of a procedure for creating a correspondence table in the second specific example of the second embodiment of this invention. First, for the group attribute holding unit 94-5, a correspondence table is created by the procedure shown in FIG. In S101, “/ G
The members (names) of all the other members are listed, and in S102, duplicates of the listed names are removed. In S103, a table having the same number of entries as the number of names is created, and each table is created. Enter a name in the first field of the row, and finally, in S104, create a new group for the name of the first field of all entries and enter its identifier in the second field. A correspondence table is created in the name conversion unit 3-5 of the attribute holding unit 94-5.

For the group attribute holding units 94-6 to 94-8, correspondence tables are created according to the procedure shown in FIG. In this case, the name is passed to ARG1. In this specific example, ARG1 is one of “monthly report”, “plan”, and “patent”.

In S111, all the groups that are members of “/ G” and have ARG1 as a member are searched, and the names in “/ G” are listed (this embodiment). A list including “1G” or “2G”). Then, in S112, a table having a number of entries equal to the number of names is created, and the name is entered in the first field of each row. Finally, S113
, For the name NAME of the first field of all entries, an identifier obtained by resolving “/ G / NAME / ARG1” with “/” is stored in the corresponding second field of the table.
Store each in the field.

As a result of such processing, the name “1” is stored in the name conversion section 3-6 of the group attribute holding section 94-6.
"G" and "2G" are "1G monthly report" and "2G monthly report" respectively.
A correspondence table for solving the problem is created. Similarly, in the name conversion unit 3-7 of the group attribute storage unit 94-7, a correspondence table for resolving the name “1G” to “1G plan” is created, and the name conversion of the group attribute storage unit 94-8 is performed. Part 3-8
, A correspondence table for resolving the name “2G” to “2G patent” is created. In this way, FIG.
The correspondence table shown in (I) is created.

In this way, the group attribute holding units 94-4 to 94-8 as shown in FIGS. 17 and 18 are created, and further stored in these name conversion units 3-4 to 3-8. A correspondence table is created.

The group management section 93 thus configured
Local filing provided by, locally realizes the directory “＼”, “＼ document”, “＼ document＼ plan”, “＼ document＼ monthly report” and “＼ document＼ patent”. I do. In contrast to the filing where the first user classifies the monthly report, plan and patent files at the group level, the second user sets the local group by local filing classified by document type. Has been realized.

The second user assigns the resource specified by the first user with the path name of “/ G / 1G / monthly report” using the group attribute holding units 94-4 to 94-8 to “＼ It can be accessed with the path name of “Document-specific {monthly report} 1G”. As described above, in the second specific example, the first user classifies the monthly report, the plan, and the patent file determined according to the group, whereas the second user classifies the local report classified according to the document type. Files can be categorized by filing that has a typical group.

More specifically, in this specific example, the directory "$ document \ monthly report" is a union of all the members of the directory of the directory "/ G" that have a specific condition. It is configured to be a member. In this case, a procedure for calculating a union of members of a group given in a plurality of contexts in advance or a procedure for removing a member that does not satisfy a predetermined condition is prepared, and these procedures are combined to maintain group attribute. The name conversion table of the unit 6 may be easily generated. Alternatively, these procedures may be executed at the time of resolving a name, and a resolution result may be obtained on demand. In this embodiment,
Although the union is calculated, the procedure for calculating the union is not limited to this. In general, any operation on a set, such as a difference set, an intersection set, a direct sum or a direct product, may be used.

As described above, in the second specific example, the file naming rules are fixed, and the naming and group hierarchies defined by the system designer, the system administrator, and the person who stores the files are used. It solves the conventional problem that access is not possible according to the naming rules set individually for each user or the group structure based on individual classification criteria, and the preferences and intentions of each user's access method This implements a highly flexible distributed system that provides a namespace for resource access, including local group resources for each user reflecting the above.

Next, a third example of the second embodiment of the present invention will be described. In the third specific example, a case will be described in which a member included in a local directory is configured as a resource having a predetermined property.
In this specific example, it is assumed that the predetermined property is that the file compressed and stored by the predetermined compression method behaves as if it were not compressed. Here, it is assumed that the resource data DATA1G monthly report, DATA1G plan, DATA2G monthly report, and DATA2G patent are each compressed and stored by a predetermined compression method.

FIG. 21 is a block diagram showing an example of a group management unit in the third specific example of the second embodiment of the present invention. FIG. 22 is an example of a correspondence table similarly held in the name conversion unit. FIG. In the third specific example, the group attribute holding units 94-2 and 94 in the first specific example described above are used.
-3 name resolution units 4-2, 4-3 and resource realization units 5-2,
5-3 is changed. In FIG. 21, a local file system is configured by newly using group attribute holding units 94-10 to 94-13. Group attribute holding unit 94-10 and group attribute holding unit 94-11
Is the group attribute holding unit 94-0 in the first specific example.
And the group attribute holding unit 94-1.

The name conversion unit 3-12 of the group attribute holding unit 94-12 obtains the name “monthly report” output from the name analysis unit 2-12, and executes the resource element string {“1G monthly report”} and the procedure “compression”. A resource realization expression <“compression / decompression”, “1G monthly report”> which is a pair with “decompression” is output.
12 outputs a similar name resolution result. Similarly, the name conversion unit 3-12 obtains the name “plan” and obtains the resource realization expression <compression / decompression ”,“ 1G plan ”, which is a set of the resource element sequence {“ 1G plan ”} and the procedure“ compression / decompression ”. Plan ">
Further, the name resolution unit 4-12 outputs a similar name resolution result. The name conversion unit 3-13 of the group attribute holding unit 94-13 has a resource element string {“2G monthly report”} and a procedure “compression / expansion” for the name “monthly report” output from the name analysis unit 2-13. , A resource realization expression <“compression / decompression”, “2G monthly report”> is output, and for the name “patent”, a resource element string {“2G total patent”}, a procedure “compression / decompression”, and a resource identifier The resource realization expression <“compression / expansion”, “2G patent”>, which is a set of “2G patent”, is output, and the name resolution unit 4-13 outputs the same name resolution result.

The name resolving unit 4-12 transmits the name resolving result including the procedure <“compression / decompression”, “1G monthly report”> to the resource realizing unit 5.
-12, a new resource identifier "compression / decompression 1G
Monthly report ". Resource identifier “Compression / decompression 1G monthly report”
Is a handle that allows file operations. When writing to this handle, the resource realizing unit 5-12 compresses the write data and sets the compressed data to be written in the resource identifier “1G monthly report”. Also, when reading from this handle,
The data is read from the resource identifier "1G monthly report", decompressed, and then set to return as read data from the handle. Such a setting is realized by, for example, realizing the handle as a pipeline of the UNIX OS,
This can be realized by implementing as a process of compressing or expanding data input from one pipeline and outputting the data to the other pipeline. In general, RPC (remote procedure call) and M
It can be realized by arbitrary inter-process communication such as the port of the ach OS.

As in the case of the above-described resource identifier “compression / expansion 1G monthly report”, the resource realizing unit 5-12 uses the name resolution expression <
A resource identifier “compression / expansion 1G plan” is generated from “compression / expansion”, “1G plan”>, and the resource realizing unit 5-13 generates a resource identifier “compression” from the name resolution expression <“compression / expansion”, “2G monthly report”>. It generates a “decompressed 2G monthly report” and extracts the resource identifier “compressed and decompressed 2G” from the name resolution expression ““ compression and decompression ”,“ 2G patent ”>
Patent ".

In the first specific example described above, when each resource data is stored in a compressed state, the first user
When accessing the "/ G-specific / 1G / monthly report", "/ G-specific / 1G / plan", "/ G-specific / 2G / monthly report", and "/ G-specific / 2G / patent", it is expanded at the time of reading. Processing must be performed individually. When storing, it is necessary to perform compression processing before storing. On the other hand, as shown in FIG. 21 and FIG.
-94-13, the third user has the second “/ G-specific / 1G / monthly report”, the second “/ G-specific / 1G / plan” and the second The user can access "/ G / G / monthly report" and the second "/ G / G / patent". At this time, the resource data DATA1G monthly report, DATA
The 1G plan, the DATA2G monthly report, and the DATA2G patent are resource data DATA1G monthly report, DATA1G which are not compressed even though they are compressed.
It can be treated as if it were a plan, a DATA2G monthly report, or a DATA2G patent.

In this specific example, the resource data DATA1G
Monthly report, DATA1G plan, DATA2G monthly report, DATA
In the 2G patent, all compression is performed using the same compression method. However, compression is not necessarily performed using the same compression method. The procedure related to compression and decompression is performed by the name conversion units 4-12 and 4-12.
13 can be managed individually in each correspondence table, so that the group attribute holding units 94-12 and 94-1
Even in the case of resource data of a different compression / expansion method for each resource that can be solved in 3 respectively, a predetermined compression / expansion method is applied and the resource can be handled.

The procedure for performing the compression / decompression processing is managed by the name conversion units 3-12 and 3-13, and the resource realization unit 5
Although it has been described that the program is actually started up at -12 and 5-13, the name conversion units 3-12 and 3-13 and the resource realization unit 5-1
Instead of being handled by 2, 5-13, it may be handled by either the group attribute holding unit 94-10 or the group attribute holding unit 94-11.

FIG. 23 is a configuration diagram showing another example of the group management unit in the third specific example of the second embodiment of the present invention. FIG. 24 is a diagram showing a correspondence table similarly held in the name conversion unit. It is explanatory drawing of another example. In this example, an example is shown in which a procedure is handled by the group attribute holding unit 94-11. In this case, “compression / decompression” may be registered as a procedure in the correspondence table held by the name conversion unit 3-11. Then, the child group attribute storage unit 94-12 or the group attribute storage unit 94-13 of the group attribute storage unit 94-11
Compression and decompression processing can be performed on an operation using the handle of the resource returned from. That is, “/ G
1G "or less partial directory, and" / G / 2
The procedure “compression / decompression” is applied to all resources included in the partial directories under G ”.

FIG. 25 is a configuration diagram showing still another example of the group management unit in the third specific example of the second embodiment of the present invention, and FIG. 26 is a correspondence table similarly held in the name conversion unit. It is explanatory drawing of another example of. In this example, an example in which a procedure is handled by the group attribute holding unit 94-10 is shown. In this case, "compression / decompression" may be registered as a procedure in the correspondence table held by the name conversion unit 3-10. Then, compression / expansion processing can be performed on the handle operation of the resource returned from the child group attribute holding unit 94-11 of the group attribute holding unit 94-10. That is, the procedure “compression / expansion” can be applied to all resources included in the directory under “/ G”.

As described above, in general, the processing of procedures handled by the group attribute holding units having a parent-child relationship in a tree structure is cascaded in series and processed in order from parent to child or from child to parent. It can be configured as follows.

In this specific example, the description has been made using the compression / expansion processing. However, the applied procedure is not limited to the compression / expansion processing.
For example, for a file that stores image data, this resource management method is applied by assigning a local name to a local resource so that it can be realized by combining procedures for converting gradation, resolution, and color space. Functions can also be provided. If it is a document, it can provide local resources in the format of the desired document editor in combination with a procedure for converting the document format.

In storing and retrieving audio and video, a resource having the property of ensuring that reading and writing are performed at a constant time interval is desired. However, since existing filings do not have such properties, reading and writing at certain time intervals are not guaranteed. In such a case, in this specific example, in addition to the conversion of the write and read cycles and the conversion of the data size of one screen or one phoneme, which is the data sampling quality, it is possible to pre-read and delay the data. By combining the procedures for handling the buffer function, it is possible to provide a function that guarantees that reading and writing can be performed at regular time intervals in the above-described writing and extracting of audio and video. For example, when reading / writing of existing filing is delayed, the data amount is increased or decreased by adaptively changing the data quality in conjunction with the free space of the buffer data accumulated by the buffer function, and always at a fixed time interval. It is also possible to configure so as to ensure reading and writing.

As described above, in the third specific example, the first
Conventionally, when a user handles compressed filing, the decompression process at the time of use and the compression process at the time of storage have to be performed individually, whereas the third user automatically performs the compression and decompression. The filing as performed can be realized and handled locally. In addition, it is possible not only to configure a local directory having the property of individually performing arbitrary processing such as compression and decompression, but also to set the members of a predetermined directory and the hierarchy of the directory in a tree structure or the like. Files that are descendants in the case of a graph structure can constitute a local directory having the property of being readable and writable by performing the same processing. Further, a file system having such a property that a plurality of processes are set in different directories and the plurality of processes are cascaded and automatically performed by stacking the directory hierarchical structure can be configured.

In the conventional filing, there is a problem that the properties of the files determined by the system provider, the system administrator and the file storage cannot be individually changed by the user. It was necessary to individually perform processing for changing the properties as needed. However, according to this specific example, since local filing can be provided in a form including a function of changing properties, as described above, a resource composed of a plurality of group attribute holding units that manage by combining names and procedures can be provided. The management method provides a namespace for local resource access for each user that reflects the preferences and intentions of each user's access method, thereby solving the conventional problems and providing a highly flexible distributed system. Has been embodied.

In particular, since the name space can be designed and configured hierarchically by a plurality of group attribute holding units, the name space can be easily designed and reused, and in this sense, a highly flexible distributed system can be used. It embodies the system.

Next, a fourth specific example according to the second embodiment of the present invention will be described. In the second specific example, the name conversion unit 3- of the group attribute holding units 94-4 to 94-8 is used.
4 to 3-8 realize a resource element sequence from a name by searching a correspondence table created in advance by a predetermined algorithm. In the fourth embodiment, instead of using a correspondence table created in advance,
When executing the name conversion, the correspondence table was created according to the method of creating the correspondence table of the name conversion units 3-4 to 3-8 of the group attribute holding units 94-4 to 94-8 described in the second embodiment. Later, a resource element sequence is generated by performing name conversion.

FIG. 27 is a configuration diagram showing an example of the group management unit in the fourth specific example of the second embodiment of the present invention. In the figure, group attribute holding units 94-10 to 94-
13 is the same as FIG. The correspondence tables held by these name conversion units 3-10 to 3-13 are the same as those shown in FIG.

The name conversion section 3-15 of the group attribute holding section 94-15 is a correspondence table of the name conversion section-5 of the group attribute holding section 94-5 shown in FIG. 18C in the second specific example. And a program for creating a similar correspondence table. The name conversion unit 3-15 performs name conversion based on the correspondence table obtained as a result of activating this program. This program is, for example, the same as the algorithm shown in FIG.

Similarly, the name conversion unit 3-16 of the group attribute storage unit 94-16, the name conversion unit 3-17 of the group attribute storage unit 94-17, and the name conversion unit 3-18 of the group attribute storage unit 94-18 Have a program for executing the algorithm as shown in FIG. 20, for example, and perform the name conversion based on the correspondence table obtained as a result of activating the program.

Here, the correspondence table is generated for all entries, but the name conversion unit may be configured to dynamically generate only a portion related to an entry necessary for resolution.

As described above, the group attribute holding unit 94
By configuring -14 to 94-18, for example,
The fourth user can realize a local group by local filing classified according to the document type, similarly to the second user described in the second specific example. With it,
The local group can realize a local group having a property in which a change in the hierarchical structure of the group due to filing handled by the first user is dynamically reflected.

For example, if the first user is “/ G-specific / 1G /
When the resource specified by the path name “weekly report” is stored, the fourth user can read “{document-specific {weekly report} 1” without re-creating the correspondence table of the group attribute holding unit 94-14.
The same document can be read and written by the path name "G".

In the conventional resource management system, since the group provided by filing is static and fixed, it is necessary to dynamically determine the members of the group and the contents of the file based on a predetermined calculation result. However, there is a problem in that the individual user must perform the calculation periodically by some means and reflect the calculation result to the group or the file.

As described above, in the fourth specific example, a local group defined by a procedure for dynamically configuring members and a local file defined by a procedure for dynamically calculating contents are stored. The system can be constructed so that names can be assigned and handled, and access can be made based on the result of invoking the procedure periodically or every time access is made. Name space for local resource access can be configured for each user reflecting the user's intention and intention, thereby solving the conventional problems and realizing a highly flexible distributed system.

In particular, in the fourth specific example, the procedure for configuring the name conversion unit so that the set of names resolved by the group attribute holding unit is dynamically determined and treating the group attribute holding unit as a group resource is described. By configuring to handle dynamically determined members, it is possible to provide group resources having dynamic members. As a result, a highly flexible distributed system is realized.

FIG. 28 is a block diagram showing a third embodiment of the resource management device of the present invention. The symbols in the figure are the same as those in FIG. 1 or FIG. The third embodiment is an example in which the name resolution unit 4 provided in common in the first embodiment is arranged in each context holding unit. Conversely, this is an example in which the name resolution units 4-1 to 4-n arranged in each context holding unit in the second embodiment are provided as a common name resolution unit 4.

The third embodiment comprises n context holding units from the context holding unit 1-1 to the context holding unit 1-n and one resource realizing unit 5. The number of context holding units may be one, and generally, any number of context holding units may be used. Similarly, the number of resource realizing units may be one or more, and may generally be configured by any number of resource realizing units.

Each of the context holding units 1-1 to 1-n has a unique context identifier, and has terminals 6-1 to 6-n and terminals 7-1 to 7-n, respectively. . The terminals 6-1 to 6-n are input terminals of the context holding units 1-1 to 1-n, respectively. Terminal 6
In 1 to 6-n, the names of the resources are input. The terminals 7-1 to 7-n are respectively connected to the context holding unit 1-.
Output terminals 1 to 1-n. Terminals 7-1 to 7-n are
Each outputs a resource name resolution result corresponding to the resource name input to the terminals 6-1 to 6-n.

The context holding units 1-1 to 1-n
Are name analysis units 2-1 to 2-n and name conversion units 3-1 to
3-n and name resolution units 4-1 to 4-n are provided. The name analyzers 2-1 to 2-n and the name converters 3-1 to 3-n are the same as those in the first and second embodiments.

The name converters 3-1 to 3-n are almost the same as those in the second embodiment, but have input terminals 9-1 to 9-n.
In n, the name resolution results of the resources corresponding to the resource names output from the output terminals 8-1 to 8-n to the context holding units 1-1 to 1-n are input. That is, each of the name resolution units 4-1 to 4-n is connected to each of the name conversion units 3-1 to 3-n
When the context identifier is included in the resource realization expression received from, the resource name is output from the output terminals 8-1 to 8-n to the context holding unit indicated by the context identifier, and the corresponding name resolution result is output. To terminals 9-1 to
9-n. In this way, the context holding unit is applied in a chain until the context realization is not included in the resource realization expression. Name resolution results corresponding to all or any of the obtained resource realization expressions are output from output terminals 7-1 to 7 of context holding units 1-1 to 1-n.
Output from -n.

Further, the resource realizing section 5 is the same as in the first embodiment. The resource realizing unit 5 includes terminals 11 and 12
have. The terminal 11 is connected to the context holding unit 1-1.
1-n output from the output terminals 7-1 to 7-n of the resource corresponding to the name are input. Terminal 12
Is an output terminal of the resource realizing unit 5, and outputs a handle of the resource corresponding to the name resolution result output from the context holding units 1-1 to 1-n.

By configuring as shown in the third embodiment, the conventional problems can be solved and flexibility can be improved in the same manner as in the above-mentioned first and second embodiments. A highly distributed system can be realized.

FIG. 29 is a configuration diagram showing a first specific example according to the third embodiment of the present invention. Reference numerals in the figure are the same as those in FIG. In the first specific example, FIG.
Corresponds to the group attribute holding unit. The first specific example does not include a resource realizing unit in the group attribute holding unit as compared with the first specific example of the above-described second embodiment. Name resolution units 4-1 to 4- in this specific example
m is the name of the group attribute holding unit represented by the identifier of the group attribute holding unit when the set of the identifier and name of the group attribute holding unit is included in the resource element sequence in the input resource realization expression. Instead of requesting the resolution and obtaining the handle of the resource represented by the name, the name resolution tree is obtained as the name resolution result represented by the name. Thereby, the group attribute holding units 94-1 to 94-m output a name resolution tree upon inputting the name. The resource realizing unit 5 inputs the name resolution tree output from the group attribute holding units 94-1 to 94-m, interprets the name resolution tree, and outputs a handle of the resource represented by the name.

FIG. 30 is an explanatory diagram of an example of a name resolution tree. FIG. 30 shows a resolution tree of a name resolution result <C1;N1> obtained as a result of resolving the name N1 by specifying the identifier C1 of the group attribute holding unit. A node represents a group attribute holding unit, and an arc represents a connection between handles. <Cx;Nx> assigned to the node
(Where x is an integer from 1 to 20) is a set of an identifier and a name of a group attribute holding unit which is a context for providing a resource corresponding to the node. Cx is an identifier of a group attribute holding unit that is a context, and Nx is a local name in a context determined by Cx. The black circles in the nodes are resource identifiers indicating resources realized in advance, and provide one handle to the parent. Label rx attached to a black circle (where x is 2, 4, 5, 9, 1
1, 12, 16, 17, 18, 19) is a resource identifier. Open circles represent resources provided locally in this example. Open circles are given by the procedure given by the context of that node. Label px attached to a white circle (where x is 1, 3, 6, 7, 8, 1
0, 13, 14, 15) is a procedure identifier.

A square in which a black or white circle is shown represents a context. When the context located at a node of the parse tree inputs a name representing the node, a context tree having the node as a root is output.

In this example, the name resolution expression is a parse tree, but it need not be a parse tree. For example, a character string representing a term may be used. Any method can be used as long as it can express the connection between the procedure and the identifier of the resource and the handle. For example, if the solution tree of <C1;N1> in FIG. 30 is expressed by a term, the solution tree of <C1;N1> = p1 (r2; p3 (p7 (r
11; r12); p8 (p13 (r16; r17));
r9); r4; r5; p6 (p10 (p14 (r1
8); p15 (r19; r20)))). In the following example, the solution tree is represented by terms.

In the first specific example of the third embodiment, each group attribute holding unit outputs based on the example described in the second specific example of the second embodiment. The term expression of the name resolution tree is shown, and the process of resolving names is described. FIG. 31 is a configuration diagram illustrating an example of the group management unit according to the first example of the third embodiment of this invention. The group management unit 93 shown in FIG.
This is almost the same as that shown in FIG. However, in this specific example, each of the group attribute holding units 94-0 to 94-8 does not have the resource realizing units 5-0 to 5-8. In the following description, it is assumed that 1 · is a procedure indicating that the handle of the argument is passed to the parent context without any processing.

FIG. 32 is an explanatory diagram showing an example of a process of resolving the name “/ G / G1 / monthly report” in the first specific example of the third embodiment of this invention. When the name “/ G / G1 / monthly report” is input to the group attribute storage unit 94-0, the name resolution unit 4-0 resolves the name “/ G1 / monthly report” to the group attribute storage unit 94-1. Is requested. further,
The name resolution unit 4-1 of the group attribute storage unit 94-1 requests the group attribute storage unit 94-2 to resolve the name "/ monthly report". The group attribute holding unit 94-2 resolves the name “/ monthly report” and outputs the name resolution result 1 (“G1 monthly report”) to the name resolution unit 4- of the group attribute holding unit 94-1.
Return to 1. Upon receiving the name resolution result, the name resolution unit 4-1 returns the name resolution result 1 · (1 · (“G1 monthly report”)) to the group attribute holding unit 94-0. The name resolution unit 4-0 of the group attribute holding unit 94-0 receives the name resolution result and sends the name resolution result 1 to the resource realization unit 5.
・ (1 ・ (1 ・ (“G1 monthly report”))) is output. The resource realizing unit 5 outputs a handle of the resource corresponding to the name resolution result.

FIG. 33 is an explanatory diagram showing an example of the process of resolving the name “/ G / G1” in the first specific example of the third embodiment of the present invention. Also in this case, the name "/ G
When "1" is input to the group attribute storage unit 94-0, the name resolution unit 4-0 requests the group attribute storage unit 94-1 to resolve the name "/ G1". 94-2 is requested to resolve the name "". At this time, in the name resolution unit 4-2 of the group attribute holding unit 94-2, since the name is an empty character string, the procedure group (G1 The name resolution unit 4-1 receives this and outputs a name resolution result 1 · (group (G1)), and the name resolution unit 4-0 outputs 1 · (1 · (group (G
1))) is output to the resource realizing unit 5.

FIG. 34 is an explanatory diagram showing an example of the process of solving the name “{document-specific} {monthly report} G1” in the first specific example of the third embodiment of this invention. Also in this case, the same as the above-described example, but the name “{document-specific} {monthly report} G1” is input to the group attribute holding unit 94-4. Then, the name resolving unit 4-4 requests the group attribute holding unit 94-5 to resolve the name “$ monthly report @ G1”, and further sends the group attribute holding unit 94-6 the name “$ G1”. Is requested. The group attribute holding unit 94-6 resolves the name “$ G1” and outputs the name resolution result 1 (“G1 monthly report”) to the name resolution unit 4--5 of the group attribute holding unit 94-5.
Return to 5. Upon receiving the name resolution result, the name resolution unit 4-5 returns the name resolution result 1 · (1 · (“G1 monthly report”)) to the group attribute holding unit 94-4. The name resolution unit 4-4 of the group attribute holding unit 94-4 receives the name resolution result and sends the name resolution result 1 to the resource realization unit 5.
・ (1 ・ (1 ・ (“G1 monthly report”))) is output. In this way, the same name resolution result as that shown in FIG. 32 can be output to the resource realizing unit 5.

Also, in the example described in the third specific example of the second embodiment, the name can be similarly resolved in the first specific example of the third embodiment. it can. Here, a configuration diagram of the group management unit in this specific example is not shown, but in FIG.
It is assumed that the configuration excludes -10 to 5-13. Hereinafter, the process of resolving names will be described for some examples.

FIG. 35 is an explanatory diagram of another example of the process of resolving the name "/ G / G1 / monthly report" in the first specific example of the third embodiment of the present invention. Name “/ G / G1 /
When the “monthly report” is input to the group attribute storage unit 94-10, the name resolution unit 4-10 sends the group report to the group attribute storage unit 94-10.
11 was asked to resolve the name "/ G1 / monthly report"
Further, it requests the group attribute holding unit 94-12 to resolve the name "/ monthly report". Group attribute holding unit 94
-12 resolves the name "/ monthly report". At this time, since the procedure “compression / expansion” is specified, the compression / expansion (“G1 monthly report”) is stored as the name resolution result in the group attribute holding unit 9
4-1 is returned to the name resolution unit 4-1. Name resolution unit 4-1
Receives the name resolution result, and receives the group attribute holding unit 94
In response to −0, the name resolution result 1 · (compression / expansion (“G1 monthly report”)) is returned. Further, the group attribute holding unit 94-0
Receives the name resolution result,
The name resolution result 1 · (1 · (compression / expansion (“G1 monthly report”))) is output to the resource realization unit 5.

Further, as a modification of the third specific example of the above-described second embodiment, the example described with reference to FIG. 23 is also different from the first specific example of the third embodiment. Similarly, name resolution can be performed. FIG.
FIG. 26 is an explanatory diagram of still another example of the process of resolving the name “/ G / G1 / monthly report” in the first specific example of the third embodiment of the present invention. Similarly to the case described above, when the name "/ G / G1 / monthly report" is input to the group attribute holding unit 94-10, the name resolution unit 4-10 sends the name "/ G1 / monthly report" to the group attribute holding unit 94-11. / G1 / monthly report "is requested, and the group attribute holding unit 94-12 is requested to resolve the name" / monthly report ". The group attribute holding unit 94-12 resolves the name “/ monthly report” and returns 1 (“G1 monthly report”) to the name resolution unit 4-1 of the group attribute holding unit 94-1 as a name resolution result. Name resolution unit 4-1
Receives the name resolution result, and receives the group attribute holding unit 94
For −0, the name is resolved. At this time, since the procedure “compression / expansion” is specified, compression / expansion (1 · (“G1 monthly report”)) is returned as the name resolution result. Further, the name resolution unit 4-0 of the group attribute holding unit 94-0
Receives the name resolution result and outputs the name resolution result 1 · (compression / decompression (1 · (“G1 monthly report”))) to the resource realization unit 5.

[0215] The resource realization expression 5 receives a name resolution tree which is a name resolution result obtained by giving a name to a context. Next, the solution tree is searched, and if the node is a leaf node representing a resource realized in advance, a handle for applying an operation to the resource is obtained from the resource identifier. Since the handle of the resource is realized in advance, it can be obtained from the identifier. For example, if the resource is a file, a port corresponding to the identifier is obtained as a result of performing the open process by specifying the identifier. In the UNIX file system, the resource identifier may be a file name or an inode number. In the case of a resource obtained by HTTP, the identifier of the resource is URL (Universal).
Resource Locator).

If the node is an intermediate node, the handle of the child node is connected to the argument port, and communication with the argument port is performed to start a procedure for performing a predetermined process. The type of procedure is determined by the label assigned to the node of the solution tree. The argument port is a port for connecting a resource handle given as an argument of a procedure determined by a label given to an intermediate node. The procedure applies a predetermined operation to the handle connected to the argument port. In addition, since the procedure creates a new handle, if this node is a non-root node, connect the new handle to the argument port of the parent node of the solution tree. If the node is a root, return the handle to the client as the handle of the resource for the given name.

A method of sequentially traversing the nodes of the name resolution tree and activating the procedure corresponding to the node is, for example, analyzing a syntax tree obtained by performing a syntax analysis when constructing a compiler. Can be realized by the same method as the method of generating the object code corresponding to each of the nodes. As a method of analyzing the syntax tree and executing an action corresponding to each node of the syntax tree, for example,
A. V. Aho, R .; Sethi, J. et al. D. Ullma
n, "Compilers", Addison-We
Syntax- described in Chapters 5 to 9 of sley Publishing, 1986.
Directed Translation Method and C
It can be realized by using the method of the mode generation.

FIG. 37 is a configuration diagram showing a second specific example according to the third embodiment of the present invention. In the figure, the same parts as those in FIG. 121
-1 to 121-4 are name analysis units, and 122-1 to 122-
4 is a name resolution unit, 123-1 to 123-4 are name change units, 124-1 to 124-4 are member output units, and 125-
1 to 125-4 are member addition units, and 126-1 to 126-
Reference numeral 4 denotes a member deleting unit, and 127-1 to 127-4 denote resource realizing units.

Each of the context holding units 1-1 to 1-4 includes:
It has context identifiers ctxt-1 to ctx-4, and has a name analyzer 121-1 to 121-4, a name resolver 122-
1-122-4, name change units 123-1 to 123-4,
Member output units 124-1 to 124-4, member addition unit 1
25-1 to 125-4, member deletion units 126-1 to 12-12
6-4, and is constituted by resource realizing units 127-1 to 127-4.

In this specific example, name analysis section 121-1
121-4 have the same function as the name analysis unit 2 in each of the above-described embodiments and specific examples, and are functionally equivalent. Here, it is assumed that the input name is output as it is. Also, the name resolution units 122-1 to 122-4
It has the functions of the name conversion unit 3 and the name resolution unit 4 in each of the above embodiments and specific examples.

Regarding the context holding unit 1-1, the name resolving unit 122-1 manages a name, a resource identifier, and a resource realization expression, which is a set of procedures, in a table. here,
The name name1 is represented by a resource realization expression <compression, res-1>
In addition, the name name2 is changed to a resource realization expression <extension, re
s-2>. Name change unit 123-1
Takes a name and a second name as input, and uses a name resolution unit 122-
Change the correspondence between the name and the resource realization expression in the table of No. 1. The member output unit 124-1 includes a name resolution unit 122-1.
Returns a list <name1, name2> of names that can be resolved by extracting the name part from the table consisting of pairs of names and resource realization expressions managed by. Member addition unit 12
5-1 inputs a set of a name and a resource realization expression, and adds the set to the table so that the input name can be resolved into a resource realization expression by the name resolution unit 122-1. Member deletion unit 126-
1 inputs a name and deletes a set including the input name from the correspondence between the name and the resource realization expression held by the name resolution unit 122-1. The resource realizing unit 127-1 is the name resolution unit 1
The resource identifier output by 22-1 is input to the resource management unit 22, requested to output a file, and a result obtained by applying the procedure output by the name resolution unit 122-1 to the output result is returned.

Regarding the context holding unit 1-2, the name resolution unit 122-2 manages a resource realization expression which is a set of a name, a resource identifier, and a procedure in a table, and stores the name name2 in the resource realization expression <compression, res- 3> and the name name
3 is resolved to a resource realization expression <extension, res-4>. The name change unit 123-2 receives the name and the second name as input, and changes the correspondence between the table name and the resource realization expression held by the name resolution unit 122-2. Member output unit 124-
2 is a list of resolvable names <name2, name by extracting a name part from a table composed of pairs of names and resource realization expressions managed by the name resolution unit 122-2.
3> is returned. The member adding unit 125-2 inputs a pair of a name and a resource identifier, and adds a correspondence to the table so that the name resolving unit 122-2 can resolve the input name into a resource identifier. The member deletion unit 126-2 inputs the name,
The set including the input name is deleted from the correspondence between the name and the resource realization expression held by the name resolution unit 122-2. The resource realizing unit 127-2 inputs the resource identifier output by the name resolving unit 122-2 to the resource managing unit 22 and requests to output a file.
Returns the result of applying the procedure output by -2.

Regarding the context holding unit 3, the name resolution unit 122-3 inputs a name and executes the following procedure. First, a request for outputting a file is given by passing the input name to the context holding unit 1-1, and if a non-empty result is returned, the result is returned as it is, and the processing ends. If an empty result is returned, the input name is passed to the context holding unit 1-2 to request output of a file. If a non-empty result is returned, the result is returned as it is. To end. If an empty result is returned, return an empty result.

[0224] The name change unit 123-3 receives the name and the second name as input, and executes the following procedure. First,
The name and the second name input to the context holding unit 1-1 are passed, and a change of the name is requested. Further, the input name and the second name are passed to the context holding unit 1-2, and a request to change the name is made.

The member output unit 124-3 executes the following procedure. First, the output of the member is requested to the context holding unit 1-1, and the result is set to A. Also,
The output of the member is requested to the context holding unit 1-2, and the result is set to B. The result of concatenating the result A and the result B is C, and C is returned.

The member adding unit 125-3 inputs a set of a name and a resource realization expression, and executes the following procedure.
First, a set of the name and the resource realization expression input to the context holding unit 1-1 is passed, and a request is made to add a member to the table. Exit if the request succeeds. In the case of failure, the combination of the name and the resource realization expression input to the context holding unit 1-2 is further passed, and a request is made to add a member to the table.

The member deletion unit 126-3 inputs a name and executes the following procedure. First, the input name is passed to the context holding unit 1-1, and a request is made to delete the member. Furthermore, the input name is passed to the context holding unit 1-2, and a request is made to delete the member.

The resource realizing section 127-3 includes the name resolving section 12
The output result of 2-3 is returned as it is.

Next, an example of the operation of the second specific example according to the third embodiment of the present invention will be described. Here, an operation in a case where the context identifier ctx-3 is specified to the communication unit 23 to request the output of the file represented by the name name1 will be described.

[0230] The context management unit 24 searches the context holding unit 1-3 having the context identifier ctx-3, and gives the context holding unit 1-3 the name nam.
Enter e1 and request to output the file. The context holding unit 1-3 inputs the name name1 to the name analysis unit 121-3, and obtains the name name1.
Next, the context holding unit 1-3 sends the name to the name resolution unit 122.
Enter the name name1 for -3 and request to resolve the name.

[0231] The name resolution unit 122-3 executes the above-described procedure. That is, first, it requests the context holding unit 1-1 to output a file with the name name1. The context holding unit 1-1 converts the name name1 into a name analysis unit 121.
-1 to get the name name1. Next, the context holding unit 1-1 inputs the name name1 to the name resolution unit 122-1 of the context holding unit 1-1.
The name resolution unit 122-1 of the context holding unit 1-1,
Returns <compression, res-1> for the input name1.

Next, the context holding unit 1-1 requests the resource management unit 22 to output a file to the resource holding unit having the resource identifier res-1.
The resource management unit 22 searches for the resource holding unit 21-1 whose resource identifier is equal to res-1, and requests to output a file. The resource holding unit 21-1 outputs the file and returns the file to the resource management unit 22.

The context holding unit 1-1 having received the output result of the file from the resource management unit 22 inputs the output result and the procedure “compression” to the resource realizing unit 127-1 and requests that the procedure be applied. The resource realizing unit 127-1
According to the definition of the procedure “compression”, the output result of the input file is compressed and returned to the context holding unit 1-1.

The context holding unit 1-1 returns the output result of the resource realizing unit 127-1 to the name resolution unit 122-3, and ends the processing. The name resolution unit 122-3 returns the input to the communication unit 23 as it is.

In this way, the name name1 is resolved, and a resource obtained by performing a compression process on the resource res-1 can be obtained. At this time, the user can handle the virtual resource having the name “name1” as a resource that has been subjected to a predetermined compression process. Further, in this specific example, each unit included in the context holding unit has a procedure. In this way, it is possible to configure so that the name is resolved by using the context holding unit in a chain according to the correspondence relationship with the name, and the resolution is performed by a predetermined procedure.

The specific examples in the first embodiment are the same as the specific examples in the second embodiment, except that the group attribute holding unit includes the name solving unit and the resource realizing unit. In each specific example of the first embodiment, the configuration similar to that of the second embodiment or the third embodiment is configured by including the name resolution unit and the resource realization unit in the context holding unit. be able to. In this case, the operations of the name resolution unit and the resource realization unit are the same as the name resolution unit and the resource realization unit of each specific example in the second embodiment, or the name resolution unit of each specific example in the third embodiment. It is the same as the resource realization unit. As described above, the functions shown in each specific example in the first embodiment can be realized by the configurations of the second and third embodiments.

Similarly, in each specific example of the second embodiment, the context holding unit in each specific example of the first embodiment does not include the name resolution unit and the resource realization unit.
Further, as in each specific example of the third embodiment, the group attribute holding unit is configured without including the resource realizing unit.
In each specific example of the embodiment, the name resolution unit and the resource realization unit are configured not to be included in the group attribute holding unit, thereby being configured in the same manner as the first embodiment and the third embodiment. Can be. In this case, the operations of the name resolving unit and the resource realizing unit are the same as those of the specific examples in the first embodiment or the specific example in the third embodiment. As described above, the functions shown in each specific example in the second embodiment can be realized by the configurations of the first and third embodiments.

Further, in each specific example of the third embodiment, in each specific example of the first embodiment, the context holding unit does not include the name resolution unit, and in the second embodiment, In each specific example of the second embodiment, the name resolution unit is not included in the group attribute storage unit in each specific example of the second embodiment, as in the case where the group attribute storage unit includes the resource realization unit. The configuration is the same as that of the first embodiment, and the resource realization unit is included in the group attribute holding unit, so that the configuration can be the same as that of the second embodiment. When the name resolution unit is not included in the group attribute holding unit, the operation of the name resolution unit is the same as that of each specific example in the first embodiment. When the resource realizing unit is included in the group attribute holding unit, the operation of the resource realizing unit is the same as that of the resource realizing unit of each specific example in the second embodiment. Thus, the third
The functions shown in the specific examples in the embodiment can be realized by the configurations of the first and second embodiments.

Next, a fourth embodiment of the resource management device of the present invention will be described. In each of the above-described embodiments, the name analysis unit 2 and the name conversion unit 3, the name resolution unit 4 in the third embodiment, and the resource realization unit 5 in the second embodiment,
Each context holding unit is configured to correspond to a context identifier. However, this context identifier is only one attribute for specifying the name analysis unit 2, the name conversion unit 3, the name resolution unit 4, and the resource realization unit 5. The name analysis unit 2, the name conversion unit 3, the name resolution unit 4, and the resource realization unit 5 can be associated with other various attributes, and each of them is selected and used according to the attribute. It is possible.

The configuration of the fourth embodiment is basically the same as the configurations of the above-described first to third embodiments. In the fourth embodiment, in each of the specific examples of the first to third embodiments, each context holding unit holds an attribute instead of a context identifier. Of course, a context identifier may be included as one of the attributes. In each of the specific examples of the following embodiments, as an example, a modified example of the first specific example of the above-described first embodiment will be described. However, other specific examples of the first embodiment and Similar modifications can be made to each specific example of the second and third embodiments.

FIG. 38 is a configuration diagram showing a specific example according to the fourth embodiment of the present invention. In the figure, the same parts as those in FIG. 131 is a context database unit; 132 is a context database search unit; 133 is a context set;
1-134-N are context holding units;
35-N is an attribute holding unit. Here, the context set is a set “Context”.

The context database unit 131
The context holding units 134-1 to 134-N are managed as a context set 133. In general, the context database unit 131 manages an arbitrary number of sets, assigns a name to the set, and refers to the set by using the name of the set. You may refer to this instead.

The context database unit 131
Is provided with a context database search unit 132 for searching the context set 133. The context database search unit 132 receives the resource search expression described using the attribute, and searches the context set 133 for a context holding unit having an attribute satisfying the resource search expression.

Each context holding unit 134-1 to 134
-N are attribute holding units 135-1 to 135 -N, respectively.
And name analyzers 2-1 to 2-N and name converters 3-1 to 3-N
N. Attribute holding units 135-1 to 13-13
5-N holds an arbitrary number of attributes as a list of pairs of attribute names and attribute values. Of course, a context identifier may be included as an attribute. When the attribute is only the context identifier, the first identifier of the first embodiment described above is used.
The configuration is similar to that of the specific example.

An example of a specific operation in a specific example of the fourth embodiment of the present invention will be described. Here, the attribute holding units 135-1 to 135 -N include three attributes of an attribute “owner” representing an owner, “mdate” representing a change date and time, and “category” representing a category.
Stored as a list of attribute name and attribute value pairs.
The attribute values are property. owner,
property. mdate, property. c
category. The property. owner value is “Smith”, property. mdate value is 95.18.18, property. category
Is "picture", and the attribute holding unit 135-
All properties from 2 to the attribute storage 135-N
ty. owner value is "Bill", property
y. The value of mdate is 95.3.3, property
y. It is assumed that the value of the category is "sound".

The name analyzer 2-1 outputs all the input names as they are. The name conversion unit 3-1 uses the name n
resource realization expression for ame1 <{, {res-1}}
> Is output. In this resource realization expression, the realization element sequence is empty, and the resource element sequence is composed of the resource identifier res-1. That is, it means that the resource having the resource identifier res-1 is used as it is, and this resource realization expression is equivalent to only the resource identifier res-1. Therefore, here, the name conversion unit 3-1 outputs the resource identifier res-1 for the name name1. Further, it is assumed that the name resolution unit 4 outputs the input resource search expression and the resource search expression in the resource realization expression to the context database search unit 132 as they are.

Now, if the attribute value representing the owner is “Smit
h "is specified, the attribute value representing the change date and time is newer than March 16, 1995, and the attribute value representing the category is specified as" image ", and an inquiry is made to the name" name1 ". Consider the case.

FIG. 39 is an explanatory diagram of an example of a resource search formula in a specific example of the fourth embodiment of the present invention. When making the above inquiry, for example, a resource search expression OQL-1 as shown in FIG. 39 may be input. This resource search expression OQL-1 is represented by Object Dataaba
se Management Group (ODMG)
Object Query Language proposed by
e: Described according to OQL. The meaning of the resource search expression OQL-1 is that the attribute property. owner
Is equal to "Smith" and the attribute property. The value of mdate is 95.3.
An attribute pro that is greater than 16 and represents a category
p-erty. If the category value is "pictur"
A search is made for a context holding unit equal to e ". If there is one corresponding context holding unit as a result of the search, the corresponding context holding unit is returned; otherwise, an error is returned.

When the communication unit 23 receives the inquiry request for the name name1 specifying the resource search expression OQL-1,
The attribute holding unit 135 of the context holding units 134-1 to 134-N for the context database unit 131.
A request is made to search for a resource satisfying the resource search formula OQL-1 from 1 to 135-N.

The context database unit 131 makes the context database search unit 132
L-1 is passed, and a context attribute holding unit that satisfies the resource search expression OQL-1 is searched. Here, the attribute holding unit 1
Since only 35-1 satisfies the condition of the resource search expression OQL-1, the context database unit 131 outputs the context search unit 135 as a search result of the resource search expression OQL-1.
Returns -1.

The communication unit includes a context holding unit 135-1
Is input as name1 to request name resolution processing.
The context holding unit 135-1 inputs the name name1 to the name analysis unit 2-1 and requests the name analysis unit 2-1 to analyze the name. Name na input to name analysis unit 2-1
me1 is output as it is as the name name1, and the name name1 is input to the name conversion unit 3-1. The name conversion unit 3-1 outputs a resource identifier res-1 for the input name name1.

Resource identifier re input to name resolution unit 4
s-1 is output as it is, and the resource search formula O
As a result of resolving the name name1 specifying QL-1, a resource identifier res-1 is obtained. From this resource realization representation, a resource having the resource identifier res-1 is obtained by the resource realization unit 5.

Next, a fifth embodiment of the resource management device of the present invention will be described. In each of the above-described embodiments, the context holding unit is specified by the context identifier or the attribute in units of the context holding unit, and the name to be resolved is input. However, each part in one context holder may be exactly the same as the corresponding part in another context holder. It is wasteful to arrange components common to some context holding units in each context holding unit in this way. In addition, when there are a plurality of context holding units having a certain common component, if the common component is modified in a certain context holding unit, it is not reflected in the other context holding units in the above embodiments. There was an inconvenience.

In the fifth embodiment, the name analysis unit 2 and the name conversion unit 3 existing in the context holding unit
Furthermore, each of the name resolution unit 4 and the resource realization unit 5 has an attribute, and a set is formed for each of these components. By selecting a component that satisfies the resource search formula from each set and using the selected component, the same operation as when the context holding unit is selected can be performed. In the following specific example, a case will be described in which only one name resolution unit 4 and one resource realization unit 5 exist, as in the above-described first embodiment. However, the present invention is not limited to this. When there are a plurality of name resolution units 4 as in the third embodiment, or as in the second embodiment,
Even when a plurality of resource realizing units 5 exist, the same configuration can be adopted.

FIG. 40 is a configuration diagram showing a specific example according to the fifth embodiment of the present invention. In the figure, FIG. 2, FIG.
The same parts as those described above are denoted by the same reference numerals and description thereof will be omitted. 1
41 is a set of name analysis units, 142 is a set of name conversion units, 14
3-1 to 143-N are name analysis unit holding units, and 144-1 to 144-1.
144-N is an attribute holding unit, 145-1 to 145-L are name conversion unit holding units, and 146-1 to 146-L are attribute holding units.

The context database unit 131 includes a context database search unit 132, N name analysis unit holding units 143-1 to 143-N, and L name conversion unit holding units 145-1 to 145-L. I have. The context database unit 131 stores the N name analysis unit holding units 143-1 to 143-N in the name analysis unit set 141.
And L name conversion unit holding units 145-1 to 15-1
45-L is managed as a name conversion unit set 142.

Name analysis unit holding units 143-1 to 143-N
Are attribute holding units 144-1 to 144-N for holding attributes
And name analyzers 2-1 to 2-N.
Further, the name conversion unit holding units 145-1 to 145-L include attribute holding units 146-1 to 146-L for holding attributes and name conversion units 3-1 to 3-L. Attribute holding units 144-1 to 144-N and attribute holding unit 146-1
146-L holds an arbitrary number of attributes as a list of pairs of attribute names and attribute values.

An example of a specific operation in a specific example of the fifth embodiment of the present invention will be described. Here, the name analysis unit set 141 is a set “Parser”, and the name conversion unit set 142 is a set “Trans”.

Also, the name analysis unit holding units 143-1 to 14-14
In the attribute holding units 144-1 to 144-N forming the 3-N, an attribute "name" representing a name is held as a list of pairs of attribute names and attribute values. Attribute holding unit 14
The attribute value representing the name of 4-1 to 144-N is prop
erty. It can be referred to as name. The property. The value of the name is “path_expression”, and the property.name of the attribute holding units 144-2 to 144 -N.
It is assumed that the value of the name is “dot_notation”.

Further, the name conversion unit holding units 145-1 to 15-1
45-N Attribute Holders 146-1 to 146-L
Has two attributes, an attribute “owner” representing an owner and an attribute “category” representing a category.
Stored as a list of attribute name and attribute value pairs.
The attribute values of the attribute holding units 146-1 to 146-L are, respectively, property. owner, property
y. It can be referred to as category. In the property holding unit 146-1, property. owner
Is "Smith", property. categ
The value of “ory” is “picture”, and the attribute holding unit 1
46-2 to 146-L. own
er is “Bill”, property. cat
It is assumed that the value of “gory” is “sound”.

The name analysis section 2-1 of the name analysis section holding section 143-1 outputs the longest continuous character string without the character "/" from the beginning of the name for the input name. And The name conversion unit 3-1 of the name conversion unit holding unit 145-1 outputs the resource identifier res-1 for the name name1. Further, it is assumed that the name resolution unit 4 outputs all the input resource search expressions as they are.

Now, if the attribute value representing the name is “path_
search for a context having a name analysis unit equal to "expression" and a name conversion unit whose attribute value indicating the owner is equal to "Smith" and attribute value indicating the category is equal to "image". For the name "name1 / name2 / name3"
A description will be given of an operation example when requesting name resolution.

FIG. 41 is an explanatory diagram of an example of a resource search formula in a specific example of the fifth embodiment of the present invention. When making the above request, for example, a resource search expression OQL-2 as shown in FIG. 41 may be input as the resource search expression. This resource search expression OQL-2 is, as in the fourth embodiment described above, Object DataBaseM
Object Query Language (OQ) proposed by the analysis Group (ODMG)
L. The meaning of the resource search expression OQL-2 is an attribute pr representing a name from the set Parser.
operty. If the value of the name is "path_expre
search for a name analysis unit holding unit equal to “session”, and if there is one corresponding name analysis unit holding unit, the name analysis unit of the corresponding name analysis unit holding unit is set as the name analysis unit of the context of the search result. Otherwise, an error is returned.In addition, from the set Trans, an attribute p representing the owner is set.
property. owner value is equal to "Smith" and the attribute property.
A search is made for a name conversion unit holding unit having a category value equal to "picture". If there is only one corresponding name conversion unit holding unit, the name conversion unit of the corresponding name conversion unit holding unit is searched for the context of the search result context. It is a name conversion part, and otherwise requests an error to be returned.

When the communication unit 23 receives the inquiry request of the name “name1 / name2 / name3” together with the resource search expression OQL-2, it requests the context database unit 131 to obtain a context satisfying the resource search expression OQL-2. I do. The context database unit 131 passes the resource search expression OQL-2 to the context database search unit 132, searches the name analysis unit holding unit and the name conversion unit holding unit that satisfy the resource search expression OQL-2, and generates a context.

FIG. 42 is a flowchart showing an example of a search operation of the name analysis unit and the name conversion unit in a specific example of the fifth embodiment of the present invention. First, in S151, a name analysis unit holding unit that satisfies the conditions of the resource search expression is searched, and set as a set 1. Here, N name analysis unit holding units 143-1 to 143 which are elements of the set Parser
For -N, each name analysis unit holding unit 143-1 to 143
-N attribute holding units 144-1 to 144-
N representing the name held in N.N.
The value of “name” is changed to “path_expression”
Compare with The result is true because the name analysis unit holding unit 14
Since it is 3-1, a set including only the name analysis unit holding unit 143-1 as an element is referred to as a set 1.

In S152, it is determined whether or not the number of elements of the set 1 obtained in S151 is 1, and if it is other than 1, an error is returned and the processing ends. Otherwise, go to the next step. In this case, the process proceeds to S153.

In S153, the name analysis unit 2-i is extracted from the name analysis unit holding unit 143-i, which is an element of the set 1. The extracted name analysis unit 2-i is used as the name analysis unit of the context that is the search result of the resource search expression. Here, the name analysis unit 2-1 is extracted.

Next, in S154, a name conversion unit holding unit that satisfies the conditions of the resource search expression is searched, and set as a set 2. Here, for the L name conversion unit storage units 145-1 to 145-L that are elements of the set Trans, the attribute storage unit 146 that is a component of the name conversion unit storage units 145-1 to 145-L is used. The value of the attribute “property.owner” representing the owner held in each of 1-146-L is compared with “Smith”, the result is true, and the attribute “property.categor” representing the category is obtained.
The value of “y” is compared with “picture.” Since the result is true in the name conversion unit holding unit 145-1, a set having only the name conversion unit holding unit 145-1 as an element is set 2
And

In S155, it is determined whether or not the number of elements of the set 2 obtained in S154 is 1, and if it is not 1, an error is returned and the processing is terminated. Otherwise, go to the next step. Here, the process proceeds to S156.

In step S156, the name conversion unit 3-j is extracted from the name conversion unit holding unit 145-j, which is an element of the set 2. The extracted name conversion unit 3-j is a name conversion unit of the context that is the search result of the resource search expression. Here, the name conversion unit 3-1 is extracted.

[0271] In S157, a context having the name analysis unit obtained in S153 and the name conversion unit obtained in S156 as constituent elements is generated and returned as a result. Here, since the name analysis unit 2-1 and the name conversion unit 3-1 are extracted, a context composed of these is generated and returned as a search result.

The communication unit 23 assigns a name “name1 / name2 / name3” to the generated context.
To request name resolution. This name "name
“1 / name2 / name3” is input to the name analysis unit 2-1 retrieved by the search. The name analysis unit 2-1 inputs the input name “name1 / name2”.
/ Name3 ”, a character string“ name1 ”from the beginning to before the character“ / ”is output.
1 "is input to the name conversion unit 3-1.

The name converter 3-1 outputs a resource identifier res-1 for the input character string "name1". The resource identifier res-1 input to the name resolution unit 4 is output as it is, and is transmitted to the communication unit 23 by the resource search expression OQL-2.
"Name1 / name2 / name
As a result of the resolution of 3 ", the resource identifier res-1 is returned.

Next, a sixth embodiment of the resource management device of the present invention will be described. In the above-described fifth embodiment, an example has been described in which each part constituting a context is searched by a resource search formula to generate a context. This sixth
In the embodiment of the present invention, the components constituting the context, namely, a name analysis unit, a name conversion unit, and a name resolution unit,
Further, the resource realization unit is composed of name analysis information, name conversion information, name resolution information, and resource realization information, respectively. By retrieving the name analysis information, name conversion information, name resolution information, and resource realization information, respectively, , Each part is generated. Of course, it is not necessary that all the units constituting the context are generated in this way, and only a part of them may be generated. Further, as in the specific examples shown in the above-described first to fourth embodiments, even in a configuration in which the context holding unit exists, as in the specific examples shown in the fifth embodiment, The present invention can be applied to a configuration in which each part constituting the context is searched.

In the following specific example, as an example of such a configuration, the context is composed of a name analysis unit and a name conversion unit, and the name analysis unit is provided in the name analysis unit holding unit as in the fifth embodiment. The name conversion unit searched from the set and the name conversion unit is generated based on the name conversion information searched from a plurality of sets having the name conversion information. However, the present invention is not limited to this. In the case where the name resolution unit 4 exists in the context as in the third embodiment, or in the case where the name resolution unit 4 and the resource realization unit are included in the context as in the second embodiment. 5
The same configuration can be used even when there is also one. In addition to the name conversion unit, the name analysis unit, the name resolution unit, and the resource realization unit may be configured to search and generate name analysis information, name resolution information, and resource realization information, respectively.

FIG. 43 is a configuration diagram showing a specific example according to the sixth embodiment of the present invention. In the figure, the same parts as those in FIG. 40 are denoted by the same reference numerals, and description thereof will be omitted. 161-
Reference numeral 163 denotes a name conversion information set. The context database unit 131 is a context database search unit 1
32, and N name analysis unit holding units 143-1 to 143-
It has a name analysis unit set 141 having N and three name conversion information sets 161 to 163.

Each of the name conversion information sets 161 to 163 is configured such that the name conversion information can be searched by the context database search unit 132. The name conversion information only needs to be information that allows name conversion, for example,
It may be a relation table or a function. In addition, item rewriting rules, attribute grammar rules, and Syntax Directed Tr
A conversion rule of an answer may be used. Further, it may be a clause set in logic programming, synthesis of an automaton (synthesis of transition rules), transition rules of a Turing machine, or the like. Further, it may be an instance of an object in object-oriented programming.

In the following description, it is assumed that the name conversion information is a relation table as an example. Here, the name analysis unit set 141 is a set Parser, the name conversion information set 161 is a set Parts, and the name conversion set 162 is a set Suppl.
y, the name conversion set 163 is referred to as a set Companies. FIG. 44 is an explanatory diagram of an example of a name conversion information set in a specific example of the sixth embodiment of the present invention. FIG.
Shows an example of the contents of the set Parts. Set Parts
Stores data on parts. Set Par
ts is a set having a binary set as an element, and the first term of the binary set is referred to as name and the second term is referred to as price. The name of the first term is the name of the part, and the second term p
rice represents the price of the part. For example, <part
The 1, 1500> binary indicates that the price of the part having the name “part1” is 1500.

FIG. 45 is an explanatory diagram of another example of the name conversion information set in one specific example of the sixth embodiment of the present invention. FIG. 45 shows the set Supply. Set Suppl
y stores data on the delivery status of parts. The set Supply is also a set having a binary set as an element. The first term of the binary set is name, and the second term is supp.
referred to as lier. The name in the first term represents the name of the part, and the supplier in the second term represents the supplier of the part. For example, the binary set of <part1, com1> indicates that the supplier of the part having the name “part1” is “co
m1 ".

FIG. 46 is an explanatory diagram of still another example of the name conversion information set in one specific example of the sixth embodiment of the present invention. FIG. 46 shows the set Companies. The set Companies stores data on suppliers. The set Companies is a set having a three-term set as an element, and the first term of the three-term set is referred to as name, the second term is referred to as tel, and the third term is referred to as outline. In the first section, name is the name of the supplier, in the second section, tel is the telephone number of the supplier, and in the third section, outlin
e represents a resource identifier of a file resource describing the outline of the supplier. For example, <com1, tel, res-5>
In the three-part set, the telephone number of the supplier of the part having the name “com1” is “11-111-1111”, and the resource identifier of the file resource that describes the outline of the supplier is “res”.
-5 ".

An example of a specific operation in a specific example of the sixth embodiment of the present invention will be described. Here, the name analysis unit holding units 143-1 to 143-N include the attribute holding units 144-1 to 144-N for holding attributes and the name analysis units 2-1 to 143-N.
2-N. Attribute holding unit 144-1
144-N holds an attribute “name” representing a name as a list of pairs of attribute names and attribute values.
property. The attribute value representing the name can be referred to by the name. The property. Of the attribute storage unit 144-1 constituting the name analysis unit storage unit 143-1. n
The value of “name” is “path_expression”, and the value of “prop” to the attribute holding units 144-2 to 144-N is set.
erty. The value of the name is "dot_notatio
The name analysis unit 4 outputs a longest continuous character string without including the character “/” from the beginning of the name for the input name. It is assumed that the name resolution unit 5 outputs all the input resource search expressions as they are.

FIG. 47 is an explanatory diagram of an example of a resource search formula in a specific example of the sixth embodiment of the present invention. Now, it is assumed that a resource search formula OQL-3 as shown in FIG. 47 is input as a resource search formula. The resource search expression OQL-3 shown in FIG. 47 is similar to the fifth and sixth embodiments described above, and includes Object Database M.
Object Query Language (OQ) proposed by the analysis Group (ODMG)
L. This resource search formula OQL-3
Has the following meaning. First, the set Pars
er, an attribute property. n
Searches the name analysis unit holding unit whose value of ame is equal to “path_expression”, and if there is one corresponding name analysis unit holding unit, searches the name analysis unit of the corresponding name analysis unit holding unit for the name of the context of the search result Analyze section, otherwise return error. Furthermore, the set Pa
The Cartesian product of rts, the set Supply and the set Companies is obtained, and this is set as a set 1. From the set 1, the value of a term corresponding to the price of the set Parts is 1000
And the value of the term corresponding to the name of the set Parts is equal to the value of the term corresponding to the name of the set Supply, and the value of the term corresponding to the supplier of the set Supply and the value of the term corresponding to the name of the set Company are equal to The equal elements are selected to be set 2. For each element of the set 2, a set is generated that has a binary set consisting of a term corresponding to the name of the set Company and an item corresponding to the outline of the set Company, and is used as a name conversion unit of the search result.

When the above-described resource search expression OQL-3 is specified,
When making an inquiry request for the name “com1 / name2 / name3”, the communication unit 23 receives them,
It requests the context database unit 131 for a context consisting of a name analysis unit and a name conversion unit that satisfies the resource search expression OQL-3. Context database part 1
31 passes the resource search expression OQL-3 to the context database search unit 132, searches for a name analysis unit that satisfies the resource search expression OQL-3, and searches for the resource search expression OQL.
A name conversion unit is generated from the name conversion information satisfying -3 to form a context.

FIG. 48 is a flowchart showing an example of the operation of searching the name analysis unit and searching for name conversion information in a specific example of the sixth embodiment of the present invention. Here, S171 to S173 correspond to S1 in FIG. 42 described above.
Same as 51 to S153. In this example, the set Par
N name analysis unit holding units 143-1 that are elements of ser
143-N to 143-N
Attribute holding units 144-1 to 14-14 which are constituent elements of 43-N
The attribute “propert” representing the name held in 4-N
y. The value of “name” is changed to “path_expression”.
n ”, the name analysis unit holding unit 143 whose result is true
A set 1 consisting of only -1 is obtained. Then, from the name analysis unit holding unit 143-1 which is an element of the set 1 to the name analysis unit 2-
1 is taken out as a context name analysis unit.

Next, in S174, name conversion information that satisfies the conditions of the resource search expression is extracted, and a name conversion unit is generated. In the case of the above-described resource search expression OQL-3, first,
Set Parts, Set Supply and Set Compan
The Cartesian product of y is obtained, and this is set as a set 2-1. Among the elements of the set 2-1, an element having a value of the term corresponding to the price of the set Parts that is larger than 1000 is selected, and this set is referred to as a set 2-2. Among the elements of the set 2-2,
The value of the term corresponding to the name of the set Parts and the set Su
Those having the same value of the term corresponding to the name of pply are selected, and this set is referred to as set 2-3. Furthermore, set 2-
Among the elements of 3, the supplier of the set Supply
And the value of the term corresponding to the name of the set Company are equal, and this set is referred to as the set 2
-4.

FIG. 49 is an explanatory diagram of a specific example of name conversion information that satisfies the conditions of the resource search expression in a specific example of the sixth embodiment of the present invention. When the set 2-4 is obtained as described above from the set Parts, the set Supply, and the set Company shown in FIGS. 44 to 46, the result is as shown in FIG.

Further, based on the resource search expression OQL-3, for each element of the set 2-4, the set Company
Is the first term from, and the set C
The term corresponding to the outline of the company is the second term t
A binomial set as o is constructed, a set having these binomial elements as elements is generated, and this set is referred to as a set 2-5.

FIG. 50 is an explanatory diagram of a specific example of a name conversion unit generated in a specific example of the sixth embodiment of the present invention. The set 2-5 generated in this manner is the first set.
This is information for converting the name of the item from to the resource identifier of to in the second item. Thus, the name conversion unit can be configured by the set 2-5 shown in FIG.

Returning to FIG. 48, in S175, in S17
The context is generated by the name analysis unit extracted in 3 and the name conversion unit generated in S174. here,
By the name analysis unit 2-1 and the generated name conversion unit,
A context is created.

The context database unit 131 receives the name of the name analysis unit 2- as a search result of the resource search expression OQL-3.
1 and a context having the name conversion unit generated by the set 2-5 as a component is returned as a result.

The communication unit 23 sends the requested name “com1 / name2” to the context created in this way.
/ Name3 "to request a name resolution operation. The name" com1 / name2 / name "is sent to the name analysis unit 2-1.
e3 "is input, and the longest character string" com1 "that is continuous without including the character" / "from the beginning of the name is output.
Since the name conversion unit has the information shown in FIG.
The term “res-” of the to of the element whose term is “com1”
5 "is output.

The res-5 input to the name resolution unit 4 is output as it is. As a result of requesting the communication unit 23 to specify OQL-3 and requesting the resolution of the name “com1 / name2 / name3”, the resource identifier res- 5 is returned.

In each of the specific examples of the fourth to sixth embodiments described above, the resource identifier was obtained by one name resolution procedure. However, in some cases, the name and the resource search expression were obtained. Sometimes it is done. In that case, the communication unit 23 sends the obtained resource search formula to the context database unit 131 again, searches for the context, and requests the searched context to resolve the name. As described above, resources can be obtained by repeatedly performing the name resolution process, as in the specific examples of the above-described first to third embodiments.

Further, in the specific examples of the fourth to sixth embodiments described above, the configuration in which the resource realizing unit 5 is provided is shown, but it is also possible to configure without providing the resource realizing unit 5. . In particular, in the case where the resource identifier is output from the name resolution unit as in each of the above-described examples, the resource realization unit 5 is unnecessary.

[0295]

As is apparent from the above description, according to the present invention, a local resource having a desired property is obtained by performing a predetermined process on a global resource. It can provide a function to handle local resources with different names. In addition, by performing different processing on a plurality of resources and accumulating the results, it is possible to determine whether a local resource having a single local name having a property desired by each user actually exists. Can be provided. Further, means for name analysis and name conversion, and furthermore, name resolution and resource realization can be appropriately combined by a search formula, and each of these means can be constituted by a search formula. As a result, a resource management apparatus and a resource management method that embody a highly flexible distributed system that provides a name space for local resource access for each user reflecting the preference and intention of the access method of each user are provided. There is an effect that it can be provided.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a first embodiment of a resource management device of the present invention.

FIG. 2 is a configuration diagram illustrating a first specific example of the resource management device according to the first exemplary embodiment of the present invention.

FIG. 3 is an explanatory diagram of an example of a correspondence table between resource element strings and resource realization expressions used in a name conversion unit in the first specific example of the first embodiment of this invention.

FIG. 4 is a flowchart illustrating an example of the operation of a procedure concat.

FIG. 5 is a flowchart illustrating an example of a read process in an example of an operation of a procedure concat.

FIG. 6 is a flowchart illustrating an example of a write process in an example of an operation of a procedure concat.

FIG. 7 is a flowchart illustrating an example of an operation of the name resolution unit 4 in the first specific example of the first exemplary embodiment of the present invention.

FIG. 8 is an explanatory diagram of an example of a correspondence table used in a name conversion unit of a second context holding unit in the second specific example of the first embodiment of this invention.

FIG. 9 is an explanatory diagram of an example of a correspondence table used in the name conversion unit according to the third specific example of the first embodiment of this invention;

FIG. 10: Procedure interpolate_400_
4 is a flowchart illustrating an example of a process of 100.

FIG. 11 is a block diagram showing a second embodiment of the resource management device of the present invention.

FIG. 12 is a configuration diagram illustrating a first specific example according to the second embodiment of the present invention.

FIG. 13 is an explanatory diagram of a local file system.

FIG. 14 is a configuration diagram illustrating an example of a resource management unit according to a first example of the second embodiment of this invention;

FIG. 15 is a configuration diagram illustrating an example of a group management unit according to the first specific example of the second embodiment of this invention;

FIG. 16 is an explanatory diagram of an example of a correspondence table held in a name conversion unit according to the first specific example of the second embodiment of this invention;

FIG. 17 is a configuration diagram illustrating an example of a group management unit according to a second specific example of the second embodiment of this invention;

FIG. 18 is an explanatory diagram illustrating an example of a correspondence table held in a name conversion unit according to a second specific example of the second embodiment of this invention;

FIG. 19 is a flowchart illustrating an example of a procedure for creating a correspondence table in a second specific example of the second embodiment of this invention.

FIG. 20 is a flowchart illustrating another example of a procedure for creating a correspondence table in the second specific example of the second embodiment of this invention.

FIG. 21 is a configuration diagram illustrating an example of a group management unit according to a third specific example of the second embodiment of this invention;

FIG. 22 is an explanatory diagram illustrating an example of a correspondence table held in a name conversion unit according to a third specific example of the second embodiment of this invention;

FIG. 23 is a configuration diagram illustrating another example of the group management unit according to the third specific example of the second embodiment of this invention;

FIG. 24 is an explanatory diagram of another example of the correspondence table held in the name conversion unit according to the third specific example of the second embodiment of this invention;

FIG. 25 is a configuration diagram illustrating still another example of the group management unit according to the third specific example of the second embodiment of this invention;

FIG. 26 is an explanatory diagram of still another example of the correspondence table held in the name conversion unit according to the third specific example of the second embodiment of this invention;

FIG. 27 is a configuration diagram illustrating an example of a group management unit according to a fourth specific example of the second embodiment of this invention;

FIG. 28 is a block diagram showing a third embodiment of the resource management device of the present invention.

FIG. 29 is a configuration diagram showing a first specific example according to the third embodiment of the present invention.

FIG. 30 is an explanatory diagram of an example of a name resolution tree.

FIG. 31 is a configuration diagram illustrating an example of a group management unit according to a first example of the third embodiment of this invention;

FIG. 32 is an explanatory diagram illustrating an example of a process of solving a name “/ G / G1 / monthly report” in the first specific example of the third embodiment of this invention.

FIG. 33 is an explanatory diagram of an example of a process of resolving a name “/ G / G1” in the first specific example of the third embodiment of this invention;

FIG. 34 is an explanatory diagram showing an example of a process of resolving a name “{document specific} monthly report G1” in the first specific example of the third embodiment of this invention.

FIG. 35 is an explanatory diagram of another example of the process of resolving the name “/ G / G1 / monthly report” in the first specific example of the third embodiment of this invention.

FIG. 36 is an explanatory diagram of still another example of the process of resolving the name “/ G / G1 / monthly report” in the first specific example of the third embodiment of this invention.

FIG. 37 is a configuration diagram showing a second specific example according to the third embodiment of the present invention.

FIG. 38 is a configuration diagram showing a specific example according to the fourth embodiment of the present invention.

FIG. 39 is an explanatory diagram of an example of a resource search expression in a specific example of the fourth embodiment of the present invention.

FIG. 40 is a configuration diagram showing a specific example according to the fifth embodiment of the present invention.

FIG. 41 is an explanatory diagram of an example of a resource search formula in a specific example of the fifth embodiment of the present invention.

FIG. 42 is a flowchart illustrating an example of a search operation of a name analysis unit and a name conversion unit according to a specific example of the fifth embodiment of the present invention.

FIG. 43 is a configuration diagram showing a specific example according to the sixth embodiment of the present invention.

FIG. 44 is an explanatory diagram of an example of a name conversion information set in a specific example of the sixth embodiment of the present invention.

FIG. 45 is an explanatory diagram of another example of the name conversion information set in one specific example of the sixth embodiment of the present invention.

FIG. 46 is an explanatory diagram of still another example of the name conversion information set in one specific example of the sixth embodiment of the present invention.

FIG. 47 is an explanatory diagram of an example of a resource search formula in a specific example of the sixth embodiment of the present invention.

FIG. 48 is a flowchart showing an example of a search operation of a name analysis unit and a search of name conversion information in a specific example of the sixth embodiment of the present invention.

FIG. 49 is an explanatory diagram of a specific example of name conversion information that satisfies a condition of a resource search expression according to a specific example of the sixth embodiment of the present invention.

FIG. 50 is an explanatory diagram of a specific example of a name conversion unit generated in a specific example of the sixth embodiment of the present invention;

[Explanation of symbols]

1-1 to 1-n ... context holding unit, 2-1 to 2-n
... Name analysis unit, 3-1-3-n ... Name conversion unit, 4,4-
1-4-n ... name resolution unit, 5,5-1-5-n ... resource realization unit, 6-1-6-n, 7-1-7-n, 8, 8-1
8-n, 9, 9-1 to 9-n, 10 to 12... Terminals, 21
-1 to 21-n: Resource holding unit, 22: Resource management unit, 23
... Communication unit, 24 ... Context management unit, 91 ... Resource management unit, 92-1 to 92-n ... Resource attribute holding unit, 93 ... Group management unit, 94-1 to 94-m ... Group attribute holding unit, 131 ... Context database section, 132: context database search section, 133: context set, 134-1 to 134-N: context holding section,
135-1 to 135-N: Attribute holding unit, 141: Name analysis unit set, 142: Name conversion unit set, 143-1 to 14-14
3-N: Name analysis unit holding unit, 144-1 to 144-N ...
Attribute holding unit, 145-1 to 145-L ... name conversion unit holding unit, 146-1 to 146-L ... attribute holding unit, 161-1
63 ... name conversion information set.

 ────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Ichiro Yamashita 430, Nakai-cho, Ashigagami-gun, Kanagawa Prefecture Inside Green Tech Nakai Fuji Xerox Co., Ltd. (56) References Maeda Maekawa 2 eds. Next Comes ", 1st Edition, Kyoritsu Shuppan, December 1991, Eliezer Levy, translated by Yoshiharu Amami," Distributed File System: Concepts and Examples "," Bit Separate Volume acm computing survey eyes '90 Computer "・ Science ”, Kyoritsu Shuppan, July 1992, PP. 141-191

Claims (11)

(57) [Claims] 1. A resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected via a network, comprising: a context holding unit having a context identifier; and a name resolution unit.
The context holding means is a name analysis means for inputting a resource name, which is a name given to a resource, for analyzing the name of the resource name, and an analysis result by the name analysis means is realized in advance in the computer system. A first resource element sequence whose element is a resource identifier unique to a real resource and a first realization element sequence which is procedure information for processing the first resource element sequence. A second resource element sequence having a set of a resource realization expression or a context identifier and a resource name as an element and a second realization element sequence that is procedure information for processing the second resource element sequence A second resource element string included in the second resource realization expression converted by the name conversion means in the context holding means. of Source Name resource management device and outputs to the context holding unit indicated by the corresponding context identifier. 2. A resource management apparatus for use in a network information system in which a plurality of computer systems for performing information processing are connected via a network, comprising a context holding unit having a context identifier, a name solving unit, and a resource realizing unit. The context holding means inputs a resource name, which is a name given to the resource, and analyzes the name of the resource name. The analysis result by the name analysis means is realized in advance in the computer system. And a first resource element sequence having only a resource identifier unique to the real resource being performed as an element, and a first realization element sequence as procedure information for processing the first resource element sequence. A second resource element sequence having a first resource realization expression or a set of a context identifier and a resource name as an element, and a method for processing the second resource element sequence A name conversion unit for converting into a second resource realization expression which is a set of a second realization element sequence which is continuation information, wherein the name resolution unit is converted by the name conversion unit in the context holding unit; The resource name of the second resource element string included in the second resource realization expression is output to the context holding unit indicated by the corresponding context identifier or converted by the name conversion unit in the context holding unit. 1 resource realization expression, the resource realization means interprets a first realization element sequence included in the first resource realization expression output by the name resolution means, and interprets the interpretation result as the first resource realization expression. A resource management device for executing a real resource corresponding to an element sequence and realizing the resource to generate a resource. 3. A resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected to a network, comprising a first context holding unit having a context identifier and a second context holding unit. The first context holding means includes a first name analysis means for inputting a resource name, which is a name given to the resource, for analyzing the name of the resource name, and an analysis by the first name analysis means. A first name conversion means for converting the result into a first resource element string having only resource identifiers unique to a real resource previously realized in the computer system, and a first name conversion means A first name to be converted into a first name resolution result which is a set of the converted first resource element sequence and procedure information for processing the first resource element sequence Solving means for interpreting procedural information included in the first name resolution result converted by the first name solving means, and executing the interpreted result on a real resource corresponding to the first resource element sequence. Resource generating means for outputting a handle information for operating the resource, the second context holding means receives the resource name and analyzes the name of the resource name A second name analysis unit, a second name conversion unit that converts an analysis result of the second name analysis unit into a second resource element string having a set of a context identifier and a resource name as an element, Output the resource name of the second resource element string converted by the name conversion means to the first context holding means corresponding to the context identifier, and handle information obtained from the first context holding means and the hand Second name resolution means for converting a second name resolution result which is a set of procedural information for processing resources corresponding to the information, and a second name resolution result converted by the second name resolution means And interpreting the procedure information included in the handle information and executing the interpretation result on the resource corresponding to the handle information to generate a second resource
A resource management device comprising: a resource realizing unit. 4. A resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected to a network, comprising a first context holding unit having a context identifier and a second context holding unit. The first context holding means includes a first name analysis means for inputting a resource name, which is a name given to the resource, for analyzing the name of the resource name, and an analysis by the first name analysis means. A first resource element sequence for converting the result into a first resource element sequence having a resource identifier inherent to a real resource previously realized in the computer system as an element
A first resource element string converted by the first name converting means and a name resolution result which is a set of procedure information for processing the first resource element string. The second context holding means inputs a resource name, analyzes the name of the resource name, and analyzes the result of analysis by the second name analyzing means. Second name conversion means for converting a set of a context identifier and a resource name into a second resource element string having elements as elements;
The resource name of the second resource element string converted by the second name conversion means is output to the first context holding means indicated by the corresponding context identifier, and the first context holding means outputs a name resolution result. A second name resolution means for receiving the resource management information. 5. A resource management apparatus used in a network information system in which a plurality of computer systems for performing information processing are connected to a network, wherein the first context holding means and the second context holding means having a context identifier are provided; Resource realizing means, wherein the first context holding means receives as input a resource name, which is a name given to the resource, and analyzes the name of the resource name; First name conversion means for converting the result of analysis by the name analysis means into a first resource element sequence having only resource identifiers unique to real resources previously realized in the computer system as elements; , Which is a set of a first resource element string converted by the name conversion means and procedure information for processing the first resource element string.
First name resolution means for outputting a name resolution result of
The second context holding means receives the resource name and analyzes the name of the resource name;
Second name conversion means for converting the result of analysis by the second name analysis means into a second resource element string having a set of a context identifier and a resource name as elements, and conversion by the second name conversion means The resource name of the second resource element string is output to the first context holding unit indicated by the corresponding context identifier, and the resource identifier and the resource identifier are output using the first name resolution result received from the first context holding unit. A second name resolution unit that outputs a second name resolution result, which is a set of procedure information for processing the real resource corresponding to the resource identifier, wherein the resource realization unit holds the second context Means for interpreting procedural information included in the second name resolution result output by the second name resolution means in the means, and interpreting the result of interpretation as a real resource realized in advance corresponding to the resource identifier Resource management apparatus characterized by generating a resource by running against. 6. A resource name, which is a name given to a resource, is input, a name of the resource name is analyzed, and a name analysis result is converted into a first resource element string having the resource name as an element. A resource name included in the converted first resource element string is analyzed, and the analysis result is converted into a second resource element consisting only of a resource identifier unique to a real resource previously realized in the computer system. To obtain a procedure information for processing the converted second resource element sequence, interpret the procedure information, and apply the procedure information to the real resource corresponding to the second resource element sequence based on the interpretation result. To generate a resource, obtain handle information for operating the generated resource, obtain procedural information for processing a resource corresponding to the handle information, interpret the procedural information, and interpret the interpretation result as the handle. Resources corresponding to information A resource management method characterized by generating another resource by applying. 7. A resource management device used in a computer system for performing information processing, wherein a resource name, which is a name assigned to a resource in association with an attribute, is input and one or more names for analyzing the name of the resource name are input. An analysis unit, a first resource element sequence in which a result of the analysis by the name analysis unit associated with the attribute is a resource identifier unique to a real resource previously realized in the computer system, and the first resource element sequence; A first resource realization expression consisting of a set of a first realization element sequence, which is procedure information for processing a resource element sequence, or a set of a search expression and a resource name that directly or indirectly specifies the attribute, is used as an element. Is converted into a second resource realization expression composed of a set of a second resource element sequence to be used and a second realization element sequence which is procedural information for processing resources obtained from the second resource element sequence. The name conversion means, a name analysis means based on the search expression included in the second resource realization expression converted by the name conversion means or the input search expression, and a name analysis result from the name analysis means. A selection unit for selecting a name conversion unit to be received, and a resource name of a second resource element string included in the second resource realization expression converted by the name conversion unit or an input resource name is selected by the selection unit. A resource management device comprising name resolution means for passing the name to a name analysis means. 8. The name conversion means comprises at least one name conversion information associated with the attribute, and the selection means specifies the at least one name conversion information to specify the name conversion information. Means for selecting a means, and further comprising name conversion means for configuring a name conversion means based on the one or more name conversion information specified by the selection means, wherein the name analysis means selected by the selection means comprises the name The resource management device according to claim 7, wherein the name analysis result is passed to the name conversion means configured by the conversion configuration means. 9. A plurality of the name resolution means are provided in association with the attribute, the selection means further selects the name resolution means, and the name conversion means selected by the selection means is the name conversion means. The resource management device according to claim 7, wherein the first resource realization expression or the second resource realization expression is transferred to the name solving means selected by the selecting means. 10. The method according to claim 1, wherein the first name conversion means obtains a first
Resource realization means for interpreting a first realization element sequence of the resource realization expression of the above and generating a resource based on a real resource previously realized corresponding to the first resource element sequence from the result of the interpretation. Any one of claims 7 to 9
The resource management device according to the item. 11. A plurality of said resource realizing means are associated with said attribute, said selecting means further selects said resource realizing means, and said name solving means is a resource selected by said selecting means. 10. The method according to claim 9, wherein the first resource realization expression is passed to realizing means.
2. The resource management device according to 1.