JP2008204413A - 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 conversion regulation storage means in the information processing system stores external attributes and conversion regulations for converting a common identifier generated by a common identifier generating means, into an external identifier. An external transmission receiving means receives instructions to transmit an entity to the outside. A converting means converts the common identifier of the entity to be transmitted in accordance with the instructions received by the external transmission receiving means, according to the conversion regulations stored in association with the external attributes stored in the conversion regulation storage means when the external transmission receiving means receives the transmission instructions to the outside. <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 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 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.
Moreover, many of these ID systems have strong restrictions. One of the most severe restrictions is that “the system must be memorable by humans”. For example, the ID system includes an ID for identifying the person, a personal identification number, and the like. If there is a restriction of storing in human short-term memory and processing, if it is a number, it is necessary to limit it to about 7 digits plus or minus 2 digits. The storage of meaningful character strings can be a little longer, but it remains a major limitation. Further, when linking with other commercial systems, the system may have unique restrictions (for example, 5 to 10 alphanumeric characters). Considering information exchange on the Internet, it may be necessary to make it impossible to guess the contents of the ID from the description of the ID from the viewpoint of security.

  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. An object of the present invention is to provide an information processing system and an information processing program capable of maintaining compatibility between an ID system used internally and an external ID system. In particular, when providing services in conjunction with external ID systems other than ID systems that can be defined internally, and with external ID systems that have restrictions that cannot express the internal ID system as they are, the ID system used internally Is compatible with the 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;
Conversion rule storage means for storing an external attribute and a conversion rule for converting the common identifier generated by the common identifier generation means into the external identifier;
An external transmission receiving means for receiving an instruction to transmit the entity to the outside;
When an external transmission instruction is accepted by the external transmission acceptance unit, the external transmission acceptance is performed according to the conversion rule stored in correspondence with the external attribute stored in the conversion rule storage unit. An information processing system comprising: conversion means for converting a common identifier of an entity to be transmitted by an instruction received by the means into the external identifier.

[Claim 2] The information processing according to [Claim 1], further comprising conversion storage means for storing an external identifier converted by the conversion means and a common identifier to be converted in association with each other. system.

[Claim 3] 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;
Conversion rule storage means for storing an external attribute and a conversion rule for converting the external identifier into a common identifier generated by the common identifier generation means;
A reception receiving means for receiving an entity from the outside;
When reception is accepted by the reception acceptance means, the entity accepted by the reception acceptance means according to the conversion rule stored corresponding to the external attribute stored in the conversion rule storage means An information processing system comprising: conversion means for converting the identifiers into the common identifiers.

[Claim 4] It further comprises conversion storage means for storing an external identifier and a common identifier in association with each other,
The information according to claim 3, wherein the conversion unit converts the identifier of the entity received by the reception reception unit into a common identifier based on the correspondence stored in the conversion storage unit. Processing system.

[Claim 5] Further comprising conversion storage means for storing an external identifier and a common identifier in association with each other,
If the identifier of the entity received by the reception receiving unit is not stored in the conversion storage unit, the conversion unit causes the common identifier generation unit to generate a common identifier, and causes the conversion storage unit to The information processing system according to claim 3, wherein the identifier and the common identifier are stored in association with each other.

[Claim 6] 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;
Conversion rule storage means for storing an external attribute and a conversion rule for converting the common identifier generated by the common identifier generation means into the external identifier;
An external transmission receiving means for receiving an instruction to transmit the entity to the outside;
When an external transmission instruction is accepted by the external transmission acceptance unit, the external transmission acceptance is performed according to the conversion rule stored in correspondence with the external attribute stored in the conversion rule storage unit. An information processing program that functions as a conversion unit that converts a common identifier of an entity to be transmitted by an instruction received by a unit into the external identifier.

[Claim 7] The computer further includes:
The information processing program according to claim 6, wherein the information processing program functions as a conversion storage unit that stores an external identifier converted by the conversion unit and a common identifier to be converted in association with each other.

[Claim 8] 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;
Conversion rule storage means for storing an external attribute and a conversion rule for converting the external identifier into a common identifier generated by the common identifier generation means;
A reception receiving means for receiving an entity from the outside;
When reception is accepted by the reception acceptance means, the entity accepted by the reception acceptance means according to the conversion rule stored corresponding to the external attribute stored in the conversion rule storage means An information processing program that functions as a conversion means for converting an identifier of a common identifier into a common identifier.

[Claim 9] The computer further includes:
Function as conversion storage means for storing external identifiers and common identifiers in association with each other,
The information according to claim 8, wherein the conversion unit converts the identifier of the entity received by the reception reception unit into a common identifier based on the correspondence stored in the conversion storage unit. Processing program.

[Claim 10] The computer further includes:
Function as conversion storage means for storing external identifiers and common identifiers in association with each other,
If the identifier of the entity received by the reception receiving unit is not stored in the conversion storage unit, the conversion unit causes the common identifier generation unit to generate a common identifier, and causes the conversion storage unit to The information processing program according to claim 8, wherein the identifier and the common identifier are stored in association with each other.

  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 of claim 2, even when a service is provided in conjunction with a restricted external ID system that cannot express the internal ID system as it is, it is managed by another external ID system. Since ID transmission to the apparatus can be performed, there is an effect that it is possible to link with a wider variety of external systems than when the present configuration is not provided.

  According to the information processing system according to claim 3, 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 system of claim 4, the internal ID corresponding to the external ID is identified even when the service is provided in conjunction with a limited external ID system that cannot express the internal ID system as it is. As a result, it is possible to receive IDs from devices managed by other external ID systems. Therefore, compared with the case where this configuration is not provided, the linkage with a wider variety of external systems can be achieved. There is an effect that it becomes possible.

  According to the information processing system of claim 5, even when a service is provided in conjunction with a restricted external ID system that cannot express the internal ID system as it is, a new internal ID is generated, ID can be received from a device managed by the external ID system, so that it is possible to link with a wider variety of external systems than when this configuration is not provided. There is an effect.

  According to the information processing program of claim 6, 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 program of claim 7, even when a service is provided in conjunction with a restricted external ID system that cannot express the internal ID system as it is, it is managed by another external ID system. Since ID transmission to the apparatus can be performed, there is an effect that it is possible to link with a wider variety of external systems than when the present configuration is not provided.

  According to the information processing program according to claim 8, 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 9, even when a service is provided in cooperation with a restricted external ID system that cannot express the internal ID system as it is, the internal ID corresponding to the external ID is specified. As a result, it is possible to receive IDs from devices managed by other external ID systems. Therefore, compared with the case where this configuration is not provided, the linkage with a wider variety of external systems can be achieved. There is an effect that it becomes possible.

  According to the information processing program of claim 10, even when a service is provided in conjunction with a restricted external ID system that cannot express the internal ID system as it is, a new internal ID is generated, ID can be received from a device managed by the external ID system, so that it is possible to link with a wider variety of external systems than when this configuration is not provided. There is an effect.

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 includes an entity management server 11, a common ID management server 14, and an external ID system conversion server 24. These are connected to each other by an internal channel 25 which is an internal network (line). The external ID system conversion server 24 is connected to an external system via an external network 26 such as the Internet. There may be a plurality of entity management servers 11. In addition, each server of the entity management server 11, the common ID management server 14, and the external ID system conversion server 24 is configured independently. For example, the entity management server 11 and the common ID management server 14 are combined into one server. It is good also as a server and the combination is arbitrary. Further, it may be a module corresponding to the entity management server 11, the common ID management server 14, and the external ID system conversion server 24 in one device. In this case, the internal channel 25 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 14 includes an entity distribution destination management module 12 and an entity distribution destination DB 13. As shown in FIG. 2, the entity delivery destination management module 12 and the entity delivery destination DB 13 are connected to each other.
As shown in FIG. 2, the entity delivery destination DB 13 is accessed from the entity delivery destination management module 12 and stores delivery destination information for each subspace and category of the entity.
As shown in FIG. 2, the entity delivery destination management module 12 accesses the entity delivery destination DB 13 and is transmitted from outside the common ID management server 14 (for example, the entity generation module 8 and the external ID system conversion module 19). The entity is received and distributed outside the common ID management server 14 based on the information stored in the entity distribution destination DB 13.

The external ID system conversion server 24 includes an external access channel 15, an external access channel management module 16, an external access channel management DB 17, an external transmission reception module 18, an external ID system conversion module 19, a common ID conversion module 20, an internal transmission module 21, An ID conversion recording module 22 and an ID conversion recording DB 23 are provided.
As shown in FIG. 2, one or more external access channels 15 are connected to the external access channel management module 16 and exchange entities with an external system having an external ID system via an external network 26. To do.

The external access channel management module 16 is connected to one or more external access channels 15, an external access channel management DB 17, an external ID system conversion module 19, and a common ID conversion module 20 as shown in FIG. The external access channel 15 is managed using the channel management DB 17. Then, based on instructions from the external ID system conversion module 19 and the common ID conversion module 20, the external access channel management DB 17 is accessed to search for a corresponding conversion rule.
As shown in FIG. 2, the external access channel management DB 17 is connected to the external access channel management module 16 and converts the attribute and common ID of the external access channel 15 that is an external system into an external ID or vice versa. Stores conversion rules. That is, it stores the attribute of each external access channel 15, the common ID and the conversion rule between the common ID that is the internal ID for each external access channel 15 and the external ID.

As shown in FIG. 2, the external transmission reception module 18 is connected to the external ID system conversion module 19 and receives an entity transmission instruction from the internal system to the external system. When the transmission instruction is accepted, the external ID system conversion module 19 is activated. A common ID is assigned to the entity.
As shown in FIG. 2, the external ID system conversion module 19 is connected to the external access channel management module 16, the external transmission reception module 18, and the ID conversion recording module 22, and the common ID received by the external transmission reception module 18 is determined. Conversion to an external ID is performed according to the attribute of the external access channel 15. At that time, the attributes of the external access channel 15 are extracted from the external access channel management DB 17 via the external access channel management module 16. Also, the ID conversion recording module 22 is notified of the conversion.

As shown in FIG. 2, the common ID conversion module 20 is connected to the external access channel management module 16, the internal transmission module 21, and the ID conversion recording module 22, and is based on an entity transmission instruction from the external system to the internal system. Thus, the external ID is converted into a common ID according to the attribute of the external access channel 15. The external ID converted into the entity is passed to the internal transmission module 21. At that time, the attributes of the external access channel 15 are extracted from the external access channel management DB 17 via the external access channel management module 16. Also, the ID conversion recording module 22 is notified of the conversion.
As illustrated in FIG. 2, the internal transmission module 21 is connected to the common ID conversion module 20, and transmits an entity to the internal system based on the common ID converted by the common ID conversion module 20. The transmission destination is obtained by inquiring the common ID management server 14.

As shown in FIG. 2, the ID conversion recording module 22 is connected to the external ID system conversion module 19, the common ID conversion module 20, and the ID conversion recording DB 23, and records ID conversion in the ID conversion recording DB 23. The conversion from the external ID to the internal ID, the conversion from the internal ID to the external ID, that is, the correspondence between the external ID and the internal ID is stored in the ID conversion record DB 23.
As shown in FIG. 2, the ID conversion record DB 23 is connected to the ID conversion record module 22, and based on an instruction from the ID conversion record module 22, the conversion record of the common ID to the external ID and the common of the external ID The record of assignment to ID is stored.

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 of providing a service in cooperation with a server or the like. In addition, an internal system is used from an external general user via an external server.
For example, in offices and the like, devices such as multifunction peripherals (also called multi-function copiers, which have functions of scanners, printers, copiers, fax machines, etc., hereinafter also referred to as MFP (Multi Function Peripherals)) and users A personal computer or the like as a client is arranged. The entity management server 11 is built in the data center. Similarly, an ID is exchanged between a common ID system system in which the external ID system conversion server 24 built in the data center is connected via an in-house LAN and an external system of an external ID system connected via the Internet or the like. carry out. Exchange destinations include a group of external servers that provide various services, and general users who use external servers.

(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 issues a common ID by combining the subspace ID, the category ID, and the entity ID (steps S408 and 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. “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).
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 12 in the common ID management server 14 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 13 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, business type, and the like.
FIG. 9 shows an example of the print / scan server management information entity. That is, the 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 company where the apparatus is installed, the type of business, the department name, and the like. -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 of the external system and transmitting the entity to the external system.

First, the external transmission reception module 18 receives an external transmission instruction of an entity from the internal system (step S1102).
Next, the external ID system conversion module 19 makes an inquiry to the external access channel management module 16 and requested from the attributes for each external access channel 15 stored in the external access channel management DB 17 in the form shown in FIG. The conversion rule of the external access channel 15 that executes the transmission instruction is acquired (step S1104).

  The data structure of information stored in the external access channel management DB 17 will be described with reference to FIG. The table stored in the external access channel management DB 17 has an access channel ID column, a subspace ID column, a category ID column, a conversion rule column, and a simple conversion column. The access channel ID column stores an identifier of the access channel, that is, an ID that can uniquely identify the external system when processing is performed in cooperation with the external system. That is, which external system is supported is specified using this column. The subspace ID column and the category ID column store a subspace ID and a category ID in the common ID, respectively. That is, it is made to correspond to a combination of identifiers other than the entity ID of the internal system corresponding to the access channel ID stored in the access channel ID column.

The conversion rule column is a conversion rule for creating compatibility between the external ID system adopted by the external system corresponding to the access channel ID stored in the access channel ID column and the ID system of the common ID that is the internal ID. is there. For example, the internal ID subspace / category ID is removed to generate an external ID, the internal ID category ID is removed to generate an external ID, the internal ID is converted to a 6-digit number, and other databases To generate a corresponding external ID, add a number one by one in the order of generating the external ID to generate an external ID of 8 digits, or generate an external ID by RSA encryption.
The simple conversion field stores a flag indicating whether or not the conversion rule stored in the conversion rule field is a simple conversion (Y indicates that it is a simple conversion and N indicates that it is not a simple conversion). To do. Here, the simple conversion is a rule that can mechanically convert the entity ID expressed by the common ID (a rule that can be reversely converted or a rule that does not require conversion). For example, a rule such as “remove subspace ID and category ID” is a simple conversion rule. A rule that is not simple conversion is a case where a serial number is assigned to each external access channel 15 or encrypted and transmitted.

Subsequently, it is determined whether or not the conversion rule is a simple conversion rule (step S1106). Actually, it is identified by a flag in the simple conversion column in the table shown in FIG.
If it is not a simple conversion rule (NO in step S1106), first, the rule is applied to create an external ID (step S1108).
Then, the correspondence relationship between the external ID and the common ID is stored in the ID conversion recording DB 23 through the ID conversion recording module 22 (step S1110).
In the case of a simple conversion rule (YES in step S1106), the rule is applied to create an external ID (step S1112).
Finally, the entity is transmitted to the outside using the converted external ID (step S1114).

FIG. 13 shows an example of simple conversion. In this example, when the common ID is converted into the external ID, the subspace ID and the category ID are removed. That is, the external ID “17A420E3” is generated by removing the subspace ID and category ID of the common ID “02-0001: 02-0005: 04-17A420E3”.
FIG. 14 is an example of non-simple conversion. Regardless of the value of the common ID, a unique 8-digit serial number is assigned within the external access channel 15. In the case of such conversion, naturally, not all ID spaces that can be expressed by common IDs can be expressed by external IDs. That is, the common ID “02-0001: 02-0005: 04-17A420E3” is converted into the external ID which is the serial number “050010003”. FIG. 15 shows conversion record information stored in the ID conversion record DB 23 in this example. That is, the common ID and the converted external ID are stored in association with each other.
FIG. 16 is also an example of non-simple conversion. In this example, encryption processing is performed so that the value of the common ID is not known. FIG. 17 shows conversion record information stored in the ID conversion record DB 23 in this example.

(Reception of common ID from external ID system)
FIG. 18 is a flowchart showing a process of converting an entity received from an external system having an external ID system in accordance with a common ID and transmitting it to an internal system that is a common ID management system.

First, the external access channel 15 receives an internal transmission instruction from an entity (step S1802).
Next, the common ID conversion module 20 makes an inquiry to the external access channel management module 16 and sends the requested transmission from the attributes for each external access channel 15 stored in the external access channel management DB 17 in the form shown in FIG. The conversion rule of the external access channel 15 that executes the instruction is acquired (step S1804). Here, the conversion rules stored in the external access channel management DB 17 include not only a rule for converting from a common ID to an external ID, but also a rule for converting from an external ID to a common ID. Further, when the rule is reversely convertible, only one rule may be stored. However, it is necessary to attach a code indicating whether the rule is a conversion rule from an external ID to a common ID or a conversion rule from a common ID to an external ID.

Subsequently, it is determined whether or not the conversion rule is a simple conversion rule (step S1806).
If it is not a simple conversion rule (NO in step S1806), the ID conversion record DB 23 is searched through the ID conversion record module 22. In the ID conversion record, as in the example shown in FIG. 15 or FIG. 17, conversion result information of the common ID and the external ID is stored (step S1808).
If an external ID is registered in the ID conversion record DB 23 (YES in step S1808), the external ID is converted into a common ID based on the search result (step S1810).

If not registered (NO in step S1808), the entity management server 11 assigns a new common ID to generate an entity because it is a new external ID (step S1812).
Then, the combination of the resulting common ID and external ID is stored in the ID conversion record DB 23 (step S1814).
If the determination in step S1806 is a simple rule, reverse conversion of the conversion rule at the time of transmission is performed to convert it to a common ID (step S1816).
Finally, the entity is transmitted to the internal system using the obtained common ID (step S1818).

  As shown in FIG. 19, the hardware configuration of a 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, common ID issue request module 7, entity distribution destination management module 12, external access channel management module 16, external transmission acceptance module 18, external ID system conversion A CPU (microprocessor) 1901 that executes programs such as the module 19, the common ID conversion module 20, the internal transmission module 21, the ID conversion recording module 22, and the like, a RAM (random access memory) 1902 that stores the program and data, A ROM (read only memory) 1903 storing a program for starting the computer, an HD (hard disk) 1904 as an auxiliary storage device, and an input for inputting data such as a keyboard and a mouse. A device 1906, an output device 1905 such as a CRT or a liquid crystal display, a communication line interface 1907 for communicating with other devices via a network, for example, and a bus 1908 for connecting them to exchange data It is configured. A plurality of these computers may be connected to each other via a network.

  Note that the hardware configuration illustrated in FIG. 19 illustrates one configuration example, and the present embodiment is not limited to the configuration illustrated in FIG. 19, 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. 19 may be connected to each other through 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. 7 to 10, 12, 15, and 17 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 and stored or distributed. 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 a flowchart 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 the transmission process of the entity to an external ID system management apparatus. It is explanatory drawing which shows the example of the information managed by external access channel management DB. It is explanatory drawing which shows the example of the simple conversion of an external ID system. It is explanatory drawing which shows the example (serial number conversion) of the non-simple conversion of an external ID system. It is explanatory drawing which shows the example (serial number conversion) of the conversion recording information memorize | stored in ID conversion recording DB. It is explanatory drawing which shows the example (encryption conversion) of the non-simple conversion to an external ID system. It is explanatory drawing which shows the example (encryption conversion) of the conversion recording information memorize | stored in ID conversion recording DB. It is a flowchart which shows the example which performs the reception process of the entity from an external ID system management apparatus. 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 ... Entity delivery destination management module 13 ... Entity delivery destination DB
14 ... Common ID management server 15 ... External access channel 16 ... External access channel management module 17 ... External access channel management DB
DESCRIPTION OF SYMBOLS 18 ... External transmission reception module 19 ... External ID system conversion module 20 ... Common ID conversion module 21 ... Internal transmission module 22 ... ID conversion recording module 23 ... ID conversion recording DB
24 ... External ID system conversion server 25 ... Internal channel 26 ... External network

Claims (10)

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;
Conversion rule storage means for storing an external attribute and a conversion rule for converting the common identifier generated by the common identifier generation means into the external identifier;
An external transmission receiving means for receiving an instruction to transmit the entity to the outside;
When an external transmission instruction is accepted by the external transmission acceptance unit, the external transmission acceptance is performed according to the conversion rule stored in correspondence with the external attribute stored in the conversion rule storage unit. An information processing system comprising: conversion means for converting a common identifier of an entity to be transmitted by an instruction received by the means into the external identifier. The information processing system according to claim 1, further comprising conversion storage means for storing an external identifier converted by the conversion means and a common identifier to be converted in association with each other. 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;
Conversion rule storage means for storing an external attribute and a conversion rule for converting the external identifier into a common identifier generated by the common identifier generation means;
A reception receiving means for receiving an entity from the outside;
When reception is accepted by the reception acceptance means, the entity accepted by the reception acceptance means according to the conversion rule stored corresponding to the external attribute stored in the conversion rule storage means An information processing system comprising: conversion means for converting the identifiers into the common identifiers. Conversion storage means for storing an external identifier and a common identifier in association with each other;
The information processing system according to claim 3, wherein the conversion unit converts the identifier of the entity received by the reception reception unit into a common identifier based on the correspondence stored in the conversion storage unit. . Conversion storage means for storing an external identifier and a common identifier in association with each other;
If the identifier of the entity received by the reception receiving unit is not stored in the conversion storage unit, the conversion unit causes the common identifier generation unit to generate a common identifier, and causes the conversion storage unit to The information processing system according to claim 3, wherein the identifier and the common identifier are stored in association with each other. 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;
Conversion rule storage means for storing an external attribute and a conversion rule for converting the common identifier generated by the common identifier generation means into the external identifier;
An external transmission receiving means for receiving an instruction to transmit the entity to the outside;
When an external transmission instruction is accepted by the external transmission acceptance unit, the external transmission acceptance is performed according to the conversion rule stored in correspondence with the external attribute stored in the conversion rule storage unit. An information processing program that functions as a conversion unit that converts a common identifier of an entity to be transmitted by an instruction received by a unit into the external identifier. The computer further
7. The information processing program according to claim 6, wherein the information processing program functions as a conversion storage unit that stores an external identifier converted by the conversion unit and a common identifier to be converted in association with each other. 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;
Conversion rule storage means for storing an external attribute and a conversion rule for converting the external identifier into a common identifier generated by the common identifier generation means;
A reception receiving means for receiving an entity from the outside;
When reception is accepted by the reception acceptance means, the entity accepted by the reception acceptance means according to the conversion rule stored corresponding to the external attribute stored in the conversion rule storage means An information processing program that functions as a conversion means for converting an identifier of a common identifier into a common identifier. The computer further
Function as conversion storage means for storing external identifiers and common identifiers in association with each other,
The information processing program according to claim 8, wherein the conversion unit converts the identifier of the entity received by the reception reception unit into a common identifier based on the correspondence stored in the conversion storage unit. . The computer further
Function as conversion storage means for storing external identifiers and common identifiers in association with each other,
If the identifier of the entity received by the reception receiving unit is not stored in the conversion storage unit, the conversion unit causes the common identifier generation unit to generate a common identifier, and causes the conversion storage unit to The information processing program according to claim 8, wherein the identifier and the common identifier are stored in association with each other.

Images