Data management method and data management system

The data management method and system streamline data access in data lakes by allowing terminal devices to identify and download necessary data using attribute lists or user IDs, addressing inefficiencies in data retrieval and personnel changes.

JP7748925B2Active Publication Date: 2025-10-03MITSUBISHI ELECTRIC BUILDING SOLUTIONS CORP
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2022165502
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-10-14
Publication Date
2025-10-03
Estimated Expiration
2042-10-14

AI Technical Summary

Technical Problem

Data utilization personnel in different departments struggle to efficiently identify and access necessary data within a data lake due to large volumes of data, requiring time-consuming manual confirmation with data administrators.

Method used

A data management method and system that allows terminal devices to interact with a data lake by sending attribute lists or user IDs to identify and download specific data names and access keys, enabling direct data access without manual intervention.

Benefits of technology

Facilitates easy and efficient data retrieval within a data lake, reducing time and effort for data utilization personnel and accommodating personnel transfers and personal tasks within organizations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007748925000001
    Figure 0007748925000001
  • Figure 0007748925000002
    Figure 0007748925000002
  • Figure 0007748925000003
    Figure 0007748925000003
Patent Text Reader

Abstract

To provide a data management method and a data management system that allow a person in charge of utilizing data to easily acquire necessary data in a data lake.SOLUTION: A terminal device transmits, to a data lake, an attribute list of an application of a department that uses the terminal device. The data lake refers to a data catalog, identifies data names of one or more pieces of data having an attribute list that is coincident with the attribute list of the application, and transmits the one or more data names to the terminal device. The terminal device selects desired one or more data names from among the received one or more data names, and transmits the desired one or more data names to the data lake. The data lake transmits, to the terminal device, one or more access keys to access the received one or more data names. The terminal device uses the received one or more access keys to download desired data from the data lake.SELECTED DRAWING: Figure 7
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present disclosure relates to a data management method and a data management system. [Background technology]

[0002] Recently, as a way to utilize information within a company, progress has been made in building data lakes, which are systems for storing data from all departments in a single data area and utilizing the data.

[0003] Patent Document 1 describes a data lake that stores multiple pieces of product-related data generated for each product in multiple production lines equipped with at least one piece of manufacturing equipment. This data lake has a data management server that registers the version of the manufacturing equipment in the production line for each product and manages access permission granting rules for granting access permissions to the versions, and an access control server that controls access permissions based on the access permission granting rules. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2022-035602 Summary of the Invention [Problem to be solved by the invention]

[0005] The data utilization applications used by data users in each department are selected from commercially available general-purpose applications depending on the purpose, and as a result, there will be multiple data utilization applications for each department and division within the company.

[0006] A data catalog is provided so that data in the data lake can be used (referenced) from the data utilization applications of each department. The data catalog contains the table of contents and index information for each piece of data in the data lake. Data utilization personnel in each department refer to the data catalog to select the data they want to use and download the data in the data lake to their data utilization applications.

[0007] However, because data lakes contain large amounts of data, data utilization personnel cannot determine whether the data is necessary just by looking at the contents of the data catalog, and must therefore confirm the contents with the data lake's data administrator, which is time-consuming.

[0008] Therefore, an object of the present disclosure is to provide a data management method and a data management system that allow data utilization personnel to easily obtain the necessary data within a data lake. [Means for solving the problem]

[0009] The data management method disclosed herein is a data management method for a terminal device to access data stored in a data lake, and includes the steps of: the terminal device launching an application of a department using the terminal device in accordance with a user's instructions; the terminal device sending an attribute list of the application of the department using the terminal device to the data lake; the data lake receiving the attribute list of the application; the data lake referring to a data catalog to identify data names of one or more data having an attribute list that matches the attribute list of the application; the data lake sending the one or more data names to the terminal device; the terminal device receiving the one or more data names; the terminal device selecting one or more desired data names from the one or more received data names; the terminal device sending the one or more desired data names to the data lake; the data lake receiving the one or more data names; the data lake sending one or more access keys to the terminal device for accessing the one or more received data names; the terminal device receiving the one or more access keys; and the terminal device downloading the desired data from the data lake using the one or more received access keys.

[0010] The data management method disclosed herein is a data management method for a terminal device to access data stored in a data lake, and includes the steps of: the terminal device launching an application of a department using the terminal device in accordance with a user's instructions; when the application is launched by a special user, the terminal device sending the special user's ID to the data lake; the data lake receiving the special user's ID; and, if the received special user's ID is registered in the special user list, the data lake identifying one or more data names that the special user can access; and the data lake sending the one or more data names to the terminal device. the terminal device receiving one or more data names; the terminal device selecting one or more desired data names from the one or more received data names; the terminal device transmitting the one or more desired data names to the data lake; the data lake receiving one or more data names; the data lake transmitting one or more access keys to the terminal device for accessing the one or more received data names; the terminal device receiving one or more access keys; and the terminal device downloading the desired data from the data lake using the one or more received access keys. [Effects of the Invention]

[0011] According to the present disclosure, data utilization personnel can easily obtain the necessary data within the data lake. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing the configuration of a data management system. [Figure 2] 1 is a diagram showing the configuration of a data lake 1 according to a first embodiment. [Figure 3] 10(a), 10(b), and 10(c) are diagrams showing the data body stored in the data body storage unit 14. FIG. [Figure 4] FIG. 1 is a diagram illustrating an example of a data catalog. [Figure 5] 2 is a diagram showing the configuration of a terminal device 2 according to the first embodiment. FIG. [Figure 6] 10(a), 10(b), and 10(c) are diagrams showing examples of application information. [Figure 7] 3 is a flowchart showing the processing procedure of a data management method by the data management system according to the first embodiment. [Figure 8] FIG. 10 is a diagram showing the configuration of a data lake 1A according to a second embodiment. [Figure 9] 10 is a diagram showing an example of a special user list stored in a special user list storage unit 19. FIG. [Figure 10] FIG. 11 is a diagram showing the configuration of a terminal device 2A according to a second embodiment. [Figure 11] 10 is a flowchart showing the processing steps of a data management method performed by a data management system according to a second embodiment. [Figure 12] FIG. 11 is a diagram showing the configuration of a data lake 1B according to a third embodiment. [Figure 13] FIG. 11 is a diagram showing the configuration of a terminal device 2B according to a third embodiment. [Figure 14] 11 is a flowchart showing the processing steps of a data management method performed by a data management system according to a third embodiment. [Figure 15] FIG. 10 is a diagram showing the configuration of a data lake 1C according to a fourth embodiment. [Figure 16] FIG. 10 is a diagram showing an example of a personal task target list. [Figure 17] 10 is a flowchart showing the processing procedure of a data management method by a data management system according to a fourth embodiment. [Figure 18] FIG. 2 is a hardware configuration diagram of a data lake and a terminal device. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments will be described with reference to the drawings.

[0014] Embodiment 1 1 is a diagram showing the configuration of a data management system. The data management system includes a data lake 1 and terminal devices 2-1 to 2-n. In the following description, the terminal devices 2-1 to 2-n may be collectively referred to as terminal device 2. For example, a terminal device 2 may be provided for each department.

[0015] FIG. 2 is a diagram illustrating the configuration of the data lake 1 according to the first embodiment.

[0016] The data lake 1 includes a communication unit 11, a data catalog storage unit 12, an access key storage unit 13, a data body storage unit 14, a data name identification unit 15, an access key identification unit 16, and a download control unit 17.

[0017] The communication unit 11 communicates with the terminal device 2 .

[0018] The data body storage unit 14 stores the data body. Figures 3(a), (b), and (c) are diagrams showing the data body stored in the data body storage unit 14. The data body includes a data name, a data ID, and data.

[0019] The data catalog storage unit 12 stores a data catalog. FIG. 4 is a diagram showing an example of a data catalog. The data catalog includes a data name, a data ID, and a list of data attributes. The attributes include business, function, and region. Business indicates the business in which the data is used, and corresponds to "elevators" or "air conditioning," etc. Function indicates the function in which the data is used, and corresponds to "personnel" or "maintenance," etc. Region indicates the region in which the data is used, and corresponds to "nationwide" or "Kansai," etc.

[0020] The data name identification unit 15 refers to the data catalog stored in the data catalog storage unit 12 and identifies the data name of one or more pieces of data having an attribute list that matches the attribute list of the application received from the terminal device 2.

[0021] The access key specifying unit 16 specifies one or more access keys for accessing data with one or more data names, and reads out one or more access keys stored in the access key storage unit 13 .

[0022] The access key storage unit 13 stores an access key required to download the data body stored in the data body storage unit 14.

[0023] The download control unit 17 controls the download of the data body from the data body storage unit 14 to the terminal device 2 .

[0024] FIG. 5 shows a configuration of the terminal device 2 according to the first embodiment.

[0025] The terminal device 2 includes a communication unit 21, a display unit 22, an application storage unit 23, an application information storage unit 24, a data storage unit 25, an application execution unit 26, an application attribute list identification unit 27, a data name selection unit 28, and a download control unit 29.

[0026] The communication unit 21 communicates with the data lake 1.

[0027] The display unit 22 displays the screen of the application.

[0028] The application storage unit 23 stores applications (software) of the department that uses the terminal device 2.

[0029] The application execution unit 26 executes an application for the department that uses the terminal device 2, which is stored in the application storage unit 23, in accordance with a user's instruction.

[0030] The application information storage unit 24 stores application information. Figures 6(a), (b), and (c) are diagrams showing examples of application information. The application information includes the application's function, the department using the application, and a list of application attributes. The application's function corresponds to data analysis, etc. The application's department corresponds to "Tokyo Branch, Elevator Department, Design Section," etc. The application's attribute list includes business, function, and region. The business represents the business in which the application is used, and corresponds to "elevator" or "air conditioning," etc. The function represents the function in which the application is used, and corresponds to "personnel" or "maintenance," etc. The region represents the region in which the application is used, and corresponds to "nationwide" or "Kansai," etc.

[0031] The application attribute list specifying unit 27 reads the application information from the application information storage unit 24 to specify the attribute list of the application currently being executed.

[0032] The data name selection unit 28 selects one or more desired data names from among one or more data names received from the data lake 1 in accordance with an instruction from the user of the terminal device 2.

[0033] The download control unit 29 controls the download of the data body in the data lake 1 to the terminal device 2 .

[0034] The data storage unit 25 stores the data body downloaded from the data lake 1.

[0035] FIG. 7 is a flowchart showing the processing procedure of the data management method according to the data management system of the first embodiment.

[0036] In step S101, the application execution unit 26 of the terminal device 2 starts an application of the department that uses the terminal device 2, which is stored in the application storage unit 23, in accordance with an instruction from the user.

[0037] In step S102, the application attribute list specifying unit 27 of the terminal device 2 specifies the attribute list of the application being executed by reading the application information from the application information storage unit 24. The communication unit 21 transmits the application attribute list to the data lake 1.

[0038] In step S103, the communication unit 11 of the data lake 1 receives the application attribute list.

[0039] In step S104, the data name identification unit 15 of the data lake 1 refers to the data catalog stored in the data catalog storage unit 12 and identifies the data names of one or more pieces of data having an attribute list that matches the attribute list of the received application. For example, the data name identification unit 15 may identify the data names of one or more pieces of data having an attribute list that matches all of the business, function, and region in the attribute list of the application. However, if there is an item in the business, function, or region in the attribute list of the data in the data catalog that is not defined, the data name identification unit 15 may unconditionally determine that the item matches. For example, if the application's attribute list lists the business as "elevator," the function as "design," and the region as "Tokyo," and the data's attribute list lists the business as "elevator," the function as "none," and the region as "none," it is determined that the application's attribute list and the data's attribute list match.

[0040] In step S105, the communication unit 11 of the data lake 1 transmits one or more data names to the terminal device 2.

[0041] In step S106, the communication unit 21 of the terminal device 2 receives one or more data names.

[0042] In step S107, the data name selection unit 28 of the terminal device 2 selects one or more desired data names from the received one or more data names in accordance with an instruction from the user of the terminal device 2.

[0043] In step S108, the communication unit 21 of the terminal device 2 transmits one or more desired data names to the data lake 1.

[0044] In step S109, the communication unit 11 of the data lake 1 receives one or more data names.

[0045] In step S110, the access key identification unit 16 identifies one or more access keys for accessing data with one or more data names, and reads out one or more access keys stored in the access key storage unit 13. The communication unit 11 of the data lake 1 transmits the one or more access keys to the terminal device 2.

[0046] In step S111, the communication unit 21 of the terminal device 2 receives one or more access keys.

[0047] In step S112, the download control unit 29 of the terminal device 2 and the download control unit 17 of the data lake 1 use one or more access keys to control the download of the data body stored in the data body storage unit 14 of the data lake 1 to the terminal device 2. The download control unit 29 of the terminal device 2 stores the received data body in the data storage unit 25.

[0048] According to this embodiment, when a person in charge uses a data lake, the person in charge can save time and effort in selecting the necessary data from the data catalog.

[0049] Embodiment 2 Even in large companies, work is not completely divided organizationally, and some work is still tied to individuals. One reason for this is that when employees are transferred to a new department or restructured, they continue to carry out work from their previous department. Therefore, even if applications are introduced for each department or division, they do not support work tied to individuals who have been transferred.

[0050] In this embodiment, a system is provided that allows employees (called special users) who have been transferred from other departments and have personal tasks to view data from their previous department via applications used by their current department. This allows the special users to utilize data necessary for work in their previous department by using applications from their current department.

[0051] FIG. 8 is a diagram showing the configuration of a data lake 1A according to the second embodiment.

[0052] The difference between the data lake 1A of embodiment 2 and the data lake 1 of embodiment 1 is that the data lake 1A of embodiment 2 has a data name identification unit 15A that is different from that of embodiment 1, and has a special user list storage unit 19 instead of the data catalog storage unit 12.

[0053] The special user list storage unit 19 stores a special user list. The special user list defines the data name and data ID of accessible data corresponding to a user ID. FIG. 9 is a diagram showing an example of a special user list stored in the special user list storage unit 19. For example, the data name of data accessible to a special user with user ID "1234" is defined as "Elevator Contract" and the data ID is defined as "34333eddf3."

[0054] The data name specification unit 15A refers to the special user list stored in the special user list storage unit 19 and specifies the data names of one or more pieces of data that can be accessed by the special user of the user ID received from the terminal device 2B.

[0055] FIG. 10 is a diagram showing the configuration of a terminal device 2A according to the second embodiment.

[0056] The terminal device 2A of embodiment 2 differs from the terminal device 2 of embodiment 1 in that the terminal device 2A of embodiment 2 is equipped with a special user ID identification unit 37 instead of the application information storage unit 24 and the application attribute list identification unit 27.

[0057] If the user using the application is a special user, the special user ID identification unit 37 identifies the user ID of the user. The user ID used when logging in to the terminal device or application can be used to identify the user using the application.

[0058] FIG. 11 is a flowchart showing the processing procedure of the data management method according to the data management system of the second embodiment.

[0059] In step S201, the application execution unit 26 of the terminal device 2A starts an application stored in the application storage unit 23 for the department that uses the terminal device 2A, in accordance with an instruction from the user.

[0060] In step S202, if the user using the application is a special user, the special user ID identification unit 37 of the terminal device 2A identifies the user ID of the special user. The communication unit 21 transmits the user ID to the data lake 1.

[0061] In step S203, the communication unit 11 of the data lake 1A receives the user ID.

[0062] In step S204, the data name identification unit 15A of the data lake 1A refers to the special user list stored in the special user list storage unit 19, and identifies the data names of one or more pieces of data that can be accessed by the special user of the received user ID. For example, when the received user ID is "1234", the data name identification unit 15 refers to the special user list and identifies the data name "elevator contract" of the data that can be accessed by the user with the user ID "1234".

[0063] In step S205, the communication unit 11 of the data lake 1A transmits one or more data names to the terminal device 2A.

[0064] In step S206, the communication unit 21 of the terminal device 2A receives one or more data names.

[0065] In step S207, the data name selection unit 28 of the terminal device 2A selects one or more desired data names from the received one or more data names in accordance with an instruction from the user of the terminal device 2A.

[0066] In step S208, the communication unit 21 of the terminal device 2A transmits one or more desired data names to the data lake 1A.

[0067] In step S209, the communication unit 11 of the data lake 1A receives one or more data names.

[0068] In step S210, the access key identification unit 16 identifies one or more access keys for accessing data with one or more data names, and reads out one or more access keys stored in the access key storage unit 13. The communication unit 11 of the data lake 1 transmits the one or more access keys to the terminal device 2A.

[0069] In step S211, the communication unit 21 of the terminal device 2A receives one or more access keys.

[0070] In step S212, the download control unit 29 of the terminal device 2A and the download control unit 17 of the data lake 1A use one or more access keys to control the download of the data body stored in the data body storage unit 14 of the data lake 1A to the terminal device 2A. The download control unit 29 of the terminal device 2A stores the received data body in the data storage unit 25.

[0071] According to this embodiment, when personnel changes occur within an organization, it is possible to eliminate the need to change the settings of the data lake access rights of the person who has been transferred.

[0072] Embodiment 3 FIG. 12 is a diagram showing the configuration of a data lake 1B according to the third embodiment.

[0073] The difference between the data lake 1B of embodiment 3 and the data lake 1 of embodiment 1 is that the data lake 1B of embodiment 3 has a data name identification unit 15B that is different from that of embodiment 1, and has a special user list memory unit 19.

[0074] The special user list storage unit 19 stores the special user list.

[0075] The data name specification unit 15B specifies the data names of one or more pieces of data having an attribute list that matches the attribute list of the received application, by referring to the data catalog stored in the data catalog storage unit 12. The data name specification unit 15B specifies the data names of one or more pieces of data that can be accessed by the special user of the received user ID, by referring to the special user list stored in the special user list storage unit 19.

[0076] FIG. 13 is a diagram showing the configuration of a terminal device 2B according to the third embodiment.

[0077] The terminal device 2B of the third embodiment differs from the terminal device 2 of the first embodiment in that the terminal device 2B of the third embodiment includes a special user ID specifying unit 37.

[0078] If the user using the application is a special user, the special user ID identification unit 37 identifies the user ID of the user.

[0079] FIG. 14 is a flowchart showing the processing procedure of the data management method according to the data management system of the third embodiment.

[0080] In step S301, the application execution unit 26 of the terminal device 2B starts an application stored in the application storage unit 23 for the department that uses the terminal device 2B, in accordance with an instruction from the user.

[0081] In step S302, the application attribute list identification unit 27 of the terminal device 2B identifies the attribute list of the running application by reading application information from the application information storage unit 24. If the user using the application is a special user, the special user ID identification unit 37 of the terminal device 2B identifies the user ID of the special user. The communication unit 21 transmits the application attribute list and the user ID of the special user to the data lake 1B.

[0082] In step S303, the communication unit 11 of the data lake 1B receives the application attribute list and the user ID of the special user.

[0083] In step S304, the data name identification unit 15B of the data lake 1B refers to the data catalog stored in the data catalog storage unit 12 to identify the data names of one or more pieces of data having an attribute list that matches the attribute list of the received application. The data name identification unit 15B of the data lake 1B refers to the special user list stored in the special user list storage unit 19 to identify the data names of one or more pieces of data that can be accessed by the special user of the received user ID.

[0084] In step S305, the communication unit 11 of the data lake 1B transmits one or more data names to the terminal device 2B.

[0085] In step S306, the communication unit 21 of the terminal device 2B receives one or more data names.

[0086] In step S307, the data name selection unit 28 of the terminal device 2B selects one or more desired data names from the received one or more data names in accordance with an instruction from the user of the terminal device 2B.

[0087] In step S308, the communication unit 21 of the terminal device 2B transmits one or more desired data names to the data lake 1B.

[0088] In step S309, the communication unit 11 of the data lake 1B receives one or more data names.

[0089] In step S310, the access key identification unit 16 identifies one or more access keys for accessing data with one or more data names, and reads out one or more access keys stored in the access key storage unit 13. The communication unit 11 of the data lake 1B transmits the one or more access keys to the terminal device 2B.

[0090] In step S311, the communication unit 21 of the terminal device 2B receives one or more access keys.

[0091] In step S312, the download control unit 29 of the terminal device 2B and the download control unit 17 of the data lake 1B use one or more access keys to control the download of the data body stored in the data body storage unit 14 of the data lake 1B to the terminal device 2. The download control unit 29 of the terminal device 2B stores the received data body in the data storage unit 25.

[0092] According to this embodiment, it is possible to obtain the same effects as those of the first and second embodiments.

[0093] Embodiment 4 Even if a person in charge is transferred, the person may continue to perform tasks that cannot be handled by the personnel of the previous department alone. As a result, the person in charge may be hindered in his / her work in the new department. In this embodiment, a system is provided for detecting the occurrence of personal tasks that are not the responsibility of the organization, thereby making it possible to attempt to eliminate personal tasks.

[0094] FIG. 15 is a diagram showing the configuration of a data lake 1C according to the fourth embodiment.

[0095] The data lake 1C of the fourth embodiment differs from the data lake 1B of the third embodiment in that the data lake 1C of the fourth embodiment includes a personal business target person list creation unit 59.

[0096] 16 is a diagram showing an example of a personal task target list, which includes the user IDs of special users.

[0097] FIG. 17 is a flowchart showing the processing procedure of the data management method according to the data management system of the fourth embodiment.

[0098] In step S401, the personal task target list creation unit 59 of the data lake 1C creates a personal task target list made up of the user IDs of the special users stored in the special user list storage unit 19.

[0099] In step S402, the communication unit 11 of the data lake 1C transmits the personal task target list to the terminal device 2B used by the personnel department.

[0100] In step S403, the communication unit 21 of the terminal device 2B used by the personnel department receives the personal task target list.

[0101] According to this embodiment, it is possible to discover personnel who are subject to personal tasks and promote the creation of an organization that is easy to reform.

[0102] The data lake and terminal device described in the first to fourth embodiments can be configured with corresponding operations implemented by digital circuit hardware or software. When the data lake and terminal device are implemented using software, these devices can include, for example, a processor 1001 and a memory 1002 connected by a bus 1003, as shown in FIG. 1, and the processor 1001 can execute a program stored in the memory 1002.

[0103] [Note] The above-described embodiment is a specific example of the following additional notes.

[0104] (Appendix 1) A data management method for a terminal device to access data stored in a data lake, comprising: a step of launching an application of a department using the terminal device in accordance with an instruction from a user; The terminal device transmits an attribute list of applications of a department using the terminal device to the data lake; receiving, by the data lake, a list of attributes of the application; The data lake refers to a data catalog to identify a data name of one or more pieces of data having an attribute list that matches an attribute list of the application; the data lake transmitting the one or more data names to the terminal device; receiving, by the terminal device, the one or more data names; a step of the terminal device selecting one or more desired data names from the received one or more data names; the terminal device transmitting one or more desired data names to the data lake; the data lake receiving the one or more data names; The data lake sends one or more access keys to the terminal device for accessing the one or more received data names; receiving, by the terminal device, the one or more access keys; A data management method comprising a step in which the terminal device downloads desired data from the data lake using the one or more received access keys.

[0105] (Appendix 2) 2. The data management method of claim 1, wherein the attribute list includes business, function, and region.

[0106] (Appendix 3) The step of transmitting the attribute list of the application further includes a step of, when the application is launched by a special user, the terminal device transmitting an ID of the special user together with the attribute list of the application to the data lake; The step of receiving the list of attributes of the application further includes the step of the data lake receiving an ID of the special user along with the list of attributes of the application; A data management method as described in Appendix 1 or 2, wherein the step of identifying the data name further includes a step of the data lake identifying one or more data names that can be accessed by the special user when the received special user ID is registered in a special user list.

[0107] (Appendix 4) A data management method for a terminal device to access data stored in a data lake, comprising: a step of launching an application of a department using the terminal device in accordance with an instruction from a user; When the application is launched by a special user, the terminal device transmits an ID of the special user to the data lake; the data lake receiving an ID of the special user; The data lake identifies one or more data names that can be accessed by the special user when the received special user ID is registered in the special user list; the data lake transmitting the one or more data names to the terminal device; receiving, by the terminal device, the one or more data names; a step of the terminal device selecting one or more desired data names from the received one or more data names; the terminal device transmitting one or more desired data names to the data lake; the data lake receiving the one or more data names; The data lake sends one or more access keys to the terminal device for accessing the one or more received data names; receiving, by the terminal device, the one or more access keys; A data management method comprising a step in which the terminal device downloads desired data from the data lake using the one or more received access keys.

[0108] (Appendix 5) The data lake stores personal business objects including user IDs registered in the special user list. person creating a list; The data lake transmits the personal task target list to a terminal device of a human resources department; The data management method according to any one of appendices 1 to 4, further comprising a step of receiving the personal task target list by a terminal device of the human resources department.

[0109] (Appendix 6) A data management system comprising a data lake and a terminal device, The data lake and the terminal device execute the data management method described in any one of Supplementary Notes 1 to 5.

[0110] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is defined by the claims, not the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0111] 1, 1A, 1B, 1C Data lake, 2, 2A, 2B Terminal device, 11, 21 Communication unit, 12 Data catalog storage unit, 13 Access key storage unit, 14 Data main body storage unit, 15, 15A, 15B Data name identification unit, 16 Access key identification unit, 17, 29 Download control unit, 19 Special user list storage unit, 22 Display unit, 23 Application storage unit, 24 Application information storage unit, 25 Data storage unit, 26 Application execution unit, 27 Application attribute list identification unit, 28 Data name selection unit, 37 Special user ID identification unit, 59 Personal business target list creation unit, 1001 Processor, 1002 Memory, 1003 Bus.

Claims

1. A data management method for a terminal device to access data stored in a data lake, comprising: a step of launching an application of a department using the terminal device in accordance with an instruction from a user; The terminal device transmits an attribute list of applications of a department using the terminal device to the data lake; receiving, by the data lake, a list of attributes of the application; The data lake refers to a data catalog to identify a data name of one or more pieces of data having an attribute list that matches an attribute list of the application; the data lake transmitting the one or more data names to the terminal device; receiving, by the terminal device, the one or more data names; a step of the terminal device selecting one or more desired data names from the received one or more data names; the terminal device transmitting one or more desired data names to the data lake; the data lake receiving the one or more data names; The data lake transmitting one or more access keys for accessing the received one or more data names to the terminal device; receiving, by the terminal device, the one or more access keys; and a step in which the terminal device downloads desired data from the data lake using the one or more received access keys.

2. The data management method of claim 1 , wherein the attribute list includes business, function, and region.

3. The step of transmitting the attribute list of the application further includes a step of, when the application is launched by a special user, the terminal device transmitting an ID of the special user together with the attribute list of the application to the data lake; The step of receiving the list of attributes of the application further includes the step of the data lake receiving an ID of the special user along with the list of attributes of the application; The data management method of claim 1, wherein the step of identifying the data name further includes a step of identifying one or more data names that the special user can access when the ID of the received special user is registered in the special user list of the data lake.

4. A data management method for a terminal device to access data stored in a data lake, comprising: a step of launching an application of a department using the terminal device in accordance with an instruction from a user; When the application is launched by a special user, the terminal device transmits an ID of the special user to the data lake; the data lake receiving an ID of the special user; The data lake identifies one or more data names that can be accessed by the special user when the received special user ID is registered in the special user list; the data lake transmitting the one or more data names to the terminal device; receiving, by the terminal device, the one or more data names; a step of the terminal device selecting one or more desired data names from the received one or more data names; the terminal device transmitting one or more desired data names to the data lake; the data lake receiving the one or more data names; The data lake transmitting one or more access keys for accessing the received one or more data names to the terminal device; receiving, by the terminal device, the one or more access keys; and a step in which the terminal device downloads desired data from the data lake using the one or more received access keys.

5. A step in which the data lake creates a personal business target list including user IDs registered in the special user list; The data lake transmits the personal task target list to a terminal device of a human resources department; 5. The data management method according to claim 4, further comprising a step of receiving the personal task target list by a terminal device of the personnel department.

6. A data management system comprising a data lake and a terminal device, A data management system, wherein the data lake and the terminal device execute the data management method according to any one of claims 1 to 5.

Citation Information

Patent Citations

  • Method for succeeding technique / Skill

    JP2002123669A

  • Vehicle data conversion device and vehicle data output method

    JP2018081707A

  • Sensor network management method and sensor network management system

    JP2018124935A

  • Information processor and method

    JP2020107166A

  • Data lake, data management server and data management system

    JP2022035602A