Delegation application system, delegation application method, and delegation application program

The delegation application system simplifies the creation and verification of application and delegation data, ensuring efficient validation of the agent's authority, addressing the challenges of manual creation and verification in existing systems.

JP7583650B2Active Publication Date: 2024-11-14HITACHI SYST LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2021038944
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-03-11
Publication Date
2024-11-14
Estimated Expiration
2041-03-11

AI Technical Summary

Technical Problem

Existing delegation systems require the delegator or agent to manually create power of attorney details and service providers to verify the agent's authority, which can be cumbersome and error-prone, especially for those unfamiliar with the procedures.

Method used

A delegation application system that includes a delegator terminal, agent terminal, verification support device, and service providing device, which assists in creating and verifying application form and delegation data, ensuring the agent's authority is easily confirmed before providing services.

Benefits of technology

Enables easy creation of application and delegation data by the delegator or agent and facilitates quick verification by service providers, ensuring the agent's authority is validated, thus streamlining the delegation process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007583650000001
    Figure 0007583650000001
  • Figure 0007583650000002
    Figure 0007583650000002
  • Figure 0007583650000003
    Figure 0007583650000003
Patent Text Reader

Abstract

To allow a mandator or a representative to easily create application data and delegation data required for delegation application of a procedure, and / or to assist a service provider in easily confirming a proxy right of the representative.SOLUTION: A delegation application system 100 includes a mandator terminal 102, a representative terminal 101, a verification support device 103 for providing the mandator terminal 102 or the representative terminal 101 with a format of application data required for procedure application and delegation data for proving delegation to the representative, and verifying the delegation data created on the basis of the format, and a service providing device 104 for providing a service applied by the application data in the case where a successful result about the delegation data submitted with the application data is acquired with the verification by the verification support device 103.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a delegation application system, a delegation application method, and a delegation application program. [Background technology]

[0002] 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.

[0003] For example, Patent Document 1 discloses a technology for electronically realizing a paper-based power of attorney. In the delegation system disclosed in Patent Document 1, a delegator or an agent transmits a power of attorney created electronically on a smart device or the like to the delegator's or agent's smart device using short-range wireless communication to create a token including 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 checks the delegation details. According to the delegation system of Patent Document 1, an application by a proxy can be made paperless. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2016-206982 A Summary of the Invention [Problem to be solved by the invention]

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

[0006] 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 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 agent's authority to act on behalf of the agent. [Means for solving the problem]

[0007] In order to solve the above problem, the present invention provides an authorization application system that supports an application for a procedure to receive 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 required for the application for the procedure and a format of authorization data proving that the application is authorized to the agent, and verifies the authorization data created based on the format; and a service providing device that provides the service requested in the application data when a successful result is obtained in the verification by the verification support device for the authorization data submitted together with the application data. prior to application for the procedure, the verification support device transmits the application data and the format of the delegation data to the delegator terminal or the agent terminal, and receives and retains the application data and the delegation data created based on each of the formats from the delegator terminal or the agent terminal; when application for the procedure is made, the service providing device receives the application data and the delegation data from the agent terminal and requests the verification support device to verify the delegation data; the verification support device verifies the delegation data retained before application 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; if the verification result of the delegation data is successful, the service providing device provides the service requested in the application data received from the agent terminal; the delegation data can specify a delegation period indicating a validity period of the delegation data or a delegation number indicating a validity number of times the delegation data can be used; and at the time of application 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. A delegation application system is provided.

[0008] 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 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, and a second step of, prior to 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 receiving the delegation data from the delegator terminal or the agent terminal and holding the delegation data; a third step of, when the service providing device receives the application form data and the delegation data from the agent terminal at the time of application for the procedure, 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 the application for the procedure, which corresponds to the delegation data subject to 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 form data received from the agent terminal if the verification result of the delegation data is successful. In the delegation data, a delegation period indicating a validity period of the delegation data or a delegation number indicating a valid use number of the delegation data can be specified, 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. ,A delegation application method is provided.

[0009] In addition, in order to solve the above problem, the present invention provides an delegation application program to be executed by a computer constituting a delegation application system, which 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, and before the application for the procedure, causes the verification support device to execute a process of providing the delegator terminal or the agent terminal with application form data necessary for the application for the procedure and a format of delegation data that proves that the application is delegated to the agent, and causes the verification support device to perform a process of providing the delegator terminal or the agent terminal with application data necessary for the application for the procedure and a format of delegation data that proves that the application is delegated to the agent, and and executing a process of receiving the application data and the delegation data created by the application from the delegator terminal or the agent terminal and storing the data, and when the application for the procedure is made, causing the service providing device to execute a process of requesting the verification support device to verify the delegation data when the application data and the delegation data are received from the agent terminal, causing the verification support device to execute a process of verifying the delegation data stored before the application for 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 if the verification result of the delegation data is successful. In the delegation data, a delegation period indicating a validity period of the delegation data or a delegation count indicating a valid use count of the delegation data can be specified, and in the process executed by the verification support device when applying for the procedure, the delegation data is verified based on the delegation period or the delegation count specified in the delegation data. , a delegated application program is provided. Effect of the Invention

[0010] According to the present invention, it is possible to assist a principal or agent in easily creating application data and delegation data required for proxy application of a procedure, and / or to assist a service provider in easily confirming the agent's authority to act on behalf of another. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram showing an example of the overall configuration of a delegation application system 100 according to one embodiment of the present invention. [Diagram 2]2 is a block diagram showing an example of a functional configuration of an agent terminal 101 and a delegator terminal 102. FIG. [Diagram 3] 1 is a block diagram showing an example of a functional configuration of a verification support device 103. FIG. [Figure 4] 1 is a block diagram showing an example of a functional configuration of a service providing device 104. FIG. [Diagram 5] FIG. 11 is a diagram showing an example of personal information. [Figure 6] FIG. 11 is a diagram illustrating an example of delegation history information. [Figure 7] FIG. 13 is a diagram showing an example of an application data / delegation data format. [Figure 8] FIG. 11 is a diagram illustrating an example of delegation data state information. [Figure 9] FIG. 13 is a diagram illustrating an example of a validation rule. [Figure 10] 10 is a sequence diagram showing an example of a processing procedure for delegation request processing executed by the delegation request system 100. FIG. [Figure 11] 13 is a flowchart showing an example of a processing procedure of a first verification process. [Figure 12] 13 is a flowchart illustrating an example of a processing procedure of a second verification process. [Figure 13] FIG. 11 is a sequence diagram showing an example of a procedure for revocation processing. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In addition, the same components and processes are denoted by the same reference numerals throughout the drawings, and duplicated explanations will be omitted.

[0013] (1) Composition 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 a proxy application by a principal or agent regarding a proxy application for various procedures for receiving the provision of services, and supports the service provider in confirming the proxy authority of the agent. In this specification, application data is electronic data required for an application 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 the agent makes a proxy application for a procedure, it is necessary to submit the application data and delegation data to the service provider (service providing device 104).

[0014] As shown in FIG. 1, the delegation application system 100 is composed of multiple agent terminals 101 each used by an agent, multiple delegator terminals 102 each used by a delegator, a verification support device 103 that provides formats for delegation data and application form 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.

[0015] 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.

[0016] The external server 106 has a function of providing a predetermined external service, and is realized by a general server computer. As an external service, the external server 106 provides information that is necessary when a service provider confirms the proxy authority of an agent, but is not held by the verification support device 103, specifically, for example, information on the qualifications of the agent and information showing the relationship between the corporate representative and the employee.

[0017] The computers, smart devices, or server computers that realize each of the above devices (agent terminal 101, delegator terminal 102, verification support device 103, service providing device 104, and external server 106) are each configured by hardware components such as a processor such as a CPU (Central Processing Unit), a memory, an external storage device, a communication device such as a NIC (Network Interface Card), an input device such as a keyboard or a mouse, and an output device such as a display or a printer, all of which are connected to each other via a bus or the like. Note that each of the above hardware components is not limited to being mounted in 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.

[0018] The reading device 105 is realized by an IC card reader or the like having a function of reading predetermined information using short-distance wireless communication. In this example, an independent reading device 105 is described as a specific example of a means for acquiring predetermined 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 an essential component and may be replaced by other means for acquiring the above-mentioned predetermined information, or the service providing device 104 may have a similar function.

[0019] (1-1) Agent terminal 101, delegator terminal 102 Fig. 2 is a block diagram showing an example of the 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 memory unit 202, a communication unit 203, and an input / output unit 204, which are connected by a bus or the like. The calculation unit 201 is realized by a processor executing a program stored in a memory or an external storage device. The memory 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.

[0020] The calculation unit 201 supports the creation of delegation data and application data, manages the state of the delegation data, and signs the delegation data. As functional units for realizing these functions, the calculation unit 201 has a data creation support unit 205, a delegation data state management unit 206, and a digital signature attachment unit 207.

[0021] The data creation support unit 205 supports the agent or the 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 storage 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 digital signature assignment unit 207 assigns a digital signature to the delegation data or application data created by its own terminal.

[0022] The storage unit 202 stores personal information of each of the principals or agents, and information on past delegations. As shown in FIG. 2, the storage unit 202 includes a personal information storage unit 208 and a delegation history storage unit 209.

[0023] The personal information storage unit 208 stores personal information (see FIG. 5) indicating the name, date of birth, address, etc. of the delegator 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.

[0024] 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 by 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 by the calculation unit 201 and information held in the memory unit 202 from the other devices.

[0025] The input / output unit 204 receives input from the agent or the delegate who operates the terminal, and outputs predetermined information by displaying it on a display or the like.

[0026] (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.

[0027] The calculation unit 301 manages the formats of application data and 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.

[0028] 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.

[0029] 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 holding 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 holding unit 310, and also responds to a request to invalidate the delegation data from another device.

[0030] 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 storage unit 302 and the information acquired from the external server 106. The trail management unit 308 manages the delegation data and the trail that indicates the results of the verification.

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

[0032] Format holding unit 309 holds the formats of application data and delegation data (see FIG. 7). Note that, as described later in FIG. 7, in this description, a format in which application data and delegation data are integrated (application data / delegation data format 530) is shown as an example of a format held by format holding unit 309, but the application data format and the delegation data format may be prepared separately and held in format holding unit 309.

[0033] 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).

[0034] 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).

[0035] The input / output unit 304 receives an input from the administrator of the verification support device 103 .

[0036] (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.

[0037] 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 an 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.

[0038] 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.

[0039] The storage unit 402 stores trail information. The storage unit 402 includes a trail information storage unit 408 that stores trail information that records the trail of a series of processes related to an application.

[0040] 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 by the calculation unit 401 to other devices (the agent terminal 101 and the verification support device 103) and receives information necessary for processing by the calculation unit 401 and information held in the memory unit 402 from the other devices (the verification support device 103).

[0041] The input / output unit 404 accepts input from an administrator of the service providing device 104 and input from a user who wishes to receive a service provided by the service providing device 104, and receives information read by the reading device 105.

[0042] 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 Figs. 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," and the like. Each of the storage units 202, 302, and 402 may be configured with a plurality of 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. A part or all of the data equivalent to the program or data stored in each of the storage units 202, 302, and 402 may be provided from one or more servers equipped with non-transient storage devices connected to a network 107 such as the Internet, or via a non-transient storage medium. Each of the components shown in Figs. 2 to 4 does not need to be physically separated, and for example, one component may serve as another component. Furthermore, components within one terminal or device may be distributed across multiple devices.

[0043] (2) Data Structure An example of the data structure of various data held in the delegation request system 100 according to this embodiment will be described below.

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

[0045] In personal information 510, the name of the subject (agent or delegate) is set in name 511. Address 512 is an item in which the address of the subject is set, and for example, the city, ward, town, village, district, block, number, building name, room number, etc. are set. 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, and is set in the Gregorian calendar or Japanese calendar, etc. Phone number 514 is an item in which the phone number of the subject is set, and multiple phone numbers, such as a home phone, a mobile phone phone, and a work phone number, may be set.

[0046] Fig. 6 is a diagram showing an example of delegation history information. Delegation history information 520 shown in Fig. 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 data items of a delegation data ID 521, delegator information 522, agent information 523, delegation contents 524, and revocation status 525.

[0047] The delegation data ID 521 is a unique identifier for each piece of delegation information (delegation data), and may use a UUID (Universally Unique IDentifier), or may be issued sequentially by the verification support device 103 during the delegation application processing described later in FIG. 10.

[0048] The delegator information 522 and the 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. The delegation contents 524 are set to the contents that the delegator delegates to the agent, and are described as, for example, "obtaining a copy of the resident's card."

[0049] In the expiration status 525, whether the target delegation data is currently valid or expired is set. For example, if the delegation data has been used and expired, "Expired (used)" is written. The reason why the delegation data expires may be due to a validity period or valid number of times (see delegation period / number of times 537 in FIG. 7) previously set in the delegation data, 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 written as "valid", or the number of times it can be used or a deadline may be set.

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

[0051] The name of the application is set in the application data name 531, for example, "Application for Publication of Copy of Resident Record, etc." 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 written 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.

[0052] Specific details that the delegator or the agent must specify or select for the application are set in the application information 534. Specifically, for example, if the application is for the issuance of a copy of a resident's certificate, the application information 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.

[0053] In the delegation content 535, the content of the delegation in the application is set, 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. In the agent information 536, personal information such as the agent's name, address, and telephone number is set. The agent information 536 is not set by the verification support device 103, but by the agent terminal 101 or the delegator terminal 102.

[0054] In the delegation period / number of times 537, the validity conditions of delegation in the delegation data (valid number of times and validity period) are set. The validity conditions of 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 later is written. In addition, both the validity period and the validity number of times may be set. Note that the format held in the format holding 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 hold the formats for both purposes in association with each other.

[0055] Fig. 8 is a diagram showing an example of delegation data state information. The delegation data state information 540 in Fig. 8 is an example of the delegation data state information stored in the delegation data state storage unit 310 of the verification support device 103. The delegation data state information 540 includes data items of a delegation data ID 541 and an expiration state 542.

[0056] 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.

[0057] Fig. 9 is a diagram showing an example of a verification rule. A verification rule 550 in Fig. 9 is an example of a verification rule stored in the verification rule storage unit 312 of the verification support device 103. The verification rule 550 has data items of an application form data name 551 and a verification rule 552.

[0058] 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. A validation rule for each application is set in the validation rule 552. Specific validation rules may, for example, be set such as that the applicant's electronic signature is required, and that maximum authorization from a corporation to an employee is permitted.

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

[0060] (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.

[0061] According to FIG. 10, first, the delegator operates the delegator terminal 102 to obtain application data and delegation data format related to the service that the delegator desires to receive from the verification support device 103 (step S101).

[0062] Next, the delegator operates the delegator terminal 102 to create application data and delegation data in accordance with 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.

[0063] Next, the delegator operates the delegator terminal 102 to affix an electronic signature to the application data and delegation data created in step S102 (step S103). The affixing of the electronic signature is executed by the electronic signature affixing unit 207. At this time, depending on the service to be provided, the electronic signature of the application data may be omitted. Furthermore, when affixing the electronic signature, the electronic signature affixing unit 207 may create the signature data by using a private key stored in an IC card or the like.

[0064] 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).

[0065] 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, while Fig. 10 shows the processing of steps S106 to S111 on the assumption that a corporation has been designated as the agent, if the agent is an individual (e.g., the user of 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.

[0066] 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, whereby the verification support device 103 can verify the validity of the delegation from the corporation to the employee by using these data in verifying the delegation data described later. Then, verification support device 103, which 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 delegation data status storage unit 310, and sends an acceptance response including the delegation data ID to agent terminal 101B (step S110). After step S110, the representative of the corporation operates agent terminal 101B to transmit the application data and delegation data to agent terminal 101A (step S111).

[0067] 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-mentioned processes (steps S107 to S110) regarding the delegation from the corporation to the employee may be performed in advance as delegation content that permits multiple applications at a timing prior to step S101.

[0068] The processing of steps S101 to S111 described above is processing carried out before applying for the procedure, and is processing in which the delegation application system 100 supports the creation of application data and delegation data. The processing of steps S112 to S119 described below is processing carried out when applying for the procedure, and is processing in which the delegation application system 100 supports the verification of the delegation data.

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

[0070] 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 transmits a verification request for 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 body, but includes at least the delegation data ID) included in the delegation data and application data.

[0071] The verification support device 103 (entrusted data verification unit 307) that has received the verification request checks whether verification is possible with only the data stored in the storage unit 302, and if verification is not possible, requests the external server 106 to provide data (verification data) that is lacking for verification (step S115). In response to the request, the external server 106 that provides a predetermined external service transmits verification data such as the proxy's qualification information to the verification support device 103 (step S116).

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

[0073] Next, the service provider checks 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 of directly passing it to the agent, or in a form of sending predetermined data from the service providing device 104 to the agent terminal 101A or the agent terminal 101B.

[0074] As described above, by performing the processes of steps S101 to S119 in FIG. 10, the delegation application system 100 can support the creation of application data and delegation data, as well as support the verification of the delegation data.

[0075] In addition, among the processes 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).

[0076] The service may also be provided over the network 107. In this 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.

[0077] (3-2) Verification process 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.

[0078] 11 is a flowchart showing an example of the processing procedure of the first verification process, which corresponds to a series of processes executed in common, regardless of the type of application data, among the verification processes of delegation data in this embodiment.

[0079] According to FIG. 11, first, the delegation data verification unit 307 acquires the delegation data, application data, and personal identification information received from the service providing device 104, and the verification data received from the external server 106 (step S201).

[0080] 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 number of times is specified in the delegation data instead of the delegation period, the confirmation in step S202 may be skipped. The delegation period specifies the validity period of the delegation data, and the delegation number 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.

[0081] In step S203, the delegation data verification unit 307 refers to the delegation data state information (for example, the delegation data state information 540 in FIG. 7) stored in the delegation data state storage unit 310, and checks the revocation state corresponding to the delegation data ID assigned to the delegation data. If the revocation state 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 state 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 ends the process.

[0082] In step S204, the delegation data verification unit 307 verifies the electronic signature of the delegation data and checks whether the verification is successful. If delegation is made from a corporation to an employee, the electronic signature is checked for each of the two 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 the verification of the delegation data has failed, and ends the process.

[0083] 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.

[0084] In step S206, the delegation data verification unit 307 verifies the identity verification information of the agent against the agent information described 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 the verification of the delegation data has failed, and ends the process.

[0085] In step S207, the delegation data verification unit 307 checks whether the application data corresponds to the delegation data. 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 included. Alternatively, this can be achieved by checking whether the application data name corresponds to the delegation content. If the application data does not correspond to the delegation data (NO in step S207), the delegation data verification unit 307 determines that the verification of the delegation data has failed, and terminates the process.

[0086] 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.

[0087] As described above, 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. When delegation is made from a corporation to an employee, each confirmation process may be performed on two pieces of delegation data: the delegation data from the delegator to the corporation and the delegation data from the corporation to the employee.

[0088] The order of execution of the confirmation processes 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 according to changes in laws, regulations, security standards, etc.

[0089] 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 rule is held in the verification rule holding unit 312 of the verification support device 103. The second verification process is executed in addition to the first verification process described above.

[0090] 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 rule 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.

[0091] 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 the 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 the application data does not have an electronic signature (NO in step S302), the delegation data verification unit 307 determines that the verification of the delegation data has failed, and ends the process.

[0092] 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 allowed 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 allowed 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 ends the process.

[0093] 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 the verification of the delegation data has failed, and ends the process.

[0094] 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 a qualification, the delegation data verification unit 307 uses the result of the inquiry to the external server 106 (verification data) to check whether the agent has a specified professional qualification, 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 ends the process.

[0095] 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 of the 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.

[0096] As described above, by executing the processes of steps S301 to S305 in FIG. 12, the delegation data verification unit 307 can verify the delegation data by the verification process to which the verification rule according to the type of application data is applied.

[0097] Then, in the case of an application for which no verification rule is set, when the first verification process results in a successful verification, and in the case of an application for which a verification rule is set, when both the first and second verification processes result in a successful verification, the delegation data verification unit 307 judges that the verification of the delegation data related to the application has been successful. When the verification 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 verification of the delegation data is successful, the number of delegations is consumed once, 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)".

[0098] On the other hand, in the case of an application for which no verification rule is set, when the first verification process results in a failed verification, or in the case of an application for which a verification rule is set, when at least either the first verification process or the 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.

[0099] Furthermore, the trail management unit 308 records the result of the verification of the delegation data by the delegation data verification unit 307 as trail information, and causes the trail information storage unit 311 to store it. When recording the trail information, it is possible to record not only the verification result, but also the reason for the verification failure, etc. 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 causes the received trail information to be stored in the trail information storage unit 408.

[0100] (3-3) Revocation process In this embodiment, the delegator operates the delegator terminal 102, so that the delegator data status management unit 206 of the delegator terminal 102 can invalidate the delegation data stored in the verification support device 103. This invalidation process can be executed at a timing determined or desired by the delegator. In addition, by executing the invalidation process at a predetermined cycle, the delegation data for which a delegation period is specified can be invalidated when the delegation period ends. The detailed procedure of the invalidation process will be described below.

[0101] Fig. 13 is a sequence diagram showing an example of the procedure for revocation processing, which is based on the assumption that the revocation processing is executed at the discretion or desire of the delegator.

[0102] 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 request revocation of the delegation data selected in step S401 to the verification support device 103 (step S402). At this time, the delegation data ID attached to the selected delegation data is sent together with the revocation request.

[0103] Next, the delegation data management unit 306 of the verification support device 103 changes the revocation status of the delegation data corresponding to the delegation data ID received in step S402, among the delegation data held in the delegation data status holding unit 310, 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 instructed the revocation request to check whether it is the same as the delegator who sent the delegation data initially.

[0104] Next, the verification support device 103 (the delegation data management unit 306) responds with the revocation result executed 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 ends the revocation process.

[0105] As described above, by executing the processing of steps S401 to S405 in FIG. 13, 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 abuse or unauthorized use of the delegation data.

[0106] As described above, according to the delegation application system 100 of the present embodiment, even a delegator or agent with little knowledge of the contents of the procedure or delegation can easily create 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 the present 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 delegation 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.

[0107] 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 the embodiment 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.

[0108] In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the program, table, file, etc. that realizes 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.

[0109] In addition, the control lines and information lines in the drawings are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0110] 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 Arithmetic unit 202,302,402 Storage section 203,303,403 Communications Department 204,304,404 Input / output section 205 Data Creation Support Department 206 Delegated Data Status Management Unit 207 Electronic signature adding section 208 Personal Information Retention Department 209 Delegation History Storage Unit 305 Format Management Department 306 Delegated Data Management Department 307 Delegated Data Verification Unit 308 Evidence Management Department 309 Format Retention Unit 310 Delegation Data Status Holder 311 Trail Information Storage Unit 312 Validation Rule Storage Unit 405 Read information acquisition unit 406 Verification Request Section 407 Trail Management Department 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 Validation Rules

Claims

1. 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 delegation data that is the subject of the request and that was held before the application for the procedure, 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 data is provided with the delegator's digital signature when it is created. The delegation application system according to claim 1 .

3. 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 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 delegation application system according to claim 1 .

4. 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 verification support device verifies the delegation data based on the delegation data state information. The delegation application system according to claim 1 .

5. The verification support device invalidates the validity of the delegation data held by the device in response to a request from the delegator terminal.

5. The delegation application system according to claim 4.

6. The verification support device holds a verification rule corresponding to a type of the application data, and verifies the delegation data using the verification rule corresponding to the type of the application data submitted to the service providing device together with the delegation data that is the subject of the request. The delegation application system according to claim 1 .

7. The verification support device acquires information that is missing for verifying the delegation data from an external server that provides a predetermined external service, and verifies the delegation data using the acquired information and information that the verification support device holds. The delegation application system according to claim 1 .

8. The information obtained from the external server is the qualification information of the agent.

8. The delegation application system according to claim 7.

9. 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:

10. 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 required 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:

Citation Information

Patent Citations

  • Electronic commission processing system and electronic letter of attorney preparing device and electronic application preparing device

    JP2001283144A

  • Electronic certificate system, electronic certificate management server, program and control method

    JP2007143126A

  • Delegating system, proxy-carried terminal, and control method

    JP2016206982A