Data exchange system and method based on tenant space

Abstract

The invention provides a tenant space-based data exchange system and method, which can be used in the field of big data. The data exchange system comprises a data controlled exchange system and a plurality of tenant spaces, wherein each tenant space comprises a front domain and a production domain; the front domain is used for acquiring exchange data of other departments through the data controlled exchange system and providing exchange data of the department to other departments; the production domain is used for storing the obtained exchange data of other departments and managing the exchange data of the department; and the data controlled exchange system is used for realizing cross-department data exchange after obtaining the data exchange task. The interior of each tenant space is divided into a preposition domain and a production domain, so that data of different departments are effectively isolated, and the safety problem of the data in the exchange process is solved; and the data in the department is effectively isolated, and the problem that the normal work of a service system is easily influenced during data exchange is solved.

Description

Technical Field

[0001] The present application relates to the technical field of data exchange, and in particular to a tenant space-based data exchange system and method. Background Art

[0002] At present, with the development of the big data industry, data sharing and exchange systems have been widely built and used. The data exchange system is a distribution center and intersection for processing, sharing, exchanging and utilizing data based on the Internet using modern information technology. In order to provide users with different forms of data sharing services and meet different types of data sharing service needs, the flow of various types of data in the sharing and exchange system has become increasingly complex.

[0003] In the prior art, data exchange is usually achieved based on a shared exchange system of a front-end processor. The specific implementation method is: an independent front-end processor is assigned to each department or a public front-end processor is provided for each department. When data exchange is required, each department can push the data to be exchanged to its own or a public front-end processor, and other departments can obtain the corresponding exchange data from the front-end processor, thereby realizing data exchange.

[0004] However, the existing data exchange system has poor data isolation between different departments, which may lead to security risks during data exchange; and the data flow within the department is chaotic, which can easily affect the normal use of the business system. Summary of the invention

[0005] The present application provides a tenant space-based data exchange system and method to solve the problems of poor isolation of data between different departments in the existing data exchange system, potential security risks, chaotic data flow within the department, and easy impact on the normal use of the business system.

[0006] On the one hand, the present application provides a data exchange system based on tenant space, the data exchange system comprising: a data controlled exchange system and multiple tenant spaces, wherein each department corresponds to a tenant space, and each tenant space comprises: a pre-domain and a production domain;

[0007] The front-end domain is used to obtain the exchange data of other departments through the data controlled exchange system and provide the exchange data of the department to other departments;

[0008] The production domain is used to store the acquired exchange data of other departments and manage the exchange data of the department;

[0009] The data controlled exchange system is used to realize cross-departmental data exchange after obtaining a data exchange task.

[0010] Optionally, the pre-domain includes: a data sharing area and a data access area;

[0011] The data sharing area is used to provide the exchange data of the department to other departments, so that other departments can obtain the exchange data of the department through the data controlled exchange system;

[0012] The data access area is used to pre-process the exchange data of other departments and transmit the pre-processed exchange data to the data sharing area or the production domain.

[0013] Optionally, the data sharing area includes: a data sharing library and a data service library;

[0014] The data sharing library is used to receive the exchange data of the department pushed by the production domain and / or the exchange data of other departments pushed by the data access area, and to mount the received exchange data with the corresponding data directory so that the exchange data can be exchanged through the data controlled exchange system;

[0015] The data service library is used to receive the exchange data pushed by the production domain and / or the exchange data of other departments pushed by the data access area, and encapsulate the received exchange data into an interface, and connect it to the interface directory so that the exchange data provides interface services to the outside.

[0016] Optionally, the data access area includes: a source library and a standard library;

[0017] The post source library is used to store exchange data of other departments obtained through the data controlled exchange system;

[0018] The standard library is used to store standardized exchange data formed after preprocessing the exchange data in the paste source library;

[0019] The standard library is also used to push the pre-processed exchange data of other departments to the production domain, the data sharing library and the data service library.

[0020] Optionally, the production domain includes: a business application library and a shared collection library;

[0021] The business application library is used to receive exchange data pushed by multiple sub-business application libraries of the department, and push the received exchange data pushed by multiple sub-business application libraries to the data sharing library and / or the data service library;

[0022] The shared collection library is used to receive the pre-processed exchange data of other departments sent by the standard library, so as to back up the pre-processed exchange data of other departments;

[0023] The shared collection library is also used to push the pre-processed exchange data of other departments to the data sharing library and / or the data service library.

[0024] In a second aspect, the present application provides a data exchange method based on a tenant space, the method comprising:

[0025] Acquire first exchange data from the data controlled exchange system through the data access area of ​​the first department, and pre-process the first exchange data to obtain second exchange data, where the first exchange data is data of the second department;

[0026] Performing directory mounting processing on the second exchange data through the data sharing area of ​​the first department to obtain a directory mounting relationship of the second exchange data;

[0027] Optionally, the data sharing area includes: a data sharing library, and if the directory mounting process is a data directory mounting process, then performing directory mounting process on the second exchange data through the data sharing area of ​​the first department to obtain a directory mounting relationship of the second exchange data includes:

[0028] The data sharing library receives the second exchange data sent by the data access area;

[0029] The data sharing library generates a data directory corresponding to the second exchange data according to the second exchange data, and performs data directory mounting processing on the second exchange data and the data directory to obtain a data directory mounting relationship of the second exchange data;

[0030] Optionally, the data sharing area further includes: a data service library, and if the directory mounting process is an interface directory mounting process, the directory mounting process is performed on the second exchange data through the data sharing area of ​​the first department to obtain the directory mounting relationship of the second exchange data, including:

[0031] The data service library receives the second exchange data sent by the data access area;

[0032] The data service library generates an interface directory corresponding to the second exchange data according to the second exchange data, and performs interface directory mounting processing on the second exchange data and the interface directory to obtain an interface directory mounting relationship of the second exchange data;

[0033] The directory attachment relationship is sent to a unified data directory management system through the data sharing area of ​​the first department, so that the unified data directory management system verifies the directory attachment relationship and retains the directory attachment relationship after the verification is passed.

[0034] Optionally, sending the directory attachment relationship to a unified data directory management system through the data sharing area of ​​the first department includes:

[0035] The data directory attachment relationship is sent to a unified data directory management system through the data sharing library, so that the unified data directory management system verifies the data directory attachment relationship, and after the verification is passed, retains the data directory attachment relationship.

[0036] Optionally, sending the directory attachment relationship to a unified data directory management system through the data sharing area of ​​the first department includes:

[0037] The interface directory attachment relationship is sent to a unified data directory management system through the data service library, so that the unified data directory management system verifies the interface directory attachment relationship, and after the verification is passed, retains the interface directory attachment relationship.

[0038] Optionally, after preprocessing the first exchange data to obtain second exchange data, the method further includes:

[0039] The second exchange data is sent to a shared collection library or a unified data warehouse, so that the first department retains and processes the second exchange data.

[0040] Optionally, the method comprises:

[0041] Acquire the third exchange data sent by the sub-business application library of the first department through the business application library of the first department;

[0042] Performing directory mounting processing on the third exchange data through the data sharing area of ​​the first department to obtain a directory mounting relationship of the third exchange data;

[0043] The directory attachment relationship is sent to a unified data directory management system through the data sharing area of ​​the first department, so that the unified data directory management system verifies the directory attachment relationship and retains the directory attachment relationship after the verification is passed.

[0044] The tenant space-based data exchange system provided by the present application has an independent tenant space for each department, and each tenant space is divided into a front-end domain and a production domain. The front-end domain is used to obtain the exchange data of other departments through the data controlled exchange system and provide the exchange data of the department to other departments; the production domain is used to store the exchange data of other departments and manage the exchange data of the department; the data of different departments are effectively isolated, solving the security problem of data in the exchange process; and the data within the department are effectively isolated, solving the problem that the normal operation of the business system is easily affected during data exchange. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0046] Figure 1 A schematic diagram of the structure of the data exchange system based on the tenant space provided in the embodiment of the present application Figure 1 ;

[0047] Figure 2 A schematic diagram of the structure of the data exchange system based on the tenant space provided in the embodiment of the present application Figure 2 ;

[0048] Figure 3 A schematic diagram of the structure of the data exchange system based on the tenant space provided in the embodiment of the present application Figure 3 ;

[0049] Figure 4 A schematic diagram of the structure of the data exchange system based on the tenant space provided in the embodiment of the present application Figure 4 ;

[0050] Figure 5 The process of the data exchange method based on tenant space provided in the embodiment of the present application Figure 1 ;

[0051] Figure 6 The process of the data exchange method based on tenant space provided in the embodiment of the present application Figure 2 ;

[0052] Figure 7 The process of the data exchange method based on tenant space provided in the embodiment of the present application Figure 3 .

[0053] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0054] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0055] In the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with substantially the same functions and effects, and do not limit their order. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different.

[0056] In the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0057] It should be noted that the data involved in this application (including but not limited to data used for analysis, stored data, displayed data, etc.) are all information and data authorized by the department or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for departments to choose to authorize or reject.

[0058] It should be noted that the data exchange system provided in the present application can be used in the field of big data, and can also be used in any field other than the field of big data. The present application does not limit the application field of the provided data exchange system.

[0059] At present, the data exchange system is based on the Internet and realizes the processing, sharing, exchange and utilization of data through modern information technology. For example, enterprises can use the data exchange system to meet various data circulation needs between multiple departments. For example, the human resources department can obtain the financial statement data of the operating department through the data exchange system to optimize the company's salary system; the operating department can obtain the cost data of the management department through the data exchange system to formulate the project quotation.

[0060] Since the existing data exchange system needs to meet the data circulation needs of various departments, the flow of various types of data in the data exchange system has become increasingly complex, but the existing data flow control methods are still in a relatively single state, resulting in the data cannot be managed effectively and in a standardized manner, and there are certain security risks.

[0061] In order to solve the problem that data cannot be managed effectively and standardizedly and there are certain security risks, the existing technology implements data exchange by allocating an independent front-end processor to each department or providing a public front-end processor.

[0062] However, when the existing data exchange system is exchanging data, the data isolation between different departments is poor, which poses a security risk; the data flow within the department is chaotic, which can easily affect the normal use of the business system.

[0063] In view of this, the embodiment of the present application provides a data exchange system based on tenant space and a data exchange method based on tenant space. The system sets up an independent tenant space for each department, divides each tenant space into a front-end domain and a production domain, manages the exchange data of the department through the production domain of the department, pushes the exchange data to the front-end domain, and exchanges data with other departments; and obtains the exchange data of other departments through the data controlled exchange system. This method effectively isolates the data between different departments by setting each department as an independent tenant space, and solves the security problem of data in the exchange process; by dividing the tenant space into a front-end domain and a production domain, the exchange data within the department is effectively isolated from the business data, and solves the problem that the normal operation of the business system is easily affected when data is exchanged in the prior art.

[0064] The following specific embodiments are used to describe in detail the technical solution of the present application and how the technical solution of the present application solves the above technical problems. The following specific embodiments can be implemented independently or in combination with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0065] Figure 1 A schematic diagram of the structure of the data exchange system based on the tenant space provided in the embodiment of the present application Figure 1 ,like Figure 1 As shown, the data exchange system based on tenant space includes: a data controlled exchange system and multiple tenant spaces.

[0066] Among them, each department corresponds to a tenant space, and each tenant space includes: a front-end domain and a production domain; the front-end domain is used to obtain the exchange data of other departments through the data controlled exchange system and provide the exchange data of the department to other departments; the production domain is used to store the exchange data of other departments and manage the exchange data of the department; the data controlled exchange system is used to realize cross-departmental data exchange after obtaining the data exchange task.

[0067] The functions of each part of the data exchange system will be introduced in turn below.

[0068] like Figure 1 As shown, the multiple tenant spaces may include, for example, tenant space A corresponding to department A, tenant space B corresponding to department B, and tenant space X corresponding to department X, etc., and the above multiple tenants are all connected to the data controlled exchange system in communication. The tenant space corresponding to each department may send a data exchange request to the data controlled exchange system. When the data controlled exchange system receives the data exchange request, it will obtain the corresponding exchange data from the tenant spaces corresponding to other departments according to the data exchange request to realize data exchange.

[0069] Tenant space is the application functions and data resources that are logically or physically isolated by various systems deployed through application virtualization. Different departments have different tenant spaces. The tenant space corresponding to each department can be used to manage the business data of the department, as well as receive and store exchange data sent by other departments.

[0070] Since each department uses an independent data source, a corresponding tenant space can be set up for each department to achieve logical isolation at the database level and reduce the risk of cross-access to the business data of each department.

[0071] Exemplarily, each department in the tenant space-based data exchange system can achieve cross-departmental data exchange by setting up an independent tenant space and connecting multiple tenant spaces to the data controlled exchange system for communication, wherein the tenant space can be implemented by relevant software and / or hardware.

[0072] In the embodiment of the present application, the production domain refers to an area within the tenant space used to manage the data sources of each sub-business application library and store exchange data of other departments.

[0073] The sub-business application library stores various types of business data within each department. When a data exchange task is obtained, the sub-business application library pushes the exchange data to the production domain of the department to achieve the isolation of the exchange data and business data within the department, thereby ensuring that the data exchange process does not affect the normal use of the department's business system. Each department in the data exchange system has an independent production domain for managing the exchange data of the department.

[0074] The exchange data of other departments is pushed to the production domain through the front-end domain, and the production domain stores the obtained exchange data of other departments in the production domain.

[0075] For example, tenant space A corresponding to department A has an independent production domain for managing the exchange data of department A. When the exchange data of department B is pushed to the production domain of department A through the front-end domain of department A, the production domain of department A will retain and process the exchange data of department B.

[0076] In the embodiment of the present application, the front-end domain refers to a virtual area obtained by dividing the internal space of the tenant space, and the front-end domain is used to receive exchange data of other departments obtained through the data controlled exchange system and provide the exchange data of the department to other departments.

[0077] For example: Tenant space A corresponding to department A has an independent front-end domain for receiving the exchange data of department B obtained through the data-controlled exchange system; and the front-end domain of tenant space A corresponding to department A provides the exchange data of department A to department B through the data-controlled exchange system.

[0078] In an embodiment of the present application, the data controlled exchange system is used to realize cross-departmental data exchange after obtaining a data exchange task.

[0079] It can be understood that each department in the data exchange system has an independent tenant space to isolate the data of each department, and the data of different departments are exchanged through the data controlled exchange system to realize cross-departmental data exchange.

[0080] Exemplarily, taking the data exchange process between tenant space A corresponding to department A and tenant space B corresponding to department B as an example, the process of cross-department data exchange performed by the data controlled exchange system is described:

[0081] When the data-controlled exchange system obtains the data exchange task of exchanging the data in department B with department A, the exchange data in the production domain in the tenant space A is pushed to the front-end domain in the tenant space A, and the exchange data in the front-end domain in the tenant space A is transmitted to the front-end domain of the tenant space B through the data-controlled exchange system, and the front-end domain in the tenant space B transmits the exchange data of department A to the production domain of the tenant space B, thereby realizing the exchange of the data in the tenant space B corresponding to department B to the tenant space A corresponding to department A.

[0082] Optionally, the front-end domain includes: a data sharing area and a data access area; the data sharing area is used to provide the exchange data of the department to other departments, so that other departments can obtain the exchange data of the department through the data controlled exchange system; the data access area is used to pre-process the exchange data of other departments and transmit the pre-processed exchange data to the data sharing area or the production domain.

[0083] Figure 2 A schematic diagram of the structure of the data exchange system based on the tenant space provided in the embodiment of the present application Figure 2 ,like Figure 2 As shown, the data sharing area can obtain the exchange data of the department from the production domain and send the exchange data to the data controlled exchange system so that the data controlled exchange system can provide the exchange data to other departments ( Figure 2 (not shown). The data sharing area refers to an export area for providing the exchange data of the department to other departments through the data controlled exchange system.

[0084] It can be understood that when the data controlled exchange system receives a data exchange request, it will obtain the corresponding exchange data from the tenant space corresponding to other departments according to the data exchange request to achieve data exchange. Therefore, by setting a data sharing area for the tenant space corresponding to each department, the data sharing area serves as an exit to provide the exchange data of the department to other departments so that other departments can obtain the corresponding exchange data.

[0085] In a possible implementation, the production domain of the tenant space of this department pushes the exchange data to the data sharing area of ​​this department, and the data sharing area provides the exchange data of this department to other departments through the data controlled exchange system.

[0086] For example: the production domain of tenant space A corresponding to department A pushes the exchange data of department A to the data sharing area of ​​tenant space A, and the data sharing area of ​​tenant space A corresponding to department A provides the exchange data of department A to department B through the data controlled exchange system.

[0087] The data access area can obtain the exchange data sent by the tenant space corresponding to other departments through the data controlled exchange system, and pre-process the exchange data of other departments. Preprocessing refers to the process of standardizing the exchange data of other departments by the data sharing area of ​​this department, such as format conversion, character conversion, deduplication, escape, splitting, merging, desensitization, encryption, etc. This application does not impose any special restrictions on the specific implementation method of preprocessing.

[0088] The data access area can also transfer the pre-processed exchange data to the data sharing area or production domain, so that the tenant space A of this department can back up the exchange data of other departments.

[0089] In the embodiment of the present application, the data access area refers to the entry area when other departments transmit exchange data to this department through the data controlled exchange system, and the exchange data of other departments is transmitted to the data sharing area or production domain of this department after pre-processing, playing a connecting role.

[0090] In one possible implementation, other departments push exchange data to the data sharing area of ​​the front-end domain through the production domain, and transmit it to the data access area through the data controlled exchange system. The data access area preprocesses the exchange data of other departments and transmits the preprocessed exchange data to the data sharing area or the production domain.

[0091] For example: the production domain of tenant space B corresponding to department B pushes the exchange data of department B to the data sharing area of ​​the front domain in tenant space B. The data sharing area of ​​tenant space B is communicated with the data-controlled exchange system, and the exchange data of department B is transmitted to the data access area of ​​tenant space A corresponding to department A through the data-controlled exchange system. The data access area of ​​tenant space A pre-processes the exchange data of department B and transmits the pre-processed exchange data of department B to the data sharing area of ​​tenant space A or the production domain of tenant space A.

[0092] The tenant space-based data exchange system provided in the embodiment of the present application sets each department as an independent tenant space and implements data exchange across departments through a data-controlled exchange system, thereby effectively isolating data between different departments and solving the security problem of data during the exchange process; by dividing the tenant space into a front-end domain and a production domain, the exchange data within the department is effectively isolated from the business data, solving the problem that the normal operation of the business system is easily affected during data exchange.

[0093] Optionally, the data sharing area includes: a data sharing library and a data service library.

[0094] Figure 3 A schematic diagram of the structure of the data exchange system based on the tenant space provided in the embodiment of the present application Figure 3 ,like Figure 3 As shown, the data sharing library is used to receive the exchange data of the department pushed by the production domain and / or the exchange data of other departments pushed by the data access area, and to mount the received exchange data with the corresponding data directory so that the exchange data can be exchanged through the data controlled exchange system.

[0095] In one possible implementation, the data controlled exchange system pushes the exchange data of other departments to the data access area of ​​the department. The data access area pre-processes the exchange data of other departments and pushes it to the data sharing library of the department. The data sharing library connects the received exchange data of other departments with the corresponding data directory.

[0096] For example: the data controlled exchange system pushes the exchange data of department B to the data access area of ​​the tenant space of department A. The data access area of ​​the tenant space of department A pre-processes the exchange data of department B and pushes it to the data sharing library of the tenant space of department A. The data sharing library of the tenant space of department A links the exchange data of department B with the corresponding data directory.

[0097] In a possible implementation, the production domain of the department pushes the exchange data to the data sharing library, and the data sharing library mounts the exchange data of the department to the corresponding data directory. For example: the production domain of the tenant space of department A pushes the exchange data of department A to the data sharing library of the tenant space of department A, and the data sharing library of department A mounts the exchange data of department A to the corresponding data directory.

[0098] It can be understood that the exchange data is mounted with the corresponding data directory to achieve the association between the exchange data and the data directory.

[0099] Exemplarily, the data service library is used to receive exchange data pushed by the production domain and / or exchange data of other departments pushed by the data access area, and encapsulate the received exchange data into an interface, and connect it to the interface directory to enable the exchange data to provide interface services to the outside.

[0100] Optionally, the data access area includes: a source library and a standard library.

[0101] The post source library is used to store exchange data of other departments obtained through the data controlled exchange system.

[0102] Among them, the source database refers to the database close to the data source. When the exchange data is transmitted to the data access area of ​​the tenant space of other departments through the data controlled exchange system, the original exchange data is stored without any processing. It is used to ensure the stability of the exchange data.

[0103] The standard library is used to store standardized exchange data formed after preprocessing the exchange data in the source library.

[0104] The standard library is also used to push the pre-processed exchange data of other departments to the production domain, the data sharing library and the data service library.

[0105] Optionally, the production domain includes: a business application library and a shared collection library.

[0106] The business application library is used to receive exchange data pushed by multiple sub-business application libraries of the department, and push the received exchange data pushed by multiple sub-business application libraries to the data sharing library and / or the data service library.

[0107] Since the sub-business application library stores various business data of the department and maintains the normal use of the department's business system, when the department provides exchange data to the outside, it does not directly obtain the exchange data through the sub-business application library, but manages the data sources of multiple sub-business application libraries through the business application library, and pushes the exchange data pushed by multiple sub-business application libraries to the data sharing library and / or the data service library, so that the department's business system is not affected.

[0108] The following uses the tenant space of department A as an example to explain the business application library:

[0109] Sub-business application library 1, sub-business application library 2...sub-business application library N in the tenant space of department A are used to store the business data of each business system of department A. The business application library of department A is used to manage the business data in sub-business application libraries 1 to N, and receive the business data for exchange in sub-business application libraries 1 to N, and push the received exchange data to the data sharing library and / or the data service library, without actually storing data copies.

[0110] The shared collection library is used to receive the pre-processed exchange data of other departments sent by the standard library, so as to back up the pre-processed exchange data of other departments;

[0111] By backing up the pre-processed exchange data of other departments, historical exchange data of other departments are retained.

[0112] The shared collection library is also used to push the pre-processed exchange data of other departments to the data sharing library and / or the data service library.

[0113] In a possible implementation, the shared collection library pushes the pre-processed exchange data of other departments to the data sharing library, and mounts the received exchange data with the corresponding data directory.

[0114] In a possible implementation, the shared collection library pushes the pre-processed exchange data of other departments to the data service library, and encapsulates the received exchange data into an interface, which is mounted on the interface directory.

[0115] Optionally, the production domain also includes: a unified data warehouse.

[0116] The unified data warehouse is used to receive the pre-processed exchange data from other departments sent by the standard library, so as to collect and summarize the pre-processed exchange data from other departments and provide unified data resource support. The data stored in the unified data warehouse is the business data of multiple departments.

[0117] The unified data warehouse may include, but is not limited to, the following types of data resource libraries: basic information resource library, major task subject library, main field theme library, and other data resource libraries.

[0118] Figure 4 A schematic diagram of the structure of the data exchange system based on the tenant space provided in the embodiment of the present application Figure 4 .like Figure 4 As shown, the data exchange system also includes: a unified data directory management system.

[0119] In an embodiment of the present application, the unified data directory management system is used to verify whether the data directory mounting pushed by the data sharing library and / or the interface directory mounting pushed by the data service library is correct, and when the data directory mounting and / or the interface directory mounting are correct, the data directory mounting and / or the interface directory mounting are retained.

[0120] It can be understood that tenant spaces of different departments realize cross-departmental data exchange through a data controlled exchange system, and manage the directories of exchanged data of each department through a unified data directory management system.

[0121] The following is a detailed description of the data exchange process using the tenant space of department A as an example:

[0122] When tenant space A corresponding to department A needs to obtain exchange data from other departments, tenant space A can first query the location corresponding to the exchange data from the unified data directory management system. The corresponding location can be, for example, the tenant space storing the exchange data, or the interface directory corresponding to the exchange data.

[0123] When tenant space A determines the location corresponding to the exchange data, the tenant space A can send a request to the data-controlled exchange system to obtain the exchange data, so that the data-controlled exchange system obtains the exchange data from the location corresponding to the exchange data according to the request and returns it to tenant space A.

[0124] The data exchange system based on tenant space provided in the embodiment of the present application realizes data exchange across departments through multiple tenant spaces, a unified data directory management system, and a data controlled exchange system. By dividing each department into independent tenant spaces, the data between different departments is effectively isolated, solving the security problem of data in the exchange process; by dividing the tenant space into a front-end domain and a production domain, the exchange data and business data within the department are effectively isolated, solving the problem that the normal operation of the business system is easily affected during data exchange; by connecting the exchange data and the directory through a unified data directory management system, multiple tenant spaces are uniformly managed, and the data exchange process is standardized.

[0125] Figure 5 The data exchange method process based on tenant space provided in the embodiment of the present application Figure 1 This embodiment aims to explain the data interaction between different tenant spaces. Figure 5 As shown, the data exchange method based on tenant space provided in this embodiment includes:

[0126] S101: Acquire first exchange data from a data controlled exchange system through a data access area of ​​a first department, and preprocess the first exchange data to obtain second exchange data, where the first exchange data is data of a second department.

[0127] Since the data access area of ​​the first department is communicatively connected to the data-controlled exchange system, and the data-controlled exchange system is communicatively connected to the second department, the data access area of ​​the first department can obtain the exchange data sent by the tenant space corresponding to other departments through the data-controlled exchange system, and pre-process the exchange data of other departments.

[0128] Preprocessing refers to the process in which the data access area of ​​the department performs standardized processing on the exchange data of other departments, such as format conversion, character conversion, deduplication, escape, splitting, merging, desensitization, encryption, etc. This application does not impose any special restrictions on the specific implementation of preprocessing.

[0129] It is understandable that the received first exchange data may also include other data not needed by the first department. Therefore, when the first exchange data is acquired in the data access area of ​​the first department, the first exchange data needs to be preprocessed to extract the required second exchange data from the first exchange data.

[0130] Among them, the first department can be, for example, this department, and the second department can be, for example, other departments. The first exchange data is the exchange data of other departments obtained by the data access area of ​​this department from the data controlled exchange system, and the second exchange data is the standardized exchange data obtained by this department after preprocessing the exchange data of other departments.

[0131] S102: Perform directory mounting processing on the second exchange data through the data sharing area of ​​the first department to obtain a directory mounting relationship of the second exchange data.

[0132] The directory mounting refers to mounting the exchange data on the directory so that the exchange data and the directory form a corresponding association relationship, so that the location of the exchange data can be accessed through the directory.

[0133] The purpose of this step is to obtain the directory mounting relationship of the second exchange data by performing directory mounting processing on the second exchange data, so that the exchange data can be exchanged through the data controlled exchange system.

[0134] In one possible implementation, the data controlled exchange system pushes the exchange data of other departments to the data access area of ​​the department, and the data access area pre-processes the exchange data of other departments and pushes it to the data sharing library in the data sharing area of ​​the department. The data sharing library generates a data directory corresponding to the second exchange data based on the second exchange data, and performs data directory mounting processing on the second exchange data and the data directory to obtain the data directory mounting relationship of the second exchange data.

[0135] In another possible implementation, the data controlled exchange system pushes the exchange data of other departments to the data access area of ​​the department, and the data access area pre-processes the exchange data of other departments and pushes it to the data service library in the data sharing area of ​​the department. The data service library generates an interface directory corresponding to the second exchange data based on the second exchange data, and performs interface directory mounting processing on the second exchange data and the interface directory to obtain the interface directory mounting relationship of the second exchange data.

[0136] S103: Sending the directory attachment relationship to a unified data directory management system through the data sharing area of ​​the first department, so that the unified data directory management system verifies the directory attachment relationship, and after the verification is passed, retains the directory attachment relationship.

[0137] It can be understood that the data sharing area of ​​the tenant space of each department is connected to the unified data directory management system in communication, so the corresponding directories formed by the exchange data of each department can be uniformly managed through the unified data directory management system.

[0138] The purpose of this step is to verify through the unified data directory management system whether the data directory attachment pushed by the data sharing library and / or the interface directory attachment pushed by the data service library is correct, thereby verifying whether the exchange data pushed from the production domain to the front-end domain by each department is business data that can be exchanged externally, so as to ensure the data security of each department in the process of providing exchange data externally. After the verification is passed, the directory attachment relationship is retained so that the data controlled exchange system obtains the exchange data from the location corresponding to the exchange data.

[0139] The unified data directory management system is used to verify whether the data directory mounting pushed by the data sharing library and / or the interface directory mounting pushed by the data service library is correct, and when the data directory mounting and / or the interface directory mounting are correct, the data directory mounting and / or the interface directory mounting are retained.

[0140] The following is a detailed description of the data exchange process using the tenant space of department A as an example:

[0141] When tenant space A corresponding to department A needs to obtain exchange data from other departments, tenant space A can first query the location corresponding to the exchange data from the unified data directory management system. The corresponding location can be, for example, the tenant space storing the exchange data, or the interface directory corresponding to the exchange data.

[0142] When tenant space A determines the location corresponding to the exchange data, the tenant space A can send a request to the data-controlled exchange system to obtain the exchange data, so that the data-controlled exchange system obtains the exchange data from the location corresponding to the exchange data according to the request and returns it to tenant space A.

[0143] The tenant space-based data exchange method provided in the embodiment of the present application obtains the first exchange data of the second department from the data controlled exchange system through the data access area of ​​the first department, and pre-processes the first exchange data to obtain the second exchange data; performs directory mounting processing on the second exchange data through the data sharing area of ​​the first department to obtain the directory mounting relationship of the second exchange data; sends the directory mounting relationship to the unified data directory management system through the data sharing area of ​​the first department, and retains the directory mounting relationship after verification; effectively isolates the data between different departments, solves the security problems existing in the data exchange process; and uniformly manages multiple tenant spaces and standardizes the data exchange process.

[0144] Figure 6 The data exchange method process based on tenant space provided in the embodiment of the present application Figure 2 This embodiment is in Figure 5Based on the embodiment, the data exchange method based on the tenant space is described in detail. Figure 6 As shown, the data exchange method based on tenant space provided in this embodiment includes:

[0145] S201: Acquire first exchange data from a data controlled exchange system through a data access area of ​​a first department, and preprocess the first exchange data to obtain second exchange data, where the first exchange data is data of a second department.

[0146] Step S201 is similar to the above step S101 and will not be described again.

[0147] S202: Send the second exchange data to a shared collection library or a unified data warehouse, so that the first department retains and processes the second exchange data.

[0148] The shared collection library is used to receive the pre-processed exchange data of other departments sent by the data access area, so as to back up the pre-processed exchange data of other departments.

[0149] It can be understood that the second exchange data is the exchange data of other departments obtained after pre-processing through the data access area of ​​the first department. The second exchange data is backed up to prevent the second exchange data from being accidentally deleted or overwritten and becoming inaccessible. The second exchange data can be restored from the shared collection library; or when the second exchange data has multiple historical versions, the historical exchange data can be backed up and managed through the shared collection library so that the first department can obtain the required second exchange data.

[0150] The unified data warehouse is used to receive the pre-processed exchange data of other departments sent by the data access area, so as to collect and summarize the pre-processed exchange data of other departments and provide unified data resource support. The data stored in the unified data warehouse is the business data of multiple departments.

[0151] It can be understood that the unified data warehouse collects and summarizes the exchange data of other departments after pre-processing, which refers to the process of classifying and summarizing the exchange data of other departments according to certain objects. By collecting and summarizing the exchange data of other departments, various data resource libraries composed of the exchange data of other departments can be obtained, such as: basic information resource libraries, major task subject libraries, major field theme libraries and other data resource libraries.

[0152] S203: The data sharing library receives the second exchange data sent by the data access area.

[0153] The data sharing library is communicatively connected with the data access area to receive exchange data from other departments pushed by the data access area, so that the exchange data is exchanged through the data controlled exchange system.

[0154] S204: The data sharing library generates a data directory corresponding to the second exchange data according to the second exchange data, and performs data directory mounting processing on the second exchange data and the data directory to obtain a data directory mounting relationship of the second exchange data.

[0155] The directory mounting refers to mounting the exchange data on the directory so that the exchange data and the directory form a corresponding association relationship, so that the location of the exchange data can be determined through the directory.

[0156] The purpose of this step is to obtain the data directory mounting relationship of the second exchange data by performing data directory mounting processing on the second exchange data, so that the exchange data can provide exchange services to the outside through the data controlled exchange system.

[0157] The data controlled exchange system pushes the exchange data of other departments to the data access area of ​​the department. The data access area pre-processes the exchange data of other departments and pushes it to the data sharing library in the data sharing area of ​​the department. The data sharing library generates a data directory corresponding to the second exchange data based on the second exchange data, and performs data directory mounting processing on the second exchange data and the data directory to obtain the data directory mounting relationship of the second exchange data.

[0158] S205: Sending the data directory attachment relationship to a unified data directory management system through the data sharing library, so that the unified data directory management system verifies the data directory attachment relationship, and after the verification is passed, retains the data directory attachment relationship.

[0159] Among them, the unified data directory management system receives the data directory attachment relationship sent by the data sharing library, and verifies the data directory attachment relationship to verify whether the exchange data pushed by each department from the production domain to the front-end domain is business data that can be exchanged externally, so as to ensure the data security of each department in the process of providing exchange data externally.

[0160] After verification, the data directory attachment relationship is retained. The purpose of this step is to obtain the location of the required exchange data based on the data directory attachment relationship in the unified data directory management system, so that the data controlled exchange system can obtain the exchange data from the location corresponding to the exchange data.

[0161] In one possible implementation, when tenant space A corresponding to department A needs to obtain exchange data from other departments, tenant space A can first query the location corresponding to the exchange data from the unified data directory management system. The corresponding location can, for example, be the tenant space that stores the exchange data.

[0162] When tenant space A determines the location corresponding to the exchange data, the tenant space A can send a request to the data-controlled exchange system to obtain the exchange data, so that the data-controlled exchange system obtains the exchange data from the location corresponding to the exchange data according to the request and returns it to tenant space A.

[0163] S206: The data service library receives the second exchange data sent by the data access area.

[0164] The data service library is in communication connection with the data access area, and is used to receive the exchange data of other departments pushed by the data access area, so that the exchange data is exchanged through the data controlled exchange system.

[0165] S207: The data service library generates an interface directory corresponding to the second exchange data according to the second exchange data, and performs interface directory mounting processing on the second exchange data and the interface directory to obtain an interface directory mounting relationship of the second exchange data.

[0166] The interface directory mounting refers to encapsulating the received exchange data into an interface and mounting it with the interface directory so that the exchange data can provide interface services to the outside.

[0167] The purpose of this step is to obtain the interface directory mounting relationship of the second exchange data by performing interface directory mounting processing on the second exchange data, so that the exchange data can provide interface services to the outside through the data controlled exchange system.

[0168] In one possible implementation, the data controlled exchange system pushes the exchange data of other departments to the data access area of ​​the department, and the data access area pre-processes the exchange data of other departments and pushes it to the data service library in the data sharing area of ​​the department. The data service library generates a data directory corresponding to the second exchange data based on the second exchange data, and performs interface directory mounting processing on the second exchange data and the data directory to obtain the interface directory mounting relationship of the second exchange data.

[0169] S208: Sending the interface directory attachment relationship to a unified data directory management system through the data service library, so that the unified data directory management system verifies the interface directory attachment relationship, and after the verification is passed, retains the interface directory attachment relationship.

[0170] Among them, the unified data directory management system receives the interface directory attachment relationship sent by the data service library, and verifies the interface directory attachment relationship to verify whether the exchange data pushed by each department from the production domain to the front-end domain is business data that can provide interface services to the outside world, so as to ensure the data security of each department in the process of providing exchange data to the outside world.

[0171] After verification, the interface directory attachment relationship is retained. The purpose of this step is to obtain the location of the required exchange data based on the interface directory attachment relationship in the unified data directory management system, so that the data controlled exchange system can obtain the exchange data from the location corresponding to the exchange data.

[0172] In one possible implementation, when tenant space A corresponding to department A needs to obtain exchange data of other departments, tenant space A can first query the location corresponding to the exchange data from the unified data directory management system. The corresponding location can, for example, be the interface directory corresponding to the exchange data.

[0173] When tenant space A determines the location corresponding to the exchange data, the tenant space A can send a request to the data-controlled exchange system to obtain the exchange data, so that the data-controlled exchange system obtains the exchange data from the location corresponding to the exchange data according to the request and returns it to tenant space A.

[0174] The data exchange method based on tenant space provided in the embodiment of the present application is carried out by sending the second exchange data to a shared collection library or a unified data warehouse; the data sharing library / data service library receives the second exchange data sent by the data access area; the data sharing library / data service library generates a data directory / interface directory corresponding to the second exchange data according to the second exchange data, and performs data directory / interface directory mounting processing on the second exchange data and the data directory / interface directory to obtain the data directory / interface directory mounting relationship of the second exchange data; the data directory / interface directory mounting relationship is sent to a unified data directory management system through the data sharing library / data service library, so that the unified data directory management system verifies the data directory / interface directory mounting relationship, and after the verification is passed, the data directory / interface directory mounting relationship is retained; the data between different departments are effectively isolated, and the security issues existing in the data exchange process are solved; multiple tenant spaces are uniformly managed, and the data exchange process is standardized.

[0175] Figure 7 The data exchange method process based on tenant space provided in the embodiment of the present application Figure 3 This embodiment aims to explain the data flow steps of exchanging data in the tenant space. Figure 7 As shown, the data exchange method based on tenant space provided in this embodiment includes:

[0176] S301: Acquire, through the business application library of the first department, third exchange data sent by the sub-business application library of the first department.

[0177] The first department may be, for example, the current department, and the third exchange data is the exchange data of the current department; the business application library is used to receive the exchange data pushed by multiple sub-business application libraries of the current department.

[0178] Since the sub-business application library stores various business data of the department and maintains the normal use of the department's business system, when the department provides exchange data to the outside, it does not directly obtain the exchange data through the sub-business application library, but manages the data sources of multiple sub-business application libraries through the business application library, and pushes the exchange data pushed by multiple sub-business application libraries to the data sharing library and / or the data service library, so that the department's business system is not affected.

[0179] S302: performing directory mounting processing on the third exchange data through the data sharing area of ​​the first department to obtain a directory mounting relationship of the third exchange data.

[0180] The first department may be, for example, the current department, and the directory attachment process is to associate the exchange data with the directory to form an association relationship.

[0181] The purpose of this step is to further verify the directory attachment relationship by performing directory attachment processing on the third exchange data, and to perform retention processing.

[0182] Exemplarily, directory mounting processing may be performed on the exchange data of the department through the data sharing area of ​​the department to obtain the directory mounting relationship of the exchange data of the department.

[0183] S303: Send the directory attachment relationship to a unified data directory management system through the data sharing area of ​​the first department, so that the unified data directory management system verifies the directory attachment relationship, and after the verification is passed, retains the directory attachment relationship.

[0184] Among them, the unified directory management system is used to verify whether the data directory mounting pushed by the data sharing library in the data sharing area and / or the interface directory mounting pushed by the data service library are correct, and when the data directory mounting and / or the interface directory mounting are correct, the data directory mounting and / or the interface directory mounting are retained.

[0185] It can be understood that the business application library of the first department obtains the third exchange data sent by the sub-business application library of the first department, and then performs directory mounting processing on the third exchange data through the data sharing area of ​​the first department. After obtaining the directory mounting relationship of the third exchange data, it is necessary to verify the directory mounting relationship. By verifying whether the mounting relationship between the third exchange data and the corresponding directory is correct, it is ensured that the exchange data of the first department is exchange data shared externally, thereby ensuring the security of the business data of the first department.

[0186] The directory attachment relationship is retained and processed through the unified data directory management system so that other departments can obtain the association relationship between the third exchange data and the data directory attachment and / or the interface directory through the unified data directory management system, thereby obtaining the exchange data of the first department through the data controlled exchange system.

[0187] The tenant space-based data exchange method provided in the embodiment of the present application obtains the third exchange data sent by the sub-business application library of the first department through the business application library of the first department; performs directory mounting processing on the third exchange data through the data sharing area of ​​the first department to obtain the directory mounting relationship of the third exchange data; sends the directory mounting relationship to the unified data directory management system through the data sharing area of ​​the first department, so that the unified data directory management system verifies the directory mounting relationship, and retains the directory mounting relationship after the verification is passed; the exchange data and business data within the department are effectively isolated, and the problem that the normal operation of the business system is easily affected during data exchange in the prior art is solved; multiple tenant spaces are managed in a unified manner, and the data exchange process is standardized.

[0188] So far, the technical solution of the present application has been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present application is obviously not limited to these specific embodiments, and the above embodiments are only used to illustrate the technical solution of the present application rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A data exchange system based on tenant space, characterized in that: The data exchange system includes: a data controlled exchange system and a plurality of tenant spaces, wherein each department corresponds to a tenant space, and each tenant space includes: a pre-domain and a production domain; The front-end domain is used to obtain the exchange data of other departments through the data controlled exchange system and provide the exchange data of the department to other departments; The production domain is used to store the acquired exchange data of other departments and manage the exchange data of the department; The data controlled exchange system is used to realize cross-departmental data exchange after obtaining a data exchange task.

2. The data exchange system according to claim 1, characterized in that: The pre-domain includes: a data sharing area and a data access area; The data sharing area is used to provide the exchange data of the department to other departments, so that other departments can obtain the exchange data of the department through the data controlled exchange system; The data access area is used to pre-process the exchange data of other departments and transmit the pre-processed exchange data to the data sharing area or the production domain.

3. The data exchange system according to claim 2, characterized in that: The data sharing area includes: a data sharing library and a data service library; The data sharing library is used to receive the exchange data of the department pushed by the production domain and / or the exchange data of other departments pushed by the data access area, and to mount the received exchange data with the corresponding data directory so that the exchange data can be exchanged through the data controlled exchange system; The data service library is used to receive the exchange data pushed by the production domain and / or the exchange data of other departments pushed by the data access area, and encapsulate the received exchange data into an interface, and connect it to the interface directory so that the exchange data provides interface services to the outside.

4. The data exchange system according to claim 3, characterized in that: The data access area includes: a source library and a standard library; The post source library is used to store exchange data of other departments obtained through the data controlled exchange system; The standard library is used to store standardized exchange data formed after preprocessing the exchange data in the paste source library; The standard library is also used to push the pre-processed exchange data of other departments to the production domain, the data sharing library and the data service library.

5. The data exchange system according to claim 4, characterized in that: The production domain includes: a business application library and a shared collection library; The business application library is used to receive exchange data pushed by multiple sub-business application libraries of the department, and push the received exchange data pushed by multiple sub-business application libraries to the data sharing library and / or the data service library; The shared collection library is used to receive the pre-processed exchange data of other departments sent by the standard library, so as to back up the pre-processed exchange data of other departments; The shared collection library is also used to push the pre-processed exchange data of other departments to the data sharing library and / or the data service library.

6. The data exchange system according to claim 5, characterized in that: The production domain also includes: a unified data warehouse; The unified data warehouse is used to receive the pre-processed exchange data from other departments sent by the standard library, so as to collect and summarize the pre-processed exchange data from other departments and provide unified data resource support. The data stored in the unified data warehouse is the business data of multiple departments.

7. The data exchange system according to claim 3, characterized in that: The data exchange system also includes: a unified data directory management system; The unified data directory management system is used to verify whether the data directory mounting pushed by the data sharing library and / or the interface directory mounting pushed by the data service library is correct, and when the data directory mounting and / or the interface directory mounting are correct, the data directory mounting and / or the interface directory mounting are retained.

8. A data exchange method based on tenant space, characterized in that: The method comprises: Acquire first exchange data from the data controlled exchange system through the data access area of ​​the first department, and pre-process the first exchange data to obtain second exchange data, where the first exchange data is data of the second department; Performing directory mounting processing on the second exchange data through the data sharing area of ​​the first department to obtain a directory mounting relationship of the second exchange data; The directory attachment relationship is sent to a unified data directory management system through the data sharing area of ​​the first department, so that the unified data directory management system verifies the directory attachment relationship and retains the directory attachment relationship after the verification is passed.

9. The method according to claim 8, characterized in that The data sharing area includes: a data sharing library. If the directory mounting process is a data directory mounting process, the directory mounting process is performed on the second exchange data through the data sharing area of ​​the first department to obtain the directory mounting relationship of the second exchange data, including: The data sharing library receives the second exchange data sent by the data access area; The data sharing library generates a data directory corresponding to the second exchange data according to the second exchange data, and performs data directory mounting processing on the second exchange data and the data directory to obtain a data directory mounting relationship of the second exchange data; The step of sending the directory attachment relationship to a unified data directory management system through the data sharing area of ​​the first department includes: The data directory attachment relationship is sent to a unified data directory management system through the data sharing library, so that the unified data directory management system verifies the data directory attachment relationship, and after the verification is passed, retains the data directory attachment relationship.

10. The method according to claim 8, characterized in that The data sharing area further includes: a data service library. If the directory mounting process is an interface directory mounting process, the directory mounting process is performed on the second exchange data through the data sharing area of ​​the first department to obtain the directory mounting relationship of the second exchange data, including: The data service library receives the second exchange data sent by the data access area; The data service library generates an interface directory corresponding to the second exchange data according to the second exchange data, and performs interface directory mounting processing on the second exchange data and the interface directory to obtain an interface directory mounting relationship of the second exchange data; The step of sending the directory attachment relationship to a unified data directory management system through the data sharing area of ​​the first department includes: The interface directory attachment relationship is sent to a unified data directory management system through the data service library, so that the unified data directory management system verifies the interface directory attachment relationship, and after the verification is passed, retains the interface directory attachment relationship.

11. The method according to claim 8, characterized in that After preprocessing the first exchange data to obtain second exchange data, the method further includes: The second exchange data is sent to a shared collection library or a unified data warehouse, so that the first department retains and processes the second exchange data.

12. A data exchange method based on tenant space, characterized in that: The method comprises: Acquire the third exchange data sent by the sub-business application library of the first department through the business application library of the first department; Performing directory mounting processing on the third exchange data through the data sharing area of ​​the first department to obtain a directory mounting relationship of the third exchange data; The directory attachment relationship is sent to a unified data directory management system through the data sharing area of ​​the first department, so that the unified data directory management system verifies the directory attachment relationship and retains the directory attachment relationship after the verification is passed.

Images