JP7583650B2 - Delegation application system, delegation application method, and delegation application program - Google Patents

Description

The present invention relates to a delegation application system, a delegation application method, and a delegation application program.

In recent years, the Electronic Power of Attorney Act (Act on the Dissemination of Electronic Power of Attorney) has been enacted, and guidelines for realizing a digital-first society have been formulated. The Electronic Power of Attorney Act mainly specifies that the authority to carry out procedures is delegated to employees of a corporation by the representative of the corporation. Meanwhile, in administrative and private procedures, delegation is carried out between people who are not in an employment relationship using a power of attorney that is created by signing or stamping a paper that describes the details of the delegation.

One example of a technology for electronically realizing a paper power of attorney is Patent Document 1. In the delegation system disclosed in Patent Document 1, the principal or agent creates a power of attorney electronically on a smart device or the like, and sends it to the principal's or agent's smart device using short-range wireless communication to create a token that includes a signature. When receiving a service such as a procedure, the agent who has received the delegation holds the agent terminal over an IC card reader connected to the service providing terminal to send the token to the service providing terminal, and the service providing terminal performs identity authentication and then verifies the details of the delegation. With this delegation system of Patent Document 1, applications by proxy can be made paperlessly.

JP 2016-206982 A

However, in the delegation system of Patent Document 1, the principal or the agent must create the power of attorney content by themselves depending on the procedure they wish to carry out, and the service provider must check the content of the power of attorney and confirm with the agent whether they have the authority to act on behalf of the agent for the service in question.

The present invention has been made in consideration of the above points, and aims to propose a delegation application system, delegation application method, and delegation application program that can easily create the application data and delegation data required to apply for a procedure on behalf of a principal or agent who has little knowledge of the contents of the procedure or delegation, and/or can assist a service provider in easily confirming the proxy authority of an agent.

In order to solve the above problem, the present invention provides an authorization application system that supports an application for a procedure to receive the provision of a service by an agent authorized by a principal, the system comprising: a principal terminal used by the principal; an agent terminal used by the agent; a verification support device that provides the principal terminal or the agent terminal with application data necessary for the application of the procedure and a format of authorization data proving that the application is authorized to the agent, and verifies the delegation data created based on the format; and a service providing device that provides the service requested with the application data when a successful result is obtained in the verification by the verification support device for the delegation data submitted together with the application data, and A delegation application system is provided in which the delegation data is received from the delegator terminal or the agent terminal and stored, and when applying for the procedure, the service providing device receives the application form data and the delegation data from the agent terminal and requests the verification support device to verify the delegation data, and the verification support device verifies the delegation data stored before applying for the procedure that corresponds to the delegation data that is the subject of the request and responds with the verification result to the service providing device, and if the verification result of the delegation data is successful, the service providing device provides the service requested in the application form data received from the agent terminal, and the delegation data can specify a delegation period indicating the validity period of the delegation data or a delegation number indicating the number of times the delegation data can be used, and when applying for the procedure, the verification support device verifies the delegation data based on the delegation period or the delegation number specified in the delegation data .

In addition, in order to solve the above problem, the present invention provides a delegation application method by a delegation application system that supports an application for a procedure to receive the provision of a service by an agent delegated by a principal, the delegation application system having a delegator terminal used by the principal, an agent terminal used by the agent, a verification support device, and a service providing device that provides a service, the method including a first step of, prior to the application for the procedure, the verification support device providing to the delegator terminal or the agent terminal a format of application form data necessary for the application for the procedure and delegation data proving that the application is delegated to the agent, a second step of, by the verification support device, receiving and retaining the application form data and the delegation data created based on each of the formats from the delegator terminal or the agent terminal, and a second step of, at the time of the application for the procedure, the service providing device receiving from the delegator terminal or the agent terminal a format of the application form data and the delegation data proving that the application is delegated to the agent, a third step of, upon receiving the application data and the delegation data from the agent terminal, requesting the verification support device to verify the delegation data; a fourth step of, by the verification support device, verifying the delegation data held before applying for the procedure that corresponds to the delegation data that is the subject of the request and responding to the service providing device with the verification result; and a fifth step of, by the service providing device, providing the service requested in the application data received from the agent terminal if the verification result of the delegation data is successful , wherein the delegation data can specify a delegation period indicating a validity period of the delegation data or a delegation number indicating the number of times the delegation data can be used effectively, and in the fourth step, the verification support device verifies the delegation data based on the delegation period or the delegation number specified in the delegation data .

In addition, in order to solve the above problem, the present invention provides a delegation application program to be executed by a computer constituting a delegation application system that supports an application for a procedure to receive the provision of a service by an agent delegated by a principal, the computer constituting the delegation application system including a delegator terminal used by the principal, an agent terminal used by the agent, a verification support device, and a service providing device that provides a service, the computer causing the verification support device to execute a process of providing, to the delegator terminal or the agent terminal, before the application for the procedure, application form data necessary for the application for the procedure and a format of delegation data that certifies that the application is delegated to the agent, the verification support device to execute a process of receiving and retaining the application form data and the delegation data created based on each of the formats from the delegator terminal or the agent terminal, and at the time of the application for the procedure, a delegation application program is provided which, upon receiving the application data and the delegation data from the agent terminal, causes the verification support device to execute a process of requesting verification of the delegation data, causes the verification support device to execute a process of verifying the delegation data held before applying for the procedure and corresponding to the delegation data that is the subject of the request, and responds with the verification result to the service providing device, and if the verification result of the delegation data is successful, causes the service providing device to execute a process of providing the service requested in the application data received from the agent terminal, wherein the delegation data can specify a delegation period indicating a validity period of the delegation data or a delegation number indicating the number of times the delegation data can be used, and the process that is executed by the verification support device when applying for the procedure verifies the delegation data based on the delegation period or the delegation number specified in the delegation data .

The present invention can assist a principal or agent in easily creating the application data and delegation data required for proxy application of a procedure, and/or assist a service provider in easily verifying the proxy authority of the agent.

1 is a block diagram showing an example of the overall configuration of a delegation application system 100 according to an embodiment of the present invention. 2 is a block diagram showing an example of the functional configuration of an agent terminal 101 and a delegator terminal 102. [0023] FIG. FIG. 2 is a block diagram showing an example of a functional configuration of a verification support device 103. 2 is a block diagram showing an example of a functional configuration of a service providing device 104. FIG. FIG. 11 is a diagram showing an example of personal information. FIG. 11 is a diagram illustrating an example of delegation history information. FIG. 13 is a diagram showing an example of an application data/delegation data format. FIG. 11 is a diagram illustrating an example of delegation data state information. FIG. 13 is a diagram illustrating an example of a validation rule. 10 is a sequence diagram showing an example of a processing procedure of a delegation request process executed by the delegation request system 100. FIG. 13 is a flowchart illustrating an example of a processing procedure of a first verification process. 10 is a flowchart illustrating an example of a processing procedure of a second verification process. FIG. 11 is a sequence diagram showing an example of a procedure for revocation processing.

Below, an embodiment of the present invention will be described in detail with reference to the drawings. Note that the same components and processes are designated by the same reference numerals throughout the drawings, and duplicated explanations will be omitted.

(1) Configuration FIG. 1 is a block diagram showing an example of the overall configuration of a delegation application system 100 according to an embodiment of the present invention. The delegation application system 100 is a system that supports the creation of data (application data and delegation data) required for proxy applications by a principal or agent regarding proxy applications for various procedures for receiving service provision, and supports the service provider in confirming the proxy authority of the agent. In this specification, application data is electronic data required for applying for a procedure. Also, delegation data is electronic data that proves that the principal has delegated the application to the agent. Note that, as will be described later, when the agent is a corporation, electronic data that proves that the corporation has delegated the application to its employee is also referred to as delegation data. When an agent applies for a procedure, it is necessary to submit these application data and delegation data to the service provider (service providing device 104).

As shown in FIG. 1, the delegation application system 100 is composed of multiple agent terminals 101 used by each agent, multiple delegator terminals 102 used by each delegator, a verification support device 103 that provides formats for delegation data and application data and verifies the delegation data, a service providing device 104 that provides specified services, a reading device 105 connected to the service providing device 104, and an external server 106 that provides external services, all connected to a network 107 such as the Internet.

The agent terminal 101 and the delegator terminal 102 are realized by a general computer or a smart device. The verification support device 103 and the external server 106 are realized by a general server computer. The service providing device 104 is realized by a general computer.

The external server 106 has a function of providing a specific external service, and is realized by a general server computer. As an external service, the external server 106 provides information that is required when a service provider verifies the proxy authority of an agent, but that is not held by the verification support device 103, specifically, for example, the agent's qualification information and information showing the relationship between the corporate representative and the employee.

The computer, smart device, or server computer that realizes each of the above devices (agent terminal 101, delegate terminal 102, verification support device 103, service providing device 104, external server 106) is configured by connecting hardware components such as a processor such as a CPU (Central Processing Unit), memory, external storage device, communication device such as a NIC (Network Interface Card), input device such as a keyboard or mouse, and output device such as a display or printer via a bus or the like. Note that each of the above hardware components is not limited to being mounted within a single computer, smart device, or server computer, and for example, any part of the input device, output device, processing device, or storage device may be configured by another computer, etc. connected via network 107.

The reading device 105 is realized by an IC card reader or the like having a function of reading the specified information using short-range wireless communication. In this example, an independent reading device 105 is described as a specific example of a means for acquiring the specified information from the agent terminal 101 or the delegator terminal 102 of the user who wishes to receive the service, but in the delegation application system 100 according to this embodiment, the reading device 105 is not necessarily a required component and may be replaced by other means for acquiring the above-mentioned specified information, and the service providing device 104 may also have a similar function.

(1-1) Agent terminal 101, delegator terminal 102
2 is a block diagram showing an example of a functional configuration of the agent terminal 101 and the delegator terminal 102. As shown in FIG. 2, the agent terminal 101 and the delegator terminal 102 include a calculation unit 201, a storage unit 202, The computing unit 201 includes a communication unit 203 and an input/output unit 204, which are connected by a bus or the like. The computing unit 201 is realized by the processor executing a program stored in the memory or an external storage device. The unit 202 is realized by a memory or an external storage device. The communication unit 203 is realized by a communication device. The input/output unit 204 is realized by an input device or an output device.

The calculation unit 201 assists in the creation of delegation data and application data, manages the status of the delegation data, and signs the delegation data. As functional units that realize these functions, the calculation unit 201 has a data creation assistance unit 205, a delegation data status management unit 206, and an electronic signature assignment unit 207.

The data creation support unit 205 supports the agent or delegator in creating delegation data and application data based on the information acquired from the verification support device 103 and the information stored in the memory unit 202. The delegation data status management unit 206 manages the status (valid or invalid) of the delegation data stored in the verification support device 103. The electronic signature assignment unit 207 assigns an electronic signature to the delegation data or application data created on its own terminal.

The storage unit 202 stores personal information of each of the delegators or agents, and information regarding past delegations. As shown in FIG. 2, the storage unit 202 has a personal information storage unit 208 and a delegation history storage unit 209.

The personal information storage unit 208 stores personal information (see FIG. 5) indicating the name, date of birth, address, etc. of the principal or agent. The delegation history storage unit 209 stores delegation history information (see FIG. 6) indicating past delegation data, past application form data, and past delegation history.

The communication unit 203 transmits and receives information to and from other devices in the delegation application system 100 via the Internet (network 107) or short-range wireless communication. Specifically, the communication unit 203 transmits the results of processing in the calculation unit 201 to other devices (the agent terminal 101, the delegator terminal 102, the verification support device 103, the service providing device 104, or the reading device 105), and receives information necessary for processing in the calculation unit 201 and information stored in the memory unit 202 from the other devices.

The input/output unit 204 accepts input from the agent or delegator who operates the terminal, and outputs specified information by displaying it on a display, etc.

(1-2) Verification support device 103
Fig. 3 is a block diagram showing an example of a functional configuration of the verification support device 103. As shown in Fig. 3, the verification support device 103 includes a calculation unit 301, a storage unit 302, a communication unit 303, and an input/output unit 304, which are connected by a bus or the like. The calculation unit 301 is realized by a processor executing a program stored in a memory or an external storage device. The storage unit 302 is realized by a memory or an external storage device. The communication unit 303 is realized by a communication device. The input/output unit 304 is realized by an input device or an output device.

The calculation unit 301 manages the format of the application data and the delegation data, manages or verifies the delegation data, and manages the results of the management and verification of the delegation data as evidence. As functional units that realize these functions, the calculation unit 301 has a format management unit 305, a delegation data management unit 306, a delegation data verification unit 307, and an evidence management unit 308.

The format management unit 305 manages the formats of application data and delegation data. Specifically, for example, when a request for providing a format is received from the agent terminal 101 or the delegator terminal 102, the format management unit 305 provides the desired format stored in the format storage unit 309 to the requester. Also, for example, when an operation such as updating or deleting a format is performed by the administrator of the verification support device 103, the format management unit 305 performs processing on the target format according to the operation.

The delegation data management unit 306 manages the delegation data. Specifically, for example, the delegation data management unit 306 accepts the delegation data transmitted from the agent terminal 101 or the delegator terminal 102, and stores it in the delegation data status storage unit 310. In addition, for example, the delegation data management unit 306 manages the validity status (valid or invalid) of the delegation data stored in the delegation data status storage unit 310, and also responds to requests to invalidate the delegation data from other devices.

Upon receiving a request from the service providing device 104, the delegation data verification unit 307 verifies the delegation data based on the information stored in the memory unit 302 and the information acquired from the external server 106. The trail management unit 308 manages the delegation data and the trail showing the results of the verification.

The storage unit 302 stores the formats of the application data and delegation data, information indicating the state of the delegation data, trail information, and validation rules, etc. As shown in FIG. 3, the storage unit 302 has a format storage unit 309, a delegation data state storage unit 310, a trail information storage unit 311, and a validation rule storage unit 312.

The format holding unit 309 holds the formats of the application data and delegation data (see FIG. 7). As described later in FIG. 7, in this description, a format that integrates the application data and delegation data (application data/delegation data format 530) is shown as an example of a format held by the format holding unit 309, but the application data format and the delegation data format may be prepared separately and held in the format holding unit 309.

The delegation data status holding unit 310 holds delegation data status information (see FIG. 8) indicating the validity status (valid or invalid) of the delegation data. The delegation data status holding unit 310 can also hold application data and delegation data. The trail information holding unit 311 holds trail information that records the results of management or verification of the delegation data. The verification rule holding unit 312 holds verification rules based on laws and regulations, etc., and verification rules received from the service provider (see FIG. 9).

The communication unit 303 transmits and receives information to and from other devices in the delegation application system 100 via the network 107. Specifically, the communication unit 303 transmits the results of processing in the calculation unit 301 to the other devices (the agent terminal 101, the delegator terminal 102, or the service providing device 104), and receives information necessary for processing in the calculation unit 301 and information held in the memory unit 302 from the other devices (the agent terminal 101, the delegator terminal 102, the service providing device 104, or the external server 106).

The input/output unit 304 accepts input from the administrator of the verification support device 103.

(1-3) Service providing device 104
Fig. 4 is a block diagram showing an example of a functional configuration of the service providing device 104. As shown in Fig. 4, the service providing device 104 includes a calculation unit 401, a storage unit 402, a communication unit 403, and an input/output unit 404, which are connected by a bus or the like. The calculation unit 401 is realized by a processor executing a program stored in a memory or an external storage device. The storage unit 402 is realized by a memory or an external storage device. The communication unit 403 is realized by a communication device. The input/output unit 404 is realized by an input device or an output device.

The calculation unit 401 acquires information read by the reading device 105 using short-range wireless communication, requests verification of delegation data, and manages the trail of a series of processes related to the application. As functional units that realize these functions, the calculation unit 401 has a read information acquisition unit 405, a verification request unit 406, and a trail management unit 407.

The read information acquisition unit 405 acquires information on the application data or delegation data read by the reading device 105. The verification request unit 406 requests the verification support device 103 to verify the delegation data and receives the result. The trail management unit 407 manages the trail of a series of processes related to the application.

The memory unit 402 stores trail information. The memory unit 402 has a trail information storage unit 408 that stores trail information that records the trail of a series of processes related to an application.

The communication unit 403 transmits and receives information to and from other devices in the delegation application system 100 via the network 107. Specifically, the communication unit 403 transmits the results of processing in the calculation unit 401 to other devices (the agent terminal 101 and the verification support device 103), and receives information necessary for processing in the calculation unit 401 and information stored in the memory unit 402 from other devices (the verification support device 103).

The input/output unit 404 accepts input from the administrator of the service providing device 104 and input from users who wish to receive services provided by the service providing device 104, and receives information read by the reading device 105.

The internal configurations of the agent terminal 101, the delegator terminal 102, the verification support device 103, and the service providing device 104 have been described above with reference to Figures 2 to 4. In this specification, the various programs or parts thereof executed by each of the calculation units 201, 301, and 401 may be referred to as "units," "means," "functions," "modules," etc. In addition, each storage unit 202, 302, and 402 may be configured with multiple storage units each having a different storage method, such as an RDB (Relational DataBase), a file server, or a KVS (Key-Value Store), depending on the size and format of the program or data to be stored. In addition, a part or all of the data equivalent to the program or data stored in each storage unit 202, 302, and 402 may be provided from one or more other servers equipped with non-transient storage devices connected to a network 107 such as the Internet, or via a non-transient storage medium. In addition, each component shown in Figures 2 to 4 does not need to be physically separated, and for example, one component may serve as another component. Additionally, components within one terminal or device may be distributed across multiple devices.

(2) Data Structure Below, examples of data structures will be described for various data held in the delegation request system 100 according to this embodiment.

5 is a diagram showing an example of personal information. The personal information 510 shown in FIG. 5 is an example of personal information stored by the personal information storage unit 208 in the agent terminal 101 and the delegator terminal 102. The personal information 510 is configured with the data items of name 511, address 512, date of birth 513, and telephone number 514. The personal information 510 is recorded for each delegator or agent. Although FIG. 5 shows only information for one person, the personal information 510 can hold information for multiple people. In addition, the data items recorded in the personal information 510 are not limited to the example in FIG. 5. The personal information 510 may be set individually by the delegator or agent, or may be read from an IC card or the like held by the agent terminal 101 or the delegator terminal 102 and recorded.

In personal information 510, name 511 is set to the name of the subject (agent or delegate). Address 512 is an item in which the address of the subject is set, such as city, ward, town, village, district, block, number, building name, room number, etc. A postal code or prefecture name may also be set. Date of birth 513 is an item in which the date of birth of the subject is set, such as in the Gregorian or Japanese calendar. Phone number 514 is an item in which the phone number of the subject is set, and multiple phone numbers may be set, such as a home, mobile phone, and work phone.

Figure 6 is a diagram showing an example of delegation history information. The delegation history information 520 shown in Figure 6 is an example of delegation history information held by the delegator history holding unit 209 in the agent terminal 101 and the delegator terminal 102. The delegation history information 520 is configured to have the data items of a delegation data ID 521, delegator information 522, agent information 523, delegation content 524, and revocation status 525.

The delegation data ID 521 is a unique identifier for each piece of delegation information (delegation data), and may be a universally unique identifier (UUID), or may be issued sequentially by the verification support device 103 during the delegation application process described later in FIG. 10.

Delegator information 522 and agent information 523 are personal information of the delegator and agent in the target delegation data, and the number of items included in the personal information may increase or decrease depending on the type of application. Delegation content 524 sets the content that the delegator delegates to the agent, and may be written as, for example, "obtain a copy of the resident's certificate."

The expiration status 525 indicates whether the target delegation data is currently valid or expired. For example, if the delegation data has been used and expired, it is described as "Expired (used)" or the like. The reason why the delegation data expires may be due to a validity period or number of valid times previously set in the delegation data (see delegation period/number of times 537 in FIG. 7), or due to a designation of expiration by the delegator (described later in FIG. 13). If the delegation data is valid, the expiration status 525 may simply be described as "valid," or the number of times it can be used or a deadline may be set.

Figure 7 is a diagram showing an example of an application data/delegation data format. The application data/delegation data format 530 in Figure 7 is an example of a format stored in the format storage unit 309 of the verification support device 103, and shows a format in which one piece of application data and delegation data are integrated. The application data/delegation data format 530 is composed of data items of application data name 531, applicant information 532, application date 533, information related to the application 534, delegation content 535, agent information 536, and delegation period/number of times 537. Note that the application data/delegation data format 530 may have different data items depending on the application target (e.g., application data name 531).

The name of the application is set in the application data name 531, for example, "Application for Publication of Copy of Resident Record, etc." The applicant's personal information such as the applicant's name, address, and telephone number is set in the applicant information 532. The applicant information 532 is not set by the verification support device 103, but by the agent terminal 101 or the delegator terminal 102. The application date 533 is set as the date on which the application is made. The application date 533 may be entered by the applicant, or may be automatically set by the verification support device 103, the agent terminal 101, or the delegator terminal 102 at the time of application.

Information about the application 534 is set with specific details that the principal or agent needs to specify or select with respect to the application. Specifically, for example, if the application is for the issuance of a copy of a resident's certificate, the information about the application 534 allows the user to select and set whether the resident's certificate to be issued is a resident's certificate or a cancelled resident's certificate.

The delegation content 535 is set with the content of the delegation in the application, for example, "obtaining a copy of the resident's certificate." The delegation content 535 may be fixed for each application form or may be selectable. The agent information 536 is set with personal information such as the agent's name, address, and telephone number. The agent information 536 is not set by the verification support device 103, but by the agent terminal 101 or the delegator terminal 102.

In the delegation period/number of times 537, the validity conditions of the delegation in the delegation data (valid number of times and validity period) are set. The validity conditions of the delegation may be determined for each application form, or may be set individually by the applicant. As a specific setting, for example, if the use is valid only this time, "1 time" is written, and if the use is valid within one week without specifying the number of times of use, a date and time one week from now is written. In addition, both the validity period and the validity number of times may be set. Note that the format stored in the format storage unit 309 is not limited to a format in which application data and delegation data are integrated, such as the application data/delegation data format 530, and the format related to the application and the format related to the delegation (proxy) may be managed separately. However, if they are managed separately, it is necessary to store the formats for both purposes in correspondence with each other.

Figure 8 is a diagram showing an example of delegation data status information. Delegation data status information 540 in Figure 8 is an example of delegation data status information stored in the delegation data status storage unit 310 of the verification support device 103. The delegation data status information 540 is configured to have data items of delegation data ID 541 and revocation status 542.

The delegation data ID 541 is the same as the delegation data ID 521 described in the delegation history information 520 of FIG. 6. Also, the revocation status 542 is the same as the revocation status 525 described in the delegation history information 520 of FIG. 6.

Figure 9 is a diagram showing an example of a validation rule. Validation rule 550 in Figure 9 is an example of a validation rule stored in the validation rule storage unit 312 of the verification support device 103. Validation rule 550 is configured to have data items of application form data name 551 and validation rule 552.

The application data name 551 is the same as the application data name 531 described in the application data/delegation data format 530 in FIG. 7. The validation rules for each application are set in the validation rules 552. Specific validation rules may, for example, be set such as that the applicant's electronic signature is required, and that maximum authorization from the corporation to employees is permitted.

(3) Processing The following describes in detail the processing executed in the delegation request system 100 according to this embodiment.

(3-1) Delegation Application Processing Fig. 10 is a sequence diagram showing an example of the processing procedure of the delegation application processing executed by the delegation application system 100. Here, the delegation application processing refers to a series of processes in which the delegator or agent supports the creation of application data and delegation data before applying for the procedure, and supports the service provider's verification of the delegation data when applying for the procedure. In Fig. 10, among the agent terminals 101, the representative terminal of the corporation that receives delegation from the agent is designated as agent terminal 101B, and the employee terminal of the corporation is designated as agent terminal 101A.

As shown in FIG. 10, first, the delegator operates the delegator terminal 102 to obtain application data and delegation data format related to the service to be provided from the verification support device 103 (step S101).

Next, the delegator operates the delegator terminal 102 to create application data and delegation data according to the format acquired in step S101 (step S102). At this time, the data creation support unit 205 supports the delegator in creating the application data and delegation data by preprinting (presenting) information about the application and the agent based on the delegator's personal information stored in the personal information storage unit 208 and the past application data and delegation data stored in the delegation history storage unit 209. Note that a corporation can also be designated as the delegated agent, and in that case, information such as the corporation's name and representative is entered into the agent information.

Next, the delegator operates the delegator terminal 102 to attach an electronic signature to the application data and delegation data created in step S102 (step S103). The attachment of the electronic signature is performed by the electronic signature attachment unit 207. At this time, depending on the service to be provided, the electronic signature of the application data may be omitted. In addition, when attaching the electronic signature, the electronic signature attachment unit 207 may create the signature data using a private key stored in an IC card or the like.

Next, the delegator operates the delegator terminal 102 to transmit the created application data and delegation data to the verification support device 103 (step S104). The verification support device 103 assigns a unique delegation data ID to each piece of delegation data, stores the received application data and delegation data in the delegation data status storage unit 310, and sends an acceptance response including the delegation data ID to the delegator terminal 102 (step S105).

Next, the principal transmits the application data and delegation data from the principal terminal 102 to the agent terminal 101 using short-range wireless communication or the Internet (network 107) (step S106). Note that in FIG. 10, the processing of steps S106 to S111 is shown assuming that a corporation has been designated as the agent, but if the designated agent is an individual (e.g., the user of the agent terminal 101A) rather than a corporation, the application data and delegation data are transmitted directly from the principal terminal 102 to the agent terminal 101A in step S106, and the processing of steps S107 to S111 is skipped.

If a corporation is designated as the agent, the representative of the corporation who received the application data and delegation data in step S106 operates the agent terminal 101B to create delegation data for the employee (step S107) and affixes an electronic signature (step S108). Next, the representative of the corporation operates the agent terminal 101B to transmit the delegation data created in steps S107-S108 and the application data received in step S106 to the verification support device 103 (step S109). In step S109, at least information indicating the delegation relationship between the corporation and the employee (e.g., delegation data from the corporation to the employee) and information that can identify the content of the application delegated from the corporation to the employee (e.g., application data) are transmitted to the verification support device 103, so that the verification support device 103 can verify the validity of the delegation from the corporation to the employee using these data in verifying the delegation data described below. Then, the verification support device 103 that received the data in step S109 assigns a unique delegation data ID to each piece of delegation data, stores the received application data and delegation data in the delegation data status storage unit 310, and sends a reception response including the delegation data ID to the agent terminal 101B (step S110). After step S110, the representative of the corporation operates the agent terminal 101B to send the application data and delegation data to the agent terminal 101A (step S111).

In step S107, the representative of the corporation can create delegation data for the employee in association with the delegation data received in step S106. Specifically, for example, by entering the delegation data ID of the delegation data received in step S106 in the delegation content of the delegation data for the employee, it is possible to create delegation data that associates the delegation to the corporation with the delegation from the corporation to the employee. In addition, the above processing (steps S107 to S110) regarding the delegation from the corporation to the employee may be performed in advance prior to step S101 as delegation content that allows multiple applications.

The processing of steps S101 to S111 described above is performed before the procedure is applied for, and the delegation application system 100 supports the creation of the application form data and the delegation data. The processing of steps S112 to S119 described below is performed when the procedure is applied for, and the delegation application system 100 supports the verification of the delegation data.

When applying for a procedure, the agent (employee of the corporation) holds the agent terminal 101A over the reading device 105 attached to the service providing device 104, and has the reading device 105 read the application form data and delegation data received in step S111 (step S112). In addition, the agent presents an identity verification document to the service provider, or has the reading device 105 read identity verification information stored on an IC card or the like. The reading device 105 then transmits the results of these readings to the service providing device 104 (step S113).

Next, the service provider uses the service providing device 104 to request the verification support device 103 to verify the delegation data (step S114). Specifically, the verification request unit 406 of the service providing device 104 sends a request to verify the delegation data to the delegation data verification unit 307 of the verification support device 103 via the network 107, together with predetermined information (which may be the data itself, but includes at least the delegation data ID) contained in the delegation data and application data, etc.

The verification support device 103 (delegation data verification unit 307) that receives the verification request checks whether verification is possible using only the data stored in the memory unit 302, and if verification is not possible, requests the external server 106 to provide the data (verification data) that is missing for verification (step S115). In response to the request, the external server 106 that provides a specified external service transmits verification data such as the proxy's qualification information to the verification support device 103 (step S116).

Next, the verification support device 103 (delegation data verification unit 307) verifies the delegation data using the data stored in the storage unit 302 and the verification data received in step S116 (step S117), and responds with the verification result to the service providing device 104 (step S118). At this time, the verification support device 103 may store the verification result as trail information in the trail information storage unit 311. Details of the verification process by the verification support device 103 will be described later with reference to FIGS. 11 and 12.

Next, the service provider verifies the proxy authority of the agent based on the verification result received by the service providing device 104, and if the proxy authority for this application is approved, provides the agent with the service requested in the application data (step S119). The service may be provided in a form where it is handed over directly to the agent, or in a form where specified data is sent from the service providing device 104 to the agent terminal 101A or the agent terminal 101B.

By performing the processing of steps S101 to S119 in FIG. 10 as described above, the delegation application system 100 can assist in the creation of application data and delegation data, as well as assist in the verification of the delegation data.

In the process shown in FIG. 10, obtaining the format of the application data and delegation data (step S101) and creating the application data and delegation data (step S102) may be performed by the agent using the agent terminal 101 (101A, 101B). In this case, the agent performs a process of transmitting the created application data and delegation data from the agent terminal 101 to the delegator terminal 102 via short-range wireless communication or the Internet (network 107).

The service may also be provided over the network 107, in which case in step S112 the agent transmits the application data and delegation data from the agent terminal 101 (101A, 101B) to the service providing device 104 via the network 107.

10, in the delegation application process, the delegation data verification unit 307 of the verification support device 103 executes a verification process to verify the delegation data by using the data stored in the storage unit 302 and the verification data acquired from the external server 106. The detailed processing procedure of the verification process will be described below.

Figure 11 is a flowchart showing an example of the processing procedure of the first verification process. The first verification process corresponds to a series of processes that are commonly executed regardless of the type of application data among the verification processes of delegation data in this embodiment.

As shown in FIG. 11, first, the delegation data verification unit 307 acquires the delegation data, application data, and identity verification information received from the service providing device 104, and the verification data received from the external server 106 (step S201).

Next, the delegation data verification unit 307 checks whether the application date written in the application data is within the delegation period written in the delegation data (step S202). If the delegation data specifies the number of delegations rather than the delegation period, the confirmation in step S202 may be skipped. The delegation period specifies the validity period of the delegation data, and the number of delegations specifies the number of times the delegation data can be used effectively. If the application date is within the delegation period (YES in step S202), the process proceeds to step S203. On the other hand, if the application date is outside the delegation period (NO in step S202), the delegation data verification unit 307 determines that the verification of the delegation data has failed, and ends the process.

In step S203, the delegation data verification unit 307 refers to the delegation data status information (e.g., delegation data status information 540 in FIG. 7) stored in the delegation data status storage unit 310, and checks the revocation status corresponding to the delegation data ID assigned to the delegation data. If the revocation status corresponding to the delegation data ID is "valid" (YES in step S203), the process proceeds to step S204. On the other hand, if the revocation status corresponding to the delegation data ID is "revoked" (NO in step S203), the delegation data verification unit 307 determines that the verification of the delegation data has failed, and terminates the process.

In step S204, the delegation data verification unit 307 verifies the electronic signature of the delegation data to check whether the verification is successful. If delegation has been made from a corporation to an employee, the electronic signature is checked for each of the two pieces of delegation data: the delegation data from the delegator to the corporation, and the delegation data from the corporation to the employee. If the electronic signature is valid (YES in step S204), the process proceeds to step S205. On the other hand, if the electronic signature has expired (NO in step S204), the delegation data verification unit 307 determines that verification of the delegation data has failed, and ends the process.

In step S205, the delegation data verification unit 307 verifies the electronic signature of the application data and checks whether the verification is successful. If the electronic signature is valid (YES in step S205), the process proceeds to step S206. On the other hand, if the electronic signature has expired (NO in step S205), the delegation data verification unit 307 determines that the verification of the delegation data has failed, and ends the process.

In step S206, the delegation data verification unit 307 compares the identity verification information of the agent with the agent information written in the delegation data (e.g., agent information 536 in FIG. 7) to confirm whether information such as "name" and "address" match. If the identity verification information matches the agent information in the delegation data (YES in step S206), the process proceeds to step S207. On the other hand, if the identity verification information does not match the agent information in the delegation data (NO in step S206), the delegation data verification unit 307 determines that verification of the delegation data has failed and ends the process.

In step S207, the delegation data verification unit 307 checks whether the application data and the delegation data correspond. This is to check whether the delegation data corresponding to the application data has been created sufficiently, and can be achieved by checking whether all required items in the delegation data are present. Alternatively, this can be achieved by checking whether the application data name and the delegation content correspond. If the application data and the delegation data do not correspond (NO in step S207), the delegation data verification unit 307 determines that the verification of the delegation data has failed, and terminates the process.

On the other hand, if the application data and the delegation data correspond in step S207 (YES in step S207), since all checks in steps S202 to S207 have been completed successfully, the delegation data verification unit 307 determines that the verification of the delegation data has been successful and terminates the process.

By executing the processes of steps S201 to S207 in FIG. 11, the delegation data verification unit 307 can verify the delegation data by a common verification process that is independent of the type of application data. Note that when delegation is made from a corporation to an employee, confirmation processes may be performed separately for the two delegation data: the delegation data from the delegator to the corporation, and the delegation data from the corporation to the employee.

The order of execution of each confirmation process shown in steps S202 to S207 may be changed. Also, the confirmation items are not limited to the example in FIG. 11, and may be changed in response to changes in laws, regulations, security standards, etc.

Figure 12 is a flowchart showing an example of the processing procedure of the second verification process. The second verification process corresponds to a series of processes executed by applying a verification rule according to the type of application form data, among the verification processes of delegation data in this embodiment. The verification rules are stored in the verification rule storage unit 312 of the verification support device 103. The second verification process is executed in addition to the first verification process described above.

As shown in FIG. 12, first, the delegation data verification unit 307 acquires the delegation data and application data received from the service providing device 104, the verification data received from the external server 106, and the verification rules stored in the verification rule storage unit 312 (step S301). Note that the information acquired in the first verification process does not need to be acquired again in step S301, and identity verification information of the agent may also be acquired in step S301.

Next, the delegation data verification unit 307 checks whether there is a problem with the delegator's electronic signature in the application data (step S302). If the application data does not require the delegator's electronic signature, or if the application data requires the delegator's electronic signature and an electronic signature has been attached (YES in step S302), the process proceeds to step S303. On the other hand, if an electronic signature is required but an electronic signature has not been attached to the application data (NO in step S302), the delegation data verification unit 307 determines that verification of the delegation data has failed and terminates the process.

In step S303, the delegation data verification unit 307 checks whether there are any problems with the changes made to the application data by the agent. If the application data has not been changed by the agent or the agent is able to change the application data (YES in step S303), the process proceeds to step S304. On the other hand, if the application data has been changed even though the agent is not able to change the application data (NO in step S303), the delegation data verification unit 307 determines that verification of the delegation data has failed and terminates the process.

In step S304, the delegation data verification unit 307 checks whether there is a problem with the delegation from the corporation to the employee. If the delegation data has not been created by the employee, or if delegation from the corporation to the employee is permitted and the delegation data has been created by the employee (YES in step S304), the process proceeds to step S305. On the other hand, if delegation from the corporation to the employee is permitted, or if delegation from the corporation to the employee is not permitted but the delegation data has been created by the employee (NO in step S304), the delegation data verification unit 307 determines that verification of the delegation data has failed and ends the process.

In step S305, the delegation data verification unit 307 checks whether there is a problem with the qualifications of the agent. If the agent is required to have qualifications, the delegation data verification unit 307 uses the results of the inquiry to the external server 106 (verification data) to check whether the agent has the specified professional qualifications, etc. If the necessary qualification information for the agent cannot be confirmed (NO in step S305), the delegation data verification unit 307 determines that the verification of the delegation data has failed and terminates the process.

On the other hand, if no qualifications are required for the agent in step S305 or the necessary qualification information for the agent is confirmed (YES in step S305), since all checks in steps S302 to S305 have been completed with a normal judgment, the delegation data verification unit 307 determines that the verification of the delegation data has been successful and terminates the process.

By executing the processes of steps S301 to S305 in FIG. 12 as described above, the delegation data verification unit 307 can verify the delegation data through a verification process that applies verification rules according to the type of application data.

Then, in the case of an application for which no validation rule is set, when the first validation process results in a successful validation, and in the case of an application for which a validation rule is set, when both the first and second validation processes result in a successful validation, the delegation data validation unit 307 determines that the validation of the delegation data for the application has been successful. When the validation of the delegation data is successful, if the number of delegations is set in the delegation data (for example, see the delegation period/number of times 537 of the application data/delegation data format 530 in FIG. 7), the delegation data management unit 306 updates the delegation data status information (for example, the delegation data status information 540 in FIG. 8) held in the delegation data status holding unit 310. Specifically, when the validation of the delegation data is successful, one delegation count is consumed, and as a result, when the remaining number of delegations set in the delegation data is exhausted, the expiration status 542 of the delegation data status information 540 is updated to "expired (used)".

On the other hand, in the case of an application for which no verification rule is set, if the first verification process results in a failed verification, or in the case of an application for which a verification rule is set, if at least either the first or second verification process results in a failed verification, the delegation data verification unit 307 determines that the verification of the delegation data for the application has failed.

The trail management unit 308 also records the result of the verification of the delegation data by the delegation data verification unit 307 as trail information, and stores it in the trail information storage unit 311. When recording the trail information, it is possible to record not only the verification result, but also the reason why the verification failed. The trail management unit 308 may transmit the trail information to the service providing device 104, and in this case, the trail management unit 407 of the service providing device 104 stores the received trail information in the trail information storage unit 408.

(3-3) Revocation Processing In this embodiment, the delegator operates the delegator terminal 102, which allows the delegator data status management unit 206 of the delegator terminal 102 to revoke the delegation data stored in the verification support device 103. This revocation processing can be executed at a timing determined or desired by the delegator. In addition, by executing the revocation processing at a predetermined cycle, the delegation data for which a delegation period is specified can be revoked when the delegation period ends. The detailed processing procedure of the revocation processing will be described below.

Figure 13 is a sequence diagram showing an example of the processing procedure for revocation processing. In Figure 13, the processing procedure example is shown assuming that the revocation processing is executed at the discretion or request of the delegator.

According to FIG. 13, first, the delegator operates the delegator terminal 102 to select the delegation data to be revoked (step S401). Next, the delegation data status management unit 206 of the delegator terminal 102 sends a revocation request to the verification support device 103 to request the revocation of the delegation data selected in step S401 (step S402). At this time, the delegation data ID attached to the selected delegation data is sent together with the revocation request.

Next, the delegation data management unit 306 of the verification support device 103 changes the revocation status of the delegation data stored in the delegation data status storage unit 310, which corresponds to the delegation data ID received in step S402, to "revoked" (step S403). Note that before revoking the delegation data in step S403, the delegation data management unit 306 checks whether the delegator terminal 102 that sent the revocation request is the same as the delegator terminal that sent the delegation data initially (step S104 in FIG. 10), in order to determine whether the revocation request is a valid request, and authenticates the delegator who issued the revocation request to check whether it is the same as the delegator who sent the delegation data initially.

Next, the verification support device 103 (delegation data management unit 306) responds with the result of the revocation performed in step S403 to the delegator terminal 102 that sent the revocation request (step S404). Then, the delegation data status management unit 206 of the delegator terminal 102 changes the revocation status of the delegation data that is the subject of the revocation request and is stored in the delegation history storage unit 209 to "revoked" (step S405), and the revocation process ends.

By executing the processing of steps S401 to S405 in FIG. 13 as described above, the delegation application system 100 can invalidate the delegation data according to the wishes of the delegator or the expiration of the specified validity period (delegation period), thereby preventing the misuse or unauthorized use of the delegation data.

As described above, according to the delegation application system 100 of this embodiment, even a delegator or agent with little knowledge of the contents of the procedure or delegation can easily create the delegation data and application form data required for proxy application of the procedure by providing a format from the verification support device 103. Furthermore, according to the delegation application system 100 of this embodiment, when a service application is made using the delegation data and application form data created as described above, the verification support device 103 verifies the delegation data, so that the service provider can easily confirm the proxy authority of the agent. Furthermore, in the verification of the delegation data, the legitimacy can be verified not only of the delegation data delegated by the delegator to the agent, but also of the delegation data delegated by the agent of the corporation to the employee of the corporation, so that it is possible to respond to practical application procedures for various services.

The present invention is not limited to the above-described embodiment, but includes various modified examples. For example, the above-described embodiment has been described in detail to clearly explain the present invention, and is not necessarily limited to having all of the configurations described. In addition, it is possible to add, delete, or replace part of the configuration of the embodiment with other configurations.

Furthermore, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in hardware, in part or in whole, for example by designing them as integrated circuits. Furthermore, the above-mentioned configurations, functions, etc. may be realized in software, by a processor interpreting and executing a program that realizes each function. Information on the programs, tables, files, etc. that realize each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

In addition, the control lines and information lines shown in the drawings are those that are considered necessary for explanation, and do not necessarily show all control lines and information lines on the product. In reality, it can be assumed that almost all components are interconnected.

100 Delegation application system 101 Agent terminal 102 Delegator terminal 103 Verification support device 104 Service providing device 105 Reading device 106 External server 107 Network 201, 301, 401 Calculation unit 202, 302, 402 Storage unit 203, 303, 403 Communication unit 204, 304, 404 Input/output unit 205 Data creation support unit 206 Delegation data status management unit 207 Digital signature assignment unit 208 Personal information storage unit 209 Delegation history storage unit 305 Format management unit 306 Delegation data management unit 307 Delegation data verification unit 308 Trail management unit 309 Format storage unit 310 Delegation data status storage unit 311 Trail information storage unit 312 Verification rule storage unit 405 Read information acquisition unit 406 Verification request unit 407 Trail management unit 407
408 Trail information storage unit 510 Personal information 520 Delegation history information 530 Application data/delegation data format 540 Delegation data status information 550 Verification rule

Claims (10)

A delegation application system that supports an application for a procedure to receive a service by an agent delegated by a delegator, comprising:
A delegator terminal used by the delegator;
an agent terminal used by the agent;
a verification support device that provides the delegator terminal or the agent terminal with a format of application form data required for the application of the procedure and delegation data that certifies that the application is delegated to the agent, and verifies the delegation data created based on the format;
a service providing device that provides a service requested in the application data when a successful result is obtained in the verification by the verification support device for the delegation data submitted together with the application data;
Equipped with
Before applying for the above procedure,
the verification support device transmits formats of the application data and the delegation data to the delegator terminal or the agent terminal, receives the application data and the delegation data created based on each of the formats from the delegator terminal or the agent terminal, and stores the application data and the delegation data;
When applying for the above procedure,
When the service providing device receives the application data and the delegation data from the agent terminal, the service providing device requests the verification support device to verify the delegation data;
the verification support device verifies the delegation data that corresponds to the requested delegation data and that was held before the procedure was applied for, and responds with the verification result to the service providing device;
the service providing device provides the service requested in the application data received from the agent terminal when the verification result of the delegation data is successful;
In the delegation data, a delegation period indicating a valid period of the delegation data or a delegation number indicating a valid number of times the delegation data can be used can be specified;
When applying for the procedure, the verification support device verifies the delegation data based on the delegation period or the delegation count specified in the delegation data.
A delegation application system comprising: 2. The delegation application system according to claim 1, wherein the delegation data is provided with an electronic signature of the delegator when the delegation data is created. The delegation data includes first delegation data that the delegator delegates to a corporation as the agent, and second delegation data that the corporation delegates to an employee of the corporation;
When the first delegation data is created by the delegator terminal, and a first agent terminal used by the corporation creates the second delegation data based on the first delegation data and transmits it to a second agent terminal used by the employee,
the verification support device receives and holds the first delegation data from the delegator terminal, and receives and holds the second delegation data from the first agent terminal;
When the second delegation data is submitted from the second agent terminal to the service providing device together with the application data,
The delegation application system according to claim 1 , wherein the verification support device verifies not only the second delegation data but also the related first delegation data in response to the request from the service providing device. the verification support device holds delegation data state information for managing a validity state of each of the delegation data held by the device itself;
The delegation application system according to claim 1 , wherein the verification support device verifies the delegation data based on the delegation data state information. 5. The delegation application system according to claim 4 , wherein the verification support device invalidates a valid state of the delegation data held by the verification support device in response to a request from the delegator terminal. The delegation application system of claim 1, characterized in that the verification support device holds verification rules corresponding to the type of application data, and verifies the delegation data using the verification rules corresponding to the type of application data submitted to the service providing device together with the delegation data that is the subject of the request. The delegation application system of claim 1, characterized in that the verification support device obtains information missing for verifying the delegation data from an external server that provides a specified external service, and verifies the delegation data using the obtained information and information it holds. The delegation application system according to claim 7 , wherein the information acquired from the external server is qualification information of the agent. A delegation application method using a delegation application system that supports an application for a procedure to receive a service by an agent delegated by a delegator, comprising:
the delegation application system includes a delegator terminal used by the delegator, an agent terminal used by the agent, a verification support device, and a service providing device that provides a service;
Before applying for the above procedure,
a first step in which the verification support device provides the delegator terminal or the agent terminal with application form data required for the application of the procedure and a format of delegation data proving that the application is delegated to the agent;
a second step in which the verification support device receives the application data and the delegation data created based on each of the formats from the delegator terminal or the agent terminal and holds them;
When applying for the above procedure,
a third step of, when the service providing device receives the application data and the delegation data from the agent terminal, requesting the verification support device to verify the delegation data;
a fourth step of the verification support device verifying the delegation data held before the application of the procedure, which corresponds to the delegation data that is the subject of the request, and responding with the verification result to the service providing device;
a fifth step of the service providing device providing the service requested in the application data received from the agent terminal when the verification result of the delegation data is successful;
Equipped with
In the delegation data, a delegation period indicating a valid period of the delegation data or a delegation number indicating a valid number of times the delegation data can be used can be specified;
In the fourth step, the verification support device verifies the delegation data based on the delegation period or the delegation count specified in the delegation data.
A delegation application method comprising: A delegation application program executed by a computer constituting a delegation application system, which supports an application for a procedure to receive a service by an agent delegated by a delegator, comprising:
the computers constituting the delegation application system include a delegator terminal used by the delegator, an agent terminal used by the agent, a verification support device, and a service providing device that provides a service;
Before applying for the above procedure,
causing the verification support device to execute a process of providing, to the delegator terminal or the agent terminal, application form data necessary for applying for the procedure and a format of delegation data proving that the application is delegated to the agent;
causing the verification support device to execute a process of receiving the application data and the delegation data created based on each of the formats from the delegator terminal or the agent terminal and storing the data;
When applying for the above procedure,
when the service providing device receives the application data and the delegation data from the agent terminal, the service providing device executes a process of requesting the verification support device to verify the delegation data;
causing the verification support device to execute a process of verifying the delegation data held before the application of the procedure, which corresponds to the delegation data that is the subject of the request, and responding to the service providing device with the verification result;
and causing the service providing device to execute a process of providing the service requested in the application data received from the agent terminal when a result of the verification of the delegation data is successful;
In the delegation data, a delegation period indicating a valid period of the delegation data or a delegation number indicating a valid number of times the delegation data can be used can be specified;
The process to be executed by the verification support device when applying for the procedure includes verifying the delegation data based on the delegation period or the delegation count specified in the delegation data.
A delegation application program comprising:

Images