JP2002245353A - Data processing system for electronic application - Google Patents

Abstract

PROBLEM TO BE SOLVED: To resolve such problem that a user cannot receive required services in security processing or risk management using a black list when a one stop service system is assumed which collectively accepts procedure application and service application in not only administrative organs but also private service organs. SOLUTION: A user is requested to input necessary information suitable for a service by a request authentication DB 22, and the user is authenticated by a user authentication DB 32, and a service organ is guaranteed by a service organ DB 23, and it is confirmed whether a service meets the application from the user or not by a request service DB 25. User IDs, passwords, access flags, and service IDs are taken as management objects of a black list database; and information of the black list database is confirmed on the basis of user's ID and password to discriminate whether access in the entrance of this data processing system should be permitted or not by the pertinent access flag when the user is a black list object.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a data processing system for electronic applications. In particular, one procedural agency accepts applications for procedures and services to multiple agencies,
The present invention relates to a data processing system that realizes a so-called one-stop service.

[0002]

2. Description of the Related Art For example, regarding a data processing system for receiving a procedure application to a plurality of administrative agencies,
A technique described in Japanese Patent Application Laid-Open No. 1-213046 is known. With this technology, for example, it is necessary to refuse application for procedures by a person other than himself or an unauthorized person,
At the time of application acceptance, user authority confirmation and personal authentication confirmation are performed. If any of the confirmation results is denial, the user is not allowed to access the system. By performing such a security process, an unauthorized application for a procedure is not accepted.

On the other hand, in the field of paid services provided by private service organizations, so-called “blacklists” are used.
Risk management has been conventionally performed, such as users who cannot be registered as members.

[0004]

[Problems to be Solved by the Invention] Assuming a one-stop service system that collectively receives procedure applications and service applications for all organizations, including not only administrative organizations but also private service organizations, the security processing and black Risk management using lists has disadvantages.

[0005] For example, it is assumed that a check is made at the time of acceptance of an application as to whether the user is the person / authorized / blacklisted, and if any of them is rejected, the use is not permitted. This would result in all blacklisted applications being rejected. Originally, however, it is desirable to control the blacklister to accept some services, such as services to other service organizations, notification of address changes to administrative organizations, and free services.

[0006] The present invention is to solve such a problem. That is, blacklist information that defines information that specifies a service that cannot be accessed and information of a person that cannot access the data processing system is held. An object of the present invention is to make it possible to finely control the use of the one-stop service system using the blacklist information.

[0007]

In order to achieve the above object, in the data processing system for electronic application according to the present invention,
User IDs, passwords, access flags, and service IDs are managed as blacklist databases. Accordingly, when an application is received from an unauthorized user who is a blacklist target person, the information in the blacklist database is confirmed based on the user ID and the password, and the corresponding access flag is used at the entrance of the data processing system. The access permission (access permission to the mediation center) is determined. Also has a service ID,
By holding the service organization indicated by the service ID and the service menu in association with each other, the subject of application rejection (rejection after input of application information from the user) for the set of service organization and service menu indicated by the service ID Can be determined.

In the electronic application data processing system according to the present invention, a user ID, a reception ID, a service ID, a processing status flag, and a request content are managed as a request service database, and an access ID, a password, and Service organizations, service menus, representative names, addresses, and telephone numbers are managed. In this way, when registering data in the service institution database at the mediation center, the location, business description, creditworthiness, etc. of the service institution are investigated, and only the service institution that has reached a registrable level is registered. It is guaranteed. Also, the service information requested by the user is stored in the request service database at the mediation center,
When providing a service, the mediation center receives service information issued from a service organization. After receiving the service information, check whether the content matches the previously saved request service, and if it matches, send the service to the user; if not, request the service again from the service organization By doing so, it is guaranteed that the service as requested by the user will be provided.

[0009]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 shows an overall configuration for performing an electronic application data processing system according to the present invention. Figure 1
The electronic application data processing system shown in (1) includes a user terminal 1, a center management server 2 installed in an intermediary center provided between the user and the service organization, and a management server 3 installed in a service organization providing the service. ing.
The user terminal 1 is connected to the center management server 2 and inputs application information from the user, and inputs necessary information that the mediation center requests from the user in accordance with the service to be applied by the user. And display a message from the mediation center to the user. The center management server 2 receives input information from the user terminal 1 by the user, manages access to the mediation center from the user, and executes various databases (black list DB 24, request authentication DB 22,
The user accesses the information in the request service DB 25, the user authentication DB 21, and the service institution DB 23).

[0010] The center management server 2 executes an application program related to processing for an application from a user. Further, the center management server 2 manages various databases and executes a process according to the processing request when a processing request for the database occurs. The management server 3 receives the user information and the requested service information sent from the mediation center. The management server 3 manages a service processing system that performs a process related to providing a service.

Hereinafter, each of FIGS. 2 to 10 will be described. FIG. 2 shows a record format of the request authentication DB 22 that manages information to be requested to be input to the user as necessary information by a service (service institution and service menu) requested by the user. R10 is the name of a service organization that handles the service requested by the user, and R1
1 is a service menu requested by the user. R1
2 to R19 are flags for judging information requested by the user as information that requires input in order to receive a service requested by the user. Each flag includes a user ID flag, a password flag, a name flag, a date of birth flag, a gender flag, an address flag, a telephone number flag,
This is a payment information flag. The possible values of the flags R12 to R19 are "0" or "1". The value of the flag is set to “1” for an item that requires the user to input as necessary information.

A flag is set to "0" for an item for which the user does not require input as necessary information.
R100 is a pay / free flag, and its possible value is “0” or “1”. The value of the flag is set to “0” when the cost for receiving the service is free. Also, “1” is set when the fee for receiving the service is charged. R101 is the service ID
By giving the service (service institution and service menu), the service (service institution and service menu) can be specified.

The record creation or change of the request authentication DB 22 is performed when information is added or changed in the service institution and service menu handled by the mediation center (to the user in order to provide the service in FIG. 1). This is performed at the mediation center based on the information requesting input.

The request authentication DB 22 is referred to by receiving application information from the user terminal 1 at the mediation center, confirming the contents of the service (service institution and service menu) requested by the user, and then receiving the request from the user. It is performed at the mediation center based on the application information. That is, the service (service institution and service menu) requested by the user and R
By making 10 and R11 correspond, the values of the flags of R12 to R19 and R100 corresponding to R10 and R11 are referred to. By this reference, R12 to R1
The user is requested to input an item for which the value of the flag of No. 9 is “1”. The value of the R100 flag is "1"
In the case of, it is understood that the service (service institution and service menu) is charged.

FIG. 3 shows a record format of the blacklist DB 24 for managing information of a user who has made an unauthorized application. R20 and R21 are a user ID and a password for the user to access the mediation center. R2
Reference numeral 2 denotes an access flag indicating whether or not the user has authority to access the mediation center. The possible value of the flag of R22 is “0” or “1”. The value of the flag is set to “1” when the user does not have the authority to access the mediation center.

Further, "0" is set in the flag when the user has the right to access the mediation center. R2
Reference numeral 3 denotes service information when a user makes an illegal application, and sets a corresponding service ID (R101) stored in the request authentication DB 22. Blacklist DB
This data processing system using 24
Access to the mediation center is prohibited for users who performed more than once. Therefore, the reason why “1” is set in R22 is that the same user has made an illegal application twice or more. Further, a user who has made an unauthorized application only once can access the mediation center in the present data processing system, and thus “0” is set in R22. Therefore, the user whose value of R22 is "0" can access the mediation center. However, if the set of the service institution and the service menu applied by the user matches the set of the service institution and the service menu indicated by the service ID (R23) stored in the blacklist DB 24 of the user, The data processing system does not accept service requests from users.

The creation of a record in the blacklist DB 24 is performed after the processing result of the service providing process based on the application from the user terminal 1 is confirmed, and when the billing process in the service institution is not normally performed due to a delay in payment of the user, the mediation is performed. It is performed at the center. The update of the blacklist DB 24 is performed by the mediation center when the processing result is correct after the processing result of the service providing processing by the application from the user terminal 1 is confirmed.

The blacklist DB 24 has the meaning of a blacklist at the mediation center (access restriction at the entrance of the data processing system) and a blacklist at a service organization (application restriction after selecting a service menu). Having both meanings in one blacklist DB 24 is due to the improper application status of the user (when the user makes an improper application more than once), and restricts access at the entrance (access denied). ), And there is no problem in using one DB for operation. In addition, the meaning of both is separated DB
If you have as each, refer to each DB in each process,
Due to the occurrence of DB update, the processing is only complicated, and the functions to be performed are the same as those described above (having both meanings). Therefore, the present invention includes the case where the DBs are separately provided.

Further, sharing one black list with another service organization without having a black list for each service organization is achieved by using the mediation center provided between the user and the service organization by the data processing system. This is because it is necessary to centrally manage information not as a service organization but as an unauthorized application at the mediation center. However, when a blacklist is provided for each service institution, it is necessary to refer to a plurality of (for the number of service institutes) blacklists in order to grasp the improper application information of the user. For this reason, there is an inconvenience that the processing becomes complicated.

The present invention uses a blacklist DB as an intermediary center.
By having it in one place, this inconvenience is eliminated. The setting of the blacklist DB 24 is performed when an illegal application occurs. FIG. 4 shows a record format of the request service DB 25 that manages information of a service requested by a user in an application. R30 is a user ID required for the user to access the mediation center. R
Reference numeral 31 is a reception ID used to uniquely identify a record. R32 is a service ID indicating a set of a service menu that is the service content requested by the user and a name of a service institution that provides the service. R33
Is a processing status flag which is a flag for determining the processing status of the application from the user.

The value that can be taken by the flag of R33 is "0", "1", or "2". When the process for the application from the user is being processed, "2" is set as the value.
When the service for the application from the user is received, the value is set to “1”. Further, when all processes (including expense payment) for the application from the user are completed, the value is set to “0”. R34 is the request content of the service applied by the user.

The record creation of the request service DB 25 is as follows.
After the service requested from the user terminal 1 is confirmed in the blacklist DB 24, the service is performed in the mediation center based on the input information from the user terminal 1. At this time, the value of the processing status flag is set as “2” (under processing). The request service DB 25 is updated after confirming the service (content, ticket, etc.) issued by the service organization at the mediation center,
When it is confirmed that the processing has been correctly performed (the service is as requested by the user), the processing is performed at the mediation center. At this time, the value of the processing status flag indicates that the service is charged (the service ID in the request service DB 25).
Based on the request, the charged / requested DB 22
If the value of the free flag is "1", it is set as "1" (service reception). If the service is free (based on the service ID of the request service DB 25, the item of the request authentication DB 22 referred to). If the value of a certain paid / free flag is "0", it is set as "0" (processing end). In addition, when it is possible to confirm at the mediation center that the payment processing of the service has been correctly performed in the monthly processing, the mediation center requests the service DB2.
5 are updated. The value of the processing status flag at this time is
Set as "0" (processing end).

The request service DB 25 is referred to R31 in order to confirm the service requested by the user (service institution and service menu) and whether the service provided by the service institution is appropriate (guarantee of service contents). R30, R32 and R33, R34. After confirming that the service is appropriate, the service is sent from the mediation center to the user. In order to grasp the processing status of the user's service application, R3
1, the request service DB 25 is referred to, and R
30, R32 and R33, R34. FIG.
Is a record format of the user authentication DB 21 that manages information of users who are authorized to access the mediation center. R40 and R41 are a user ID and a password that the user needs to enter to access the mediation center. R40 and R4, which are information of the user authentication DB 21, are determined by the user ID and password input by the user.
1 and access is permitted when there is data.
R42 to R46 are names of users having access authority,
Address, phone number, date of birth, and gender.

A record of the user authentication DB 21 is created by a request from a user who wishes to use a system (service provision by electronic application) handled by the mediation center, when user information is added, At the mediation center based on the information of In addition, user authentication DB
Reference 21 is made at the mediation center based on the input information (user ID and password) from the user terminal 1 when the user terminal 1 accesses the mediation center.

FIG. 6 shows a record format of the service institution DB 23 for managing information on services (service institution and service menu) that can be provided in the present electronic application. R50 and R51 are an access ID and a password required to access the service organization from the mediation center. R52 and R53 are the name of the service organization and the contents of the service that can be provided. If there is no R52 or R53 that matches the user's application information (the service requested by the user), the user is notified of the application information. Request re-entry. R
54 to R56 are the representative name, address, and telephone number of the service organization.

The record creation (change) of the service institution DB 23 is based on the information (service service menu etc.) from the service institution in FIG. 1 when an addition (change) occurs in the service institution and the service menu handled by the mediation center. Then, it is performed at the mediation center. The service institution DB 23 is referred to by the mediation center based on the application information from the user after the application information from the user terminal 1 is received by the mediation center.

FIG. 7 is a flowchart showing a main processing routine and an after-processing routine of the processing operation in the data processing system for electronic application. The main process flow in FIG. 7 is a process from receiving an application from a user to making a service request to a service institution. The user is authenticated (step S1), and the user and the service institution / Service menu group is blacklist D
It is confirmed whether the information does not match the information in B24, and a service request is made to the service organization (step S2). FIG.
The after-processing flow is post-processing of service provision by electronic application, and updates the request service DB 25 and the black list DB 24 managed by the mediation center (step S3).

FIG. 8 is a flowchart for performing a procedure which is the first stage of processing in the data processing system. Here, first, by referring to the user authentication DB 21 and the blacklist DB 24, it is confirmed whether the user has the authority to access the mediation center (step S100). The process to be performed next is assigned based on the result of the confirmation of the access right (step S101).
In step S101, it is determined that the user does not have the access right because the user inputs the user ID input from the user terminal 1,
The password is the user IDR40 of the user authentication DB 21,
This is a case where the information does not match the information of the password R41. Or, the user ID input from the user terminal 1 by the user,
Password is user IDR2 of blacklist DB24
0, when it matches the password R21 and the access flag R22 is "1", it is determined that there is no access right. For example, referring to FIG. 3 specifically, a user whose user ID and password are “A0000003” and “A03” has two records in the blacklist DB 24 (by making an invalid application twice). Therefore, the value of the access flag R22 is “1”. Therefore, when the user accesses the mediation center, it is determined that there is no access right (step S10).
1), access denied (access denied at the entrance). Next, if the user ID and password are "A0000
Since the user of “001” and “A01” has only one record in the blacklist DB 24 (because the user has made an invalid application once), the value of the access flag R22 is “0”. Therefore, when the user accesses the mediation center, it is determined that the user has the access right (step S101), and the user becomes accessible. If it is determined in step S101 that there is an access right, the user inputs application information from the user terminal 1 (step S102).

The service institution and service contents, which are the application information input by the user, are stored in the service institution DB 23
(Service institution name R52 and service menu R5
Confirm by referring to 3) (step S103). The process is distributed according to the service institution and the right or wrong of the service content (step S104). If the service organization and the service content are not correct, the process is distributed depending on whether the user inputs the application information again (step S).
105). When the user re-enters the application information, the user requests input of the application information (step S102). Also,
If the user does not re-enter the application information, the application from the user is rejected (step S111), and the process ends.

If the service institution and the service contents are correct in step S104, the user refers to the request authentication DB 22 with the application information (service institution name and service menu) input (step S106). Thereby, the user is requested to input necessary information (items whose values are 1 in the flags R12 to R19) (step S107). The user inputs necessary information requested in step S107 (step S108),
The process is sorted according to the input information (step S10).
9). If the input is not correct in step S109,
The process is distributed depending on whether or not the user inputs necessary information again (step S110). When the user re-enters the necessary information, the user is required to input it (step S10).
8). If the necessary information is not re-entered in step S110, the application is rejected (step S111), and the process ends. If the input of the necessary information is correct in step S109, the process proceeds to the next process.

FIG. 9 is a flow chart for confirming the presence or absence of unauthorized application information of a user by referring to the blacklist DB 24 and requesting a service from a service organization. User ID based on the user ID and password entered by the user
Blacklist DB using R20 and password R21
24 (step S20).
0), it is confirmed whether the user has made an illegal application in the past (whether the user is a blacklist target person) or not (whether the user is not a blacklist target person), and the process is distributed (step S201). If the user has made an unauthorized application in the past (blacklist target person), the application of the user is an application for the service ID (R23) corresponding to the user ID (R20) and the password (R21). Is determined, and the process is distributed (step S20).
2).

The application from the user is a blacklist DB
If the request is for the service ID (R23) of No. 24, the request is rejected (step S205), and the process is terminated. If the application from the user is not an application for the service ID (R23) of the blacklist DB 24 in step S202, the service can be requested. Alternatively, if the user has not made an unauthorized application in the past (ie, is not a blacklist target) in step S201, it is possible to request a service. For example, specifically explaining with reference to FIG. 3, the user ID and the password are “A0000001” and “A0
The service applied by the 1 ”user is a service organization =
The service I on the record in the blacklist DB 24, such as “a”, service menu = “book”
If the combination is the same as the combination of the service organization and the service menu defined in D (R23), it is determined that the application from the user is not allowed (step S202), and the application is rejected (step S205). However, if the service applied by the user is a service institution = “a” and a service menu = “concert ticket”, the service ID (R2
If the set is not the same as the set of the service institution name and the service menu defined in 3), it is determined that the application from the user can be accepted (step S202), and the service can be requested (step S202). S204). Also, the service applied by the user whose user ID and password are “A0000002” and “A02” is a service on the record in the blacklist DB 24 such as “service institution = b” and service menu = “concert ticket”. If the combination is not the same as the combination of the service menu and the service institution name defined by the ID (R23), it is determined that the application from the user is acceptable (step S202), and the service can be requested. (Step S204).

When the service can be requested, after registering the information of the service requested by the user in the request service DB 25 (step S203), the service is requested to the service institution (user information and the service institution are registered). Request service information) (step S204),
Proceed to the next process.

FIG. 10 is a flowchart when the processing result of the service provision by the user application is reflected in various databases. At the mediation center, whether the process is a monthly process (when the process of paying for the service is performed monthly) and the processing status flag R33 of the request service DB 25
It is determined whether or not = "1" (step S300). If not, it is checked whether the processing status flag R33 = "2" (step S301). Processing status flag R3
If 3 is not "2", the processing is terminated and the process proceeds to the next processing. In step S301, the processing status flag R33 =
If it is "2", the contents of the service issued by the service organization are confirmed (step S303). The process is sorted according to the result of the service content confirmation (step S
305). If the service content is not correct, the process is terminated and the process proceeds to the next process.

If the service content is correct in step S305, or if the service is paid (there is a charge for the service), the value of the processing status flag is changed from "2" to "1", and the request service DB 25 Is updated (step S312). If the service is free of charge (there is no payment for the service), the request service DB 25 is updated assuming that the value of the processing status flag is changed from "2" to "0" (step S31).
2). After this update, the process proceeds to the next process. Here, specifically explaining with reference to FIG. 4, the reception ID is “2000020”.
2001 ", that is, the user ID is" A0000002 "
Since the processing status flag of the user of is "2",
Step S303 is performed. Here, if the service content issued by the service organization received at the mediation center is correct, the value of the processing status flag of this user is updated from “2” to “1” in step S312 (the reception ID is “20000202001”, ie, when the user ID is “A
0000002 "for the service ID" a
0002 ", and referring to the paid / free flag, which is an item of the request authentication DB 22, based on the service ID, the value is" 1 ", so that the service is paid).

If this is the case at step S300, the processing result of service provision (whether or not the processing has been completed normally) is confirmed (step S302). The processing is distributed according to the processing result (step S304). If the processing result is NG, if the user is registered in the blacklist DB 24 (the user has made an illegal application once in the past), the access flag R22 is set to "1" and the other By setting incorrect application information in the item, the user information is registered in the blacklist DB 24 (step S31).
0). If the user is not registered in the blacklist DB 24 (the user has never made an improper application in the past), the access flag R22 is set to “0” and other items are set to improper application information. Then, the user information is registered in the blacklist DB 24 (step S3).
10). If the processing result is OK in step S304,
The process is distributed depending on whether the user is a blacklist target person and the access flag R22 = "1" (step S306). If not, delete the applicable record of this application and use the same user IDR2
0 and the value of the access flag R22 in the record of the password R21 are updated from "1" to "0" (step S307). After this update, the request service DB 25
Is changed from "1" to "0" in the request service DB 25 (step S3).
11). Here, a specific description will be given with reference to FIG. 3. For a user whose user ID and password are “A0000003” and “A03”, the service institution =
If the fraud is canceled for the application of “a” and the service menu = “concert ticket” (when the payment is made later), the processing status flag =
Since it is “1” and is a blacklist subject with the access flag R22 = “1”, the process is determined (step S3).
06), the record corresponding to the application for which the fraud has been canceled is deleted, and the access flag R22 is set to the other record of the user whose user ID and password are “A0000003” and “A03”.
The blacklist DB 24 is updated by changing the access flag R22 from "1" to "0" (step S3).
07).

Next, if the user ID and the password are "A
0000001 "and" A01 ", the service requested by the user is" a "and the service menu is" concert ticket ", the service can be received. Judge if this application is an unauthorized application (step S30
4) Since the application information is service ID = “a0002” or the like and one record already exists (this is the second time due to the improper application), the access flag R22 = “1” (recorded already) Access flag R2
2 = “0” also as the access flag R22 = “1”)
Register in the blacklist DB 24 (Step S31)
0). Thereby, the user ID and the password are “A
The users of “0000001” and “A01” are denied access at the entrance because the access flag R22 is “1” in the future application, and the user ID and password are “A0000002” and “A02”. If the service applied by the user of the service institution is "b" and the service menu is "concert ticket", it is possible to receive the service,
If there is no fraud in this application, it is the same as the service ID of this application (step S308), so that the user ID and password are “A0000002” and “A02”.
Is deleted from the blacklist DB 24 (step S309).

However, if the service organization = “e” in the application where there is no fraud, the record is not deleted from the blacklist DB 24 because the service ID is different (step S 308). If it is determined in step S306 that the user is the subject of the blacklist and the service ID in this application is the same as the service IDR23, the process is distributed (step S3).
08). If not, the value of the processing status flag of the request service DB 25 is changed from "1" to "0", and the request service DB 25 is updated (step S31).
1). If applicable in step S308, the user information in the blacklist DB 24 is deleted (step S3).
09). After this deletion, the request service DB 25 is updated, assuming that the value of the processing status flag of the request service DB 25 is changed from "1" to "0" (step S31).
1). After this update, the process proceeds to the next process.

[0039]

According to the present invention, in an electronic application processing system installed between a user and a service organization, a service that is specific information including a user's name and address, and a user's unauthorized application information. Information including an institution name, a service menu, and the like, and specific information including a service institution name, an address, and the like of the service institution are collected and accumulated as various databases, and processing suitable for users and services is executed.
As a result, a data processing system capable of reducing troubles and improving user convenience can perform a series of processes for providing a service in electronic application.

[Brief description of the drawings]

FIG. 1 is an overall system configuration diagram showing a configuration of an electronic application data processing system according to the present invention.

FIG. 2 is a record layout diagram of a request authentication database according to the present invention.

FIG. 3 is a record layout diagram of a blacklist database according to the present invention.

FIG. 4 is a record layout diagram of a request service database according to the present invention.

FIG. 5 is a record layout diagram of a user authentication database according to the present invention.

FIG. 6 is a record layout diagram of a service institution database according to the present invention.

FIG. 7 is a flowchart for explaining a main processing routine and an after-processing routine of the operation of the electronic application processing in the data processing system of FIG. 1;

FIG. 8 is a flowchart for explaining a procedure process in the main process flowchart of FIG. 7;

FIG. 9 is a flowchart for explaining service request processing in the main processing flowchart of FIG. 7;

FIG. 10 is a flowchart for explaining an update process in the after-process flowchart of FIG. 7;

[Explanation of symbols]

 1 User terminal 2 Center management server 21 User authentication database 22 Request authentication database 23 Service institution database 24 Blacklist database 25 Request service database 3 Management server 31・ Service processing system

Claims (3)

[Claims] A first user information storage unit for storing user attribute information; and a service provider information storage unit for storing service provider attribute information. In a data processing system for electronic application that accepts and processes a service, a second user information storage that stores a service providing organization and service contents for a service requested by the user when the user performs a predetermined procedure process. Means for determining whether or not the user can access and provide the requested service received from the user by referring to the second user information storage means after receiving the application information from the user. Data processing system for electronic applications. 2. A data processing system for electronic applications according to claim 1, wherein a service received from a user is stored in a second user information storage means as information on said user. A data processing system for an electronic application, wherein the request is rejected when the content is handled. 3. The electronic application data processing system according to claim 1, further comprising a request service storage means for storing, as a history, the contents of the service requested by the user, and transmitting and requesting the service request to a service organization. Means for storing information about the service in the request service storage means, receiving a service processing result from the service organization, extracting a corresponding record from the request service storage means, and judging whether or not the request service and the processing result correspond to each other; Means for transferring a processing result to a user when the data is processed.