CN117130991A - Data sharing method, device, equipment and storage medium - Google Patents
Data sharing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN117130991A CN117130991A CN202311109381.2A CN202311109381A CN117130991A CN 117130991 A CN117130991 A CN 117130991A CN 202311109381 A CN202311109381 A CN 202311109381A CN 117130991 A CN117130991 A CN 117130991A
- Authority
- CN
- China
- Prior art keywords
- data
- shared
- sharing
- subsystem
- area
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 230000008569 process Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 210000004258 portal system Anatomy 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/176—Support for shared access to files; File sharing support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data sharing method, a device, equipment and a storage medium, which can be applied to the distributed field or the financial field. The method comprises the following steps: when the second subsystem applies for accessing the shared data, determining the sharing range of the shared data; if the sharing range is shared among the subsystems, determining whether a sharing association relationship exists between the second subsystem and the first subsystem, wherein the first subsystem is a subsystem for writing the sharing data into a pre-opened sharing area, and the sharing area is determined according to the data type of the sharing data and/or the association of the sub-data contained in the sharing data; if the second subsystem and the first subsystem have a sharing association relationship, searching the sharing data from the sharing area, and sending the searched sharing data to the second subsystem. Therefore, the application can realize the data sharing between the first subsystem and the second subsystem, thereby improving the office efficiency.
Description
Technical Field
The present application relates to the field of data sharing technologies, and in particular, to a data sharing method, apparatus, device, and storage medium.
Background
In order to realize convenient office work, a plurality of subsystems are generally integrated into one large system at present, for example, a plurality of subsystems of a bank can be connected into an employee unified portal system, so that a bank employee can conduct various business transactions in the employee unified portal system.
When office work is performed based on one or more subsystems in a large system, a lot of text data and media data can be reused, however, the existing large system can only realize data sharing in one subsystem, and if office work involves a plurality of subsystems, the same data used by the plurality of subsystems cannot be shared, so that office work efficiency is low.
Disclosure of Invention
In view of the above, the present application provides a data sharing method, device, equipment and storage medium, which are used for solving the problem in the prior art that data sharing cannot be performed between subsystems and that all types of shared data are stored in a cache, resulting in poor data sharing effect, and the technical scheme is as follows:
a data sharing method, comprising:
when a second subsystem applies for accessing shared data, determining a sharing range of the shared data;
if the sharing range is inter-subsystem sharing, determining whether a sharing association relationship exists between the second subsystem and a first subsystem, wherein the first subsystem is a subsystem for writing the sharing data into a pre-opened sharing area, and the sharing area is determined according to the data type of the sharing data and/or the association of sub-data contained in the sharing data;
if the second subsystem and the first subsystem have a sharing association relationship, searching the sharing data from the sharing area, and sending the searched sharing data to the second subsystem.
Optionally, the determining of the shared area according to the data type of the shared data and/or the relevance of the sub data contained in the shared data includes:
if the shared data comprises sub data and the relevance of the sub data contained in the shared data is greater than or equal to a preset relevance threshold value, determining a pre-opened shared memory area as the shared area;
if the shared data comprises sub-data and the relevance of the sub-data contained in the shared data is smaller than the relevance threshold, determining the pre-opened shared memory area and/or shared disk area as the shared area, wherein the shared memory area is used for storing the text type sub-data contained in the shared data and the shared disk area is used for storing the stream file type sub-data contained in the shared data;
if the shared data does not contain sub data and the shared data is of a text type, determining the shared memory area as the shared area;
and if the shared data does not contain sub data and the shared data is of a stream file type, determining the shared disk area as the shared area.
Optionally, the determining process of the relevance of the sub data contained in the shared data includes:
determining the source and purpose of the sub-data contained in the shared data;
and determining the relevance of the sub data contained in the shared data according to the source and the purpose of the sub data contained in the shared data.
Optionally, the shared disk area is a shared disk area on a server.
Optionally, if the shared area is the shared memory area and the shared data is data under a field added with a preset prefix, the storage mode of the shared data in the shared area is encryption storage;
the searching the shared data from the shared area and sending the searched shared data to the second subsystem comprises the following steps:
searching ciphertext data and encryption and decryption factors corresponding to the shared data from the shared area;
and sending the searched ciphertext data and the encryption and decryption factor to the second subsystem, wherein the encryption and decryption factor is used for decrypting the ciphertext data to obtain the shared data.
Optionally, the determining whether the second subsystem has a shared association relationship with the first subsystem includes:
acquiring a pre-established data table, wherein the data table is used for storing sharing association relations among at least one group of subsystems;
and inquiring from the data table based on the identification of the second subsystem, and determining whether the second subsystem has a sharing association relationship with the first subsystem according to an inquiry result.
Optionally, the establishing process of the data table includes:
acquiring a sharing association relationship among at least one group of subsystems input by a user;
judging whether the sharing association relation between at least one group of subsystems is respectively in a preset scope indicated by a sharing prohibition condition, wherein the sharing prohibition condition describes subsystem pairs with parameters and data conflicts;
and storing the sharing association relation which is judged to be not in the scope indicated by the sharing prohibition condition into a pre-established empty table to obtain the data table.
A data sharing apparatus comprising:
the sharing range determining module is used for determining the sharing range of the sharing data when the second subsystem applies for accessing the sharing data;
the association relation determining module is used for determining whether the second subsystem and a first subsystem have a sharing association relation if the sharing range is shared among the subsystems, wherein the first subsystem is a subsystem for writing the sharing data into a pre-opened sharing area, and the sharing area is determined according to the data type of the sharing data and/or the association of the sub data contained in the sharing data;
and the shared data searching module is used for searching the shared data from the shared area and sending the searched shared data to the second subsystem if the second subsystem and the first subsystem have a shared association relation.
A data sharing device comprising a memory and a processor;
the memory is used for storing programs;
the processor is configured to execute the program to implement the steps of the data sharing method according to any one of the above.
A readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the data sharing method as claimed in any one of the preceding claims.
According to the technical scheme, when the second subsystem applies for accessing the shared data, the shared range of the shared data is determined, if the shared range is shared between the subsystems, whether the second subsystem has a shared association relationship with the first subsystem is determined, if the second subsystem has the shared association relationship with the first subsystem, the shared data is searched from the shared area, and the searched shared data is sent to the second subsystem. Therefore, the application can realize the data sharing between the first subsystem and the second subsystem, thereby improving the office efficiency.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of a data sharing method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a data sharing device according to an embodiment of the present application;
fig. 3 is a hardware structure block diagram of a data sharing device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The application provides a data sharing method, a device, equipment and a storage medium, and the data sharing method, the device, the equipment and the storage medium are described in detail through the following embodiments.
It should be noted that the data sharing method, the device, the equipment and the storage medium provided by the application can be applied to the distributed field or the financial field. The foregoing is merely an example, and is not intended to limit the application fields of the data sharing method, apparatus, device and storage medium provided by the present application.
Referring to fig. 1, a flow chart of a data sharing method according to an embodiment of the present application is shown, where the data sharing method may include:
step S101, when the second subsystem applies to access the shared data, the sharing range of the shared data is determined.
In the embodiment of the application, all the shared data have the identification information for representing the shared range, and the shared range of the shared data can be determined through the identification information.
Here, the sharing range includes intra-subsystem sharing and inter-subsystem sharing.
The sharing in the subsystem means that the data shared by one subsystem can only be used by the subsystem, and other subsystems are not allowed to access, for example, the client basic information shared by the subsystem a can only be used by the subsystem a, and if the client basic information is required to be used by other subsystems, the client basic information can only be obtained by a manual input or device reading mode, and the client basic information shared by the subsystem a is not allowed to be accessed.
The sharing between subsystems refers to that the data shared by one subsystem allows access of other subsystems having a shared association relationship with the subsystem, for example, the subsystem a and the subsystem B have a shared association relationship, so that the client basic information shared by the subsystem a allows access of the subsystem B, but the subsystem C having no shared association relationship with the subsystem a cannot access, so that the subsystem C can only be obtained by manual input or device reading if the client basic information is required.
Step S102, if the sharing range is the sharing between the subsystems, determining whether the second subsystem has a sharing association relationship with the first subsystem.
Here, the first subsystem is a subsystem for writing shared data into a pre-opened shared area, the first subsystem and the second subsystem are different subsystems, and the first subsystem and the second subsystem may be integrated into one large system, for example, integrated into an employee unified portal system. The employee unified portal system refers to a system for unified management of employees in a bank by using the front end of the system, and an atomic system is accessed to an employee unified portal, which is called a sub-component of the employee unified portal.
In order to realize sharing among subsystems, the first subsystem can write the shared data into a pre-opened shared area, so that other subsystems can acquire the shared data from the shared area. In order to keep consistent with the sharing manner in the subsystem, the embodiment of the application writes the shared data shared in the subsystem into the shared area.
The shared area is determined according to the data type of the shared data and/or the relevance of the sub data contained in the shared data.
Here, the data types include two types: the text type and the stream file type, the data of the stream file type is, for example, image, video, audio, etc., and the data amount of the text type is smaller than the data amount of the stream file type.
Step S103, if the second subsystem and the first subsystem have a sharing association relationship, searching the sharing data from the sharing area, and transmitting the searched sharing data to the second subsystem.
Specifically, if the second subsystem and the first subsystem have a shared association relationship, the data shared by the first subsystem can be accessed and used by the second subsystem, and similarly, the data shared by the second subsystem can be accessed and used by the first subsystem.
Therefore, when the second subsystem and the first subsystem have a sharing association relationship, the shared data searched from the sharing area can be sent to the second subsystem.
The data sharing method provided by the application determines the sharing range of the shared data when the second subsystem applies for accessing the shared data, if the sharing range is shared between the subsystems, determines whether the second subsystem has a sharing association relationship with the first subsystem, and if the second subsystem has the sharing association relationship with the first subsystem, searches the shared data from the sharing area and sends the searched shared data to the second subsystem. Therefore, the embodiment of the application can realize data sharing between the first subsystem and the second subsystem, thereby improving office efficiency.
In an alternative embodiment, the embodiment of the present application may further include the steps of: and if the sharing range is shared in the subsystem, rejecting the access request of the second subsystem.
Specifically, since the shared data that the second subsystem applies to access is the data shared by the first subsystem, and the first subsystem has marked the data for intra-subsystem sharing when sharing the data, that is, the first subsystem does not allow the second subsystem to access the shared data, the embodiment of the application can reject the access request of the second subsystem.
In some embodiments of the present application, the above-mentioned process of determining the shared area according to the data type of the shared data and/or the relevance of the sub-data included in the shared data is described, that is, when the first subsystem needs to store the shared data for sharing to other subsystems, the process of determining which shared area to use to store the shared data according to the data type of the shared data and/or the relevance of the sub-system included in the shared data is described.
Alternatively, the embodiments of the present application include various cases, which are described below.
First case: if the shared data does not contain sub data and the shared data is of a text type, determining the pre-opened shared memory area as a shared area; if the shared data does not contain sub data and the shared data is of a stream file type, the pre-opened shared disk area is determined to be a shared area.
Specifically, in the case where the shared data does not include sub data, the shared area storing the shared data may be determined only according to the data type of the shared data.
And if the shared data is of a streaming file type, determining the shared disk area as the shared area. Namely, the data volume of the text type shared data is smaller, and the embodiment of the application can store the text type shared data to the shared memory area; because the memory space is limited and the data volume of the shared data of the stream file type is large, in order to avoid occupying a large amount of memory space and causing the access speed of the shared data to be reduced, the shared data of the stream file type can be stored in the shared disk area.
Second case: if the shared data comprises sub-data and the relevance of the sub-data contained in the shared data is greater than or equal to a preset relevance threshold value, determining the pre-opened shared memory area as a shared area; if the shared data comprises sub-data and the relevance of the sub-data contained in the shared data is smaller than the relevance threshold, determining a pre-opened shared memory area and/or a shared disk area as a shared area, wherein the shared memory area is used for storing the text type sub-data contained in the shared data, and the shared disk area is used for storing the stream file type sub-data contained in the shared data.
Optionally, the process of determining the relevance of the sub-data contained in the shared data may include: determining the source and the purpose of the sub-data contained in the shared data, and determining the relevance of the sub-data contained in the shared data according to the source and the purpose of the sub-data contained in the shared data.
For example, the shared data includes three sub-data including a name, an identification card number and a certificate photo, and if the three sub-data are all from the identification card and are all used for determining the identity information of the client, then the three sub-data can be determined to have strong relevance.
In the above description, in the case where the shared data includes the sub data, the shared area storing the shared data may be determined according to the association of the sub data included in the shared data in combination with the data type of the shared data.
If the relevance of the sub-data contained in the shared data is smaller than a preset relevance threshold, distinguishing the data types of the sub-data contained in the common data, and determining the shared area according to the distinguished data types.
If the shared data only comprises the sub data of the text type, determining the shared memory area as a shared area; if the shared data only comprises the sub data of the stream file type, determining the shared disk area as a shared area; if the shared data contains both text type sub-data and stream file type sub-data, the shared memory area and the shared disk area are determined to be shared areas, in which case the text type sub-data is stored in the shared memory area and the stream file type sub-data is stored in the shared disk area.
In summary, when the relevance of each sub-data contained in the shared data is not strong, the embodiment of the application stores the text type sub-data and the stream file type sub-data separately. This is because: if the relevance of each sub-data contained in the shared data is not strong, the probability that each sub-data contained in the shared data is accessed together is low, and the sub-data can be stored separately at the moment, so that the phenomenon that a large amount of memory space is occupied because the sub-data of the stream file type with large data volume is stored in the shared memory area is avoided.
Otherwise, if the relevance of the sub-data contained in the shared data is greater than or equal to the preset relevance threshold, the data types of the sub-data contained in the shared data are not distinguished, and the shared memory area is directly determined as the shared area.
That is, when the relevance of the sub-data included in the shared data is high, each sub-data included in the shared data can be stored in the shared memory area without being separately stored, so that when other sub-systems access the shared data, the relevant sub-data can be searched out and returned together.
For example, the shared data includes a name (text type), an identification card number (text type) and a document photo (stream file type) in the identity document, all of which are information obtained by reading the identity document, and have strong relevance, and even if the three sub-data includes the text type and the stream file type, the three sub-data are still combined and stored in the shared memory area.
According to the embodiment of the application, the sub-data with strong relevance are put together, so that when the second sub-system requests to access the sub-data with strong relevance, the sub-data with strong relevance can be directly taken out together, the interaction times are reduced, the transaction time is saved, and the user experience is better.
In an alternative embodiment, the shared disk area may be a local disk area.
In view of the fact that the temporary path of the local disk may be changed when the switching sub-assembly (i.e., the switching sub-system, e.g., the first sub-system is switched to the second sub-system) is switched, the searching operation in step S103 is difficult, and preferably, the shared disk area may be a shared disk area on the server. The path of the shared disk on the server is more stable, so that the query work can be completed more quickly.
In another embodiment of the present application, if the shared area is a shared memory area and the shared data is data under a field with a preset prefix added, the storage mode of the shared data in the shared area is encrypted storage. For example, the shared data from the first subsystem is identity document information, and a preset prefix (for example, gtgx) is added to a field related to the identity document information, so that the shared data is encrypted and then stored in the shared memory area according to the embodiment of the application.
Optionally, in order to improve sharing efficiency as much as possible under the condition of encrypting the shared data, a key data confusion replacement algorithm can be selected as the encryption algorithm. Taking 12345 as shared data and 3 encryption and decryption factors as examples, key data confusion replacement algorithm is selected for encryption, and then ciphertext data is 45678.
Of course, the above encryption algorithm is merely an example, and other encryption algorithms may be selected in addition to the above, which is not specifically limited herein.
Based on this, the process of searching for shared data from the shared area and transmitting the searched shared data to the second subsystem in the foregoing may include: and searching ciphertext data and an encryption and decryption factor corresponding to the shared data from the shared area, and sending the searched ciphertext data and the encryption and decryption factor to the second subsystem, wherein the encryption and decryption factor is used for decrypting the ciphertext data to obtain the shared data.
Therefore, in the embodiment of the application, under the condition that the second subsystem has access to the shared data, the ciphertext data and the encryption and decryption factors can be returned to the second subsystem, so that the second subsystem decrypts the ciphertext data through the encryption and decryption factors, and the shared data can be obtained. The whole process system is automatically completed, so that the second subsystem does not need to input shared information manually or read the shared information by equipment, the time for the second subsystem to acquire the shared information is saved, and the service handling efficiency of the second subsystem is improved.
In one embodiment of the present application, the foregoing process of determining whether the second subsystem has a shared association relationship with the first subsystem is described.
In this embodiment, whether the second subsystem has a shared association relationship with the first subsystem may be determined through a pre-established data table, and specifically, the pre-established data table is obtained, where the data table is used to store the shared association relationship between at least one group of subsystems; and inquiring from the data table based on the identification of the second subsystem, and determining whether the second subsystem has a sharing association relationship with the first subsystem according to an inquiry result.
Specifically, when the second subsystem applies for accessing the shared data, the embodiment of the application can acquire the identifier of the second subsystem, then can query from the data table based on the identifier of the second subsystem, and if the second subsystem and the first subsystem are queried in the data table to have a corresponding relationship, then the second subsystem and the first subsystem are determined to have a shared association relationship; and otherwise, determining that the second subsystem and the first subsystem have no shared association relationship.
Optionally, the process of creating the data table may include: acquiring a sharing association relationship among at least one group of subsystems input by a user; judging whether sharing association relations among at least one group of subsystems are respectively in a preset scope indicated by a sharing prohibition condition, wherein the sharing prohibition condition describes subsystem pairs with parameters and data conflicts; and storing the sharing association relation which is judged to be not in the scope indicated by the forbidden sharing condition into a pre-established empty table to obtain a data table.
Specifically, the user may set the sharing association relationship between at least one group of subsystems according to the requirement, for example, the user sets that the subsystem A, B, C can share data, and the subsystem A, B, C is a group of sharing association relationship; in addition, it is further configured that data sharing may be performed between the subsystems D and E, and the subsystem A, B, C shares an association relationship for another group.
Considering that in practical application, parameters or data conflicts may exist between some subsystems, so that data sharing between the subsystems cannot be performed, and therefore, the embodiment of the application presets a sharing prohibition condition. If the sharing association relationship between any group of subsystems set by the user is in the range of the indication of the forbidden sharing condition, the group of the subsystems cannot take effect, and the embodiment of the application can prompt the user to configure failure and reasons. For example, the subsystem D is a subsystem for acquiring basic information of a client, and the user of the subsystem E is relatively complex, and there is a risk of data leakage, and at this time, a sharing prohibition condition may be that the subsystem D and the subsystem E are prohibited from sharing data, so that when the user sets that data sharing between the subsystems D and E is possible, the setting will fail.
The embodiment of the application can store the sharing association relation which is not in the scope indicated by the sharing prohibition condition into the data table. For example, in the above example, the shared associations made up of the subsystems A, B, C may be stored to the data table, whereas the shared associations made up of the subsystems D, E may not be stored to the data table.
After the sharing association relation set by the user is stored in the data table, the data sharing among the subsystems can be carried out based on the sharing association relation in the data table, and because the sharing association relation in the data table is set by the user according to the requirement condition of service handling of the user, the data sharing among the subsystems is carried out based on the sharing association relation in the data table, so that the service handling speed of the user can be improved, the service handling efficiency of the user is improved, and the user experience is better.
In order that those skilled in the art will more readily understand the present application, the following examples will be presented in their entirety.
Firstly, the embodiment of the application can pre-open a plurality of special areas (namely shared areas) for sharing data among all subsystems or inside the subsystems, wherein the special areas for sharing data need to be isolated from the data interaction area. Here, the shared area includes a shared memory area and a shared disk area.
Meanwhile, the embodiment of the application opens up an entrance for setting the subsystem with the shared association relationship, and the user can set the shared association relationship among the subsystems through the entrance, thereby establishing a data table.
When a user uses the first subsystem to conduct office work, shared data (such as customer identity information obtained through a second-generation identifier, card information obtained through an IC (Integrated Circuit, integrated circuit) card reader-writer and the like) can be obtained in the first subsystem, if the obtained shared data needs to be shared out (can be shared in the subsystems or can be shared among the subsystems, and can be distinguished through different identification information), the embodiment of the application can determine the shared area for storing the shared data according to the data type of the shared data and/or the relevance of the sub-data contained in the shared data, namely, the shared data is stored in the shared memory area and/or the shared disk area according to the above determination, and then the shared data is stored in the determined shared area.
If the shared data is data with a field added with a preset prefix, encrypting the data stored in the shared memory area when the shared data is stored in the shared area; if the shared data is not the data in the field added with the preset prefix, encryption is not needed when the shared data is stored in the shared memory area and/or the shared disk area.
If the first subsystem applies to access the shared data, the shared data can be searched from the shared area and returned to the first subsystem, and the whole process does not need to query the data table.
When the user switches from using the first subsystem to the second subsystem, if the second subsystem applies to access the shared data, the method is executed according to the steps S101-S103; and if the second subsystem applies for accessing the shared data and the shared range of the shared data is shared in the subsystem, rejecting the access request of the second subsystem.
Optionally, the embodiment of the application can record the production (i.e. the process of storing the shared data in the shared area) and consumption condition (i.e. the process of inquiring the shared data from the shared area and sending the shared data to the second subsystem) of the shared data, and if a problem is encountered, the shared data can be rapidly checked and recovered.
After the large system provided by the application is closed, the shared data in the shared area can be released, and the abuse of the data is prevented.
In summary, the data sharing method provided by the embodiment of the application can provide the most suitable data sharing modes in various scenes according to different scenes of the system, can improve the performance and the safety of the system, can provide new ideas for other system designs, and can effectively ensure the data sharing and the data safety with smaller resource consumption.
The embodiment of the application also provides a data sharing device, which is described below, and the data sharing device described below and the data sharing method described above can be referred to correspondingly.
Referring to fig. 2, a schematic structural diagram of a data sharing device according to an embodiment of the present application is shown, and as shown in fig. 2, the data sharing device may include: a shared range determination module 201, an association relationship determination module 202, and a shared data lookup module 203.
The shared range determining module 201 is configured to determine a shared range of the shared data when the second subsystem applies to access the shared data.
The association determining module 202 is configured to determine whether a sharing association exists between the second subsystem and the first subsystem if the sharing range is the inter-subsystem sharing, where the first subsystem is a subsystem that writes the sharing data into a pre-opened sharing area, and the sharing area is determined according to a data type of the sharing data and/or an association of sub-data included in the sharing data.
And the shared data searching module 203 is configured to search shared data from the shared area if the second subsystem and the first subsystem have a shared association relationship, and send the searched shared data to the second subsystem.
In one possible implementation manner, the process of determining the association of the shared region according to the data type of the shared data and/or the sub-data contained in the shared data in the association determining module may include:
if the shared data comprises sub-data and the relevance of the sub-data contained in the shared data is greater than or equal to a preset relevance threshold value, determining the pre-opened shared memory area as a shared area;
if the shared data comprises sub-data and the relevance of the sub-data contained in the shared data is smaller than the relevance threshold, determining a pre-opened shared memory area and/or a shared disk area as a shared area, wherein the shared memory area is used for storing the text type sub-data contained in the shared data, and the shared disk area is used for storing the stream file type sub-data contained in the shared data;
if the shared data does not contain the sub data and the shared data is of a text type, determining the shared memory area as a shared area;
if the shared data does not contain sub data and the shared data is of a stream file type, the shared disk area is determined to be a shared area.
In one possible implementation manner, the process of determining the sub-data included in the shared data in the association determining module may include:
determining the source and the purpose of the sub-data contained in the shared data;
and determining the relevance of the sub data contained in the shared data according to the source and the purpose of the sub data contained in the shared data.
In one possible implementation, the shared disk area is a shared disk area on a server.
In one possible implementation, if the shared area is a shared memory area and the shared data is data under a field with a preset prefix added, the storage mode of the shared data in the shared area is encrypted storage.
Based on this, the process of the shared data searching module searching the shared data from the shared area and transmitting the searched shared data to the second subsystem may include:
searching ciphertext data and encryption and decryption factors corresponding to the shared data from the shared area;
and sending the searched ciphertext data and the encryption and decryption factors to a second subsystem, wherein the encryption and decryption factors are used for decrypting the ciphertext data to obtain shared data.
In one possible implementation manner, the process of determining, by the association determining module, whether the second subsystem has a shared association with the first subsystem may include:
acquiring a pre-established data table, wherein the data table is used for storing sharing association relations among at least one group of subsystems;
and inquiring from the data table based on the identification of the second subsystem, and determining whether the second subsystem has a sharing association relationship with the first subsystem according to an inquiry result.
In one possible implementation manner, the process of establishing the data table by the association relationship determining module may include:
acquiring a sharing association relationship among at least one group of subsystems input by a user;
judging whether sharing association relations among at least one group of subsystems are respectively in a preset scope indicated by a sharing prohibition condition, wherein the sharing prohibition condition describes subsystem pairs with parameters and data conflicts;
and storing the sharing association relation which is judged to be not in the scope indicated by the forbidden sharing condition into a pre-established empty table to obtain a data table.
The embodiment of the application also provides a data sharing device. Optionally, fig. 3 shows a block diagram of a hardware structure of the data sharing device, and referring to fig. 3, the hardware structure of the data sharing device may include: at least one processor 301, at least one communication interface 302, at least one memory 303, and at least one communication bus 304;
in the embodiment of the present application, the number of the processor 301, the communication interface 302, the memory 303 and the communication bus 304 is at least one, and the processor 301, the communication interface 302 and the memory 303 complete communication with each other through the communication bus 304;
processor 301 may be a central processing unit CPU, or a specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of the present application, etc.;
the memory 303 may include a high-speed RAM memory, and may further include a non-volatile memory (non-volatile memory), etc., such as at least one magnetic disk memory;
wherein the memory 303 stores a program, the processor 301 may call the program stored in the memory 303, the program being configured to:
when the second subsystem applies for accessing the shared data, determining the sharing range of the shared data;
if the sharing range is shared among the subsystems, determining whether a sharing association relationship exists between the second subsystem and the first subsystem, wherein the first subsystem is a subsystem for writing the sharing data into a pre-opened sharing area, and the sharing area is determined according to the data type of the sharing data and/or the association of the sub-data contained in the sharing data;
if the second subsystem and the first subsystem have a sharing association relationship, searching the sharing data from the sharing area, and sending the searched sharing data to the second subsystem.
Alternatively, the refinement function and the extension function of the program may be described with reference to the above.
The embodiment of the application also provides a readable storage medium, on which a computer program is stored, which when executed by a processor, implements a data sharing method as described above.
Alternatively, the refinement function and the extension function of the program may be described with reference to the above.
Finally, it is further noted that relational terms such as second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A data sharing method, comprising:
when a second subsystem applies for accessing shared data, determining a sharing range of the shared data;
if the sharing range is inter-subsystem sharing, determining whether a sharing association relationship exists between the second subsystem and a first subsystem, wherein the first subsystem is a subsystem for writing the sharing data into a pre-opened sharing area, and the sharing area is determined according to the data type of the sharing data and/or the association of sub-data contained in the sharing data;
if the second subsystem and the first subsystem have a sharing association relationship, searching the sharing data from the sharing area, and sending the searched sharing data to the second subsystem.
2. The data sharing method according to claim 1, wherein the determining of the shared area according to the data type of the shared data and/or the relevance of the sub data included in the shared data includes:
if the shared data comprises sub data and the relevance of the sub data contained in the shared data is greater than or equal to a preset relevance threshold value, determining a pre-opened shared memory area as the shared area;
if the shared data comprises sub-data and the relevance of the sub-data contained in the shared data is smaller than the relevance threshold, determining the pre-opened shared memory area and/or shared disk area as the shared area, wherein the shared memory area is used for storing the text type sub-data contained in the shared data and the shared disk area is used for storing the stream file type sub-data contained in the shared data;
if the shared data does not contain sub data and the shared data is of a text type, determining the shared memory area as the shared area;
and if the shared data does not contain sub data and the shared data is of a stream file type, determining the shared disk area as the shared area.
3. The data sharing method according to claim 2, wherein the determining of the association of the sub-data included in the shared data includes:
determining the source and purpose of the sub-data contained in the shared data;
and determining the relevance of the sub data contained in the shared data according to the source and the purpose of the sub data contained in the shared data.
4. A data sharing method according to claim 2 or 3, wherein the shared disk area is a shared disk area on a server.
5. The data sharing method according to claim 2, wherein if the shared area is the shared memory area and the shared data is data in a field to which a preset prefix is added, the storage mode of the shared data in the shared area is encryption storage;
the searching the shared data from the shared area and sending the searched shared data to the second subsystem comprises the following steps:
searching ciphertext data and encryption and decryption factors corresponding to the shared data from the shared area;
and sending the searched ciphertext data and the encryption and decryption factor to the second subsystem, wherein the encryption and decryption factor is used for decrypting the ciphertext data to obtain the shared data.
6. The method of claim 1, wherein determining whether the second subsystem has a shared association with the first subsystem comprises:
acquiring a pre-established data table, wherein the data table is used for storing sharing association relations among at least one group of subsystems;
and inquiring from the data table based on the identification of the second subsystem, and determining whether the second subsystem has a sharing association relationship with the first subsystem according to an inquiry result.
7. The data sharing method of claim 6, wherein the data table establishment process comprises:
acquiring a sharing association relationship among at least one group of subsystems input by a user;
judging whether the sharing association relation between at least one group of subsystems is respectively in a preset scope indicated by a sharing prohibition condition, wherein the sharing prohibition condition describes subsystem pairs with parameters and data conflicts;
and storing the sharing association relation which is judged to be not in the scope indicated by the sharing prohibition condition into a pre-established empty table to obtain the data table.
8. A data sharing apparatus, comprising:
the sharing range determining module is used for determining the sharing range of the sharing data when the second subsystem applies for accessing the sharing data;
the association relation determining module is used for determining whether the second subsystem and a first subsystem have a sharing association relation if the sharing range is shared among the subsystems, wherein the first subsystem is a subsystem for writing the sharing data into a pre-opened sharing area, and the sharing area is determined according to the data type of the sharing data and/or the association of the sub data contained in the sharing data;
and the shared data searching module is used for searching the shared data from the shared area and sending the searched shared data to the second subsystem if the second subsystem and the first subsystem have a shared association relation.
9. A data sharing device comprising a memory and a processor;
the memory is used for storing programs;
the processor is configured to execute the program to implement the respective steps of the data sharing method according to any one of claims 1 to 7.
10. A readable storage medium having stored thereon a computer program, which, when executed by a processor, implements the steps of the data sharing method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311109381.2A CN117130991A (en) | 2023-08-30 | 2023-08-30 | Data sharing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311109381.2A CN117130991A (en) | 2023-08-30 | 2023-08-30 | Data sharing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117130991A true CN117130991A (en) | 2023-11-28 |
Family
ID=88852473
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311109381.2A Pending CN117130991A (en) | 2023-08-30 | 2023-08-30 | Data sharing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117130991A (en) |
-
2023
- 2023-08-30 CN CN202311109381.2A patent/CN117130991A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10621376B2 (en) | Personal ledger blockchain | |
| US11558360B2 (en) | Selective encryption of profile fields for multiple consumers | |
| US10985902B2 (en) | Dynamic symmetric searchable encryption | |
| US7854010B2 (en) | Method and apparatus for searching rights object and mapping method and mapping apparatus for the same | |
| EP2731044B1 (en) | Client computer for querying a database stored on a server via a network | |
| US20190377900A1 (en) | Protecting Personally Identifiable Information (PII) Using Tagging and Persistence of PII | |
| US8219544B2 (en) | Method and a computer program product for indexing files and searching files | |
| US20160006717A1 (en) | Prompting login account | |
| US11138323B2 (en) | Blockchain-based content management system, method, apparatus, and electronic device | |
| US9864880B1 (en) | Data encryption and isolation | |
| CN107515879B (en) | Method and electronic equipment for document retrieval | |
| US8769302B2 (en) | Encrypting data and characterization data that describes valid contents of a column | |
| US11972414B2 (en) | Data recording methods and apparatuses, electronic devices, and storage media | |
| CN107402821A (en) | Access control method, device and the equipment of shared resource | |
| US20080222112A1 (en) | Method and System for Document Searching and Generating to do List | |
| KR20170102219A (en) | Method and apparatus for processing transactions | |
| WO2022252880A1 (en) | Data processing method, apparatus and system, and storage medium | |
| JP4594078B2 (en) | Personal information management system and personal information management program | |
| US20100114834A1 (en) | Method and system for storing and retrieving information | |
| US11250151B2 (en) | Encrypted search over encrypted data with reduced volume leakage | |
| CN117130991A (en) | Data sharing method, device, equipment and storage medium | |
| CN116009791A (en) | Data classified storage management method, device, equipment and medium | |
| CN114661793A (en) | Fuzzy query method and device, electronic equipment and storage medium | |
| AU2015413372B2 (en) | Selective encryption of profile fields for multiple consumers | |
| JP6631091B2 (en) | Information processing apparatus and information processing program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |