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

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processing system capable of maintaining compatibility between an internal ID system and an external ID system when providing service in coordination with an external system. <P>SOLUTION: A subspace information storage means in the information processing system stores a first subspace identifier in a common identifier in association with a second subspace identifier which is an identifier different from the first subspace identifier and can uniquely identify a subspace specified by the first subspace identifier. A category information storage means stores a first category identifier in the common identifier in association with a second category identifier which is an identifier different from the first category identifier and can uniquely identify a category specified by the first category identifier. A converting means converts the common identifier into an identifier using the second subspace identifier or the second category identifier, using the subspace information storage means or the category information storage means. <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 targets (users, contents, etc.) and appropriately execute processing for them. Therefore, it is necessary to manage an identifier (IDentification, hereinafter also referred to as “ID”) that can uniquely identify a management target.
For example, several methods have been proposed for user management when providing electronic services. For example, if ID federation technology is used, an environment in which one user can use a plurality of services is provided.
As a technique related to these, for example, the technique described in Patent Document 1 relates to basic processing of 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 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 will also be 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.
As described above, the ID federation technique can be regarded as a technique for systematically managing users managed in a plurality of organizations.

Further, for example, the technology described in Patent Document 3 relates to 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 in 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 the distributed subsystem to operate autonomously.
When providing a service by combining different types of complex management targets on a system that is distributed on a large scale and operates autonomously in this way, IDs are allocated to the management targets, guaranteeing the uniqueness of the IDs, Efficient storage and retrieval of ID assignment targets is the basis for realizing a service in such a system.
Further, when actually providing a service, it is necessary to link with an ID system (also referred to as “external ID system”) outside the ID management system (also referred to as “internal ID system”) of the system to be provided. For example, when the internal ID system is a binary ID, the service may be provided in cooperation with a system that does not accept a binary ID. Furthermore, X. When acquiring a 509 certificate, it is necessary to specify an identification name in a format determined by the standard. Also, e-mail and server addresses have a standard format, and other formats cannot be specified arbitrarily.

  Therefore, the present invention can efficiently implement ID allocation for a management target for a system that provides a service by combining a plurality of types of management targets, and provides a service in cooperation with an external system. It is an object of the present invention to provide an information processing system and an information processing program that can maintain compatibility between an ID system used internally and an external ID system.

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;
A first subspace identifier, which is a subspace identifier in the common identifier generated by the common identifier generation means, and a subspace specified by the first subspace identifier can be uniquely identified, and the first subspace Subspace information storage means for storing a second subspace identifier corresponding to an identifier different from the identifier,
A first category identifier that is a category identifier in the common identifier generated by the common identifier generation means and a category specified by the first category identifier can be uniquely identified, and an identifier different from the first category identifier Category information storage means for storing the second category identifier in association with each other,
Conversion means for converting the common identifier generated by the common identifier generation means into an identifier using the second subspace identifier or the second category identifier using the subspace information storage means or the category information storage means. An information processing system comprising:

[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;
A first subspace identifier, which is a subspace identifier in the common identifier generated by the common identifier generation means, and a subspace specified by the first subspace identifier can be uniquely identified, and the first subspace Subspace information storage means for storing a second subspace identifier corresponding to an identifier different from the identifier,
A first category identifier that is a category identifier in the common identifier generated by the common identifier generation means and a category specified by the first category identifier can be uniquely identified, and an identifier different from the first category identifier Category information storage means for storing the second category identifier in association with each other,
The second subspace identifier or the identifier using the second category identifier received from the outside is used as the first subspace identifier or the first category identifier using the subspace information storage means or the category information storage means. An information processing system comprising conversion means for converting the identifier into an identifier.

[Claim 3] 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;
A first subspace identifier, which is a subspace identifier in the common identifier generated by the common identifier generation means, and a subspace specified by the first subspace identifier can be uniquely identified, and the first subspace Subspace information storage means for storing a second subspace identifier corresponding to an identifier different from the identifier,
A first category identifier that is a category identifier in the common identifier generated by the common identifier generation means and a category specified by the first category identifier can be uniquely identified, and an identifier different from the first category identifier Category information storage means for storing the second category identifier in association with each other,
Conversion means for converting the common identifier generated by the common identifier generation means into an identifier using the second subspace identifier or the second category identifier using the subspace information storage means or the category information storage means. An information processing program characterized by functioning.

[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;
A first subspace identifier, which is a subspace identifier in the common identifier generated by the common identifier generation means, and a subspace specified by the first subspace identifier can be uniquely identified, and the first subspace Subspace information storage means for storing a second subspace identifier corresponding to an identifier different from the identifier,
A first category identifier that is a category identifier in the common identifier generated by the common identifier generation means and a category specified by the first category identifier can be uniquely identified, and an identifier different from the first category identifier Category information storage means for storing the second category identifier in association with each other,
The second subspace identifier or the identifier using the second category identifier received from the outside is used as the first subspace identifier or the first category identifier using the subspace information storage means or the category information storage means. An information processing program that functions as a conversion unit that converts an identifier into an identifier.

  According to the information processing system according to claim 1, an external system having an external ID system capable of efficiently allocating an ID to the management target for a system that provides a service by combining a plurality of types of management targets. When providing a service in conjunction with the system, it is possible to carry out ID transmission to a device managed by another external ID system while maintaining the internal ID system handled by this information processing system. Compared to the case where this configuration is not provided, there is an effect that it becomes easier to link the service managed by the common ID with other services.

  According to the information processing system according to claim 2, an external system having an external ID system capable of efficiently allocating an ID to the management target for a system that provides a service by combining a plurality of types of management targets. When providing services in conjunction with the system, it is possible to carry out ID reception from devices managed by other external ID systems while maintaining the internal ID system handled by this information processing system. Compared to the case where this configuration is not provided, there is an effect that it becomes easier to link the service managed by the common ID with other services.

  According to the information processing program of claim 3, an external system having an external ID system that can efficiently allocate an ID to the management target for a system that provides a service by combining a plurality of types of management targets. When the service is provided in cooperation with the system, it is possible to carry out ID transmission to a device managed by another external ID system while maintaining the internal ID system handled by the information processing system by this information processing program Therefore, as compared with the case where this configuration is not provided, there is an effect that it is easier to link the service managed by the common ID with other services.

  According to the information processing program of claim 4, an external system having an external ID system capable of efficiently allocating IDs for the management targets to a system that provides a service by combining a plurality of types of management targets. When providing a service in cooperation with the system, it is possible to receive IDs from devices managed by other external ID systems while maintaining the internal ID system handled by the information processing system by this information processing program Therefore, as compared with the case where this configuration is not provided, there is an effect that it is easier to link the service managed by the common ID with other services.

Hereinafter, a preferred embodiment of the present invention will be described with reference to the drawings.
(Overall configuration of the 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, a user who is a corporation or an individual will be exemplified and explained as a user. In order to simplify the description, there is a case where it is described that the user or the like mainly operates, but this means that the system operates according to the operation by the user.

FIG. 1 is a conceptual module configuration diagram in the common ID issuing module 6 of the service ID management and exchange apparatus according to the present embodiment.
The service ID management and exchange 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 entity management server 11). 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 exchange device is a device that simultaneously manages a plurality of objects identified by IDs. Information related to this management target (or information itself when the management target is information itself) is called an entity, and 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 assigned by the administrator, the service ID management and exchange apparatus may be assigned 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 ID that guarantees the uniqueness of each category entity in the subspace. .
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 exchange device.
The service ID management exchange apparatus shown in FIG. 2 has an entity management server 11, a common ID management server 18, and an external ID system exchange server 25. These are connected to each other by an internal channel 26 which is an internal network (line). The external ID system exchange server 25 is connected to an external system via an external network 27. A plurality of entity management servers 11 and external ID system exchange servers 25 may be provided. The entity management server 11, the common ID management server 18, and the external ID system exchange server 25 are configured independently. For example, a combination of the entity management server 11 and the external ID system exchange server 25 is 1 There may be two servers, and the combination is arbitrary. Further, it may be a module corresponding to the entity management server 11, the common ID management server 18, and the external ID system exchange server 25 in one device. In this case, the internal channel 26 is an internal bus.

The entity management server 11 includes the common ID issue module 6, the common ID issue request module 7, the entity generation module 8, the entity management module 9, and the entity storage DB 10 shown in the module configuration diagram of FIG.
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 issued by the common ID issuing module 6 is passed to the entity generating module 8 in accordance with a request from the entity generating module 8.
As shown in FIG. 2, the entity generation module 8 is connected to the common ID issue request module 7 and the entity management module 9, and receives the common ID issued by the common ID issue module 6 from the common ID issue request module 7. An entity to be managed is generated for the common ID.

As shown in FIG. 2, the entity storage DB 10 is accessed from the entity management module 9 and stores the delivery destination information of the entity. The entity delivery destination information refers to a place where a plurality of entities indicated by the subspace ID and the category ID are to be stored.
As shown in FIG. 2, the entity management module 9 is connected to the entity generation module 8 and the entity storage DB 10, and is generated by the entity generation module 8 based on the delivery destination information stored in the entity storage DB 10. The entity in the common ID is distributed outside the entity management server 11.

The common ID management server 18 includes a subspace management module 12, a subspace information DB13, a category management module 14, a category information DB15, an entity distribution destination management module 16, and an entity distribution destination DB17.
As shown in FIG. 2, the subspace management module 12 is connected to the subspace information DB 13, the category management module 14 is connected to the category information DB 15, and the entity distribution destination management module 16 is connected to the entity distribution destination DB 17.

The subspace information DB 13 can uniquely identify the subspace ID in the common ID and the subspace identified by the subspace ID, and an ID different from the subspace ID, specifically a mnemonic code that is a character string, Are stored in association with each other.
In response to a request from the external ID system exchange server 25, the subspace management module 12 stores the association in the subspace information DB 13 or searches for the subspace ID in the subspace information DB 13 or the mnemonic code corresponding thereto. To the external ID system exchange server 25.

The category information DB 15 can uniquely identify a category ID in the common ID and a category specified by the category ID, and stores an ID different from the category ID, specifically, a mnemonic code that is a character string in association with each other. To do.
In response to a request from the external ID system exchange server 25, the category management module 14 stores the association in the category information DB 15, or searches the category ID in the category information DB 15 or the mnemonic code corresponding to the category ID, and searches for the external ID. The system is transferred to the system exchange server 25.

The entity delivery destination DB 17 stores delivery destination information for each subspace and category of the entity.
The entity delivery destination management module 16 stores delivery destination information or the like in the entity delivery destination DB 17 or receives an entity transmitted from the entity management module 9, and based on the information stored in the entity delivery destination DB 17, the common ID Deliver outside the management server 18.

The external ID system exchange server 25 includes an external transmission instruction reception module 19, an external ID system conversion module 21, an external transmission module 23, an internal transmission module 20, a common ID conversion module 22, and an internal transmission instruction reception module 24.
As shown in FIG. 2, an external transmission instruction receiving module 19, an external ID system conversion module 21, and an external transmission module 23 are connected and have a function of converting an internal ID into an external ID. 20, a common ID conversion module 22 and an internal transmission instruction reception module 24 are connected to each other and have a function of converting from an external ID to an internal ID.

The external transmission instruction receiving module 19 receives the common ID conversion instruction and the common ID for converting the common ID into the external ID system adopted by the external system via the internal channel 26. Then, the common ID is passed to the external ID system conversion module 21.
The external ID system conversion module 21 converts the common ID received from the external transmission instruction reception module 19 to the common ID expression format according to the external ID system. The conversion result is passed to the external transmission module 23.
The external transmission module 23 transmits the ID converted by the external ID system conversion module 21 to the external system via the external network 27.

The internal transmission instruction receiving module 24 receives a common ID conversion instruction and an external ID from an external system having an external ID system via the external network 27. Then, the external ID is passed to the common ID conversion module 22.
The common ID conversion module 22 converts the external ID received from the internal transmission instruction reception module 24 into a common ID expressed in an internal format. The conversion result is passed to the internal transmission module 20.
The internal transmission module 20 transmits the ID converted by the common ID conversion module 22 to the inside through the internal channel 26.

FIG. 3 is a diagram showing an installation example when the service ID management and exchange device is specifically realized.
The devices installed in offices, data centers, etc. are managed by internal IDs, and the devices in the offices are external systems that have an external ID system different from the internal ID system. This is an example in which a service is provided in cooperation with a server, an external certificate authority, or the like.
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 is arranged. The entity management server 11 is built in the data center. Similarly, an ID exchange between an external ID system exchange server 25 constructed in a data center and a common ID system connected via an in-house LAN and an external ID system connected via the Internet or the like is performed. carry out. Exchange destinations include a group of external servers providing various services, a PKI certificate authority, and the like.

(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 are 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 may have a non-volatile counter for each category without taking the form of a database, and may have a simple configuration in which the counter is counted up every time an entity ID is issued. .

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, and expressed in hexadecimal. “02-0051: 02-0003: 04-000000FF” is a subspace ID for the electronic document storage service. As “0051” (length 2), “0003” (length 2) as a category ID for a corporate user, and “000000FF” (length 4) as an entity ID of a specific user. Assumes. 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).
For the issued common ID, 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 9 (step S608).
The entity management module 9 inquires of the entity delivery destination management module 16 in the common ID management server 18 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 9 distributes the entity to the storage destination # 1 or the storage destination # 2 (step S612).
The entity management module 9 of the storage destination # 1 or the storage destination # 2 stores the entity in the entity storage DB 10 (step S614). In some cases, the storage location is the same subspace (when the sent entity management module 9 and the received entity management module 9 are in the same entity management server 11). In this case, the storage is stored locally. .

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

(Transmission of common ID to external ID system)
FIG. 11 is a flowchart showing a process of converting the common ID according to the external ID system and transmitting the entity to the outside. This process is mainly performed by the external transmission instruction receiving module 19, the external ID system conversion module 21, and the external transmission module 23.
First, the external transmission instruction receiving module 19 receives an external transmission instruction of an entity (step S1102). This is because the internal system calls a server belonging to the external ID system for service linkage, It corresponds to a process of issuing a request for acquiring a 509 certificate.
Then, the conversion format is determined according to the type of external ID system to be transmitted (step S1104). In other words, the external ID system adopted by the external system is in hexadecimal format, the identification name is expressed in ASCII format, the identification name is expressed in binary compatible format, the address name is expressed in ASCII format, and the address name is expressed in binary compatible format. If so, the following processing is performed according to the format.

  In the case of the hexadecimal format, the external ID system conversion module 21 converts the common ID into a format as shown in FIG. 12 (step S1106). This is a common ID of an actual binary expression in hexadecimal notation as it is. Although not readable by humans, the ID in FIG. 12 is obtained by converting a common ID “02-0001: 02-0005: 04-17A420E6”.

When the identification name is in ASCII format, the external ID system conversion module 21 converts the common ID into a format as shown in FIG. 13 (step S1108). In other words, the external ID system is an example in the case of hierarchical data of Country, Organization, Three Organizational Units, and Common Name. This is an example when the common name, which is the identification name, is in ASCII format.
“Country = Japan” and “Organization = EXAMPLE Co., Ltd.” are determined in advance. That is, since the count of the internal system is a fixed value, a constant value is set.

  “Organizational Unit = FXBID-A” indicates that the identification name of the internal ID system is in ASCII format. “Organizational Unit = E-SERVICE” is based on the value of the subspace ID = 0001, and the subspace management module 12 stores the mnemonic code from the information stored in the subspace information DB 13 in the format shown in FIG. "E-SERVICE" has been acquired. That is, the data structure in the subspace information DB 13 is a table having columns for storing a subspace ID, a mnemonic code corresponding to the subspace ID, and a description thereof as shown in FIG.

  “Organizational Unit = USERS” is based on the value of category ID = 0005, and the category management module 14 obtains “USERS” of the mnemonic code from the information stored in the category information DB 15 in the format shown in FIG. It is a thing. “Common Name = FX123456” is an entity ID expressed in ASCII format. That is, the data structure in the category information DB 15 is a table having columns for storing a category ID, a mnemonic code corresponding to the category ID, and a description thereof as shown in FIG.

When the identification name is in a binary compatible format, the external ID system conversion module 21 converts the common ID into a format as shown in FIG. 16 (step S1110). That is, the external ID system is a case of hierarchical data of Country, Organization, Three Organizational Units, and Common Name, and is an example in the case where the common name as the identification name is in a binary compatible format.
“Country” and “Organization” are the same as in the ASCII format described above.
“Organizational Unit = FXBID-B” indicates that the identification name of the common ID system is a binary compatible format.
The next two “Organizational Units” are the same as in the ASCII format.
“Common Name = 32F1B03417A420ED” is an entity ID representing a binary in hexadecimal format.

If the address name is in ASCII format, the external ID system conversion module 21 converts the common ID into a format as shown in FIG. 17 (step S1112).
The suffix “EXAMPLE.co.jp” is assigned in advance. That is, since the count of the internal system is a fixed value, a constant value is set.
“FXBID-A” indicates that the address name of the common ID system is in ASCII format.
“E-SERVICE” is obtained by obtaining a mnemonic code from the value of subspace ID = 0001, and “USERS” is obtained from the value of category ID = 0005.
“FX123456” is an entity ID expressed in ASCII.

If the address name is in a binary compatible format, the external ID system conversion module 21 converts the common ID into a format as shown in FIG. 18 (step S1114).
After the “@” mark, “FXBID-B” is the same as the ASCII format except that the address name of the common ID system indicates a binary compatible format.
“32F1B03417A420ED” before the “@” mark is an entity ID representing a binary in hexadecimal format.

  After any of the processes in steps S1106 to S1114, the external transmission module 23 assigns these converted IDs to the entity and transmits them to the external system managed by the external ID system (step S1116).

(Reception from external ID system)
FIG. 19 is a flowchart showing a process of converting an entity received from the external ID system in accordance with the common ID and transmitting it to the common ID management system. This process is mainly performed by the internal transmission instruction receiving module 24, the common ID conversion module 22, and the internal transmission module 20.
First, the internal transmission instruction receiving module 24 receives a reception from the external ID system, that is, an internal transmission instruction of an entity (step S1902). This is because the processing to the entity transmitted in the processing shown in FIG. 11 is processed as a result of processing by the external system, for example, a reply from the external server is received. It corresponds to the receiving process after the issue of the 509 certificate.
Then, a format to be converted is determined according to the type of the received external ID system (step S1904). In other words, the external ID system adopted by the external system is in hexadecimal format, the identification name is expressed in ASCII format, the identification name is expressed in binary compatible format, the address name is expressed in ASCII format, and the address name is expressed in binary compatible format. If so, the following processing is performed according to the format.

In the case of the hexadecimal format, the common ID conversion module 22 converts the format shown in FIG. 12 to the common ID format shown in FIG. 5 (step S1906). This is the reverse process of step S1106.
If the identification name is in ASCII format, the common ID conversion module 22 converts the format shown in FIG. 13 to the common ID format shown in FIG. 5 (step S1908). This is the reverse process of step S1108.
If the identification name is in a binary compatible format, the common ID conversion module 22 converts the format shown in FIG. 16 to the common ID format shown in FIG. 5 (step S1910). This is the reverse process of step S1110.
If the address name is in ASCII format, the common ID conversion module 22 converts the format as shown in FIG. 17 to the common ID format as shown in FIG. 5 (step S1912). This is the reverse process of step S1112.
If the address name is in a binary compatible format, the common ID conversion module 22 converts the format shown in FIG. 18 to the common ID format shown in FIG. 5 (step S1914). This is the reverse process of step S1114.
Then, the internal transmission module 20 gives these converted common IDs to the entity, and transmits them to the internal system managed by the common ID system (step S1916).

  Note that the hardware configuration of the computer on which the program according to the present embodiment is executed is a general computer as shown in FIG. 20, specifically, a personal computer, a computer that can be a server, or the like. Programs such as the common ID issue acceptance module 1, the common ID generation module 3, the entity ID issue module 4, the common ID issue request module 7, the subspace management module 12, the external ID system conversion module 21, and the common ID conversion module 22 are executed. A CPU (microprocessor) 2001, a RAM (random access memory) 2002 for storing the program and data, a ROM (read only memory) 2003 for storing a program for starting the computer, and an auxiliary storage device Communication device for communicating with other devices via a network, for example, an HD (hard disk) 2004, an input device 2006 for inputting data such as a keyboard and a mouse, and an output device 2005 such as a CRT or a liquid crystal display. Interface 2007, and, and a bus 2008 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. 20 illustrates one configuration example, and the present embodiment is not limited to the configuration illustrated in FIG. 20, 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. 20 may be connected to each other via a communication line 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. 7 to 10 and 12 to 18 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.
Then, the program or a part thereof may be recorded on the recording medium and stored, distributed, or the like. 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 above 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 service ID management exchange apparatus. It is explanatory drawing which shows the example of installation of an entity management server, an external ID system exchange server, an external server, an external certificate authority, a print / scan server, and a user client. It is a flowchart which shows the issuing process example of common ID. It is explanatory drawing which shows the example of a logical structure of common ID. It is explanatory drawing which shows the example of the production | generation process (distribution destination central management type) of an entity. It is explanatory drawing which shows the example of the information managed by entity distribution destination DB. It is explanatory drawing which shows the example of a user management information entity. It is explanatory drawing which shows the example of a printing / scan server management information entity. It is explanatory drawing which shows the example of a scan image entity. It is a flowchart which shows the example which performs a transmission process to the external ID system management apparatus of an entity. It is an example of the hexadecimal format of an external ID system. It is explanatory drawing which shows the example whose identification name of an external ID system is an ASCII format. It is explanatory drawing which shows the example of the subspace information memorize | stored in subspace information DB. It is explanatory drawing which shows the example of the category information memorize | stored in category information DB. It is explanatory drawing which shows the example whose identification name of an external ID system is a binary compatible format. It is explanatory drawing which shows the example of the address name of an external ID system in an ASCII format. It is explanatory drawing which shows the example whose address name of an external ID system is a binary compatible format. It is a flowchart which shows the example which performs the reception process from the external ID system management apparatus of an entity. 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 ... Entity management module 10 ... Entity storage DB
11 ... Entity management server 12 ... Subspace management module 13 ... Subspace information DB
14 ... Category management module 15 ... Category information DB
16 ... Entity delivery destination management module 17 ... Entity delivery destination DB
DESCRIPTION OF SYMBOLS 18 ... Common ID management server 19 ... External transmission instruction reception module 20 ... Internal transmission module 21 ... External ID system conversion module 22 ... Common ID conversion module 23 ... External transmission module 24 ... Internal transmission instruction reception module 25 ... External ID system exchange server 26 ... Internal channel 27 ... External network

Claims (4)

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;
A first subspace identifier, which is a subspace identifier in the common identifier generated by the common identifier generation means, and a subspace specified by the first subspace identifier can be uniquely identified, and the first subspace Subspace information storage means for storing a second subspace identifier corresponding to an identifier different from the identifier,
A first category identifier that is a category identifier in the common identifier generated by the common identifier generation means and a category specified by the first category identifier can be uniquely identified, and an identifier different from the first category identifier Category information storage means for storing the second category identifier in association with each other,
Conversion means for converting the common identifier generated by the common identifier generation means into an identifier using the second subspace identifier or the second category identifier using the subspace information storage means or the category information storage means. An information processing system comprising: 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;
A first subspace identifier, which is a subspace identifier in the common identifier generated by the common identifier generation means, and a subspace specified by the first subspace identifier can be uniquely identified, and the first subspace Subspace information storage means for storing a second subspace identifier corresponding to an identifier different from the identifier,
A first category identifier that is a category identifier in the common identifier generated by the common identifier generation means and a category specified by the first category identifier can be uniquely identified, and an identifier different from the first category identifier Category information storage means for storing the second category identifier in association with each other,
The second subspace identifier or the identifier using the second category identifier received from the outside is used as the first subspace identifier or the first category identifier using the subspace information storage means or the category information storage means. An information processing system comprising conversion means for converting the identifier into an 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;
A first subspace identifier, which is a subspace identifier in the common identifier generated by the common identifier generation means, and a subspace specified by the first subspace identifier can be uniquely identified, and the first subspace Subspace information storage means for storing a second subspace identifier corresponding to an identifier different from the identifier,
A first category identifier that is a category identifier in the common identifier generated by the common identifier generation means and a category specified by the first category identifier can be uniquely identified, and an identifier different from the first category identifier Category information storage means for storing the second category identifier in association with each other,
Conversion means for converting the common identifier generated by the common identifier generation means into an identifier using the second subspace identifier or the second category identifier using the subspace information storage means or the category information storage means. An information processing program characterized by functioning. 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;
A first subspace identifier, which is a subspace identifier in the common identifier generated by the common identifier generation means, and a subspace specified by the first subspace identifier can be uniquely identified, and the first subspace Subspace information storage means for storing a second subspace identifier corresponding to an identifier different from the identifier,
A first category identifier that is a category identifier in the common identifier generated by the common identifier generation means and a category specified by the first category identifier can be uniquely identified, and an identifier different from the first category identifier Category information storage means for storing the second category identifier in association with each other,
The second subspace identifier or the identifier using the second category identifier received from the outside is used as the first subspace identifier or the first category identifier using the subspace information storage means or the category information storage means. An information processing program that functions as a conversion unit that converts an identifier into an identifier.

Images