Data management system and data management method

Abstract

A data management system which has a private cloud system and a public cloud system, and is connected to one or more user terminals, wherein: the private cloud system has a server device; the server device comprises a management table master for managing data to be accessed from the user terminal, a private-side authentication function for authenticating user privileges on the basis of a combination of a user ID and an occupation, and a private-side data provision unit for providing data to be accessed on the basis of the authentication result from the private-side authentication function; and the public-cloud system comprises a public-side authentication function for authenticating the user privileges on the basis of the combination of user ID and occupation, and a public-side data provision unit for partially providing private cloud system data on the basis of the authentication results from the public-side authentication function.

Description

Data Management System and Data Management Method

[0001] The present invention relates to a data management system and a data management method.

[0002] Conventionally, in data management services for projects involving multiple people or in the development of programs, functions and data typified by project management have been managed on a single server, and a management method has been adopted in which multiple people access it.

[0003] In order to control access from a user to a resource, there is a technique described in Japanese Patent Application Laid-Open No. 2009-301357 (Patent Document 1). This publication states that "when access to a resource is performed by an application, a role identification procedure for identifying a role stored in an operating environment storage unit that stores the role of a user in association with the operating environment in which the application is executed is executed by a computer from the operating environment in which the application is executed. Further, the computer device disclosed in the present application specifies access control information associated with the role specified by the role identification procedure from an access control information storage unit that stores access control information in association with the role of the user, and based on the specified access control information, causes the computer to execute an access control execution procedure for performing access control to the resource."

[0004] Japanese Patent Application Laid-Open No. 2009-301357

[0005] In the above Patent Document 1, it is possible to cope with a situation in which inconsistencies occur in the authorities given to the same user in access control by an OS (Operating System) or access control by an application. However, when multiple users are involved in multiple resources and the complexity is such that their access rights are related to the state of the project or their roles change over time, the existing system cannot handle advanced access control.

[0006] Therefore, an object of the present invention is to perform detailed access control even under complex situations.

[0007] To achieve the above objective, one representative data management system of the present invention is a data management system having a private cloud system and a public cloud system, and connected to one or more user terminals, wherein the private cloud system has a server device, the server device comprises a management table master for managing data to be accessed from the user terminal, a private-side authentication function for authenticating user privileges based on a combination of user ID and service, and a private-side data provision unit for providing data to be accessed based on the authentication result by the private-side authentication function, and the public cloud system comprises a public-side authentication function for authenticating user privileges based on a combination of user ID and service, and a public-side data provision unit for partially providing data from the private cloud system based on the authentication result by the public-side authentication function. Furthermore, one representative data management method of the present invention is a data management method in a data management system having a private cloud system and a public cloud system and connected to one or more user terminals, characterized in that the private cloud system registers and manages the data to be accessed from the user terminals in a management table master, performs private-side authentication to authenticate the user's authority based on a combination of user ID and service, and provides the data to be accessed based on the authentication result of the private-side authentication, and the public cloud performs public-side authentication to authenticate the user's authority based on a combination of user ID and service, and partially provides the data of the private cloud system based on the authentication result of the public-side authentication.

[0008] According to the present invention, detailed access control can be performed even under complex circumstances. Other issues, configurations, and effects will be clarified by the following description of the embodiments.

[0009] This is a block diagram showing the overall structure of the data management system. This is an explanatory diagram of the interrelationships of access control, taking into account the roles of the parties involved, users, tasks, resources, and functions in the embodiment. This is a specific example of data (1). This is a specific example of data (2). This is an explanatory diagram of rearranging user IDs and services. This is a flowchart of rearranging user IDs and services. This is an explanatory diagram of reusing history. This is a flowchart of reusing history. This is a specific example of displaying data (1). This is a specific example of displaying data (2). This is a specific example of displaying data (3).

[0010] Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. In this specification and the drawings, components having substantially the same function or configuration are denoted by the same reference numerals, and redundant descriptions are omitted.

[0011] This invention relates to a data management system including a cloud system and a method for managing data. In recent years, there has been a growing demand for configurations that include public cloud environments, such as for teleworking and outsourcing of business operations to other companies. On the other hand, companies also have a need to back up data that is difficult to put on the public cloud, or information that is no longer needed due to security reasons, to private servers (hereinafter referred to as private cloud). When a company adopts business process outsourcing, where tasks that would normally be performed by employees working at a location are performed remotely or partially outsourced to an external company, there are cases where multiple companies and users are involved in a chain reaction of operations. Furthermore, from the perspective of risk management and resilience, there are cases where substitute personnel or support staff respond to events or tasks that need to be addressed.

[0012] However, unlike existing systems, user identification and management centered on individual users such as user IDs and email addresses makes role sharing difficult. Furthermore, if a user transfers to another department or leaves the company, their access rights are lost, and it is impossible to transfer the area they were using to another person with the same role.

[0013] On the other hand, if only roles and access permissions are managed, it is possible to assign roles to users and control access on a function-by-function basis for each role, but if the same role and function are used, the same access permissions will be granted to all tasks.

[0014] These problems arise because the dimension of protecting the data we want to safeguard does not align with the dimension of permissions and status that need to be considered, such as the users and roles that access it. Furthermore, managing the synchronization or data imbalance between public and private clouds, as well as manipulating information in the public cloud in response to event information and permission changes, are also important.

[0015] Considering the above points, the present invention provides a resource control and access control system, method, and program that can perform resource management and access control while manipulating the dimension of information for protecting data, resources, and functions such as people, roles, timing, and status, and the dimension of permissions held by accessing users. In implementation, a hybrid cloud that links public and private clouds is utilized to contribute to data management for users who are in charge of multiple services (roles), both inside and outside the company.

[0016] Therefore, the data management system manages the data and functions to be protected by associating them with the resources to be deployed, manages a multidimensional access permission model by associating it with these combinations, and generates a set of IDs for recognizing the roles of the business executors and the executors, linked with multidimensional access permission information. Then, when access is received from a business executor, the system recognizes whether the multidimensional access permissions held by the accessing user match or are included in the multidimensional access permission model assigned to the data and functions to be protected and the resources to be deployed, and performs access control.

[0017] Figure 1 is a block diagram showing the overall configuration of the data management system. The data management system 400 includes a private cloud system 200 and a public cloud system 100, and is connected to one or more user terminals 600.

[0018] The private cloud system 200 has server equipment. Server equipment is a computer that is physically equipped with a computing unit (CPU: Central Processing Unit), memory as main memory, and hard disk drives as secondary storage. The public cloud system 100 has computing resources (GPU (Graphics Processing Unit), CPU, virtual computing resources, etc.) that are used by the metaverse, generative AI, etc.

[0019] In Figure 1, user 800a is, for example, an employee of a business operator that has installed the private cloud system 200, and accesses the private cloud system 200 by operating user terminal 600a. User terminal 600a has user identification information 610a and sends and receives communication packets 700a to and from the private cloud system 200.

[0020] User 800b is, for example, an employee of a business operator and accesses the public cloud system 100 by operating user terminal 600b. User terminal 600b has user identification information 610b and sends and receives communication packets 700b with the private cloud system 200. Similarly, user 800c is, for example, an employee of an external company and accesses the public cloud system 100 by operating user terminal 600c. User terminal 600c has user identification information 610c and sends and receives communication packets 700c with the public cloud system 100.

[0021] In other words, the services of the public cloud system 100 can be accessed by internal and external users from the public network, while the private cloud system 200 can only be accessed by employees of the business operator.

[0022] The server device of the private cloud system 200 has a service / person ID management authentication function 201, a data / resource management function 202, an electronic approval function 203, a management table master 204, and a management table temporary area 205. The public cloud system 100 has a service / person ID management authentication function 101, a synchronization / imbalance management agent 102, spatial resources 110, and a generation AI resource 111.

[0023] The service / person ID management authentication function 201 determines the administrative authority to access the management table master 204 and the spatial resources of the public cloud system 100. The service / person ID management authentication function 201 is a private-side authentication function that authenticates user authority based on the combination of user ID and service (role).

[0024] The data resource management function 202 controls the synchronization of data and data imbalance between the private cloud system 200 and the public cloud system 100. The data resource management function 202 is a private-side data provision unit that provides data to be accessed based on the authentication results from the private-side authentication function.

[0025] The electronic approval function 203 manages the registration of differential data by obtaining approval from the user terminal 600a regarding whether or not the differential data registered in the temporary management table area 205 should be registered in the management table master 204.

[0026] The management table master 204 manages the data that is accessed from the user terminal 600. The management table master 204 is, for example, a data catalog vector index that manages data. The management table temporary area 205 temporarily stores data received from the synchronization / imbalance management agent 102. Specifically, the management table temporary area 205 stores the differences that occurred in the public cloud system 100 as temporary update data.

[0027] The service / person ID management authentication function 101 determines access. The service / person ID management authentication function 101 is a public-side authentication function that authenticates the user's authority based on a combination of user ID and service (role).

[0028] The synchronization / imbalance management agent 102 transmits data changes in the spatial resources 110 and the generated AI resources 111 in the public cloud system 100 to the private cloud system 200. The synchronization / imbalance management agent 102 is a public-side data provision unit that partially provides data from the private cloud system 200 based on the authentication results of the service / person ID management authentication function 101, which is a public-side authentication function.

[0029] The public cloud system 100 includes at least one of the following: an area for storing data space resources, an area for storing virtual three-dimensional space resources, and an area for storing content generation resources. For example, the space resource 110 is used to store data from the management table master 204 of the private cloud system 200 that has been transmitted by the data resource management function 202. The generation AI resource 111 generates a resource search key based on text data entered by the user terminal 600b, for example. That is, it can generate content such as strings suitable for resource searching from natural language text that is easily recognizable to the user 800a.

[0030] The private-side data provider, the data resource management function 202, can transmit a portion of the data to be accessed to the public-side data provider, the synchronization / imbalance management agent 102. The synchronization / imbalance management agent 102 provides the data received from the data resource management function 202 to user terminals 600b and 600c. When there are changes to the data received from the data resource management function 202, the synchronization / imbalance management agent 102 transmits the changed data back to the data resource management function 202, thereby maintaining data consistency between the private cloud system 200 and the public cloud system 100.

[0031] Furthermore, the data resource management function 202 can accept synchronization commands from the user terminal 600, extract data from the management table master 204, and send the extracted data to the synchronization / imbalance management agent 102. The synchronization / imbalance management agent 102 can also receive data from the data resource management function 202 and write it to the spatial resources of the public cloud system 100.

[0032] Furthermore, when the data resource management function 202 receives update data from the synchronization / imbalance management agent 102 on the public cloud system 100 side, it stores the received update data in the temporary management table area 205 and activates the electronic approval function 203. The electronic approval function 203 sends a notification to the user terminal 600a asking whether or not to reflect the update data in the management table master 204.

[0033] Furthermore, the public-side authentication function, the service / person ID management authentication function 101, is capable of performing the steps of processing access rights for data space resources, processing access rights for virtual 3D space resources, and processing access rights for content generation resources.

[0034] Furthermore, when the public-side data provider, the synchronization / imbalance management agent 102, restricts access to resources stored in the public cloud system 100, it releases those resources and issues commands to higher-level applications to behave as if they do not have permission to access those resources.

[0035] Figure 2 is an explanatory diagram of the interrelationships of access control, taking into account the roles of the parties involved, users, operations, resources, and functions in the embodiment. The role of "operator" is assigned to users on the private cloud system 200 side, while the roles of "local related company," "classification / generation AI," "supervision business," and "supervision company" are assigned to users on the public cloud system 100 side. In Figure 2, the access space is shown as a dashed line area, access rights are shown as nodes, and sharing relationships are shown as links. Also, in Figure 2, the phases progress in the order of preparation, operations, inspection, and post-completion.

[0036] In the preparation phase, an access space is created where the business operator and local related companies have access rights, and a sharing relationship is established between the business stakeholders and the local related companies. The access space in the preparation phase is a data sharing space where resources are shared as data.

[0037] In the business phase, an access space is created in which the business operator, local related companies, and the classification / generation AI have access rights, and a shared relationship is established among the business operator, local related companies, and the classification / generation AI. The access space in the business phase is a metaverse space. That is, the classification / generation AI generates a metaverse, which is a virtual three-dimensional space, based on resources, and the business operator and local related companies access the resources represented as objects within the metaverse.

[0038] During the inspection phase, an access space is created in which the service provider, local related companies, supervisory bodies, and supervisory companies have access rights, and a shared relationship is established among them. The access space during the inspection phase is a space in which audio and video are shared.

[0039] In the post-completion phase, an access space is created where only the service provider has access rights, and access from the public cloud system 100 is prevented. Therefore, the data after completion is saved as an archive in a governed state.

[0040] Figures 3 and 4 show specific examples of data. The user data 300A shown in Figure 3 has items such as User ID 300A-1, Name 300A-2, and Status 300A-3. When deleting a user registration, if the user data itself is deleted, it becomes impossible to check the access rights the user previously had and the history of the user's past accesses. Therefore, when deleting a user registration, the Status 300A-3 item is updated from "Enabled" to "Disabled," and the user data itself is retained.

[0041] Specifically, the user data 300A associates the user ID "user001@a.com" with the name "user001", the status "valid", and so on. Also, the user data 300A associates the user ID "user002@a.com" with the name "user002", the status "valid", and so on. Further, the user data 300A associates the user ID "user001@b.com" with the name "User001", the status "invalid", and so on.

[0042] The management data 300B (service management data 300B) shown in FIG. 3 has items such as a user ID 300B-1, a service 300B-2, a status 300B-3, etc. The service management data 300B is data for managing the services (roles) assigned to users, and manages the validity and invalidity of the combinations of users and services in the status item so that the history can be confirmed even after the assignment of services to users is cancelled.

[0043] Specifically, the service management data 300B associates the user ID "user001@a.com" with the service "business operator" and the status "valid", and so on. Also, the service management data 300B associates the user ID "user002@a.com" with the service "local related company", and so on. Further, the service management data 300B associates the user ID "user001@b.com" with the service "classification / generation AI", and so on.

[0044] The management data 300C (resource access right data 300C) shown in FIG. 4 is data for managing the access rights to resources. The resource access right data 300C has items such as a resource ID 300C-1, a resource Type 300C-2, a service ID 300C-3, a user ID 300C-4, a right 300C-5, a period 300C-6, a status 300C-7, etc.

[0045] Resource ID 300C-1 is identification information that uniquely identifies the resource. Resource Type 300C-2 takes the value "On-Premise" if the resource is located in the private cloud system 200, and "Public Cloud" if it is located in the public cloud system 100. Service ID 300C-3 is a name that uniquely identifies the service (role). User ID 300C-4 uses the ID registered in user data 300A. Authority 300C-5 indicates the content of the access rights set for the resource based on the combination of Service ID 300C-3 and User ID 300C-4. Period 300C-6 indicates the period during which Authority 300C-5 is valid. State 300C-7 can take values ​​such as "Enabled," indicating that access privilege 300C-5 is enabled; "Invalid," indicating that access privilege 300C-5 is disabled; or "Unbalanced," indicating that access privilege 300C-5 differs between the private cloud system 200 and the public cloud system 100.

[0046] The management data 300D (function access rights data 300D) shown in Figure 4 is data that manages access rights to functions. The function access rights data 300D has items such as function D300D-1, function type 300D-2, service ID 300D-3, user ID 300D-4, authority 300D-5, period 300D-6, and status 300D-7.

[0047] Function ID 300D-1 is identification information that uniquely identifies a function. Function Type 300D-2 indicates the classification of the function. Service ID 300D-3 is a name that uniquely identifies a service (role). User ID 300D-4 uses the ID registered in user data 300A. Authority 300D-5 indicates the content of the access authority set for the function in question based on the combination of Service ID 300D-3 and User ID 300D-4. Period 300D-6 indicates the period during which authority 300D-5 is valid. Status 300D-7 can take values ​​such as "Valid" indicating that access authority 300D-5 is valid, "Invalid" indicating that access authority 300D-5 is invalid, or "Unbalanced" indicating that access authority 300D-5 differs between the private cloud system 200 and the public cloud system 100.

[0048] The management data 300E (business access right data 300E) shown in FIG. 4 is data for managing access rights to business operations. The business access right data 300E has items such as business D300E-1, business type 300E-2, service ID 300E-3, user ID 300E-4, authority 300E-5, period 300E-6, status 300E-7, etc.

[0049] The business ID 300E-1 is identification information that uniquely identifies a business operation. The business type 300E-2 indicates the classification of the business operation. The service ID 300E-3 is a name that uniquely identifies a service (role). The user ID 300E-4 uses the ID registered in the management data 300A (user data 300A). The authority 300E-5 indicates the content of the access right set for the combination of the service ID 300E-3 and the user ID 300E-4 for the business operation. The period 300E-6 indicates the period during which the authority 300E-5 is valid. The status 300E-7 takes values such as "valid" indicating that the access right 300E-5 is valid, "invalid" indicating that the access right 300E-5 is invalid, and "unbalanced" indicating that the access right 300E-5 is different between the private cloud system 200 and the public cloud system 100.

[0050] FIG. 5 is an explanatory diagram of the recombination of user ID and service. In FIG. 5, first, user001@a.com is in a state where service A is assigned. user001@a.com is an employee of a business operator. When user001@a.com leaves the company, for example, due to retirement, user001@a.com is removed from the combination of user001@a.com and service A. Then, user001@b.com, a junior employee of a local affiliated company, is added. As a result, a combination of user001@b.com and service A is generated. That is, the authority of service A that the business operator had is given to the local affiliated company, and BPO can be realized. In this way, by enabling the recombination of the service history and the pair of person IDs, and allowing the delegation of the utilization authority of the hybrid cloud, the sustainability of the company can be ensured even in a state of declining birthrate and labor shortage.

[0051] Figure 6 is a flowchart of the rearrangement of user IDs and services. The service / person ID management and authentication function 201 sequentially executes the following steps S11 to S13.

[0052] Step S11: The service / person ID management authentication function 201 changes the status of user001@a.com in the management data 300A from "enabled" to "disabled". Then proceed to step S12.

[0053] Step S12: The service / person ID management authentication function 201 invalidates the past service history of user001@a.com from the management tables 300B, 300C, 300D, and 300E. Then proceed to step S13.

[0054] Step S13: The service / person ID management authentication function 201 copies the past service history of user001@a.com from the management tables 300B, 300C, 300D, and 300E, changes the copied information to user001@b.com, and then terminates the process.

[0055] Figure 7 is an explanatory diagram of history reuse. The history, which is a record of past access by the service provider, is saved as an archive in the post-completion process. Therefore, the service provider can generate management data 300F (deployment-related management data 300F) from the history and reuse it for subsequent implementations, for example, by providing it to the local related company that will take over the project. In particular, multidimensional data including the metaverse requires effort to create and maintain, so reuse can result in a significant reduction in effort.

[0056] Deployment relationship management data 300F is data that associates, for example, resource ID, function ID, business ID, period, status, etc. By linking business ID, function ID, and resource ID using deployment relationship management data 300F, resource management and permission management can be linked.

[0057] Figure 8 is a flowchart of the history reuse process. The data resource management function 202 sequentially executes the following steps S21 to S24.

[0058] Step S21: The data resource management function 202 verifies the configuration of the management data 300F. Then, it proceeds to step S22. Step S22: The data resource management function 202 deploys the target business data to the area indicated by the resource ID, according to the information in the management table of the management data 300E. Then, it proceeds to step S23.

[0059] Step S23: The data resource management function 202 deploys the function to the area indicated by the resource ID, according to the information in the management table of the management data 300E. Then, the process proceeds to step 24. Step S24: The data resource management function 202 changes the status of the corresponding row in the deployment relationship management data 300F from "disabled" to "enabled" and terminates the process.

[0060] Figures 9 to 11 show specific examples of data display. In display example 1-1a in Figure 9, the target ID of a task is specified, and the time-series display of access rights is shown. The target ID of a task is specified using a hierarchical structure, for example, "common root ID / mission 1 / task 1". In display example 1-1a, the specified task 1 includes processes 1 to 5 that are executed sequentially. Display example 1-1a can show the access rights status for each process, for each combination of service and user.

[0061] In Display Example 1-1b of Figure 9, a combination of service and user ID is specified, and the timeline of access rights is displayed. The service and user ID are specified using a hierarchical structure, for example, "common root ID / service A / user ID 1". In Display Example 1-1b, service A / user ID 1 is granted access rights to the resource with target ID 1 and access rights to the resource with target ID 2. Subsequently, the access rights for target ID 1 are revoked, and access rights for the function with target ID 3 are added.

[0062] In Figure 9, example 1-1c visualizes the permission history. Specifically, it shows which users have permissions granted to the target resource, along with how those permissions change over time.

[0063] In the display example 1-1d of Figure 10, resources specified in a hierarchical structure are designated as evaluation targets 1-1d-1, and the folksonomy consideration score is graphed as the evaluation value 1-1d-2. Furthermore, by specifying evaluation targets 1-1d-1 using the pointer 1-1d-3, the considerations can be displayed individually.

[0064] Furthermore, in the display example 1-1d of Figure 10, the status changes 1-1d-5 for the target task 1-1d-4 at each relative time are shown. For example, at relative time 1, target ID 1 is being processed. At relative time 2, target ID 1 and target ID 2 are being processed. At relative time 3, target ID 2 and target ID 3 are being processed. At relative time 4 (the current time), target ID 1 and target ID 3 are being processed, and at relative time 5, target ID 1 and target ID 2 are being processed.

[0065] Furthermore, in display example 1-1d of Figure 10, the degree of access permission achievement is displayed using a sunburst graph 1-1E. The sunburst graph 1-1E displays the inclusion and surplus / deficiency of permissions for resource, function, and task combinations of service and user ID. Additionally, for example, by pointing to an area indicating a lack of permissions, details can be displayed, and contact information for granting the missing permissions can be shown.

[0066] The display example in Figure 11 is used to display the source data of the data created by the generating AI and to verify permissions. In Figure 11, the resources are arranged in a hierarchical structure. Specifically, under resource structure ID 1-1F, there is directory ID 1-1F-1. And under directory ID 1-1F-1, there are data ID 1-1F-1a, specification ID 1-1F-1c, program ID 1-1F-1b, etc.

[0067] Based on this resource structure, the source data generated by the AI ​​can be displayed. Furthermore, the permission settings for each user-service combination can be checked for each source data. This prevents situations where the AI ​​presents data generated using data that the user does not have access to.

[0068] As described above, the data management system 400 protects data used in business operations using the private cloud system 200, and synchronizes only data that needs to be shared with external users, such as in business process outsourcing, with the public cloud system 100, enabling data sharing and collaborative work by multiple users using spatial resources.

[0069] Therefore, it becomes possible to manage the execution environment, data synchronization, and the services and people who can access it, including remote work and outsourcing of business operations to other affiliated companies, which were difficult with conventional technologies.

[0070] Furthermore, it enables detailed access control even in complex situations where the deployment location of data or functions changes, or where the state of operations or the permissions held by individuals change—situations that were difficult with conventional technologies.

[0071] Furthermore, once the service has ended, data security can be achieved by creating an imbalance between data in public and private clouds, or by releasing the spatial resources and resources for generative AI in the public cloud.

[0072] Furthermore, by combining the management methods for service IDs and user IDs, and enabling the exchange of person IDs for different service access scopes, it becomes possible to outsource services previously handled by internal users to external users (BPO).

[0073] Furthermore, access rights in conventional public cloud systems are person-based, meaning that when a user leaves the company, their email address and other credentials become unusable, and the concept of the service they performed also ceases to exist. However, this system allows for the management, reuse, and editing of the service history performed by past user IDs, and enables the transfer of all or part of that history to a new user ID.

[0074] As described above, the system disclosed in the embodiment is a data management system 400 connected to one or more user terminals 600, comprising a private cloud system 200 and a public cloud system 100. The private cloud system comprises a server device, which includes a management table master for managing data to be accessed by the user terminals, a private-side authentication function for authenticating user privileges based on a combination of user ID and service, and a private-side data provision unit for providing data to be accessed based on the authentication result of the private-side authentication function. The public cloud system comprises a public-side authentication function for authenticating user privileges based on a combination of user ID and service, and a public-side data provision unit for partially providing data from the private cloud system based on the authentication result of the public-side authentication function. With this configuration and operation, the data management system 400 can perform detailed access control even under complex circumstances.

[0075] Furthermore, the private-side data provider unit can transmit a portion of the data to be accessed to the public-side data provider unit, and the public-side data provider unit provides the data received from the private-side data provider unit, and maintains data integrity by transmitting the modified data to the private-side data provider unit if there are any changes to the data received from the private-side data provider unit. This configuration and operation allows for the management of data shared between the private and public sides.

[0076] Furthermore, the private cloud system 200 includes a temporary management table area for temporarily storing data received from the public data provision unit, and an electronic approval function for obtaining approval on whether or not to reflect the data stored in the temporary management table area in the management table master. This configuration and operation enable secure management of private data.

[0077] Furthermore, the public cloud system 100 includes at least one of the following: an area for storing data space resources, an area for storing virtual 3D space resources, and an area for storing content generation resources. This configuration and operation allows users connected to the public side to utilize the data space, virtual 3D space, and content generation.

[0078] Furthermore, the private-side data provision unit receives a synchronization command from the user terminal, extracts data from the management table master, and sends the extracted data to the public-side data provision unit. This configuration and operation allows the private-side and public-side data to be synchronized at any desired time.

[0079] Furthermore, the public-side data provision unit receives data from the private-side data provision unit and writes it to the spatial resources of the public cloud system. This configuration and operation allows a portion of the private-side data to be provided to users on the public-side.

[0080] The private-side data provider unit receives update data from the public-side data provider unit on the public cloud system side, stores the received update data in the temporary management table area, activates the electronic approval function, and the electronic approval function notifies the user terminal whether or not to reflect the update data in the management table master. Through this configuration and operation, data updates on the private side can be strictly controlled by user approval.

[0081] Furthermore, the public-side authentication function can perform the steps of processing access rights for data space resources, processing access rights for virtual 3D space resources, and processing access rights for content generation resources. Public-side data is managed in block storage, and the area of ​​block storage is difficult for users to recognize, which presents a challenge in that it can be difficult to know which resource to access. However, by providing a step to process access rights in this way, the user's access destination can be made clear.

[0082] Furthermore, the public data provision unit generates content based on the text data entered by the user terminal and searches for resources using the generated content as a key. This configuration and operation enables users to perform highly accurate searches using natural language.

[0083] Furthermore, when the public data provider restricts access to resources stored in the public cloud system, it releases those resources and issues commands to higher-level applications to behave as if they do not have permission to access those resources. This configuration and operation allows access to be restricted while concealing the state of the restricted resources. In addition, it is possible to make the system behave as if the resource itself does not exist when a user attempts to access a resource for which they do not have access rights.

[0084] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are included. For example, the embodiments described above are explained in detail to make the present invention easier to understand, and are not necessarily limited to those having all the configurations described. Furthermore, it is possible to replace or add configurations, not just delete them.

[0085] 100: Public cloud system 101: Service / person ID management authentication function 102: Synchronization / imbalance management agent 110: Spatial resources 111: Generated AI resources 200: Private cloud system 201: Service / person ID management authentication function 202: Data / resource management function 203: Electronic approval function 204: Management table master 205: Management table temporary area 300A: Management data (user data) 300B: Management data (service management data) 300C: Management data (resource access rights data) 300D: Management data (function access rights data) 300E: Management data (business access rights data) 300F: Management data (deployment-related management data) 400: Data management system 600: User terminal 610: User identification information 700: Communication packet 800: User

Claims

1. A data management system comprising a private cloud system and a public cloud system, and connected to one or more user terminals, wherein the private cloud system comprises a server device, the server device comprising a management table master for managing data to be accessed from the user terminals, a private-side authentication function for authenticating user privileges based on a combination of user ID and service, and a private-side data provision unit for providing data to be accessed based on the authentication result of the private-side authentication function, and the public cloud system comprising a public-side authentication function for authenticating user privileges based on a combination of user ID and service, and a public-side data provision unit for partially providing data from the private cloud system based on the authentication result of the public-side authentication function.

2. A data management system according to claim 1, wherein the private data provision unit is capable of transmitting a portion of the data to be accessed to the public data provision unit, and the public data provision unit provides the data received from the private data provision unit, and maintains data integrity by transmitting the modified data to the private data provision unit when there is a change in the data received from the private data provision unit.

3. A data management system according to claim 2, wherein the private cloud system further comprises a temporary management table area for temporarily storing data received from the public data provision unit, and an electronic approval function for obtaining approval on whether or not to reflect the data stored in the temporary management table area in the management table master.

4. A data management system according to claim 3, wherein the public cloud system comprises at least one of the following: an area for storing data space resources, an area for storing virtual three-dimensional space resources, and an area for storing content generation resources.

5. A data management system according to claim 2, wherein the private data provision unit receives a synchronization command from the user terminal, extracts data from the management table master, and sends the extracted data to the public data provision unit.

6. A data management system according to claim 2, wherein the public-side data provision unit receives data from the private-side data provision unit and writes it to the spatial resources of the public cloud system.

7. A data management system according to claim 3, wherein the private-side data provision unit receives update data from the public-side data provision unit on the public cloud system side, stores the received update data in the temporary management table area, activates the electronic approval function, and the electronic approval function notifies the user terminal whether or not to reflect the update data in the management table master.

8. A data management system according to claim 4, wherein the public-side authentication function is capable of performing the steps of: processing access rights for data space resources; processing access rights for virtual three-dimensional space resources; and processing access rights for content generation resources.

9. A data management system according to claim 4, wherein the public-side data provision unit generates content based on text data entered by the user terminal, and searches for resources using the generated content as a key.

10. A data management system according to claim 4, wherein the public-side data provision unit, when restricting access to resources stored in the public cloud system, releases the resources and issues a command to a higher-level application to behave as if it does not have permission to access the resources.

11. A data management method in a data management system having a private cloud system and a public cloud system and connected to one or more user terminals, characterized in that the private cloud system registers and manages the data to be accessed from the user terminals in a management table master, performs private-side authentication to authenticate the user's authority based on a combination of user ID and service, and provides the data to be accessed based on the authentication result of the private-side authentication, and the public cloud system performs public-side authentication to authenticate the user's authority based on a combination of user ID and service, and partially provides the data of the private cloud system based on the authentication result of the public-side authentication.

Images