Data Management Server
The data management server addresses the challenge of managing large volumes of video data by providing secure storage, access control, and sharing features, ensuring efficient data retrieval and posthumous distribution based on user preferences.
Patent Information
- Application Number
- JP2024008214
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-01-23
- Publication Date
- 2025-01-28
- Estimated Expiration
- 2044-01-23
AI Technical Summary
The management of large volumes of video data stored on servers for customized video services poses challenges in terms of data use and security, especially when accessing and sharing these data among members and facilities.
A data management server that allows for secure storage and management of member and facility information, including image files, with features for access control, ranking, search functions, partner sharing, and contact management, ensuring data safety and ease of retrieval based on user preferences and relationships.
Ensures secure access and efficient management of video data, enabling easy retrieval and sharing based on user preferences, while allowing for posthumous data distribution according to user wishes.
Smart Images

Figure 0007623046000001_ABST
Abstract
Description
[Technical field]
[0001] The technical field disclosed in this specification relates to a technology for managing data provided by members. [Background technology]
[0002] In recent years, with the development of video technology and communication technology, various video services using image files are being provided at events or ceremonies. For example, Patent Document 1 discloses a configuration in which image files provided by a user are stored in a server on the Internet in advance, and when the user dies, the image files stored in the server are used at the funeral. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2012-113702 A Summary of the Invention [Problem to be solved by the invention]
[0004] As mentioned above, recent advances in technology have made it possible for facilities nationwide that can provide video services to hold ceremonies customized for each user, using data that has been stored in advance on a server on the network. However, because the various data provided by users is stored on the server for a long period of time, the amount of data becomes enormous, and the use and management of this data becomes an issue. [Means for solving the problem]
[0005] The data management server, which has been developed to solve the above-mentioned problems, A data management server that manages information on facilities that can provide video services and information on members that can use the facilities, The data management server includes: A plurality of facilities and a plurality of members can be registered, and a member folder is provided as a storage area for each registered member; The data management server further comprises: storing basic information of the member and basic information of the facility, the basic information of the member including first area information indicating a location and destination information indicating a communication destination, and the basic information of the facility including second area information indicating a location and a type of video service that can be provided; The data management server further comprises: The functions available to the member include an image file management function, a facility search function, a partner function, and a contact management function; The facility has a function of transmitting facility information as a function that the facility can use, The data management server further comprises: The image file management function is capable of accepting provision of image files from a registered member, member A, storing the image files provided by member A in the member folder of member A, and further restricting access to the image files stored in the member folder of member A from anyone other than member A; The image file management function further includes a function for setting ranks for the plurality of image files stored in the member folder of the member A, and further includes a function for receiving a selection of a type of video service from the member A. When the selection of a type of video service is received, a number of image files having a higher rank are extracted from the image files stored in the member folder of the member A according to the selected type of video service. The data management server further comprises: The facility search function is capable of accepting a selection of search conditions from member A, and when a search instruction is accepted with the search conditions selected, a search is made for the registered facilities that satisfy the selected search conditions, and the search conditions can include information indicating a location and a type of video service, and when the information indicating a location is selected as the search conditions, the facility that matches the selected location is extracted based on at least one of the first area information and the second area information, and when the type of video service is selected as the search conditions, the facility that can provide the selected video service is extracted, The facility search function further allows at least one of the registered facilities to be registered as a favorite facility in association with the member A; The data management server further comprises: the facility information transmission function is capable of receiving the facility information from a facility X, which is a registered facility, and transmitting the facility information provided from the facility X to the member who has registered the facility X as a favorite facility, based on the destination information of the member; The data management server further comprises: In the partner function, a member B who is a registered member can be registered as a partner of the member A, and when the member B is registered as a partner of the member A, it is possible to allow the member B to access the image files stored in the member folder of the member A; The partner function further includes: if the member B is registered as the partner of the member A, it is possible to receive a notification of the death of the member A from the member B; and when the notification of the death of the partner of the member A is received, the death of the partner of the member A is registered; The data management server further comprises: The contact management function allows for the registration of contact information indicating a communication destination for contact from the member A in association with the member A, and further allows for the registered contact information to be divided into groups, and allows for communication to be made for each of the registered contact information or each of the groups; The contact management function is further capable of accepting will data provided by member A, storing the provided will data in the member folder of member A, and restricting access to the will data stored in the member folder of member A from any party other than member A, and associating the will data with at least one of the registered contact information, and when the death of member A is registered, transmitting the will data in the member folder of member A based on the associated contact information. It is characterized by the following.
[0006] According to the data management server disclosed in this specification, image files available for video services provided at registered facilities can be stored in a member folder to which access can be restricted for each registered member. Therefore, the safety of the image files can be guaranteed. Furthermore, by being able to set a rank for the stored image files, even if a large number of image files are stored, the image files can be easily extracted according to the type of video service, and the use of the stored image files can be promoted. Furthermore, it is possible to search for facilities that meet the member's desires, and further, by registering favorite facilities, the facility side can send facility provision information to the member. Furthermore, by registering another member as a partner, the stored image files can be shared with the partner member. Furthermore, by dividing the contact information into groups and registering them, the contacts can be selected for each group. Furthermore, will data can be associated with specific contact information and stored in the member folder, and after the death of a member, will data can be sent based on the specific contact information, and the will can be passed on to the person of the contact.
[0007] A control method for implementing the functions of the above-mentioned device, a computer program, and a computer-readable storage medium storing the computer program are also novel and useful. Effect of the Invention
[0008] According to the technology disclosed in this specification, in a system in which data provided by members is stored in a data management server on a network, a technology is realized for optimally utilizing and managing the data collected in the data management server. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a data storage system. [Diagram 2] FIG. 2 is a diagram showing detailed configurations of a facility and a data management server. [Diagram 3] FIG. 1 is a diagram showing a ceremony venue at a facility. [Figure 4] 13 is a diagram showing the structure of a folder for each member in the data management server. [Diagram 5] FIG. 13 is a diagram showing the structure of a contact file stored in a member's folder. [Figure 6] A diagram showing the structure of a will file stored in a member's folder. [Figure 7] FIG. 2 is a diagram showing the configuration of a member database. [Figure 8] FIG. 2 is a diagram showing the configuration of a facility database. [Figure 9] FIG. 4 is a diagram showing a list of functions of the data management server. [Figure 10] FIG. 2 is a diagram showing an overview of an image file management function. [Figure 11] FIG. 2 is a diagram showing an overview of a facility search function, a facility information transmission function, and a member information viewing function. [Figure 12] FIG. 1 is a diagram showing an overview of a contact management function. [Figure 13] FIG. 1 is a diagram showing an overview of a confidential information management function. [Figure 14]FIG. 13 is a diagram illustrating an overview of a request memo management function. [Figure 15] FIG. 13 is a diagram showing the flow of data stored in a member folder in the case where a partner is registered. [Figure 16] FIG. 13 is a diagram showing the flow of data stored in a member folder when a person is not registered as a partner. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] The data storage system according to the present embodiment will be described in detail below with reference to the attached drawings. The data storage system according to the present embodiment can register a plurality of facilities that can provide video services and a plurality of members that can use the facilities. The data storage system according to the present embodiment accepts various data such as image files from members, and stores and manages the various provided data in a data management server.
[0011] [Overall configuration of data storage system] The data storage system 100 disclosed in this specification, as shown in FIG. 1, has a data management server 1 capable of storing various types of data, and the data management server 1 is connected to a computer 2X in a facility 20X, a computer 2Y in a facility 20Y, a computer 3A of a member A, a computer 3B of a member B, and a computer 3C of a member C via a network 10 such as the Internet.
[0012] Facilities that can be registered in the data storage system 100 are located all over the country, and the number of registered facilities is not limited to two, facilities 20X and 20Y, but may be three or more. The computers 2X and 2Y of each facility may be the same model or different models, but they share the same configuration and functions required to use the data management server 1. In this specification, when the facility is not specified, it will be referred to as "facility 20," and when the facility's computer is not specified, it will be referred to as "facility computer 2."
[0013] The data management server 1 stores member information managed by an operating company that manages facilities 20 throughout the country, and is capable of communicating with computers 2 in facilities throughout the country. The data management server 1 also has a function as a web server, and is capable of transferring data to and from devices other than the facility's computer 2 via web pages provided by the web server. For this reason, for example, if member A, member B, and member C are registered as members of the facility (hereinafter, the members of the facility are simply referred to as "members"), and the personal computers (PCs) owned by each member are connected to the network 10, necessary data can be transferred to and from each member's PCs 3A, 3B, and 3C. In this specification, when a member's PC is not specified, it is described as "member's PC 3." In addition, the type of device for each member to access the data management server 1 is not limited to a PC, and may be any device capable of displaying a web page, such as a smartphone.
[0014] [Detailed configuration of facilities and data management server] Next, the detailed configuration of the facility 20 capable of providing video services and the data management server 1 will be described with reference to the block diagram of FIG.
[0015] [Facilities that can provide video services] 2, in addition to the facility computer 2, a projector 91, a display 92, and a speaker 93 are installed in the facility 20. The number of projectors 91, displays 92, and speakers 93 is not limited to one each, and may be multiple. In addition, the facility computer 2 is also not limited to one computer, and may be configured with multiple computers.
[0016] 3 shows an example of a funeral hall that is a ceremony venue in facility 20. Facility 20 is capable of providing various video services, and a ceremony venue is prepared for providing the video services. The ceremony venue shown in FIG. 3 is provided with a projection space 90 for projecting a 3D hologram, and a 3D image 91P is projected from a projector 91 onto the projection space 90. Furthermore, in the ceremony venue, seating areas for participants are provided surrounding projection space 90.
[0017] In addition, in the ceremony venue, flat displays 92A, 92B, 92C, 92D, and 92E corresponding to digital signage are arranged on the walls surrounding the projection space 90. The number of flat displays 92A, 92B, 92C, 92D, and 92E is not limited to five, and may be one or a number other than five. Each flat display 92A, 92B, 92C, 92D, and 92E may be the same model or different models, but they have the configuration and functions necessary for configuring the data storage system 100 in common. In this specification, when the display is not specified, it is described as "display 92".
[0018] The image displayed by the projector 91 is not limited to a 3D hologram, and may be, for example, an image produced by projection mapping. In this case, for example, a three-dimensional object to be projected is placed in the ceremony venue, and the projector 91 projects a mapping image onto the three-dimensional object. It may also be an image (such as a video or slide show) displayed on a screen. Furthermore, the display 92 is not limited to one compatible with digital signage, and may be one for displaying image data to be, for example, a funeral portrait. In other words, various image display means can be installed in the facility 20, and the video services that can be provided vary from facility to facility.
[0019] [Data Management Server] 2, the data management server 1 includes a controller 19 including a CPU 11 and a memory 12, a user interface (hereinafter, interface will be referred to as "IF") 13, and a communication IF 14, which are electrically connected to the controller 19. Note that the controller 19 in FIG. 2 is a general term for hardware and software used to control the data management server 1, and does not necessarily represent a single piece of hardware actually present in the data management server 1.
[0020] The CPU 11 executes various processes according to the programs read from the memory 12 and based on the operation of the operator. Various programs including an operating system (OS) and various data are stored in the memory 12. The buffer provided in the CPU 11 is also an example of a memory. An example of the memory 12 is not limited to a ROM, RAM, HDD, etc. built into the data management server 1, but may be a storage medium that is readable and writable by the CPU 11.
[0021] Specifically, the memory 12 of the data management server 1 is provided with a member folder for each member, which serves as a storage area for various data. For example, when member A, member B, and member C are registered, a member folder 50A for member A, a member folder 50B for member B, and a member folder 50C for member C are provided, as shown in FIG. 2. In this specification, when a member folder is not specified, it is described as a "member folder 50." The data management server 1 can restrict access to the member folder 50A from accounts other than member A's account. Access to the other member folders 50 can also be restricted from accounts other than those of the members corresponding to those member folders 50. The administrator of the data management server 1 may not be subject to this restriction.
[0022] 4, for example, image files 51, ranking data 52, contact files 53, request memos 54, will files 55, confidential data 56, comment data 57, shared setting data 58, and public setting data 59 can be stored in member folder 50. These data may be stored together in one member folder 50, or folders may be provided within member folder 50 for each of the above types of data, and data may be stored in each folder according to the type of data.
[0023] Image file 51 may be data that can be used in the video service that can be provided at facility 20, that is, data that can be displayed by projector 91 or display 92 installed at facility 20, and may be a still image file or a video file. A plurality of image files 51 can be stored in member folder 50. A member can store image files of turning points in life, such as Shichi-Go-San, entrance ceremonies, graduation ceremonies, weddings, childbirth, and 60th birthdays, in the member's member folder. Image file 51 may also be an image file that was specially photographed in a photography studio at facility 20.
[0024] The ranking data 52 is data that records the priority (rank) of the multiple image files 51 stored in the member folder 50, and the priority is set by the member. In this embodiment, it is text data in which file names are listed in order of priority, separated by line breaks or commas.
[0025] The contact file 53 is a file in which the addresses of attendees to be invited to ceremonies such as wedding receptions, memorial parties, funerals, and memorial services are registered. Specifically, the contact file 53 can include contact records 530 for each contact, such as contact record 530A for contact A, contact record 530B for contact B, contact record 530C for contact C, and contact record 530D for contact D, as shown in FIG. 5. Each contact record 530 includes a contact ID, a name, an address, a mobile phone number, and an email address. The contact ID is information for identifying the contact record. It is not necessary to input all of the address, mobile phone number, and email address, and it is sufficient to input at least one of them. It is to be noted that the email address in the contact record is an example of contact information.
[0026] Furthermore, contact file 53 can include contact groups 531, such as contact group 531A and contact group 531B, in which multiple contacts can be registered. Each contact group 531 includes a group ID and at least one contact ID that will be a member of the group. The group ID is information for identifying the group. The contact IDs included in a contact group indicate the contact IDs included in contact record 530.
[0027] The request memo 54 is data for recording requests regarding the ceremony. The request memo 54 is, for example, a text file, but there is no limit to the file format or the contents. A plurality of request memos 54 can be stored in the member folder 50. The request memo 54 is an example of request data.
[0028] The will file 55 is data that is restricted from being accessed from any account other than the member's own account, and is a file in which will data is registered that is to be automatically sent to a previously designated recipient after the death of the member is registered. Specifically, the will file 55 can include a will record 550 for each will data, such as a will record 550A for contact person A and a will record 550B for contact person B, as shown in FIG. 6. Each will record includes a will ID, will data, and recipient information. The will ID is information for identifying the will record 550. The will data is data indicating a message, photo, or video to be conveyed after death, or data used for video services such as 3D hologram data. The will data may be a URL or QR code indicating the storage destination of the file, in addition to data indicating the file itself to be sent. For example, if the will data is a QR code that stores the storage destination of 3D hologram data, the facility can provide a video service based on the 3D hologram data by having the QR code read by a reader at the facility. One will record 550 may include one or more will data. The recipient information indicates a contact ID included in the contact record 530 or a group ID included in the contact group 531. One will record 550 may contain one or more recipients.
[0029] The confidential data 56 is data to which access from any account other than the member's own account is restricted, and is data that is automatically sent to members registered as partners after the death of a member is registered. A plurality of confidential data 56 can be stored in the member folder 50. A member can store highly confidential personal information, such as a bank account number, securities number, cash card PIN, Internet account information, and various other passwords, as confidential data 56 in the member's folder.
[0030] The comment data 57 is data for adding a comment or a title to each image file 51 stored in the member folder 50. In the comment data 57, the comment content and each image file 51 are associated with each other.
[0031] The sharing setting data 58 is data that stores sharing settings for whether or not the image files 51, ranking data 52, contact files 53, request memos 54, and comment data 57 stored in the member folder 50 are shared with members registered as partners. In the case of image files 51, the sharing settings may be set for all image files 51 stored in the member folder 50, or for each individual image file 51. In the case of the contact file 53, the sharing settings may be set for all contact records 530 registered in the contact file 53, or for each individual contact record 530. In the case of the request memos 54, the sharing settings may be set for all request memos 54 stored in the member folder 50, or for each individual request memo 54.
[0032] The disclosure setting data 59 is data that stores a disclosure setting as to whether or not the image files 51 stored in the member folder 50 are to be made public to third parties after the death of the member. The disclosure setting may be set for all image files 51 stored in the member folder 50, or may be set for each individual image file 51.
[0033] Returning to the explanation of Fig. 2, the memory 12 of the data management server 1 is provided with a member folder 50, the access of which is restricted for each member, as well as a public folder 40, the access of which is not restricted compared to the member folder 50, as storage areas for various data. The public folder 60 can be accessed if a member is logged in to the data management server 1 with his / her account. It is not necessary to be logged in with a member's account, and the public folder 60 may be accessible via a browser from a computer that can access the data management server 1.
[0034] Furthermore, the memory 12 of the data management server 1 stores a member database (hereinafter, database is referred to as "DB") 70 that stores basic information about members, and a facility DB 80 that stores basic information about facilities.
[0035] The member DB 70 is a file in which a member record 71 for each member is registered. For example, as shown in Fig. 7, the member DB 70 can include a member record 71 for each member, such as a member record 71A for member A, a member record 71B for member B, and a member record 71C for member C.
[0036] Each member record 71 includes basic information and usage information of the member. The basic information of the member includes the member ID, name, date of birth, gender, residential area, address, mobile phone number, email address, and payment method. The basic information of the member is information that needs to be input when registering as a member. The member ID is information for identifying the member record. The residential area is information indicating an area divided by prefecture, city, town, village, etc. The residential area may be automatically set from the input address. It is not necessary to input all of the address, mobile phone number, and email address, and it is sufficient that at least one of them is input. The residential area of the member record 71 is an example of first area information. The email address of the member record 71 is an example of destination information.
[0037] The usage information is information that is appropriately input after a member is registered, and includes partner membership, sharing settings, favorite facilities, and selected video services. A member can register another member as a partner. The initial setting is that no partner is registered, and "no partner" is stored in the partner member field. In addition, it is possible to set whether or not various pieces of information in the member record 71 are shared with partner members. The role of partner members will be described later. The sharing settings may apply to all data written in the member record 71, or may be set for each individual piece of data.
[0038] Furthermore, members can register at least one of the registered facilities as a favorite facility. The favorite facility included in the usage information is an example of favorite information. In the initial setting, no favorite facilities are registered, and "no favorite facility" is stored in the favorite facility item. The role of the favorite facility will be described later. Furthermore, members can select one of multiple types of video services, and can register the selected type of video service as a selected video service. Types of video services include, for example, projection mapping, 3D hologram, funeral portrait, slide show, and digital signage. The role of the selected video service will be described later.
[0039] The facility DB 80 is a file in which a facility record 81 for each facility is registered. The facility DB 80 can include a plurality of facility records 81, such as a facility record 81X for facility X, a facility record 81Y for facility Y, etc., as shown in FIG.
[0040] Each facility record 81 includes basic information about the facility. The basic information about the facility includes a facility ID, name, residence area, address, telephone number, email address, homepage (HP) URL, and types of video services that can be provided. The basic information about the facility is information that needs to be input when registering the facility. The facility ID is information for identifying the facility record. The residence area is information that indicates an area divided by prefecture, city, town, village, etc., similar to the residence area of the member record 71. The residence area may be automatically set from the input address. It is not necessary to input all of the address, telephone number, email address, and HP URL, as long as at least one of them is input. The residence area of the facility record 81 is an example of second area information.
[0041] In addition, the memory 12 of the data management server 1 stores a web program 61 that functions as a web server and provides a web page. The member can access the member folder 50 corresponding to the logged-in user with the authority of the logged-in user by displaying the web page from a browser installed in the member's PC 3 and logging in to the data management server 1 from the web page. Through the web page, the member can provide, for example, new data (image file 51, contact record 530, wish memo 54, will record 550, confidential data 56), delete existing data, and edit existing data (member record 71, ranking data 52, comment data 57, shared setting data 58, public setting data 59). Through the web page, the member can register or cancel partner members, register or cancel favorite facilities, and select or cancel video services. On the other hand, the member cannot access the member folder 50 of members other than the member. Furthermore, those who are not members cannot access the member folder 50. In addition, a person who is not a member can register as a new member by inputting the necessary information via a web page provided by the web program 61, and when the person registers as a new member, a member folder 50 is created for that new member.
[0042] In this specification, when a member is able to access a member folder or data within a member folder, it means that when logged in with that member's account, the member folder or data within the member folder can be accessed.
[0043] The user IF 13 is, for example, a touch panel, and includes hardware for displaying a screen for notifying the user of information, and hardware for accepting operations by the user. Note that the user IF 13 may be a combination of a display and an operation unit such as a keyboard or a mouse.
[0044] The communication IF 14 includes hardware for communicating with external devices such as the facility computer 2 and the member's PC 3 via the network 10. The communication standards of the communication IF 14 are Ethernet (registered trademark), Wi-Fi (registered trademark), etc. The data management server 1 may be provided with multiple communication IFs 14 compatible with multiple communication standards.
[0045] The data management server 1 may be configured as one computer or as multiple computers. For example, the data management server 1 may be configured so that each function of the data management server 1, which will be described later, is executed by a different computer. Also, the computer that executes the functions of the data management server 1 and the storage that saves the files or data provided by the members may be separate devices.
[0046] [Data management server functions] Next, a description will be given of the functions of the data management server 1. As shown in Fig. 9, the functions of the data management server 1 include a member-oriented function 30 and a facility-oriented function 40. Each function is realized by the CPU 11 executing the function based on instructions from the member's PC 3 or the facility's computer 2.
[0047] Specifically, the data management server 1 has, as functions 30 for members, an image file management function 31, a facility search function 32, a contact management function 33, a confidential information management function 34, a request memo management function 35, and a partner function 36, and, as functions 40 for facilities, a facility information transmission function 41 and a member information viewing function 42. Each function will be explained below. In the following explanation, it is assumed that member A, member B, and member C are registered as members, facility X and facility Y are registered as facilities, member A and member B are registered as partner members, and member C does not have a partner registered.
[0048] [Image file management function] The image file management function 31, which is one of the member-oriented functions 30, will be described with reference to Fig. 10. The image file management function 31 is a function for managing image files 51 provided by members.
[0049] When logged in from PC3A with the account of member A, the data management server 1 can provide PC3A with a web page for uploading an image file 51 by a web program 61. PC3A displays the web page by a browser and accepts the selection of the image file 51 to be uploaded and an instruction to upload. Then, in response to accepting an instruction to upload with the image file 51 to be uploaded selected, PC3A uploads the selected image file 51 to the data management server 1. When the image file 51 is uploaded from PC3A, the data management server 1 saves the image file 51 in a member folder 50A for member A, who is the logged-in user. Note that a folder may be created for each type of video service in the member folder 50, and image files 51 may be stored for each type of video service.
[0050] Furthermore, when a user logs in from PC3A with the account of member A, the data management server 1 can provide PC3A with a web page for displaying a list of image files 51 stored in the member folder 50A for member A by using a web program 61. PC3A displays the web page by a browser and accepts the selection of image files 51 and a delete instruction or a download instruction. Then, in response to a delete instruction being input with one or more image files 51 selected, the data management server 1 deletes the selected image files 51 from the member folder 50A for member A. In response to a download instruction being input with one or more image files 51 selected, the data management server 1 transmits the selected image files 51 to the PC3 of member A.
[0051] Furthermore, when a user logs in from PC 3A with the account of member A, the data management server 1 can provide PC 3A with a web page for editing the ranking data 52 by the web program 61. PC 3A displays the web page by a browser and accepts editing of the ranking data 52, i.e., setting of the ranking (rank). For example, the data management server 1 accepts a selection of an image file 51 for which a ranking is to be set from among the image files 51 stored in the member folder 50A for member A, and accepts the setting of the ranking for the selected image file 51. Then, in response to the setting of the ranking for the selected image file 51, the data management server 1 saves the ranking data 52 in which the edited ranking is stored in the member folder 50A for member A, who is the logged-in user.
[0052] The ranking of the image files 51 does not need to be set for all image files 51 stored in the member folder 50, but may be set only for image files 51 with high priority among the image files 51 stored in the member folder 50A for member A. For example, member A selects 20 image files 51, sets the rankings of the 20 image files 51 from 1st to 20th, and saves the setting results as ranking data 52 in the member folder 50A for member A.
[0053] Furthermore, when member A's account is used to log in from PC 3A, data management server 1 can provide PC 3A with a web page for selecting a type of video service by web program 61. PC 3A displays the web page by a browser and accepts the selection and setting instruction of the type of video service. Then, in response to input of a setting instruction with a type of video service selected, data management server 1 refers to member DB 70 and writes the selected type of video service into member record 71A of member A.
[0054] Furthermore, when member A sets the ranking of image files 51 and selects the type of video service, data management server 1 becomes able to create a preview file corresponding to the selected video service, which is the selected video service, and becomes able to provide PC 3A with a web page for receiving an instruction to create the preview file by web program 61. Then, when the instruction to create the preview file is received, data management server 1 creates a preview file and provides PC 3A with the created preview file. The data management server 1 may request a facility or a video service production company to create the preview file, and may receive the preview file from the facility or production company. Then, data management server 1 may transmit the created preview file to PC 3A, or may provide PC 3A with a web page capable of playing the created preview file by web program 61.
[0055] The type or number of image files 51 used in the preview file varies depending on the type of video service. For example, if the selected video service is a funeral portrait, the image file 51 used is one photo file. Therefore, the data management server 1 extracts the photo file with the highest priority based on the ranking data 52 from the member folder 50A of member A, and creates a preview file using the extracted photo file. If the selected video service is a slide show, 3D hologram, or digital signage, multiple image files 51 can be used, and both photo files and video files can be used. Therefore, the data management server 1 extracts a predetermined number of image files 51 with high rankings based on the ranking data 52, which is determined in advance according to the type of video service, and creates a preview file using the extracted image files 51. When a facility or a video service production company is requested to create a preview file, the extracted image file 51 is passed to the facility or the video service production company.
[0056] Furthermore, when member A sets the ranking of image files 51 and selects the type of video service, data management server 1 becomes capable of accepting a request to create the selected video service, which is the selected video service, and becomes capable of providing PC 3A with a web page for accepting the request to create the selected video service by web program 61. Then, upon accepting the request to create the selected video service, data management server 1 produces the video service. As with the preview file, the production of the video service may be requested from the data management server 1 to a facility or a video service production company, and the facility or production company may produce the video service. When the production of the video service is requested to a video service production company, the extracted image file 51 is passed to the facility or video service production company.
[0057] When a video service production company or a facility management company receives a request from data management server 1 to create a preview file or produce a video service, the video service production company or the facility management company creates the preview file or data required to implement the video service using the delivered image files 51. For example, if there is a request to produce projection mapping, the video service production company or the facility management company receives the required number of image files 51 depending on the mapping target, and creates data to be used for the projection mapping production using the image files 51.
[0058] In addition, requests for the production of video services can be made not only by member A, but also by partner member B, a facility. Therefore, for example, after the death of member A, a video service that uses image files 51 stored in member folder 50A of member A, such as a video service to be used for member A's funeral, can be requested by both a partner member and a facility.
[0059] Furthermore, when extracting the image file 51, the data management server 1 refers to the comment data 57, and if a comment has been added to the extracted image file 51, the data management server 1 also extracts the comment. This allows the comment to be reflected in the preview file and data required for implementing the video service.
[0060] Furthermore, when a user logs in from PC3B with the account of member B and an image file 51 that is permitted to be shared by registered partner member A is in the member folder 50A for member A, the data management server 1 can provide PC3B with a web page for viewing the image file 51 by the web program 61. On the other hand, when a user logs in from PC3C with the account of member C, the data management server 1 does not provide PC3C with a web page for viewing the image file 51 stored in the member folder 50A for member A. In other words, the data management server 1 allows member B, who is registered as a partner member, to view the image file 51 stored in the member folder 50A for member A if sharing is permitted, but does not allow member B, who is registered as a partner member, or member C, who is not a partner member, to view the image file 51 if sharing is not permitted.
[0061] Furthermore, when the death of member A is registered, the data management server 1 refers to the public setting data 59 and stores the image file 51 that is set to be public in the public folder 60. At this time, the original image file 51 stored in the member folder 50A for member A may be deleted from the member folder 50A for member A, or may be left there. The public folder 60 may or may not be further divided into folders for each member. Furthermore, when comment data 57 is associated with the image file 51 stored in the public folder 60, the comment data 57 may also be stored in the public folder 60.
[0062] This image file management function 31 allows the image file 51 provided by member A to be stored in the member folder 50A of member A, and further restricts access to the image file 51 from anyone other than member A, thereby allowing the image file 51 to be appropriately managed. In addition, by being able to set a rank for the image file 51 stored in the member folder 50, even if a large number of image files 51 are stored, the number of image files 51 according to the type of video service can be easily extracted. For example, when a close relative of member A (e.g., a member registered as a partner) needs to prepare image files such as photographs for the funeral of member A after the death of member A, the image file 51 provided by member A is set to a rank, so that the possibility of implementing a video service that meets member A's desire increases. In addition, the image file 51 set to be public is stored in the public folder 60 after the death of the member is registered, and the image file 51 of the member is made public so that it can be freely viewed, providing an opportunity for people other than the member to learn more about the member's life in a more understandable and in-depth manner.
[0063] Furthermore, this image file management function 31 allows members to store image data representing various scenes in their lives (weddings, graduation ceremonies, etc.) and important things (souvenirs and hobby items) in the data management server 1, and to reproduce those scenes at any time by reading the image data into their own computers, allowing them to preserve many memories and providing a service for the members' end of life preparations after retirement. In addition, the facility 20 can realize an environment like a memorial hall for the member by reading the image files 51 according to the ranking data 52. The image files 51 provided by the members are managed in a unified manner by the data management server 1. Therefore, the image files 51 can be read from anywhere in the country and used for the video services that the facility 20 can provide.
[0064] [Facility search function, facility information transmission function, and member information viewing function] The facility search function 32, which is a member-oriented function 30, and the facility information transmission function 41 and member information viewing function 42, which are facility-oriented functions 40, will be described with reference to Fig. 11. The facility search function 32 is a function that enables members to search for facilities and obtain facility information. The facility information transmission function 41 is a function that enables facilities to issue facility information to members. The member information viewing function 42 is a function that enables facilities to view part of their members' information.
[0065] When logged in from PC3A with the account of member A, the data management server 1 can provide PC3A with a web page for searching facilities by the web program 61. PC3A displays the web page by a browser and accepts the search conditions for facilities. The search conditions for facilities include, for example, "any residence area," "video service," and "near the member." For example, if the search condition is "any residence area," facilities in the residence area selected by the member are searched for. If the search condition is "video service," facilities that can provide the video service selected by the member are searched for. If the search condition is "near the member," facilities whose residence area is the same as the member's residential area are searched for. A plurality of search conditions may be combined. When the search conditions are input from PC3A, the data management server 1 refers to the facility DB 80, extracts facilities that match the search conditions, and provides a web page for displaying the extraction results. PC3A displays the web page by a browser.
[0066] The search results for facilities include basic information about the facility (name, address, telephone number, etc.), the types of video services the facility can provide, and the URL of its website. PC3A displays this information so members can learn more about the facility.
[0067] Furthermore, when the user logs in from the PC3A with the account of member A, the data management server 1 can provide the PC3A with a web page for registering a favorite facility by the web program 61. The PC3A displays the web page by a browser and accepts the selection of a favorite facility from among the facilities registered in the facility DB80. When a registration instruction is input from the PC3A with one facility selected, the data management server 1 writes the selected facility as a favorite facility in the member record 71A of member A in the member DB70. Furthermore, the number of facilities registered in the member record 71A of member A as a favorite facility is not limited to one, and multiple facilities may be registered as favorite facilities. If a favorite facility has already been registered in the member record 71A of member A, the selected facility may be overwritten or registered as another favorite facility. Furthermore, the data management server 1 may have a function of canceling the registration of a favorite facility when a favorite facility has already been registered.
[0068] When logged in from a computer 2X of facility X using an account of facility X, the data management server 1 can provide the computer 2X with a web page for uploading facility information by using a web program 61. The computer 2X displays the web page by a browser and accepts the selection and issue instruction of the facility information to be uploaded. The computer 2X can create facility information for announcing or advertising an event held by the facility, and uploads the selected facility information to the data management server 1 in response to accepting an instruction to transmit the facility information with one of the created facility information selected.
[0069] When facility information is uploaded from computer 2X, data management server 1 refers to member DB 70 and transmits the facility information to the email addresses of members who have facility X registered in their favorites.
[0070] The destination of the facility information is not limited to the members registered as favorites. For example, the destination may be a member in the same residential area as the residence area of facility X. Also, the destination of the facility information may be selected to be the members registered as favorites or the members in the same residential area.
[0071] The data management server 1 also manages whether or not to permit the facility to view member information such as the personal information of the member stored in the member DB 70 and the files stored in the member folder 50 for each member. For example, when the data management server 1 is logged in from the computer 2X of the facility X with the account of the facility X, the data management server 1 permits the computer 2X to view the date of birth, age, sex, and selected video service of the personal information of the member for the member who lives in the same residential area as the facility X. This allows the facility X to use this information for marketing. However, the name and address are not disclosed, so the individual is not identified. Also, for members who have the facility X registered as a favorite, the data management server 1 permits the name, date of birth, age, sex, address, telephone number, email address, and selected video service of the personal information of the member to be viewed, and further permits the request memo 54 to be viewed among the files stored in the member folder 50. For members who have the facility X registered as a favorite, the name and address are disclosed, so the facility X can identify the individual. This allows the facility X to use this information to propose suitable video services to each member who has registered the facility X as a favorite. It should be noted that the request memo 54 may be permitted to be viewed even for facilities that are not registered as favorites. Alternatively, the request memo 54 may be permitted to be viewed if a setting as to whether or not to permit viewing is accepted, and if viewing is permitted, viewing of the facilities may also be permitted.
[0072] Furthermore, when logged in from PC3B with member B's account and partner-registered member A has permitted sharing of favorite facilities, the data management server 1 can provide PC3B with a web page for viewing information on member A's favorite facilities by the web program 61. On the other hand, when logged in from PC3C with member C's account, the data management server 1 does not provide PC3C with a web page for viewing information on member A's favorite facilities. In other words, the data management server 1 allows member B, who is registered as a partner member, to view information on member A's favorite facilities if sharing is permitted, but does not allow member B, who is not a partner member, to view the information if sharing is not permitted, or member C, who is not a partner member.
[0073] The facility search function 32 allows members to easily select facilities suitable for the video services they desire. The facility information transmission function 41 allows facilities to transmit facility information to members who are likely to request video services, and members can also obtain facility information from facilities that are likely to request video services. The member information viewing function 42 allows facilities to carry out appropriate marketing activities.
[0074] [Contact management function] The contact management function 33, which is one of the member-oriented functions 30, will be described with reference to Fig. 12. The contact management function 33 is a function for managing information indicating contact information provided by members.
[0075] When member A's account is logged in from PC 3A, the data management server 1 can provide PC 3A with a web page for editing the contact file 53 by the web program 61. PC 3A displays the web page by a browser and accepts editing of the contact file 53, i.e., registration of a new contact record 530, and editing or deletion of an existing contact record 530. When the data management server 1 receives an instruction from PC 3A regarding editing of the contact file 53, it updates the contact file 53 in accordance with the instruction.
[0076] Furthermore, when the user logs in from the PC3A with the account of member A, the data management server 1 can provide the PC3A with a web page for sending e-mail by the web program 61. The PC3A displays the web page by a browser and accepts input of the contents to be sent by e-mail and selection of the destination. The destination is selected from among the contact records 530 registered in the contact file 53. Multiple destinations may be selected. In addition to individual contact records 530, contact groups 531 may also be selected as destinations. Then, in response to the input of the contents to be sent by e-mail and selection of the destination on the web page being accepted, the data management server 1 sends an e-mail of the input contents to be sent to the selected destination. When the contact's computer receives the e-mail, the contents to be sent can be displayed by an application program such as a mailer.
[0077] Furthermore, when member A logs in from PC3A with his / her account, the data management server 1 can provide PC3A with a web page for editing the will file 55 by the web program 61. PC3A displays the web page by a browser and accepts editing of the will file 55, i.e., registration of a new will record 550, and editing or deletion of an existing will record 550. When the data management server 1 receives an instruction from PC3A regarding editing of the will file 55, it updates the will file 55 in accordance with the instruction.
[0078] Furthermore, when the death of member A is registered, the data management server 1 refers to the will file 55, and automatically sends an e-mail including the will data to a specified destination according to the contents registered in each will record 550. When the computer of the contact indicated in the destination receives the e-mail, it can display the contents of the transmission using an application program such as a mailer.
[0079] Furthermore, when a user logs in from PC3B using the account of member B and a contact record 530 that is permitted to be shared by registered partner member A is in member A's contact file 53, the data management server 1 can provide PC3B with a web page for viewing the contact record 530 by the web program 61. On the other hand, when a user logs in from PC3C using the account of member C, the data management server 1 does not provide PC3C with a web page for viewing the contact record 530 in member A's contact file 53. In other words, the data management server 1 allows member B, who is registered as a partner member, to view the contact record 530 in member A's contact file 53 if sharing is permitted, but does not allow member B, who is registered as a partner member, or member C, who is not a partner member, to view the contact record 530 if sharing is not permitted.
[0080] The method of sending messages and data from the data management server 1 is not limited to email, but may be, for example, short messages or various messenger services.
[0081] This contact management function 33 allows the member A's contact file 53 to be edited, and furthermore, by restricting access to the contact record 530 of the member A's contact file 53 from anyone other than the member A, the image file can be appropriately managed. Also, by registering will data in advance and sending the will data to a pre-specified address after the death of the member A, it is possible to send messages, etc. that the member A wishes to convey after his or her death.
[0082] [Confidential information management function] The secret information management function 34, which is one of the functions 30 for members, will be described with reference to Fig. 13. The secret information management function 34 is a function for managing secret data 56 provided by members.
[0083] When member A's account is logged in from PC 3A, the data management server 1 can provide PC 3A with a web page for uploading secret data 56 by a web program 61. PC 3A displays the web page by a browser and accepts the selection of a file to be saved as secret data 56. Then, in response to accepting the upload instruction, PC 3A uploads the selected file to the data management server 1. When the file is uploaded from PC 3A, the data management server 1 saves the file as secret data 56 in a member folder 50A for member A.
[0084] Furthermore, when member A's account is logged in from PC 3A, the data management server 1 can provide PC 3A with a web page for displaying a list of secret data 56 stored in member A's member folder 50A by using the web program 61. PC 3A displays the web page by a browser and accepts selection of secret data 56 to be deleted. Then, in response to input of a deletion instruction on the web page, the data management server 1 deletes the selected secret data 56 from member A's member folder 50A.
[0085] Furthermore, when the death of member A is registered, the data management server 1 automatically transmits an e-mail including the secret data 56 to member B who is registered as a partner. The PC 3B of member B can receive the secret data 56 by receiving the e-mail.
[0086] It should be noted that the secret data 56 only needs to be viewable by member B, who is the partner of member A, after the death of member A, and the data management server 1 may not send the secret data 56 by email, but may send, for example, a URL of the storage destination of the secret data 56, and when the URL is accessed while logged in from PC3B with member B's account, the secret data 56 can be made viewable. Furthermore, after the death of member A is registered, the data management server 1 may notify member B, who is the partner of member A, of the existence of the secret data 56 by email or the like, and may not restrict access to the secret data 56 from member B.
[0087] This secret information management function 34 makes it possible to store the secret data 56 provided by member A, and furthermore, by restricting access to the secret data 56 from anyone other than member A, the secret data 56 can be appropriately managed. Furthermore, after the death of member A, the secret data 56 is automatically sent to member B who is registered as a partner, so that member B can use the secret data 56 for sorting after the death.
[0088] [Request memo management function] The request memo management function 35, which is one of the member-oriented functions 30, will be described with reference to Fig. 14. The request memo management function 35 is a function for managing request memos 54 provided by members.
[0089] When member A's account is logged in from PC 3A, the data management server 1 can provide PC 3A with a web page for uploading a request memo 54 by the web program 61. PC 3A displays the web page by a browser and accepts the selection of a file to be saved as the request memo 54. Then, in response to accepting the upload instruction, PC 3A uploads the selected file to the data management server 1. When the file is uploaded from PC 3A, the data management server 1 saves the file as the request memo 54 in the member folder 50A for member A.
[0090] Furthermore, when member A's account is logged in from PC 3A, the data management server 1 can provide PC 3A with a web page for displaying a list of request notes 54 stored in member A's member folder 50A by using the web program 61. PC 3A displays the web page by a browser and accepts the selection of the request note 54 to be deleted. Then, in response to a deletion instruction being input on the web page, the data management server 1 deletes the selected request note 54 from member A's member folder 50A.
[0091] Furthermore, when a request memo 54 that is permitted to be shared by a registered partner member A is in the member folder 50A for member A, the data management server 1 can provide a web page for viewing the request memo 54 to PC3B by the web program 61 when the data management server 1 is logged in from PC3B with the account of member B, and the request memo 54 is in the member folder 50A for member A and permitted to be shared by the registered partner member A. On the other hand, when a request memo 54 is logged in from PC3C with the account of member C, the data management server 1 does not provide a web page for viewing the request memo 54 stored in the member folder 50A for member A to PC3C. In other words, the data management server 1 allows the request memo 54 stored in the member folder 50A for member A to be viewed by member B, who is registered as a partner member, if sharing is permitted, but does not allow the request memo 54 to be viewed by member B, who is registered as a partner member, or member C, who is not a partner member, if sharing is not permitted.
[0092] Furthermore, when a user logs in from a computer 2X of facility X using an account for facility X, and when member A has registered facility X as a favorite facility and a request note 54 for which sharing is permitted is in the member folder 50A for member A, the data management server 1 can provide the computer 2X with a web page for viewing the request note 54 by the web program 61. On the other hand, when a user logs in from a computer 2Y of facility Y using an account for facility Y, the data management server 1 does not provide the computer 2Y with a web page for viewing the request note 54 stored in the member folder 50A for member A. In other words, if sharing is permitted for the request note 54 stored in the member folder 50A for member A, the data management server 1 allows viewing from facility X registered as a favorite facility, but does not allow viewing from facility Y which is not a favorite facility.
[0093] This request memo management function 35 makes it possible to store the request memo 54 provided by member A, and furthermore, by limiting access to the request memo 54 to member A, member A's partners, or member A's favorite facilities, the request memo 54 can be appropriately managed. For example, partner members can view the request memo 54, allowing member A's requests to be shared with partner members. In addition, favorite facilities can view the request memo 54, allowing the facilities to customize video services to meet member A's requests.
[0094] [Partner Features] As an explanation of the partner function 36, which is a function 30 for members, the flow of data from partner settings to the member folder 50 will be explained with reference to Fig. 15. The partner function 36 is a function for sharing data stored in the member folder 50 with members who are registered as partners.
[0095] For member A to register member B as a partner, first, member A and member B register themselves as members with each other (P1). Specifically, each member accesses the data management server 1 from their PC 3, requests membership registration, and enters basic information into the data management server 1, whereby the member's member record 71 is registered in the member DB 70 and the membership registration is completed. As a result, a member folder 50 is provided in the data management server 1 for each of member A and member B, and various files or data, such as image files 51, can be uploaded.
[0096] Next, member A sends member B an invitation email to become partners (P3), and member B approves becoming partners based on the invitation email (P4), whereby member B is registered as member A's partner. Specifically, member A's PC 3A inputs a command to the data management server 1 to request member B to become a partner, and the data management server 1 sends an invitation email to member B. This invitation email contains a link for inputting a command as to whether or not to approve member A's becoming a partner. If a command to approve is input, member B is registered as member A's partner, and if a command to disapprove is input, member B is not registered as member A's partner. In addition, when member B inputs a command as to whether or not to approve, an email indicating the result is sent to member A.
[0097] In addition, when member B is registered as member A's partner, member A may be automatically registered as member B's partner, or member B may be asked whether or not to register member A as a partner, and the decision as to whether or not to register member A may be made based on the result of the inquiry.
[0098] When partner registration is complete, member B can view (P6) any image files 51, ranking data 52, contact files 53, and request memos 54 that have been uploaded (P5) by member A and saved in folder 50 for member A and that are permitted to be shared. In addition, member B can view (P6) any member record 71A of member A that is permitted to be shared.
[0099] In addition to the partner function 36, part of the basic information of member A can be viewed from the computer 2X of facility X (P7). In addition, when facility X is registered as a favorite facility by member A, the request memo 54 saved in the folder 50 for member A can be viewed from the computer 2X of facility X (P7).
[0100] Thereafter, when member A dies, for example, member B notifies the data management server 1 of member A's death (P11). For example, the data management server 1 provides a web page for inputting a death notification by web program 61, and a death notification command is input from member B's PC 3B using that web page. Alternatively, the death notification may be received by a close relative of member A via telephone call or the like.
[0101] When the data management server 1 is notified of the death of member A, it executes a process to confirm the death of member A (P12). For example, a death confirmation notification is sent to facility X, which is registered as a favorite facility of member A, and the death is confirmed by a response from facility X. When the death of member A is confirmed, the death of member A is registered.
[0102] When the death of member A is registered, the will data is sent to the registered contact information based on the will file 55 stored in the folder 50 for member A (P13). In addition, the secret data 56 stored in the folder 50 for member A is sent to member B, who is his partner (P14).
[0103] Furthermore, when the death of member A is registered, for example, facility X, which is registered as a favorite facility, receives a request to produce a video service from member B, who is registered as a close relative or partner of member A. The facility that receives the production request obtains the number of image files 51 required for the video service selected by member A from folder 50 for member A (P15), and becomes able to implement the video service using those image files 51 (P16).
[0104] This partner function 36 allows various information or files provided by member A to be shared, and enables member B to check the video services, etc. desired by member A. For example, partner members can view image files 51 and ranking data 52, allowing partner member B to suggest the content of video services to member A. Partner members can also view contact files 53, allowing partner member B to suggest the addition of guests, etc. to member A.
[0105] In the data storage system of this embodiment, a member may or may not register a partner. The flow of data stored in a folder for member C in the case of member C who does not have a registered partner will be described with reference to FIG. 16. Note that the same processes as those shown in FIG. 15 are denoted by the same reference numerals. Also, it is assumed that member C has registered facility X as a favorite facility.
[0106] First, member C registers as a member (P1). As a result, a folder 50 for member C is created in the data management server 1, and various files or data such as an image file 51 can be uploaded. Member C does not register a partner.
[0107] The image file 51, ranking data 52, contact file 53, and request memo 54 uploaded by member C (P5) and saved in the folder 50 for member C cannot be viewed by anyone other than member C, in principle. However, the request memo 54 can be viewed from facilities registered as favorite facilities (P7).
[0108] The data management server 1 can also accept a death notice of a registered member (P10). For example, the data management server 1 provides a web page for inputting a death notice by the web program 61, and the death notice of member C is accepted using the web page when logged in with the account of one of the members. The death notice may also be accepted by phone call from a close relative of member C.
[0109] When the data management server 1 receives the notification of the death of member C, it executes a process to confirm the death of member C (P12). Note that, because confirmation of the death can also be received from persons other than partner members, the process may include more steps than notification from partner members. For example, in addition to sending a death confirmation notification to facility X, which is registered as a favorite facility of member C, a confirmation notification may also be sent to the member who made the death notification.
[0110] When the death of member C is registered, the will data is sent to the registered contacts based on the will file 55 stored in the folder 50 for member C (P13). On the other hand, if the partner is not registered, the secret data 56 is not sent.
[0111] In addition, when the death of member C is registered, facility X, which has been registered as a favorite facility, becomes able to download the number of image files 51 required for the video service selected by member C from folder 50 for member C (P15), and becomes able to provide the video service using those image files 51 (P16).
[0112] As described above in detail, according to the data management server 1 of this embodiment, the image files 51 available for the video service provided at the facility 20 can be stored in the member folder 50 to which access can be restricted for each member, and the image files 51 stored can be ranked, so that even if a large number of image files 51 are stored, the image files 51 can be easily extracted according to the type of video service. In addition, the facility 20 that meets the desires of the member A can be searched for, and by registering a favorite facility, the facility can send facility information to the member A. In addition, by registering the member B as a partner member, the image files 51 stored in the member folder 50A of the member A can be shared with the member B. In addition, by grouping and registering the email addresses of contacts in the communication file 53, the contacts can be selected for each group. In addition, by storing the will record 550 in which the will data is associated with a specific email address in the will file 55, the will data can be sent to the specific email address after the death of the member A. As a result, in a data storage system 100 that stores data provided by members in a data management server 1 on a network 10, files or data collected in the data management server 1 can be suitably used or managed.
[0113] It should be noted that the present embodiment is merely an example and does not limit the present invention in any way. Therefore, the present invention can be modified and improved in various ways without departing from the scope of the present invention. For example, in the embodiment, access to files or data stored in the member folders 50 of the data management server 1 is restricted from accounts other than those of the members corresponding to each member folder 50 and their partner members, but access from accounts with administrator privileges does not need to be restricted.
[0114] In the embodiment, the data management server 1 stores an image file 51 indicating an image (still image or video) to be projected or displayed on the projector 91 or display 92 in the facility 20. The data indicating an image here includes data indicating audio, and audio can be played along with the image during playback, but the data management server 1 may store only the data indicating audio in addition to the image file 51. In this case, it is not limited to the data indicating audio itself, and it may be configured to store, for example, only the title of a song, and the song data is downloaded from a server having the song data when playback of the song is selected.
[0115] Furthermore, in the embodiment, when the data management server 1 receives a request from member A to create a selected video service, it extracts image files 51 according to the ranking data 52 and starts creating the video service, but for example, in the case of a video service to be used for a funeral, although member A may request this before he or she dies, in most cases the video service will be created after the death of member A. Therefore, after the death of member A is registered, the data management server 1 may automatically transmit the selected video service and image files 51 extracted according to the ranking data 52 to the facility registered in the favorites. Alternatively, the image files 51 may be extracted and transmitted in response to a request from the facility registered in the favorites.
[0116] In the embodiment, the usage information of each member (partner member, shared settings, favorite facilities, selected video services) is included in the member record 71 and stored in the member DB 70, but may be stored in the member folder 50.
[0117] In addition, in the embodiment, examples of confidential data include bank account numbers, securities numbers, cash card PIN numbers, Internet account information, and various other passwords, and if these are registered as will data, they can be sent to people other than partner members after the member's death.
[0118] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as ASIC, or a combination of these. The processes disclosed in the embodiments may be realized in various forms, such as a recording medium having a program for executing the processes recorded thereon, or a method. [Explanation of symbols]
[0119] 1 Data management server 2 Facility Computers 3. Member's PC 50 Members' Folder 51 Image files 52 Ranking Data 53 Contact File 54 Request Memo 55 Will File 56 Confidential Data 61 Web Programs 70 Member Database 71 Membership Records 80 Facility Database 100 Data Storage System
Claims
1. A data management server that manages information on facilities that can provide video services and information on members that can use the facilities, The data management server includes: A plurality of facilities and a plurality of members can be registered, and a member folder is provided as a storage area for each registered member; The data management server further comprises: storing basic information of the member and basic information of the facility, the basic information of the member including first area information indicating a location and destination information indicating a communication destination, and the basic information of the facility including second area information indicating a location and a type of video service that can be provided; The data management server further comprises: The functions available to the member include an image file management function, a facility search function, a partner function, and a contact management function; The facility has a function of transmitting facility information as a function that the facility can use, The data management server further comprises: The image file management function is capable of accepting provision of image files from a member A who is a registered member, storing the image files provided by the member A in the member folder of the member A, and further restricting access to the image files stored in the member folder of the member A from any party other than the member A, The image file management function further includes a function for setting ranks for the plurality of image files stored in the member folder of the member A, and further includes a function for receiving a selection of a type of video service from the member A, and when the selection of a type of video service is received, a function for extracting a number of image files with a higher rank that is determined according to the type of the selected video service from among the image files stored in the member folder of the member A, The data management server further comprises: The facility search function can accept a selection of search conditions from the member A, and when a search instruction is accepted with the search conditions selected, the facility that satisfies the selected search conditions is searched for from among the registered facilities, and the search conditions can include information indicating a location and a type of video service, and when the information indicating the location is selected as the search conditions, the facility that matches the selected location is extracted based on at least one of the first area information and the second area information, and when the type of video service is selected as the search conditions, the facility that can provide the selected video service is extracted, The facility search function further allows the member A to register at least one of the registered facilities as a favorite facility in association with the member A; The data management server further comprises: the facility information transmission function is capable of receiving the facility information from a facility X that is a registered facility, and transmitting the facility information provided from the facility X to the member who has registered the facility X as a favorite facility, based on the destination information of the member; The data management server further comprises: In the partner function, a member B who is a registered member can be registered as a partner of the member A, and when the member B is registered as a partner of the member A, the member B can be permitted to access the image files stored in the member folder of the member A, The partner function further includes: if the member B is registered as the partner of the member A, it is possible to receive a notification of the death of the member A from the member B; and when the notification of the death of the partner of the member A is received, the death of the partner of the member A is registered; The data management server further comprises: The contact management function allows for the registration of contact information indicating a communication destination for contact from the member A in association with the member A, and further allows for the registered contact information to be divided into groups, and allows for communication to be made for each of the registered contact information or each of the groups; The contact management function is further capable of accepting will data provided by member A, storing the provided will data in the member folder of member A, and restricting access to the will data stored in the member folder of member A from any party other than member A, and further capable of associating the will data with at least one of the registered contact information, and when the death of member A is registered, transmitting the will data in the member folder of member A based on the associated contact information. A data management server comprising:
2. 2. The data management server according to claim 1, The data management server includes: The image file management function allows a user to set whether or not to share the image files stored in the member folder of the member A with a partner; The data management server further comprises: In the partner function, among the image files stored in the member folder of the member A, the image files set to be shared are not restricted from being accessed by the member B who is registered as a partner, and the image files set not to be shared are restricted from being accessed by the member B. A data management server comprising:
3. 2. The data management server according to claim 1, The data management server further comprises: The function available to the member is a function for managing confidential information; The confidential information management function is capable of accepting confidential information provided by the member A, storing the provided confidential information in the member folder of the member A, and restricting access to the confidential information stored in the member folder of the member A from anyone other than the member A before the death of the member A is registered, and not restricting access to the confidential information from the member B who is registered as a partner after the death of the member A is registered. A data management server comprising:
4. 2. The data management server according to claim 1, The data management server includes: In the partner function, when the member A registers the member B as a partner, a partner invitation notification is sent to the member B based on the destination information of the member B, and when an operation for approval is received from the member B based on the invitation notification, the member B is registered as the partner of the member A. A data management server comprising:
5. 2. The data management server according to claim 1, The data management server includes: In the facility search function, a setting can be made as to whether or not to share favorite information indicating the favorite facility with a partner; In the partner function, when the favorite information registered in association with the member A is set to be shared, access from the member B registered as a partner is not restricted, and when the favorite information is set not to be shared, access from the member B is restricted. A data management server comprising:
6. 2. The data management server according to claim 1, The data management server includes: The contact management function allows a user to set whether or not to share the contact information associated with the member A; In the partner function, the contact information associated with the member A and registered is set to be shared, but access from the member B registered as a partner is not restricted for the contact information that is set not to be shared, and access from the member B is restricted for the contact information that is set not to be shared. A data management server comprising:
7. 2. The data management server according to claim 1, The data management server includes: The facility has a function for viewing member information as a function that the facility can use, The member information viewing function allows a part of the registered member information to be viewed from the facility X. A data management server comprising:
8. 8. The data management server according to claim 7, The data management server includes: In the member information viewing function, the member information that can be viewed from the facility X can be viewed in detail in the case of the member who has registered the facility X as the favorite facility, compared with the member who has not registered the facility X as the favorite facility. A data management server comprising:
9. 2. The data management server according to claim 1, The data management server includes: In the image file management function, when a selection of a type of video service is received from the member A, preview data corresponding to the selected video service, the preview data being capable of displaying the plurality of image files extracted from the member folder of the member A, is provided to the member A. A data management server comprising:
10. 2. The data management server according to claim 1, The data management server includes: The function available to the member is a request data management function; The request data management function is capable of accepting request data in which requests to facilities are written from the member A, storing the accepted request data in the member folder of the member A, and further restricting access to the request data stored in the member folder of the member A from facilities other than the favorite facilities associated with the member A, and not restricting access from the favorite facilities associated with the member A. A data management server comprising:
11. 11. The data management server according to claim 10, The data management server includes: The desired data management function allows a user to set whether or not to share the desired data stored in the member folder of the member A with a partner; In the partner function, among the requested data stored in the member folder of the member A, the requested data set to be shared is not restricted from being accessed by the member B who is registered as a partner, and the requested data set to not be shared is restricted from being accessed by the member B. A data management server comprising:
12. 2. The data management server according to claim 1, The data management server includes: The image file management function allows a setting as to whether or not the image files stored in the member folder of the member A are to be made public, and on condition that the death of the member A is registered, the image files set to be made public are stored in a public folder which has no access restrictions compared to the member folder. A data management server comprising:
Citation Information
Patent Citations
System for emergency situations
JP2012003738A
Funeral media providing system and method therefor
JP2012113702A
Data storage system
JP2013050943A