Information processing system, method, and program
The information processing system automates insurance contracting in smart cities by integrating user terminals and servers for identity verification and contract processing, enhancing insurance solutions and promoting safer urban environments.
Patent Information
- Application Number
- JP2023192169
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-11-10
- Publication Date
- 2025-05-22
- Estimated Expiration
- 2043-11-10
AI Technical Summary
Existing technologies lack an efficient and integrated system for providing insurance solutions that can enhance the value of smart cities or super cities.
An information processing system that automates the insurance contracting process by integrating user terminals, first and second information processing servers, to verify identities and process insurance contracts based on personal and risk-related data.
The system enables automatic insurance contracting for residents and employees of smart cities, providing comprehensive compensation and encouraging behavioral changes by reflecting risk-related data in insurance premiums.
Smart Images

Figure 2025079476000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing system, a method, and a program. [Background technology]
[0002] In recent years, various technologies that promote digitalization have been developing rapidly, and efforts are being made in various regions to incorporate these technologies into urban development in order to solve the problems facing cities and regions.
[0003] One example of such an initiative is the realization of smart cities or super cities, and approaches are being taken from various angles, including medical care, transportation, energy, and disaster prevention. Summary of the Invention [Problem to be solved by the invention]
[0004] Therefore, the present invention aims to provide an information processing system, method, and program that can provide new added value to smart cities or super cities through insurance. [Means for solving the problem]
[0005] An information processing system according to one embodiment of the present invention includes a processing unit that processes a request for resident registration from a user terminal, and the processing unit sends an identity verification request to a first information processing server based on personal information and identity verification information included in the request for resident registration, and if a positive identity verification result is received in response to the identity verification request, sends a contract request including the personal information and information on the insurance that is the subject of the contract to a second information processing server, and if a positive contract result is received in response to the contract request, notifies the user terminal of completion of resident registration.
[0006] According to this aspect, the information processing system can support automatic contracting of insurance in response to a request for resident registration. The information processing system can provide comprehensive compensation to people involved in smart cities or super cities, thereby ensuring a safe and secure life.
[0007] The information processing system may further include a transfer unit that transmits the personal data collected by the user terminal to the first information processing server. According to this aspect, the first information processing server can effectively collect the personal data and contribute to the utilization of the data.
[0008] The first information processing server may process the request for identity verification based on a database in which information on people related to a specific area is registered. According to this aspect, it is possible for a person who has an address in a smart city or a super city or an employee of a company located in the city to automatically contract for insurance that is equally necessary for residents of the smart city or the super city.
[0009] The first information processing server may process the request for identity verification based on a database in which information on persons related to a specific company is registered. According to this aspect, it is possible for employees of a specific company to automatically apply for insurance that is equally necessary for employees of the company.
[0010] The information processing system may further include a recommendation unit that transmits information on insurance to be proposed to a user who uses the user terminal. According to this aspect, it is possible to provide the user of the user terminal with information on additional insurance suitable for the user in addition to the insurance for the automatic contract.
[0011] The information processing system may further include a distribution unit that distributes bonus data to the user terminal. According to this aspect, the user of the user terminal cooperates in providing the personal data, and thereby the user can receive benefits, such as the provision of bonus data.
[0012] The second information processing server may request risk-related data from the first information processing server and calculate the insurance premium based on the acquired risk-related data. According to this aspect, the second information processing server can calculate a more reasonable insurance premium by utilizing various risk-related data of the city to be insured. By reflecting the various risk-related data of the city in the insurance premium, it is possible to encourage behavioral changes of people related to the smart city or super city.
[0013] A method according to another aspect of the present invention includes a computer receiving a request for resident registration from a user terminal, sending an identity verification request to a first information processing server based on personal information and identity verification information included in the request for resident registration, if a positive identity verification result is received in response to the identity verification request, sending a contract request including the personal information and information on the insurance that is the subject of the contract to a second information processing server, and if a positive contract result is received in response to the contract request, notifying the user terminal of completion of resident registration.
[0014] A program according to another aspect of the present invention causes one or more computers to perform the following processes: receiving a request for resident registration from a user terminal; sending an identity verification request to a first information processing server based on personal information and identity verification information included in the request for resident registration; if a positive identity verification result is received in response to the identity verification request, sending a contract request including the personal information and information on the insurance that is the subject of the contract to a second information processing server; and if a positive contract result is received in response to the contract request, notifying the user terminal of completion of resident registration.
[0015] According to another aspect of the present invention, a second information processing server connected to the first information processing server via a communication network includes a calculation unit that requests risk-related data from the first information processing server and calculates insurance premiums based on the acquired risk-related data, the insurance being insurance for people related to a specific region or company, and the risk-related data being information about the specific region or company. According to this aspect, the second information processing server can calculate more reasonable insurance premiums by utilizing various risk-related data about the specific region or company to be insured. By reflecting the various risk-related data about the specific region or company in the insurance premium, it is possible to encourage behavioral changes in people related to the specific region or company. Effect of the Invention
[0016] According to the present invention, it is possible to provide an information processing system, method, and program that can provide new added value to smart cities or super cities through insurance. [Brief description of the drawings]
[0017] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of a system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram illustrating an example of a configuration of an application server according to an embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram showing an example of a member database (DB) according to one embodiment of the present invention. [Figure 4] FIG. 2 is a diagram showing an example of an insurance DB according to one embodiment of the present invention. [Diagram 5] FIG. 2 is a diagram showing an example of a privilege DB according to an embodiment of the present invention. [Figure 6] FIG. 2 is a diagram illustrating an example of a configuration of a city OS server according to an embodiment of the present invention. [Figure 7] FIG. 2 is a diagram showing an example of the configuration of an insurance company server according to an embodiment of the present invention. [Figure 8] FIG. 2 is a diagram showing an example of an insurance premium DB according to one embodiment of the present invention. [Figure 9] FIG. 2 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment of the present invention. [Figure 10] 10 is a flowchart showing an example of a resident registration process according to an embodiment of the present invention. [Figure 11] 10 is a flowchart showing an example of a resident registration process according to an embodiment of the present invention. [Figure 12] 10 is a flowchart illustrating an example of a data providing process according to an embodiment of the present invention. [Figure 13] 11 is a flowchart illustrating an example of a recommendation process according to an embodiment of the present invention. [Figure 14] 13 is a flowchart showing an example of insurance premium calculation processing according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0018] With reference to the accompanying drawings, the embodiments of the present invention will be described. Note that the following embodiments are intended to facilitate understanding of the present invention and are not intended to limit the present invention. In addition, the present invention can be modified in various ways without departing from the gist of the invention. Furthermore, a person skilled in the art can adopt an embodiment in which each element described below is replaced with an equivalent, and such an embodiment is also included in the scope of the present invention.
[0019] <System configuration> An overview of the present invention will be described with reference to Fig. 1. Fig. 1 is a diagram illustrating an example of the configuration of a system according to an embodiment of the present invention.
[0020] The system 1 includes an application sales management server 10, a city OS server 20, a user terminal 30, an application server 40, and an insurance company server 50. The insured application system is an example of an information processing system, and includes the application server 40 in this embodiment. The application sales management server 10, the city OS server 20, the user terminal 30, the application server 40, and the insurance company server 50 are configured to communicate via a communication network N. The network N is, for example, the Internet, a VPN (Virtual Private Network), a public telephone network, or the like. There are no particular limitations on the specific communication method in the network N, whether it is a wired connection or a wireless connection, etc.
[0021] The application sales management server 10 is a server device of a vendor that mediates the sale of applications (hereinafter, also referred to as "apps"). The application sales management server 10 includes an application DB 11 (not shown) in which a plurality of applications to be sold are registered.
[0022] The city OS server 20 is an example of a first information processing server, and in this embodiment is an administrative server device that collects and manages various data related to a specific city (an example of a specific region). The city OS server 20 includes a resident DB 21 in which information on people related to the city is registered. People related to the city include, for example, people who have addresses in the city and employees of companies located in the city.
[0023] The user terminal 30 is a terminal used by a person related to the city. A user can access the application sales management server 10 via the user terminal 30 and view a list of applications that can be purchased. In addition, a user can request the purchase of an application via the user terminal 30.
[0024] The application server 40 is a server device that executes an application purchased from the application sales management server 10 and executes a predetermined information processing related to the application. Examples of server applications that run on the application server 40 include, but are not limited to, those that collect insurance contract data, movement data, health care data, and the like and execute information processing.
[0025] The insurance company server 50 is an example of a second information processing server, and in this embodiment is a server device of an insurance company. The insurance company server 50 includes an insurance contract DB 51 in which information on insurance contracts is registered.
[0026] A user can access the application sales management server 10 via the user terminal 30 and request the purchase of an insurance-included application. When the application sales management server 10 receives the purchase request, the application sales management server 10 distributes the insurance-included application from the application DB 11 to the user terminal 30 and causes the user terminal 30 to download the application.
[0027] The user launches the downloaded insurance app, inputs personal information, identity verification information, and payment information for the app, and sends a request for resident registration (hereinafter also referred to as a "registration request") to the application server 40. In response to receiving the registration request, the application server 40 sends an identity verification request to the city OS server 20 based on the personal information and identity verification information received from the user terminal 30. When a positive identity verification result is received in response to the identity verification request, the application server 40 sends a contract request to the insurance company server 50 based on the personal information and payment information for the app. The insurance company server 50 can carry out the prescribed insurance contract processing in response to the contract request.
[0028] <Functional configuration> (Application Server) Fig. 2 is a diagram showing an example of the configuration of an application server according to an embodiment of the present invention. Although Fig. 2 assumes a single application server 40 and shows only the necessary functional configuration, the application server 40 may be configured as a part of a multi-functional distributed system made up of multiple computer systems, or cloud computing made up of one or more information processing devices may realize part of the functional configuration of the application server 40. Also, the division of the server-side and client-side processing of the insurance application shown in Fig. 2 and Fig. 9 described later is an example, and part of the server-side processing may be handled by the client side, and part of the client-side processing may be handled by the server side.
[0029] The application server 40 includes an input unit 410 , a control unit 420 , a storage unit 430 , a communication interface 440 , and a display unit 450 .
[0030] The input unit 410 is configured to receive operations from a user of the application server 40, and can be realized by a keyboard, a mouse, a touch panel, or the like.
[0031] The control unit 420 includes an arithmetic processing unit 421 such as a CPU or MPU equivalent to a processor, and a memory 422 such as a RAM. The arithmetic processing unit 421 (processor) loads a program recorded in the storage unit 430 into the memory 422 and executes it based on various inputs, thereby realizing the functions and processing described below in the arithmetic processing unit 421. This program may be stored in a computer-readable non-transitory recording medium such as a CD-ROM, or distributed via a network and installed in the computer. The memory 422 functions as a work memory required for the arithmetic processing unit 421 (processor) to execute the program.
[0032] The memory unit 430 is configured by a storage device such as a hard disk, and records various programs necessary for executing processes in the control unit 420, data necessary for executing the various programs, etc. In this embodiment, it is preferable that the memory unit 430 has a member DB 431, an insurance DB 432, and a privilege DB 433.
[0033] The member DB 431 stores basic information of members of the insured service provided by the application server 40. In one embodiment, as shown in FIG. 3, the member DB 431 stores a member ID, name, My Number, insurance information, etc. The member ID is information for uniquely identifying a member of the insured service. In this embodiment, a user who uses the insured service enters into a service contract for the service using the present invention, and is assigned a member ID through the service contract.
[0034] The insurance information is information indicating insurance that has been subscribed to. Insurance includes, but is not limited to, accident insurance, liability insurance, personal effects insurance, household goods insurance, injury and illness insurance, personal mobility insurance, and pet insurance.
[0035] The insurance DB 432 stores information on insurance provided by insurance companies. In one embodiment, as shown in FIG. 4, the insurance DB 432 stores an insurance ID, a company ID, an insurance name, insurance details, type, etc. The insurance ID is information for uniquely identifying an insurance. The insurance details stores information indicating the insurance details. The company ID is information for uniquely identifying a company, and if the insurance identified by the insurance ID is an insurance exclusively for employees of a certain company, the corresponding company ID is stored. The type stores "1" indicating mandatory subscription or "0" indicating optional subscription.
[0036] The privilege DB 433 stores privilege information provided to a user who uses an insured service. In one embodiment, as shown in Fig. 5, the privilege DB 433 stores a privilege ID, privilege content, store used, usage period, etc. The privilege ID is information for uniquely identifying a privilege. The privilege content stores information indicating the content of the privilege. The usage store stores information indicating the store where the privilege can be used. The usage period stores information indicating the period during which the privilege can be used.
[0037] The communication interface 440 is a hardware module for connecting the application server 40 to the network N and for communicating with other devices on the network N, including the city OS server 20, the user terminal 30, and the insurance company server 50.
[0038] The display unit 450 is configured to display various images processed under the control of the arithmetic processing unit 421, and can be realized by a display or the like.
[0039] Furthermore, as shown in FIG. 2, the calculation processing unit 421 includes, as functional units, a registration request processing unit 4211, a transfer unit 4212, a recommendation unit 4213, and a benefit distribution unit 4214.
[0040] The registration request processing unit 4211 transmits an identity verification request to the city OS server 20 in response to a registration request from the user terminal 30. In this embodiment, the registration request includes personal information such as name, address, and age, identity verification information, and payment information for the application, and the identity verification request includes name, address, age, identity verification information, and the like. An example of identity verification information is information that can be read from a My Number card, but is not limited to this. Specifically, the identity verification information can be any information that can be authenticated by the city OS server 20 that handles identity verification processing.
[0041] When the registration request processing unit 4211 receives a positive identity verification result as a response to the identity verification request, it transmits a contract request to the insurance company server 50. In one embodiment, the positive identity verification result includes the My Number. In this embodiment, the contract request includes the name, address, and age, which are examples of personal information, as well as payment information for the application, insurance information, and the like.
[0042] The payment information for the app includes the payment method, payment timing, payment source information, etc. for the app fee. The payment method is specified with information indicating credit card payment, direct debit, etc., the payment timing is specified with information indicating monthly or annual payment, and the payment source information is specified with credit card information or account information depending on the payment method. The insurance information includes information on the insurance to be contracted. In this embodiment, the registration request processing unit 4211 obtains the insurance ID of the insurance whose type is required from the insurance DB 432, and includes it in the insurance information.
[0043] In this embodiment, a portion of the application fee is paid to an insurance company as insurance premium, but this is just an example and is not limiting.
[0044] When the registration request processing unit 4211 receives a positive contract result as a response to the contract request, it issues a member ID for the user and registers the record in the member DB 431. When registering, the registration request processing unit 4211 also registers the My Number received from the city OS server 20. The registration request processing unit 4211 also notifies the user terminal 30 of the completion of the registration request together with the member ID.
[0045] The transfer unit 4212 transmits the personal data received from the user terminal 30 to the city OS server 20. In this embodiment, the transfer unit 4212 transfers the personal data by further including the My Number corresponding to the member ID included in the personal data, but in another embodiment, the transfer unit 4212 may transmit the received personal data to the city OS server 20 without including the My Number.
[0046] In response to a recommendation request from the user terminal 30, the recommendation unit 4213 transmits information on insurance that the user of the user terminal 30 can subscribe to at his / her discretion. In this embodiment, the recommendation request includes a member ID, and the recommendation unit 4213 obtains the My Number from the member DB 431 based on the received member ID, and transmits a resident inquiry request including the My Number to the city OS server 20.
[0047] When resident data is received as a response to the resident inquiry request, the recommendation unit 4213 transmits an insurance information request including the resident data to the insurance company server 50. The resident data includes family information, pet information, etc. When insurance information is received from the insurance company server 50 as a response to the insurance information request, the recommendation unit 4213 transmits the received insurance information to the user terminal 30.
[0048] The privilege distribution unit 4214 distributes privilege data to the user terminal 30. In this embodiment, the privilege distribution unit 4214 distributes the privilege data stored in the privilege DB 433 to the user terminal 30. The privilege distribution unit 4214 may distribute the privilege data in response to a distribution request from the user terminal 30, or may distribute the privilege data at any timing, such as once every two days.
[0049] (City OS Server) 6 is a diagram showing an example of the configuration of a city OS server according to an embodiment of the present invention. The city OS server 20 includes an input unit 210, a control unit 220, a storage unit 230, a communication interface 240, and a display unit 250.
[0050] The input unit 210 is configured to receive operations from a user of the city OS server 20, and can be realized by a keyboard, a mouse, a touch panel, or the like.
[0051] The control unit 220 includes an arithmetic processing unit 221 such as a CPU or MPU equivalent to a processor, and a memory 222 such as a RAM. The arithmetic processing unit 221 (processor) loads a program recorded in the storage unit 230 into the memory 222 and executes it based on various inputs, thereby achieving functions and processing described below in the arithmetic processing unit 221. The memory 222 functions as a work memory required for the arithmetic processing unit 221 (processor) to execute the program.
[0052] The storage unit 230 is configured with a storage device such as a hard disk, and records various programs required for executing processes in the control unit 220, data required for executing the various programs, etc. In this embodiment, it is preferable that the storage unit 230 has a resident DB21, a movement data DB231, a city data DB232, and a company data DB233.
[0053] As described above, the resident DB 21 stores information on people related to the city. In one embodiment, the resident DB 21 stores personal information, family information, pet information, health care information, etc. The personal information includes name, address, My Number, etc. The family information includes information on family members. The pet information includes information indicating whether or not a pet is owned. The health care information includes health care data collected from the user terminal 30.
[0054] Information regarding traffic and people flow is stored in the movement data DB 231. In one embodiment, the movement data DB 231 stores movement data collected from the user terminal 30.
[0055] The city data DB232 stores information about cities. The company data DB233 stores information about companies. While the resident DB21 stores information that identifies individuals, the city data DB232 and the company data DB233 store information that represents the characteristics of cities or companies. In this embodiment, the city data DB232 and the company data DB233 store risk-related information required for calculating insurance premiums for various insurances. In one embodiment, the company data DB stores company IDs, company names, risk-related information, etc.
[0056] The risk-related information may include any information that can be used to calculate insurance premiums for various types of insurance, such as the number of traffic accidents, the number of fires, population density, and natural disaster information.
[0057] The communication interface 240 is a hardware module that connects the city OS server 20 to the network N and communicates with other devices on the network N, including the application server 40 and the insurance company server 50.
[0058] The display unit 250 is configured to display various images processed under the control of the arithmetic processing unit 221, and can be realized by a display or the like.
[0059] Furthermore, as shown in FIG. 6, the calculation processing unit 221 includes, as functional units, an identity verification unit 2211, a receiving unit 2212, a resident inquiry unit 2213, and a risk inquiry unit 2214.
[0060] The identity confirmation unit 2211 performs identity confirmation processing in response to an identity confirmation request from the application server 40. As described above, in this embodiment, the identity confirmation request includes name, address, age, identity confirmation information, etc., and the identity confirmation information includes, for example, information that can be read from a My Number card. In this embodiment, if the identity confirmation based on the resident DB 21 is successful, the identity confirmation unit 2211 transmits a positive identity confirmation result including the My Number to the application server 40. On the other hand, if the identity confirmation is unsuccessful, the identity confirmation unit 2211 transmits a negative identity confirmation result to the application server 40.
[0061] The receiving unit 2212 receives personal data from the application server 40 and stores it in the storage unit 230. In this embodiment, when the receiving unit 2212 receives personal data including movement data from the application server 40, the receiving unit 2212 stores the personal data in the movement data DB 231. In addition, when the receiving unit 2212 receives personal data including health care data from the application server 40, the receiving unit 2212 stores the personal data in the resident DB 21.
[0062] The resident inquiry unit 2213 transmits resident data in response to a resident inquiry request from the application server 40. In this embodiment, the resident inquiry unit 2213 receives a resident inquiry request including the My Number, refers to the resident DB 21 based on the My Number, and acquires corresponding resident data. In one embodiment, the resident inquiry unit 2213 acquires resident data including family information and pet information from the resident DB 21 and transmits it to the application server 40.
[0063] The risk inquiry unit 2214 transmits risk-related data in response to a risk inquiry request from the insurance company server 50. In this embodiment, when the risk inquiry unit 2214 receives a risk inquiry request including a company ID from the insurance company server 50, it obtains risk-related data for the received company ID from the company data DB 233 and transmits it to the insurance company server 50. In addition, when the risk inquiry unit 2214 receives a risk inquiry request that does not include a company ID, it obtains risk-related data from the city data DB 232 and transmits it to the insurance company server 50.
[0064] (Insurance company server) 7 is a diagram showing an example of the configuration of an insurance company server according to an embodiment of the present invention. The insurance company server 50 includes an input unit 510, a control unit 520, a storage unit 530, a communication interface 540, and a display unit 550.
[0065] The input unit 510 is configured to receive operations from a user of the insurance company server 50, and can be realized by a keyboard, a mouse, a touch panel, or the like.
[0066] The control unit 520 includes an arithmetic processing unit 521 such as a CPU or MPU equivalent to a processor, and a memory 522 such as a RAM. The arithmetic processing unit 521 (processor) loads a program recorded in the storage unit 530 into the memory 522 and executes it based on various inputs, thereby achieving functions and processing described below in the arithmetic processing unit 521. The memory 222 functions as a work memory required for the arithmetic processing unit 521 (processor) to execute the program.
[0067] The storage unit 530 is configured with a storage device such as a hard disk, and records various programs necessary for executing processes in the control unit 520, data necessary for executing the various programs, etc. In this embodiment, it is preferable that the storage unit 530 has an insurance contract DB 51 and an insurance premium DB 531 that store information related to insurance contracts.
[0068] Insurance premiums for various insurances are stored in the insurance premium DB 531. In one embodiment, as shown in Fig. 8, insurance ID, company ID, insurance name, insurance details, insurance premium, type, conditions, etc. are stored in the insurance premium DB 531. Information used by the insurance determination unit 5213 described later is stored in the conditions.
[0069] The communication interface 540 is a hardware module for connecting the insurance company server 50 to the network N and communicating with other devices on the network N, including the city OS server 20 and the application server 40.
[0070] The display unit 550 is configured to display various images processed under the control of the arithmetic processing unit 521, and can be realized by a display or the like.
[0071] Furthermore, as shown in FIG. 7, the calculation processing unit 521 includes a contract processing unit 5211, a calculation unit 5212, and an insurance determination unit 5213 as functional units.
[0072] The contract processing unit 5211 performs contract processing in response to a contract request from the application server 40. In this embodiment, the contract processing unit 5211 receives a contract request including a name, an address, an age, payment information for the application, etc., and registers contract data in the insurance contract DB 51 based on the received information. When registration in the insurance contract DB 51 is completed, the contract processing unit 5211 transmits a positive contract result to the application server 40. In this embodiment, the contract processing unit 5211 transmits a positive contract result including an insurance ID for which the contract has been completed. On the other hand, if registration of the contract information fails, the contract processing unit 5211 transmits a negative contract result to the application server 40.
[0073] The calculation unit 5212 calculates the insurance premiums for various insurances. In this embodiment, the calculation unit 5212 requests risk-related data required for calculating the insurance premiums for various insurances from the city OS server 20. The calculation unit 5212 calculates the insurance premiums based on the acquired risk-related information. The calculation unit 5212 can calculate the insurance premiums at any timing, such as once a year.
[0074] In response to an insurance information request from the application server 40, the insurance determination unit 5213 transmits information on insurance that the user of the user terminal 30 can optionally subscribe to. In this embodiment, the insurance information request includes resident data, and the insurance determination unit 5213 determines insurance to propose to the user of the user terminal 30 based on the received resident data and the conditions in the insurance premium DB 531. The resident data includes family information, pet information, etc., and when the resident data matches the conditions in the insurance premium DB 531, the insurance determination unit 5213 may determine the matching insurance as the insurance to be proposed.
[0075] (User terminal) 9 is a diagram showing an example of the configuration of a user terminal according to an embodiment of the present invention. In this embodiment, a smartphone is assumed to be the user terminal 30, but any other mobile terminal can be used as appropriate.
[0076] The user terminal 30 includes an input unit 310 , a control unit 320 , a storage unit 330 , a communication interface 340 , and a display unit 350 .
[0077] The input unit 310 is configured to receive operations from the user of the user terminal 30, and can be realized by a keyboard, a mouse, a touch panel, or the like.
[0078] The control unit 320 includes an arithmetic processing unit 321 such as a CPU or MPU equivalent to a processor, and a memory 322 such as a RAM. The arithmetic processing unit 321 (processor) loads a program recorded in the storage unit 330 into the memory 322 and executes it based on various inputs, thereby realizing the functions and processing described below in the arithmetic processing unit 321. This program may be stored in a computer-readable non-transitory recording medium such as a CD-ROM, or distributed via a network and installed in the computer. The memory 322 functions as a work memory required for the arithmetic processing unit 321 (processor) to execute the program.
[0079] The storage unit 330 is configured with a storage device such as a hard disk, and records various programs required for executing processes in the control unit 320, data required for executing the various programs, etc. In this embodiment, it is preferable that the storage unit 330 has a movement data storage unit 331, a health care data storage unit 332, and a privilege data storage unit 333.
[0080] The movement data storage unit 331 stores a history of location information of the user terminal 30. In one embodiment, the movement data storage unit 331 stores date, time, latitude, longitude, and the like.
[0081] The health care data storage unit 332 stores health care information of the user of the user terminal 30. In one embodiment, the health care data storage unit 332 stores the date, the number of steps, the walking distance, and the like.
[0082] The privilege data storage unit 333 stores privilege information provided to a user who uses an insured service. In one embodiment, the privilege data storage unit 333 stores a privilege ID, privilege content, store used, usage period, etc. The privilege ID is information for uniquely identifying a privilege. The privilege content stores information indicating the content of the privilege. The usage store stores information indicating the store where the privilege can be used. The usage period stores information indicating the period during which the privilege can be used.
[0083] The communication interface 340 is a hardware module for connecting the user terminal 30 to the network N and for communicating with other devices on the network N, including the application server 40.
[0084] The display unit 350 is configured to display various images processed under the control of the arithmetic processing unit 321, and can be realized by a display or the like.
[0085] Furthermore, as shown in FIG. 9, the arithmetic processing unit 321 includes, as functional units, a screen control unit 3211, a registration request unit 3212, an acquisition unit 3213, a transmission unit 3214, a recommendation request unit 3215, and a privilege management unit 3216.
[0086] The screen control unit 3211 creates a corresponding screen in response to an input from the user or information received from the application server 40, and displays it on the display unit 350. Specifically, for example, the screen control unit 3211 creates a resident registration screen for requesting registration of a resident or the like, a recommendation screen for confirming optional insurance, a privilege screen for confirming privileges, etc., and displays them on the display unit 350.
[0087] The registration request unit 3212 sends a registration request to the application server 40. In the present embodiment, the registration request unit 3212 sends a registration request including name, address, age, personal identification information, payment information of the application, etc. to the application server 40.
[0088] The acquisition unit 3213 acquires personal data provided to the urban OS server 20. In the present embodiment, the acquisition unit 3213 acquires the position information of the user terminal 30 and stores it in the movement data storage unit 331. Further, the acquisition unit 3213 uses the outputs of the acceleration sensor and gyro sensor of the user terminal 30 to acquire the number of steps and walking distance of the user and stores them in the healthcare data storage unit 332.
[0089] The transmission unit 3214 transmits the personal data acquired by the acquisition unit 3213 to the application server 40. In the present embodiment, the transmission unit 3214 transmits the movement data in the movement data storage unit 331 and the healthcare data in the healthcare data storage unit 332 to the application server 40 together with the member ID. The transmission unit 3214 can transmit personal data at an arbitrary timing, such as at a predetermined time every day. The transmission unit 3214 may delete the transmitted data from the storage unit 330 or store information indicating that the data has been transmitted.
[0090] The recommendation request unit 3215 transmits a recommendation request requesting insurance information to the application server 40. In this embodiment, the recommendation request unit 3215 transmits to the application server 40 a recommendation request including a member ID.
[0091] The privilege management unit 3216 manages the privilege data storage unit 333. In this embodiment, the privilege management unit 3216 manages the privilege usage status and the privilege usage period. In one embodiment, the privilege management unit 3216 may transmit a distribution request to the application server 40.
[0092] <Operation> (Resident registration processing) A resident registration process according to an embodiment of the present invention will be described in detail with reference to Fig. 10 and Fig. 11. In this embodiment, it is assumed that user A, who is a resident of a smart city, performs resident registration. First, with reference to Fig. 10, a process up to transmitting a registration request for resident registration in the user terminal 30 will be described. Then, with reference to Fig. 11, a resident registration process in the application server 40 that has received the registration request from the user terminal 30 will be described.
[0093] In this embodiment, it is assumed that an insurance-included application is registered in the application DB 11 of the application sales management server 10 before the processing of Fig. 10 is started. In step S101, user A operates the user terminal 30 to access the application sales management server 10. In this embodiment, it is assumed that user A starts an application sales application provided by the application sales management server 10 and installed in the user terminal 30, thereby causing the user terminal 30 to access the application sales management server 10.
[0094] In step S102, the user terminal 30 transmits a request to display a list of applications to the application sales management server 10. In this embodiment, it is assumed that the user terminal 30 transmits the request to display a list of applications to the application sales management server 10 when User A selects a “Display list of applications” control on the screen displayed on the user terminal 30.
[0095] In step S103, the user terminal 30 displays a list screen of applications sent from the application sales management server 10. In step S104, the user terminal 30 transmits a download request for the insured app displayed on the application list screen. In this embodiment, it is assumed that User A selects the insured app on the screen displayed on the user terminal 30 and selects the “download” control, causing the user terminal 30 to transmit a download request for the insured app to the application sales management server 10.
[0096] In step S105 , the user terminal 30 downloads the insurance-included application distributed from the application sales management server 10 .
[0097] User A installs the downloaded insurance-included application in the user terminal 30, and in step S106, the user terminal 30 accesses the application server 40 by activating the insurance-included application.
[0098] In step S107, the screen control unit 3211 of the user terminal 30 displays a resident registration screen. In this embodiment, it is assumed that the screen control unit 3211 displays a resident registration screen including the designation of name, address, age, personal identification information, and payment information for the application. Here, it is assumed that the designation of personal identification information is performed by reading from the My Number card. The payment information for the application includes the payment method for the application fee, the payment time, the payment source information, etc. The payment method is information indicating credit card payment, account transfer, etc., the payment time is information indicating monthly or annual payment, and the payment source information is credit card information or account information specified according to the payment method.
[0099] In step S108, the registration request unit 3212 of the user terminal 30 sends a registration request to the application server 40. In this embodiment, it is assumed that the registration request unit 3212 sends a registration request to the application server 40 when user A makes a predetermined input on the resident registration screen and selects the "Send" control.
[0100] Subsequently, with reference to FIG. 11, the resident registration process of the application server 40 that has received the registration request from the user terminal 30 will be described.
[0101] In step S201, the registration request processing unit 4211 of the application server 40 receives a registration request from the user terminal 30. In this embodiment, the registration request processing unit 4211 receives a registration request including name, address, age, personal identification information, and payment information for the application.
[0102] In step S202, the registration request processing unit 4211 sends a personal identification request to the city OS server 20. In this embodiment, the registration request processing unit 4211 sends a personal identification request including name, address, age, and personal identification information to the city OS server 20.
[0103] In step S203, the registration request processing unit 4211 determines whether or not a positive identity verification result has been received as a response to the identity verification request. If a negative identity verification result has been received (step S203: No), in step S204, the registration request processing unit 4211 transmits information indicating that resident registration has failed to the user terminal 30.
[0104] On the other hand, if a positive identity verification result is received (step S203: Yes), in step S205, the registration request processing unit 4211 transmits a contract request to the insurance company server 50. Here, it is assumed that the registration request processing unit 4211 receives a positive identity verification result including the My Number, and transmits a contract request to the insurance company server 50. In this embodiment, the contract request includes name, address, age, which are examples of personal information, payment information for the application, insurance information, etc., and it is assumed that the registration request processing unit 4211 transmits a contract request including the insurance information "N-001, N-002, N-003" to the insurance company server 50.
[0105] In step S206, the registration request processing unit 4211 determines whether or not a positive contract result has been received as a response to the contract request. If a negative contract result has been received (step S206: No), the process proceeds to step S204, and the registration request processing unit 4211 transmits information indicating that the resident registration has failed to the user terminal 30.
[0106] On the other hand, if a positive contract result is received (step S206: Yes), in step S207, the registration request processing unit 4211 issues a member ID for the user to the member DB 431 and registers the record. Here, the registration request processing unit 4211 receives a positive contract result including the insurance IDs "N-001, N-002, N-003" for which the contract has been completed, issues a member ID for the user, and registers the record. When registering, the registration request processing unit 4211 also registers the My Number received from the city OS server 20 in step S203 and the insurance ID received from the insurance company server 50 in step S206.
[0107] In step S208, the registration request processing unit 4211 notifies the user terminal 30 of the completion of the registration request. In this embodiment, the registration request processing unit 4211 notifies the user terminal 30 of the completion of the registration request together with the member ID "0001".
[0108] In this embodiment, an example in which user A, a resident of a smart city, performs resident registration has been described, but employees of a company located in the smart city can also perform resident registration in the same way. When employee B performs resident registration, a positive identity verification result including a company ID and an employee ID may be received in step S203 instead of a positive identity verification result including a My Number. In this way, the registration request processing unit 4211 can obtain insurance information of the contract target from the insurance DB 432 based on the received company ID, and transmit a contract request to the insurance company server 50 in step S205.
[0109] (Data provision processing) Next, the data provision process according to one embodiment of the present invention will be described in detail with reference to Fig. 12. In this embodiment, the acquisition unit 3213 of the user terminal 30 for which resident registration has been completed acquires location information of the user terminal 30 at predetermined timings such as every 5 minutes and stores the information in the movement data storage unit 331. The acquisition unit 3213 also acquires the number of steps and walking distance of the user using outputs from an acceleration sensor, a gyro sensor, and the like of the user terminal 30 and stores the information in the health care data storage unit 332.
[0110] In step S301, the transmission unit 3214 of the user terminal 30 transmits the personal data acquired by the acquisition unit 3213 to the application server 40. In this embodiment, the transmission unit 3214 transmits the movement data in the movement data storage unit 331 and the health care data in the health care data storage unit 332 to the application server 40 together with the member ID.
[0111] In step S302, the transfer unit 4212 of the application server 40 includes the My Number in the personal data, and in step S303, transmits the personal data to the city OS server 20.
[0112] In step S304, the receiving unit 2212 of the city OS server 20 receives the personal data from the application server 40 and stores it in the memory unit 230. In this embodiment, when the receiving unit 2212 receives the personal data including movement data from the application server 40, it stores it in the movement data DB 231. In addition, when the receiving unit 2212 receives the personal data including healthcare data from the application server 40, it stores it in the resident DB 21.
[0113] (Recommendation processing) The recommendation process according to one embodiment of the present invention will be described in detail with reference to Fig. 13. In this embodiment, an example of recommending optimal insurance to a user A who has completed resident registration will be described.
[0114] In step S401, the recommendation request unit 3215 of the user terminal 30 transmits a recommendation request requesting insurance information to the application server 40. In this embodiment, it is assumed that the user terminal 30 including the member ID transmits a recommendation request to the application server 40 when User A selects the “Consider additional insurance” control on the screen displayed on the user terminal 30.
[0115] In step S402, the recommendation unit 4213 of the application server 40 acquires the My Number from the member DB 431 based on the member ID included in the recommendation request. Then, in step S403, the recommendation unit 4213 transmits a resident inquiry request including the My Number to the city OS server 20.
[0116] In step S404, the resident inquiry unit 2213 of the city OS server 20 refers to the resident DB 21 based on the My Number included in the resident inquiry request, acquires the corresponding resident data, and transmits it to the application server 40. In this embodiment, it is assumed that the resident inquiry unit 2213 acquires resident data including family information "children (ages 10, 8)" and pet information "has pet" from the resident DB 21 and transmits it to the application server 40.
[0117] In step S405, the recommendation unit 4213 transmits an insurance information request including the resident data received from the city OS server 20 to the insurance company server 50. In step S406, the insurance determination unit 5213 of the insurance company server 50 determines the insurance to be proposed to the user of the user terminal 30 based on the resident data and the conditions in the insurance premium DB 531. Here, it is assumed that the insurance determination unit 5213 has determined pet insurance and bicycle insurance as the insurance to be proposed to the user.
[0118] In step S407, the recommendation unit 4213 transmits the insurance information received from the insurance company server 50 to the user terminal 30.
[0119] In step S408, the screen control unit 3211 of the user terminal 30 displays a recommendation screen based on the received insurance information.
[0120] (Insurance premium calculation process) An insurance premium calculation process according to one embodiment of the present invention will be described in detail with reference to Fig. 14. In this embodiment, the process of Fig. 14 is started in response to an instruction to calculate an insurance premium from an administrator of the insurance company server 50.
[0121] In step S501, the calculation unit 5212 of the insurance company server 50 requests risk-related data necessary for calculating insurance premiums for various insurances from the city OS server 20. Here, it is assumed that the calculation unit 5212 has sent a risk inquiry request that does not include a company ID to the city OS server 20.
[0122] In step S502, the risk inquiry unit 2214 of the city OS server 20 acquires risk-related data based on the risk inquiry request. In this embodiment, when the risk inquiry unit 2214 receives a risk inquiry request including a company ID from the insurance company server 50, it acquires risk-related data for the received company ID from the company data DB 233. In addition, when the risk inquiry unit 2214 receives a risk inquiry request that does not include a company ID, it acquires risk-related data from the city data DB 232. Here, it is assumed that the risk inquiry unit 2214 acquires risk-related data from the city data DB 232.
[0123] In step S503, the risk inquiry unit 2214 transmits the acquired risk-related data to the insurance company server 50.
[0124] In step S504, the calculation unit 5212 calculates the insurance premium based on the received risk-related information.
[0125] As described above, according to this embodiment, the system 1 can support people related to the smart city to automatically purchase the necessary insurance equally. Providing comprehensive compensation to people related to the smart city can ensure a safe and secure life. In addition, the functions of the transmission unit 3214 of the user terminal 30 and the transfer unit 4212 of the application server 40 enable the city OS server 20 to effectively collect personal data and contribute to the utilization of city data.
[0126] By cooperating in providing personal data, the user of the user terminal 30 can receive benefits such as the provision of special data. Furthermore, the recommendation unit 4213 of the application server 40 and the resident inquiry unit 2213 of the city OS server 20 work together to provide the user of the user terminal 30 with information on additional insurance suitable for the user in addition to the insurance for the automatic contract.
[0127] Furthermore, by cooperation between the calculation unit 5212 of the insurance company server 50 and the risk inquiry unit 2214 of the city OS server 20, the insurance company can calculate more reasonable insurance premiums by utilizing various risk-related data of the city that is the subject of compensation. By reflecting various risk-related data of the city in the insurance premiums, it is possible to encourage behavioral changes of people related to the smart city.
[0128] In this embodiment, an example has been described in which the city OS server 20 performs identity verification processing based on the resident DB 21, enabling people with addresses in a smart city and employees of companies located in the city to automatically sign up for insurance that is equally necessary for all residents of the smart city. However, in another embodiment, a specified company server may perform identity verification processing based on the employee DB, enabling employees of a specified company to automatically sign up for insurance that is equally necessary for all employees of that company.
[0129] <Another embodiment> In the above embodiment, an example has been described in which the registration request processing unit 4211 of the application server 40 notifies the user terminal 30 of the completion of the registration request after the identity verification processing in the city OS server 20 and the insurance contract processing in the insurance company server 50. On the other hand, in another embodiment, the registration request processing unit 4211 of the application server 40 may notify the user terminal 30 of the completion of the registration request after the identity verification processing in the city OS server 20, and send a contract request to the insurance company server 50 immediately after this notification processing or in parallel with this notification processing. All modes in which the identity verification processing in the city OS server 20 and the insurance contract processing in the insurance company server 50 are performed together are included in the scope of the present invention. [Explanation of symbols]
[0130] 10… Application sales management server, 11… Application DB, 20… Urban OS server (first information processing server), 210… Input unit, 220… Control unit, 221… Arithmetic processing unit, 222… Memory, 2211… Identity verification unit, 2212… Receiver, 2213… Resident inquiry unit, 2214… Risk inquiry unit, 230… Storage unit, 21… Resident etc. DB, 231… Movement data DB, 232… Urban data DB, 233… Enterprise data DB, 240… Communication interface, 250… Display unit, 30… User terminal, 310… Input unit, 320… Control unit, 321… Arithmetic processing unit, 322… Memory, 3211… Screen control unit, 3212… Registration request unit, 3213… Acquisition unit, 3214… Transmitter, 3215… Recommendation request unit, 3216… Privilege management unit, 330… Storage unit, 331… Movement data storage unit, 332… Healthcare data storage unit, 333… Privilege data storage unit, 340… Communication interface, 350… Display unit, 40… Application server (information processing system), 410… Input unit, 420… Control unit, 421… Arithmetic processing unit, 422… Memory, 4211… Registration request processing unit (processing unit), 4212… Transfer unit, 4213… Recommendation unit, 4214… Privilege distribution unit (distribution unit), 430… Storage unit, 431… Member DB, 432… Insurance DB, 433… Specific DB, 440… Communication interface, 450… Display unit, 50… Insurance company server (second information processing server), 510… Input unit, 520… Control unit, 521… Arithmetic processing unit, 522… Memory, 5211… Contract processing unit, 5212… Calculation unit, 5213… Insurance decision unit, 530… Storage unit, 51… Insurance contract DB, 531… Insurance premium DB, 540… Communication interface, 550… Display unit, N… Network
Claims
1. An information processing system including a processing unit for processing a resident registration request from a user terminal, The processing unit includes: Transmitting an identity verification request to a first information processing server based on the personal information and identity verification information included in the request for resident registration; When a positive identity verification result is received in response to the identity verification request, a contract request including the personal information and information on the insurance to be contracted is transmitted to a second information processing server; When a positive contract result is received as a response to the contract request, notify the user terminal of the completion of resident registration; Information processing system.
2. The information processing system according to claim 1 , further comprising a transfer unit that transmits personal data collected by said user terminal to said first information processing server.
3. The information processing system according to claim 1 , wherein the first information processing server processes the request for identity verification based on a database in which information on people associated with a specific region is registered.
4. The information processing system according to claim 1 , wherein the first information processing server processes the request for identity verification based on a database in which information on people associated with a specific company is registered.
5. The information processing system according to claim 1 , further comprising a recommendation unit that transmits information on insurance to be proposed to a user who uses the user terminal.
6. The information processing system according to claim 1 , further comprising a distribution unit that distributes bonus data to the user terminal.
7. The information processing system according to claim 1 , wherein the second information processing server requests risk-related data from the first information processing server, and calculates a premium for the insurance based on the acquired risk-related data.
8. The computer receiving a request for resident registration from a user terminal; Transmitting an identity verification request to a first information processing server based on personal information and identity verification information included in the request for resident registration; When a positive identity verification result is received as a response to the identity verification request, a contract request including the personal information and information on the insurance to be contracted is transmitted to a second information processing server; When a positive contract result is received as a response to the contract request, notifying the user terminal of the completion of resident registration. The method includes:
9. On one or more computers, A process of receiving a request for resident registration from a user terminal; A process of transmitting an identity verification request to a first information processing server based on personal information and identity verification information included in the request for resident registration; When a positive identity verification result is received as a response to the identity verification request, a process of transmitting a contract request including the personal information and information on the insurance to be contracted to a second information processing server; When a positive contract result is received as a response to the contract request, a process of notifying the user terminal of completion of resident registration; A program that executes the following.
10. A second information processing server connected to the first information processing server via a communication network, a calculation unit that requests risk-related data from the first information processing server and calculates an insurance premium based on the acquired risk-related data; The insurance is for persons related to a specific region or company, The risk-related data is information regarding the particular region or company; A second information processing server.