JP4432242B2 - Insurance contract renewal management server - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an insurance contract renewal system, an insurance contract renewal method, a client terminal, an insurance contract renewal management server, and a recording medium for generating data useful for insurance contract renewal of an insurance policyholder.
[0002]
BACKGROUND OF THE INVENTION
In general, at the time of insurance contract, it is generally performed that a health examination is performed on a policyholder and both the insurance company and the policyholder confirm the health condition. Based on the result of the health check, it is determined whether or not an insurance contract is possible. If possible, an insurance contract is concluded. In addition, by subscribing to not smoking at the time of contract, risk-divided insurance that can receive premium discounts has also emerged.
[0003]
[Problems to be solved by the invention]
However, in fact, insurance companies can understand the health of a contractor by conducting a health check at the time of contracting or by notification, but it is not possible to grasp the health status of the subsequent contractor. It is. For this reason, the lifestyle of the contractor after the contract cannot be reflected in the insurance, and thus an insurance system that can reflect the lifestyle of the contractor after the contract cannot be constructed.
[0004]
The present invention has been made in view of such a situation, and an insurance contract renewal system, an insurance contract renewal method, a client terminal, an insurance, which can construct an insurance system that can reflect the lifestyle of the contractor after the contract is made It is an object to provide a contract renewal management server and a recording medium.
[0028]
[Means for Solving the Problems]
In the insurance contract renewal management server according to the invention of claim 1 , a contract level table in which a plurality of insurance contract levels and the average number of steps per day corresponding to each insurance contract level are stored in association with each other And an ID receiving means for receiving ID data given from an insurance company, transmitted from a terminal having a function of detecting the number of steps carried by the policyholder, and transmitted from the terminal at predetermined intervals. a step count receiving means for receiving the step count data of the policyholder to be, for each policyholder, the ID and data is stored, a storage unit count data received is accumulated and stored by the step number receiving means , based on the ID data received by the ID receiving unit, a retrieving means for retrieving subscriber file of the storage means, 蓄in said storage means and passes a first predetermined time period Calculating the average daily number of steps from the stored count data, and calculation means for storing in the storage means, insurance contracts corresponding to average daily number of steps calculated by the calculation means and passes a second predetermined time period The contract renewal means for calculating the level using the contract level table, renewing the contract of the policyholder using the calculated insurance contract level, and the contractor file of the policyholder of the storage means by the contract renewal means And a transmission unit for transmitting a result of contract renewal by the contract renewal unit to the terminal.
[0032]
In the insurance contract renewal management server according to the second aspect of the invention, the storage means is a database connected to the management server via the network.
[0033]
Therefore, according to the above-described inventions according to claims 1 and 2, it is possible to provide a management server capable of constructing an insurance system that can reflect the lifestyle of the contractor after the contract.
[0039]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to the drawings. As shown in FIG. 1, an insurance contract renewal system 1 according to the present embodiment includes a mobile phone terminal 4 as a client terminal that can be connected to each other via a base station 1, a public telephone network 2 and a network 3, an insurance The contract renewal management server 5 (hereinafter simply referred to as the management server 5) and the database 6 connected to the management server 5 via the network 3 are configured. The management server 5 is a server operated and managed by a life insurance company, and the mobile phone terminal 4 is a terminal carried by an insurance contractor who has concluded a contract with the insurance company.
[0040]
The mobile phone terminal 4 has a device main body 402, a telescopic rod antenna 403 is provided on the top of the device main body 402, and a telephone speaker 404 is disposed on the upper front surface. Below the speaker 404, a display unit 405 including an LCD for displaying received messages, operation guidance of the mobile phone terminal 4, operation status, and the like is disposed. A plurality of keys 407 are arranged at the lower part of the display unit 5, and a microphone 408 is arranged near the lower end of the keys 407.
[0041]
FIG. 2 is a block diagram showing a circuit configuration of the mobile phone terminal 4, and the speaker 404, the display unit 405, the key 407, and the microphone 408 are connected to the control unit 9. Further, a pedometer 406, a speaker 410, a transmission / reception unit 411 connected to the antenna 43, a sound source 412, a reception data storage unit 413, a clock unit 414, and an ID storage unit 415 are connected to the control unit 9.
[0042]
The pedometer 406 has a well-known configuration and includes an acceleration sensor inside. The pedometer 406 generates a signal every time a person carrying the mobile phone terminal 4 walks, and the generation of this signal is counted by a counter 93 described later. The speaker 410 is for calling and generates a ring tone when receiving an incoming call. The transmission / reception unit 411 performs wireless communication with the base station 16 shown in FIG. The sound source 12 stores waveform data, and the received data storage unit 413 stores received mail data. The clock unit 414 is used for measuring a predetermined number of days, which will be described later, and the ID storage unit 415 stores an ID given by an insurance company who owns the mobile phone terminal 4 from an insurance company.
[0043]
The control unit 409 includes a CPU, a ROM, a RAM, and the like. The CPU operates according to a program stored in the ROM while using the RAM as a work area, thereby controlling each unit and necessary for the mobile phone terminal 4. Execute the process. As described above, the program may be stored in the ROM in advance, or a storage medium storing the program may be attached to the control unit 409. In this case, the storage medium is composed of a magnetic or optical recording medium or a semiconductor memory. The program stored in the storage medium may be configured to receive a part or all of the program from the management server 5 and store it.
[0044]
In addition, the control unit 409 transmits the measurement value by the pedometer 406 to the management server 5 via the telephone line network 2 and the network 3, or takes in the message data stored in the management server 5, and displays the display unit 5 Execute the process displayed on the screen. In order to perform such data communication, the controller 409 includes an encoder 91 that converts data into a signal for transmission, a decoder 92 that restores message data from a received signal, and a signal from the pedometer 406, That is, a counter 93 for counting the number of steps is built in.
[0045]
As shown in FIG. 3, the management server 5 includes a CPU 502, a program memory 503, a RAM 504, an input unit 505, a display unit 506, and a communication unit 507 connected via a bus 501. The CPU 502 controls each unit by operating while using the RAM 504 as a work area based on a program stored in the program memory 503. The input unit 505 includes a keyboard and a mouse, and the display unit 506 includes a CRT and an LCD. The communication unit 507 has a modem or the like, exchanges data with the mobile phone terminal 4 via the telephone line network 2 and the base station 1, and exchanges data with the database 6 via the network 3.
[0046]
The program memory 503 stores a contract level table 510 shown in FIG. 4 together with the program. The contract level table 510 includes a plurality of areas 511, 512, 513, and 5014 that correspond to each other. The area 511 stores the insurance contract levels “1” to “5”, and the area 512 stores the daily activity levels “low”, “normal”, and “normal” corresponding to the insurance contract levels “1” to “5”. Somewhat high, high, and fairly high are stored. An area 513 stores an average number of steps per day corresponding to each level, and an area 514 stores an insurance discount rate corresponding to each level.
[0047]
The program memory 503 is composed of a magnetic or optical recording medium or a semiconductor memory. This program memory 503 is fixed to the management server 5 or is detachably mounted. The program, table data, and the like stored in the program memory 503 may be configured to be received and stored from the communication unit 507 via the network 3 in part or in whole.
[0048]
As shown in FIG. 5, the database 6 stores a contractor file 601 for each contractor who has contracted with an insurance company. This contractor file 601 has areas 602 to 608. The area 602 records the contractor name, and the area 603 records the ID assigned to the contractor. In area 604, the current contract level of the contractor (see area 511 in FIG. 4) is recorded. The area 605 records a discount rate (see the area 514 in FIG. 4), and the area 606 stores the current month count value that is an accumulated value of the number of steps in the current month while being updated. Further, the area 607, 608,... Stores the average number of steps per day for each month.
[0049]
In the present embodiment having the above configuration, the control unit 409 of the mobile phone terminal 4 operates according to the flowchart of FIG. 6 based on a program stored in the internal ROM. First, the counter 93 is reset (step SA1), and then the step count is executed (step SA2). At this time, if the policyholder is acting with the mobile phone terminal 4, a signal is output from the pedometer 406 for each walk, and the control unit 409 counts up the counter 93 in response to this. The number of steps taken by policyholders will be measured.
[0050]
Next, it is determined based on the date data measured by the clock unit 414 whether or not a predetermined number of days have passed (step SA3). Here, since the average number of steps is calculated in units of one month in this embodiment as will be described later, the predetermined number of days is not particularly limited as long as the number of days is within one month, such as one week or two days. However, it is preferably the number of days (for example, one day) in which the number of steps can be easily counted in units of one month.
[0051]
Further, the processing in step SA2 is continued until the determination in step SA3 is YES. Therefore, the measurement of the number of steps by the pedometer 406 is continued until the predetermined number of days is reached, and the value of the counter 93 is increased. If the predetermined number of days have elapsed, the control unit 409 performs automatic call processing, accesses the management server 5 via the base station 1, the public telephone network 2, and the network 3, and stores the ID storage unit 4 in the ID storage unit 4. The stored ID is transmitted to the management server 5 (step SA4). Subsequently, the control unit 409 reads the count value of the counter 93 and transmits it to the management server 5 (step SA5).
[0052]
Thereafter, it is determined whether or not the processing result of the management server 5 has been received (step SA6). If not received, the processing from step SA1 is repeated. Accordingly, by repeatedly executing the processes of steps SA1 to SA6, the number of steps of the policyholder during the predetermined number of days is transmitted from the mobile phone terminal 4 to the management server 5 every time the predetermined number of days elapses. As will be described later, when the processing result is transmitted from the management server 5 side and received (step SA6; YES), the processing result is displayed on the display unit 405 (step SA7).
[0053]
On the other hand, the CPU 502 of the management server 5 executes processing according to the flowchart shown in FIG. 7 based on the program stored in the program memory 503. That is, the ID transmitted from the mobile phone terminal 4 is received (step SB1), and the count value is received (step SB2). Next, based on the ID received in step SB1, the contractor file 601 of the contractor corresponding to the ID is searched from the database 6 (step SB3).
[0054]
Further, the current count value received in the previous step SB2 is added to the current count value of the current month (the number of steps of the contractor) stored in the area 606 of the searched contractor file 601 and updated. (Step SB4). Subsequently, based on the timing function of the CPU 502, it is determined whether or not one month has passed (step SB5), and the processes of steps SB1 to SB5 are repeated until one month has passed. As a result, the number of steps of the corresponding contractor is sequentially updated and recorded in the area 606 of the contractor file 601.
[0055]
Then, if one month has passed, the process proceeds from step SB5 to step SB1, and the average number of steps per day in the current month is calculated by dividing the count value stored in the area 606 by the number of days in the current month. The calculated average number of steps is recorded in the corresponding month area in the areas 607, 608... In the contractor file 601 of the contractor (step SB6). After that, the unnecessary month count value remaining in the area 606 of the contractor file 601 of the contractor is cleared (step SB7).
[0056]
Further, it is determined whether or not 12 months (one year) have elapsed (step SB8), and the processes of steps SB1 to SB8 are repeated until December has elapsed. As a result, the average number of steps per day for each month for 12 months of the contractor is recorded in the areas 607, 608,... Of the contractor file 601. If the average number of steps per day for each month for 12 months of the contractor is recorded in the areas 607, 608... Of the contractor file 601, the contract renewal process is executed. (Step SB9).
[0057]
This contract renewal process (step SB9) is executed according to the flowchart shown in FIG. First, in the area 607, 608,... Of the contractor file 601, it is determined whether or not the month of the daily activity level that is one level higher than the current contract level is “3” or more (step SB91). That is, as in the case of Mr. A shown in FIG. 9 (A), if the 10% discount application (one year contract) of “slightly high” was applied in the last April declaration, “slightly high” As shown in FIG. 4, the contract level is 3. Further, the contract level one above the contract level 3 is “4”, the daily activity level is “high”, and the average number of steps per day is 8001 to 10,000.
[0058]
Therefore, in step SB91, it is determined whether or not there are three or more values of “8001 to 10000” as the next level in the step count data for 12 months shown in FIG. 9A. Then, in FIG. 9A, the values “8001 to 10000” are April, May, June, October, January, February, and March, which is a total of seven. Therefore, the determination result in step SB91 is YES, and the contract is renewed to level 4, which is one level higher (step SB92). That is, the contract level recorded in the area 604 of the contractor file 601 of Mr. A is changed from “3” to “4”.
[0059]
Further, it is determined whether or not the month of the daily activity level that is one level higher than the current contract level is “7” or more (step SB93). As described above, in the case of Mr. A shown in FIG. 9A, since the month of the daily activity level that is one level higher than the current contract level is “7”, the process proceeds from step SB93 to step SB94. In step SB94, the difference between the premium of the current contract level and the premium of the contract level one level higher is refunded (to Mr. A) (step SB94). This difference can be refunded by transferring money to the account of the contractor by a remittance method using the known network 3.
[0060]
The contractor (Mr. A) continues to process these processing results, that is, to change the contract level to “4” and to refund the difference between the premium of the current contract level and the premium of the next contract level. ) To the mobile phone terminal 4 (step SB99). Then, in step SA6 in the flowchart of FIG. 6 described above, it is determined whether or not the mobile phone terminal 4 side has received this processing result, and when it is received, this is displayed on the display unit 405 in step SA7. Therefore, the contractor is renewed to the next higher contract level according to his / her own activity level in one year, and the discount rate becomes higher (in the case of Mr. A, 10% to 20%; see FIG. 4), and the difference amount You can know that there is a refund.
[0061]
On the other hand, if the determination in step SB91 is NO, the process proceeds to step SB95, and in the area 607, 608... Of the contractor file 601, the month of the daily activity level one level lower than the current contract level is “ 3 "or more is determined (step SB95). In other words, as in the case of Mr. B shown in FIG. 9B, if the 10% discount application (one year contract) of “Slightly High” was applied in the last April's contract declaration, “Slightly High” As shown in FIG. 4, the contract level is 3. Further, the contract level one lower than the contract level 3 is “2”, the daily activity level is “normal”, and the average number of steps per day is 3001 to 5000.
[0062]
Therefore, in step SB95, it is determined whether or not there are three or more values of “3001 to 5000” as the next level in the step count data for 12 months shown in FIG. 9B. Then, in FIG. 9B, the values of “3001 to 5000” are July, October, and November, which is a total of three. Therefore, the determination result in step SB95 is YES, and the contract is renewed to level 4 which is the next lower level (step SB96). That is, the contract level recorded in the area 604 of Mr. B's contractor file 601 is changed from “3” to “2”.
[0063]
Further, it is determined whether or not the month of the daily activity level one level lower than the current contract level is “7” or more (step SB97). As described above, in the case of Mr. B shown in FIG. 9B, the month of the daily activity level that is one level lower than the current contract level is “3”, so that the process of step SB98 is not performed. Proceed to SB99. Therefore, in the case of Mr. B, only that the contract level is changed to “2” is transmitted to the mobile phone terminal 4 of the contractor (Mr. B) (step SB99).
[0064]
If the determination in step SB97 is yes, the process proceeds to step SB98. In step SB98, the difference between the insurance premium at the current contract level and the insurance premium at the next contract level is added. The additional amount of the difference may be deducted from the account of the contractor by a known deduction method using the network 3.
[0065]
Subsequently, these processing results, that is, that the contract level has been changed, and that the difference between the premium of the current contract level and the premium of the next contract level is refunded are transmitted to the mobile phone terminal 4 of the contractor. (Step SB99). As a result, the contractor is renewed to the contract level one level lower according to his / her activity level in one year, and the discount rate is lowered (in the case of Mr. B, 10% to 0%; see FIG. 4), and You can know that there are additional charges.
[0066]
In the present embodiment, a pedometer is used as the detection means for detecting the daily activity amount. However, the present invention is not limited to this, and the body motion of the contractor is detected by the vibration detection sensor, or the daily activity is detected. You may make a contractor self-report the amount of activity. In the present embodiment, the contractor file 601 is stored in the database 6, but the contractor file 601 may be stored in the RAM 504 in the management server 5.
[0067]
【The invention's effect】
As described above, according to the present invention, it is possible to construct an insurance system that can reflect the lifestyle of the contractor after the contract. Further, it is possible to use appropriate step count data that can reflect the lifestyle of the contractor while reducing the communication cost by reducing the number of accesses from the client terminal to the management server as much as possible. Further, it is possible to construct an insurance system that can appropriately reflect the lifestyle of the contractor after the contract in the contract renewal. In addition, it is possible to construct a simple insurance system that can reflect the lifestyle of the policyholder after the contract, while changing the level set at the time of renewal according to the number of steps of the policyholder.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram showing an embodiment of the present invention.
FIG. 2 is a block diagram showing a mobile phone terminal as a client terminal.
FIG. 3 is a block diagram showing a management server.
FIG. 4 is a schematic diagram showing a configuration of a contract level table stored in a program memory of the management server.
FIG. 5 is a schematic diagram showing a memory configuration of a contractor file.
FIG. 6 is a flowchart showing a processing procedure of the mobile phone terminal.
FIG. 7 is a flowchart showing a processing procedure of the management server.
FIG. 8 is a flowchart showing details of contract renewal processing.
FIG. 9 is a diagram illustrating a recording example of a contractor file.
[Explanation of symbols]
1 Insurance Contract Renewal System 2 Public Telephone Network 3 Network 4 Mobile Phone Terminal 5 Management Server 6 Database 93 Counter 405 Display Unit 406 Pedometer 415 ID Storage Unit 502 CPU
503 Program memory 510 Contract level table 601 Contractor file

Claims (2)

A contract level table in which a plurality of insurance contract levels and an average number of steps per day corresponding to each insurance contract level are stored in association with each other;
ID receiving means for receiving the ID data given from the insurance company by the policyholder transmitted from a terminal having a function of detecting the number of steps carried by the policyholder;
Step number receiving means for receiving step number data of the policyholder transmitted from the terminal every predetermined period ;
For each policyholder, the ID data is stored, and storage means for storing the step count data received by the step count receiving means ;
Search means for searching for a contractor file in the storage means based on the ID data received by the ID receiving means;
Calculating means for calculating an average number of steps per day from step count data accumulated and stored in the storage means when a first predetermined period has elapsed, and storing the average number of steps in the storage means;
The insurance contract level corresponding to the average number of steps per day calculated by the calculating means after the second predetermined period has elapsed is calculated using the contract level table, and the policyholder's contract using the calculated insurance contract level Contract renewal means for renewal,
Changing means for changing the contractor file of the policyholder in the storage means by the contract renewal means;
An insurance contract renewal management server, comprising: transmission means for transmitting a result of contract renewal by the contract renewal means to the terminal. The insurance contract renewal management server according to claim 1, wherein the storage means is a database connected to the management server via the network.

Images