CN111324368B - Data sharing method and server - Google Patents
Data sharing method and server Download PDFInfo
- Publication number
- CN111324368B CN111324368B CN201811539370.7A CN201811539370A CN111324368B CN 111324368 B CN111324368 B CN 111324368B CN 201811539370 A CN201811539370 A CN 201811539370A CN 111324368 B CN111324368 B CN 111324368B
- Authority
- CN
- China
- Prior art keywords
- data
- identifier
- sharing
- user
- user identifier
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000012986 modification Methods 0.000 claims description 14
- 230000004048 modification Effects 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 7
- 238000004891 communication Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 8
- 238000011156 evaluation Methods 0.000 description 3
- 238000012549 training Methods 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000007781 pre-processing Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Storage Device Security (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the invention provides a data sharing method and a server, the method is applied to the server, the server stores data created by different users, the data can only be checked by the creating users, the data is part or all of the data in an algorithm workflow, and the method comprises the following steps: receiving a sharing instruction comprising a data identifier; setting the data corresponding to the data identifier as shared data; receiving a data acquisition request comprising the data identifier; and sending the data corresponding to the data identifier. By implementing the embodiment of the invention, the data sharing efficiency can be improved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a data sharing method and a server.
Background
With the continuous development of computer technology, the use of algorithms to solve problems has become a common way to solve problems. In the process of developing an algorithm, a plurality of software developers commonly cooperate to complete the algorithm. Thus, in the algorithm development process, software developers may need to share data such as code written by themselves to other software developers. At present, when data such as written codes and the like are required to be shared, the data required to be shared is required to be packaged, and then the data is copied to other software developers through storage equipment such as a mobile hard disk and the like. Particularly in the case of a large amount of shared data, the copy time is long, so that the data sharing efficiency is lowered.
Disclosure of Invention
The embodiment of the invention provides a data sharing method and a server, which are used for improving data sharing efficiency.
An embodiment of the present invention provides a data sharing method, where the method is applied to a server, where the server stores data created by different users, where the data can only be viewed by the creating user, and the data is part or all of data in an algorithm workflow, and the method includes:
receiving a sharing instruction comprising a data identifier;
setting the data corresponding to the data identifier as shared data;
receiving a data acquisition request comprising the data identifier;
and sending the data corresponding to the data identifier.
In one embodiment, the sharing instruction further includes a first user identification, and the method further includes:
acquiring a second user identifier of a creating user of the data corresponding to the data identifier;
and judging whether the first user identifier is the same as the second user identifier, and executing the step of setting the data corresponding to the data identifier as shared data under the condition that the first user identifier is the same as the second user identifier.
In one embodiment, the method further comprises:
and judging whether the data corresponding to the data identifier is shared data or not, and executing the step of sending the data corresponding to the data identifier when the data is judged to be shared data.
In one embodiment, the data acquisition request further includes a third user identification, the method further comprising:
and judging whether the second user identifier is the same as the third user identifier, and executing the step of judging whether the data corresponding to the data identifier is shared data or not under the condition that the second user identifier and the third user identifier are different.
In one embodiment, the sharing instruction further includes a sharing manner, and the sending the data corresponding to the data identifier includes:
and sending the data corresponding to the data identifier under the condition that the sharing mode is all sharing.
In one embodiment, in a case that the sharing manner is partial sharing, the sharing instruction further includes a sharing user identifier, and the method further includes:
judging whether the third user identifier belongs to the shared user identifier, and executing the step of sending the data corresponding to the data identifier under the condition that the third user identifier belongs to the shared user identifier.
In one embodiment, the sharing instruction further includes a sharing authority, and after the sending the data corresponding to the data identifier, the method further includes:
receiving a modification instruction comprising the data identification, modification data information and replacement data;
and replacing the data corresponding to the modified data information in the data corresponding to the data identification by using the replacement data.
A second aspect of the embodiment of the present invention provides a server, where the server stores data created by different users, where the data can only be viewed by the creating user, and the data is part or all of data in an algorithm workflow, where the data includes:
the receiving unit is used for receiving a sharing instruction comprising a data identifier;
a setting unit, configured to set data corresponding to the data identifier received by the receiving unit as shared data;
the receiving unit is further configured to receive a data acquisition request including the data identifier;
and the transmitting unit is used for transmitting the data corresponding to the data identifier received by the receiving unit.
In one embodiment, the sharing instruction further includes a first user identification, and the server further includes:
the acquisition unit is used for acquiring a second user identifier of the creation user of the data corresponding to the data identifier;
and the first judging unit is used for judging whether the first user identifier received by the receiving unit is the same as the second user identifier acquired by the acquiring unit, and the setting unit sets the data corresponding to the data identifier as shared data under the condition that the first judging unit judges that the first user identifier is the same as the second user identifier.
In one embodiment, the server further comprises:
and the second judging unit is used for judging whether the data corresponding to the data identifier received by the receiving unit is shared data or not, and the transmitting unit transmits the data corresponding to the data identifier when the second judging unit judges that the data is shared data.
In one embodiment, the data acquisition request further includes a third user identification, and the server further includes:
and the third judging unit is used for judging whether the second user identifier is the same as the third user identifier received by the receiving unit, and if the third judging unit judges that the second user identifier is different, the second judging unit judges whether the data corresponding to the data identifier is shared data.
In an embodiment, the sharing instruction further includes a sharing manner, and the sending unit is specifically configured to send the data corresponding to the data identifier when the sharing manner is all sharing.
In one embodiment, in the case that the sharing manner is partial sharing, the sharing instruction further includes a sharing user identifier, and the server further includes:
and the fourth judging unit is used for judging whether the third user identifier received by the receiving unit belongs to the shared user identifier, and the transmitting unit transmits data corresponding to the data identifier under the condition that the fourth judging unit judges that the third user identifier belongs to the shared user identifier.
In one embodiment, the sharing instruction further includes a sharing authority, and the receiving unit is further configured to receive a modification instruction including the data identifier, modification data information, and replacement data after the sending unit sends the data corresponding to the data identifier in a case that the sharing authority is readable and writable;
the server further includes:
and the replacing unit is used for replacing the data corresponding to the modified data information in the data corresponding to the data identifier by using the replacing data received by the receiving unit.
A third aspect of the embodiments of the present invention provides a server storing data created by different users, the data being viewable only by the creating user, the data being part or all of the data in an algorithm workflow, the server comprising a processor, a memory, and a transceiver, the processor, the memory, and the server being interconnected, wherein:
the transceiver is used for receiving a sharing instruction comprising a data identifier;
the memory is used for storing a computer program, the computer program comprises program code, and the processor is used for calling the program code to execute the following operations:
setting the data corresponding to the data identifier as shared data;
the transceiver is further configured to receive a data acquisition request including the data identifier;
the transceiver is further configured to send data corresponding to the data identifier.
In one embodiment, the sharing instructions further comprise a first user identification, and the processor is further configured to invoke the program code to:
acquiring a second user identifier of a creating user of the data corresponding to the data identifier;
and judging whether the first user identifier is the same as the second user identifier, and executing the step of setting the data corresponding to the data identifier as shared data under the condition that the first user identifier is the same as the second user identifier.
In one embodiment, the processor is further configured to invoke the program code to:
judging whether the data corresponding to the data identifier is shared data or not, and transmitting the data corresponding to the data identifier by the transceiver under the condition that the data is judged to be shared data.
In one embodiment, the data acquisition request further includes a third user identification, and the processor is further configured to invoke the program code to:
and judging whether the second user identifier is the same as the third user identifier, and executing the step of judging whether the data corresponding to the data identifier is shared data or not under the condition that the second user identifier and the third user identifier are different.
In one embodiment, the sharing instruction further includes a sharing manner, and the transceiver sending the data corresponding to the data identifier includes:
and sending the data corresponding to the data identifier under the condition that the sharing mode is all sharing.
In one embodiment, in the case that the sharing manner is partial sharing, the sharing instruction further includes a sharing user identifier, and the processor is further configured to invoke the program code to perform the following operations:
judging whether the third user identifier belongs to the shared user identifier, and transmitting data corresponding to the data identifier by the transceiver under the condition that the third user identifier belongs to the shared user identifier.
In one embodiment, the sharing instruction further includes a sharing authority, and the transceiver is further configured to receive a modification instruction including the data identifier, modification data information, and replacement data after sending data corresponding to the data identifier if the sharing authority is readable and writable;
the processor is further configured to invoke the program code to:
and replacing the data corresponding to the modified data information in the data corresponding to the data identification by using the replacement data.
A fourth aspect provides a readable storage medium storing a computer program comprising program code which when executed by a processor causes the processor to perform the data sharing method provided by the first aspect or any embodiment of the first aspect.
A fifth aspect provides an application for executing the data sharing method provided by the first aspect or any embodiment of the first aspect at runtime.
In the embodiment of the invention, the server stores data created by different users, the data is part or all of the data in the algorithm workflow and can only be checked by the creating user, the server receives a sharing instruction comprising a data identifier, sets the data corresponding to the data identifier as shared data, receives a data acquisition request comprising the data identifier, and sends the data corresponding to the data identifier. Therefore, after the data in the algorithm workflow stored on the server is set as the shared data, the user can acquire the data from the server without copying, and the data sharing efficiency can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart of a data sharing method according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating another data sharing method according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an AI algorithm workflow provided by an embodiment of the invention;
fig. 5 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another server according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The embodiment of the invention provides a data sharing method and a server, which are used for improving data sharing efficiency. The following will describe in detail.
In order to better understand the data sharing method and the server provided by the embodiment of the present invention, a network architecture used in the embodiment of the present invention is described below. Referring to fig. 1, fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention. As shown in fig. 1, the network architecture may include a server 101 and one or more terminal devices 102 (3 are schematically shown in fig. 1), with the server 101 and the terminal devices 102 being connected by a network. A user identifier, such as a user account, may be set for each user, and in addition, a user password may be configured for each user identifier to verify whether the user corresponding to the user identifier is a legal user. The terminal device 102 may establish a communication connection with the server 101 through the user identifier, and one terminal device 102 may establish a communication connection with the server 101 through a plurality of user identifiers, but may establish a communication connection with the server 101 through only one user identifier at a time. After the terminal device 102 establishes a communication connection with the server 101, the user may create new data on the terminal device 102, view the stored data, and modify the stored data, with the data created by each user through the terminal device 102 being stored by the server 101 under the corresponding user identification. The terminal device 102 may be a terminal device, such as a desktop computer, a notebook computer, or other devices.
Referring to fig. 2, fig. 2 is a flow chart of a data sharing method according to an embodiment of the present invention based on the network architecture shown in fig. 1. Some of the steps in the flow chart shown in fig. 2 may be split into several steps. The data sharing method is applied to the server. As shown in fig. 2, the data sharing method may include the following steps.
201. And receiving a sharing instruction comprising the data identifier from the first terminal equipment.
In this embodiment, the server may receive a communication connection request including or carrying a user identifier from the terminal device, and then may determine whether the user identifier belongs to a user identifier created by the server, and in case that it is determined that the user identifier belongs to the user identifier created by the server, the server may send a communication connection establishment completion message to the terminal device, and then may perform communication between the server and the terminal device. In addition, the communication connection request may further include or carry a user password, and when it is determined that the user identifier belongs to the user identifier created by the server, whether the user password is correct or not may be continuously determined, and when it is determined that the user password is correct, the server sends a communication connection establishment completion message to the terminal device. In case that the user identification is judged not to belong to the created user identification or the user password is wrong, the server can send the information of the user identification or the password to the terminal equipment.
In this embodiment, after the server establishes a communication connection with the terminal device, the software developer may create data in the server through the terminal device, where the data is part or all of the data in the algorithm workflow, such as the entire algorithm workflow, a certain task node in one algorithm workflow, input and output of a certain task node in one algorithm workflow, and the like, and in the case where the data is created but not shared, the data can only be viewed and modified by the creating user. The algorithm may be an artificial intelligence (artificial intelligence, AI) algorithm, or may be another algorithm, which is not limited in this embodiment. Referring to fig. 4, fig. 4 is a schematic diagram of an AI algorithm workflow according to an embodiment of the present invention. As shown in fig. 4, a workflow is formed by three tasks of data preprocessing, model training and model evaluation, and the three tasks are interdependent. In model training, multiple instances are implemented to perform model training simultaneously, with parameters of each instance being different. After the model evaluation task is completed, a model evaluation report is generated, including the values of the corresponding parameters of each model.
In this embodiment, after the server establishes a communication connection with the first terminal device, the server may receive a sharing instruction including or carrying the data identifier from the first terminal device. In addition, the sharing instruction can also comprise or carry sharing authority and sharing mode. Sharing rights include read-only and readable-writable. Under the condition that the sharing authority is read-only, other users can only view the sharing data and cannot modify the sharing data; in the case where the sharing right is readable and writable, other users can view not only the shared data but also modify the shared data. The sharing mode may include all sharing, i.e., sharing data to all users in the server, and partial sharing, i.e., sharing data to some users in the server. In the case that the sharing mode is partial sharing, the sharing instruction may further include or carry a user identifier of the shared partial user, that is, a sharing user identifier. In addition, the sharing instruction may further include a first user identification of a user using the first terminal device.
202. Setting the data corresponding to the data identification as shared data.
In this embodiment, after receiving the sharing instruction from the first terminal device, the server may directly set the data corresponding to the data identifier as the shared data. When the sharing instruction further includes a sharing authority and a sharing mode, in the process of setting the data corresponding to the data identifier as the shared data, the sharing authority and the sharing mode of the data corresponding to the data identifier also need to be set.
In this embodiment, the second user identifier of the creating user of the data corresponding to the data identifier may be obtained first, then, whether the first user identifier is the same as the second user identifier is determined, and if it is determined that the first user identifier is the same as the second user identifier, it is indicated that the user sending the sharing instruction is the creating user of the data, that is, the creating user is sharing the data, and the data corresponding to the data identifier is set as the sharing data. Under the condition that the first user identification is different from the second user identification, the user sending the sharing instruction is not the creation user of the data, namely, the creation user is not sharing the data, and the non-creation user does not have the authority of sharing the data, so that the sharing instruction can be directly discarded, or the sharing instruction can be discarded, and meanwhile, the information without the sharing authority can be sent to the first terminal equipment.
203. A data acquisition request including a data identification is received from a second terminal device.
In this embodiment, after the server establishes a communication connection with the second terminal device, the server may receive a data acquisition request including or carrying a data identifier from the second terminal device. In addition, the data acquisition request may further comprise a third user identification of the user using the second terminal device. The first terminal device and the second terminal device may be the same terminal device or different terminal devices.
204. And sending data corresponding to the data identification to the second terminal equipment.
In this embodiment, after receiving the data acquisition request from the second terminal device, the server may directly send data corresponding to the data identifier to the second terminal device.
In this embodiment, whether the second user identifier is the same as the third user identifier may be determined first, and if it is determined that the second user identifier is the same as the third user identifier, it is indicated that the user who obtains the data is the creation user of the data, and the data corresponding to the data identifier is directly sent to the second terminal device. And under the condition that the second user identifier and the third user identifier are different, indicating that the user for acquiring the data is not the creation user of the data, and continuously judging whether the data corresponding to the data identifier is the shared data. And when the data corresponding to the data identifier is judged not to be shared data, the data acquisition request can be directly discarded, and meanwhile, an unauthorized message can be sent to the second terminal equipment. And under the condition that the data corresponding to the data identifier is judged to be shared data, acquiring a sharing mode of the data corresponding to the data identifier. And directly sending the data corresponding to the data identifier to the second terminal equipment under the condition that the acquired sharing mode is all sharing. And if the acquired sharing mode is partial sharing, continuously judging whether the third user identifier belongs to the sharing user identifier of the data corresponding to the data identifier, and if the third user identifier is judged to belong to the sharing user identifier of the data corresponding to the data identifier, indicating that the user corresponding to the third user identifier is the sharing user of the data corresponding to the data identifier, and sending the data corresponding to the data identifier to the second terminal equipment. Under the condition that the third user identification does not belong to the shared user identification of the data corresponding to the data identification, the user corresponding to the third user identification is indicated not to be the shared user of the data corresponding to the data identification, the data acquisition request can be directly discarded, and meanwhile, a non-authority message can be sent to the second terminal equipment.
In the data sharing method described in fig. 2, after the data in the algorithm workflow stored on the server is set as the shared data, the user can acquire the data from the server without copying, so that the data sharing efficiency can be improved.
Referring to fig. 3, fig. 3 is a flow chart of another data sharing method according to an embodiment of the present invention based on the network architecture shown in fig. 1. The order of execution of the steps in the flowchart shown in fig. 3 may be changed, some steps may be split into several steps, and some steps may be omitted, according to different needs. The data sharing method is applied to the server. As shown in fig. 3, the data sharing method may include the following steps.
301. A sharing instruction comprising a data identifier and a first user identifier is received from a first terminal device.
Step 301 is the same as step 201, and the detailed description refers to step 201, and will not be repeated here.
302. It is determined whether the first user identifier is identical to the second user identifier, and if it is determined that the first user identifier is identical to the second user identifier, step 303 is executed.
In this embodiment, after receiving the sharing instruction from the first terminal device, the server may first obtain the second user identifier of the creating user of the data corresponding to the data identifier, then determine whether the first user identifier is the same as the second user identifier, and if it is determined that the first user identifier is the same as the second user identifier, indicate that the user sending the sharing instruction is the creating user of the data, that is, the creating user is sharing the data, and execute step 303. Under the condition that the first user identification is different from the second user identification, the user sending the sharing instruction is not the creation user of the data, namely, the creation user is not sharing the data, and the non-creation user does not have the authority of sharing the data, so that the sharing instruction can be directly discarded, or the sharing instruction can be discarded, and meanwhile, the information without the sharing authority can be sent to the first terminal equipment.
303. Setting the data corresponding to the data identification as shared data.
In this embodiment, the server sets the data corresponding to the data identifier as the shared data when it is determined that the first user identifier is the same as the second user identifier. When the sharing instruction further includes a sharing authority and a sharing mode, in the process of setting the data corresponding to the data identifier as the shared data, the sharing authority and the sharing mode of the data corresponding to the data identifier also need to be set.
304. A data acquisition request comprising a data identifier and a third user identifier is received from a second terminal device.
Step 304 is the same as step 203, please refer to step 203 for detailed description, and detailed description is omitted herein.
305. It is determined whether the second user identifier and the third user identifier are identical, and if they are different, step 306 is executed, and if they are identical, step 309 is executed.
In this embodiment, after receiving the data acquisition request from the second terminal device, the server may first determine whether the second user identifier is the same as the third user identifier, and if it is determined that the second user identifier is the same as the third user identifier, it indicates that the user who acquires the data is the creation user of the data, and then step 309 is directly executed. In case it is determined that the second user identification and the third user identification are different, it is indicated that the user who acquired the data is not the creating user of the data, and step 306 is performed.
306. Whether or not the data corresponding to the data identifier is shared data is determined, and if it is determined that the data is shared data, step 307 is executed.
In this embodiment, when it is determined that the second user identifier and the third user identifier are different, it may be continuously determined whether the data corresponding to the data identifier is shared data. If it is determined that the data corresponding to the data identifier is shared data, step 307 is executed. And when the data corresponding to the data identifier is judged not to be shared data, the data acquisition request can be directly discarded, and meanwhile, an unauthorized message can be sent to the second terminal equipment.
307. And acquiring a sharing mode of the data corresponding to the data identifier.
308. If the sharing method of the data corresponding to the data identifier is partial sharing, it is determined whether the third user identifier belongs to the shared user identifier of the data corresponding to the data identifier, and if it is determined that the third user identifier belongs to the shared user identifier of the data corresponding to the data identifier, step 309 is executed.
In this embodiment, after the server obtains the sharing manner of the data corresponding to the data identifier, step 309 is directly executed when the sharing manner of the data corresponding to the data identifier is all sharing.
In this embodiment, when the sharing manner of the data corresponding to the data identifier is partial sharing, it may be continuously determined whether the third user identifier belongs to the shared user identifier of the data corresponding to the data identifier, and when it is determined that the third user identifier belongs to the shared user identifier of the data corresponding to the data identifier, it is indicated that the user corresponding to the third user identifier is the shared user of the data corresponding to the data identifier, and step 309 is executed. Under the condition that the third user identification does not belong to the shared user identification of the data corresponding to the data identification, the user corresponding to the third user identification is indicated not to be the shared user of the data corresponding to the data identification, the data acquisition request can be directly discarded, and meanwhile, a non-authority message can be sent to the second terminal equipment.
309. And sending data corresponding to the data identification to the second terminal equipment.
310. And receiving a modification instruction comprising the data identification, the modification data information and the replacement data from the second terminal equipment under the condition that the sharing authority is readable and writable.
In this embodiment, after the server sends the data corresponding to the data identifier to the second terminal device, the server may receive a modification instruction including the data identifier, the modified data information, and the replacement data from the second terminal device when the sharing authority is readable and writable and the user needs to modify the data corresponding to the data identifier.
311. And replacing data corresponding to the modified data information in the data corresponding to the data identification by using the replacement data.
In the data sharing method described in fig. 3, after the data in the algorithm workflow stored on the server is set as the shared data, the user can acquire the data from the server without copying, so that the data sharing efficiency can be improved.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a server according to an embodiment of the present invention, based on the network architecture shown in fig. 1. The server stores data created by different users, the data can only be checked by the creating user, and the data is part or all of the data in the algorithm workflow. As shown in fig. 5, the server may include:
a receiving unit 501, configured to receive a sharing instruction including a data identifier;
a setting unit 502, configured to set data corresponding to the data identifier received by the receiving unit 501 as shared data;
a receiving unit 501, configured to receive a data acquisition request including a data identifier;
a transmitting unit 503, configured to transmit the data corresponding to the data identifier received by the receiving unit 501.
As a possible implementation manner, the sharing instruction further includes a first user identifier, and the server may further include:
an obtaining unit 504, configured to obtain a second user identifier of the creating user of the data corresponding to the data identifier received by the receiving unit 501;
a first determining unit 505, configured to determine whether the first user identifier received by the receiving unit 501 is the same as the second user identifier acquired by the acquiring unit 502, where the setting unit 502 sets the data corresponding to the data identifier as shared data if the first determining unit 505 determines that the first user identifier is the same.
As a possible implementation manner, the server may further include:
a second determining unit 506, configured to determine whether the data corresponding to the data identifier received by the receiving unit 501 is shared data, and when the second determining unit 506 determines that the data is shared data, the transmitting unit 503 transmits the data corresponding to the data identifier.
As a possible implementation manner, the data acquisition request further includes a third user identifier, and the server may further include:
a third determining unit 507, configured to determine whether the second user identifier is the same as the third user identifier received by the receiving unit 501, and if the third determining unit 507 determines that the data is different, the second determining unit 506 determines whether the data corresponding to the data identifier is shared data.
As a possible implementation manner, the sharing instruction further includes a sharing manner, and the sending unit 503 is specifically configured to send data corresponding to the data identifier when the sharing manner is all sharing.
As a possible implementation manner, in the case that the sharing manner is partial sharing, the sharing instruction further includes a sharing user identifier, and the server may further include:
a fourth determining unit 508, configured to determine whether the third user identifier received by the receiving unit 501 belongs to the shared user identifier, where the sending unit 503 sends data corresponding to the data identifier when the fourth determining unit 508 determines that the third user identifier belongs to the shared user identifier.
As a possible implementation manner, the sharing instruction further includes a sharing authority, and the receiving unit 501 is further configured to receive a modification instruction including a data identifier, modification data information, and replacement data after the sending unit 503 sends data corresponding to the data identifier in a case where the sharing authority is readable and writable;
the server may further include:
a replacing unit 509 for replacing data corresponding to the modified data information in the data corresponding to the data identification with the replacement data received by the receiving unit 501.
The server of the present embodiment may correspond to the server in the method described in the embodiment of the present invention, and the foregoing and other operations and/or functions of each unit in the server are respectively for implementing the corresponding flows in each method in fig. 2 to 3, which are not described herein for brevity.
Referring to fig. 6, fig. 6 is a schematic diagram of a structure of another server according to an embodiment of the present invention based on the network architecture shown in fig. 1. The server stores data created by different users, the data can only be checked by the creating user, and the data is part or all of the data in the algorithm workflow. As shown in fig. 6, the server may include a processor 601, a memory 602, a transceiver 603, and a bus 604. The processor 601 may be a general purpose Central Processing Unit (CPU), a plurality of CPUs, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention. The Memory 602 may be, but is not limited to, a read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a random access Memory (random access Memory, RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a compact disc read-Only Memory (Compact Disc Read-Only Memory) or other optical disk storage, a compact disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 602 may be separate or integrated with the processor 601. Bus 604 is coupled to processor 601. Bus 604 carries information among the components described above. Wherein:
a transceiver 603 for receiving a sharing instruction including a data identifier;
the memory 602 is used for storing a computer program comprising program code, the processor 601 being used for invoking the program code to:
setting the data corresponding to the data identifier as shared data;
the transceiver 603 is further configured to receive a data acquisition request including a data identifier;
the transceiver 603 is further configured to send data corresponding to the data identifier.
As a possible implementation, the sharing instruction further includes a first user identification, and the processor 601 is further configured to invoke the program code to perform the following operations:
acquiring a second user identifier of the creating user of the data corresponding to the data identifier;
judging whether the first user identifier is the same as the second user identifier, and if so, executing the step of setting the data corresponding to the data identifier as shared data.
As a possible implementation, the processor 601 is further configured to invoke the program code to perform the following operations:
whether or not the data corresponding to the data identifier is shared data is determined, and if the data is determined to be shared data, the transceiver 603 transmits the data corresponding to the data identifier.
As a possible implementation, the data acquisition request further comprises a third user identification, and the processor 601 is further configured to invoke the program code to perform the following operations:
judging whether the second user identifier is the same as the third user identifier, and executing the step of judging whether the data corresponding to the data identifier is shared data or not under the condition that the second user identifier is different from the third user identifier.
As a possible implementation manner, the sharing instruction further includes a sharing manner, and the sending, by the transceiver 603, data corresponding to the data identifier includes:
and when the sharing mode is all sharing, sending the data corresponding to the data identifier.
As a possible implementation manner, in the case that the sharing manner is partial sharing, the sharing instruction further includes a sharing user identifier, and the processor 601 is further configured to invoke the program code to perform the following operations:
judging whether the third user identifier belongs to the shared user identifier, and if so, transmitting data corresponding to the data identifier by the transceiver 603.
As a possible implementation manner, the sharing instruction further includes a sharing authority, and the transceiver 603 is further configured to receive a modification instruction including the data identifier, the modified data information and the replacement data after sending the data corresponding to the data identifier in a case where the sharing authority is readable and writable;
the processor 601 is also operative to invoke program code to perform the following operations:
and replacing data corresponding to the modified data information in the data corresponding to the data identification by using the replacement data.
It should be understood that the server of the present embodiment may correspond to the server shown in fig. 5, and the foregoing and other operations and/or functions in the server are respectively for implementing the corresponding flows of the server in the respective methods in fig. 2-3, and are not repeated herein for brevity.
In one embodiment, a storage medium is provided for storing an application for executing the data sharing method of fig. 2-3 at runtime.
In one embodiment, an application is provided for executing the data sharing method of FIGS. 2-3 at runtime.
The foregoing has outlined rather broadly the more detailed description of embodiments of the invention, wherein the principles and embodiments of the invention are explained in detail using specific examples, the above examples being provided solely to facilitate the understanding of the method and core concepts of the invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
Claims (9)
1. The data sharing method is characterized in that the method is applied to a server, the server stores data created by different users, wherein the data is stored by the server under a corresponding user identifier, the data can only be checked by the creating user, and the data is part or all of the data in an algorithm workflow, and the method comprises the following steps:
receiving a sharing instruction comprising a data identifier and a first user identifier, wherein the sharing instruction comprises a sharing authority and a sharing mode;
acquiring a second user identifier of a creating user of the data corresponding to the data identifier;
judging whether the first user identifier is the same as the second user identifier; and setting the data corresponding to the data identifier as shared data under the condition that the data identifier is judged to be the same, wherein the method comprises the following steps of: setting the sharing authority and sharing mode of the data corresponding to the data identifier;
receiving a data acquisition request comprising the data identifier;
and sending the data corresponding to the data identifier.
2. The method according to claim 1, wherein the method further comprises:
and judging whether the data corresponding to the data identifier is shared data or not, and executing the step of sending the data corresponding to the data identifier when the data is judged to be shared data.
3. The method of claim 2, wherein the data acquisition request further comprises a third user identification, the method further comprising:
and judging whether the second user identifier is the same as the third user identifier, and executing the step of judging whether the data corresponding to the data identifier is shared data or not under the condition that the second user identifier and the third user identifier are different.
4. A method according to claim 3, wherein said transmitting data corresponding to said data identity comprises:
and sending the data corresponding to the data identifier under the condition that the sharing mode is all sharing.
5. The method of claim 4, wherein in the case where the sharing manner is partial sharing, the sharing instruction further includes a sharing user identifier, the method further comprising:
judging whether the third user identifier belongs to the shared user identifier, and executing the step of sending the data corresponding to the data identifier under the condition that the third user identifier belongs to the shared user identifier.
6. The method according to any one of claims 1-5, wherein, in the case where the sharing right is readable and writable, after the sending the data corresponding to the data identifier, the method further comprises:
receiving a modification instruction comprising the data identification, modification data information and replacement data;
and replacing the data corresponding to the modified data information in the data corresponding to the data identification by using the replacement data.
7. A server, wherein the server stores data created by different users, wherein the data is stored by the server under a corresponding user identifier, the data can only be viewed by the creating user, and the data is part or all of data in an algorithm workflow, and the method comprises the following steps:
the receiving unit is used for receiving a sharing instruction comprising a data identifier and a first user identifier, wherein the sharing instruction comprises a sharing authority and a sharing mode;
the first judging unit is used for acquiring a second user identifier of the creating user of the data corresponding to the data identifier; judging whether the first user identifier is the same as the second user identifier;
a setting unit, configured to set, when it is determined that the data identifiers are the same, data corresponding to the data identifiers received by the receiving unit as shared data, where the setting unit includes: setting the sharing authority and sharing mode of the data corresponding to the data identifier;
the receiving unit is further configured to receive a data acquisition request including the data identifier;
and the transmitting unit is used for transmitting the data corresponding to the data identifier received by the receiving unit.
8. A server, wherein the server stores data created by different users, wherein the data is stored by the server under corresponding user identities, the data can only be viewed by the creating user, the data is part or all of the data in an algorithm workflow, the server comprises a processor, a memory and a transceiver, the processor, the memory and the server are connected with each other, wherein:
the transceiver is used for receiving a sharing instruction comprising a data identifier and a first user identifier, wherein the sharing instruction comprises a sharing authority and a sharing mode;
the processor is used for calling program codes to execute the following operations:
acquiring a second user identifier of a creating user of the data corresponding to the data identifier;
judging whether the first user identifier is the same as the second user identifier;
the memory is used for storing a computer program, the computer program comprises program code, and the processor is used for calling the program code to execute the following operations:
and setting the data corresponding to the data identifier as shared data under the condition that the data identifier is judged to be the same, wherein the method comprises the following steps of: setting the sharing authority and sharing mode of the data corresponding to the data identifier;
the transceiver is further configured to receive a data acquisition request including the data identifier;
the transceiver is further configured to send data corresponding to the data identifier.
9. A storage medium storing data created by different users, wherein the data is stored by the storage medium under corresponding user identifications, the data is viewable only by a creating user, the data is part or all of data in an algorithmic workflow, the storage medium stores a computer program comprising program code which when executed by a processor causes the processor to:
receiving a sharing instruction comprising a data identifier and a first user identifier, wherein the sharing instruction comprises a sharing authority and a sharing mode;
acquiring a second user identifier of a creating user of the data corresponding to the data identifier;
judging whether the first user identifier is the same as the second user identifier; and setting the data corresponding to the data identifier as shared data under the condition that the data identifier is judged to be the same, wherein the method comprises the following steps of: setting the sharing authority and sharing mode of the data corresponding to the data identifier;
receiving a data acquisition request comprising the data identifier;
and sending the data corresponding to the data identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811539370.7A CN111324368B (en) | 2018-12-17 | 2018-12-17 | Data sharing method and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811539370.7A CN111324368B (en) | 2018-12-17 | 2018-12-17 | Data sharing method and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111324368A CN111324368A (en) | 2020-06-23 |
| CN111324368B true CN111324368B (en) | 2024-03-22 |
Family
ID=71166837
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811539370.7A Active CN111324368B (en) | 2018-12-17 | 2018-12-17 | Data sharing method and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111324368B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113485784A (en) * | 2021-06-08 | 2021-10-08 | 中国联合网络通信集团有限公司 | Model training method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101452454A (en) * | 2007-11-30 | 2009-06-10 | 华为技术有限公司 | File set sharing method and device |
| CN101751421A (en) * | 2008-12-08 | 2010-06-23 | 北京中星微电子有限公司 | Anisomerous synchronization method, system and device of database in video monitoring system |
| CN101859139A (en) * | 2010-06-01 | 2010-10-13 | 杭州和利时自动化有限公司 | Data sharing realizing method of distribution type control system and device thereof |
| CN103108005A (en) * | 2011-11-11 | 2013-05-15 | 上海聚力传媒技术有限公司 | Method, device and system for achieving data sharing in distributed storage system |
| CN104580364A (en) * | 2014-12-01 | 2015-04-29 | 百度在线网络技术（北京）有限公司 | Resource sharing method and device |
| CN105187377A (en) * | 2015-06-25 | 2015-12-23 | 联想(北京)有限公司 | Data processing method, data processing device, data access method and data access device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104660678B (en) * | 2015-01-16 | 2018-05-18 | 深信服科技股份有限公司 | Using data sharing method and device |
-
2018
- 2018-12-17 CN CN201811539370.7A patent/CN111324368B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101452454A (en) * | 2007-11-30 | 2009-06-10 | 华为技术有限公司 | File set sharing method and device |
| CN101751421A (en) * | 2008-12-08 | 2010-06-23 | 北京中星微电子有限公司 | Anisomerous synchronization method, system and device of database in video monitoring system |
| CN101859139A (en) * | 2010-06-01 | 2010-10-13 | 杭州和利时自动化有限公司 | Data sharing realizing method of distribution type control system and device thereof |
| CN103108005A (en) * | 2011-11-11 | 2013-05-15 | 上海聚力传媒技术有限公司 | Method, device and system for achieving data sharing in distributed storage system |
| CN104580364A (en) * | 2014-12-01 | 2015-04-29 | 百度在线网络技术（北京）有限公司 | Resource sharing method and device |
| CN105187377A (en) * | 2015-06-25 | 2015-12-23 | 联想(北京)有限公司 | Data processing method, data processing device, data access method and data access device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111324368A (en) | 2020-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109636317B (en) | Service control method, device, system and storage medium | |
| US11150896B2 (en) | Automated generation of service definitions for message queue application clients | |
| CN108287708B (en) | Data processing method and device, server and computer readable storage medium | |
| CN104391716A (en) | Plug-in-based application program implementing method and device | |
| CN106339177A (en) | Method and device for creating virtual machines | |
| CN111694617B (en) | Processing method of network offline model, artificial intelligence processing device and related products | |
| CN107294750B (en) | Cloud cluster energy self-identification distributed configuration management method and device | |
| CN111414391A (en) | Method and system for accessing multiple data sources | |
| CN112036125B (en) | Document management method and device and computer equipment | |
| CN110278192A (en) | Method, apparatus, computer equipment and the readable storage medium storing program for executing of extranet access Intranet | |
| CN107480554A (en) | A kind of right management method, rights management device and intelligent terminal | |
| CN110737425B (en) | Method and device for establishing application program of charging platform system | |
| CN111767144A (en) | Transaction routing determination method, device, equipment and system for transaction data | |
| CN110381150B (en) | Data processing method and device on block chain, electronic equipment and storage medium | |
| CN115098112A (en) | Method, equipment and medium for deploying financial cloud application resources | |
| CN108459910A (en) | A kind of method and apparatus for deleting resource | |
| CN111324368B (en) | Data sharing method and server | |
| CN113794581A (en) | Distributed CP unified deployment method, network equipment and storage medium | |
| CN112181599A (en) | Model training method, device and storage medium | |
| CN113094048A (en) | Data display rule determining method, display method, device, equipment and medium | |
| CN112561690A (en) | Method, system, equipment and storage medium for testing credit card staging service interface | |
| CN114116681B (en) | Data migration method and device | |
| CN112286622A (en) | Virtual machine migration processing and strategy generating method, device, equipment and storage medium | |
| CN112380411B (en) | Sensitive word processing method, device, electronic equipment, system and storage medium | |
| CN111464395A (en) | Method and device for creating block chain and readable storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |