Information processing system, information processing method and program

Abstract

To suppress decrease in profit rate of a service provider due to intervention of a service mediation system.SOLUTION: An information processing method includes executing: by a computer, acquiring plan data related to a funeral plan; acquiring current environmental data related to the funeral plan; acquiring a predicted amount of money of the funeral plan by inputting at least a portion of the plan data and the environmental data to a fee prediction model; and outputting the predicted amount of money to a funeral company that provides the funeral plan.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present disclosure relates to an information processing system, an information processing method, and a program. [Background technology]

[0002] In the past, it was common for the chief mourner to request a funeral from a nearby funeral parlor through the intermediation of a hospital, police, etc. In recent years, systems have been proposed that act as an intermediary between the chief mourner and the funeral parlor via a network such as the Internet, as in Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-271876 Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, those requesting funerals are not familiar with funeral services in their daily lives, but when the deceased passes away, they are suddenly forced to take charge of the funeral as the chief mourner. The chief mourner must decide many matters in a short period of time, from the details of the funeral to contacting the relevant parties, and carefully considering the options and fees for each matter often poses great difficulties and stress. Therefore, it is desirable for funeral service intermediaries to provide an improved system that can support such clients.

[0005] The present disclosure aims to provide an improved information processing system, information processing method, and program for funeral-related intermediary services. [Means for solving the problem]

[0006] An information processing system according to one aspect of the present disclosure includes a plan data acquisition unit configured to acquire plan data relating to a funeral plan, an environmental data acquisition unit configured to acquire current environmental data related to the funeral plan, a fee acquisition unit configured to acquire a predicted amount for the funeral plan by inputting the plan data and at least a portion of the environmental data into a fee prediction model, and a fee output unit configured to output the predicted amount to a funeral home that provides the funeral plan.

[0007] An information processing method according to one aspect of the present disclosure includes a computer executing the following steps: acquiring plan data relating to a funeral plan; acquiring current environmental data related to the funeral plan; obtaining a predicted amount for the funeral plan by inputting the plan data and at least a portion of the environmental data into a price prediction model; and outputting the predicted amount to a funeral home that provides the funeral plan.

[0008] A program according to one aspect of the present disclosure causes a computer to obtain plan data relating to a funeral plan, obtain current environmental data related to the funeral plan, obtain a predicted amount for the funeral plan by inputting the plan data and at least a portion of the environmental data into a price prediction model, and output the predicted amount to a funeral home that provides the funeral plan.

[0009] A program according to one aspect of the present disclosure causes a computer to accept input of plan data relating to a funeral plan from a funeral home, transmit the plan data to another computer, and receive data from the other computer indicating the predicted amount of the funeral plan obtained by inputting the plan data into a fee prediction model. [Brief explanation of the drawings]

[0010] [Figure 1]FIG. 1 is a schematic diagram illustrating the configuration of an information processing system. [Figure 2] FIG. 2 is a block diagram illustrating an example of the electrical configuration of the client terminal. [Figure 3] FIG. 3 is a block diagram illustrating the electrical configuration of the funeral home terminal. [Figure 4] FIG. 4 is a block diagram illustrating an example of the electrical configuration of the server. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of requester data. [Figure 6] FIG. 6 is a diagram illustrating an example of the configuration of plan data. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of the environment data. [Figure 8] FIG. 8 is a flow diagram illustrating the flow of the plan display process. [Figure 9] FIG. 9 is a flow diagram illustrating an example of the flow of negotiation processing. [Figure 10] FIG. 10 is a flow diagram illustrating the flow of the payment process. [Figure 11] FIG. 11 is a flow diagram illustrating the flow of the fee proposal process. [Figure 12] FIG. 12 is a diagram illustrating an example of a plan display screen. [Figure 13] FIG. 13 is a diagram illustrating an example of a client side negotiation screen. [Figure 14] FIG. 14 is a diagram illustrating an example of the funeral home side negotiation screen. [Figure 15] FIG. 15 is a diagram illustrating a payment screen before payment. [Figure 16] FIG. 16 is a diagram illustrating a payment screen after payment. [Figure 17] FIG. 17 is a diagram illustrating an example of the plan input screen. [Figure 18] FIG. 18 is a diagram illustrating an example of a fee proposal screen before the fee change. [Figure 19] FIG. 19 is a diagram illustrating an example of the fee proposal screen after the fee change. [Figure 20] FIG. 20 is a diagram illustrating a plan display screen after the fee change. DETAILED DESCRIPTION OF THE INVENTION

[0011] Examples of the information processing system, information processing method, and program of the present disclosure will be described with reference to Figures 1 to 20. The information processing system of the present disclosure is configured to provide an intermediary service that mediates contracts related to the provision of funeral services. The present invention is not limited to these examples, but is defined by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0012] [Overall system configuration] As shown in FIG. 1, the information processing system 10 comprises one or more funeral home terminals 30 and one or more servers 40. Below, an example will be described in which the information processing system 10 comprises one funeral home terminal 30 and one server 40. The funeral home terminal 30 is a terminal used by a provider of funeral services (for example, a funeral home or an employee of the funeral home; hereinafter simply referred to as the "provider"). The funeral home terminal 30 is located, for example, in the funeral home's store.

[0013] The information processing system 10 may include one or more client terminals 20. The client terminal 20 is a terminal used by a client who requests funeral services (hereinafter simply referred to as a "client"). The client terminal 20 is capable of communicating with the server 40 via the network NT. Both the funeral service provider and the client are users of the intermediary service.

[0014] The funeral home terminal 30 can communicate with the server 40 via the network NT. The client terminal 20 and the funeral home terminal 30 can communicate via the network NT and the server 40. The network NT includes, for example, the Internet, a wide area network (WAN), a local area network (LAN), a provider terminal, a wireless communication network, a wireless base station, and a dedicated line, but is not limited to these.

[0015] [Requester device configuration] The requester terminal 20 is, for example, a smartphone. The requester terminal 20 may be, for example, a mobile terminal device such as a feature phone, a PDA (Personal Digital Assistant), a wearable device, a notebook computer, or a tablet computer. The requester terminal 20 may be, for example, a fixed terminal device such as a desktop computer or a workstation.

[0016] 2, the requester terminal 20 includes one or more processors 21, one or more memories 22, one or more communication interfaces 23, one or more touch sensors 24, one or more displays 25, and one or more GNSS receivers 26. Below, an example will be described in which the requester terminal 20 includes one each of the processor 21, memory 22, communication interface 23, touch sensor 24, display 25, and GNSS receiver 26.

[0017] The processor 21 executes various processes based on programs. The programs are stored in the memory 22. The processor 21 is, for example, a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor unit (MPU), a field-programmable gate array (FPGA), or other arithmetic device. The processor 21 is, for example, a processing circuit configured to execute various software processes. The processing circuit may include a dedicated hardware circuit (e.g., an ASIC) that processes at least a part of the software processes. In other words, the software processes may be executed by a processing circuitry that includes at least one of one or more software processing circuits and one or more dedicated hardware circuits.

[0018] The memory 22 may include storage that permanently stores data including programs. The storage may be, for example, a read-only memory (ROM), a hard disk drive, a flash memory, or other non-volatile storage device. The storage may also be a removable storage device such as a memory card. The memory 22 may also include a random access memory (RAM) or other volatile memory that temporarily stores programs and data read from the storage.

[0019] The memory 22 stores, for example, an OS (Operating System), a client-side funeral app program 22a, and client data. The client-side funeral app program 22a includes a plurality of instructions for executing the client-side funeral app. The client-side funeral app is provided, for example, from the server 40 or another application server via the network NT to realize the function of requesting a funeral. The client data includes information about the client requesting the provision of funeral services. The client data may include, for example, authentication data for authenticating the client. The authentication data includes, for example, a client ID and a password. The client ID is an identifier for identifying the client.

[0020] The communication interface 23 includes a device for connecting to the network NT via a wired or wireless connection. The communication interface 23 realizes a function for communicating with other devices via the network NT. The communication interface 23 is, for example, Wi-Fi (registered trademark), Bluetooth (registered trademark), NFC (Near Field Communication), or another wireless communication interface. The communication interface 23 may also be, for example, a LAN (Local Area Network) or another wired communication interface.

[0021] The touch sensor 24 is, for example, a capacitive touch sensor, a resistive touch sensor, an ultrasonic touch sensor, or another type of touch sensor. The detection range of the touch sensor 24 is a part or all of the display surface of the display 25. The touch sensor 24 is an input device capable of detecting inputs by tapping, swiping, dragging, flicking, and other modes. The display 25 is a transmissive or non-transmissive display device. The display 25 is, for example, a liquid crystal monitor, an organic electroluminescence (EL) monitor, or another type of display device. The display 25 is capable of displaying various images.

[0022] The requester terminal 20 may include other input devices in addition to or instead of the touch sensor 24. Examples of other input devices include a controller, a motion sensor, a distance measurement sensor, a microphone, and a camera. The controller has one or more operation components. Examples of the operation components include a button, a key, a switch, a handle, a bar, a touchpad, or a stick. Examples of the motion sensor include an acceleration sensor and an angular velocity sensor. The requester terminal 20 may include other output devices in addition to or instead of the display 25. Examples of the other output devices may be a sound output device that outputs sound.

[0023] The GNSS receiver 26 acquires location information regarding the current location of the requester terminal 20. The GNSS receiver 26 is, for example, a GPS receiver, a GLONASS receiver, a Galileo receiver, a BDS receiver, or a receiver of other satellite signals. The GNSS receiver 26 can acquire location information regarding the current location coordinates of the terminal 20 from positioning satellites. The location coordinates are, for example, latitude and longitude coordinate values.

[0024] [Configuration of funeral home terminal] The funeral home terminal 30 is, for example, a notebook computer. The funeral home terminal 30 may be, for example, a mobile terminal such as a smartphone, feature phone, PDA, wearable device, or tablet computer. The funeral home terminal 30 may be, for example, a fixed terminal such as a desktop computer or workstation.

[0025] 3, the funeral home terminal 30 includes one or more processors 31, one or more memories 32, one or more communication interfaces 33, one or more keyboards 34, and one or more displays 35. Below, an example will be described in which the funeral home terminal 30 includes one each of the processor 31, memory 32, communication interface 33, keyboard 34, and display 35.

[0026] The processor 31 executes various processes based on programs. The programs are stored in the memory 32. The processor 31 is, for example, a CPU, a GPU, an MPU, an FPGA, or another computing device. The memory 32 may include storage that permanently stores data including the programs. The memory 32 may also include RAM or other volatile memory that temporarily stores the programs and data.

[0027] The memory 32 stores, for example, an OS, a funeral home funeral application program 32a, and corporate data. The funeral home funeral application program 32a includes a plurality of instructions for executing the funeral home funeral application. The funeral home funeral application is provided, for example, from the server 40 or another application server via the network NT to realize the function of accepting funeral orders. The corporate data includes information about the funeral home. The corporate data may include, for example, a corporate ID. The corporate ID is an identifier for identifying the funeral home.

[0028] The communication interface 33 includes a device for connecting to the network NT via a wired or wireless connection. The communication interface 33 realizes a function for communicating with other devices via the network NT. The communication interface 33 is, for example, a Wi-Fi, Bluetooth, NFC, or other wireless communication interface. The communication interface 33 may also be, for example, a LAN, or other wired communication interface.

[0029] The keyboard 34 is an input device that can input character information. The display 35 is a transmissive or non-transmissive display device. The display 35 is, for example, a liquid crystal monitor, an organic EL monitor, or another display device. The display 35 can display various images.

[0030] The funeral home terminal 30 may be provided with other input devices in addition to or instead of the keyboard 34. Examples of other input devices include a controller, a motion sensor, a distance measurement sensor, a microphone, a camera, a mouse, and a touch sensor. The funeral home terminal 30 may be provided with other output devices in addition to or instead of the display 35. Examples of other output devices may be sound output devices that output sound.

[0031] [Server Configuration] 4, the server 40 includes one or more processors 41, one or more memories 42, and a communication interface 43. The following description will be given using an example in which the server 40 includes one processor 41, one memory 42, and one communication interface 43. The server 40 may be a general-purpose computer such as a workstation or a desktop computer.

[0032] The processor 41 executes various processes based on programs. The programs are stored in the memory 42. The processor 41 is, for example, a CPU, a GPU, an MPU, an FPGA, or another computing device. The memory 42 may include storage that permanently stores data including the programs. The memory 42 may also include RAM or other volatile memory that temporarily stores the programs and data.

[0033] The communication interface 43 includes a device for connecting to the network NT via a wired or wireless connection. The communication interface 43 realizes a function for communicating with other devices via the network NT. The server 40 can communicate with each of the client terminal 20 and the funeral home terminal 30 via the network NT via the communication interface 43. The communication interface 43 is, for example, a LAN or other wired communication interface. The communication interface 43 may also be, for example, Wi-Fi, Bluetooth, NFC, or other wireless communication interface.

[0034] The server 40 may include a keyboard 44 and a display 45. The keyboard 44 is an example of an input device. The server 40 may include other input devices in addition to or instead of the keyboard 44. The other input devices may include, for example, a controller, a motion sensor, a distance measurement sensor, a microphone, a camera, a mouse, or a touch sensor. The display 45 is an example of an output device. The server 40 may include other output devices in addition to or instead of the display 45. The other output devices may include, for example, a projector or a speaker that outputs audio. Such input devices and output devices may be external devices separate from the main body of the server 40.

[0035] The memory 42 stores, for example, an OS, an intermediary program 42a, a fee proposal program 42b, a client database 42c, a plan database 42d, and an environment database 42e. The memory 42 may store at least one of a fee prediction model 46 and a plan recommendation model 47. The fee prediction model 46 and the plan recommendation model 47 may be trained machine learning models. At least one of the databases 42c, 42d, and 42e, the fee prediction model 46, and the plan recommendation model 47 may be stored in the storage of one or more computers or servers other than the server 40.

[0036] The intermediary program 42a includes multiple instructions for implementing the function of acting as an intermediary between the client and the funeral home. The fee proposal program 42b includes multiple instructions for implementing the function of proposing the fees for a funeral (hereinafter referred to as "funeral fees") according to one or more funeral plans registered in the plan database 42d.

[0037] The requester database 42c stores requester data relating to requesters. As shown in FIG. 5, the requester database 42c stores, for example, a requester ID, requester attribute data, and other data related to the requester. The requester attribute data and other data related to the requester are managed in association with the requester ID. The requester attribute data and other data related to the requester correspond to each of a plurality of requesters. The requester attribute data is information indicating the attributes of the requester. The attributes of the requester are classified based on information such as the requester's age, sex, address, occupation, place of work, and estimated annual income.

[0038] The client database 42c may share some or all of its data with user databases of other services that share users with the intermediation service of the present disclosure. The other services may be, for example, but are not limited to, e-commerce sites, travel service sites, store or service membership programs, point programs, or electronic payment services. By using data from such other services, even if a client is using the intermediation service for the first time, various attribute data can be used in the intermediation service while eliminating the need for the client to input data themselves.

[0039] The plan database 42d stores plan data relating to funeral plans. As shown in Figure 6, the plan database 42d stores, for example, a corporation ID, a plan ID, plan content data, scope data, fee data, supply and demand data, and other data related to the funeral home. The plan ID is managed in association with the corporation ID. The plan ID is an identifier for identifying the funeral plan.

[0040] The plan details data, range data, fee data, supply and demand data, and other data related to the funeral home are managed in association with the plan ID. The plan details data, range data, fee data, supply and demand data, and other data related to the funeral home correspond to each of the multiple funeral plans.

[0041] The plan content data includes information indicating the content of the corresponding funeral plan. The range data is information indicating the area within which funeral services according to the corresponding funeral plan can be provided (hereinafter referred to as the service area). The service area is determined arbitrarily by the funeral home. The service area is, for example, a predetermined area centered on the location of the funeral home. The service area may also be any area determined by the funeral home. Areas are classified, for example, by prefecture, region, city, town, and village. The fee data is information indicating the funeral fee (set fee) for the corresponding funeral plan. The supply and demand data includes information regarding the demand and supply of funerals according to the corresponding funeral plan.

[0042] The environment database 42e stores environmental data relating to the environment in which funeral services are provided (hereinafter referred to as "funeral environment"). As shown in FIG. 7, the environmental database 42e stores, for example, area data, date data, congestion data, and other data related to the funeral environment. The area data includes information for identifying the area. The congestion data and other data related to the funeral environment are managed in association with the area data. The congestion data and other data related to the funeral environment correspond separately to multiple areas. The congestion data includes information indicating the congestion status of each area. The information indicating the congestion status includes, for example, information indicating the congestion status of crematoriums in each area and the congestion status of funeral homes in each area. The date data includes information regarding the current date and the date on which funeral services will be provided. The date data includes data indicating the six days of the week, the seven days of the week, and public holidays.

[0043] The price prediction model 46 may include, for example, a machine learning model for predicting demand for funeral services, or a reinforcement learning model for maximizing rewards (e.g., profits or sales). The demand prediction model for predicting demand may use, for example, a regression model or other model to output an optimal price based on the demand forecast as a prediction result. The reinforcement learning model may use, for example, a bandit algorithm or other algorithm to output a price for maximizing rewards (profits or sales) as a prediction result.

[0044] The plan recommendation model 47 may be, for example, a learning model that implements collaborative filtering or content-based filtering, or may be a learning model that uses other algorithms. The plan recommendation model 47 is configured to input client data of a client and output, as a prediction result, one or more funeral plans that are predicted to be recommended to the client from among multiple funeral plans.

[0045] The plan recommendation model 47 may output one or more funeral plans as prediction results, along with a recommendation level or recommendation ranking for each funeral plan. The recommendation level may be, for example, the degree of similarity between one or more attributes related to the client or funeral environment calculated by the prediction calculation. The recommendation ranking may be determined based on the recommendation level.

[0046] In other words, clients with similar attributes (e.g., age or annual income) or clients in similar environments (e.g., the same region) may have similar funeral plan preferences. Therefore, by using a learning model to predict attributes correlated with funeral plan preferences based on past data, it becomes possible to recommend more appropriate funeral plans even to new clients.

[0047] At least some of the past client data, plan data, and environmental data may be used to generate (e.g., train, build, or validate) the fare prediction model 46 and the plan recommendation model 47. These data may be obtained from databases 42c, 42d, and 42e. Various parameters of the fare prediction model 46 may be updated as needed or periodically as the client data, plan data, and environmental data are updated.

[0048] The fee prediction model 46 and the plan recommendation model 47 may be configured to output a prediction result by combining multiple prediction results from multiple learning models or other methods (e.g., rule-based prediction methods based on past data). The prediction method to be adopted may also be changed depending on the input data. For example, if there is little data on which to base the prediction due to conditions such as time, region, or client, the prediction accuracy may decrease. Therefore, a certain prediction method may be adopted under conditions in which the prediction accuracy of that method is higher than that of other prediction methods.

[0049] [Funeral app overview] The funeral app is used by the client or the provider. Funeral apps include a client-side funeral app used by the client and a funeral home-side funeral app used by the provider. Note that the funeral app according to the present disclosure may refer to a mobile application that can be run on a device such as a smartphone, or may refer to an application that can be displayed on a web browser running on a device such as a smartphone or desktop.

[0050] The client-side funeral app according to the present disclosure realizes a function of proposing a funeral plan to the client based on the client's location information and client data managed in the client database 42c. The client-side funeral app may also provide a forum for business negotiation between the client and a funeral parlor that offers the funeral plan selected by the client. For example, the client-side funeral app may provide a forum for business negotiation between the funeral parlor and the client by providing a chat room in which the funeral parlor and the client can participate.

[0051] The client-side funeral app may further include a function for settling the funeral costs of the funeral plan selected by the client. Here, the "payment" performed by the client-side funeral app is an electronic payment. The electronic payment is performed using, for example, electronic currency or a credit card. The electronic currency may be, for example, electronic money, digital currency, virtual currency, coupons, or points. By using the client-side funeral app, the client can receive funeral services based on a funeral plan that is suitable for them and has an appropriate price.

[0052] The funeral home app according to the present disclosure implements a function for registering funeral plans in the plan database 42d. The funeral home app may provide a forum for business negotiations between the funeral home and a client who selects a funeral plan offered by the funeral home. The funeral home app may provide a forum for business negotiations between the client and the funeral home, for example, by providing a chat room in which the client and the funeral home can participate.

[0053] The funeral home app may further include a function for billing the client for the funeral fee for the funeral plan selected by the client. The funeral home app may further include a function for proposing changes to the funeral fee. The funeral home app may be configured to propose changes to the funeral fee for each funeral plan based on, for example, the plan data managed by the plan database 42d and the environmental data managed by the environmental database 42e.

[0054] [Screen display overview for each device] As the client-side funeral app is executed, various screens are displayed on the display 25 of the client terminal 20. The various screens include, for example, a plan display screen, a client-side negotiation screen, and a payment screen.

[0055] The plan display screen is the initial screen when the client's funeral app is launched. The plan display screen displays one or more funeral plans. Each funeral plan displayed on the plan display screen includes information indicating the contents of that plan. The client can select their preferred funeral plan from the one or more funeral plans displayed on the plan display screen.

[0056] The client-side negotiation screen is displayed when the client selects a funeral plan. The client-side negotiation screen is a screen for providing a forum for negotiation between the client and the funeral home that offers the funeral plan selected by the client. The client-side negotiation screen may be, for example, a chat room in which the client and the funeral home that offers the funeral plan selected by the client participate. The client may be able to customize the funeral plan by negotiating with the funeral home.

[0057] The payment screen is displayed when the funeral home bills for the funeral fee. The payment screen displays the funeral fee for the funeral plan decided upon through negotiation. The client can pay the funeral fee through the payment screen.

[0058] As the funeral home application is executed, various screens are displayed on the display 35 of the funeral home terminal 30. The various display screens include, for example, an initial screen, a plan input screen, a funeral home negotiation screen, and a fee update screen.

[0059] The initial screen is the initial screen displayed when the funeral home funeral app is launched. On the initial screen, a new operation can be performed to register a new funeral plan in the plan database 42d. On the initial screen, an update operation can be performed to update the contents of a funeral plan already registered in the plan database 42d. When the provider performs a new operation or an update operation via the initial screen, the plan input screen is displayed.

[0060] The plan entry screen displays the details of a new funeral plan or an existing funeral plan. The plan entry screen allows the provider to register or update a funeral plan with any content.

[0061] The funeral home negotiation screen is displayed when the client selects a funeral plan offered by the funeral home. A separate funeral home negotiation screen is displayed for each client. In other words, multiple funeral home negotiation screens can be displayed simultaneously. Each funeral home negotiation screen may be, for example, a chat room in which the funeral home and one client who selected a funeral plan offered by the funeral home participate. The provider can request the funeral fee for the funeral plan decided upon through negotiation via the funeral home negotiation screen.

[0062] The fee update screen is displayed when the funeral home terminal 30 receives fee data sent from the server 40. The fee data includes information output by the server 40 indicating the estimated amount of the funeral plan. The estimated amount of the funeral plan can be said to be the funeral fee that the server 40 predicts to be appropriate. The update screen displays the estimated amount indicated by the fee data sent by the server 40. The provider can update the funeral fee of the funeral plan to the estimated amount predicted by the server 40 via the update screen.

[0063] [Outline of the process performed by the funeral app] The processing performed by the funeral app may include a funeral plan proposal process, a business negotiation process, a payment process, and a funeral fee proposal process. The funeral plan proposal process is executed by the client's funeral app. The business negotiation process and the payment process are executed by the client's funeral app and the funeral home's funeral app. The funeral fee proposal process is executed by the funeral home's funeral app.

[0064] The funeral plan proposal process realizes the function of proposing a funeral plan to the client. The business negotiation process provides a forum for business negotiations between the client and the funeral home. The payment process realizes the function of billing the client for the funeral fee for the funeral plan selected by the client and the function of settling the funeral fee for the funeral plan selected by the client. The funeral fee proposal process realizes the function of proposing changes to the funeral fee.

[0065] [Funeral plan proposal process flow] The flow of the funeral plan proposal process will be explained. The funeral plan proposal process is executed when the client-side funeral app is launched. In other words, the funeral plan proposal process is a process that is executed when the client-side funeral app is launched.

[0066] As shown in FIG. 8, in step S100, the processor 21 of the client terminal 20 transmits authentication data to the server 40. The authentication data is input by the client, for example, when the client-side funeral app is launched for the first time. The authentication data may be data generated or acquired by the client using another application. In other words, the authentication data may be shared between the client-side funeral app and the other application.

[0067] The other application may be, for example, an application linked to the client-side funeral app. The other application may be, for example, but is not limited to, an application that provides an e-commerce site, an application that provides a points program, or an application that provides electronic payment services. The authentication data may include, for example, the client ID and password. The authentication data may also include other client data.

[0068] In step S101, processor 41 of server 40 receives authentication data. In step S102, processor 41 of server 40 authenticates the requester based on the authentication data. Processor 41 determines that authentication of the requester has been successful, for example, when the requester ID identified from the authentication data matches the password.

[0069] In step S103, processor 41 of server 40 transmits the authentication result of the requester to client terminal 20. In step S104, processor 21 of client terminal 20 receives the authentication result of the requester. If client authentication fails, processor 21 may terminate the funeral plan proposal process. Processor 21 may terminate the funeral plan proposal process, for example, if client authentication fails a specified number of times. As described above, the funeral plan proposal process is a process performed when the client-side funeral app is started. Therefore, terminating the funeral plan proposal process means terminating the client-side funeral app.

[0070] If the requester is successfully authenticated, in step S105, the processor 21 of the requester terminal 20 transmits the requester data. The requester data is input by the requester, for example, when the requester-side funeral app is launched for the first time. The requester data may be data generated or acquired by the requester using another application. In other words, the requester data may be shared between the funeral app and the other application.

[0071] The requester data may include, for example, data indicating the current location of the requester. The processor 21 identifies the current location of the requester based on the location information acquired from the GNSS receiver 26. The data indicating the current location of the requester is, for example, data indicating latitude and longitude coordinate values.

[0072] In step S106, processor 41 of server 40 updates requester database 42c based on the requester data received from requester terminal 20. Processor 41 may be able to update requester database 42c based on requester data received from another server, or may be able to refer to requester data managed by another server. The other server is a server that can communicate with requester terminal 20 when the requester uses another application.

[0073] In step S107, processor 41 of server 40 determines one or more funeral plans to recommend to the client based on the updated client data. For example, processor 41 inputs the client data into plan recommendation model 47, and obtains the funeral plans recommended to the client, which plan recommendation model 47 outputs. The client data to be input into plan recommendation model 47 is obtained by processor 41 from client database 42c.

[0074] The client data input to the plan recommendation model 47 may include at least some of the data items (e.g., attribute data correlated with funeral plan preferences) used to generate the plan recommendation model 47. The client data input to the plan recommendation model 47 may include, for example, client attribute data. The client attribute data may include, for example, static data and dynamic data.

[0075] Static data is data indicating, for example, date of birth, place of origin, gender, and biometric information. Data indicating biometric information is used for biometric authentication. Dynamic data is data indicating, for example, name, age, current address, current location, family composition, annual income, occupation, income, employment status, living situation, hobbies, and behavioral history. Behavioral history is, for example, funeral app usage history, other application usage history, website browsing history, and website search history. Funeral app usage history includes funeral plan browsing history, funeral plan search history, and funeral history using funeral plans. Other application usage history includes product or service transaction history.

[0076] In step S108, processor 41 of server 40 transmits plan data indicating the one or more determined funeral plans to client terminal 20. That is, processor 41 outputs one or more funeral plans to recommend to the client. The plan data includes, for example, information indicating the details of each funeral plan, funeral fees, funeral home, and recommendation order. In step S109, processor 21 of client terminal 20 receives the plan data. In step S110, processor 21 of client terminal 20 displays a plan display screen on display 25 based on the plan data. Processor 21 displays the funeral plans on the plan display screen based on the recommendation order.

[0077] [Negotiation process flow] The flow of negotiation processing will be explained. The negotiation process is executed when the client terminal 20 receives a negotiation operation from the client while the client-side funeral application is running.

[0078] As shown in Figure 9, in step S200, processor 21 of client terminal 20 transmits plan data indicating the funeral plan being viewed to server 40. In step S201, processor 41 of server 40 receives the plan data. Processor 41 identifies the funeral plan selected by the client, for example, from the plan ID included in the plan data. Processor 41 identifies the funeral home that offers the funeral plan selected by the client, for example, from the corporation ID included in the plan data.

[0079] In step S202, processor 41 of server 40 transmits the negotiation destination data to client terminal 20 and funeral home terminal 30. The negotiation destination data includes data indicating the client and data indicating the funeral home. Processor 41, for example, transmits the negotiation destination data including a corporation ID indicating the identified funeral home to client terminal 20 of the client who performed the negotiation operation. Processor 41, for example, transmits the negotiation destination data including a client ID indicating the client who performed the negotiation operation to funeral home terminal 30 of the identified funeral home.

[0080] In step S203, processor 21 of client terminal 20 receives the negotiation destination data. In step S204, processor 21 of client terminal 20 displays a client-side negotiation screen on display 25. In step S205, processor 31 of funeral home terminal 30 receives the negotiation destination data. In step S206, processor 31 of funeral home terminal 30 displays a funeral home-side negotiation screen on display 35.

[0081] In steps S207 to S209, processor 21 of client terminal 20 and processor 31 of funeral home terminal 30 each transmit and receive negotiation data via server 40. That is, when processor 41 of server 40 receives negotiation data transmitted from client terminal 20, it transmits the negotiation data or data obtained by processing the negotiation data to funeral home terminal 30. On the other hand, when processor 41 receives negotiation data transmitted from funeral home terminal 30, it transmits the negotiation data or data obtained by processing the negotiation data to client terminal 20. The negotiation data includes, for example, character data to be displayed on the negotiation screen. The character data is data entered by the client and the provider.

[0082] [Payment process flow] The flow of the payment process will be explained. The settlement process is executed when the funeral home terminal 30 accepts a billing operation from the provider while the funeral home-side funeral app is running.

[0083] As shown in Fig. 10, in steps S300 to S302, processor 31 of funeral home terminal 30 transmits billing data to client terminal 20 via server 40. That is, when processor 41 of server 40 receives the billing data transmitted from funeral home terminal 30, it transmits the billing data or data obtained by processing the billing data to client terminal 20. The billing data includes, for example, data indicating the contents of the funeral plan decided upon through business negotiations. The billing data includes, for example, data indicating the funeral fees for the funeral plan decided upon through business negotiations.

[0084] In step S303, processor 21 of client terminal 20 receives the billing data. Processor 21 displays a payment screen on display 25, for example, based on data included in the billing data indicating the details of the funeral plan decided through negotiations. Processor 21 displays the payment screen to show the details of the funeral plan decided through negotiations. Processor 21 displays the payment screen on display 25, for example, based on data included in the billing data indicating the funeral fees for the funeral plan decided through negotiations. Processor 21 displays the payment screen to show the funeral fees for the funeral plan decided through negotiations.

[0085] In steps S304 to S306, upon receiving the payment operation, processor 21 of client terminal 20 settles the funeral fees for the funeral plan decided upon through negotiation, and transmits payment data indicating that the funeral fees have been settled to funeral home terminal 30 via server 40. In other words, upon receiving the payment data transmitted from client terminal 20, processor 41 of server 40 transmits the payment data or data obtained by processing the payment data to funeral home terminal 30. For example, upon payment of the funeral fees, processor 21 displays a payment screen indicating that the funeral fees have been settled.

[0086] In step S307, processor 31 of funeral home terminal 30 receives the payment data. Processor 31 displays a negotiation screen on display 25, for example, to indicate that the funeral fee has been paid.

[0087] [Price proposal processing flow] The flow of the fee proposal process will be described. The fee proposal process is executed when a predetermined proposal time arrives. The predetermined proposal time arrives, for example, at a predetermined cycle. The predetermined cycle may arrive, for example, every predetermined day, every predetermined week, or every predetermined month. The predetermined proposal time may arrive at the same time for all funeral plans, or at different times for some funeral plans. The predetermined proposal time may arrive at different cycles for each funeral plan, for example.

[0088] As shown in FIG. 11, in step S400, the processor 41 of the server 40 obtains the predicted amount for each funeral plan registered in the plan database 42d for which a predetermined proposal period has arrived. For example, the processor 41 obtains the predicted amount of the funeral plan output by the fee prediction model 46 by inputting at least a portion of the plan data and environmental data into the fee prediction model 46. The processor 41 obtains the plan data and environmental data to be input into the fee prediction model 46 from the plan database 42d and the environmental database 42e. If the predicted amount of the funeral plan falls outside a predetermined range between the lower and upper limits, the processor 41 may correct the predicted amount so that it falls within the same range. If the predicted amount exceeds the upper limit, the processor 41 may correct the predicted amount to the upper limit or a value obtained by multiplying the upper limit by a predetermined coefficient. If the predicted amount falls below the lower limit, the processor 41 may correct the predicted amount to the lower limit or a value obtained by multiplying the lower limit by a predetermined coefficient. In this case, the upper or lower limit may be determined in advance depending on the funeral plan.

[0089] For example, the processor 41 may update at least a part of the environmental data acquired from the environmental database 42e to reflect the current situation (for example, congestion data or date data). Alternatively, the processor 41 may update the environmental data at predetermined intervals, instead of updating the environmental data when acquiring the environmental data.

[0090] The plan data and environmental data input into the fee prediction model 46 may include at least some of the data items used to generate the fee prediction model 46. The plan data input into the fee prediction model 46 may include, for example, data indicating the contents of the target funeral plan, data indicating the current funeral fees for the target funeral plan, and supply and demand data for the target funeral plan.

[0091] The contents of a funeral plan include, for example, whether or not the body will be transported, whether or not the body will be laid to rest, whether or not a wake will be held, whether or not a funeral will be held, whether or not a funeral service will be held, and whether or not cremation will be held, but are not limited to these. For example, the contents of a funeral plan may include the type or grade of vehicle used to transport the body if the body is to be transported. For example, the contents of a funeral plan may include the period for which the body will be laid to rest if the body is to be laid to rest. For example, the contents of a funeral plan may include the contents of the wake if a wake will be held. For example, the contents of a funeral plan may include the contents of the funeral if a funeral is held. For example, the contents of a funeral may include the funeral method (how the body will be disposed of). For example, the contents of a funeral plan may include the contents of the funeral if a funeral service is held.

[0092] The supply and demand data may include data indicating the demand and supply of each funeral plan over one or more observation periods. The one or more observation periods may include a past period. The past period may include, for example, a predetermined period going back from the present and a predetermined period of the same time. The predetermined period of the same time may include, for example, the same day a predetermined number of years ago, the same week a predetermined number of years ago, the same month a predetermined number of years ago, the same day a predetermined number of times ago, the same week a predetermined number of months ago, the same day of the week a predetermined number of times ago in the Rokuyo calendar, and the same day of the week a predetermined number of weeks ago in the Henetsuyo calendar.

[0093] The data indicating the demand for funeral plans includes, for example, the number of times the target funeral plan has been sold, the number of times the target funeral plan has been viewed, and the number of times negotiations have been held for the target funeral plan via the funeral app. The data indicating the demand for funeral plans is updated, for example, by the processor 41 of the server 40. The data indicating the supply of funeral plans includes, for example, information indicating the maximum number of funeral services that the provider of the target funeral plan can provide on the same day or in the same time slot. The maximum number of funeral services that can be provided may vary, for example, depending on the demand for other funeral plans provided by the provider of the target funeral plan on the same day or in the same time slot.

[0094] The one or more observation periods may include a future period. The future period may be, for example, a scheduled date for providing funeral services (hereinafter simply referred to as the "scheduled date"). The data indicating the demand and supply of funeral plans on the scheduled date may include, for example, a prediction of the demand and supply of funeral plans on the scheduled date. The prediction of the demand and supply of funeral plans on the scheduled date may be output, for example, by inputting data indicating the demand and supply of each funeral plan for a past period into a machine learning model for predicting demand for funeral plans.

[0095] The environmental data input to the price prediction model 46 may include, for example, at least some of the area data, date data, and congestion data. The area data may include, for example, but is not limited to, data on funeral prices in the area where the funeral home offering the target funeral plan is located.

[0096] The data on funeral fees may include, but is not limited to, the going rate for funeral fees in the area where the funeral home is located. The date data may include, but is not limited to, data indicating the day of the week for the scheduled date, data indicating the day of the week for the scheduled date, and data indicating whether the scheduled date is a public holiday. The congestion data may include, but is not limited to, data indicating the capacity or usage status of crematoria in the area where the funeral home offering the target funeral plan is located.

[0097] In step S401, the processor 41 of the server 40 transmits fee data indicating the estimated cost of the funeral plan to the funeral home terminal 30. In other words, the server 40 outputs the estimated cost of the funeral plan to the funeral home that provides the funeral plan. The fee data includes, for example, data indicating a plan ID for identifying the funeral plan. The fee data may also include an evaluation of the current funeral fee (set fee).

[0098] Processor 41 may evaluate the funeral fees based on the difference between the predicted amount and the current funeral fee (set fee). For example, if the predicted amount and the current funeral fee are the same, or if the difference between the predicted amount and the current funeral fee is less than a specified value, processor 41 may output an evaluation result that the current funeral fee is appropriate. Also, if the current funeral fee is higher or lower than the predicted amount by more than a specified value, processor 41 may output an evaluation result that the current funeral fee is "high" or "low."

[0099] The evaluation results may be displayed in multiple evaluation levels. The specified value may be determined, for example, based on the current funeral fee, may be a predetermined value, or may be determined by the provider via the funeral app. If processor 41 evaluates that the current funeral fee (set fee) is appropriate, it does not need to transmit fee data to funeral home terminal 30.

[0100] In step S402, processor 31 of funeral home terminal 30 receives the fee data. Processor 31, for example, displays a fee update screen on display 35 based on the fee data. Processor 31 displays the fee update screen to show, for example, the estimated amount, the current funeral fee, and some or all of the plan details.

[0101] In step S403, upon receiving the update operation, the processor 31 of the funeral home terminal 30 transmits to the server 40 an update instruction to update the funeral fee for the target funeral plan to the predicted amount.

[0102] In step S404, processor 41 of server 40 receives the update instruction. In step S405, processor 41 of server 40 updates the funeral plan fees managed by plan database 42d to the estimated amount. Processor 41 may send data indicating that the fees have been updated to funeral home terminal 30. Processor 31 of funeral home terminal 30 may update the fee update screen to indicate that the fees have been updated.

[0103] [Examples of display screens on each device and processing flow related to display] [Plan selection screen] When the processor 21 of the client terminal 20 starts the client-side funeral application, the processor 21 displays a plan selection screen on the display 25.

[0104] 12, the plan selection screen includes various objects. For example, the plan selection screen includes an object 61 indicating the details of the funeral plan, an object 62 indicating the name of the funeral plan, an object 63 indicating the standard funeral fee for the funeral plan, and an object 64 indicating the name of the funeral home that offers the funeral plan. The plan selection screen displays the funeral plan by displaying these various objects 61 to 64.

[0105] For example, while the plan selection screen is displayed, the processor 21 of the requester terminal 20 accepts input of a redisplay operation to redisplay the funeral plan that was displayed immediately before. For example, while the plan selection screen is displayed, the processor 21 of the requester terminal 20 accepts input of a display advance operation to display the next funeral plan. For example, while the plan selection screen is displayed, the processor 21 of the requester terminal 20 accepts input of a negotiation operation to display a negotiation screen with the funeral home that offers the funeral plan. The redisplay operation is, for example, an upward swipe. The display advance operation is, for example, a downward swipe. The negotiation operation is, for example, a rightward swipe.

[0106] Processor 21 of client terminal 20 displays funeral plans on the plan selection screen in descending order of recommendation rank. That is, processor 21 first displays the funeral plan that is most recommended to the client on the plan selection screen. Then, by accepting a display advance operation, processor 21 displays the funeral plan that is second most recommended to the client on the plan selection screen. The client can negotiate with the funeral home that offers the funeral plan by selecting the funeral plan that they prefer from the recommended funeral plans, for example, through a negotiation operation.

[0107] [Requester's Negotiation Screen] When the processor 21 of the client terminal 20 accepts the negotiation operation, it displays on the display 25 a client-side negotiation screen to provide a forum for negotiation between the client and the funeral home that offers the displayed funeral plan.

[0108] As shown in Figure 13, the client's negotiation screen includes various objects. For example, the client's negotiation screen includes object 71 indicating the name of the funeral plan, object 72 indicating the name of the funeral home that offers the funeral plan, and object 73 indicating the details of the negotiation. Object 73 is, for example, a chat room. The chat room includes a field for entering messages and messages sent and received between the client and the funeral home.

[0109] Processor 21 of client terminal 20 displays a client-side negotiation screen to show the content of the message sent to the funeral home, for example, based on negotiation data sent to funeral home terminal 30 via server 40. Processor 21 displays a client-side negotiation screen to show the content of the message received from the funeral home, for example, based on negotiation data received from funeral home terminal 30 via server 40. This allows the client to negotiate with the funeral home questions, funeral plan details, and changes to the funeral fee by sending and receiving messages in the chat room.

[0110] [Funeral home negotiation screen] When the funeral home terminal 30 receives the negotiation destination data, it displays the funeral home side negotiation screen on the display 35.

[0111] 14, the funeral home's negotiation screen includes various objects. For example, the funeral home's negotiation screen includes an object 81 indicating the name of the funeral plan, an object 82 indicating the client's name, an object 83 indicating the negotiation details, and an object 84 indicating the funeral fee for the funeral plan decided upon through negotiation. Object 84 includes, for example, a field for inputting the funeral fee for the funeral plan decided upon through negotiation, and a billing button for billing for the funeral fee.

[0112] Processor 31 of funeral home terminal 30 displays the funeral home side negotiation screen to show the content of the message sent to the client, for example, based on negotiation data sent to client terminal 20 via server 40. Processor 31 displays the funeral home side negotiation screen to show the content of the message received from the client, for example, based on negotiation data received from client terminal 20 via server 40. This allows the provider to respond to client questions, funeral plan details, requests for changes to funeral fees, etc., by sending and receiving messages in the chat room.

[0113] For example, based on the provider's input operation of the funeral fee, processor 31 displays the funeral home side negotiation screen to show the funeral fee of the funeral plan decided through negotiation. For example, based on the provider's operation of claiming the funeral fee, processor 31 sends claim data to client terminal 20. This allows the provider to present the funeral fee of the funeral plan decided through negotiation to the client and to claim the funeral fee from the client.

[0114] [Payment screen] When the processor 21 of the client terminal 20 receives the fee data, it displays a payment screen on the display 25.

[0115] 15, the payment screen includes various objects. For example, the payment screen includes an object 91 that indicates the details of the funeral plan decided upon through business negotiations, and an object 92 that indicates the funeral fees for the funeral plan decided upon through business negotiations. Object 92 is, for example, a payment button for paying the funeral fees for the funeral plan decided upon through business negotiations.

[0116] The processor 21 can, for example, settle the funeral fees based on the client's payment operation. This allows the client to pay the funeral fees if they are satisfied with the contents of the funeral plan and the funeral fees decided through negotiations. In other words, if the client is satisfied with the contents of the funeral plan and the funeral fees after changes are made through negotiations, they can enter into a contract with the funeral home to receive funeral services based on that funeral plan.

[0117] For example, when the funeral fee is paid, the processor 21 of the client terminal 20 updates the payment screen. 16, the processor 21 displays the payment screen to include, for example, an object 101 indicating the contracted funeral plan, an object 102 indicating the funeral home with which the funeral contract has been made, and an object 103 indicating the paid funeral fee. This allows the client to retain the contract details by, for example, capturing the payment screen after the funeral fee payment has been made.

[0118] [Plan input screen] When the processor 31 of the funeral home terminal 30 accepts the new operation, it displays a plan input screen on the display 35.

[0119] 17, the plan input screen includes various objects. The plan input screen includes, for example, an object 111 indicating the details of the funeral plan to be newly registered in the plan database 42d, and an object 112 (for example, a button) for instructing the registration of the funeral plan.

[0120] Object 111 may include, for example, a field for inputting a plan name and a field for inputting a funeral fee. Object 111 may include, for example, a field for inputting an image to be displayed on the plan selection screen and a field for selecting a display pattern for the funeral plan to be displayed on the plan selection screen. Object 111 may include, for example, an object that instructs the display of a preview of the plan selection screen based on the funeral plan being input. Object 111 may include, for example, objects that indicate the presence or absence and type of transportation, placement, wake, funeral, memorial service, and funeral ceremony.

[0121] For example, when processor 31 of funeral home terminal 30 accepts a registration operation, it transmits data indicating the entered funeral plan details and an instruction to register the funeral plan to server 40. For example, when server 40 receives the data indicating the funeral plan details and the instruction to register the funeral plan, it registers the funeral plan in plan database 42d based on the data indicating the funeral plan details. This allows the provider to register any funeral plan in plan database 42d by entering the funeral plan details.

[0122] [Price update screen] When the processor 31 of the funeral home terminal 30 receives the fee data, it displays a fee update screen on the display 35.

[0123] 18, the fee update screen includes various objects. The fee update screen includes, for example, object 121 indicating that a predicted amount has been proposed as the funeral fee, and object 122 indicating the proposed funeral fee. The fee update screen includes, for example, object 123 (e.g., a button) indicating that the predicted amount is to be accepted as the funeral fee, and object 124 (e.g., a button) indicating that the predicted amount is not to be accepted as the funeral fee. Object 121 may be, for example, a field indicating the name of the funeral plan for which the predicted amount has been proposed.

[0124] The fee update screen may include, for example, an object 125 (e.g., a check button) that instructs whether approval should be omitted from the next time onward. The object 125 may include an input field for at least one of an upper limit and a lower limit of the funeral fee when approval is omitted.

[0125] When the processor 31 of the funeral home terminal 30 receives an update operation instructing to update the funeral fee, it updates the fee update screen. 19, when the funeral fees are updated, the fee update screen may include, for example, object 131 indicating that the funeral fees have been changed and object 132 indicating the changed funeral fees. Object 131 may be, for example, text indicating the name of the funeral plan for which the funeral fees have been changed. The provider can recognize that the funeral fees have been updated by the fee update screen being updated.

[0126] As shown in Figure 20, when the change in funeral fee is approved, the funeral plan is displayed with the changed funeral fee on the plan selection screen. Specifically, in the processing of step S108, processor 41 of server 40 transmits plan data including data indicating the changed funeral fee to client terminal 20. In other words, processor 41 can output an estimated amount as the funeral fee for the funeral plan to the client. When processor 21 of client terminal 20 receives the plan data including data indicating the changed funeral fee, it displays the plan selection screen on display 25 to show the changed funeral fee.

[0127] For example, if a client is viewing a funeral plan whose funeral fee has been changed, the funeral fee presented to the client may not be changed. For example, if a client is viewing a funeral plan whose funeral fee has been changed, processor 21 displays a plan selection screen on display 25 that shows the funeral fee before the change. The fact that a client is viewing a funeral plan whose funeral fee has been changed may mean, for example, that the target funeral plan is currently being displayed on the plan selection screen, or that the client's funeral app has been running since the target funeral plan was displayed (the client's funeral app has not been closed).

[0128] [Effects of the present disclosure] The server 40 that provides the intermediary service can set appropriate funeral fees according to the environmental data, thereby proposing the most suitable funeral plan to the client, and the client can then select a funeral plan with an appropriate fee.

[0129] The widespread adoption of funeral service intermediation systems may intensify price competition among funeral homes. As a result, there are concerns that the number of funeral requests based on traditional pricing may decrease, or that funeral homes' profit margins may decline due to price reductions. In this regard, the present disclosure allows funeral fees to be appropriately adjusted according to the situation, thereby preventing a decline in the service provider's profit margins even when a funeral service intermediation system is involved. Therefore, the intermediation service of the present disclosure makes it possible to propose the optimal funeral plan for both the client and the provider.

[0130] While a client may not have the time to contact multiple funeral homes and compare multiple funeral plans, they may still want to know details that are not provided in the funeral plan. In this regard, the present disclosure allows the client to directly negotiate the selected funeral plan with the provider via a client-side negotiation screen linked to the plan selection screen. Since both the client and the provider share the selected plan data, negotiations can proceed smoothly.

[0131] Furthermore, the client can make payments via the client terminal 20 based on the data indicating the funeral plan details decided upon through negotiations. This allows the client and the provider to quickly arrange the funeral. This reduces the difficulty and stress that the client may experience when making a decision from multiple options, taking into account the cost.

[0132] In this way, the intermediary service of the present disclosure can mediate business negotiations related to funeral services while providing various information or a forum for information exchange to help both the funeral home and the client. Therefore, according to the present disclosure, the user experience of both the client and the provider, who are users of the intermediary service, can be improved.

[0133] The effects of the present disclosure will be described. (1) Processor 41 of server 40 acquires plan data related to a funeral plan. Processor 41 acquires current environmental data related to the funeral plan. Processor 41 acquires a predicted amount for the funeral plan by inputting at least a portion of the plan data and environmental data into fee prediction model 46. Processor 41 outputs the predicted amount to the funeral home that provides the funeral plan. This allows the provider to consider setting the predicted amount calculated based on the plan data and environmental data as the new funeral fee.

[0134] (2) The plan data includes plan content data that indicates the content of the corresponding funeral plan. This increases the likelihood of obtaining a predicted amount appropriate for the content of each funeral plan.

[0135] (3) The plan data includes supply and demand data that indicates the demand for the corresponding funeral plan, which increases the likelihood of obtaining a predicted amount appropriate for the demand for each funeral plan.

[0136] (4) The environmental data includes data indicating at least one of the date and area for which the funeral service will be provided. The data indicating the date includes data related to at least one of the six days of the week, the seven days of the week, and public holidays. This increases the likelihood of obtaining a predicted amount based on at least one of the date and area for which the funeral service will be provided. It also increases the likelihood of obtaining a predicted amount based on information such as the six days of the week, the seven days of the week, and public holidays.

[0137] (5) The environmental data includes congestion data indicating the congestion status of the crematorium. The congestion status includes the capacity or usage status of the crematorium. This improves the possibility of obtaining a predicted amount based on the capacity or usage status of the crematorium.

[0138] (6) The processor 41 of the server 40 can output the estimated amount of the funeral plan to the client as the funeral fee for the funeral plan. This allows the client to select a funeral plan based on the estimated amount and the updated funeral fee.

[0139] (7) The fee prediction model 46 includes at least one of a machine learning model for predicting demand for funeral services and a reinforcement learning model for maximizing profits or sales, which are remuneration. This increases the likelihood of obtaining a predicted amount according to the predicted demand for funeral services or a predicted amount for maximizing remuneration.

[0140] (8) The plan data includes the current set price for the corresponding funeral plan. The server 40 is configured to output a rating for the set price along with the estimated price. The rating is based on the difference between the set price and the estimated price. This makes it easy for the provider to set the funeral price based on the rating.

[0141] (9) The processor 41 of the server 40 outputs a funeral plan recommended to the client by inputting client data into the plan recommendation model 47. This can reduce the time it takes for the client to search for a preferred funeral plan.

[0142] (10) The client data includes client attribute data, which increases the likelihood of obtaining a funeral plan that matches the client's attributes. (11) The client attribute data includes data indicating the client's hometown, address, current location, etc. This increases the likelihood of obtaining a funeral plan that matches the client's hometown, address, current location, etc.

[0143] (12) The client attribute data includes data indicating the client's income, such as annual salary. This can improve the client's chances of obtaining a funeral plan that matches their income. (13) The client attribute data includes data indicating the client's living situation, hobbies, behavioral history, etc. This increases the likelihood of obtaining a funeral plan that matches the client's living situation, hobbies, behavioral history, etc.

[0144] (14) When processor 21 of client terminal 20 accepts a negotiation operation, it transmits plan data to server 40, including data indicating the plan ID of the displayed funeral plan. When processor 41 of server 40 receives the plan data, it transmits negotiation destination data to client terminal 20 and funeral home terminal 30. Processor 21 of client terminal 20 and processor 31 of funeral home terminal 30 display negotiation screens on displays 25 and 35 for negotiation between the client and the funeral home. This allows the client to easily negotiate with the funeral home. The client can then customize the funeral plan to suit their own wishes.

[0145] (15) When the processor 21 of the client terminal 20 receives the billing data, it displays a payment screen on the display 25 to show the funeral fees for the customized funeral plan. When the processor 21 accepts the payment operation, it settles the funeral fees. This allows the client to settle the funeral fees if they are satisfied with the funeral fees for the customized funeral plan.

[0146] [Example of change] This embodiment can be modified as follows: This embodiment and the following modifications can be combined and implemented within the scope of technical compatibility.

[0147] [Change Example 1] The plan data may include data relating to one or more funeral plans and may be changed as desired.

[0148] [Change Example 2] The environmental data may include data relating to one or more funeral environmental elements and may be changed as desired.

[0149] [Change Example 3] The predetermined proposal time may be reached when the funeral home terminal 30 receives a prediction request from the provider. In other words, the funeral plan prediction amount may be obtained at any time desired by the provider. In this case, the next proposal time may not arrive until a predetermined period has passed.

[0150] [Change Example 4] The funeral home terminal 30 may be capable of accepting an instruction to omit approval of changes to the funeral fee based on the predicted amount when registering or updating a funeral plan. In this case, the funeral home terminal 30 may be capable of accepting an instruction to omit approval of changes to the funeral fee based on the predicted amount if the predicted amount is within a predetermined range. For a funeral plan for which approval of changes to the funeral fee based on the predicted amount has been omitted, the predetermined proposal time may arrive when the funeral plan is determined as the funeral plan to be recommended to the client. In other words, for a funeral plan for which approval of changes to the funeral fee based on the predicted amount has been omitted, the predicted amount may be determined when the funeral plan is determined as the funeral plan to be recommended to the client.

[0151] [Change Example 5] The processor 41 of the server 40 may obtain a predicted funeral plan price by inputting other data into the price prediction model in addition to or instead of the plan data and environmental data. The other data may be, for example, client data. In other words, the predicted funeral plan price may be obtained for each client. This increases the likelihood of setting a funeral fee that is appropriate for each client. In this case, the funeral home's negotiation screen may display the funeral price initially presented to the client.

[0152] This allows the provider to determine the funeral fee through negotiation based on the initially presented funeral fee. For example, if the funeral fee initially presented to the client is different even for the same funeral plan, the funeral home can provide different funeral-related services to the client whose funeral fee is relatively higher by adding services not included in the funeral plan. For example, a service not included in the funeral plan could be to assign a relatively skilled employee to handle the funeral.

[0153] [Change Example 6] The supply and demand data may be linked to the funeral fees for each funeral plan. In other words, the supply and demand data may include supply and demand data when the funeral plan has a first price and supply and demand data when the funeral plan has a second price. This increases the likelihood of obtaining a predicted amount that reflects changes in demand due to fluctuations in the funeral fees for each funeral plan.

[0154] [Change Example 7] The above-described processes and the order of steps are merely examples, and are not intended to be limiting. The order of steps and processes can be arbitrarily changed without departing from the scope of the embodiments and modifications.

[0155] [Change Example 8] In the above-mentioned embodiments and modified examples, some or all of the processing and steps performed by the processor 21 of the client terminal 20 may be performed by one or both of the processor 31 of the funeral home terminal 30 and the processor 41 of the server 40.

[0156] [Change Example 9] Of the above-mentioned embodiments and modified examples, some or all of the processing and steps performed by processor 31 of funeral home terminal 30 may be performed by one or both of processor 21 of client terminal 20 and processor 41 of server 40.

[0157] [Change Example 10] In the above-described embodiment and modified examples, some or all of the processes and steps executed by processor 41 of server 40 may be executed by one or both of processor 21 of client terminal 20 and processor 31 of funeral home terminal 30. In other words, each of the processes and steps described in the embodiment and modified examples may be executed by any one or more processors among processor 21 of client terminal 20, processor 31 of funeral home terminal 30, and processor 41 of server 40.

[0158] [Change Example 11] When each of the processes and steps described in the embodiments and modified examples is configured to be executed by the processor 21 of the client terminal 20 or the processor 31 of the funeral home terminal 30, the information processing system 10 may be configured without including one or more servers 40.

[0159] [Note] Below, aspects that can be understood from the above embodiment and modified examples are listed. [Aspect 1] A plan data acquisition unit configured to acquire plan data related to a funeral plan; an environmental data acquisition unit configured to acquire current environmental data related to the funeral plan; a fee acquisition unit configured to acquire a predicted amount of the funeral plan by inputting the plan data and at least a portion of the environmental data into a fee prediction model; An information processing system comprising: a fee output unit configured to output the predicted amount to a funeral home that provides the funeral plan.

[0160] In the above embodiment, the server 40 that acquires the plan data in step S400 corresponds to the plan data acquisition unit, and the server 40 that acquires the environmental data in step S400 corresponds to the environmental data acquisition unit. In the above embodiment, the server 40 that acquires the predicted amount of the funeral plan by inputting the plan data and environmental data into the fee prediction model in step S400 corresponds to the fee acquisition unit. In the above embodiment, the server 40 that transmits fee data including data indicating the predicted amount to the funeral home terminal 30 in step S401 corresponds to the fee output unit.

[0161] [Aspect 2] The information processing system of aspect 1, wherein the plan data includes data indicating the contents of the corresponding funeral plan.

[0162] [Aspect 3] The information processing system according to aspect 1 or aspect 2, wherein the plan data includes data indicating demand for corresponding funeral plans.

[0163] [Aspect 4] The environmental data includes data indicating at least one of a date and a region where the funeral service will be provided; The information processing system according to any one of Aspects 1 to 3, wherein the data indicating the date includes data relating to at least one of the six days of the week, the seven days of the week, and public holidays.

[0164] [Aspect 5] The environmental data includes data indicating the congestion status of the crematorium, An information processing system according to any one of aspects 1 to 4, wherein the congestion status includes the capacity or usage status of the crematorium.

[0165] [Aspect 6] An information processing system according to any one of aspects 1 to 5, wherein the fee output unit is configured to output the predicted amount to the person requesting the funeral as the fee for providing funeral services according to the funeral plan.

[0166] [Aspect 7] An information processing system described in any one of aspects 1 to 6, wherein the fee prediction model includes at least one of a machine learning model for predicting demand for funeral services or a reinforcement learning model for maximizing profits or sales, which are rewards.

[0167] [Aspect 8] The plan data includes the current set price of the corresponding funeral plan; the fee output unit is configured to output an evaluation of the set fee together with the predicted amount; The information processing system according to any one of aspects 1 to 5, wherein the evaluation is performed based on the difference between the set fee and the predicted amount.

[0168] [Aspect 9] The computer Obtaining plan data relating to a funeral plan; obtaining current environmental data related to said funeral plan; inputting the plan data and at least a portion of the environmental data into a price prediction model to obtain a predicted price for the funeral plan; outputting the predicted amount to a funeral home that provides the funeral plan; 2. An information processing method, comprising:

[0169] [Aspect 10] On the computer, Obtaining plan data relating to a funeral plan; obtaining current environmental data related to said funeral plan; inputting the plan data and at least a portion of the environmental data into a price prediction model to obtain a predicted price for the funeral plan; and outputting the predicted amount to a funeral home that provides the funeral plan.

[0170] [Aspect 11] On the computer, Accepting input of plan data relating to a funeral plan from a funeral home; transmitting the plan data to another computer; A program that receives and executes data indicating the predicted amount of the funeral plan from the other computer, the data being obtained by inputting the plan data into a price prediction model.

[0171] It will be apparent to those skilled in the art that the present invention may be embodied in other specific forms without departing from the spirit of the present invention. For example, some of the components described in the embodiment (or one or more aspects thereof) may be omitted, or some components may be combined. The same applies to procedures. The scope of the present invention should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. [Explanation of symbols]

[0172] NT...Network 10...Information processing system 20...Client terminal 21...Processor 22...Memory 23...Communication interface 24...Touch sensor 25...Display 26...GNSS receiver 30...Funeral home terminal 31...Processor 32...Memory 33...Communication interface 34...Keyboard 35...Display 40...Server 41...Processor 42...Memory 43...Communication interface 61-64, 71-73, 81-84, 91, 92, 101-103, 111, 112, 121-125, 131, 132...Objects

Claims

1. A plan data acquisition unit configured to acquire plan data related to a funeral plan; an environmental data acquisition unit configured to acquire current environmental data related to the funeral plan; a fee acquisition unit configured to acquire a predicted amount of the funeral plan by inputting the plan data and at least a portion of the environmental data into a fee prediction model; A fee output unit configured to output the predicted amount to a funeral home that provides the funeral plan, The plan data includes the current set price of the corresponding funeral plan; the fee output unit is configured to output an evaluation of the set fee together with the predicted amount; An information processing system, wherein the evaluation is based on the difference between the set fee and the predicted amount.

2. The information processing system according to claim 1 , wherein the plan data includes data indicating the contents of a corresponding funeral plan.

3. The information processing system of claim 1 , wherein the plan data includes data indicating demand for corresponding funeral plans.

4. The environmental data includes data indicating at least one of a date and a region where the funeral service will be provided; The information processing system according to claim 1 , wherein the data indicating the date includes data relating to at least one of the six days of the week, the seven days of the week, and public holidays.

5. The environmental data includes data indicating the congestion status of the crematorium, The information processing system of claim 1 , wherein the congestion status includes the capacity or usage status of the crematorium.

6. 2. The information processing system according to claim 1, wherein the fee output unit is configured to output the predicted amount to the person requesting the funeral as a fee for the provision of funeral services under the funeral plan.

7. The information processing system of claim 1, wherein the fee prediction model includes at least one of a machine learning model for predicting demand for funeral services or a reinforcement learning model for maximizing profits or sales as compensation.

8. The computer Obtaining plan data relating to a funeral plan; obtaining current environmental data related to said funeral plan; inputting the plan data and at least a portion of the environmental data into a price prediction model to obtain a predicted price for the funeral plan; outputting the predicted amount to a funeral home that provides the funeral plan; performing The plan data includes the current set price of the corresponding funeral plan; The predicted amount is output together with an evaluation of the set fee, An information processing method, wherein the evaluation is based on the difference between the set fee and the predicted amount.

9. On the computer, Obtaining plan data relating to a funeral plan; obtaining current environmental data related to said funeral plan; inputting the plan data and at least a portion of the environmental data into a price prediction model to obtain a predicted price for the funeral plan; outputting the predicted amount to a funeral home that provides the funeral plan; The plan data includes the current set price of the corresponding funeral plan; The predicted amount is output together with an evaluation of the set fee, The evaluation is based on the difference between the set price and the predicted amount.

10. On the computer, Accepting input of plan data relating to a funeral plan from a funeral home; transmitting the plan data to another computer; receiving from the other computer data indicating a predicted amount of the funeral plan obtained by inputting the plan data into a price prediction model; The plan data includes the current set price of the corresponding funeral plan; The predicted amount is output together with an evaluation of the set fee, The evaluation is based on the difference between the set price and the predicted amount.

Images