JP2008269230A - Insurance system and portable communication terminal used for it - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow a user to easily receive an insurance service via a portable communication terminal having a function previously installed for an insurance when purchased. <P>SOLUTION: When a customer 30 performing a cellular phone purchase procedure and an insurance contract application procedure carries out the purchase procedure for a cellular phone combined with an insurance contract at a counter of a cellular phone company 6, predetermined information such as personal information of the customer input during the procedure is registered in a customer database of the cellular phone company 6, and at the same time, transmitted to an insurance company 11 to be registered in a customer database 15 of the insurance company 11. The cellular phone to be sold to an insurance contract user is a dedicated one having a support function (a set mail automatic transmission function and the like: S13) previously installed for the insurance contact user. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention provides, for example, an insurance system that manages a insurance contract using a computer when a user makes a contract for various types of insurance such as traffic accident insurance, liability insurance, or mobile phone damage insurance, and the insurance system. The present invention relates to a mobile communication terminal used.

  In this type of insurance system and mobile communication terminal, what is generally known, for example, an insurance control signal for an insurance contract is transmitted to the insurance contract computer from a mobile communication terminal such as a mobile phone possessed by the user. In some cases, in response to the transmitted insurance control signal, the insurance contract computer controls the establishment or termination of the insurance contract or the period conditions related to the insurance contract (Patent Document 1).

The device described in Patent Document 1 transmits an information signal related to the position or moving distance of a mobile communication terminal from the mobile communication terminal to the insurance contract computer, and the insurance contract computer uses the transmitted information related to the position or moving distance. It was configured to control monetary conditions related to insurance contracts in response to signals.
JP 2003-50914 A

  However, the device described in Patent Document 1 is to effectively use a mobile communication terminal afterwards after purchasing the mobile communication terminal for an insurance contract. As a result, the user performs the purchase procedure at the time of purchasing the mobile communication terminal, and then performs the application procedure at the time of applying for an insurance contract.

  Moreover, since the mobile communication terminal used for the insurance contract is not customized for the insurance contract, there is no function customized for the insurance contract at the time of purchase. Had the inconvenience of being difficult to use in enjoying insurance services.

  The present invention has been conceived in view of such circumstances, and its purpose is to allow a user to easily receive an insurance service using a mobile communication terminal in which a function already prepared for insurance has been incorporated from the time of purchase. Is to be able to.

Specific examples of means for solving the problems and their effects

  Next, specific examples of means for solving the problems are shown in parentheses and the effects are described.

(1) An insurance system for managing a user's insurance contract using a computer (for example, the customer management server 13, the Web server 12, the insurance processing server 10 in FIG. 1),
When a user applies for an insurance contract, the user is registered as an insurance contract user (for example, S70 and S71 in FIG. 8B) to provide an insurance service. 1 customer management server 13, customer database 15, etc.)
When a user purchases a mobile communication terminal, when the user desires the insurance contract and performs the insurance contract application procedure and the mobile communication terminal purchase procedure, the mobile communication terminal ( For example, including the mobile phone 1) of FIG. 1 and FIG.
The mobile communication terminal supports an insurance contract user who applied for the insurance contract (for example, S13 in FIG. 5, a memory 23 in which an insurance contact address is stored in advance, an institution (police) that reports when an accident occurs) A function for automatically transmitting an accident occurrence notification to the insurance company 11 after a telephone contact to a insurance station, etc.) is a mobile communication terminal dedicated for insurance contract users.

  According to such a configuration, the support function for the insurance contract user is incorporated in the mobile communication terminal provided to the insurance contract user who has performed the insurance contract application procedure and the mobile communication terminal purchase procedure. In addition, the user can receive support for insurance using the mobile communication terminal from the beginning of purchase, and the convenience of the user is improved.

(2) A user's insurance contract (for example, a contract for traffic accident insurance, liability insurance, mobile phone damage insurance, etc.) and a computer (for example, customer management server 13, web server 12, insurance processing server 10 in FIG. 1) A mobile communication terminal (for example, provided to the user when the user desires the insurance contract and performs the application procedure of the insurance contract and the purchase procedure of the mobile communication terminal) 1 and 2 of the mobile phone 1),
Support functions for insurance contract users who have applied for the insurance contract (for example, S13 in FIG. 5, memory 23 in which the insurance correspondence window address is stored in advance, an organization (the police, fire department, etc.) that reports when an accident occurs) A function for automatically sending an accident notice to an insurance company after telephone contact is incorporated in advance.

  According to such a configuration, the support function for the insurance contract user is incorporated in the mobile communication terminal provided to the insurance contract user who has performed the insurance contract application procedure and the mobile communication terminal purchase procedure. In addition, the user can receive support for insurance using the mobile communication terminal from the beginning of purchase, and the convenience of the user is improved.

  (3) The mobile communication terminal, as the support function, automatically transmits an e-mail address to the insurance business server when an e-mail address is set in the mobile communication terminal (for example, FIG. 5). S13).

  According to such a configuration, the registration procedure of the mail address to the insurance business server is automatically performed, and the convenience for the user is improved.

  Next, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a configuration diagram showing an overall outline of an insurance system according to the present invention. A gateway 7 of the mobile phone company 6, a gateway 12 of the insurance company 11, and a gateway 4 of the mobile phone network 2 are connected through the Internet 5 as an example of a communication network, and are configured to transmit and receive information to and from each other. Yes. In addition, a base station 3 is connected to the mobile phone network 2, wireless communication is performed between the mobile phone 1 as an example of a mobile communication terminal and the base station 3, and the data of the wireless communication is transferred to the mobile phone network 2. The data is transmitted to the mobile phone company 6 or the insurance company 11 via the gateway 4 and the Internet 5. Further, data from the mobile phone company 6 or the insurance company 11 is transmitted to the mobile phone 1 via the Internet 5, the gateway 4, the mobile phone network 2, and the base station 3.

  In addition to the gateway 7 described above, the mobile phone company 6 stores an insurance processing server 8 for processing insurance business using the mobile phone 1 and customer data of contract users who have subscribed to the insurance contract. A customer database 10 and other servers 9 are provided.

  In addition to the gateway 12 described above, the insurance company 11 includes a Web server 14, a Web database 16, a customer management server 13 for managing customers of contract users who have subscribed to an insurance contract using the mobile phone 1, and its contract users A customer database 15 storing customer data is provided.

  In the customer database 15, the terminal ID (manufactured by the mobile phone) of the mobile phone 1 possessed by the contract user who has subscribed to the insurance contract using the mobile phone 1, the e-mail address of the mobile phone, the name and address of the contract user A telephone number, insurance information for identifying the type of insurance that has been subscribed, accident claim data, and the like are stored. The mobile phone 1 is a mobile phone dedicated to insurance contract users that is sold only to users who have applied for insurance contracts and purchased mobile phones, improving user convenience when operating insurance operations. The support function is built in beforehand. Since no e-mail address has been set yet at the time of sale of the mobile phone 1, no data is stored in the e-mail address storage area of the customer database 15. In addition, accident claim data is data related to claims for insurance claims in the event of accidents covered by insurance (for example, traffic accidents, liability accidents, mobile phone damage accidents, etc.). “None” data indicating that it has not been recorded is stored. If an accident occurred and there was a claim for insurance payment, the contents of the accident, the contents of the claim, and data on the situation of the accident (for example, photos) Data) and other accident details data are stored. The insurance information is information that identifies the type of insurance that the contract user has subscribed. For example, in the case of a user with the terminal ID “814311”, the user has subscribed to traffic accident insurance and the terminal ID is “710436”. In the case of a user, both accident liability insurance and traffic accident insurance are enrolled. In the case of “traffic accident insurance”, when a mobile phone possessed by the contract user is damaged due to a traffic accident, an insurance payment for damage to the mobile phone can be received. Apart from this traffic accident insurance, there is a mobile phone damage insurance as compensation when the mobile phone is damaged due to a cause other than a traffic accident.

  The web database 16 of the insurance company 11 stores data of website pages prepared for contract users, and is configured so that the cellular phone 1 can be used to access the website pages. . Specifically, the page of this Web site has an insurance correspondence window, and the accident correspondence window or the consultation window can be accessed using the insurance correspondence window as an entrance. The accident claim counter page further includes a traffic accident claim counter page, a liability accident claim counter page, and a mobile phone damage accident claim counter page. When the contract user wants to consult with the insurance company 11 about insurance, he / she operates the mobile phone 1 to access the page of the website of the insurance company 11. Then, the insurance correspondence window is displayed first, and by selecting (clicking) the consultation window from that, the consultation window page is displayed on the mobile phone 1, and the consultation items are entered in the designated area of the consultation window. By transmitting, the insurance company 11 responds to the consultation item and returns it to the mobile phone 1 (reply by e-mail, etc.).

  When a contract user has an accident covered by his / her insurance, he / she operates the mobile phone 1 to access the insurance correspondence window, and selects the accident claim window page to the accident claim window page. to access. On the accident claim counter page, depending on the type of accident that occurred, access either the traffic accident claim counter page, the liability accident claim counter page, or the mobile phone damage accident claim counter page. Then, the accessed accident claim counter page is displayed on the mobile phone 1, and a predetermined item is input to a predetermined location of the accident claim counter page and transmitted to the insurance company 11, and the digital camera 26 of the mobile phone 1 (FIG. 2). The photograph of the accident site is taken according to (see), and the photograph data is transmitted to the insurance company 11.

  The data input to the accident claim window and the photo data of the accident site are stored in the corresponding mobile ID area in the accident claim data of the customer database 15.

  The customer database 10 of the mobile phone company 6 stores various data other than the “accident claim data” among the stored data of the customer database 15 of the insurance company 11.

  FIG. 2 is a functional block diagram of the mobile phone 1. The mobile phone 1 is provided with a control unit 22 composed of a CPU (Central Processing Unit) as a control center, and a memory 23 in which a program for controlling the control unit and various data are stored. The control unit 22 reads data and programs stored in the memory 23, executes a predetermined control operation, and stores the received data in the memory 23 as necessary.

  A wireless unit 21 is connected to the control unit 22, and an antenna 20 is connected to the wireless unit 21. The control unit 22 is connected to an operation unit 24 operated by a user, a reception unit 25, a digital camera 26, a display unit 27 including a liquid crystal, a transmission unit 28, and a surroundr 29. When the user operates the operation unit 24, the operation signal is input to the control unit 22, and the voice uttered by the user is input from the receiver unit 25 to the control unit 22, and when the user takes a picture with the digital camera 26, the photo data Is input to the control unit 22. Further, when the user accesses the Web page by operating the operation unit 24, the Web page is displayed on the display unit 27. When a call is received from another person, a call sound is generated by the surrounder 29, and the operation unit 24 is operated to make a call state. Then, the radio wave 21 from the other party is received by the antenna 20 and the control is performed. The other party's voice is emitted from the transmitter 28 via the unit 22.

  The memory 23 stores a control program and data necessary for a general mobile phone. As described above, the mobile phone 1 is a customized mobile phone dedicated to an insurance contract user who has subscribed to an insurance contract. There are programs and data stored in advance in the memory 23 for realizing functions convenient for the user in carrying out the insurance business. For example, programs such as S13 in FIG. 5 and S23 in FIG. 6 to be described later are stored in the memory 23 in advance.

  FIG. 3 is an explanatory diagram for explaining the flow of the insurance system that is combined with the sale of the mobile phone in order to use the mobile phone.

  First, in (1), an approximate insurance premium (annual insurance premium) is paid from the mobile phone company 6 to the insurance company 11. As described above, there are three types of insurance, traffic accident insurance, liability insurance, and mobile phone damage insurance, each with an annual contract of 2000 yen for one contract. The mobile phone company 6 predicts the number of contracts in one year and pays an insurance premium to the insurance company 11 in advance by multiplying the predicted expected number of contracts by 2000 yen.

  Next, in (2), the customer (contractor) 30 performs a mobile phone purchase procedure and an insurance contract application procedure at the mobile phone company 6 window. Specifically, the prescribed matters (personal information) such as the policyholder and the insured person are entered on one mobile phone application form (several photo forms), and the insurance agreement is entered. Thus, the mobile phone purchase procedure and the insurance contract application procedure are completed, and the mobile phone 1 is sold to the customer (contractor) 30. The terminal ID of the sold mobile phone 1 and the contents entered by the customer (contractor) 30 are input to the computer as electronic data by an employee of the mobile phone company 6, and the input data is a customer database of the mobile phone company 6. 10 is registered. At the same time, the electronic data is transmitted to the insurance company 11 in (3) and registered in the customer database 15 of the insurance company 11.

  Next, the customer (contractor) 30 sets an e-mail address for the newly purchased mobile phone 1. Then, the data of the set mail address is automatically transmitted to the insurance company 11 as well as the mobile phone company 6 in (4). When the set mail address is transmitted, the telephone number and the terminal ID of the mobile phone 1 are automatically transmitted together as will be described later. As a result, the mobile phone company 6 and the insurance company 11 that have received the transmitted data search the customer databases 10 and 15 based on the received terminal ID, and locate the mail address in the corresponding terminal ID area. Register the received email address.

  Next, in (5), the insurance company 11 directly emails the insurance correspondence window address (URL) at the time of the occurrence of an insurance accident to the mobile phone 1 of the customer (contractor) 30. The customer (contractor) 30 stores the received insurance correspondence window address in the memory (favorite) of the mobile phone 1.

  Next, when an insurance accident occurs, the customer (contractor) 30 operates the mobile phone 1 to access the insurance correspondence window address of the insurance company 11 in (6) and is displayed on the Web page. Enter the required information in the specified format and send it. For example, when a traffic accident occurs, in (6) -A, input information for a predetermined format and image data taken by the digital camera 26 at the traffic accident site are transmitted to the insurance company 11. Further, when a liability insurance accident occurs, in (6) -B, the input information to the predetermined format and the image data of the damaged digital camera 26 are sent to the insurance company 11 by e-mail.

  In the case of a liability liability accident, the insurance company 11 confirms the victim (partner liable for property damage) by telephone and uses the confirmation content for insurance examination.

  Next, when paying the insurance money as a result of the document examination, the insurance money is transferred from the insurance company 11 to the bank account of the customer (contractor) 30 in (8).

  Next, in (9), the settlement of the premium payment at the end of the year is performed between the mobile phone company 6 and the insurance company 11. This is because in (1) above, the mobile phone company 6 paid the insurance premium to the insurance company 11 by multiplying the estimated number of annual contracts by 2000 yen, and one year after the payment. Since the actual number of applications per year is fixed, settlement is made by reconciling the total contract amount corresponding to the actual number of applications and the estimated premium paid in advance.

  FIG. 4 is a flowchart of the program stored in the memory 23 of the mobile phone 1. First, in step (hereinafter simply referred to as “S”) 1, a mail address setting process is executed when the mail address is set for the mobile phone 1, and a web browser process is performed in S 2 to change the mail address. The mail address change process at the time of setting is performed, and other processes are executed in S4, and the process returns to S1.

  FIG. 5 is a flowchart showing the specific control contents of the mail address setting process shown in S1 of FIG. In S10, it is determined whether or not an operation for setting its own mail address has been performed. If it has not been performed, this mail address setting process ends (returns), but the operation for setting its own mail address is performed. If YES in step S11, the flow advances to step S11 to perform processing for storing the set mail address in the memory 23.

  Next, the process proceeds to S12, and a process for transmitting the mail address, the telephone number, and the terminal ID together with the registration request signal to the mobile phone company 6 is performed. In response to this, the cellular phone company 6 performs a process of registering the mail address transmitted to the corresponding mail address area of the customer database 10.

  Next, in S13, a process for transmitting the e-mail address, the telephone number, and the terminal ID together with the registration request signal to the insurance company 11 is performed. Upon receiving this, the insurance company 11 performs a process of registering the received mail address in the corresponding mail address area of the customer database 15.

  Next, the process proceeds to S14, where it is determined whether or not the address of the insurance service counter has been received. If not received, the process proceeds to S15, where it is determined whether or not an inappropriate authentication result has been received. If not, the process returns to S14.

  In the customer management server 13 of the insurance company 11 that has received the registration request signal, e-mail address, telephone number, and terminal ID data, it is determined whether or not the received terminal ID is a terminal ID registered in the customer database 15. If the terminal ID is checked and registered, the address (URL) of the insurance correspondence window in the Web database 16 is returned to the mobile phone 1. On the other hand, if the received terminal ID is not registered in the customer database 15, it means that an e-mail address has been transmitted from a user who has not performed the insurance contract procedure. Send back. If the address of the insurance service counter is returned from the insurance company 11, a determination of YES is made in S14, the process proceeds to S16, and a process of registering the address of the insurance service window in the memory 23 is performed. On the other hand, if the above-described improper authentication result is returned from the insurance company 11, a determination of YES is made in S15 and the process proceeds to S17, where the improper display is performed by the display unit 27 of the mobile phone 1, and this mail The address setting process ends.

  FIG. 6 is a flowchart showing the specific control contents of the mail address change process shown in S3 of FIG. In S20, it is determined whether or not a mail address changing operation has been performed. If not, the mail address changing process is terminated. When the user operates the operation unit 24 of the mobile phone 1 to change the already set mail address to another mail address, a YES determination is made at S20 and the process proceeds to S21 to change his / her mail address. Processing to update the new mail address is performed. Next, in S22, a process for transmitting the new mail address, the telephone number, and the terminal ID together with the mail address change signal to the mobile phone company 6 is performed. Next, in S23, a process for transmitting the new mail address, the telephone number, and the terminal ID together with the mail address change signal to the insurance company 11 is performed.

  In response to this, the mobile phone company 6 and the insurance company 11 perform a process of updating the mail address stored in the corresponding mail address area of the customer databases 10 and 15 to the new mail address.

  FIG. 7 is a flowchart showing specific control contents of the Web browser process shown in S2 of FIG. First, in S25, it is determined whether or not there is an access to the home page. If there is no access, the Web browser process is terminated. If the user operates the operation unit 24 of the mobile phone 1 to access any homepage on the Web, a determination of YES is made in S25, and the process proceeds to S26 to access the insurance support window. It is determined whether or not. If the access is not to the insurance support window, other web browser processing is executed in S56, and the web browser processing ends. On the other hand, when the user accesses the URL of the insurance service counter page of the insurance company 11, a determination of YES is made in S26 and the process proceeds to S27, where the terminal ID is transmitted from the mobile phone 1 to the insurance company 11. As will be described later, the insurance company 11 searches the customer database 15 based on the received terminal ID, determines whether or not the corresponding terminal ID is registered, and if it is registered, the authentication result is appropriate. If it is not registered, a reply that the authentication result is inappropriate is returned. After transmitting the terminal ID, the cellular phone 1 determines whether or not an authentication result has been returned in S27 and waits until it is received. Then, if there is a reply of the authentication result from the insurance company 11, the control proceeds to S29, and it is determined whether or not the reply result is appropriate. If it is inappropriate, the process proceeds to S30, an inappropriate display is made by the display unit 27, and this Web browser process is terminated. On the other hand, if the returned authentication result is appropriate, the control advances to S31, and the insurance correspondence window page is displayed by the display unit 27.

  The user who has viewed the insurance correspondence window uses the operation unit 24 to access either the accident claim window or the consultation window, or even cancel. In the mobile phone 1, it is determined whether or not an access operation to the accident claim counter has been performed in S32. If no access operation has been performed yet, whether or not an access operation to the consultation counter has been performed in S33. If an access operation has not been performed yet, a determination is made in S34 as to whether or not a cancel operation has been performed. If a cancel operation has not yet been performed, the process returns to S33. If the user performs a cancel operation in the course of the loop of S32, S33, S34, and S32, a YES determination is made in S34, and the Web browser process ends. On the other hand, if the user performs an access operation to the consultation window, a determination of YES is made in S33 and the process proceeds to S54, a consultation window page is displayed on the display unit 27, and a consultation reception process is performed in S55, and this Web browser process. Ends. Further, when an access operation to the accident claim counter is performed, a determination of YES is made in S32 and the process proceeds to S35, and the page of the accident claim counter is displayed on the display unit 27.

  Next, the control unit 22 of the mobile phone 1 determines whether or not a traffic accident selection operation has been performed in S36, and if there is no traffic accident selection operation yet, the process proceeds to S37 to select a liability liability accident operation. If there is not yet, the process proceeds to S54a, and it is determined whether there has been an operation for selecting a mobile phone damage accident, and if not, the process proceeds to S38 to determine whether a cancel operation has been performed. If the determination is made and there is not yet, the process returns to S36.

  If the user performs a cancel operation in the course of the loop of S36, S37, S54, S38, and S36, a YES determination is made in S38, and the Web browser process ends. If the user performs a traffic accident selection operation, a determination of YES is made in S36 and the process proceeds to S39, and a traffic accident entry page (traffic accident claim counter page) is displayed on the display unit 27. On the other hand, if the user performs a liability accident selection operation, a determination of YES is made in S37, the process proceeds to S40, and a page for entering a liability liability accident (a liability accident claim counter page) is displayed on the display unit 27. Furthermore, if the user performs an operation for selecting a mobile phone damage accident, a determination of YES is made in S54, and the process proceeds to S200 in FIG. 11, where the mobile phone damage accident entry page (mobile phone damage accident claim window) is displayed on the display unit 27. Is displayed. In the case of this mobile phone damage accident, for example, when the call function is damaged and the access to the website and the communication function are not damaged, the above-described online control of S54a and S200 to S204 by the mobile phone 1 is possible. It becomes. If the access to the website or the communication function is damaged, online control is not possible, and the offline charging procedure using mail or the like, or the online charging procedure using other communication devices Will be performed.

  After the traffic accident entry page is displayed in S39, the process proceeds to S47, where it is determined whether or not the entry of predetermined items has been completed. If it has not been completed yet, the process proceeds to S48 and a cancel operation is performed. It is determined whether or not a cancel operation has been performed yet, the process returns to S47. The user looks at the traffic accident entry page displayed on the display unit 27 and operates the operation unit 24 to enter a predetermined item or perform a cancel operation. If a cancel operation has been performed, a YES determination is made in S48, and the Web browser process is terminated. On the other hand, when the completion operation is performed after the predetermined items are entered, a determination of YES is made in S47, and the process proceeds to S49, where the display unit 27 displays a message with a photograph of the accident site.

  Next, the process proceeds to S50, where it is determined whether or not a photograph of the accident site has been attached. If not, the process proceeds to S51, and it is determined whether a cancel operation has been performed. If not, the process returns to S50. If the user performs a cancel operation, a determination of YES is made in S51, and the Web browser process ends. On the other hand, if the user takes a photograph of the accident site with the digital camera 26 and attaches the captured image data, a determination of YES is made in S50 and the process proceeds to S52, and the entry item and the attached photo data are displayed on the Web server of the insurance company 11 Processing to transmit to 14 is performed.

  Next, the process proceeds to S53, where the current position is specified by the GPS function (positioning function) provided in the mobile phone 1, and the current position data is transmitted to the Web server 14 of the insurance company 11, and this process is performed. The web browser process ends.

  On the other hand, after the entry page at the time of liability accident at S40 is displayed, it is determined at S41 whether or not the entry of predetermined items has been completed. If it has not been completed yet, a cancel operation is performed at S42. If it has not been operated yet, the process returns to S41. If the user performs a cancel operation, a determination of YES is made in S42, and this Web browser process ends. On the other hand, if the user inputs a predetermined item and completes the operation by looking at the entry page at the time of the liability accident displayed on the display unit 27, a determination of YES is made in S41, the process proceeds to S43, and a photograph of the damaged object is attached. Message display is performed by the display unit 27.

  Next, the process proceeds to S44, where it is determined whether or not a damaged photograph has been attached. If not, the process proceeds to S45, and it is determined whether a cancel operation has been performed. If not, the process returns to S44. If the user performs a cancel operation, a determination of YES is made in S45, and the Web browser process ends. On the other hand, when the user takes a photograph of the damaged object with the digital camera 26 and attaches the captured image data, a determination of YES is made in S44, and the process proceeds to S46. Processing for transmitting to the Web server 14 is performed, and processing for specifying and transmitting the current position by the GPS function in S53 is performed.

  After displaying the entry page at the time of the mobile phone damage accident in S200 of FIG. 11 (b), it is determined whether or not the entry of the predetermined items is completed in S201. The process proceeds to S202, where it is determined whether or not a cancel operation has been performed. If not, the process returns to S201. If the user performs a cancel operation, a determination of YES is made in S202, and the Web browser process ends. On the other hand, if the user operates the operation unit 24 to enter a predetermined item and completes the operation, a determination of YES is made in S201 and the process proceeds to S203, and the entered entry data is transferred to the Web server 14 of the insurance company 11. Processing to send to is performed.

  Next, the process proceeds to S204, in which the current position is specified by the GPS function provided in the mobile phone 1 and the current position data is transmitted to the Web server 14 of the insurance company 11, and this Web browser process ends. To do.

8 and 9 are flowcharts showing the control operation of the customer management server 13.
First, referring to FIG. 8 (a), an application process performed at the time of applying for an insurance contract is executed at S60, an e-mail address receiving process is performed at S61, and an e-mail address change receiving process is performed at S62. In S63, it is determined whether or not an authentication request has been made. If not, the process proceeds to S65. If there is, an authentication process is performed in S64, and an accident claim registration process is performed in S65. In S66, the year-end settlement process is performed, and the process returns to S60.

  FIG. 8B is a flowchart showing the specific control contents of the application process shown in S60. In S70, it is determined whether or not application form data transmitted from the mobile phone company has been received when the insurance contract application procedure is performed. On the other hand, if the application form data is received, the process proceeds to S71, and based on the application form data, personal data other than the mail address (terminal ID, name, address, telephone number, insurance information) is stored in the customer database 15. ) Is registered.

  FIG. 8C is a flowchart showing the specific control contents of the mail address reception process shown in S61. In S75, it is determined whether or not a registration request signal has been received. If it has not been received, the mail address reception process ends. If a registration request signal is transmitted from the mobile phone 1 according to S13 in FIG. 5, a determination of YES is made in S75, and the process proceeds to S76 to perform an authentication process. The specific control contents of this authentication process are shown in the flowchart of FIG. The flowchart of FIG. 8D is also a flowchart of specific control contents of the authentication process shown in S64 described above.

  With reference to FIG.8 (d), the process which searches the customer database 15 based on received terminal ID and a telephone number is performed by S85. Then, through S86, it is determined whether or not the corresponding customer personal data is registered in the customer database 15. In the customer database 15, personal data of a contract user who has taken out insurance contract procedures and subscribed to insurance is registered, and the received terminal ID is the mobile phone of the contract user registered in the customer database 15. Is determined in S86. If the personal data of the corresponding customer is registered, the process proceeds to S87, and a process of returning a proper authentication result is performed. On the other hand, if there is no personal data of the corresponding customer, a process of returning an inappropriate authentication result is performed in S88, and the authentication process is terminated (returned). When the authentication request is returned from the Web server 14 in S36, the return destination of the authentication result in S87 and S88 is the Web server 14 that is the authentication request source, and the other FIG. 8 (c), FIG. 9 (a), etc. The mobile phone 1 that has transmitted the registration request signal and the mail address change signal is executed in the flowchart shown in FIG.

  Following the authentication process in S76, it is determined in S77 whether or not the result of the authentication process is appropriate. If it is appropriate, the process proceeds to S78, where the received mail address is stored in the corresponding area in the customer database 15, and the insurance correspondence window address (URL) is returned to the mobile phone 1 in S79. Processing is performed, and this mail address reception processing is completed. In the mobile phone 1 that has received the reply of the insurance correspondence window address, a determination of YES is made in S14 of FIG. 5 described above, and processing for registering the address of the insurance correspondence window is performed in S16.

  On the other hand, if the authentication result is inappropriate, NO is determined in S77 and the process proceeds to S80, where the customer management server 13 displays the received terminal ID and the unregistered abnormality message. The employee of the insurance company 11 who sees this display can recognize that an unregistered abnormality has occurred. There are mainly two possible causes of this unregistered abnormality. First of all, it can be considered that a mobile phone 1 exclusively for a contract user in which an automatic mail transmission function (S13) at the time of mail setting is incorporated is sold to a user who has not performed the insurance contract procedure. In this case, since a registration request signal is transmitted from the mobile phone of a user other than the contract user, naturally the corresponding personal information is not registered in the customer database 15, and an unregistered abnormality message is displayed. It will be.

  Secondly, the mobile phone 1 dedicated to the contract user is sold to the contract user who made the insurance contract, and personal information at the time of contract application of the contract user is transmitted from the mobile phone company 6 to the insurance company 11. The case where it was not done can be considered. As described in FIG. 3 (9), this is because the mobile phone company 6 applies insurance contracts because the insurance contract money is settled between the mobile phone company 6 and the insurance company 11 at the end of the fiscal year. It is conceivable that the mobile phone company 6 illegally obtains the insurance contract amount equivalent to the underdeclared amount at the end of the year when the insurance company 11 is declared less than the actual amount. Even in the case where an illegal act due to such underreporting occurs, an unregistered abnormality message is displayed, whereby an employee of the insurance company 11 notices the abnormality and investigates the truth to the mobile phone company 6. It becomes possible. This underreporting abnormality is detected when a registration request signal is automatically transmitted to the customer management server 13 of the insurance company 11 when the e-mail address is set from the mobile phone 1 dedicated to the contract user sold to the contract user. Yes, since this is automatically transmitted directly from the mobile phone 1 dedicated to the customer user to the customer management server 13 of the insurance company 11 without going through the mobile phone company 6, an underreport is made. There is no way for the mobile phone company 6 to stop the automatic transmission. Therefore, it can be expected that the mobile phone company 6 can prevent the underdeclaration fraud.

  In order to ensure the effect of deterring this underreporting fraud, the number of insurance contracts (for example, “2” when the terminal ID is 710436) is transmitted together in S13 of FIG. The number of insurances of the corresponding customer's insurance information may also be checked for authentication in S151.

  In addition, if the fraudulent act of underreporting is only for the deterrent effect, the automatic transmission target is not limited to the automatic transmission of email set by the contract user, but the mobile phone 1 purchased by the contract user (for example, purchase) Some information (for example, information indicating that a one-person contract has been subscribed, information on the number of subscriptions, etc.) may be automatically transmitted when the first call is made.

  FIG. 9A is a flowchart showing the specific control contents of the mail address change reception process in S62. In S90, it is determined whether or not a mail address change signal has been received. If it has not been received, the mail address change reception process ends. On the other hand, if a new mail address, a telephone number, and a terminal ID are transmitted from the cellular phone 1 together with the mail address change signal in accordance with S23 of FIG. 6, a determination of YES is made in S90, and the above-described authentication process is performed in S91. It is.

  Then, in S92, it is determined whether or not the result of the authentication process is appropriate. If it is appropriate, the process proceeds to S93, and the received new mail address is stored in the corresponding area in the customer database 15. On the other hand, when the result of the authentication process is inappropriate, the process proceeds to S94, and the customer management server 13 displays the received terminal ID and the unregistered abnormality message.

  FIG. 9B is a flowchart showing the specific control contents of the accident claim registration process of S65. In S95, it is determined whether or not an accident claim registration request has been made. If not, the accident claim registration process is terminated. On the other hand, entry data, imaging data, etc. at the time of the accident claim are transmitted from the mobile phone 1 to the Web server 14 according to S46, S52, S53, S203, S204, and the Web server 14 causes the accident according to S137 of FIG. If the billing registration request, the received entry data, the current position, and the terminal ID data are transmitted to the customer management server 13, a determination of YES is made in S95 and the process proceeds to S96. In S96, the customer database 15 is searched based on the received terminal ID, and the accident claim data is stored in the corresponding area.

  FIG. 9C is a flowchart showing specific control contents of the year-end settlement process in S66. By S100, it is determined whether or not a year-end settlement operation has been performed. If an employee of the insurance company 11 operates the customer management server 13 to perform the year-end settlement operation, a determination of YES is made in S100 and the process proceeds to S101, where the customer database is checked to determine the number of insurance contract applications this year. Processing for calculation and aggregation is performed. For example, in the case of a user whose terminal ID stored in the customer database 15 of FIG. 1 is 710436, one person has two insurances (responsibility insurance and traffic accident insurance). The number of contracts is counted as “2”. Next, the process proceeds to S102, where the number of applications × 2000 yen is calculated, and a process for obtaining the contract amount for the current year is performed. Next, the process proceeds to S103, where the contract amount of this year minus the estimated insurance premium received (the estimated insurance premium payment paid from the mobile phone company 6 in accordance with FIG. 3 (1)) is calculated, and the balance is calculated. Then, in S104, the calculated balance is displayed by the customer management server 13. When the value of this balance is positive, the mobile phone company 6 is charged only for the positive balance. Conversely, if the balance is a negative value, the insurance company 11 pays the negative balance amount to the mobile phone company 6.

  FIG. 10 is a flowchart showing the control operation of the Web server 16. First, in S110, it is determined whether or not the mobile phone 1 has accessed the homepage of the insurance company 11, and if not, the processing of this Web server is terminated. On the other hand, when the user operates the mobile phone 1 to access the home page, the control proceeds to S111, and it is determined whether or not the access is to the insurance support window. If the access is not to the insurance support window, other Web server processing is performed in S112, and then the Web server processing ends. On the other hand, when the user operates the mobile phone 1 to access the insurance support window, a determination of YES is made in S111 and the process proceeds to S113, where it is determined whether or not the terminal ID has been received and until it is received. stand by. In the mobile phone 1, as described in S 27 of FIG. 7 described above, after accessing the insurance support window, a process of automatically transmitting the terminal ID of the accessed mobile phone 1 is performed. Is transmitted, a determination of YES is made in S113, the process proceeds to S114, and a process of issuing an authentication request to the customer management server 13 is performed.

  Thereafter, in S115, it is determined whether or not the proper authentication result has been received. If it has not been received yet, the process proceeds to S116, and it is determined whether or not the inappropriate authentication result has been received and has not yet been received. If not, the process returns to S115. Upon receiving the authentication request, the customer management server 13 makes a determination of YES in S63 described above, executes the authentication process in S64, and returns a proper authentication result in S87 or an incorrect authentication result in S88. If the inappropriate authentication result is returned, a determination of YES is made in S116, the process proceeds to S124, and a process of returning the inappropriate authentication result to the mobile phone 1 is performed. In response to this, the cellular phone 1 performs improper display in S30 of FIG. On the other hand, if a proper authentication result is returned from the customer management server 13, a determination of YES is made in S115, and the process proceeds to S117, where a process of returning the proper authentication result to the mobile phone 1 is performed. In the cellular phone 1 that has received this, a determination of YES is made in S29 of FIG. 7 described above, and a process of displaying the insurance correspondence window is performed in S31.

  In the Web server 14, after S <b> 117, processing for transmitting the insurance correspondence window page to the mobile phone 1 is performed in S <b> 118. Next, the process proceeds to S119, where it is determined whether or not there has been an access to the accident claim window. If there is not yet an access to the consultation window, it is determined whether or not there has been an access to the consultation window. In step S119, it is determined whether or not a cancel operation has been performed. If not, the process returns to step S119.

  If a cancel operation is performed from the mobile phone 1 according to S34 in FIG. 7 during the loop of S119 → S120 → S121 → S119, the determination of YES is made in S121 and the processing of this Web server ends. On the other hand, when access to the consultation counter is performed in accordance with S33 of FIG. 7, a determination of YES is made in S120, the process proceeds to S122, and a process of transmitting the page of the consultation counter to the mobile phone 1 is performed. Thus, the consultation handling process is performed and the process of this Web server is completed.

  Further, if the mobile phone 1 accesses the accident claim window according to S32 of FIG. 7 described above, a determination of YES is made in S119, and the process proceeds to S125 shown in FIG. A determination is made as to whether or not a selection operation has been made. If not, the process proceeds to S126, and a determination is made as to whether or not a liability accident has been selected. If not, the process proceeds to S127 to select a mobile phone damage accident. A determination is made as to whether or not there has been an operation. If there is no operation, the process proceeds to S133, and a determination is made as to whether or not a cancel operation has been performed. If not, the process returns to S125.

  If a cancel operation is performed by the mobile phone 1 in accordance with S38 in FIG. 7 during the loop of S125, S126, S127, S133, and S125, YES is determined in S133 and the processing of this Web server is performed. finish. If the mobile phone 1 performs a traffic accident selection operation in accordance with S36 of FIG. 7, a determination of YES is made in S125, and the process proceeds to S128, and the traffic accident entry page (traffic accident claim window page) is displayed on the mobile phone. After the process of transmitting to 1, the process proceeds to S130.

  In S130, it is determined whether or not the entry item, the photo data, and the current position have been received. If not yet received, the process proceeds to S131 to determine whether or not a cancel operation has been performed. If not, the process returns to S130.

  When the cancel operation is performed in S48 or S58 of FIG. 7 in the mobile phone 1, a YES determination is made in S131, and the processing of this Web server ends. On the other hand, if the entry item, the photo data, and the current position are transmitted in accordance with S52 and S53 in FIG. 7 in the mobile phone 1, a determination of YES is made in S130, and the process proceeds to S132 to receive the accident claim registration request and the received entry Processing for transmitting the item, the photo data, the current position, and the terminal ID to the customer management server 13 is performed.

  On the other hand, if the operation for selecting a liability accident is performed on the mobile phone 1 in accordance with S37 of FIG. 7, a determination of YES is made in S126, and the process proceeds to S129. Page) is returned to the mobile phone 1. Thereafter, the loop of S130 → S131 → S130 is circulated. If a cancel operation is performed on the mobile phone 1 in accordance with S42 or S45 in FIG. 7 during the loop, the determination of YES is made in S131 and the processing of this Web server is terminated. On the other hand, if the cellular phone 1 transmits the entry, the photo data, and the current position data in accordance with S46 and S53, the determination of YES is made in S130 and the process of S132 is executed.

  If a cellular phone damage accident is selected in accordance with S54 in FIG. 7 in the cellular phone 1, a determination of YES is made in S127, and the process proceeds to S134, where the cell phone damage entry page (cell phone damage accident claim window) is displayed on the cellular phone. The process of returning to 1 is performed. Thereafter, in S135, it is determined whether or not the entry data has been received. If not yet received, the process proceeds to S136, and it is determined whether or not a cancel operation has been performed. Returns to S135.

  If a cancel operation is performed in S202 of FIG. 11B on the mobile phone 1, a YES determination is made in S136, and the processing of this Web server ends. On the other hand, if the entry data and the current position data are transmitted in accordance with S203 and S204 in FIG. 11B in the mobile phone 1, a determination of YES is made in S135, and the process proceeds to S137, where an accident claim registration request is received. Processing for transmitting the received entry data, current position, and terminal ID to the customer management server 13 is performed. In response to this, the customer management server 13 determines YES in S95 of FIG. 9 described above, and executes the registration process of S96.

12 and 13 are flowcharts showing the control operation of the insurance processing server 8.
Referring to FIG. 12 (a), an application process executed when an insurance contract application procedure and a mobile phone application procedure are performed is performed in S140, and an email address reception process is performed in S141. In step S142, mail address change acceptance processing is performed. In step S143, year-end settlement processing is performed, and then the process returns to step S140.

  FIG. 12B is a flowchart showing the specific control contents of the purchase process shown in S140. In S145, it is determined whether or not application data has been input. If there is no application data, the application process ends. On the other hand, when the application form data described based on (2) of FIG. 3 is input to the insurance processing server 8, a determination of YES is made in S145, and the process proceeds to S146, where the customer is based on the application form data. Processing for registering data (terminal ID, name, address, telephone number, insurance information) other than the mail address in the database 10 is performed. Next, the process proceeds to S147, and processing for transmitting the application form data to the customer management server 15 of the insurance company 11 is performed.

  FIG. 12C is a flowchart showing the specific control contents of the mail address reception process shown in S141. This mail address reception process is substantially the same as the mail address reception process shown in FIG. 8C, and the difference is that the process of S79 of FIG. 8C is not performed. Since other than that is the same, the description here is not repeated.

  FIG. 12D is a flowchart showing specific control contents of the authentication processing in S151. This authentication process has the same control contents as the authentication process shown in FIG. 8D, and the description thereof will not be repeated.

  FIG. 13A is a flowchart showing specific control contents of the mail address change reception process in S142. This mail address change reception process has the same contents as the mail address change reception process shown in FIG. 9A, and the description thereof will not be repeated.

  FIG. 13B is a flowchart showing the specific control contents of the year-end settlement process shown in S143. First, in S165, it is determined whether or not a year-end settlement operation has been performed. If an employee of the mobile phone company 6 operates the insurance processing server and performs the year-end settlement operation, a determination of YES is made in S165 and the process proceeds to S166, where the customer database 10 is checked to apply for an insurance contract for the current year. A process of calculating and summing the number is performed. Next, in S167, the number of applications × 2000 yen is calculated to calculate the contract amount for the current year. Next, the process proceeds to S168, and the process of calculating the balance by calculating the contract amount of the current year−the estimated insurance premium for payment (see the description of (1) in FIG. 3) is performed. Next, the process proceeds to S169, and the insurance balance server 8 displays the calculated balance. If this balance is positive, the mobile phone company 6 will charge the insurance company 11 for the positive balance. If the balance is negative, the negative balance will be The mobile phone company 6 pays the insurance company 11.

[Modification]
Next, modifications of the embodiment described above are listed.

  (1) In the above-described embodiment, the procedure for purchasing a mobile phone and applying for an insurance contract is performed by entering predetermined items on a predetermined form at the window of the mobile phone company 6 (offline contract). It was. However, instead, using the user's personal computer, etc., the mobile phone company's application window is accessed via the Internet, and the policyholder and the covered You may make an online contract that allows you to apply by filling in predetermined items including personal information of the insurer. In that case, a copy of the identification card is mailed to the mobile phone company 6 so that the telephone can be confirmed. The price plan, mobile phone operation method, handling precautions, and important explanations are introduced to the user's personal computer via video on the Internet, and finally the identity confirmation is sent via the Internet to confirm the mobile phone purchase procedure and insurance contract. The application process is completed. Then, the mobile phone 1 is mailed to the contract user at a later date. Data relating to the insurance contract application procedure is transmitted from the mobile phone company 6 to the insurance company 11, and the insurance company 11 also registers the data of the contract contents. This simplifies the document and speeds up the procedure.

  (2) In addition to the aforementioned S13 and S23, as a support function for a contract insurance contract user incorporated in advance in the mobile phone 1 dedicated to the contract user, the address (URL) of the insurance support window of the insurance company 11 is stored in advance. (Favorites and the like) 23 may be stored. Furthermore, when a telephone call (for example, 110 or 119) of an organization (for example, police or fire department) to which a user generally contacts in the event of an accident is input to the mobile phone 1 and a call is made, After the call, the fact that an accident has occurred automatically is transmitted from the mobile phone 1 to the customer management server 13 of the insurance company 11, and the corresponding telephone number of the user is searched in the customer management server. You may make it the structure which takes a telephone. In this way, the telephone from the insurance company 11 can prompt the user to access the insurance correspondence window and prevent the user from forgetting to access the insurance correspondence window after the accident occurs. Can do.

  (3) In the above-described embodiment, the terminal ID of the mobile phone 1 is registered in the customer databases 15 and 10 and the customer databases 15 and 10 are searched based on the terminal ID. In addition to or in addition, a cookie may be used. Specifically, after storing a cookie for identifying the mobile phone 1 in the memory 23 of the dedicated mobile phone 1 sold to the contract user, the mobile phone 1 is sold to the contract user, and the customer database In 15 and 10, the personal information of the contract user is registered together with the cookie. When the mobile phone 1 accesses the Web server 14, the customer management server 13, or the insurance processing server 8, the cookie stored in the memory 23 is transmitted from the mobile phone 1 to these servers, and the server side The customer databases 15 and 10 are searched based on the received cookie, and the corresponding personal information can be determined.

  (4) The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

It is a system diagram which shows the whole structure of an insurance system. It is a functional block diagram of a mobile phone. It is explanatory drawing which shows the flow of an insurance system. It is a flowchart which shows control of a mobile telephone. It is a flowchart which shows the specific control content of a mail address setting process. It is a flowchart which shows the specific control content of a mail address change process. It is a flowchart which shows the specific control content of a web browser process. (A) is a flowchart which shows the control of a customer management server, (b) is a flowchart which shows the specific control content of the process at the time of application, (c) is a flowchart which shows the specific control content of the process at the time of mail address reception. (D) is a flowchart showing the specific control contents of the authentication process. (A) is a flowchart showing the specific control contents of the mail address change reception process, (b) is a flowchart showing the specific control contents of the accident claim registration process, and (c) is the specific of the year-end settlement process. It is a flowchart which shows the content of automatic control. It is a flowchart which shows the control operation of a Web server. (A) is a flowchart showing the continuation of the control operation of the Web server, and (b) is a flowchart showing the continuation of the Web browser process. (A) is a flowchart showing the control operation of the insurance processing server, (b) is a flowchart showing the specific control contents of the application process, and (c) shows the specific control contents of the mail address reception process. It is a flowchart and (d) is a flowchart which shows the specific control content of an authentication process. (A) is a flowchart which shows the specific control content of a mail address change reception process, (b) is a flowchart which shows the specific control content of a year-end settlement process.

Explanation of symbols

  1 Mobile phone, 5 Internet, 6 Mobile phone company, 8 Insurance processing server, 10 Customer database, 11 Insurance company, 13 Customer management server, 15 Customer database, 14 Web server, 16 Web database, 22 Control unit, 23 Memory, 24 Operation unit, 26 digital camera, 27 display unit, 30 customer (contractor).

Claims (3)

An insurance system for managing a user's insurance contract using a computer,
An insurance service server for registering the user as an insurance contract user in order to provide an insurance service when the application procedure for the insurance contract is performed by the user;
A mobile communication terminal provided to the user when the user purchases the mobile communication terminal and the user desires the insurance contract and performs the application procedure of the insurance contract and the purchase procedure of the mobile communication terminal; Including
The insurance system, wherein the mobile communication terminal is a mobile communication terminal dedicated to an insurance contract user in which a support function for an insurance contract user who applied for the insurance contract is incorporated in advance. Used in an insurance system that manages a user's insurance contract using a computer, provided to the user when the user desires the insurance contract and performs the insurance contract application procedure and the mobile communication terminal purchase procedure A portable communication terminal,
A mobile communication terminal in which a support function for an insurance contract user who applied for the insurance contract is incorporated in advance.   The said mobile communication terminal is provided with the automatic transmission means which transmits this mail address to the said server for insurance business automatically, when setting a mail address to the said mobile communication terminal as the said support function. Mobile communication terminal.

Images