JP2008225724A - Information processing system and information processing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processing system, efficiently allocating an identifier to an entity required for performing service. <P>SOLUTION: A category identifier accept means of the information processing system accepts a category identifier, a sub-space storage means stores a sub-space for uniquely specifying a sub-space, an entity identifier issue means issues an entity identifier for ensuring the uniqueness of the entity by each category in the sub-space, a common identifier generation means generates a common identifier by synthesizing the sub-space identifier, the category identifier with the entity identifier, and an entity storage means requires issue of the common identifier, receives the common identifier, and stores the common identifier in association with the entity required for performing service. A service providing means provides service according to the specified common identifier by performing entity. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an information processing system and an information processing program.

In order to provide an electronic service, it is necessary to systematically manage various management objects and appropriately execute processing for them.
Therefore, several methods have been proposed for user management when providing electronic services. For example, if ID federation technology is used, it is possible to provide an environment where one user can use a plurality of services.

  For example, the technique described in Patent Document 1 relates to a basic method of this ID federation. That is, in Patent Document 1, when user authentication at a service providing site is performed using a user ID / password (authentication information), since the authentication information is managed for each service providing site, the user is authenticated for each service providing site. It is necessary to memorize information, and if the user forgets the authentication information, the operational cost burden at the service providing site such as suspension of access to the service providing site and authentication information reacquisition procedure becomes a problem. It is disclosed that a user authentication management site is established and user authentication information managed by each service providing site is integrated and managed so that the user can always access the service providing site with a single authentication information. .

  For example, the technique described in Patent Document 2 relates to a mechanism for sharing registered personal information with other services. That is, Patent Document 2 aims to improve the convenience of users by improving the efficiency of the management of personal information required when users try to receive services provided by various service organizations. When an organization concludes a personal information exchange contract with various service organizations and with users, and manages the personal information of the users collectively, and when the users receive services provided by the service organizations It is disclosed that personal information is provided to the service organization as necessary.

  Further, for example, the technique described in Patent Document 3 provides a function of transmitting image data to a server after user authentication in a convenience store or the like. That is, Patent Document 3 has a problem that an image processing apparatus that can be connected to a network is installed in a store such as a convenience store, and image data recorded in a mobile phone with a camera is stored in an easy and reliable manner. The image processing apparatus includes an image processing unit having a printing apparatus and an information processing unit connected to the image processing unit, and is connected to a server apparatus via a network. The information processing unit includes user ID information, It has a storage device that stores member registration information including fingerprint data and face photo data, an authentication means, and an upload means. When a fingerprint is input from a user, the fingerprint data and the fingerprint data of the storage device are collated, If both match, the ID information and face photo data corresponding to the fingerprint data are extracted from the storage device and displayed on the screen. , Uploading the image data recorded in the device such as a cellular phone with the user of the camera to a predetermined storage area of the server apparatus is disclosed.

In general, when a document is stored in a document database or when an ID is assigned to a file in a normal OS file system, it is a widely known general method.
JP 2004-078622 A JP 2001-344379 A Japanese Patent Laying-Open No. 2005-020582

However, when actually providing an electronic service, it is necessary to manage not only users and documents but also various objects such as service functions, contracts, printers, scanners, user clients, servers, and the like. Furthermore, depending on the case, there is a possibility that there are many types of users and documents instead of one type. For example, a user managed by the company, a user managed by a customer company, a scanned document, a processed document, and the like.
Further, when the service provision becomes large scale in many fields, it is inevitable that the system providing the service is distributed, and it is necessary to configure these distributed subsystems to operate autonomously.
When providing a service by combining different types of complex managed entities on a large-scale, distributed, autonomous system, identifiers are assigned to the managed objects and the uniqueness of the identifiers It is the basis of services realized by such a system to guarantee and efficiently store and retrieve identifier assignment targets.

  Accordingly, the present invention provides an information processing system and an information processing program that are capable of efficiently allocating identifiers for entities required for executing services in a distributed system that manages various types of entities. The purpose is to do.

The gist of the present invention for achieving the object lies in the inventions of the following items.
[Claim 1] Category identifier receiving means for receiving a category identifier capable of uniquely identifying a category;
Subspace storage means storing a subspace identifier that can uniquely identify a subspace that divides the identifier space into an exclusive space; and
An entity identifier issuing means for issuing an entity identifier that guarantees the uniqueness of an entity by category within a subspace;
It is an identifier in the entire identifier space by combining the subspace identifier stored by the subspace storage unit, the category identifier received by the category identifier receiving unit, and the entity identifier issued by the entity identifier issuing unit. A common identifier generating means for generating a common identifier;
Requesting the category identifier reception means to issue a common identifier together with the category identifier, receiving the common identifier generated by the common identifier generation means, and associating the common identifier with an entity necessary for executing the service. Entity storing means for storing;
An information processing system comprising service providing means for providing a service by executing an entity stored by the entity storage means in accordance with a designated common identifier.

[Claim 2] Category identifier receiving means for receiving a category identifier capable of uniquely identifying a category;
Subspace storage means storing a subspace identifier that can uniquely identify a subspace that divides the identifier space into an exclusive space; and
An entity identifier issuing means for issuing an entity identifier that guarantees the uniqueness of an entity by category within a subspace;
It is an identifier in the entire identifier space by combining the subspace identifier stored by the subspace storage unit, the category identifier received by the category identifier receiving unit, and the entity identifier issued by the entity identifier issuing unit. A common identifier generating means for generating a common identifier;
Requests the category identifier reception means to issue a common identifier together with the category identifier, receives the common identifier generated by the common identifier generation means, and receives the common service and a basic service that is an entity necessary for executing the service. Entity storage means for storing correspondingly;
Entity combination storage means for storing a combination of basic services stored by the entity storage means as a service;
Information processing comprising: basic service execution means for executing the basic service stored in the entity storage means constituting the service stored in the entity combination storage means in accordance with a designated service system.

[Claim 3] The system further comprises execution condition verification means for verifying basic service conditions executable by the basic service execution means,
The information processing system according to claim 2, wherein the basic service execution unit executes the basic service when it is verified that the execution is possible by the execution condition verification unit.

[Claim 4] A computer,
A category identifier receiving means for receiving a category identifier that can uniquely identify the category;
Subspace storage means storing a subspace identifier that can uniquely identify a subspace that divides the identifier space into an exclusive space; and
An entity identifier issuing means for issuing an entity identifier that guarantees the uniqueness of an entity by category within a subspace;
It is an identifier in the entire identifier space by combining the subspace identifier stored by the subspace storage unit, the category identifier received by the category identifier receiving unit, and the entity identifier issued by the entity identifier issuing unit. A common identifier generating means for generating a common identifier;
Requesting the category identifier reception means to issue a common identifier together with the category identifier, receiving the common identifier generated by the common identifier generation means, and associating the common identifier with an entity necessary for executing the service. Entity storing means for storing;
An information processing program that functions as a service providing unit that provides a service by executing an entity stored in the entity storage unit according to a specified common identifier.

[Claim 5] A computer,
A category identifier receiving means for receiving a category identifier that can uniquely identify the category;
Subspace storage means storing a subspace identifier that can uniquely identify a subspace that divides the identifier space into an exclusive space; and
An entity identifier issuing means for issuing an entity identifier that guarantees the uniqueness of an entity by category within a subspace;
It is an identifier in the entire identifier space by combining the subspace identifier stored by the subspace storage unit, the category identifier received by the category identifier receiving unit, and the entity identifier issued by the entity identifier issuing unit. A common identifier generating means for generating a common identifier;
Requests the category identifier reception means to issue a common identifier together with the category identifier, receives the common identifier generated by the common identifier generation means, and receives the common service and a basic service that is an entity necessary for executing the service. Entity storage means for storing correspondingly;
Entity combination storage means for storing a combination of basic services stored by the entity storage means as a service;
Information processing characterized by functioning as basic service execution means for executing the basic service stored in the entity storage means constituting the service stored in the entity combination storage means according to a designated service program.

[Claim 6] The computer,
Further functioning as an execution condition verification means for verifying conditions of the basic service executable by the basic service execution means,
The information processing program according to claim 5, wherein the basic service execution unit executes the basic service when it is verified that the execution condition verification unit can execute the basic service.

  According to the information processing system according to claim 1, an identifier for an entity necessary for executing a service in a distributed system that manages various types of entities, as compared to a case where the configuration is not provided. Can be more efficiently implemented.

  According to the information processing system according to claim 2, in a distributed system that manages various types of entities, the basic service required for the execution of the service is compared with a case where this configuration is not provided. The allocation of identifiers can be performed more efficiently, and a service that is a combination of the basic services can be more easily defined.

  According to the information processing system of the third aspect, it is possible to impose restrictions for each combination of basic services and to perform more flexible service control as compared with the case where this configuration is not provided. become.

  According to the information processing program of claim 4, in the distributed system that manages many kinds of entities, the identifiers for the entities required for the execution of the service, compared to the case where this configuration is not provided Can be more efficiently implemented.

  According to the information processing program of claim 5, in a distributed system that manages various types of entities, the basic service required for executing the service is compared with a case where the configuration is not provided. The allocation of identifiers can be performed more efficiently, and a service that is a combination of the basic services can be more easily defined.

  According to the information processing program of the sixth aspect, it is possible to impose restrictions for each combination of basic services and to perform more flexible service control as compared with the case where this configuration is not provided. become.

A preferred embodiment for realizing the present invention will be described below with reference to the drawings.
This embodiment is for providing a complex service by linking a plurality of simple services. In other words, when providing a single large service (hereinafter referred to as a linked service) by combining individual small service functions (hereinafter referred to as a primitive service), a flexible and high security level linked service is provided. In order to do this, the servers that can start the primitive service are limited in units of groups.

(Overall configuration of service ID management device)
1 and 2 are conceptual module configuration diagrams of an embodiment of the present invention.
The module generally refers to a component such as software or hardware that can be logically separated. Therefore, the module in the present embodiment indicates not only a module in a program but also a module in a hardware configuration. Therefore, the present embodiment also serves as an explanation of a program, a system, and a method. In addition, the modules correspond almost one-to-one with the functions. However, in mounting, one module may be composed of one program, or a plurality of modules may be composed of one program. A plurality of programs may be used. The plurality of modules may be executed by one computer, or one module may be executed by a plurality of computers in a distributed or parallel environment. Hereinafter, “connection” includes not only physical connection but also logical connection.
The system includes a configuration in which a plurality of computers, hardware, devices, and the like are connected by communication means such as a network, and also includes a case where the system is realized by a single computer, hardware, devices, and the like.
Hereinafter, explanation will be given mainly by exemplifying users (including managers) who are corporations and individuals as users. In order to simplify the description, the description may be made so that the user or the like operates as the main body, but this means that the system operates in response to an operation by the user or the like.

FIG. 1 is a conceptual module configuration diagram in a common ID issuing module 6 that is the core of a service ID (IDentification) management apparatus according to the present embodiment.
The service ID management apparatus as a whole is composed of a plurality of functional units (functions corresponding to the subspace ID 2 in the common ID issuing module 6 of the service providing module 14). This functional unit is called a subspace. From the viewpoint of ID management, the subspace is obtained by dividing the ID space of the entire apparatus into a plurality of exclusive partial spaces. A unique ID (subspace ID) is assigned to each subspace by the administrator.
Also, this subspace may be allocated to the system so that a conventional system can be included in the logical space by the common ID.

In addition, the service ID management device is a device that manages a target identified by an ID. Information on the management target (or information itself when the management target is information itself) is called an entity. Specifically, in the present embodiment, a script (script, program) or the like for executing a primitive (basic) service is included, and a script or the like for executing a cooperative service combining primitive services may be included. The type of entity is called a category. The category is assigned an ID (category ID) that can be uniquely identified by the administrator. The category ID is for collectively handling a plurality of types (system, logical space, logical area, target world, provided service, etc.).
The entity is assigned an ID (entity ID) that can be uniquely identified by the entity ID issuing module 4.

An ID for uniquely identifying an entity in all ID spaces including a subspace ID, a category ID, and an entity ID is called a common ID.
Although the subspace ID and category ID are allocated by the administrator, the service ID management apparatus may be allocated by a certain algorithm (for example, sequentially assigning numbers in the order of occurrence).

The common ID issue module 6 includes a common ID issue acceptance module 1, a subspace ID 2, a common ID generation module 3, an entity ID issue module 4, and an issued entity ID management DB 5. There is a common ID issuing module 6 for each subspace.
As shown in FIG. 1, the common ID issuance acceptance module 1 is connected to the common ID generation module 3 and accepts a common ID issuance request together with a category ID from the outside of the common ID issuance module 6 to perform common ID issuance processing. To start.
As shown in FIG. 1, the entity ID issuing module 4 is connected to the common ID generating module 3 and the issued entity ID management DB 5 and issues an entity ID that guarantees the uniqueness of each entity in the subspace. To do.
As shown in FIG. 1, the issued entity ID management DB 5 is connected to the entity ID issuing module 4 and stores a record for guaranteeing the uniqueness of the entity ID.
As shown in FIG. 1, the subspace ID 2 is connected to the common ID generation module 3 and is a subspace ID that uniquely identifies the subspace. The subspace ID2 is stored in a storage device such as a memory.
As shown in FIG. 1, the common ID generation module 3 is connected to the common ID issuance acceptance module 1, the subspace ID 2, and the entity ID issuance module 4, and receives the subspace ID and common ID issuance acceptance extracted from the subspace ID2. The category ID received by the module 1 and the entity ID issued by the entity ID issuing module 4 are combined to generate a common ID.

FIG. 2 is a module configuration diagram showing the configuration of the service ID management device.
The service ID management apparatus illustrated in FIG. 2 includes a service providing module 14, an entity distribution module 20, and a service cooperation management module 25. These are connected to each other by a channel 26 which is a communication line or the like. Note that there may be a plurality of service providing modules 14, and there may also be a plurality of entity distribution modules 20 and service cooperation management modules 25. In addition, the service providing module 14, the entity distribution module 20, and the service cooperation management module 25 may be realized as servers, respectively. In this case, the service distribution module 14, the entity distribution module 20, and the service cooperation management module 25 are configured independently. 25 may be combined into one server, and the combination is arbitrary.

As shown in FIG. 2, the service providing module 14 includes the common ID issue module 6, the common ID issue request module 7, the entity generation module 8, the cooperative service execution module 9, and the entity management module 10 shown in the module configuration diagram of FIG. , An execution condition verification module 11, a primitive service execution module 12, and an entity storage DB 13.
As shown in FIG. 2, the common ID issuance request module 7 is connected to the common ID issuance module 6 and the entity generation module 8, and requests the common ID issuance module 6 to issue a common ID by specifying a category ID. The common ID is received from the common ID issuing module 6. Then, the common ID is passed to the entity generation module 8.
As shown in FIG. 2, the entity generation module 8 is connected to the common ID issue request module 7, the cooperation service execution module 9, and the entity management module 10. The common ID issue module 6 issues the common ID issued by the common ID issue module 6. An entity that is received from the request module 7 and is a management target for the common ID is generated. The generated entity is stored in the entity storage DB 13 via the entity management module 10. In addition, upon execution of a service by the cooperative service execution module 9, an entity generation instruction is received and an entity is generated.

As shown in FIG. 2, the cooperation service execution module 9 is connected to the entity generation module 8, the entity management module 10, and the primitive service execution module 12, and executes the cooperation service. At that time, the primitive service execution module 12 is instructed to execute the primitive service constituting the cooperation service, the entity required for the cooperation service is requested to the entity management module 10, and at the time of execution of the cooperation service. An entity that needs to be generated is instructed to the entity generation module 8.
As shown in FIG. 2, the entity management module 10 is connected to the entity generation module 8, the cooperation service execution module 9, and the entity storage DB 13, and stores the entity generated by the entity generation module 8 in the entity storage DB 13. In response to a request from the cooperation service execution module 9, the entity storage DB 13 is managed by reading the requested entity from the entity storage DB 13 and passing it to the cooperation service execution module 9.
As shown in FIG. 2, the execution condition verification module 11 is connected to the primitive service execution module 12 and checks the execution condition of the primitive service executed by the primitive service execution module 12.
As shown in FIG. 2, the primitive service execution module 12 is connected to the cooperation service execution module 9 and the execution condition verification module 11, and executes a primitive service based on an instruction from the cooperation service execution module 9. At the time of execution, it is checked if it is checked by the execution condition verification module 11 and is determined to be executable.
As shown in FIG. 2, the entity storage DB 13 is connected to the entity management module 10 and stores the entity generated by the entity generation module 8 via the entity management module 10.

As shown in FIG. 2, the entity distribution module 20 includes an entity distribution destination management module 16, an entity distribution destination DB 17, an entity group management module 18, and an entity group DB 19.
As shown in FIG. 2, the entity delivery destination management module 16 is connected to the entity delivery destination DB 17, and accesses the entity delivery destination DB 17 to manage the delivery destination information for each subspace and category of the entity.
As shown in FIG. 2, the entity delivery destination DB 17 is connected to the entity delivery destination management module 16 and stores delivery destination information for each subspace and category of the entity.
As shown in FIG. 2, the entity group management module 18 is connected to the entity group DB 19, accesses the entity group DB 19, and manages entity group information.
As shown in FIG. 2, the entity group DB 19 is connected to the entity group management module 18 and stores entity group information.

As illustrated in FIG. 2, the service cooperation management module 25 includes a primitive service distribution module 21, a primitive service storage DB 22, a service cooperation script distribution module 23, and a service cooperation script storage DB 24.
As shown in FIG. 2, the primitive service distribution module 21 is connected to the primitive service storage DB 22, and accesses the primitive service storage DB 22 and executes a script for executing the primitive service as needed in each subspace (service Distribution module 14).
As shown in FIG. 2, the primitive service storage DB 22 is connected to the primitive service distribution module 21 and stores a script for executing the primitive service.
As shown in FIG. 2, the service cooperation script distribution module 23 is connected to the service cooperation script storage DB 24. The service cooperation script distribution module 23 accesses the service cooperation script storage DB 24, and executes a script for executing the cooperation service as needed. Delivered to the space (service providing module 14).
As shown in FIG. 2, the service cooperation script storage DB 24 is connected to the service cooperation script distribution module 23 and stores a service cooperation script that expresses the cooperation service by a combination of primitive services.

FIG. 3 is a diagram illustrating an installation example when the cooperation service providing apparatus is specifically realized.
For example, offices and the like include devices such as multifunction peripherals (also called multi-function copiers, which have functions such as scanners, printers, copiers, and fax machines, hereinafter referred to as MFPs (Multi Function Peripherals)). A personal computer or the like (service providing module 14) is arranged. The other service providing module 14 is constructed in a server such as a data center. These service providing modules 14 are connected by the Internet which is a kind of channel 26.
That is, in this system, a user uses a device that is a service providing module 14 in an office or the like, and cooperates with the service providing module 14 in the data center to provide an integrated service.

(Common ID issuance)
FIG. 4 is a flowchart illustrating an example of a common ID issuing process.
The common ID issue request module 7 passes the common ID issue request together with the category ID of the common ID to be issued to the common ID issue module 6.
The category ID and common ID issue request is input to the common ID issue acceptance module 1 (step S402).

The common ID issue acceptance module 1 that has received the common ID issue request passes the category ID to the common ID generation module 3.
The common ID generation module 3 requests the entity ID issuing module 4 to issue an entity ID.
The entity ID issuing module 4 issues an ID that is unique in the category in the subspace managed by the common ID issuing module 6.
The issued entity ID management DB 5 stores entity IDs that have been issued so far, and the entity ID issuing module 4 stores entity IDs so as not to overlap with the entity IDs stored in the issued entity ID management DB 5. Issue (step S404).

When the issuance of the entity ID is completed, the issued entity ID is stored in the issued entity ID management DB 5 (step S406).
The issued entity ID management DB 5 has a non-volatile counter for each category without taking the form of a database, and can have a simple configuration in which the counter is counted up every time an entity ID is issued. is there.
In the flowchart shown in FIG. 4, a common ID is generally issued to an entity. This entity includes a script required for executing a service (a script for executing a primitive service, a script for executing a cooperative service). ) Is included.

Then, the common ID generation module 3 combines the subspace ID, the category ID, and the entity ID (step S408), and issues a common ID (step S410).
An example of the logical structure of the common ID obtained by combining the subspace ID, the category ID, and the entity ID will be described with reference to FIG. The common ID is composed by combining the subspace ID, category ID, and entity ID in this order. Of course, any order may be used as long as the order is determined in advance.

  In the data structure of the common ID, each of the subspace ID, the category ID, and the entity ID is expressed by a combination of length information and an actual ID. That is, the subspace ID is composed of the subspace ID length and the subspace ID actual data, and the subspace ID length indicates the data length of the subspace ID actual data (8 bits as one unit, the same applies hereinafter). The space ID actual data indicates data that is the main body (substance) of the subspace ID. The category ID includes a category ID length and category ID actual data. The category ID length indicates the data length of the category ID actual data, and the category ID actual data indicates data that is the main body of the category ID. The entity ID includes an entity ID length and entity ID actual data. The entity ID length indicates the data length of the entity ID actual data. The entity ID actual data indicates data that is the main body of the entity ID.

  More specifically, a common ID such as “02-0051: 02-0003: 04-000000FF” is generated. Actually, a delimiter that makes human-readable is unnecessary, but for descriptive purposes, the delimiter between the subspace ID, category ID, and entity ID is expressed by “:”. In addition, “-” is inserted between the ID length and the ID itself, which is expressed in hexadecimal (may be an alphanumeric character expressed in 8 bits). “02-0051: 02-0003: 04-000000FF” is “0051” (length 2) as the subspace ID for the electronic document storage service, and “0003” (length) as the category ID for the corporate user. 2) assumes that “000000FF” (length 4) is assigned as the entity ID of a particular user. Therefore, these are synthesized and “02-0051: 02-0003: 04-000000FF” becomes a common ID.

(Generate entity)
FIG. 6 is a flowchart showing an example of processing for issuing a common ID and generating an entity.
First, the common ID issue request module 7 designates a category ID and requests the common ID issue module 6 to issue a common ID (step S602).
The common ID issuance module 6 that has received the category ID issues a common ID by executing the processing shown in the flowchart of FIG. 4 (step S604).
The entity generation module 8 receives the common ID issued in step S604 and assigns the entity to the common ID (step S606).

Then, the entity generation module 8 sends the common ID assigned with the entity to the entity management module 10 (step S608).
The entity management module 10 inquires of the entity delivery destination management module 16 in the entity delivery module 20 about the delivery destination of the entity, and refers to the entity delivery destination information (step S610). The entity delivery destination information is stored in the entity delivery destination DB 17 in the form shown in FIG. That is, the entity distribution destination information includes “No.” indicating the number, subspace ID, category ID, storage destination # 1 indicating the first place where the entity is stored (or distributed), and stores (or distributes the entity). ) Has storage location # 2 indicating the second location to be.
Then, the entity management module 10 distributes the entity to the storage destination # 1 or the storage destination # 2 (step S612).
The entity management module 10 of the storage destination # 1 or the storage destination # 2 stores the entity in the entity storage DB 13 (step S614). In some cases, the storage destination is the same subspace (when the sent entity management module 10 and the received entity management module 10 are in the same service providing module 14), and in this case, they are stored locally. .

An example of an entity generated in this way is shown. FIG. 8 shows an example of the management information entity of the multifunction peripheral. That is, a common ID (“02-0001: 02-0001: in one example of FIG. 8 :) for print / scan server management information including the name of the installation company in which the MFP is installed, the type of business, the department name, and the like. 04-000000FF ").
FIG. 9 shows an example of a scan image entity. That is, a common ID (“02-0023: 02-0010: 04-00FFDDCC” in one example of FIG. 9) is assigned to the image read by the scanner.

(Providing cooperative services)
A script example of a basic service (primitive service) constituting the cooperation service stored in the primitive service storage DB 22 will be described with reference to FIG.
The script of the primitive service is a basic unit of service provision, and describes processing in a specific subspace (service provision module 14). The primitive service script may be in any form as long as it can be executed on a specific platform, but here, a script executed on a server or a multifunction machine is assumed. The script of the primitive service itself is also distributed as an entity by the entity distribution module 20 and stored in the entity storage DB 13 of each subspace (service providing module 14). That is, in the example of FIG. 10, “02-0003: 02-0E0E: 04-000000FF” is assigned as the common ID. The category ID “0E0E” indicates that the script is an execution script.

An example of entity grouping information stored in the entity group DB 19 and managed by the entity group management module 18 will be described with reference to FIGS. 11 and 12.
The data structure shown in FIG. 11 is grouped by subspace ID and category ID. In other words, it has a group ID column, a corresponding subspace ID column, and a category ID column. The group ID column stores a common ID indicating the group, and a subspace ID that identifies an entity constituting the group. The category ID is stored in the subspace ID column and the category ID column, respectively. For example, in the second line of FIG. 11, entity data whose actual data of subspace ID is 0003 and category ID is unspecified is grouped, and a common ID as a group ID is “02” for the entity group. -0003: 02-0F0A: 04-00000001 ". In this way, entity grouping is specified only by subspace ID (when actual data of category ID and actual data of entity ID are not specified), or specified by subspace ID and category ID (entity ID actual data may be unspecified). “0F0A” indicates a group type defined by a subspace and a category.
The data structure shown in FIG. 12 is a group of specific entities. That is, the common IDs of the entities are listed and a common ID that is a group ID is assigned to the listed entity groups (in the example of FIG. 12, “02-0003: 02-0F0B: 04- 00000004 "). “0F0B” indicates a group type defined by specific entity designation.
In other words, when comparing both, the data structure shown in FIG. 11 is used to represent a relatively wide range of groups that can be specified by subspace IDs or category IDs. In the data structure shown in FIG. It is used to group specific entities within a narrow range.
In particular, the entity in the data structure shown in FIGS. 11 and 12 may be used as the entity of the service providing module 14 so that the service providing module 14 that can execute the cooperation service may be specified. Further, by making an entity a content entity, a cooperative service may be provided only for specific content.

A script example of the cooperative service stored in the service cooperative script storage DB 24 will be described with reference to FIG.
The data structure of FIG. 13 corresponds to the “STEP” field that stores the processing order of the linked service, the “EXEC-ID” field that stores the ID indicating the execution unit of the process corresponding to the “STEP”, and the process. It has a “Group ID” column for storing the ID of the group to be recorded. Note that the ID stored in the “EXEC-ID” field may be a common ID or a subset of the common ID.
Here, for simplification of description, the configuration is executed sequentially from the top. Each execution unit is configured by a pair of a primitive service script ID to be executed and an executable group ID. That is, it is expressed that this primitive service can be executed only in an environment that satisfies a specific group condition.

FIG. 14 is a flowchart showing processing for executing a plurality of primitive services in cooperation with each other under a certain group condition.
First, in the service module actually used (specific subspace (service providing module 14)), the ID of the service cooperation script as shown in FIG. 13 is specified by the user's operation, and the cooperation service is activated. (Step S1402).
The cooperation service execution module 9 acquires the cooperation service script from the service cooperation script storage DB 24 in the service cooperation management module 25 through the service cooperation script distribution module 23 using the ID specified in step S1402 (step S1404). .

The cooperation service execution module 9 acquires the current recursive call level. When it is designated by an operation by the user and execution is started, it is the first. This process is a necessary process because it is assumed that the cooperation service is recursively called (step S1406).
Next, before executing the primitive service by the primitive service execution module 12, the execution condition verification module 11 checks the execution condition. Here, the information stored in the entity group DB 19 in the entity distribution module 20 is referred to via the entity group management module 18, and the group ID condition defined by the service linkage script matches the specified condition. It is verified whether it is (step S1408). If they do not match, it is displayed to the user that it cannot be executed in the current environment, and the process ends.
If they match, the primitive service execution module 12 executes the first primitive service (step S1410).

It is determined whether or not the service cooperation script has been executed (step S1412). If it has been completed, the process proceeds to step S1418; otherwise, the process proceeds to step S1414.
The above processing is called recursively. At that time, a subspace (service providing module 14) for executing the next primitive service is acquired. The subspace ID information may be extracted from a group ID or extracted from conditions in individual primitive services (step S1414).
Then, the processing of this flowchart is recursively started in the cooperation destination subspace (step S1416).
Naturally, this call destination process is not a direct activation from the user, so the recursive call level acquisition process in step S1406 is executed with the second and subsequent values. In the primitive service execution process of step 1410, the second and subsequent executions are performed.
In this way, when the script is executed up to the last script, the recursive call is sequentially released, the process returns to the first call level, the result is displayed as necessary (step S1418), and the process is terminated (step S1420).

Here, as an example of processing, execution by recursive call has been described as an example, but the essence of processing is also simple when executing scripts procedurally sequentially or while executing execution is managed by a central server. does not change.
Some linkage services include and do not include user interaction. In the case of a linked service that does not include user interaction, the user only instructs the start of the service, but in practice, a plurality of services are linked in a place that is not visible to the user, and the result is presented to the user. When the user interaction is included, an interaction with the user occurs in the middle of the service, and a step of confirming the user's intention is included. In some cases, the server used may change. In the present embodiment, both are included in the cooperation service.
In the description of this embodiment, for simplification of explanation, a service without user interaction has been described. However, a service having user interaction can be described by describing user interaction in a primitive service script and a service linkage script. You may make it respond | correspond to.

With reference to FIG. 15, an example of a state of operating on the actual apparatus shown in FIG. 3 will be described as processing according to the flowchart shown in FIG. 14.
This cooperative service is (No. 1) located in an office or the like, and scans a document using a multi-function peripheral that is the service providing module 14; (No. 3) In the data center or the like, a character recognition server executes the character recognition on the character recognition server, and (No. 4) data. In the center or the like, the process of saving in the network storage which is the service providing module 14 is shown.
That is, the user has no. In step 1, a paper document is scanned using the multifunction machine. No. In the process 2, a comment is attached on the user's notebook PC. And No. In step 3, the character recognition server is activated and the result is No. 3. 4 is stored in the network storage.
This process is executed on the MFP in the company to which the user belongs, the notebook PC of the user, the character recognition service group provided by the plurality of companies to which the user belongs, and the specific network storage to which the user has a contract. This is limited by the execution condition verification module 11. That is, a service with a high security level may be provided. On the other hand, any in-house multifunction device can be used, and a flexible service that can select a character recognition service from several candidates is provided. May be.

(Hardware configuration etc.)
As shown in FIG. 16, the hardware configuration of the computer on which the program according to the present embodiment is executed is a general computer, specifically a personal computer, a computer that can be a server, or the like. Common ID issue acceptance module 1, common ID generation module 3, entity ID issue module 4, linkage service execution module 9, execution condition verification module 11, primitive service execution module 12, entity distribution destination management module 16, primitive service distribution module 21, etc. A CPU (microprocessor) 1601 for executing the program, a RAM (random access memory) 1602 for storing the program and data, and a ROM (read only memory) 1603 for storing a program for starting the computer. An HD (hard disk) 1604 as an auxiliary storage device, an input device 1606 for inputting data such as a keyboard and a mouse, an output device 1605 such as a CRT or a liquid crystal display, Communication line interface 1607 for communicating with other devices via a Ttowaku And, and a bus 1608 for exchanging data by connecting them. A plurality of these computers may be connected to each other via a network.

  Note that the hardware configuration illustrated in FIG. 16 illustrates one configuration example, and the present embodiment is not limited to the configuration illustrated in FIG. 16, and is a configuration capable of executing the modules described in the present embodiment. I just need it. For example, some modules may be configured with dedicated hardware (for example, Application Specific Integrated Circuit (ASIC)), and some modules are in an external system and connected via a communication line. In addition, a plurality of systems shown in FIG. 16 may be connected to each other via communication lines so as to cooperate with each other. In particular, in addition to a personal computer, it may be incorporated in an information appliance, a copier, a fax machine, a scanner, a printer, a multifunction machine, or the like.

  In the above embodiment, the data structures shown in FIGS. 5 and 7 to 13 are not limited to these data structures, and may be other data structures. For example, the table structure may be a link structure or the like. Further, the data items are not limited to those shown in the drawings, and may have other data items.

The program described above may be provided by being stored in a recording medium, or the program may be provided by communication means. In that case, for example, the above-described program may be regarded as an invention of a “computer-readable recording medium recording the program”.
The “computer-readable recording medium on which a program is recorded” refers to a computer-readable recording medium on which a program is recorded, which is used for program installation, execution, program distribution, and the like.
The recording medium is, for example, a digital versatile disc (DVD), which is a standard established by the DVD Forum, such as “DVD-R, DVD-RW, DVD-RAM,” and DVD + RW. Standards such as “DVD + R, DVD + RW, etc.”, compact discs (CDs), read-only memory (CD-ROM), CD recordable (CD-R), CD rewritable (CD-RW), etc. MO), flexible disk (FD), magnetic tape, hard disk, read only memory (ROM), electrically erasable and rewritable read only memory (EEPROM), flash memory, random access memory (RAM), etc. It is.
The program or a part of the program may be recorded on the recording medium for storage or distribution. Also, by communication, for example, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wired network used for the Internet, an intranet, an extranet, etc., or wireless communication It may be transmitted using a transmission medium such as a network or a combination of these, or may be carried on a carrier wave.
Furthermore, the program may be a part of another program, or may be recorded on a recording medium together with a separate program. Moreover, it may be divided and recorded on a plurality of recording media. Further, it may be recorded in any manner as long as it can be restored, such as compression or encryption.

It is a conceptual module block diagram in a common ID issuing module. It is a conceptual module block diagram of the whole cooperation service provision apparatus. It is explanatory drawing which shows the construction example of a cooperation service provision apparatus. 5 is a flowchart illustrating an example of a common ID issuing process. It is explanatory drawing which shows the example of the implementation structure of common ID. It is a flowchart which shows the example of an entity production | generation process. It is explanatory drawing which shows the example of the delivery destination information managed by entity delivery destination DB. It is explanatory drawing which shows the example of the management information entity of a service provision module. It is explanatory drawing which shows the example of the scan data managed by entity storage DB. It is explanatory drawing which shows the example of the information regarding the primitive service managed by primitive service storage DB. It is explanatory drawing which shows the example of the entity group definition information (subspace and category designation | designated) managed by entity group DB. It is explanatory drawing which shows the example of the entity group definition information (individual entity designation | designated) managed by entity group DB. It is explanatory drawing which shows the example of the service cooperation script managed by the service cooperation script storage DB. It is a flowchart which shows the process example of a cooperation service. It is explanatory drawing which shows the example of execution of a cooperation service. It is a block diagram which shows the hardware structural example of the computer which implement | achieves this Embodiment.

Explanation of symbols

1 ... Common ID issue acceptance module 2 ... Subspace ID
3 ... Common ID generation module 4 ... Entity ID issuing module 5 ... Issued entity ID management DB
6 ... Common ID issue module 7 ... Common ID issue request module 8 ... Entity generation module 9 ... Cooperation service execution module 10 ... Entity management module 11 ... Execution condition verification module 12 ... Primitive service execution module 13 ... Entity storage DB
14 ... Service providing module 16 ... Entity delivery destination management module 17 ... Entity delivery destination DB
18 ... Entity group management module 19 ... Entity group DB
20 Entity delivery module 21 Primitive service delivery module 22 Primitive service storage DB
23 ... Service linkage script distribution module 24 ... Service linkage script storage DB
25 ... Service cooperation management module 26 ... Channel

Claims (6)

A category identifier receiving means for receiving a category identifier that can uniquely identify the category;
Subspace storage means storing a subspace identifier that can uniquely identify a subspace that divides the identifier space into an exclusive space; and
An entity identifier issuing means for issuing an entity identifier that guarantees the uniqueness of an entity by category within a subspace;
It is an identifier in the entire identifier space by combining the subspace identifier stored by the subspace storage unit, the category identifier received by the category identifier receiving unit, and the entity identifier issued by the entity identifier issuing unit. A common identifier generating means for generating a common identifier;
Requesting the category identifier reception means to issue a common identifier together with the category identifier, receiving the common identifier generated by the common identifier generation means, and associating the common identifier with an entity necessary for executing the service. Entity storing means for storing;
An information processing system comprising service providing means for providing a service by executing an entity stored by the entity storage means in accordance with a designated common identifier. A category identifier receiving means for receiving a category identifier that can uniquely identify the category;
Subspace storage means storing a subspace identifier that can uniquely identify a subspace that divides the identifier space into an exclusive space; and
An entity identifier issuing means for issuing an entity identifier that guarantees the uniqueness of an entity by category within a subspace;
It is an identifier in the entire identifier space by combining the subspace identifier stored by the subspace storage unit, the category identifier received by the category identifier receiving unit, and the entity identifier issued by the entity identifier issuing unit. A common identifier generating means for generating a common identifier;
Requests the category identifier reception means to issue a common identifier together with the category identifier, receives the common identifier generated by the common identifier generation means, and receives the common service and a basic service that is an entity necessary for executing the service. Entity storage means for storing correspondingly;
Entity combination storage means for storing a combination of basic services stored by the entity storage means as a service;
Information processing comprising: basic service execution means for executing the basic service stored in the entity storage means constituting the service stored in the entity combination storage means in accordance with a designated service. system. Further comprising execution condition verification means for verifying basic service conditions executable by the basic service execution means,
The information processing system according to claim 2, wherein the basic service execution unit executes the basic service when it is verified that the execution condition verification unit can execute the basic service. Computer
A category identifier receiving means for receiving a category identifier that can uniquely identify the category;
Subspace storage means storing a subspace identifier that can uniquely identify a subspace that divides the identifier space into an exclusive space; and
An entity identifier issuing means for issuing an entity identifier that guarantees the uniqueness of an entity by category within a subspace;
It is an identifier in the entire identifier space by combining the subspace identifier stored by the subspace storage unit, the category identifier received by the category identifier receiving unit, and the entity identifier issued by the entity identifier issuing unit. A common identifier generating means for generating a common identifier;
Requesting the category identifier reception means to issue a common identifier together with the category identifier, receiving the common identifier generated by the common identifier generation means, and associating the common identifier with an entity necessary for executing the service. Entity storing means for storing;
An information processing program that functions as a service providing unit that provides a service by executing an entity stored in the entity storage unit according to a specified common identifier. Computer
A category identifier receiving means for receiving a category identifier that can uniquely identify the category;
Subspace storage means storing a subspace identifier that can uniquely identify a subspace that divides the identifier space into an exclusive space; and
An entity identifier issuing means for issuing an entity identifier that guarantees the uniqueness of an entity by category within a subspace;
It is an identifier in the entire identifier space by combining the subspace identifier stored by the subspace storage unit, the category identifier received by the category identifier receiving unit, and the entity identifier issued by the entity identifier issuing unit. A common identifier generating means for generating a common identifier;
Requests the category identifier reception means to issue a common identifier together with the category identifier, receives the common identifier generated by the common identifier generation means, and receives the common service and a basic service that is an entity necessary for executing the service. Entity storage means for storing correspondingly;
Entity combination storage means for storing a combination of basic services stored by the entity storage means as a service;
Information processing characterized by functioning as basic service execution means for executing the basic service stored in the entity storage means constituting the service stored in the entity combination storage means according to a designated service program. The computer,
Further functioning as an execution condition verification means for verifying conditions of the basic service executable by the basic service execution means,
The information processing program according to claim 5, wherein the basic service execution unit executes the basic service when it is verified that the execution condition verification unit can execute the basic service.

Images