JP2011164707A - Contract support server, and contract support system and method of controlling the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve efficiency of a procedure for concluding a contract. <P>SOLUTION: A contract support server 200 is provided. The contract support server 200 can receive confirmation data D1 obtained by imaging a driver's license from a mobile phone 100, and manages a variety of application data D2 prepared in advance associatively to contract contents to be concluded by each. The contract support server 200 includes: a receiving unit 240 for receiving the confirmation data D1; a memory 220 storing the plurality of pieces of the application data D2; and an information processing unit 210 for executing reading processing of reading the application data D2 corresponding to the received confirmation data D1 from the memory 220, and generation processing of generating contract data indicating the contents and a condition of the contract to be concluded based on the received application data D2 and the read application data D2. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a contract support server, a control method thereof, and a contract support system.

  When a contract such as an automobile insurance contract is concluded, the insurance company uses a confirmation document such as a driver's license of the insured person to confirm the conditions and contents of the contract, and then concludes the contract. As a procedure for this conclusion, as described in Patent Document 1, an application form to which confirmation documents are attached is handed over from the applicant to the insurance company by means of paper such as facsimile or mail. In general, an insurance company employee visually checks the printed paper, or the insurance company employee visually checks the characters read by the OCR from the delivered paper and confirms the above. Examples of techniques that can contribute to the efficiency of such procedures include the systems described in Patent Documents 2 and 3. In these systems, the procedure proceeds by transmitting and receiving image data via a computer network.

JP 2004-348302 A JP 2008-234291 A JP 2009-238151 A

In the technique described in Patent Document 1, visual inspection by an insurance company employee is indispensable in the above confirmation work, and the efficiency of the procedure for concluding a contract is low. Further, Patent Document 2 does not describe a configuration for eliminating visual inspection by an insurance company employee. In other words, no technology has been proposed for achieving an efficient procedure for concluding a contract. Note that the system described in Patent Document 3 is a system for easily obtaining an estimate of an insurance contract, and does not improve the efficiency of the procedure for concluding the contract.
In view of the above, an object of the present invention is to improve the efficiency of procedures for concluding a contract.

In order to solve the above-described problems, the contract support server of the present invention can receive at least first data obtained by imaging a document that needs to be confirmed in order to conclude a contract from each portable terminal, and each concludes A contract support server that manages a plurality of second data prepared in advance in relation to contract contents to be received, a receiving unit that receives the first data, and a storage unit that stores the plurality of second data And contract contents to be concluded based on the reading process of reading the second data corresponding to the received first data from the storage unit, and the received first data and the read second data And an information processing unit that executes a generation process for generating contract data.
Documents that need to be confirmed to conclude a contract are, for example, confirmation documents such as a driver's license. The second data prepared in advance in relation to the contents of the contract to be concluded is application data indicating information described in the application form for applying for the conclusion of the contract, for example. The mobile terminal is, for example, a mobile phone.
According to this contract support server, contract data indicating contract contents to be concluded is generated based on, for example, first data derived from a confirmation document and second data derived from, for example, an application form. Visual confirmation work can be eliminated. In addition, since a portable terminal can be used, the contract procedure can be performed efficiently without selecting a place. Therefore, according to the contract support server, the procedure for concluding the contract is made efficient.

In the contract support server, the mobile terminal transmits the first data and identification information for identifying a contract, the receiving unit receives the first data and the identification information, and the storage unit The plurality of second data is stored in association with the identification information, and the information processing unit reads the second data corresponding to the received identification information from the storage unit in the reading process, In the generation process, contract data indicating contract contents to be concluded may be generated based on the first data and the read second data (mode 1).
In aspect 1, the information processing part should just read the 2nd data matched with the identification information from the portable terminal which transmits 1st data. That is, according to aspect 1, it is possible to easily identify the second data that reliably corresponds to the first data.
The identification information may be information obtained by imaging a paper on which the identification information is written, or may be manually input. A typical example of identification information is an identification number (for example, a security number) represented by numbers or characters, but a symbol such as a QR code or a combination of numbers, characters, and symbols is also included in the “identification information”.

  In the first aspect, if the second data corresponding to the identification information is not stored and cannot be read in the reading process, the information processing unit does not register the corresponding second data. A first error process (for example, S253 and S254 in FIG. 7) for returning a message to the mobile terminal may be executed. According to this aspect, it is possible to easily notify the user of the mobile terminal that the second data is not registered.

In the aspect 1, the first data indicates a contract condition, and the information processing unit, in the generation process, does not match the contract condition indicated by the second data and the contract condition indicated by the first data. If this is the case, a second error process for returning a message indicating that the conditions of the contract are inconsistent or a message prompting to change the second data so as to satisfy the conditions of the contract to the portable terminal (for example, FIG. 7 S260) may be executed.
The “advantageous to the user” typically corresponds to a case where the insurance premium is reduced or an incidental service is improved, or a case where the insurance premium is the same and the insurance premium is increased.
As described above, the second data is application data indicating information described in, for example, an application form for applying for the conclusion of a contract. Therefore, the contract condition indicated by the second data is considered to be a condition expected by the user. Therefore, when a contract having a condition that is more disadvantageous to the user than the condition of the contract indicated by the second data is concluded, the user may suffer an unexpected disadvantage. However, according to this aspect, since the contract data is not generated when the contract condition indicated by the second data and the contract condition indicated by the first data are inconsistent, the user suffers an unexpected disadvantage. Can be avoided. Further, according to this aspect, a message indicating that the condition of the contract indicated by the second data and the condition of the contract indicated by the first data do not match, or prompting to change the second data so as to satisfy the conditions of the contract The message can be easily notified to the user of the mobile terminal.

In the aspect 1, the first data indicates a contract condition, and the information processing unit uses the contract condition indicated by the first data in the generation process rather than the contract condition indicated by the second data. If the contract data is generated using the first data, and the contract conditions indicated by the first data are more disadvantageous for the user than the contract conditions indicated by the second data, A third error process (for example, S263 in FIG. 7) is executed to return a message indicating that the condition of the request is inconsistent or a message prompting to change the second data so as to satisfy the condition of the contract to the portable terminal. You may make it do.
According to this aspect, it is possible to avoid a situation in which the user suffers an unexpected disadvantage, and a message indicating that the contract condition indicated by the second data and the contract condition indicated by the first data are inconsistent Alternatively, it is possible to easily notify the user of the portable terminal of a message for urging to change the second data so as to satisfy the contract conditions. In addition, according to this aspect, the contract data can be generated even when the contract condition indicated by the second data does not match the contract condition indicated by the first data. Increased efficiency. When generating the contract data using the first data, the mobile terminal user is notified whether the contract data is generated using the first data, and the mobile terminal user is notified of the contract data. You may make it select whether to produce | generate contract data.

  In the aspect 1, the first data indicates the content of the contract, and the information processing unit prioritizes the content of the contract indicated by the first data over the second data in the generation process, and Data may be generated (Aspect 2). According to the aspect 2, even if the contents of the contract indicated by the second data and the contents of the contract indicated by the first data are inconsistent, the generation of the contract data is not stopped, so that the procedure for concluding the contract is further streamlined. The In addition, according to the aspect 2, the contract data indicated by the first data is generated based on the contract data indicated by the first data regardless of the second data. It is possible to reduce the content of the contract to be performed (for example, information to be described in the application form). This contributes to the efficiency of procedures for concluding a contract. In general, since the content of the contract indicated by the first data (for example, the driver's license) is more accurate than the second data (for example, the application form), according to the aspect 2, the contract with the more accurate content is concluded. can do.

  In aspect 2, when the information processing unit generates the contract data by prioritizing the content of the contract indicated by the first data over the second data in the generation process, the information processing unit You may make it perform the change notification process which transmits the content to the said portable terminal. According to this aspect, it is possible to easily notify the user of the mobile terminal of the difference between the content of the contract that has been concluded and the content of the contract that the user has expected.

  In each of the above aspects, a storage unit that stores the first data is provided, and the information processing unit acquires the first data from the storage unit at a predetermined cycle, and executes the reading process and the generation process You may make it do. According to this aspect, even when the second data corresponding to the first data is stored in the storage unit after the first data is stored in the storage unit, the reading process and the generation process are surely performed. Can do.

  In each of the above aspects, the first data is character data obtained by converting imaging data in the portable terminal, or the first data is imaging data, and the information processing unit converts the received first data into characters You may make it perform the conversion process converted into data before the said read-out process and the said production | generation process. When the first data is character data, the amount of communication can be reduced. When the first data is imaging data, data processing in the portable terminal can be reduced.

  In each of the above aspects, the document that needs to be confirmed to conclude the contract is a driver's license, and the first data may include excellent driver information. A driver's license is common as confirmation documents. Also, many car insurance contracts have different conditions depending on whether the insured is an excellent driver. Therefore, according to this aspect, the efficiency of the conclusion procedure can be improved for many automobile insurance contracts.

  In order to solve the above-described problem, a contract support system according to the present invention includes a contract support server according to each aspect described above and a mobile terminal that performs communication between the contract support server and transmits the first data. Is provided. According to this contract support system, it is possible to obtain the same effect as that obtained by the provided contract support server.

In order to solve the above-described problem, a control method for a contract support server according to the present invention carries first data obtained by imaging a document that needs to be confirmed to conclude a contract and identification information for identifying the contract. A control method of a contract support server that can be received from a terminal and stores and manages a plurality of second data prepared in advance in relation to contract contents to be concluded in the storage unit. The second data corresponding to the identification information is read from the storage unit, and contract data indicating contract details to be concluded is generated based on the received first data and the read second data (aspect) 3).
According to this control method, in the contract support server, contract data indicating contract contents to be concluded is generated based on, for example, first data derived from a confirmation document and second data derived from, for example, an application form. From this, it is possible to eliminate human visual confirmation. In addition, since a portable terminal can be used, the contract procedure can be performed efficiently without selecting a place. Therefore, the procedure for concluding the contract is made efficient.

  In aspect 3, the contract relates to car insurance, the document that needs to be confirmed to conclude the contract is a driver's license, and the first data includes excellent driver information, Each of the plurality of second data includes excellent driver information. In the process of generating the contract data, the excellent driver information included in the second data and the first data are included in the first data. If the excellent driver information does not match, a message indicating that the conditions of the contract do not match or a message prompting to change the second data so as to satisfy the conditions of the contract is returned to the portable terminal You may do it.

  According to this aspect, the contract data is not generated when the excellent driver information included in the second data and the excellent driver information included in the first data are inconsistent. Can be avoided. Further, according to this aspect, it is possible to easily notify the user of the mobile terminal of a message indicating that the conditions of the contract are inconsistent or a message prompting to change the second data so as to satisfy the conditions of the contract. it can. Moreover, according to this aspect, the efficiency of the conclusion procedure can be improved for many automobile insurance contracts.

  In aspect 3, the contract relates to car insurance, the document that needs to be confirmed to conclude the contract is a driver's license, and the first data includes excellent driver information, Each of the plurality of second data includes good driver information, and indicates that the good driver information included in the second data is not a good driver in the process of generating the contract data, When the excellent driver information included in the first data indicates that the driver is an excellent driver, the contract data is generated using the first data, and the excellent driver information included in the second data is the excellent driving. A message indicating that the conditions of the contract are inconsistent or satisfying the conditions of the contract when the driver information included in the first data indicates that the driver is not a good driver A message prompting the user to change the sea urchin the second data may be returned to the mobile terminal.

  According to this aspect, it is possible to avoid a situation in which the user suffers an unexpected disadvantage, and to change the second data so that the message indicating that the contract conditions are inconsistent or the conditions of the contract are satisfied A message prompting the user can be easily notified to the user of the portable terminal. In addition, according to this aspect, the contract data can be generated even when the excellent driver information included in the second data does not match the excellent driver information included in the first data. The procedure for doing so is further streamlined. Moreover, according to this aspect, the efficiency of the conclusion procedure can be improved for many automobile insurance contracts.

In the aspect 3, the contract is related to automobile insurance, the document that needs to be confirmed in order to conclude the contract is a driver's license, the first data includes address information, and the contract In the process of generating data, when the address information indicated by the second data and the address information included in the first data do not match, the address information of the first data is prioritized over the address information of the second data. The contract data may be generated.
According to this aspect, even if the address information indicated by the second data and the address information included in the first data do not match, the generation of the contract data is not stopped, so the procedure for concluding the contract is more efficient. It becomes. Further, according to this aspect, since the contract data is generated based on the address information indicated by the first data, regardless of the second data, the contents of the contract to be indicated by the second data (for example, application) Address information can be deleted from the information to be described in the certificate. This contributes to the efficiency of procedures for concluding a contract. In general, since the content of the contract indicated by the first data (driver's license) is more accurate than the second data (for example, application form), according to this aspect, the contract with the more accurate content is concluded. be able to. Moreover, according to this aspect, the efficiency of the conclusion procedure can be improved for many automobile insurance contracts.

  In this aspect, in the process of generating the contract data, when the contract data is generated by giving priority to the content of the contract indicated by the first data over the second data, the content of the first data prioritized is changed. You may make it transmit to the said portable terminal. According to this aspect, it is possible to easily notify the user of the mobile terminal of the difference between the content of the contract that has been concluded and the content of the contract that the user has expected.

  The present invention is also specified as a program for causing a computer to function as the contract support server according to each of the above aspects. The program of the present invention can receive first data obtained by imaging a document that needs to be confirmed in order to conclude a contract and identification information for identifying the contract from the mobile terminal, and each contract content to be concluded A contract support server that stores and manages a plurality of second data prepared in advance in relation to the storage unit, and reads out the second data corresponding to the received identification information from the storage unit; Based on the received first data and the read second data, a generation process for generating contract data indicating contract contents to be concluded is executed. According to the above program, the same effect as the contract support server according to the present invention can be obtained.

It is a block diagram which shows the structure of the contract assistance system 10 which concerns on the 1st-6th embodiment of this invention. It is a figure which illustrates some application forms used with the contract assistance system. It is a figure which illustrates the driver's license used with the contract assistance system. It is a flowchart of the process which concerns on the communication between the mobile telephone 100 and the contract assistance server 200 in 1st Embodiment of this invention. It is a figure which shows the mode of the imaging in the same embodiment. It is a schematic diagram which illustrates the content of the character data in the embodiment. It is a flowchart of the confirmation conclusion process in the embodiment. It is a figure which shows the mode of the imaging in 2nd Embodiment of this invention. It is a flowchart of the data transmission process in the embodiment. It is a flowchart of the data reception process in 3rd Embodiment of this invention. It is a flowchart of the data transmission process in 4th Embodiment of this invention, and a data reception process. It is a flowchart of the data transmission process in the modification (modification 1) of the embodiment. It is a flowchart of the data reception process in the modification (modification 2) of the embodiment. It is a schematic diagram which illustrates the content of the character data in 5th Embodiment of this invention. It is a flowchart of the confirmation conclusion process in the embodiment. It is a schematic diagram which illustrates the content of the character data in 6th Embodiment of this invention. It is a flowchart of the confirmation conclusion process in the embodiment. It is a flowchart of the confirmation fastening process in the modification (modification 17) of the embodiment. It is a flowchart which shows a part of data transmission process in the modification 19 which concerns on this invention.

<Configuration common to each embodiment>
FIG. 1 is a block diagram showing a configuration of a contract support system 10 according to first to sixth embodiments of the present invention. The contract support system 10 is a computer system for concluding an automobile insurance contract, and includes one or more mobile phones 100, one contract support server 200, one or more terminals 300, and one contract management server 400. With. The contract support server 200 can communicate with the mobile phone 100, the terminal 300, and the contract management server 400 via a communication network (for example, the Internet) including a wireless section.

  The mobile phone 100 is a phone that is carried by an employee of an agent who represents an insurance contract procedure, and includes an information processing unit 110, a storage unit 120, a transmission unit 130, a reception unit 140, an imaging unit 150, a display unit 160, and the like. An operation unit 170 is provided. The information processing unit 110 is a CPU (central processing unit) that processes various types of information, and can execute various types of processing by executing a first program described later. That is, the mobile phone 100 is also a computer system.

  The storage unit 120 is a non-volatile storage device that stores data in a rewritable manner, and includes, for example, an EEPROM (Electrically Erasable and Programmable Read Only Memory). Although not shown, the storage unit 120 stores a first program for controlling each unit of the mobile phone 100, an e-mail address of the mobile phone 100, and an e-mail address of the contract support server 200. The first program can be provided in a form stored in a computer-readable recording medium or in a form distributed via a communication network.

  The transmission unit 130 converts the data supplied from the information processing unit 110 into a wireless signal and transmits the wireless signal to the wireless section of the communication network. The receiving unit 140 converts a radio signal that has arrived from a radio section of the communication network into data and supplies the data to the information processing unit 110. That is, the information processing unit 110 transmits data (e-mail) to the contract support server 200 by sending and receiving radio signals to and from the wireless section, and sends a message (e-mail) from the contract support server 200 to the mobile phone 100. ) Can be received.

  The imaging unit 150 is a camera controlled by the information processing unit 110, images a scene in an imaging area outside the mobile phone 100, generates imaging data (image data), and supplies the imaging data (image data) to the information processing unit 110. That is, the information processing unit 110 can execute imaging processing for acquiring imaging data related to the imaging region. Note that the obtained imaging data may be automatically deleted after being supplied to the information processing unit 110 without being stored in the storage unit 120. Alternatively, the user of the mobile phone 100 may manually delete the image data after supplying the image data to the information processing unit 110.

  The display unit 160 is a liquid crystal display, for example, and displays an image indicated by the image data supplied from the information processing unit 110. Instead of the display unit 160, an arbitrary notification unit that notifies information may be employed. The operation unit 170 includes, for example, a plurality of buttons, and supplies signals corresponding to operations of these buttons to the information processing unit 110. A user of the mobile phone 100 can input various instructions to the mobile phone 100 by operating the operation unit 170.

  The contract support server 200 is a computer system that provides a service that supports insurance contract procedures, and is arranged in an insurance company, and includes an information processing unit 210, a storage unit 220, a transmission unit 230, and a reception unit 240. The information processing unit 210 is a CPU (central processing unit) that processes various types of information, and can execute various types of processing by executing a second program described later.

  The storage unit 220 is a non-volatile storage device that stores data in a rewritable manner, and includes, for example, a hard disk. The storage unit 220 stores a second program for controlling each unit of the contract support server 200, an e-mail address of the mobile phone 100, and an e-mail address of the contract support server 200. The second program can be provided in the same form as the first program described above. In addition, in the storage area of the storage unit 220, a storage unit 221 that stores later-described confirmation data D1 and an application DB (database) 222 that stores application data (second data) D2 described later are secured.

  The transmission unit 230 converts the data supplied from the information processing unit 210 into a signal and transmits the signal to the communication network. The receiving unit 240 converts a signal arriving from the communication network into data and supplies the data to the information processing unit 210. That is, the information processing unit 210 transmits a message (e-mail) to the mobile phone 100 by sending / receiving a signal to / from the communication network, or sends data (e-mail) from the mobile phone 100 to the contract support server 200. Data can be received, data can be transmitted to the terminal 300, data from the terminal 300 to the contract support server 200 can be received, and data can be transmitted to the contract management server 400.

  The terminal 300 is a general personal computer system, and is arranged in an insurance company. The terminal 300 includes an operation unit 310 such as a keyboard and a display unit 320 such as a liquid crystal display, and exchanges signals with a communication network. Data can be transmitted to and received from the contract support server 200. The employee of the insurance company operates the terminal 300 using the operation unit 310 to apply the car insurance contract application form (hereinafter referred to as “application form”) submitted by the applicant (user) applying for the conclusion of the car insurance contract. The application data D2 is generated by inputting the information described in the terminal 300 into the terminal 300, the generated application data D2 is transmitted to the contract support server 200, or indicated by the contract data received from the contract support server 200. Information can be displayed on the display unit 320. The contract data is data indicating the conditions and contents of the concluded auto insurance contract.

  The contract management server 400 is a computer system that provides a service for managing contract data, and has a contract DB 410 that is arranged in an insurance company and stores contract data. The contract management server 400 can receive contract data from the contract support server 200 via the communication network and store it in the contract DB 410. An employee of the insurance company can receive a service provided by the contract management server 400 by operating the contract management server 400 directly or indirectly through a communication network from a terminal (not shown).

  FIG. 2 is a diagram illustrating a part of an application form used in the contract support system 10. As shown in this figure, the application form is lined with item names such as “Securities Number”, “Address”, “Name”, “Date of Birth”, “License Color” of the insured, A column for describing the contents of the item is provided near each item name. The applicant applies for the conclusion of an automobile insurance contract by submitting an application form in which the information in these description columns has been completed to the employee of the agency. The applicant and the insured person may be the same. Further, the application form may be submitted by the applicant to the insurance company.

  Information described in the application form is divided into securities number and application information. The security number is a number for identifying a car insurance policy, and is given by an insurance company by the time the auto insurance contract is concluded, and is used as identification information for identifying the car insurance contract. For example, the car insurance contract concluded by the application form of FIG. 2 is identified by the security number “A234456789”. The application information is specifically insured address information, name information, date of birth information, license color information, and the like. The application data D2 described above is data including the application information and indicates the conditions and contents of the automobile insurance contract. In addition to the application information, the security number is also written before the application.

  Applications submitted to agency employees are submitted to insurance companies. The employee of the insurance company operates the terminal 300 to input the security number and application information described in the submitted application form, and contracts the input security number with the generated application data D2 (application information). It is transmitted to the support server 200. The transmitted securities number and application data D2 are received by the information processing unit 210 of the contract support server 200 and stored in the application DB 222 in association with each other.

  By the way, the insurance company needs to confirm a document different from the application form before the auto insurance contract is concluded. The purpose of each embodiment is to improve the efficiency of the procedure related to this confirmation and the subsequent procedure up to the conclusion of the contract. Documents that require confirmation in order to conclude a car insurance contract (hereinafter referred to as “confirmation documents”) are typically insured driver's licenses.

  FIG. 3 is a diagram illustrating a driver's license of a good driver. As shown in FIG. 3, the driver's license includes the driver's name (Kotaro Nihon), address (3-7-3 Kasumigaseki, Chiyoda-ku, Tokyo), date of birth (August 1, 1960), driving The expiry date of the license (September 1, 2013) is written in a prescribed format. The background color (license license color) of the character string indicating the expiration date is gold (gold) for an excellent driver, and blue (blue) or green (green) for a non-excellent driver. In addition, the character string “excellent” indicating that the driver is a good driver is described in a predetermined format on the driver's license of the good driver.

<First Embodiment>
In the first embodiment, the information processing unit 110 of the mobile phone 100 can convert the imaging data supplied from the imaging unit 150 into character data by OCR (Optical Character Recognition). In the first embodiment, the confirmation document is an insured driver's license, and the driver's license is imaged together with the security number. Hereinafter, the operation of the contract support system 10 when confirming the driver's license will be described.

  FIG. 4 is a flowchart of processing relating to communication between the mobile phone 100 and the contract support server 200 in the first embodiment. As shown in FIG. 4, in the first embodiment, the information processing unit 110 of the mobile phone 100 executes data transmission processing and message reception processing, and the information processing unit 210 of the contract support server 200 performs data reception processing and message transmission. Process.

  The data transmission process is a process of transmitting data related to the driver's license to the contract support server 200, and starts when an employee of the agency operates the operation unit 170 to input a specific instruction to the mobile phone 100. As shown in FIG. 5, the specific instruction is input by arranging the driver's license, the application form, and the mobile phone 100 so that the driver's license and the security number described in the application form are within the imaging area. Done after.

  When a specific instruction is input, the information processing unit 110 first executes an imaging process (S101). Thereby, imaging data including imaging data of the driver's license and imaging data of the security number described in the application form is supplied from the imaging unit 150 to the information processing unit 110. Next, the information processing unit 110 executes a conversion process for converting the imaged data into character data by OCR (S102).

  FIG. 6 is a schematic view illustrating the content of character data in the first embodiment. As shown in FIG. 6, the character data is data indicating information in characters for each item, and includes a security number and confirmation data (first data) D1. The confirmation data D1 is data including information necessary for confirmation at the time of conclusion of the automobile insurance contract among the information described in the driver's license.

  That is, in the conversion process, only information necessary for confirmation at the time of conclusion of the automobile insurance contract is selected and converted from the information described in the driver's license. This selection is possible because it is known in advance where and what is written on the driver's license. In addition, all the information described in the driver's license is converted, and from the converted information, only the information necessary for confirmation at the conclusion of the car insurance contract is selected to generate the confirmation data D1. Also good.

  In FIG. 4, the information processing unit 110 transmits the character data thus obtained to the contract support server 200 (S103). The information processing unit 210 of the contract support server 200 executes data reception processing each time character data from the mobile phone 100 arrives. Specifically, the information processing unit 210 receives data coming from the mobile phone 100 (S201), and stores the confirmation data D1 and the security number included in the received data in the storage unit 221 in association with each other. (S202).

  Further, the information processing unit 110 of the mobile phone 100 executes a message reception process every time a message from the contract support server 200 arrives. Specifically, the information processing unit 110 receives an incoming message (S151), and notifies the employee of the agency of the reception of the message (S152). In this notification, an image indicating that the message has been received is displayed on the display unit 160. The type of message that the information processing unit 210 transmits is as described below.

  FIG. 7 is a flowchart of the confirmation fastening process in the first embodiment. This confirmation conclusion process is a process for concluding an automobile insurance contract after confirmation, and is executed by the information processing unit 210 for each confirmation data D1 stored in the storage unit 221 at a constant time interval (for example, one day). Is done. When a certain confirmation data D1 is “target confirmation data D1”, in the confirmation conclusion process related to the target confirmation data D1, the information processing unit 210 first applies the application data D2 corresponding to the target confirmation data D1 (hereinafter “target application data”). A reading process of reading data D2) from the application DB 222 is executed.

  In the reading process, the information processing unit 210 first performs an acquisition process of the target application data D2 (S251). Specifically, the application data D2 (target application data D2) associated with the same security number as that associated with the target confirmation data D1 is read from the application DB 222. This trial succeeds when the target application data D2 is stored in the application DB 222, and fails when it is not stored. Next, the information processing unit 210 determines whether or not this trial is successful, that is, whether or not the target application data D2 has been acquired (S252).

  When this determination result is negative, that is, when the target application data D2 is not stored in the application DB 222, the information processing unit 210 determines whether or not a predetermined time (for example, one week) has elapsed since the reception of the target confirmation data D1. Is determined (S253). If the result of this determination is negative, the reading process and the confirmation fastening process are also terminated. On the other hand, when the result of this determination is affirmative, the information processing unit 210 performs first error processing. In the first error processing, the information processing unit 210 returns a message prompting the submission of the application form to the mobile phone 100 that is the transmission source of the target confirmation data D1 (S254). Then, the first error process, the reading process, and the confirmation fastening process are finished. In the mobile phone 100 that is the message destination, the above-described message reception process is performed.

  Note that a message indicating that the corresponding application data D2 is not registered may be transmitted instead of the message prompting the submission of the application form. However, either message must be a message including information (for example, a security number) by which an employee of the agency can specify the corresponding automobile insurance contract. This also applies to other messages transmitted in the confirmation and conclusion process.

  When the target application data D2 can be acquired (S252: YES), the information processing unit 210 generates contract data indicating the conditions and contents of the contract to be concluded based on the target confirmation data D1 and the target application data D2. Execute the generation process. In the generation process, the information processing unit 210 firstly includes name information and target confirmation data included in the acquired application information (hereinafter referred to as “target application information”) based on the target application data D2 and the target confirmation data D1. It is determined whether or not the name information indicated by D1 matches (S255).

  If the result of this determination is negative, that is, if both the name information do not match, the information processing section 210 applies the name information written on the driver's license and the corresponding application form (hereinafter referred to as “target application form”). ) Is returned to the mobile phone 100 that is the source of the target confirmation data D1 (S256). This completes the generation process and the confirmation fastening process.

  The agent of the agent who has visually recognized this message checks whether the target confirmation data D1 or the target application data D2 is incorrect, deletes the target application data D2 from the application DB 222, and corrects the name information of the insured person. Either the work of submitting the application form or the target confirmation data D1 is deleted from the storage unit 221 and the text data related to the correct driving license is transmitted from the mobile phone 100 to the contract support server 200.

  On the other hand, when both the name information match (S255: YES), the information processing unit 210 determines whether or not today is a date within the expiration date of the driver's license based on the target confirmation data D1. (S257). If the result of this determination is negative, the information processing section 210 returns a message indicating that the confirmation document has expired to the mobile phone 100 that is the transmission source of the target confirmation data D1 (S258). This completes the generation process and the confirmation fastening process. Note that the order of determining whether or not both names match (S255) and determining whether or not today is within the expiration date of the driver's license (S257) is arbitrary.

  By the way, in 1st Embodiment, if the insured person's excellent driver information (excellent driver / non-excellent driver) is different, the insurance premium is different even if the insurance money is the same. For example, even if the insurance money is the same, the premium is low when the insured is a good driver, and the premium is high when the insured is a non-excellent driver. Also, if the age group to which the insured belongs is different, the insurance premium is different even if the insurance money is the same. As described above, in the first embodiment, the superior driver information of the insured person and the age group to which the insured person belong respectively indicate the conditions (rights and obligations) of the automobile insurance contract. In the following description, the superior driver information of the insured is appropriately referred to as “driver condition”, and the age group to which the insured belongs is referred to as “age condition”.

  When today is a date within the expiration date of the driver's license (S257: YES), the information processing unit 210 determines that the date of birth indicated by the target confirmation data D1 is based on the target application data D2 and the target confirmation data D1. Then, it is determined whether or not the age condition derived from the target application data D2 is satisfied (S259). That is, it is determined whether the age condition determined from the date of birth described in the driver's license of the insured person matches the age condition determined from the date of birth described in the target application for the insured person. .

  If the result of this determination is negative, the information processing section 210 performs second error processing. In the second error processing, the information processing unit 210 transmits a message prompting to submit an application satisfying the age condition (message prompting to change the target application data D2 to satisfy the age condition) and transmitting the target confirmation data D1. A reply is made to the original mobile phone 100 (S260). This completes the second error process, the generation process, and the confirmation fastening process. Instead of this message, a message indicating that the age condition derived from the target application form and the age condition derived from the driver's license do not match may be transmitted.

  When the date of birth indicated by the target confirmation data D1 satisfies the age condition derived from the target application data D2 (S259: YES), the information processing unit 210 determines that the insured person is excellent based on the target confirmation data D1. It is determined whether or not the user is a driver (S261). When the result of this determination is negative, the information processing section 210 determines whether or not the excellent driver information determined from the license color described in the target application form indicates that the driver is an excellent driver (S262). .

  When the result of this determination is affirmative, that is, when the actual license color is blue or green, but the license color described in the target application is gold, the information processing unit 210 performs third error processing. I do. That is, if the driver condition indicated by the target confirmation data D1 is more disadvantageous for the applicant than the driver condition indicated by the target application data D2, the third error process is performed.

  In the third error processing, the information processing unit 210 sends a message prompting the submission of an application form that satisfies the driver condition (message prompting to change the target application data D2 to satisfy the driver condition) and the target confirmation data D1. Is sent back to the mobile phone 100 of the transmission source (S263). This completes the third error process, the generation process, and the confirmation fastening process. Instead of this message, a message indicating that the excellent driver information derived from the target application form does not match the excellent driver information derived from the driver's license may be transmitted.

  If the excellent driver information determined from the license color described in the target application does not indicate that it is a good driver (S262: NO), that is, the actual license color is blue or green, and the target application When the license color described in the above is blue or green, the information processing unit 210 performs a contract conclusion process (S264). This contract conclusion process is also performed when the insured is a good driver (S261: YES). Note that the order of determining whether the age condition is satisfied (S259) and determining whether the driver is a good driver (S261) is arbitrary.

  In the contract conclusion process, the information processing unit 210 first generates contract data indicating the conditions and contents of the automobile insurance contract related to the target application form based on the target application data D2 and the target confirmation data D1. Sign an auto insurance contract. Specifically, for each item in the application form, the information derived from the target application form is compared with the information derived from the driver's license, and based on the result of this comparison (match / mismatch) Select and generate contract data using the selected information.

  In the above selection, the information processing unit 210 selects information derived from the target application when the two information match, and selects information derived from the driver's license when the two information do not match. For example, if the address information of the insured person derived from the target application does not match the address information of the insured person derived from the driver's license, the address information of the insured person derived from the driver's license is selected. Is done. That is, the information processing unit 210 generates contract data by giving priority to the target confirmation data D1 over the target application data D2 in the contract conclusion process. This is because the description of the driver's license (official document) is generally more accurate than the description of the application form.

  However, if the process for generating the contract data in preference to the target confirmation data D1 is adopted as the generation process, the applicant may suffer an unexpected disadvantage. Specifically, this is a case where an automobile insurance contract with a condition that is more disadvantageous for the user than the condition derived from the target application form is concluded. For example, the insured's excellent driver information derived from the target application indicates that the driver is an excellent driver, and the insured's excellent driver information derived from the driver's license is a non-excellent driver. If the contract data is generated by selecting the excellent driver information (non-excellent driver) of the insured person derived from the driver's license, the insurance that the applicant assumed based on the contents of the target application form A car insurance contract with a premium higher than the premium will be signed.

However, as is apparent from the branch from step S261 in FIG. 7, in the first embodiment, the driver conditions derived from the target application form and the driver conditions derived from the driver's license do not match, and When the driver condition derived from the driver's license is not more advantageous for the applicant than the driver condition derived from the target application, the contract conclusion process is not performed and the third error process is performed. In other words, if the driver conditions derived from the target application form match the driver conditions derived from the driver license, or the driver condition derived from the driver license is applied rather than the driver condition derived from the target application form. The contract conclusion process is performed only when it is advantageous to the user.
In addition, as apparent from the branch from step S259 in FIG. 7, in the first embodiment, it is derived from the age condition indicated by the date of birth information of the insured person derived from the target application and the driver's license. If the age condition indicated by the date of birth information of the insured person does not match, the contract conclusion process is not performed and the second error process is performed.
Therefore, according to the first embodiment, there is no possibility that an automobile insurance contract having a condition that is more disadvantageous to the user than the condition derived from the target application form is concluded. In addition, you may make it handle age conditions similarly to the handling of driver | operator conditions. In other words, if the age condition derived from the target application and the age condition derived from the driver's license match, or the age condition derived from the driver's license is more advantageous for the applicant than the age condition derived from the target application. The contract conclusion process may be performed only in a case.

  Next, the information processing unit 210 transmits the generated contract data to the terminal 300 and the contract management server 400. This contract data is received by the contract management server 400 and stored in the contract DB 410. The contract data is received by the terminal 300. As a result, the terminal 300 can display information indicated by the contract data. That is, the employee of the insurance company that uses the terminal 300 can easily know information about the newly concluded car insurance contract without delay. This will contribute to the efficiency of shipping insurance policy.

  Next, the information processing unit 210 deletes the target confirmation data D1 from the storage unit 221 and deletes the target application data D2 from the application DB 222. Thereby, the contract conclusion process is completed. The target confirmation data D1 and the target application data D2 are saved in a storage area of the storage unit 220 that is neither the storage unit 221 nor the application DB 222. This is a measure for making it possible to refer to the target confirmation data D1 and the target application data D2 after the fact.

  Next, the information processing unit 210 performs content notification processing for notifying the agent of the agency of the conditions and content of the concluded auto insurance contract (S265). Specifically, first, the generated contract data is returned to the mobile phone 100 that is the transmission source of the target confirmation data D1. Secondly, in the contract conclusion process, whether or not the contract confirmation data D1 has been generated in preference to the target application data D2, that is, the contract conditions and contract contents determined from the description contents of the target application form are changed. Data indicating whether or not a car insurance contract is concluded is returned to the mobile phone 100. Third, in the contract conclusion process, when the contract data is generated with priority on the target confirmation data D1 over the target application data D2, the contents of the priority target confirmation data D1 (for example, derived from the driver's license) A change notification process for returning data indicating excellent driver information) to the mobile phone 100 is performed. Then, when the content notification process ends, the generation process and the confirmation fastening process also end.

Second Embodiment
The second embodiment is an embodiment obtained by modifying the first embodiment. In the second embodiment, as shown in FIG. 8, the driver's license is imaged alone, and the security number is not imaged. In the second embodiment, a data transmission process partially different from the data transmission process in the first embodiment is employed as the data transmission process in the mobile phone 100.

  FIG. 9 is a flowchart of data transmission processing in the second embodiment. As shown in FIG. 9, in the data transmission process in the second embodiment, a conversion process (S102) for converting imaging data into character data by OCR and a process for transmitting character data to the contract support server 200 (S103). In the middle, a security number input process (S104) is inserted. In this process, an employee of the agency operates the operation unit 170 to input the security number into the mobile phone 100. That is, the information processing unit 110 of the mobile phone 100 acquires the securities number in FIG. 6 based on the signal from the operation unit 170.

  As described above, since the driver's license is imaged independently in the second embodiment, the confirmation data D1 in FIG. 6 is obtained by the conversion process (S102). That is, there is a shortage of securities numbers. However, as described above, the shortage is compensated by the securities number input process (S104), and character data including the confirmation data D1 and the securities number is obtained. Then, the character data is transmitted to the contract support server 200 (S103).

<Third Embodiment>
The third embodiment is an embodiment obtained by modifying the first embodiment. In the third embodiment, as in the second embodiment, the driver's license is imaged alone, and the security number is not imaged. However, in the second embodiment, the same data transmission process as the data transmission process in the first embodiment is adopted as the data transmission process in the mobile phone 100. Therefore, the character data that does not include the security number but includes the confirmation data D1 is transmitted to the contract support server 200. Therefore, in the third embodiment, a data reception process that is partially different from the data reception process in the first embodiment is adopted as the data reception process in the contract support server 200.

  FIG. 10 is a flowchart of data reception processing in the third embodiment. In this data reception process, a process between receiving the received data (confirmation data D1) (S201) and a process of associating the confirmation data D1 and the securities number with each other and storing the data in the storage unit 221 (S202). The process for obtaining the security number (S203) is inserted. In this process, the information processing unit 210 of the contract support server 200 performs a search in the application DB 222 using information (for example, name information, address information, and date of birth information) included in the received confirmation data D1 as a search key. The application data D2 corresponding to the confirmation data D1 is specified. Then, the securities number associated with the specified application data D2 is read from the application DB 222.

  As described above, the data coming from the mobile phone 100 is the confirmation data D1. That is, there is a shortage of securities numbers. However, as described above, the shortage is compensated for by the process of acquiring the security number (S203), and the confirmation data D1 and the security number are obtained. Then, the obtained confirmation data D1 and securities number are associated with each other and stored in the storage unit 221 (S202).

<Fourth embodiment>
The fourth embodiment is an embodiment obtained by modifying the first embodiment. In the fourth embodiment, as in the first embodiment, a driver's license is imaged together with a security number (see FIG. 5). The fourth embodiment is different from the first embodiment in that the conversion process for converting the imaging data into character data by OCR is performed not in the mobile phone 100 but in the contract support server 200, and not in the confirmation data D1. It is only a point that the imaging data of the license becomes the first data.

  FIG. 11 is a flowchart of data transmission processing and data reception processing according to the fourth embodiment. As shown in FIG. 11, in the data transmission process in the fourth embodiment, between the imaging process (S101) for acquiring imaging data related to the imaging area and the process for transmitting data to the contract support server 200 (S103). There is no conversion process (S102 in FIG. 4) for converting the imaging data into character data by OCR. Therefore, imaging data including imaging data (first data) of a driver's license and imaging data of a security number is transmitted to the contract support server 200 instead of character data.

  The data reception process in the fourth embodiment is executed every time image data from the mobile phone 100 arrives. Further, in this data reception process, between the process of receiving incoming data (imaging data) (S201) and the process of storing the confirmation data D1 and the security number in association with each other in the storage unit 221 (S202), A conversion process (S204) for converting received data into character data by OCR is inserted. This conversion process differs from the conversion process (S102) of FIG. 4 only in that the received data is converted. In the fourth embodiment, since the imaging data is received in step S202, the confirmation data D1 and the security number are obtained by this conversion process (S204), and the obtained confirmation data D1 and the security number are stored in association with each other. It is stored in the part 221 (S202).

  The received imaging data is stored together with the corresponding confirmation data D1 and application data D2 in a storage area of the storage unit 220 that is neither the storage unit 221 nor the application DB 222 even after the automobile insurance contract is concluded. The This is a measure for making it possible to refer to the imaging data after the fact.

  Further, the same modification as the modification from the first embodiment to the second embodiment may be applied to the fourth embodiment. The flowchart of the data transmission process and the data reception process in Modification 1 obtained in this way is as shown in FIG. Further, the same modification as the modification from the first embodiment to the third embodiment may be applied to the fourth embodiment. A flowchart of the data reception process in Modification 2 obtained in this way is as shown in FIG.

<Fifth Embodiment>
The fifth embodiment is an embodiment obtained by modifying the first embodiment. The fifth embodiment differs from the first embodiment only in that the health insurance card of the insured person, not the insured driver's license, is used as the confirmation document.

  FIG. 14 is a schematic view illustrating the content of character data in the fifth embodiment. As shown in FIG. 14, the confirmation data D <b> 1 in the fifth embodiment includes information necessary for confirmation when the automobile insurance contract is concluded among the information described in the health insurance card. As is clear from a comparison between FIG. 6 and FIG. 14, the excellent driver information is not included in the confirmation data D <b> 1 in the fifth embodiment. Therefore, in the fifth embodiment, a confirmation fastening process that is partially different from the confirmation fastening process in the first embodiment is adopted as the confirmation fastening process.

  FIG. 15 is a flowchart of the confirmation fastening process in the fifth embodiment. As is clear from the comparison between FIG. 7 and FIG. 15, steps S <b> 261 to S <b> 263 are deleted in the confirmation fastening process in the fifth embodiment. That is, there is no branch based on the driver condition, and the information processing unit 210 of the contract support server 200 applies the age condition determined from the date of birth described in the health insurance card of the insured person and the application for the insured person. When the age condition determined from the date of birth described in the document matches (S259: YES), the contract conclusion process (S264) is performed unconditionally. In other words, an automobile insurance contract is always concluded under the driver conditions derived from the target application form.

  A modification similar to the modification from the first embodiment to the second embodiment may be applied to the fifth embodiment (Modification 3). Further, a modification similar to the modification from the first embodiment to the third embodiment may be applied to the fifth embodiment (Modification 4). Further, a modification similar to the modification from the first embodiment to the fourth embodiment may be applied to the fifth embodiment (Modification 5).

<Sixth Embodiment>
The sixth embodiment is an embodiment obtained by modifying the first embodiment. The sixth embodiment differs from the first embodiment only in that vehicle verification of the insured's own vehicle is used as the confirmation document, not the insured driver's license.

  FIG. 16 is a schematic view illustrating the content of character data in the sixth embodiment. As shown in FIG. 16, the confirmation data D <b> 1 in the sixth embodiment includes information necessary for confirmation at the time of conclusion of the automobile insurance contract among the information described in the vehicle verification. As is clear from the comparison between FIG. 6 and FIG. 16, the confirmation data D <b> 1 in the sixth embodiment does not include excellent birth date information and driver information. Therefore, in the sixth embodiment, a confirmation fastening process that is partially different from the confirmation fastening process in the first embodiment is adopted as the confirmation fastening process.

  FIG. 17 is a flowchart of the confirmation fastening process in the sixth embodiment. As is clear from a comparison between FIG. 7 and FIG. 17, steps S259 to S263 are deleted in the confirmation fastening process in the sixth embodiment. That is, there is no branch based on the age condition and the driver condition, and the information processing unit 210 of the contract support server 200 matches the name information indicated by the target application data D2 and the name information indicated by the target confirmation data D1 ( S255: YES), and if today is the day before the vehicle inspection expiry date for vehicle verification (S257: YES), the contract conclusion process (S264) is performed unconditionally.

  Note that the sixth embodiment is modified so that the confirmation data D1 includes vehicle registration information such as a vehicle registration number, and vehicle registration information derived from vehicle verification is preferentially selected in the contract conclusion process (S264). (Modification 6). Further, the sixth embodiment is modified so that the credit card of the applicant is used as the confirmation document instead of the vehicle verification of the insured's owned vehicle, and the credit derived from the credit card is used in the contract conclusion process (S264). Information such as a card number may be selected with priority (Modification 7).

  Further, a modification similar to the modification from the first embodiment to the second embodiment may be applied to the sixth embodiment, modification 6 and modification 7 (modification 8). Further, a modification similar to the modification from the first embodiment to the third embodiment may be applied to the sixth embodiment, modification 6 and modification 7 (modification 9). Further, a modification similar to the modification from the first embodiment to the fourth embodiment may be applied to the sixth embodiment, modification 6 and modification 7 (modification 10).

<Other variations>
The above-described first to sixth embodiments and modifications 1 to 10 can be variously modified. Specific modifications are exemplified below. Any two or more forms exemplified below may be appropriately combined.

(1) Modification 11
In the first to fourth embodiments and the modified examples 1 and 2 in which the driver's license of the insured person is the confirmation document, without changing the confirmation document (while keeping the driver's license of the insured person), FIG. A similar confirmation fastening process may be employed. In this case, the automobile insurance contract is always concluded under the driver condition derived from the target application form.

(2) Modification 12
In the first to fourth embodiments and modified examples 1 and 2 in which the driver's license of the insured person is the confirmation document, without changing the confirmation document (while keeping the driver's license of the insured person), FIG. A similar confirmation fastening process may be employed. In this case, the automobile insurance contract is always concluded under the age condition and driver condition derived from the target application form.

(3) Modification 13
In the fifth embodiment and the modified examples 3 to 5 where the health insurance card of the insured person is the confirmation document, the confirmation document is the same as in FIG. 17 without changing the confirmation document (while keeping the health insurance card of the insured person). A fastening process may be employed. In this case, the automobile insurance contract is always concluded under the age condition derived from the target application form.

(4) Modification 14
If the application data D2 corresponding to the target confirmation data D1 cannot be acquired in the confirmation conclusion process (S252: NO), a message prompting the submission of the application form or the corresponding application data D2 is registered immediately. You may make it transmit the message which shows that there is no.

(5) Modification 15
In each of the above-described embodiments and modifications, in the confirmation conclusion process, when the confirmation document has expired, a message indicating that the confirmation document has expired is sent every day. The time interval at which this message is transmitted may be one week or may be arbitrarily set.

(6) Modification 16
The form in which the imaging data is not transmitted from the mobile phone 100 to the contract support server 200 is modified, and the imaging data is transmitted from the mobile phone 100 to the contract support server 200. This imaging data is stored in the storage unit 220 even after the automobile insurance contract is concluded. Among the storage areas, the storage area that is neither the storage unit 221 nor the application DB 222 may be stored together with the corresponding confirmation data D1 and application data D2.

(7) Modification 17
The confirmation fastening process may be executed only once triggered by the storage of the confirmation data D1 in the storage unit 221. FIG. 18 shows a flowchart of the confirmation fastening process when this modification is applied to the sixth embodiment. As shown in FIG. 18, in this form, when the application data D2 corresponding to the target confirmation data D1 cannot be acquired (S252: NO), a message prompting the submission of the application form or the corresponding application A message indicating that the data D2 is not registered is transmitted (S254). This embodiment has an advantage that the time from when the data related to the confirmation document is transmitted from the mobile phone 100 to the contract support server 200 until the contract conclusion process is started is shortened.
In this embodiment, when imaging data instead of text data is transmitted from the cellular phone 100 to the contract support server 200, the imaging data (first data) of the driver's license is stored in the storage unit 221 as confirmation data D1. Then, before the application data acquisition process (S251) corresponding to the confirmation data D1, the confirmation data D1 may be converted to obtain character data.
By the way, in the case of contract renewal or transfer from another company, it is not uncommon to create an application form in which information is written in advance on the agency side and hand the created application form to the applicant. In this case, the application data D2 corresponding to the confirmation data D1 can be stored in the application DB 222 before the confirmation data D1 is stored in the storage unit 221. However, this is not always the case.
In the case where the application data D2 corresponding to the confirmation data D1 is stored in the application DB 222 after the confirmation data D1 is stored in the storage unit 221, in this embodiment, the contract support server 200 prompts the mobile phone 100 to submit an application form. A message is sent and nothing happens after that. That is, the mobile phone 100 must transmit the confirmation data D1 to the contract support server 200 again after the application data D2 corresponding to the confirmation data D1 is stored in the application DB 222.
In other words, in the first to sixth embodiments and modifications 1 to 16, after the confirmation data D1 is stored in the storage unit 221, application data D2 corresponding to the confirmation data D1 is stored in the application DB 222. Even in this case, there is an advantage that it is not necessary to retransmit the confirmation data D1 to the contract support server 200.

(8) Modification 18
An agent employee may present multiple contract patterns to the applicant. In this case, a plurality of application forms corresponding to a plurality of contract patterns are printed on the agency side, and application data D2 corresponding to each is stored in the application DB 222. Since only one of the application data D2 is connected to the car insurance contract that is actually concluded, the application data D2 includes the same security number. That is, the application data D2 cannot be specified only by the securities number.
Therefore, in preparation for this case, the car insurance contract may be identified by the security number and the printing serial number. For example, the driver's license may be imaged together with the security number and the printing serial number. The print serial number is a series of numbers for identifying printed application forms and is described in the application form. Of course, in the application information acquisition process (for example, S251 in FIG. 7), when there are a plurality of application data D2 indicating the same security number, the application data D2 is displayed on the display unit 320 of the terminal 300, and the insurance company's The employee (inquiries to the agency) may select one application data D2 from the application data D2 as the target application data D2.

(9) Modification 19
There may be a plurality of confirmation documents. For example, the driver's license of the insured person and the vehicle verification of the vehicle owned by the insured person may be used as the confirmation document. In this case, the contract conclusion process (for example, S265 in FIG. 7) is performed only after the confirmation of the driver's license and the confirmation of the vehicle verification are completed. When there are a plurality of confirmation documents, it is desirable that data related to a plurality of confirmation documents can be transmitted to the contract support server 200 with one mobile phone 100.
FIG. 19 is a flowchart showing a part of data transmission processing in the mobile phone 100 corresponding to a plurality of confirmation documents. This data transmission process is a modification of the data transmission process in the first embodiment, and performs a form selection process (S105) for selecting one form from a plurality of forms prior to the imaging process (S101). The conversion in the conversion process (S106) after the imaging process is a conversion using the selected form.
The form is data indicating where and how in the corresponding confirmation document, and is prepared in advance for each confirmation document. For example, if the confirmation document is a driver's license and vehicle verification, a driver's license form and a vehicle verification form are prepared in advance. In the form selection process, the information processing unit 210 of the mobile phone 100 selects one of the prepared forms in accordance with an instruction from an employee of the agency.
Note that the form may be selected based on the imaging data instead of being instructed by the employee of the agency. In this case, the form selection process is performed after the imaging process, not before the imaging process. Then, conversion using the form selected by the form selection process is performed in the conversion process. In this form, the form selection process and the conversion process can be performed by the contract support server 200.

(10) Modification 20
In the form in which the security number is imaged, the security number may be imaged separately from the confirmation document. That is, the confirmation document and the security number do not necessarily have to be imaged at once, and each may be imaged in two steps.

(11) Modification 21
Instead of the security number, a QR code that can identify the automobile insurance contract may be used. That is, any information may be used as long as the car insurance contract can be identified.
In the conversion process, data relating to colors included in the imaging data may be converted into character data. For example, the imaging data includes color data indicating a license color (gold, blue, or green), and character data (for example, a color string corresponding to the color indicated by the color data) is included in the character data obtained by the conversion process. , “Gold”, “Blue” or “Green”) may also be included. In this case, it is determined whether or not the insured person is a good driver (for example, S261 in FIG. 7) based on the presence or absence of the character string “excellent” described in the driver's license as in the above-described embodiments. Unlike the above-described embodiments, the confirmation data D1 obtained by the conversion process may be performed based on whether or not data indicating “gold” is included. . In this case, it is also possible to determine whether the license color is blue or whether the license color is green.
In addition, a mobile phone such as an applicant or an insurance company employee may be used as the mobile phone 100.
Further, the applicant may operate the mobile phone 100 to transmit data related to the confirmation document, data such as a security number, and the like.
Further, when the information processing unit 210 of the contract support server 200 generates contract data using the confirmation data D1 in the contract conclusion process (for example, S264 in FIG. 7), the contract data is generated using the confirmation data D1. A message for inquiring whether or not to generate contract data may be determined based on a response to the message. That is, the user of the mobile phone 100 may be allowed to select whether to generate contract data using the confirmation data D1.
Further, the communication method between the mobile phone 100 and the contract support server 200 is not limited to the communication method by e-mail, and various methods can be used.
Further, a PDA may be used instead of the mobile phone 100. However, this PDA needs to have at least an imaging function and a communication function. That is, any portable terminal may be used as long as it has at least an imaging function and a communication function.
Alternatively, the applicant may transmit the application data D2 to the mobile phone 100 via the Internet using a communication device such as a mobile phone or a personal computer.
Moreover, it is good also as a fire insurance contract instead of a car insurance contract. In other words, the present invention can be applied to any insurance contract, and broadly applicable to any contract.

DESCRIPTION OF SYMBOLS 10 ... Contract support system, 100 ... Mobile phone, 200 ... Contract support server, 300 ... Terminal, 400 ... Contract management server, 110 ... Information processing part, 130 ... Transmission part, 140 ... Reception part , 150... Imaging unit, 160... Display unit, 210 .. information processing unit, 220... Storage unit, 221... Storage unit, 222 .. application DB, 230. ... Display unit 400. Contract management server 410 Contract DB D1 Confirmation data D2 Application data

Claims (16)

The first data obtained by imaging at least a document that needs to be confirmed to conclude a contract can be received from the mobile terminal, and a plurality of second data prepared in advance in relation to the contract contents to be concluded by each A contract support server for managing data,
A receiving unit for receiving the first data;
A storage unit for storing the plurality of second data;
Based on the read process for reading the second data corresponding to the received first data from the storage unit and the received first data and the read second data, the contract contents to be concluded are indicated. An information processing unit that executes a generation process for generating contract data;
A contract support server characterized by that. The portable terminal transmits the first data and identification information for identifying a contract;
The receiving unit receives the first data and the identification information,
The storage unit stores the plurality of second data in association with the identification information,
The information processing unit
In the reading process, the second data corresponding to the received identification information is read from the storage unit,
In the generation process, based on the first data and the read second data, contract data indicating contract contents to be concluded is generated.
The contract support server according to claim 1, wherein:   In the reading process, if the second data corresponding to the identification information is not stored and cannot be read, the information processing unit indicates that the corresponding second data is not registered. The contract support server according to claim 2, wherein an error process is sent back to the contract support server. The first data indicates the terms of the contract,
In the generation process, the information processing unit, when the contract condition indicated by the second data and the contract condition indicated by the first data do not match, a message indicating that the contract condition does not match or The contract support server according to claim 2, wherein an error process for returning a message prompting to change the second data to satisfy the contract condition is returned to the portable terminal. The first data indicates the terms of the contract,
In the generation process, when the contract condition indicated by the first data is more advantageous to the user than the contract condition indicated by the second data, the information processing unit uses the first data to obtain the contract data. When the contract condition indicated by the first data is more disadvantageous for the user than the contract condition indicated by the second data, a message indicating that the contract condition does not match or the condition of the contract is satisfied The contract support server according to claim 2, wherein error processing is performed to return a message prompting to change the second data to the portable terminal. The first data indicates the contents of the contract,
3. The contract support according to claim 2, wherein the information processing unit generates the contract data by prioritizing the content of the contract indicated by the first data over the second data in the generation process. server.   When the information processing unit generates the contract data by prioritizing the content of the contract indicated by the first data over the second data in the generation process, the content of the first data prioritized is stored in the mobile phone The contract support server according to claim 6, wherein a change notification process to be transmitted to the terminal is executed. A storage unit for storing the first data;
8. The information processing unit according to claim 1, wherein the information processing unit acquires the first data from the storage unit at a predetermined cycle, and executes the reading process and the generation process. The contract support server described.   The first data is character data obtained by converting imaging data in the mobile terminal, or the first data is imaging data, and the information processing unit converts the received first data into character data. The contract support server according to claim 1, wherein the contract support server is executed before the reading process and the generating process.   The document that needs to be confirmed in order to conclude the contract is a driver's license, and the first data includes excellent driver information. Contract support server. The contract support server according to any one of claims 1 to 10,
A mobile terminal that performs communication with the contract support server and transmits the first data;
Contract support system with It is possible to receive from the mobile terminal first data obtained by imaging a document that needs to be confirmed in order to conclude a contract, and identification information for identifying the contract, and in advance in relation to the contract contents to be concluded A contract support server control method for storing and managing a plurality of prepared second data in a storage unit,
Reading the second data corresponding to the received identification information from the storage unit,
Based on the received first data and the read second data, contract data indicating contract contents to be concluded is generated.
A control method of a contract support server characterized by the above. The contract relates to car insurance;
The document that needs to be confirmed in order to conclude the contract is a driver's license,
The first data includes excellent driver information,
Each of the plurality of second data includes excellent driver information,
In the process of generating the contract data, when the excellent driver information included in the second data and the excellent driver information included in the first data are inconsistent, the contract conditions are inconsistent. A message indicating or a message prompting to change the second data to satisfy the conditions of the contract is returned to the mobile terminal.
The contract support server control method according to claim 12, wherein: The contract relates to car insurance;
The document that needs to be confirmed in order to conclude the contract is a driver's license,
The first data includes excellent driver information,
Each of the plurality of second data includes excellent driver information,
In the process of generating the contract data, when the excellent driver information included in the second data indicates that it is not a good driver, and the excellent driver information included in the first data indicates that it is a good driver , Generating the contract data using the first data, indicating that the excellent driver information included in the second data is an excellent driver, and the excellent driver information included in the first data is excellent driving A message indicating that the conditions of the contract do not match or a message prompting to change the second data to satisfy the conditions of the contract is returned to the mobile terminal.
The contract support server control method according to claim 12, wherein: The contract relates to car insurance;
The document that needs to be confirmed in order to conclude the contract is a driver's license,
The first data includes address information,
In the process of generating the contract data, when the address information indicated by the second data and the address information included in the first data do not match, the address information of the first data is more than the address information of the second data. Prioritize and generate the contract data,
The contract support server control method according to claim 12, wherein: In the process of generating the contract data, when the contract data is generated by giving priority to the content of the contract indicated by the first data over the second data, the content of the prioritized first data is transferred to the mobile terminal. Send,
The contract support server control method according to claim 15, wherein:

Images