JP2014149882A - Method and apparatus for processing pay-as-you-go system automobile insurance information - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a new pay-as-you-go system automobile insurance.SOLUTION: For the pay-as-you-go system automobile insurance for applying for utilization and paying an insurance fee every time of the utilization without limiting an object automobile beforehand, utilization application data including the registration number of an automobile to be an object this time is received from a terminal of an applicant, a contract data storage part storing contract data of the automobile insurance including the registration number of the object automobile for a general automobile insurance which specifies the object automobile and is effective during a contract period is searched by the registration number, and when the pertinent contract data which is the contract data including the registration number is present in the contract data storage part, the attribute data of the applicant and an application condition specified from the contract data are collated, and whether or not there is the application of a contract for the contract data to the applicant is determined. When there is the application, data for making the applicant confirm that the pay-as-you-go system automobile insurance is to be utilized separately from the contract for the contract data is transmitted to the terminal of the applicant excluding special cases.

Description

  The present invention relates to information processing technology related to pay-per-use car insurance.

  Traditionally, driver insurance has existed. Driver insurance is typically insurance that is purchased when a car that does not own a car but is borrowed from another person is driven at a certain frequency. Driver insurance typically has an insurance period of a certain length of time, such as one year, and there is a certain exclusion rule that it does not apply to cars owned by certain persons such as relatives living together. During the period, insurance is applied without having to apply for use every time. In addition, when you use a rental car, you also get automobile insurance temporarily. This is insurance that accompanies the rented car.

  In addition, WO02 / 005161 discloses a word “flexible car insurance that is personal (not vehicle-orientated)”, and a prepaid payment method is used as a price for the service. However, specific insurance details are not disclosed.

  Further, JP 2005-266877 A detects and accumulates driving conditions such as the driving time, driving time zone, traveling area, passenger seat belt wearing situation, speed, etc. of the contracted vehicle, and the accumulated information is stored in a predetermined manner. A technique is disclosed in which an insurance company server calculates insurance premiums based on stored data and charges them by a prepaid method at a time interval. However, this is a technique based on the premise that a dedicated device is installed in an automobile, and is not practical.

WO02 / 005161 JP 2005-266877 A

  In recent years, there are an increasing number of people who have a driver's license but do not own a car but rent a car as needed. Such a person does not necessarily drive frequently, so there is a problem that the insurance premium becomes high in driver insurance. Pay-per-use car insurance is preferred for such people.

  Accordingly, an object of the present invention is to provide an information processing technique related to a novel pay-per-use car insurance.

  The pay-per-use car insurance information processing method according to the present invention is targeted at (A) pay-per-use car insurance that pays a usage application and an insurance fee every time it is used without limiting the target car in advance. A reception step (including not only receiving one time but also receiving multiple times) using application data including the corresponding registration number, which is a car registration number, and (B) target Searching for a first contract data storage unit for storing car insurance contract data including the registration number of the target car for the general car insurance for which the car is specified; and (C) first contract data. When the corresponding contract data that is the contract data including the corresponding registration number exists in the storage unit, the contract data is stored in the second contract data storage unit that stores the pre-application data for the metered charge system car insurance Applicant's attribute data included in at least one of the applicant's advance application data and usage application data and the applicable conditions specified from the corresponding contract data are matched to the applicant. A determination step for determining whether the contract is applied to the contract data; and (D) if it is determined that the contract is applied to the contract data for the applicant, Except for the case of the contractor or the contractor's spouse, transmission data is sent to the applicant's terminal in order to make the applicant confirm that he / she wants to use metered car insurance separately from the contract for the contract data. Confirmation step.

  Pay-per-use car insurance is basically personal insurance, but because it is pay-per-use, a use application is made each time it is used. On the other hand, there may be a separate general automobile insurance contract for the car related to the current application. Therefore, after determining whether or not the general automobile insurance contract can be applied, the user is allowed to determine whether or not to continue the use application. Conventionally existing car insurance including driver insurance does not require such processing, and is processing specific to pay-per-use car insurance.

  In the case where the applicant is the family and relative of the contractor of the contract data, the transmission data described above may include at least a part of the contract data. Even if the applicant is the contractor's family and relatives of the relevant contract data, it is possible to use this pay-per-use car insurance in consideration of the convenience of the applicant, but after confirming the contract of the relative or family It will be judged.

  In addition, this pay-per-use car insurance information processing method applies in the (E) judging step, where the applicant corresponds to the contractor and the family or relative of the contract for the contract data, but is based on the limited special contract data included in the contract data. If it is determined that the contract for the contract data is not applicable to the contractor, it is proposed to change the limited special contract data included in the contract data, and the metered car insurance is applied separately from the contract for the contract data. You may make it further include the step which transmits the 2nd transmission data for making an applicant confirm using to an applicant's terminal. This is because it is not possible to change the contract for the contract data immediately, but to confirm whether this contract is prioritized or whether to use pay-as-you-go car insurance.

  Also, this pay-per-use car insurance information processing method (F) prompts registration of at least one of a compensation period and a compensation section after receiving a usage confirmation instruction for pay-per-use car insurance from the applicant's terminal. Transmitting the third transmission data for the application to the applicant's terminal, (G) receiving at least one of the compensation period and the compensation period from the applicant's terminal, and (H) the compensation period And the compensation section, both of the premium calculated from the compensation period and the insurance premium calculated from the compensation section may be charged. . In this way, the compensation range may be designated in terms of time, or the compensation range may be designated in the compensation section between them by designating the start point and the end point. In the latter case, for example, the start point may be specified by a mobile phone with a GPS (Global Positioning System) function. In addition, users pay attention to insurance premiums.

  In addition, this pay-per-use car insurance information processing method (I) receives fourth usage data for specifying compensation details after receiving a usage confirmation instruction for pay-per-use car insurance from the applicant's terminal. (J) when receiving data including compensation contents from the applicant's terminal, (K) determining whether the compensation content includes compensation for the vehicle, and (K) compensation content for the vehicle. Is included, the step of transmitting the fifth transmission data for prompting the applicant's terminal to transmit a photograph of the vehicle from a predetermined angle, and (L) the photographed from the applicant's terminal. Receiving the vehicle image data and storing it in the vehicle image data storage unit. This is because when the user desires vehicle insurance, it is necessary to register the state of the car in advance. The predetermined angle is the most necessary angle for handling an accident, and a necessary guide may be given.

  In addition, in this pay-per-use car insurance information processing method, the applicant applies to the contract data for the contract data corresponding to the contractor and family or relative of the contract data for the contract data in the judgment step (M). In addition, if the usage confirmation instruction for pay-as-you-go car insurance is received from the terminal of the applicant, the parameters for calculating the insurance premium of the applicant will be displayed with the contractor of the contract for the corresponding contract data. You may make it further include the step which sets to the predetermined value which premium becomes high compared with the parameter for insurance contract calculation set when it is other than a family or a relative. Parameters according to risk are set.

  In addition, the premium for the applicant's premium calculation is higher than the parameter for the insurance contract calculation set when it is determined that the contract for the contract data is not applicable. In some cases, such a predetermined value is set.

  Furthermore, this pay-per-use car insurance information processing method calculates the number of years of license holding from the license number included in the applicant's prior application data stored in the second contract data storage unit, and sets the license in advance. You may make it further include the step which specifies the parameter applicable to an applicant's license holding years among the parameter groups set so that insurance premiums may become cheaper as the license holding years are longer for each holding year range. In this way, the risk substance is reflected in the insurance premium by taking into account the number of years of license holding. For example, since the upper third digit and the fourth digit of the license number are the acquisition year, the number of years owned is calculated based on the difference from the current year.

  In addition, this pay-per-use car insurance information processing method (N) prompts registration of at least one of the compensation period and the compensation section after receiving the usage confirmation instruction of the pay-per-use car insurance from the applicant's terminal. Transmitting the third transmission data for the application to the terminal of the applicant, and (O) receiving the compensation range data including at least one of the compensation period and the compensation section from the applicant's terminal and confirming the use , The step of storing the use application data and the compensation range data in the second contract data storage unit, and (P) the applicant's compensation range data stored in the second contract data storage unit when the applicant subscribes to the general automobile insurance. And a step of determining a discount rate or an initial preferential grade for general automobile insurance when the use of a predetermined level or higher is permitted by the read coverage data. It may be so. As a result, the use of pay-per-use car insurance is promoted, and further transfer to general car insurance is also invited.

  It is possible to create a program for causing the hardware to perform the processing described above, and the program can be read by a computer such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, and a hard disk. It is stored in a possible storage medium or storage device. Note that data being processed is temporarily stored in a storage device such as a computer memory.

  New pay-per-use car insurance can be introduced.

FIG. 1 is a system configuration diagram according to the embodiment of the present invention. FIG. 2 is a diagram illustrating a processing flow of pre-registration. FIG. 3 is a diagram showing a pre-registration processing flow. FIG. 4 is a diagram illustrating a processing flow of pre-registration. FIG. 5 is a diagram showing an example of data stored in the pay-as-you-go insurance policy DB. FIG. 6 is a diagram showing a processing flow of the use application process. FIG. 7 is a diagram illustrating a process flow of the use application process. FIG. 8 is a diagram illustrating an example of an insurance type selection screen. FIG. 9 is a diagram illustrating an example of a vehicle data input screen. FIG. 10 is a diagram showing a process flow of the use application process. FIG. 11 is a diagram illustrating an example of an input screen for a compensation period and the like. FIG. 12 is a diagram illustrating a processing flow of the duplication / attribute check processing. FIG. 13 is a diagram illustrating an example of data stored in the general insurance contract DB. FIG. 14 is a diagram illustrating an example of the confirmation page A. FIG. 15 is a diagram illustrating an example of a relationship data input screen. FIG. 16 is a diagram illustrating a processing flow of the duplication / attribute check processing. FIG. 17 is a diagram illustrating an example of the confirmation page B. FIG. 18 is a diagram illustrating a processing flow of the duplication / attribute check processing. FIG. 19 is a diagram for explaining the limited special agreement. FIG. 20 is a diagram illustrating an example of a page A that cannot be accepted. FIG. 21 is a diagram illustrating an example of a page B that cannot be accepted. FIG. 22 is a diagram showing a processing flow of duplication / attribute check processing. FIG. 23 is a diagram illustrating an example of the confirmation page C. FIG. 24 is a diagram illustrating an example of the confirmation page D. FIG. 25 is a diagram showing a processing flow of duplication / attribute check processing. FIG. 26A is a diagram illustrating a processing flow of duplication / attribute check processing. FIG. 26B is a diagram illustrating an example of the confirmation page E. FIG. 27 is a diagram showing a processing flow of duplication / attribute check processing. FIG. 28 is a diagram showing a processing flow of duplication / attribute check processing. FIG. 29A is a diagram illustrating a processing flow of duplication / attribute check processing. FIG. 29B is a diagram showing a summary table of attribute checks. FIG. 30 is a diagram illustrating an example of a compensation content input screen. FIG. 31 is a diagram showing a processing flow of use application processing. FIG. 32 is a conceptual diagram of insurance premium calculation. FIG. 33 is a diagram for explaining the relationship between categories and insurance premiums. FIG. 34 is a diagram for explaining the relationship between the number of years a license is held and insurance premiums. FIG. 35 is a diagram for explaining the relationship between the number of past accidents and insurance premiums. FIG. 36 is a diagram illustrating an example of a payment method selection screen. FIG. 37 is a diagram showing an example of data stored in the pay-as-you-go insurance policy DB. FIG. 38 is a functional block diagram of a computer.

  The car insurance according to the embodiment of the present invention is a pay-as-you-go car insurance, in which basic user attribute data is registered in advance, and application for use is made before actual driving. The driving of the car is started after the contents of the insurance contract (compensation range, compensation contents, etc.) are finalized. At the time of pre-registration, it is personal auto insurance that does not specify a car. In addition, suppose that the automobile insurance which typically identified the object automobile and typically has an insurance period of one year is called general automobile insurance.

  FIG. 1 shows an outline of a system for carrying out such processing for car insurance. The network 1 including the Internet and a mobile phone communication network includes a user terminal 3 such as a personal computer or a mobile phone (in FIG. 1, the personal computer is the user terminal 3a, and in the case of a mobile phone, the user terminal 3b), A pay-as-you-go system car insurance processing server 5 that performs the main processing of the above-described form is connected. The network 1 is also connected to a partner organization server that manages a member database that stores member data and is managed by a partner organization that has a partner relationship with an insurance company that sells pay-as-you-go car insurance.

  The pay-per-use car insurance processing server 5 includes a pre-registration processing unit 51, a use application processing unit 52, a contract content check unit 53, an insurance premium calculation unit 54, and a contract takeover processing unit 55. Each processing unit of the pay-per-use car insurance processing server 5 includes a pay-per-use car insurance database (DB) 56 for storing contractor data and usage data of the pay-per-use car insurance, and a pay-per-use car insurance. Pay-as-you-go system insurance accident DB 57 for storing accident data, general insurance contract DB 58 for storing contract data for general automobile insurance, general accident DB 59 for storing accident data related to general automobile insurance, and insurance premium calculation Various data storage units 60 that store parameter data and the like can be accessed. The database and data storage unit other than the general insurance contract DB 58 may be included in the pay-per-use car insurance processing server 5. As for the general insurance contract DB 58, a replica may be included in the pay-per-use car insurance processing server 5. Further, the pay-per-use car insurance processing server 5 is realized by one or a plurality of computers. Each processing unit of the pay-per-use car insurance processing server 5 communicates with the user terminal 3 and the affiliated organization server 7 via a communication processing unit (not shown).

  The user terminals 3a and 3b have a browser function, and may have a camera or a GPS function depending on circumstances. It is assumed that various application programs can be executed, and the user terminal 3b, which is a mobile phone, can also execute a mobile application program dedicated to communication with the pay-per-use car insurance processing server 5.

  Next, the pre-registration process will be described with reference to FIGS. The applicant operates the user terminal 3 to access the pay-per-use car insurance processing server 5, and from the pay-per-use car insurance processing server 5, input page data (or pre-registration and use application) of the applicant's attribute data In the case of a portable application program, data for causing the portable application program to perform the same display is transmitted to the portable application program). Receive and display on display device. Then, the applicant operates the user terminal 3 to input attribute data, and transmits the attribute data to the pay-per-use car insurance processing server 5 (step S1).

  In this step, the user terminal 3 interacts with the multiple-time chargeable car insurance processing server 5 and the contractor name, insured person name, date of birth, address, telephone number (fixed phone, mobile phone) ), Attribute data including email address (PC, mobile phone), license data (color, renewal date and license number), password for logging into the pay-per-use car insurance processing server 5, pay-per-use car insurance You may make it transmit to the processing server 5. FIG. In addition, pay-per-use car insurance is associated with a general car insurance policy that a family or relative holds for the same insurance company. The associated general automobile insurance contract is called the main contract. That is, the attribute data includes the main contract securities number. For example, the main contract insurance policy number may be input first, the general insurance policy DB 58 may be searched from the main contract insurance policy number, and at least a part of the attribute data to be input may be omitted. Similarly, when it is known that the member is a member of an affiliated organization (for example, when it is known that a transition has been made from the affiliated organization page), the member number of the affiliated organization is input, and the pay-per-use car insurance server 5 The member data corresponding to the member number may be acquired from the affiliated organization server. Also in this case, at least a part of the attribute data to be input may be omitted. The member number of the affiliated member is also included in the attribute data.

  Further, when a mobile phone with a camera or the like is used, an image of a license is photographed and transmitted to the pay-per-use car insurance processing server 5, and the pay-per-use car insurance server 5 or a portable application program You may make it read license data.

  The pre-registration processing unit 51 of the pay-per-use car insurance processing server 5 receives the attribute data from the user terminal 3 as a pre-registration request and stores it in a storage device such as a main memory (step S3). Then, the pre-registration processing unit 51 searches the pay-as-you-go insurance DB 56 with a part of the attribute data (for example, license number, date of birth + name, etc.), and confirms whether registration for the same person has already been made. (Step S5). When such overlapping registration is recognized, the process proceeds to the process of FIG. 3 via the terminal B, and the pre-registration processing unit 51 transmits an underwriting failure notification including a message indicating that registration cannot be performed to the user terminal 3. (Step S31). The user terminal 3 receives an underwriting disapproval notification from the pay-per-use car insurance processing server 5 and displays it on the display device (step S32). Thereby, the applicant can recognize that the registration has already been made. The underwriting impossibility notification may include a part of already registered attribute data (for example, a dedicated use application URL (Universal Resource Locator)).

  Returning to the description of the processing in FIG. 2, when it is confirmed that the registration is not duplicated, the pre-registration processing unit 51 transmits the data of the insurance payment method selection page to the user terminal 3 (step S <b> 7). The user terminal 3 receives the insurance payment method selection page data and displays it on the display device (step S9). For example, a screen listing the possible payment methods such as adding credit card, electronic money, mobile phone charges, etc. is displayed, and for credit card payment, an input field for credit card number etc. (including expiration date etc.) is also displayed The

  The applicant selects a payment method, inputs a credit card number or the like in the case of a credit card, and instructs the user terminal 3 to transmit. The user terminal 3 receives a selection from the applicant (including an input in the case of a credit card), and transmits data such as a payment method to the metered-rate car insurance processing server 5 (step S11). The pre-registration processing unit 51 of the pay-per-use car insurance processing server 5 receives data such as the payment method from the user terminal 3 and stores it in a storage device such as a main memory (step S13).

  Thereafter, the pre-registration processing unit 51 transmits to the user terminal 3 data for selecting an important matter manual (hereinafter abbreviated as an important article) and a clause checking method (step S15). On the other hand, the user terminal 3 receives the page data for selecting the important article and the clause checking method from the pay-per-use car insurance processing server 5, and displays the page data on the display device (step S17). For example, a screen for selecting one of confirmation on the Web and confirmation of mailing (charged) is displayed. The user selects one of them and instructs transmission. The user terminal 3 accepts a selection input from the applicant, and transmits data of the selected confirmation method to the metered-rate car insurance processing server 5 (step S19). The pre-registration processing unit 51 of the pay-per-use car insurance processing server 5 receives the data of the confirmation method from the user terminal and stores it in a storage device such as a main memory (step S21).

  Further, the pre-registration processing unit 51 transmits data of a page for selecting a policy issuance method to the user terminal 3 (step S23). The user terminal 3 receives page data for selecting a policy issuance method from the pay-per-use car insurance server 5 and displays it on the display device (step S25). For example, a screen for selecting either web issue or mail issue (pay) is displayed. The user selects one of them and instructs transmission. The user terminal 3 accepts a selection input from the applicant, and transmits data on a method for issuing the selected insurance policy to the metered-rate car insurance processing server 5 (step S27). The pre-registration processing unit 51 of the pay-as-you-go car insurance processing server 5 receives the insurance policy issuance method data and stores it in a storage device such as a main memory (step S29). And a process transfers to the process of FIG.

  Shifting to the description of the processing in FIG. 4, the pre-registration processing unit 51 of the pay-per-use car insurance processing server 5 receives the data received so far and stored in the storage device such as the main memory as the contract data (pre-application). (Also referred to as data) is registered (ie, counted) in the pay-as-you-go insurance policy DB 56 (step S33). Also, a URL and a contract number dedicated to the applicant are issued and included in the contract data. For example, data as shown in FIG. 5 is stored in the pay-as-you-go insurance contract DB 56.

  In the example of FIG. 5, the contract number, main contract security number, contractor name, insured person name, date of birth, address, telephone (fixed, mobile phone), e-mail address (PC, mobile phone), license data ( Color, renewal date, license number), application URL, password, unacceptable flag, etc. are registered. The underwriting impossible flag is set in the accident processing when, for example, two accidents occur in one year. In addition, it is set in the accident processing even when a total of accidents more than a predetermined number have occurred. Furthermore, it is also set in the accident processing when it is detected that there is a suspicion of insurance claim fraud.

  Thereafter, the pre-registration processing unit 51 transmits a pre-registration completion notification including the use application URL and the contract number to the user terminal 3 (step S34). In addition, when the applicant chooses to refer to the insurance policy, the important article, and the clauses on the Web, the URL of the reference destination may be included. The user terminal 3 receives the pre-registration completion notification from the pay-per-use car insurance processing server 5 and displays it on the display device (step S35).

  Further, the pre-registration processing unit 51 transmits a confirmation mail including a use application URL and a contract number to a designated mail address (step S37).

  The applicant stores such data and uses it when actually applying for insurance.

  Next, processing for use application will be described with reference to FIGS. Application for use will also be made in advance before starting driving. The contractor operates the user terminal 3 to connect to the pay-per-use car insurance processing server 5, input login data, and transmit it to the pay-per-use car insurance server 5 (step S 41). An authentication processing unit (not shown) of the pay-per-use car insurance processing server 5 receives login data from the user terminal 3 (step S43), and performs authentication processing. In a normal case, when accessing the pay-per-use car insurance processing server 5 with the URL notified as the use application URL and transmitting a password, the authentication processing unit searches the pay-per-use insurance contract DB 56 with the access destination URL. The password is read out, and the read password and the received password are verified. However, since the application for use may be made immediately before driving the car, the contractor is troubled if the password is forgotten or the use application URL is lost. Therefore, for example, a combination of a use application URL and a license number, a general use application URL accessible by anyone, a combination of a license number and a password, a general use application URL accessed, a password, a contract number, and a date of birth In some cases, authentication is performed using a combination of days. Furthermore, when a mobile phone is used as a user terminal, it is also possible to apply for use using a mobile application program for pre-registration and use application, and a mobile phone or an applicant is specified in this mobile application program. If such a unique code is included, authentication using other information without a password may be possible using the unique code. The authentication processing unit outputs the contract number to the use application processing unit 52 when the authentication processing result and authentication are successful.

  When the authentication is successful, the use application processing unit 52 confirms whether the underwriting impossible flag is set on. If the underwriting impossibility flag is set to ON even if the authentication fails or the authentication is successful (step S45: Yes route), the process proceeds to the process of FIG. An underwriting impossibility notification including the reason is transmitted to the user terminal 3 (step S63). The user terminal 3 receives the underwriting impossibility notification and displays it on the display device (step S65). As a result, the contractor can determine the reason why the subscription is not possible. If the reason is authentication failure, you can re-enter and request login again.

  On the other hand, if the underwriting disable flag is off due to successful authentication (step S45: No route), the use application processing unit 52 reads the corresponding record from the pay-as-you-go insurance contract DB 56 with the contract number. And the use application process part 52 transmits the data of an insurance kind selection page (step S47). The user terminal 3 receives the insurance type selection page data and displays it on the display device (step S48). For example, a screen as shown in FIG. 8 is displayed. In the example of FIG. 8, it is selected whether to apply only for a pay-per-use car insurance or to apply a combination of a pay-per-use car insurance and domestic travel insurance / ski insurance / golfer insurance. Other combinations may be listed and selectable. In this embodiment, paying attention to pay-per-use car insurance, and for insurance other than pay-per-use car insurance, only additional processing is performed for that insurance. Is selected.

  The user terminal 3 receives the insurance type selection input from the contractor, and transmits the selected insurance type data to the pay-per-use car insurance processing server 5 (step S49). The usage application processing unit 52 of the pay-per-use car insurance processing server 5 receives the selected insurance type data and stores it in a storage device such as a main memory (step S51). Next, the use application processing unit 52 transmits the data on the vehicle data input page of the car to be driven this time to the user terminal 3 (step S53). The user terminal 3 receives the data on the vehicle data input page and displays it on the display device (step S55). For example, a screen as shown in FIG. 9 is displayed. The example of FIG. 9 includes an input field for inputting a new registration number of a car and a field for selecting a registration number and model of a car that has been driven in the past. For the registration number of a car that has been driven in the past, if the usage application processing unit 52 can retrieve the past usage registration data of the current contractor by searching, for example, the pay-as-you-go insurance policy DB 56, the usage registration data The registration numbers included in are listed.

  The contractor selects whether to input the registration number of the car to be driven this time, and instructs the user terminal 3 to transmit. The user terminal 3 receives the input of the vehicle data (that is, the registration number and model) from the contractor and transmits it to the pay-per-use car insurance server 5 (step S57). The usage application processing unit 52 of the pay-per-use car insurance processing server 5 receives the vehicle data from the user terminal 3 and stores it in a storage device such as a main memory (step S59). The use application processing unit 52 determines whether the vehicle is a vehicle that cannot be underwritten by confirming in advance from the registration number and model whether or not it corresponds to a registration number or model that cannot be underwritten in this pay-per-use car insurance system (step S61). ). If it is a vehicle that cannot be accepted, the process proceeds to the process of FIG. On the other hand, if it is a vehicle that can be accepted, the process proceeds to the process of FIG.

  Shifting to the description of the processing in FIG. 10, the use application processing unit 52 transmits input page data such as a compensation period to the user terminal 3 (step S <b> 71). The user terminal 3 receives the data of the input page such as the compensation period and displays it on the display device (step S73). For example, a screen as shown in FIG. 11 is displayed. In the example of FIG. 11, an input field for designating a compensation period by time, an input field for designating a compensation period between points, and a landmark (for example, from xx station to XX university) are designated. And an input field. Further, in the case of a mobile phone having a GPS function when driving immediately, the position data may be measured by the GPS function and transmitted to the pay-per-use car insurance processing server 5. You may make it designate both the designation | designated compensation period of time and the designation | designated compensation period between points. If the compensation period is not specified by time, additional processing such as sending and registering position data to the pay-per-use car insurance server 5 by the GPS function immediately before driving is required.

  The contractor operates the user terminal 3 to input the compensation period and instruct transmission. The user terminal 3 receives an input such as a compensation period, and transmits data such as the compensation period to the metered-rate car insurance processing server 5 (step S75). The usage application processing unit 52 of the pay-per-use car insurance processing server 5 receives data such as a compensation period and stores it in a storage device such as a main memory (step S77). Then, the use application processing unit 52 causes the contract content check unit 53 to perform duplication / attribute check processing (step S79). The duplication / attribute check processing will be described with reference to FIGS. 12 to 29B.

  The contract content check unit 53 searches the pay-as-you-go system insurance contract DB 56 based on the contract number and the compensation period of the contractor, and confirms whether substantially the same (that is, overlapping) use registration data has been registered. (FIG. 12: Step S101). If there is an overlap (step S103: Yes route), the process returns to the original process via the terminal H. This is to reconfirm the current application.

  On the other hand, when there is no duplication (step S103: No route), the contract content check unit 53 searches the general insurance contract DB 58 with the designated registration number, and determines whether or not the corresponding general car insurance exists (step S105). . The general insurance contract DB 58 stores data as shown in FIG. 13, for example. In the example of FIG. 13, a security number, a contractor name, an insured person name, a date of birth, an address, a telephone number (home, mobile phone), a registration number, a limited special contract, and the like are registered.

  When the general insurance contract DB 58 is searched with the designated registration number and the corresponding general automobile insurance exists, the contract data is read out. If there is no applicable general automobile insurance (step S107: No route), there may be a general automobile insurance insurance contract with another insurance company, but it cannot be specified here, so it is not a family or relative Those who drive other people's cars are eligible for pay-as-you-go car insurance and can register for use (hereinafter referred to as subscription). Accordingly, the contract content check unit 53 generates data for the confirmation page A and transmits it to the user terminal 3 (step S109). The user terminal 3 receives the data of the confirmation page A from the pay-per-use car insurance server 5 and displays it on the display device (step S111). The confirmation page A is a page as shown in FIG. 14, for example. Although the applicable general automobile insurance is not found, the car to be driven this time includes a message indicating the purpose of confirmation because there is a possibility that a general automobile insurance contract exists. The contractor inputs whether to proceed or cancel the procedure, and instructs transmission.

  The user terminal 3 accepts a selection input for subscription determination from the contractor, and transmits subscription determination data to the pay-per-use car insurance processing server 5 (step S113). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data from the user terminal 3 and stores it in a storage device such as a main memory (step S115). In addition, the contract content check unit 53 identifies the category for determining the charge parameter as category A in the case of joining via step S113 (step S116). Then, the processing shifts to the processing in FIG. In FIG. 16, processing is performed in accordance with subscription determination data representing subscription or subscription cancellation.

  On the other hand, when the corresponding general automobile insurance is extracted (step S107: Yes route), the contract content check unit 53 determines the data on the relationship data input page in order to determine whether or not the limited general contract is insured. Is transmitted to the user terminal 3 (step S117). The user terminal 3 receives the data on the relationship data input page from the pay-per-use car insurance server 5 and displays it on the display device (step S119). For example, the display as shown in FIG. 15 is performed. In the example of FIG. 15, a message indicating the contractor and the insured person and prompting the user to select a relationship in order to confirm whether or not he / she can join this time is included. In the example of FIG. 15, a combo box for selecting “spouse”, “married child”, “unmarried child”, “other relatives”, and “other than the above” is provided. The contractor selects the applicable one from these. In addition, you may make it select with a check button or a radio button. The contractor selects a relationship and instructs transmission. In addition, you may make it choose by choosing living / separating as an option.

  The user terminal 3 receives the relationship selection input from the contractor, and transmits the relationship data to the metered-rate car insurance processing server 5 (step S121). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the relationship data from the user terminal 3 and stores it in a storage device such as a main memory (step S123). The processing shifts to the processing in FIG.

  FIG. 16 shows a processing flow of processing after the terminal I. The contract content check unit 53 determines whether or not the subscription determination data received from the user terminal 3 indicates “subscription” (step S131), and returns to the original process if it indicates “subscription”. On the other hand, when “not subscribed” is indicated, the contract content check unit 53 transmits the data of the confirmation page B to the user terminal 3 (step S133). The user terminal 3 receives the data of the confirmation page B from the pay-per-use car insurance server 5 and displays it on the display device (step S135). For example, a screen as shown in FIG. 17 is displayed. In the example of FIG. 17, a button is clicked when joining another car. Although not shown, a button for selecting cancellation of the procedure may be provided. The contractor chooses to change the condition or cancel the procedure.

  The user terminal 3 receives a selection input for the condition change determination from the contractor and transmits it as condition change determination data to the pay-per-use car insurance processing server 5 (step S137). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the condition change determination data from the user terminal 3 (step S139), and determines whether the condition change is instructed (step S141). If the condition change is not instructed (step S141: No route), the process returns to the original process.

  When the condition change is instructed (step S141: Yes route), the contract content check unit 53 generates an information re-input page and transmits it to the user terminal 3 (step S143). The user terminal 3 receives the information re-input page data from the pay-per-use car insurance processing server 5 and displays it on the display device (step S145). For example, the data that can be changed is displayed in a form in which the already input data is embedded in the input field to prompt the contractor to change. The contractor inputs a change for the part that needs to be changed and instructs transmission.

  The user terminal 3 receives data input from the contractor, and transmits the input data to the metered-rate car insurance processing server 5 (step S147). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the input data from the user terminal 3 and stores it in a storage device such as a main memory (step S149). Then, the process returns to step S103 via the terminal K.

  Next, FIG. 18 shows a processing flow of processing after the terminal J. The contract content check unit 53 extracts the general contractor who applied for the current use from the received relationship data and attribute data read from the pay-as-you-go insurance policy DB 56 based on the registration number of the car in step S105. It is determined whether the person is a contractor or a spouse in the car insurance contract (step S151). If the person himself / herself, the name and date of birth are completely the same, and if the person is a spouse, the spouse is designated by the relationship data. If the contractor who applied for this time is not the extracted general automobile insurance policyholder or the spouse, the contract content check unit 53 determines the address included in the extracted general automobile insurance contract data. , Compare with the address included in the pre-application data to determine whether the extracted general car insurance policyholder and the living person (family (specifically child or other relative)) or other person living together (Step S171). If the addresses match, the process proceeds to the process of FIG. On the other hand, if they do not match, the processing shifts to the processing in FIG. In addition, if the contractor inputs the cohabitation / separation, the data is followed.

  On the other hand, in the case of the extracted general automobile insurance policyholder or spouse, the contract content check unit 53 performs the limited special contract data included in the extracted general automobile insurance contract data and the current use application. From the contractor's attribute data (including relationship data; the same applies hereinafter), it is determined whether the contractor who applied for this time is subject to a limited special contract (step S153). A specific example of the limited special offer is shown in FIG. 19, for example. For example, when the limitation condition is family limitation and the compensation is 26 years or older, a spouse who is 26 years of age or older, a cohabiting child (family) and a relative, and an unmarried child living separately are subject to a limited special agreement. Unmarried children and other persons (other than the above) who are living separately are not subject to the age condition, and are determined by their relationship, address and marital status. Therefore, if the contractor is 30 years old, a limited special provision is applied, but the contractor's spouse under the age of 26 is excluded. However, if a 25-year-old child falls under an unmarried child who is living separately, he / she is subject to a limited special agreement. In step S153, even if the contractor who applied for this time is a contractor or spouse of the extracted general automobile insurance, the contract may not be eligible for a limited special agreement based on age conditions. Is to confirm.

  When the contractor who applied for this time is subject to the limited special agreement, the contract content check unit 53 generates the data of the unacceptable page A from the extracted general automobile insurance contract data, and the user terminal 3 (Step S155). The user terminal 3 receives the data of the unacceptable page A from the pay-per-use car insurance processing server 5 and displays it on the display device (step S157). For example, a screen as shown in FIG. 20 is displayed. As shown in FIG. 20, since the contractor who applied for this time is the contractor who is covered by the general automobile insurance or the spouse, the general automobile insurance is not applied. Is likely to be applied, and is likely to be misunderstood. Therefore, this point is notified to the contractor. When applying for use with another automobile, the illustrated button is clicked. When canceling the procedure, a stop button (not shown) is clicked.

  Accordingly, the contractor confirms the display contents, selects the condition change or the procedure cancellation, and instructs transmission. The user terminal 3 receives the condition change determination input (condition change or procedure cancellation) from the contractor, and transmits the condition change determination data to the pay-per-use car insurance processing server 5 (step S159). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the condition change determination data from the user terminal 3 (step S161). Then, the processing shifts to the processing in FIG.

  On the other hand, if the contractor who applied for this time is not subject to the limited special agreement, the contract content check unit 53 generates the data of the unacceptable page B from the extracted contract data of the general automobile insurance, and the user It transmits to the terminal 3 (step S163). The user terminal 3 receives the data of the unacceptable page B from the pay-per-use car insurance processing server 5 and displays it on the display device (step S165). For example, a screen as shown in FIG. 21 is displayed. In this embodiment, if the contractor who applied for this time is a contractor or spouse of other general automobile insurance, the general automobile insurance should be applied preferentially and the subscription is accepted. Absent. Therefore, as shown in FIG. 21, it is urged to change the contract contents of the extracted general automobile insurance. In addition, when making a use application for another automobile, a button shown in the figure is clicked, and when canceling the procedure, a stop button (not shown) is clicked.

  Accordingly, the contractor confirms the display contents, selects the condition change or the procedure cancellation, and instructs transmission. The user terminal 3 receives the condition change determination input (condition change or procedure cancellation) from the contractor, and transmits the condition change determination data to the pay-per-use car insurance processing server 5 (step S167). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the condition change determination data from the user terminal 3 (step S169). Then, the processing shifts to the processing in FIG.

  Next, using FIG. 22, in step S171, it is determined that the extracted general car insurance policyholder is not the same person (a family (specifically a child or other relative)) or another person living together. A process after transition through the terminal M will be described.

  Here, there may be a separate family member (unmarried child), a relative (including a married child) or another person, but the relationship data received from the contractor indicates that the contractor who applied for this time is "Unmarried It is determined whether or not “child” is indicated (step S181). If it does not fall under “unmarried child”, the process proceeds to the process of FIG.

  On the other hand, in the case of “unmarried child”, the contract content check unit 53 uses the limited special contract data included in the extracted general automobile insurance contract data to determine whether the contractor who applied for this time uses the limited special contract. It is confirmed whether it is a target (step S183). For example, “children” are not eligible if the person / spouse is a special contract. When the contractor who applied for this time is a target of the limited special contract, the contract content check unit 53 generates the data of the confirmation page C from the extracted contract data of the general automobile insurance, and sends it to the user terminal 3. Transmit (step S185). The user terminal 3 receives the data of the confirmation page C from the pay-per-use car insurance server 5 and displays it on the display device (step S187). For example, a screen as shown in FIG. 23 is displayed. In the example of FIG. 23, a message indicating that the extracted general automobile insurance is used for compensation is included, but it is shown that the user can join the pay-as-you-go car insurance as it is. This is because, for unmarried children, etc., it is preferable to accumulate their driving performance in anticipation of future independence (the driving performance is taken over when subscribing to general car insurance as described below) Grades may be preferential), and even if an accident occurs, there is a request that you do not want to use general car insurance such as parents, so you can join twice. The contractor determines whether or not to proceed with the pay-as-you-go car insurance procedure as it is, and inputs it.

  The user terminal 3 receives the selection input for the subscription determination from the contractor, and transmits the subscription determination data to the pay-per-use car insurance processing server 5 (step S189). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S191). Further, the contract content check unit 53 identifies the category for determining the insurance premium as category C (step S192). And it transfers to the process of FIG.

  On the other hand, if it is determined in step S183 that the contract is not covered by the limited special agreement, the contract content check unit 53 generates the data for the confirmation page D from the extracted general automobile insurance contract data, and the user terminal 3 (Step S193). The user terminal 3 receives the data of the confirmation page D from the pay-per-use car insurance processing server 5 and displays it on the display device (step S195). For example, a screen as shown in FIG. 24 is displayed. In the example of FIG. 24, a part of the extracted contract data of the general automobile insurance is included, and notification is made that compensation is made if the contract contents of the general automobile insurance are changed. If you want to use pay-as-you-go car insurance without changing the contract, reply to that effect. That is, an input is made to continue the subscription application procedure. On the other hand, the subscription application procedure may be interrupted.

  The user terminal 3 receives the selection input for the subscription determination from the contractor, and transmits the subscription determination data to the pay-per-use car insurance processing server 5 (step S197). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S199). Further, the contract content check unit 53 identifies the category for determining the insurance premium as category B (step S200). And it transfers to the process of FIG.

  Next, the process after it is determined in step S181 that the child is not an unmarried child and the transition is made through the terminal O will be described with reference to FIG.

  The contract content check unit 53 uses the extracted general automobile insurance contract data and the attribute data (including relationship data) of the contractor who applied for this time to extract the relatives It is determined whether it includes a child (step S201). Here, it is determined whether or not it is a “separate relative”. If it is not a separate relative, the process proceeds to the process of FIG.

  On the other hand, in the case of a separate relative, the contract content check unit 53 includes the limited special contract data included in the extracted general automobile insurance contract data and the attribute data (including the relationship data) of the contractor who applied for this time. ), It is confirmed whether the contractor who applied for this time is a limited special contract (step S203). For example, if the limitation of the person is limited to the person / spouse, the separate relatives are not eligible for the restriction.

  When the contractor who applied for this time is a target of the limited special contract, the contract content check unit 53 generates the data of the confirmation page C from the extracted contract data of the general automobile insurance, and sends it to the user terminal 3. Transmit (step S205). The user terminal 3 receives the data of the confirmation page C from the pay-per-use car insurance server 5 and displays it on the display device (step S207). For example, a screen as shown in FIG. 23 is displayed. Since FIG. 23 has been described above, description thereof is omitted here. Then, the contractor determines whether or not to proceed with the procedure of the pay-per-use car insurance as it is or cancels the input.

  The user terminal 3 receives the selection input for the subscription determination from the contractor, and transmits the subscription determination data to the pay-per-use car insurance processing server 5 (step S209). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S211). Further, the contract content check unit 53 identifies the category for determining the insurance premium as the category E (step S212). And it transfers to the process of FIG.

  On the other hand, if it is determined in step S203 that the contract is not covered by the limited special contract, the contract content check unit 53 generates the data of the confirmation page D from the extracted general automobile insurance contract data, and the user terminal 3 (Step S213). The user terminal 3 receives the data of the confirmation page D from the pay-per-use car insurance server 5 and displays it on the display device (step S215). For example, a screen as shown in FIG. 24 is displayed. Since FIG. 24 has been described above, description thereof is omitted here. Then, the contractor determines whether or not to proceed with the procedure of the pay-per-use car insurance as it is or cancels the input.

  The user terminal 3 receives the selection input for the subscription determination from the contractor, and transmits the subscription determination data to the pay-per-use car insurance processing server 5 (step S217). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S219). Further, the contract content check unit 53 identifies the category for determining the insurance premium as category D (step S220). And it transfers to the process of FIG.

  Next, the processing after it is determined in step S201 that it is not a separate relative and transitioned via the terminal P will be described using FIG. 26A.

  In the processing flow described above, when the person is not a separate relative, the person is automatically identified as a separate person. Then, the contract content check unit 53 applied for the current use from the limited special contract data included in the extracted contract data of the general automobile insurance and the attribute data (including the relationship data) of the contractor who applied for the current use. It is confirmed whether the contractor is a limited special contract target (step S221). For example, when there is no limited special agreement, other persons living separately are also insured.

  If the contractor who applied for this time is a target of the limited special agreement, the contract content check unit 53 generates the data of the confirmation page E from the extracted contract data of the general automobile insurance, and sends it to the user terminal 3. Transmit (step S223). The user terminal 3 receives the data of the confirmation page E from the pay-per-use car insurance processing server 5 and displays it on the display device (step S225). For example, a screen as shown in FIG. 26B is displayed. In the example of FIG. 26B, although it is an object of compensation for another person's general automobile insurance, it is clearly shown on the condition that the insured's consent is necessary. However, since it will cause trouble to others in the event of an accident, a simple warning is given so that the application procedure can be advanced. The contractor determines whether or not to proceed with the pay-as-you-go car insurance procedure as it is, and inputs it.

  The user terminal 3 receives the selection input for the subscription determination from the contractor, and transmits the subscription determination data to the pay-per-use car insurance processing server 5 (step S227). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S229). Further, the contract content check unit 53 identifies the category for determining the insurance premium as the category G (step S230). And it transfers to the process of FIG.

  On the other hand, when it is not subject to a limited special contract, it is a typical example of subscribing to pay-per-use car insurance because it is not subject to a limited special contract for another person who is living separately. Accordingly, the contract content check unit 53 identifies the category for determining the insurance premium as category F (step S231), and returns to the original process via the terminal H.

  On the other hand, in step S171 of FIG. 18, it is determined that the person is a living person (a family (specifically, a child or other relative)) or a different person living together, and the process after the transition through the terminal N is shown in FIG. Will be described.

  Here, there is a possibility that the child is a cohabiting child or a relative or another person, but the relationship data received from the contractor indicates that the contractor who applied for this time is a “cohabit child” (ie, an unmarried child living together or It is determined whether or not it indicates a married child (step S241). When it does not correspond to “children living together”, the process proceeds to the process of FIG.

  On the other hand, in the case of “cohabitation child”, the contract content check unit 53 includes the limited special contract data included in the extracted general automobile insurance contract data and the attribute data of the contractor who applied for this time (relationship) (Including data), it is confirmed whether the contractor who applied for this time is a target of the limited special contract (step S243). For example, “children” are not eligible if the person / spouse is a special contract. When the contractor who applied for this time is a target of the limited special contract, the contract content check unit 53 generates the data of the confirmation page C from the extracted contract data of the general automobile insurance, and sends it to the user terminal 3. Transmit (step S245). The user terminal 3 receives the data of the confirmation page C from the pay-per-use car insurance server 5 and displays it on the display device (step S247). For example, a screen as shown in FIG. 23 is displayed. Since FIG. 23 has been described above, a description thereof will be omitted. Then, the contractor determines whether or not to proceed with the procedure of the pay-per-use car insurance as it is or cancels the input.

  The user terminal 3 receives the selection input for the subscription determination from the contractor, and transmits the subscription determination data to the pay-per-use car insurance processing server 5 (step S249). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S251). Further, the contract content check unit 53 identifies the category for calculating the insurance premium as category I (step S252). And it transfers to the process of FIG.

  On the other hand, if it is determined in step S243 that the contract is not covered by the limited special agreement, the contract content check unit 53 generates the data for the confirmation page D from the extracted general automobile insurance contract data, and the user terminal 3 (Step S253). The user terminal 3 receives the data of the confirmation page D from the pay-per-use car insurance processing server 5 and displays it on the display device (step S255). For example, a screen as shown in FIG. 24 is displayed. Since FIG. 24 has already been shown, a description thereof will be omitted. Then, the contractor determines whether or not to proceed with the procedure of the pay-per-use car insurance as it is or cancels the input.

  The user terminal 3 receives a selection input for subscription determination from the contractor, and transmits subscription determination data to the metered-rate car insurance processing server 5 (step S257). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S259). Further, the contract content check unit 53 identifies the category for determining the insurance premium as the category H (step S260). And it transfers to the process of FIG.

  Next, with reference to FIG. 28, a process after it is determined in step S241 that the child is not a cohabiting child and a transition is made via the terminal Q will be described.

  The contract content check unit 53 is the extracted relative data of the general automobile insurance and the attribute data (including the relationship data) of the contractor who applied for the current use, and the relative of the general automobile insurance contractor who is extracted It is determined whether or not there is (step S261). If it is not a relative living together, the process proceeds to the process of FIG.

  On the other hand, if it is a relative living together, the contract content check unit 53 includes the limited special contract data included in the extracted contract data of the general automobile insurance and the attribute data of the contractor who applied for this time (including the relationship data). ), It is confirmed whether or not the contractor who applied for this time is the target of the limited special contract (step S263). For example, in the case where the limitation of the principal / spouse is set in the limited special agreement, the relative living together is excluded from the limited special agreement.

  When the contractor who applied for this time is a target of the limited special contract, the contract content check unit 53 generates the data of the confirmation page C from the extracted contract data of the general automobile insurance, and sends it to the user terminal 3. Transmit (step S265). The user terminal 3 receives the data of the confirmation page C from the pay-per-use car insurance processing server 5 and displays it on the display device (step S267). For example, a screen as shown in FIG. 23 is displayed. Since FIG. 23 has been described above, description thereof is omitted here. Then, the contractor determines whether or not to proceed with the procedure of the pay-per-use car insurance as it is or cancels the input.

  The user terminal 3 receives the selection input for the subscription determination from the contractor, and transmits the subscription determination data to the pay-per-use car insurance processing server 5 (step S269). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S271). Further, the contract content check unit 53 identifies the category for determining the insurance premium as the category K (step S272). And it transfers to the process of FIG.

  On the other hand, if it is determined in step S263 that the contract is not covered by the limited special agreement, the contract content check unit 53 generates the data of the confirmation page D from the extracted general automobile insurance contract data, and the user terminal 3 (Step S273). The user terminal 3 receives the data of the confirmation page D from the pay-per-use car insurance processing server 5 and displays it on the display device (step S275). For example, a screen as shown in FIG. 24 is displayed. Since FIG. 24 has been described above, description thereof is omitted here. Then, the contractor determines whether or not to proceed with the procedure of the pay-per-use car insurance as it is or cancels the input.

  The user terminal 3 receives a selection input for subscription determination from the contractor, and transmits subscription determination data to the metered-rate car insurance processing server 5 (step S277). The contract content check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S279). Further, the contract content check unit 53 identifies the category for determining the insurance premium as the category J (step S280). And it transfers to the process of FIG.

  Next, with reference to FIG. 29A, a process after it is determined in step S261 that it is not a separate relative and a transition is made through the terminal R will be described.

  In the processing flow described above, if it is not a relative living together, it is automatically specified that it is another person living together. Then, the contract content check unit 53 applied for the current use from the limited special contract data included in the extracted contract data of the general automobile insurance and the attribute data (including the relationship data) of the contractor who applied for the current use. It is confirmed whether the contractor is a limited special contract target (step S281). For example, if there is no limited special agreement, other people living together are also insured.

  If the contractor who applied for this time is a target of the limited special agreement, the contract content check unit 53 generates the data of the confirmation page E from the extracted contract data of the general automobile insurance, and sends it to the user terminal 3. Transmit (step S283). The user terminal 3 receives the data of the confirmation page E from the pay-per-use car insurance server 5 and displays it on the display device (step S285). For example, a screen as shown in FIG. 26B is displayed. Since FIG. 26B has already been described, description thereof is omitted here. The contractor determines whether or not to proceed with the pay-as-you-go car insurance procedure as it is, and inputs it.

  The user terminal 3 receives the selection input for the subscription determination from the contractor, and transmits the subscription determination data to the pay-per-use car insurance processing server 5 (step S287). The contract details check unit 53 of the pay-per-use car insurance processing server 5 receives the subscription determination data (step S289). Further, the contract content check unit 53 identifies the category for determining the insurance premium as the category M (step S291). And it transfers to the process of FIG.

  On the other hand, when it is not subject to the limited special agreement, it is not subject to the limited special agreement for others living together. Accordingly, the contract content check unit 53 identifies the category for determining the insurance premium as the category L (step S293), and returns to the original process via the terminal H.

  As described above, the duplication / attribute check process is performed, and when joining, one of the categories A to M for insurance premium calculation is specified. The data of this category is output from the contract content check unit 53 to the use application processing unit 52.

  FIG. 29B shows a summary of the attribute check processing described above. According to this, it can be understood which case cannot be subscribed, which case can be subscribed to, and which category.

  Note that categories B, D, H, J, C, E, I, and K cannot be compensated by driver insurance.

  Returning to the description of the processing of FIG. 10, the use application processing unit 52 determines whether or not the usage / payment-based car insurance has been obtained in the duplication / attribute check processing in step S79 (step S81). When joining, a category is specified. If the user does not join, the category is not specified, so this data can be used for determination. If it is decided not to join, the processing shifts to the processing in FIG.

  On the other hand, when it comes to joining, the use application processing unit 52 transmits the data of the compensation content input page to the user terminal 3 (step S83). The user terminal 3 receives the compensation content input page data from the pay-per-use car insurance server 5 and displays it on the display device (step S85). For example, a table as shown in FIG. 30 is presented. The example of FIG. 30 includes a column for specifying compensation for the present metered-charge car insurance and a column for specifying compensation for domestic travel accident insurance. For pay-as-you-go car insurance, compensation can be set individually for compensation (personal / objective), injury, and some other compensation. In this way, the compensation contents can be designated in a simple form. The contractor operates the user terminal 3 to set necessity for each item.

  The user terminal 3 receives the compensation content input from the contractor, and transmits compensation content data to the metered-rate car insurance processing server 5 (step S87). The usage application processing unit 52 of the pay-per-use car insurance processing server 5 receives the compensation content data from the user terminal 3 and stores it in a storage device such as a main memory (step S89).

  In addition, it is confirmed whether the vehicle insurance is set by checking the compensation content data. If the vehicle insurance is required, the use application processing unit 52 transmits the photography guide page data to the user terminal 3. (Step S91). The user terminal 3 receives the photography guide page data and displays it on the display device (step S93). Encourage photographers to take pictures from three predetermined directions. Then, the contractor instructs to take a picture and transmit the image data of the vehicle.

  In response to an instruction from the contractor, the user terminal 3 transmits image data of the photographed photograph to the pay-per-use car insurance processing server 5 (step S95). The usage application processing unit 52 of the pay-per-use car insurance processing server 5 receives the image data from the user terminal 3 (step S97) and stores it in a storage device such as a main memory (step S97). The processing shifts to the processing in FIG. 31 via terminals F and G.

  Next, the use application processing unit 52 causes the insurance fee calculation unit 54 to calculate insurance premiums using data stored in the various data storage units 60 (step S301). As shown schematically in FIG. 32, the premium calculation for the pay-per-use car insurance is calculated based on a unique parameter.

  In this embodiment, parameter values are determined for each of (A) presence / absence of registration of main contract, (B) category, (C) number of years of license holding, (D) number of past accidents, compensation details, etc. The base premium is determined by a combination of the parameter values. The base insurance premium may be determined by, for example, reading a value registered in advance in a corresponding element of the multidimensional matrix for a parameter from a combination of parameter values, or a function using these parameters as an argument in advance. May be determined and calculated by the function. This function may be, for example, a weighted sum of parameter values.

  As described above, the compensation period can be specified in terms of time, and the compensation period may be specified between points. If both are specified, the one that is advantageous to the contractor is adopted. Therefore, a multidimensional matrix or function for calculating the premium per unit time (for example, one day) and a multidimensional matrix or function for calculating the premium per unit distance are prepared. The one that is advantageous (ie cheaper) is adopted.

  When a compensation period is specified between points, a rough route search is performed, and for example, a route passing through a high accident location registered in the general accident DB 59 is increased when it is unavoidable. In some cases. In addition, there are cases where premiums or discounts are given from various factors.

  Therefore, from the parameter values of (A) to (D) and other parameter values specified from the compensation content, etc., to the base premium specified or calculated by a function using the multidimensional matrix or those parameters as arguments, The insurance premium is calculated by multiplying the period (time or distance) and the premium or discount rate.

  Further, regarding (A) presence / absence of registration of the main contract in this embodiment, the parameters are determined so that the insurance premium is lower when the main contract is registered than when the main contract is not registered. The As for category (B), as shown in FIG. 33, the magnitude relationship of parameters is defined for each category. In the present embodiment, the premium is high when the parameter value is large, and the premium is low when the parameter is small. In FIG. 33, the magnitude of the parameter is determined with a priority such as relationship> separate living / separate living> target general automobile insurance or not. And the size of the parameter is specified in the order of child> relative> others, the size of the parameter is specified in the same living> separation, and the size of the parameter is specified in the order of applicable general automobile insurance> non-target ing. FIG. 33 shows a summary of such relationships.

  Furthermore, (C) As for the number of years of license holding, the license acquisition year is specified by the upper 3 digits and 4 digits of the license number. Determine the parameters from such a table. When the premium increases as the parameter increases, the relationship of a> b> c> d is satisfied in the table of FIG.

  Further, (D) the number of past accidents is determined from a table such as that shown in FIG. 35, for example, after the number of accidents is identified by searching the pay-by-charge insurance accident DB 57 with the contract number of the pay-per-use car insurance. To do. When the premium increases as the parameter increases, the relationship of g <h <i <j is satisfied in the table of FIG.

  The insurance fee calculation unit 54 calculates the insurance fee in this way and outputs the calculation result to the use application processing unit 52. The use application processing unit 52 receives the calculated premium value and stores it in a storage device such as a main memory. For various data for insurance premium calculation such as a multidimensional matrix, data stored in various data storage units 60 is read and used.

  The use application processing unit 52 generates payment method selection page data from the contract data stored in the pay-as-you-go system insurance contract DB 56, and transmits it to the user terminal 3 (step S303). The user terminal 3 receives the payment method selection page data from the pay-per-use car insurance processing server 5 and displays it on the display device (step S305). For example, a screen as shown in FIG. 36 is displayed. In the example of FIG. 36, a pre-registration method, a credit card, electronic money, a method of adding a mobile phone fee, etc. are selected. The user selects a payment method and inputs data as necessary.

  The user terminal 3 receives a selection input about the payment method from the contractor, and transmits the payment method data to the pay-per-use car insurance processing server 5 (step S307). The usage application processing unit 52 of the pay-per-use car insurance processing server 5 receives the payment method data from the user terminal and stores it in a storage device such as a main memory (step S309). Note that payment processing may be performed based on payment method data and insurance premium data, but the payment processing is already known and will not be described further.

  At this point, the use application processing unit 52 registers the use registration data, which has been acquired so far, in the pay-as-you-go insurance policy DB 56 as a record (step S311). The usage registration data registered in the pay-as-you-go system insurance contract DB 56 is, for example, data as shown in FIG. In the example of FIG. 37, the detail number (contract number + branch number in this case) issued for each use application, the registration number and model number of the car to be driven this time, the compensation period data (start date / time, period ), Starting and ending points for specifying the compensation period between points, compensation details (indemnity insurance, accident insurance, vehicle insurance, etc.), category, insurance premium, and vehicle insurance In this case, a pointer to an image file necessary for the case is registered. Data such as relationships may be registered. The vehicle image data may be stored in another data storage unit without being registered in the pay-as-you-go system insurance contract DB 56.

  Then, the usage application processing unit 52 generates a usage registration confirmation notification including the current usage registration data, and transmits it to the user terminal 3 (step S313). The user terminal 3 receives the usage registration confirmation notification from the pay-per-use car insurance processing server 5 and displays it on the display device (step S315).

  Further, the usage application processing unit 52 transmits a confirmation email including the current usage registration data to the designated email address (step S317).

  The applicant saves such data and collates it with actual payments or refers to it when an accident occurs later.

  By performing the above process, it is appropriate to use personal pay-as-you-go car insurance from the relationship between the contractor who applied for this time and the general car insurance insured for the car being driven. It is possible to appropriately confirm whether or not this is the case. That is, even a contractor who does not have knowledge of general car insurance for a driving car can be insured with pay-per-use car insurance in an appropriate case.

  Note that the association between the pay-per-use car insurance and the main contract is canceled when the main contract expires. For example, since the presence or absence of the main contract is one parameter when calculating the insurance premium, by searching the general insurance contract DB 58 with the registered main contract security number and confirming whether it is actually a valid contract, It is determined whether the association is valid. In the case of an invalid main contract registration, the association is deleted by deleting the main contract security number when it is found. In addition, when a new main contract is made, the contractor shall perform a separate procedure and register the main contract security number. Further, for example, when there is no registration for usage-based car insurance for 13 months or more, the main contract security number may be deleted.

  In addition to the basic functions as described above, the following incidental functions may be provided. For example, when a contractor using a mobile phone with a GPS function specifies a compensation period between points in addition to a temporal compensation period, for example, a compensation confirmation application program (pre-registration) And may be included in the mobile application program for application for use), the current location is regularly monitored, and the end point is not reached before the predetermined time before the time compensation period expires When this is detected, an alarm for confirming the extension of the period may be issued. In some cases, a confirmation mail is transmitted in cooperation with the pay-per-use car insurance processing server 5.

  Furthermore, when using a mobile phone with a GPS function, it may be possible to set the current position registration and start the insurance period.

  Although accident handling is almost the same as usual, the accident record is registered in the pay-as-you-go system insurance accident DB 57. That is, it is managed separately from the general accident DB 59 that stores accident data on general automobile insurance. Further, in the case of a contractor having a mobile phone with a GPS function, location registration is also performed for the accident location. If a compensation period is set between points later, the start point and the accident location are within 1 km, for example, or if a compensation period is set in time, an accident will occur within 30 minutes from the start date of use. If it has occurred, the contract number and other data are separately registered in the pay-as-you-go system insurance accident DB 57 as there is a suspicion of fraud insurance claims. Further, an underwriting impossible flag in the pay-as-you-go insurance contract DB 56 shown in FIG. 5 is set.

  Furthermore, when a subscriber of a pay-per-use car insurance purchases a car, he / she joins general car insurance. In this case, the driving performance may be taken over. For example, the contract number of the pay-per-use car insurance is reported, and the contract handover processing unit 55 searches the pay-per-use insurance contract DB 56 with the contract number and extracts all use registration data. Among them, if there is a case in which the usage interval is, for example, 13 months or more, the results are accumulated with the data after the usage registration data. If the number of days is equal to or greater than the predetermined number of days, for example, after raising the non-fleet grade by one grade, a contract for general automobile insurance is started. Depending on the case, you may make it start the contract of general car insurance after raising 2 grades or more. Furthermore, although the standard for raising one grade has not been reached, a predetermined discount may be performed when the number of days used is equal to or greater than the second predetermined number of days. Furthermore, instead of raising the grade, only discounts may be made from the beginning. When a compensation period is designated between points, for example, if a distance is accumulated and the distance is equal to or longer than a predetermined distance, a preferential treatment of a grade and a discount rate are determined. Note that the above is based on the assumption that there is no accident, and it is confirmed that accident data is not extracted by searching the pay-as-you-go system insurance accident DB 57 by contract number. The contract handover processing unit 55 determines whether to determine the grade at the time of takeover, the determination of the discount rate, and whether such a privilege is given, and outputs the result to the request source.

  Although the embodiment of the present invention has been described above, the present invention is not limited to this. For example, the block diagram shown in FIG. 1 is an example, and may not necessarily match the actual program module configuration. Further, when the processing result of the processing flow does not change, it is possible to change the processing order or to execute in parallel.

  The payment may be a deposit. Other settlement methods may be adopted.

  The user terminal 3 and the pay-per-use car insurance processing server 5 are computer devices. As shown in FIG. 38, the computer device includes a memory 2501 (storage unit), a CPU 2503 (processing unit), and a hard disk drive ( HDD) 2505, display control unit 2507 connected to display device 2509, drive device 2513 for removable disk 2511, input device 2515, and communication control unit 2517 for connecting to the network are connected by bus 2519. Application programs including an operating system (OS) and a Web browser are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. If necessary, the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 to perform necessary operations. Further, data in the middle of processing is stored in the memory 2501 and stored in the HDD 2505 if necessary. Such a computer realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above with the OS and necessary application programs.

3 User terminal 5 Pay-per-use car insurance processing server 51 Pre-registration processing section 52 Usage application processing section 53 Contract content check section 54 Insurance fee calculation section 55 Contract takeover processing section 56 Pay-per-use insurance contract DB 57 Pay-per-use insurance accident DB
58 General insurance contract DB 59 General accident DB
60 Various data storage

Claims (1)

From the first data storage unit that stores the data of the insured person and the data of the number of days of use for the pay-as-you-go system car insurance that pays the usage application and the insurance premium every time it is used without limiting the target car, Extracting data on the number of days of use of a customer who wishes to take out general automobile insurance in which the target vehicle is specified;
Confirming the presence or absence of an accident related to the customer from a second data storage unit storing accident data for the pay-per-use car insurance;
When it is confirmed that there is no accident related to the customer, a step of determining a discount rate or a non-fleet grade increase according to the total number of use days specified from the extracted use day data;
A pay-as-you-go car insurance information processing method executed by a computer.

Images