JP2021033643A - Life data processing system, life data processing method, and computer program - Google Patents

Abstract

To provide a life data processing system, a life data processing method, and a computer program which process data relating to a life event by a family unit.SOLUTION: The present invention is directed to a life data processing system having a life data server apparatus for processing life data by a family unit and a client apparatus for transmitting and receiving data to and from the life data server apparatus. The life data server apparatus has: a storage unit for storing life data relating to life events by associating family identification information allocated to each family upon family formation stage with life event identification information for use in identification of a life event among life events including various ceremonial occasion; and a transmission unit for transmitting service information relating to life events to the client apparatus based on the number of years after family formation, attribute information of a family member, or history of the life events.SELECTED DRAWING: Figure 1

Description

The present invention relates to a life data processing system, a life data processing method, and a computer program that process data related to life events in family units.

Various methods have been proposed for efficiently sharing data between users. In Patent Document 1, in order to facilitate data sharing between users who participated in an event, a sharing group is created by terminal devices existing within a predetermined range by using the position information of the terminal device of the user, and a predetermined group is created. A technique for distinguishing access rights to shared data inside and outside the scope of is disclosed.

JP-A-2017-004053

In various methods related to data sharing including the method disclosed in Patent Document 1, data recorded or imaged by a personal terminal device owned by each user is shared based on the association between user accounts. Managed as possible. Therefore, it is necessary to associate user accounts for each event, each project, and each purpose.

Multi-functional terminal devices that have become widespread for each user enable the input and output of various data in an individual's life, and the data is not recorded only once on a storage medium, but in the cloud. It can be distributed and held semi-permanently by the server. The inventors focused on recording and utilizing the life data of each user in family units, rather than a system in which the life data of each user that can be acquired by individual terminal devices is brought together and shared by a group. ..

The present invention has been made in view of such circumstances, and an object of the present invention is to provide a life data processing system, a life data processing method, and a computer program for processing data related to life events in a family unit.

The life data processing system of the embodiment of the present disclosure includes a life data server device that processes life data in a family unit, and a client device that transmits and receives data to and from the life data server device. The life data related to the life event is stored in the storage device in association with the family identification information given to the family unit at the family formation stage and the life event identification information for identifying the life event for each life event including the ceremonial occasion. A storage unit for storing and a transmission unit for transmitting service information related to life events to the client device based on the number of years since the formation of the family, attribute information of family members, or the history of life events are provided.

The life data processing method according to the embodiment of the present disclosure is the life data of a life data processing system including a life data server device that processes life data in family units and a client device that transmits and receives data to and from the life data server device. The server device associates the family identification information given to each family at the family formation stage with the life event identification information for identifying the life event for each life event including the ceremonial occasion, and the life data related to the life event. Is stored in the storage device, and includes a process of transmitting service information related to the life event to the client device based on the number of years since the formation of the family, the attribute information of the family member, or the history of the life event.

The computer program of the embodiment of the present disclosure identifies the family identification information given to each family at the family formation stage and the life event for each life event including the ceremonial occasion to the computer that sends and receives data to and from the client device. The life event is related to the process of storing the life data related to the life event in the storage device in association with the life event identification information to be performed, and based on the number of years since the formation of the family, the attribute information of the family member, or the history of the life event. Execute the process of sending service information to the client device.

According to the present disclosure, data related to life events in a family is stored on a family-by-family and event-by-event basis. Based on the data of life events on a family basis, it is possible to propose applications or realistic events that support the life of the family.

It is a schematic diagram of the life data processing system in this embodiment. It is a block diagram which shows the structure of a life data processing system. It is a schematic diagram of an example of life data stored in a storage device. It is a flowchart which shows an example of the processing procedure executed in the life data processing system. It is a flowchart which shows an example of the processing procedure executed in the life data processing system. It is a figure which shows the screen example based on an application. It is a flowchart which shows an example of the processing procedure in the 2nd client apparatus. It is a flowchart which shows an example of the processing procedure in the 1st client apparatus used by a participant. It is a figure which shows the content example of a family data. It is a figure which shows the content example of a family data.

The present disclosure will be specifically described with reference to the drawings showing the embodiments thereof.

FIG. 1 is a schematic diagram of the life data processing system 100 according to the present embodiment. The life data processing system 100 includes a life data server device 1, a storage device 110, a first client device 3 used by a user, and a second client device 4 used by a service provider.

The life data server device 1, the storage device 110, the first client device 3, and the second client device 4 can send and receive data to and from each other via the network N. The network N is a public communication network including the carrier network N2, includes an access point AP and a base station BS in the carrier network N2, and enables communication by wireless communication.

The life data server device 1 stores data including text, still images, moving images, and sounds in the storage device 110 in family units for each life event including a ceremonial occasion. The life data server device 1 executes a process of outputting information based on the life data stored in the storage device 110. For example, the life data server device 1 realizes the exchange of messages (texts) between the service provider related to the life event and the members of the family, and stores images, videos, sounds, etc. as life data for each life event. It can be output as appropriate.

The life data stored in the storage device 110 is generated starting from the event of family formation, associates with the identification information (for example, family code) of the formed family, and corresponds to the identification information of the event and the time information indicating the date and time. Attached and memorized as continuous cotton. The life data server device 1 provides a plurality of applications based on the stored family-based life data. Multiple applications include, for example, schedule management, message exchange, announcements, shared albums, and the like. Further, the life data server device 1 can output an electronic album for sharing each event with the family and related persons of the family and looking back based on the stored life data of each family.

The life data server device 1 can output a proposal for a new life event based on the stored life data for each family. The life data server device 1 realizes planning support and output of information on related services regarding family life events such as travel, child-rearing, employment, long-term care, end-of-life, and funeral.

A user who subscribes to the life data management service provided by the life data processing system 100, that is, a member of the family, uses an application program 3P (hereinafter referred to as an application 3P) that operates on the first client device 3 possessed by the life data server device. By communicating with 1, the service can be provided by the service provider based on the life data. A service provider who subscribes to the life data management service communicates with the life data server device 1 by means of an application program 4P (hereinafter referred to as application 4P) running on the second client device 4, and information about the service based on the life data. Can be provided.

Details of each device that realizes such a life data processing system 100 will be described. FIG. 2 is a block diagram showing the configuration of the life data processing system 100. The life data processing system 100 includes a life data server device 1, a storage device 110, a first client device 3, and a second client device 4.

The life data server device 1 uses a server computer. The life data server device 1 includes a control unit 10, a storage unit 11, and a communication unit 12. The life data server device 1 is described as one server computer for the sake of simplicity, but it is preferable that the life data server device 1 has a configuration in which processing or functions are distributed among a plurality of server computers.

The control unit 10 is a processor using a CPU (Central Processing Unit) and / or a GPU (Graphics Processing Unit). The control unit 10 executes processing using a built-in memory such as a ROM (Read Only Memory) and a RAM (Random Access Memory).

The storage unit 11 includes, for example, a hard disk or a non-volatile memory such as an SSD (Solid State Drive). The life data processing program 1P is stored in the storage unit 11. The control unit 10 reads and executes the life data processing program 1P to make a general-purpose server computer function as the life data server device 1 peculiar to the present disclosure.

The communication unit 12 includes a network card. The control unit 10 can send and receive information to and from the storage device 110, the first client device 3, and the second client device 4 via the network N by the communication unit 12.

The control unit 10 is connected to the storage device 110 and can read and write. The storage device 110 is a storage device used as a database (DB: Data Base), includes a communication unit, a large-capacity storage medium, and a processing unit, receives read / write instructions via communication, and returns a response. Although the storage device 110 will be described as one device in the following description, it is preferable that the storage device 110 is configured as a cloud storage by distributing and storing data in a plurality of storage devices.

Life data stored in family units is stored in the storage device 110 connected via the storage unit 11 and the communication unit 12.

The first client device 3 uses a personal computer. The first client device 3 may be a smartphone, a tablet terminal, or a wearable information terminal. The first client device 3 includes a control unit 30, a storage unit 31, a display unit 32, an operation unit 33, an audio input / output unit 34, a communication unit 35, and an imaging unit 36.

The control unit 30 is a processor using a CPU or GPU. The control unit 30 includes a processor such as a CPU or GPU, a memory, and the like. The control unit 30 may be configured as one piece of hardware (SoC: System On a Chip) in which a processor, a memory, a storage unit 31, and a communication unit 35 are integrated. The control unit 30 functions as a first client device 3 that executes a plurality of applications related to life data that can be transmitted / received to / from the life data server device 1 based on the application 3P stored in the storage unit 31.

The storage unit 31 includes a non-volatile memory such as a flash memory. The application 3P is stored in the storage unit 31. The storage unit 31 stores the data referred to by the control unit 30. The display unit 32 includes a display device such as a liquid crystal panel or an organic EL display. The operation unit 33 is an interface that accepts user operations, and includes physical buttons and a touch panel device with a built-in display. The operation unit 33 can accept an operation on the screen displayed on the display unit 32 by a physical button or a touch panel. The audio input / output unit 34 includes a speaker, a microphone, and the like. The voice input / output unit 34 includes a voice recognition unit, and can recognize the operation content from the input voice with a microphone and accept the operation.

The communication unit 35 is a wireless communication module that realizes transmission / reception of information to / from the life data server device 1 via the network N. The communication unit 35 may perform communication via the network N by wire using a network card.

The image pickup unit 36 includes an image pickup element such as a CMOS (Complementary MOS) image sensor. When the image pickup unit 36 is activated, it outputs an image captured by the image pickup element. The imaging unit 36 captures a still image or a moving image based on the instruction of the control unit 30.

Since the hardware configuration of the second client device 4 is the same as that of the first client device 3 and only the stored application 4P and the processing content based on the application 4P are different, the illustration and detailed description in FIG. 2 are omitted. However, the detailed processing procedure of the second client device 4 will be described later.

FIG. 3 is a schematic diagram of an example of life data stored in the storage device 110. FIG. 3 shows the life data just generated for one family (A family). For example, as shown in FIG. 3, the life data may be stored as a correspondence relationship between each data and the family identification information, or is generated as an instance in a structure such as a structure or class data for each family. May be done.

The life data shown in the correspondence relationship as shown in FIG. 3 includes family data and event data of each event. The family data includes the life data generation time, the number of members of the family, and the user information (name, contact address, attribute, etc.) of the members 1 and 2 who are initially partners in association with the family identification information. .. The family data includes the life event identification information given to the event data generated for each life event of the family in association with the family identification information. In family data, identification information of other families may be stored as related (relative) families.

Event data such as still images, moving images, texts, and sounds generated for each life event are stored in association with the event identification information. The event identification information may be uniquely assigned to each life event. The event data may include data for the app used for life events. As shown in FIG. 3, the event data may include information on other users who have participated in the life event. Information that identifies the category of the life event is associated with the life event of each family. The event data is stored in the storage device 110 together with the time information in association with the family identification information and the life event identification information.

As shown in FIG. 3, the generation of life data starts from the time of family formation, that is, the time when the service related to marriage preparation is started. For example, when a service provider that provides a wedding hall and a wedding planning service receives registration of user information including a name from a user who is preparing for marriage, it goes to the life data server device 1 via the second client device 4. Request the issuance of family identification information by specifying user information. Regarding the request, the life data server device 1 generates life data of a family including two users as members as shown in FIG. At this point, the life data includes user information for two members and identification information of a scheduled life event as shown in FIG. As event data, the unique life event identification information (unique to each event) of the event associated with the "wedding" category and the identification information of the staff of the planning service associated with the life event identification information. And are included.

In the life data processing system 100, instead of using the cloud storage so that the life data of each user can be shared among the members of the family, as shown in FIG. 3, the life data is stored and used in advance for each family. .. During a family separation event, allow some sharing between separated families. Event data can be stored in association with a real life event, and the service in that event can be linked and output to the family. Based on such family-based life data, it can be used as an application platform that cyclically supports the life of a family. Hereinafter, how to use the stored life data will be described with specific examples.

The business operator related to the planning service guides the user who visited the planning consultation to install the application 3P associated with the issued family identification information. When the application 3P is installed, the issued family identification information is stored in the storage unit 31 of the user's first client device 3. After that, the user will be able to use the Web application for consultation with the staff of the planning service, the Web application for schedule management, and the like based on the application 3P and the family identification information.

In the application 3P, the text input by the first client device 3, the still image or moving image captured by the imaging unit 36, the voice input by the voice input / output unit 34, and the like are input via the life data server device 1. A function of storing in the storage device 110 is included. That is, the user can use the storage device 110 as cloud storage for recording event data related to each life event via the application 3P.

The application 4P for the second client device 4 allows the service provider to use the Web application for supporting the provision of the service. For example, the service provider can use a Web application for sharing a message or schedule with a user, a Web application for posting an image, or the like according to the family identification information and the event identification information.

4 and 5 are flowcharts showing an example of a processing procedure executed by the life data processing system 100. The processing procedure shown in the flowcharts of FIGS. 4 and 5 is executed when a member of the family uses the application 3P.

When the first client device 3 is started to be used by starting the application 3P, the control unit 30 notifies the life data server device 1 of the family identification information stored in the storage unit 31 (step S301).

When the life data server device 1 receives the notified family identification information (step S101), the control unit 10 is scheduled based on the life data (family data) stored in association with the family identification information. The identification information of the life event is extracted (step S102).

In step S102, the control unit 10 extracts to propose a life event based on the planned life event (for example, a wedding ceremony), the number of years elapsed from the generation date and time of the family (at the time of family formation), and the composition of the members. It is preferable to do so. For example, when a wedding life event is scheduled, that is, when information such as a schedule is added and stored, the control unit 10 relates to life events such as "honeymoon" and "new life (search for a place to live)". Extract based on gender. The control unit 10 may extract the life event of the "anniversary" according to the number of years elapsed from the generation date and time of the family. The control unit 10 may extract the life event based on the history of the executed life event.

The control unit 10 transmits the extracted life event identification information to the first client device 3 as a response (step S103).

When the control unit 30 of the first client device 3 receives the response from the life data server device 1 (step S302), the control unit 30 displays an application screen including a life event selection screen based on the life event identification information included in the response. It is displayed on the display unit 32 (step S303), and the selection of the life event is accepted from the selection screen included in the application screen (step S304). Here, the control unit 10 may accept the display / non-display setting for the extracted life event depending on whether or not it is interested, so that only the life event that is of interest and the display is selected may be displayed thereafter. The display / non-display setting may be in family units or in user (member) units (first client device 3 units).

The control unit 30 transmits the identification information of the life event selected in step S304 to the life data server device 1 (step S305).

The control unit 10 of the life data server device 1 receives the identification information of the selected life event (step S104), and reads the event data stored in association with the received identification information of the life event from the storage device 110. (Step S105), the information indicating the Web application corresponding to the read event data is transmitted to the first client device 3 together with a part of the event data (step S106).

The control unit 30 of the first client device 3 receives information indicating the corresponding Web application (step S306), and displays an object (icon or the like) corresponding to the Web application group on the display unit 32 (Step S307).

The control unit 30 receives an upload request for event data such as text, still image, moving image, or voice in any of the displayed Web application groups (step S308), and the received text, still image, and moving image. Or, a data upload request in which event data such as voice is associated with the identification information of the life event corresponding to the selected Web application is transmitted to the life data server device 1 (step S309).

When the control unit 10 of the life data server device 1 receives the data upload request (step S107), the control unit 10 identifies the family to which the user belongs by identifying event data such as text, still image, moving image, or voice included in the data upload request. The information and the event data are stored in the storage device 110 in association with the identification information of the related life event (step S108).

In step S108, for example, the text of the message application regarding the preparation of the family life event “wedding”, the moving image, the still image, the sound, etc. regarding the family life event “wedding” are stored in the storage device 110.

At a timing different from step S308, the control unit 30 of the first client device 3 receives a download request for event data in the life event corresponding to the selected Web application (step S310). The control unit 30 transmits a download request to the life data server device 1 in association with the identification information of the family to which the user belongs and the identification information of the life event associated with the event data (step S311).

When the control unit 10 receives the data download request in the life data server device 1 (step S109), it is stored in the storage device 110 in association with the family identification information and the life event identification information included in the data download request. Event data is extracted (step S110), laid out on the display page, and transmitted to the first client device 3 (step S111).

When the control unit 30 of the first client device 3 receives the event data transmitted from the life data server device 1 (step S312), it displays it on the screen of the Web application (step S313) and ends the process. When transmitted as screen information (page) laid out appropriately, the control unit 30 may display an image or a moving image in the Web application based on the layout information.

FIG. 6 is a diagram showing a screen example based on the application 3P. FIG. 6A shows the main screen 330 based on the application 3P. On the main screen 330, an icon 331 for each life event that can provide a service to the A family is displayed. In the example of FIG. 6A, a Web application corresponding to a life event such as "wedding", "search for a new house", "new life procedure", and "travel" is displayed on the main screen 330 based on the newly generated life data shown in FIG. It is displayed. After the wedding is completed, the life event of "wedding" is not displayed on the main screen 330, and life events such as "travel" and "new life procedure" are displayed. Further, after several years have passed, life events such as "anniversary" and "childbirth" may be displayed on the main screen 330.

FIG. 6B is a display example when the “wedding” life event is selected. When the "wedding" life event is selected, the application screen including the message application, the schedule application, the costume rental application, the second party reservation and management application, the album, and the like is displayed. The message application displays the messages posted by designating the family identification information and the life event identification information in chronological order, and realizes message exchange between the members of the A family and the person in charge of planning. In the schedule app, regarding the wedding ceremony held at the ceremony hall reserved by Family A, the schedule of the procedures to be executed by each is displayed in an editable manner. The costume rental app allows you to exchange messages with the person in charge of costumes and select costumes. The album app allows you to share your wedding photos on a family-by-family basis. With the album app, you can also browse still images taken by professional photographers at weddings.

Each app can be used by family members to contact the person in charge of each app related to life events. Message exchange can be achieved by uploading and downloading text or images. The same applies to schedule data and the like.

In this way, the life data server device 1 can store the life data for each event in the family unit, process it appropriately, and read and output it, so that the application group related to the life event such as "wedding" can be stored in the family unit. Can be used.

The processing in the second client device 4 used by the business operator will be described. On the business side, processing is permitted only for the family identification information and the life event identification information to which the person in charge ID of each staff member is associated. When an inquiry message, a rental request, or the like is transmitted on the application selected by the first client device 3, the message is transmitted to the business operator corresponding to the application by the life data server device 1. By the processing of the business operator, the person in charge ID is stored as event data in association with the family identification information and the life event identification information together with the identification information of the service application provided by the business operator. The person in charge ID of the person in charge assigned at the actual window or the site of the meeting is the identification information of the family of the member participating in the meeting and the identification information of the life event after the fact on the life data server device 1. It may be stored in association with each other.

As a result, as shown in the event data of FIG. 3, a person in charge ID for each service content provided by the business operator in the life event is assigned. FIG. 7 is a flowchart showing an example of the processing procedure in the second client device 4.

When the person in charge of the service provided by the business operator uses the second client device 4, the person in charge ID (which may include the business operator ID) stored in the device is notified to the life data server device 1 (step S401). ..

When the control unit 10 of the life data server device 1 receives the notification of the person in charge ID from the second client device 4 (step S121), the life event identification information of the event data associated with the notified person in charge ID And the identification information of the family of life events identified by the life event identification information (step S122). The control unit 10 transmits the extracted life event identification information and the corresponding family identification information to the second client device 4 (step S123).

The second client device 4 receives the life event identification information of the life event and the family identification information extracted for the person in charge ID (step S402), and displays a list of life events corresponding to the life event identification information. (Step S403). In the list of life events, the name of the family corresponding to the identification information of the family may be displayed.

The second client device 4 accepts selection from the list of life events (step S404), and accepts upload of event data from the business operator for the selected life event (step S405). The second client device 4 transmits an upload request for event data such as a received message, still image, moving image, or voice to the life data server device 1 (step S406).

When the control unit 10 of the life data server device 1 receives the upload request from the second client device 4 of the business operator (step S124), the event data included in the upload request is combined with the family identification information and the life event identification information. In association with each other, the data is stored in the storage device 110 (step S125), and the process ends. In step S125, a message, a still image, or a moving image may be stored for each service of the person in charge ID.

As a result, the event data provided by the business operator (service provider) can also be downloaded from the first client device 3 used by the user by designating the event identification information. For example, a photographed image taken by a professional photographer is stored as family event data and can be viewed by family members. A viewing deadline may be set for each event data, and the control unit 10 of the life data server device 1 may respond to the download request by determining whether or not it is possible based on the deadline.

It is also possible to exchange messages and share data with a user who is not a member of the family but is a participant of the event by using the first client device 3. Participants of the event will be instructed by the family member or business operator who hosts the event to install the app 3P along with the family identification information and life event identification information. It is preferable that the family identification information and the life event identification information are converted into, for example, a two-dimensional code and easily obtained from an information terminal device equipped with a camera. Participants of the event can share specific data with the family only for the guided event by using the first client device 3 in which the application 3P is installed. FIG. 8 is a flowchart showing an example of a processing procedure in the first client device 3 used by the participants.

When a user who is a participant uses the first client device 3, the control unit 30 receives information for identifying each participant, for example, a participant's name, together with family identification information and life event identification information, and receives life data. Notify the server device 1 (step S321). In step S321, the control unit 30 may accept authentication information including a code known only to the participants or a code notified to a specific user by a member of the family.

The control unit 10 of the life data server device 1 receives the notification including the family identification information, the life event identification information, and the participant identification information (step S131), and responds to the family identification information and the event identification information. Refer to the event data to be performed, and confirm that the participant indicated by the identification information included in the notification is certainly a participant (step S132).

The control unit 10 transmits the information indicating the application for the participants confirmed in step S132 to the first client device 3 used by the participants as a response (step S133).

When the control unit 30 of the first client device 3 receives the response from the life data server device 1 (step S322), the control unit 30 displays an object corresponding to the application group on the display unit 32 based on the information indicating the application included in the response. Display (step S323).

The control unit 30 accepts the selection of one of the displayed Web applications by operating the object (step S324), and receives the data upload or data download request in association with the selected Web application (step S325). Is notified to the life data server device 1 (step S326).

When the control unit 10 of the life data server device 1 receives a data upload or data download request (step S134), the control unit 10 transmits event data such as text, still image, moving image, or voice to the identification information of the family to which the user belongs and the identification information of the family to which the user belongs. The event data is read / written to / from the storage device 110 in association with the identification information of the related life event (step S135). In addition, it is possible to control the access authority to the event data of the family by designating a specific participant in advance from the members of the family. The control unit 10 transmits the read / write result to the first client device 3 (step S136).

The control unit 30 of the first client device 3 receives the read / write result (step S327), displays it on the display unit 32 (step S328), and ends the process.

The above processing will be described with reference to a detailed example of a life event.
[Life event 1: Wedding]
As a starting point for life data, we will explain the processing related to interaction with service providers regarding support for holding weddings and second parties. As for "wedding", as described above, when a user who is preparing for a wedding consults with a service provider who provides a wedding hall and a wedding planning service, the service provider accepts registration. The life data server device 1 issues the identification information of the family having the user as a member via the second client device 4 of the service provider.

After that, family members will use the message app, costume rental app, and schedule app to provide wedding preparation support services from their respective businesses based on the family data and event data associated with the family identification information. Can receive. In the album app, a still image or a moving image taken by a professional photographer posted via the second client device 4, or a still image posted by a participant using the first client device 3 and the participant. , Or you can browse the moving image.

The control unit 10 of the life data server device 1 extracts a list of travel agencies associated with the wedding service provider from the wedding schedule based on the life data and the application data of each application, and sets it as a travel proposal. 1 It is also possible to transmit to the client device 3. The control unit 10 may control to create a honeymoon proposal and send a push notification from the travel application.

[Life Event 2: Childbirth / Childcare]
Service providers may include businesses that provide childbirth preparation information. The life data server device 1 extracts life events including "preparation for childbirth" by the number of years elapsed from the generation date and time of the family or the application search and selection in the first client device 3 (S102). When it is notified that the life event of "preparation for childbirth" is selected (S305), the life data server device 1 extracts "preparation for childbirth" as a scheduled life event and life event identification information. It is added to the family data in association with (“scheduled event” in FIG. 3).

After that, when a member of the family uses the first client device 3, the life events of "preparation for childbirth" and "childcare" can be selected by processing the flowcharts of FIGS. 4 and 5. For life events such as "preparation for childbirth" and "childcare", there are message apps with service providers or medical information providers that provide information on childbirth preparation, information search apps and album apps that specialize in "preparation for childbirth". Provided.

If a member of the family gives birth safely, he / she can request the life data server device 1 to register a new member (member 3, member 4, ...) Using the first client device 3. As a result, data such as name, gender, and date of birth are stored in the column of member 3 of the family data in FIG.

Based on the date of birth of a new member, that is, a member of the child generation, the control unit 10 of the life data server device 1 provides information such as a notification of the holding of an information exchange event related to childcare and a page for accepting applications for participation in the event. The data may be transmitted to the first client device 3 as related data. The information exchange event is a real event that only families registered at the facility managed by the service provider can participate, and the participating families of the event become a virtual "neighborhood" family in the app 3P. After that, it may be stored in the family data as a related family. You may apply to the life data server device 1 as a related family and store it in the family data only between the families you like. "Neighborhood" families may be able to exchange information with each other via specific apps. This can bring about the effect of sharing information between families and reducing the feeling of isolation between the family and the members of the family. It is also possible to extract the identification information of a family having similar life data on the life data server device 1 side and propose it as an information exchange partner.

Since still images and the like associated with the album application related to the growth of the members of the child generation up to that point are stored in the storage device 110 as family event data, a portfolio of child growth is created using those related data. , It is also possible to output.

Similarly, the control unit 10 of the life data server device 1 exchanges information on educational services such as childcare, school events, and private schools, and exchanges information on the shared album application according to the date of birth among the attributes of each member as the first client device. It is possible to send to 3 and upload or download event data using an application on the first client device 3.

[Life event 3: Fledging]
The service provider may include a business operator related to information providing services related to job hunting of the child generation, a business operator related to information providing services such as retirement plans of the parent generation, and “travel”. In this case, in the life data server device 1, the "fledged" of the child generation, etc., is based on the number of years elapsed from the generation date and time of the family, the age of each member, or the history of the executed events included in the family data. Life event is extracted (S102). As a result, for example, an application related to the information providing service related to "fledged" is displayed in a selectable manner on the first client device 3.

The members of the child generation may be managed as family data about the same person as the members of the new family are the same as the members of the new family when the members of the child generation form a new family. Event data for members of the parent generation's family data may be transferred or duplicated to the new family's family data. As a result, the family data continues for the life of one family, and at the same time, it branches with a parent-child relationship at each timing of the fledging of the child generation.

9 and 10 are diagrams showing an example of the contents of family data. Event data is omitted. FIG. 9 shows that the first generation family data shown in FIG. 3 corresponds to the subsequent increase in new members and also to the increase in completed events. FIG. 10 shows an example of the contents when the members of the child generation form a new family. The family data for the child generation family contains identification information for each member's parent generation family. This makes it possible to relate family data across generations. For example, it is also possible to transmit a proposal regarding a life event in a new family from an implemented event in the parent generation from the life data server device 1 to the first client device 3 used by a member of the child generation.

[Life event 4: End of life]
Service providers may include businesses related to "funerals" and "organization", and businesses related to information provision services. In this case, in the life data server device 1, the family "end of life" or based on the number of years elapsed from the generation date and time of the family, the age of each member, or the history of the executed events included in the family data. Extract life events such as "travel" (S102). As a result, for example, an application related to an information providing service such as "end of life" or "travel" is displayed in a selectable manner on the first client device 3.

Regarding the end of life, the control unit 10 of the life data server device 1 can also extract the activities of individual members in chronological order and output a historical chronology (portfolio) including moving images and the like.

In this way, the life data including the family data and the event data is continuously stored in association with the family identification information and the life event identification information. This life data can be used as a platform for applications of each business operator that supports life cyclically.

The embodiments disclosed as described above are exemplary in all respects and are not restrictive. The scope of the present invention is indicated by the scope of claims and includes all modifications within the meaning and scope equivalent to the scope of claims.

100 Life data processing system 1 Life data server device 10 Control unit 11 Storage unit 1P Life data processing program 110 Storage device 3 First client device (client device)
30 Control unit 31 Storage unit 3P application program (application)

Claims (5)

Includes a life data server device that processes life data in family units, and a client device that sends and receives data to and from the life data server device.
The life data server device is
The life data related to the life event is stored in the storage device in association with the family identification information given to the family unit at the family formation stage and the life event identification information for identifying the life event for each life event including the ceremonial occasion. Storage unit to memorize and
A life data processing system including a transmitter that transmits service information related to a life event to the client device based on the number of years since the formation of the family, attribute information of family members, or the history of life events. The life data processing system according to claim 1, wherein the life event includes a wedding ceremony, childbirth preparation, childcare, or a funeral. When a member of the child generation of a member of the family forms a new family, the identification information of the new family is given and the identification information of the new family is given.
The life data processing system according to claim 1, wherein the life data server device stores a parent-child relationship between family identification information in the storage device. The life data server device of a life data processing system including a life data server device that processes life data in a family unit and a client device that transmits and receives data to and from the life data server device.
The life data related to the life event is stored in the storage device in association with the family identification information given to the family unit at the family formation stage and the life event identification information for identifying the life event for each life event including the ceremonial occasion. Remember,
A life data processing method including a process of transmitting service information related to a life event to the client device based on the number of years since the formation of a family, attribute information of family members, or a history of life events. For computers that send and receive data to and from client devices
The life data related to the life event is stored in the storage device in association with the family identification information given to the family unit at the family formation stage and the life event identification information for identifying the life event for each life event including the ceremonial occasion. Processing to memorize and
A computer program that executes the process of sending service information related to a life event to a client device based on the number of years since the family was formed, the attribute information of family members, or the history of life events.

Images