CN114760359B - Method, system, server and computer readable storage medium for data sharing - Google Patents
Method, system, server and computer readable storage medium for data sharing Download PDFInfo
- Publication number
- CN114760359B CN114760359B CN202210398944.3A CN202210398944A CN114760359B CN 114760359 B CN114760359 B CN 114760359B CN 202210398944 A CN202210398944 A CN 202210398944A CN 114760359 B CN114760359 B CN 114760359B
- Authority
- CN
- China
- Prior art keywords
- data asset
- data
- request
- gateway
- server
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/102—Entity profiles
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application provides a data sharing method, a system, a server and a computer readable storage medium, and relates to the technical field of data processing. According to the method and the device, on the basis of realizing safe data access, the processing flow during data sharing is shortened, the response efficiency is improved, and then the user experience is improved.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a method, a system, a server, and a computer readable storage medium for data sharing.
Background
At present, when data sharing is performed in a mode of service interface call or file downloading, a request is generally required to be sent to a security token service, identity information is acquired through the security token service, then the request and the identity information are sent to a gateway, and after verification is passed, the gateway forwards the request to a corresponding service interface. However, in the prior art, more nodes are involved, and the processing flow is complicated, so that the efficiency of a client request is low, and the user experience is affected.
Disclosure of Invention
The invention aims to provide a data sharing method, a system, a server and a computer readable storage medium, which shorten the processing flow during data sharing on the basis of realizing safe data access, improve the response efficiency and further improve the user experience.
In a first aspect, the present application provides a method for sharing data, which is applied to a server; the server is respectively in communication connection with the data asset issuing end, the data asset requesting end and the gateway, and the data asset requesting end is in communication connection with the gateway; the method comprises the following steps: responding to an application filling operation initiated by the data asset request terminal, and carrying out sharing qualification check on the data asset request terminal; if the shared qualification of the data asset request end passes, sending pre-configured interface routing information to the data asset request end through the data asset release end; after receiving a data asset acquisition request initiated by a data asset request end, the gateway verifies the access authority of the data asset request end, and if the access authority passes the verification, the gateway responds to the data asset acquisition request forwarded by the gateway and sends shared data to the data asset request end; wherein the data asset acquisition request is initiated after receiving the interface routing information for the data asset request.
In an alternative embodiment, prior to the application filling operation initiated in response to the data asset request, the method further comprises: receiving a data asset to be shared uploaded from a data asset publishing terminal; and sending a route creation request to the gateway so that the gateway creates interface route information corresponding to the data asset to be shared.
In an alternative embodiment, after sending the preconfigured interface routing information to the data asset requesting end, the method further comprises: and adding the data asset request end to the shared white list in the gateway through the data asset issuing end.
In an alternative embodiment, the method further comprises: and responding to the user removing operation of the data asset issuing end, and removing the data asset requesting end from the shared white list in the gateway.
In an alternative embodiment, the application filling operation initiated by the data asset request end is used for filling application basic information, and the application basic information at least comprises the data asset use validity period and the request times.
In an alternative embodiment, the method further comprises: and modifying the application basic information of the data asset request terminal in response to the modification operation of the data asset release terminal on the application basic information filled in by the data asset request terminal.
In an alternative embodiment, the method further comprises: and after the expiration of the use validity period and/or the request times in the application basic information, removing the data asset request end from the shared white list.
In a second aspect, the present application provides a system for sharing data, including a server, and further including a data asset publishing end, a data asset requesting end and a gateway, which are respectively connected with the server in a communication manner, where the data asset requesting end is connected with the gateway in a communication manner; the server is used for responding to the application filling operation initiated by the data asset request terminal and carrying out sharing qualification check on the data asset request terminal; the data asset issuing end is used for sending the pre-configured interface routing information to the data asset requesting end through the data asset issuing end if the sharing qualification check of the data asset requesting end is passed; the gateway is used for verifying the access authority of the data asset request terminal after receiving the data asset acquisition request initiated by the data asset request terminal, and forwarding the data asset acquisition request to the server if the access authority passes the verification; the server is also used for responding to the data asset acquisition request forwarded by the gateway and sending the shared data to the data asset request end; wherein the data asset acquisition request is initiated after receiving the interface routing information for the data asset request.
In a third aspect, the present application provides a server comprising a processor and a memory, the memory storing computer executable instructions executable by the processor, the processor executing the computer executable instructions to implement the method of data sharing of any of the preceding embodiments.
In a fourth aspect, the present application provides a computer-readable storage medium storing computer-executable instructions that, when invoked and executed by a processor, cause the processor to implement a method of data sharing of any of the preceding embodiments.
The data sharing method, the system, the server and the computer readable storage medium are applied to the server which is respectively in communication connection with the data asset issuing end, the data asset requesting end and the gateway, and the data asset requesting end is in communication connection with the gateway. According to the method, a server responds to an application filling operation initiated by a data asset request terminal, the data asset request terminal carries out sharing qualification check, and if the sharing qualification check of the data asset request terminal passes, a data asset issuing terminal sends pre-configured interface routing information to the data asset request terminal so that the data asset request terminal requests corresponding sharing data assets according to the interface routing information. And after receiving the interface routing information, the data asset request end initiates a data asset acquisition request, when the gateway receives the data asset acquisition request initiated by the data asset request end, the gateway verifies the access authority of the data asset request end, and if the gateway verifies that the data asset request end has the access authority, the server responds to the data asset acquisition request forwarded by the gateway and sends the shared data to the data asset request end, so that the data sharing of the data asset issuing end and the data asset request end is realized. The method can realize safe data access without requesting token service, shortens the processing flow during data sharing, and particularly improves the response speed more aiming at the scene needing high-speed data sharing, thereby improving the user experience.
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 needed in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a block diagram of a system for data sharing according to an embodiment of the present application;
FIG. 2 is a flow chart of a method for data sharing according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a shared qualification checking provided in an embodiment of the present application;
FIG. 4 is a schematic flow chart of data asset publishing according to an embodiment of the present application;
FIG. 5 is a schematic flow chart of a method for initiating a data asset acquisition request to a gateway according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
In the prior art, when data sharing is performed in a mode of service interface call or file downloading, a request is generally required to be sent to a security token service, identity information is acquired through the security token service, then the request and the identity information are sent to a gateway, and after verification is passed, the gateway forwards the request to a corresponding service interface. However, in the prior art, more nodes are involved, and the processing flow is complicated, so that the efficiency of a client request is low, and the user experience is affected. Based on the above, the embodiments of the present application provide a method, a system, a server, and a computer readable storage medium for data sharing, which can shorten the processing flow during data sharing based on realizing secure data access, and improve the response efficiency, thereby improving the user experience.
For the sake of understanding the scheme, first, an implementation system (hereinafter referred to as a data sharing system) of the method for implementing data sharing of this embodiment will be described, and reference is made to a block diagram of a data sharing system shown in fig. 1, where the data sharing system includes a server, and a data asset issuing side, a data asset requesting side, and a gateway, which are communicatively connected to the server, respectively. In this embodiment, the data asset request end is a user end, for example, may include a terminal device such as a smart phone, a PC computer, or a notebook computer, and the data asset issue end is an administrator end, where the administrator end may also include a terminal device such as a smart phone, a PC computer, or a notebook computer.
For convenience of description, the method of sharing data in this embodiment is described with a server as an execution body, and referring to fig. 2, the method includes the following steps:
step S210, in response to the application filling operation initiated by the data asset request terminal, the data asset request terminal performs sharing qualification check.
In one embodiment, the application filling operation initiated by the data asset request end may be an operation triggered when the user applies for the data asset to be acquired through the data sharing page (may also be referred to as a sharing portal page), and the application filling operation is used for filling basic information of the application, such as the data asset to be acquired, the validity period of use, the request number (such as the number of requests per day, the number of requests per week or the total number of requests, etc.), and user identity information (such as a user name and password information) of the data asset request end itself.
In one embodiment, after the data asset request is filled with the above information, the process flow shown in fig. 3 may be referred to as follows: firstly, an administrator checks the information filled in by the data asset request terminal through the data asset release terminal, examines and approves the application of the data asset request terminal, sends the application to the server, carries out sharing qualification check on the data asset request terminal through the server, if the server passes the sharing qualification check, the data asset request terminal can be added to a sharing white list of a gateway, and the sharing qualification check passing result is sent to the data asset request terminal (namely, a user); if the server fails the shared qualification check, the result of the failed shared qualification check may be sent to the user.
Step S220, if the shared qualification check of the data asset request terminal passes, the pre-configured interface routing information is sent to the data asset request terminal through the data asset issuing terminal.
The server sends the preconfigured interface routing information corresponding to the data asset issuing end, and if the shared qualification of the data asset requesting end passes, the data asset issuing end sends the interface routing information corresponding to the requested data asset to the data asset requesting end.
Step S230, after the gateway receives the data asset acquisition request initiated by the data asset request end, verifying the access right of the data asset request end, if the verification is passed, transmitting the shared data to the data asset request end in response to the data asset acquisition request forwarded by the gateway; wherein the data asset acquisition request is initiated after receiving the interface routing information for the data asset request.
To ensure that the interface routing information corresponding to the requested data asset may be sent to the data asset requesting end, in an alternative embodiment, before the filling operation is applied in response to the request initiated by the data asset requesting end, the method further comprises:
receiving a data asset to be shared uploaded from a data asset publishing terminal;
and sending a route creation request to the gateway so that the gateway creates interface route information corresponding to the data asset to be shared.
In particular implementations, referring to FIG. 4, an administrator (i.e., a data asset publishing side) selects a data asset to publish (i.e., a data asset to be shared) via an access server and presents the data asset to a sharing portal for data sharing. When publishing, an administrator fills in basic information of the data asset to be shared, such as the name, the content profile and the like of the data asset, at the data asset publishing end, and the data asset is displayed on a display page of the sharing portal after the publishing is successful. While the data asset is being published, the server requests the gateway to create an interface routing information specific to the data asset for subsequent retrieval of the published data asset, and the user invokes the data asset via the interface routing information.
Further, after the server sends the preconfigured interface routing information to the data asset request terminal through the data asset publishing terminal, the data asset request terminal may be further added to the shared whitelist in the gateway through the data asset publishing terminal. When the data asset request end is in the shared white list, the data asset request end can be characterized to acquire, use and the like the corresponding data asset in the shared portal.
The application filling operation initiated by the data asset request terminal is used for filling application basic information, and the application basic information at least comprises the data asset use validity period and the request times. After the user of the data asset request terminal fills out the data asset use validity period and the request times, if the data asset issuing terminal passes the sharing qualification check, the data asset use validity period and the request times are characterized as being agreed.
In addition, the server also has access rights to modify the data asset requesting end, such as by operation of the data asset publishing end, the date asset usage expiration date and number of requests filled in by the data asset requesting end. In one embodiment, the server may modify the application base information of the data asset requesting end by responding to a modification operation of the application base information filled by the data asset issuing end for the data asset requesting end. For example, the data asset usage validity period filled by the data asset requesting end is long, the number of requests is the maximum number of times that can be filled, but in the subsequent usage process, the data asset usage validity period and the number of requests of the data asset requesting end need to be reduced, so that the data asset usage validity period and the number of requests can be modified by operating on the data asset issuing end, and the server responds to the modification operation and synchronizes the modification result to the data asset requesting end.
Optionally, when the data asset request end applies for acquiring the data asset, the information corresponding to the filling operation may further include basic information of the user, such as a user name and a user password, so that the server sends the preconfigured interface routing information to the data asset request end through the data asset release end, and returns the user name and the user password to the data asset request end together, and the data asset request end initiates a data asset acquisition request to the gateway after receiving the interface routing information and the basic information of the user.
The specific flow of the data asset request end initiating the data asset acquisition request to the gateway after receiving the interface routing information and the basic information of the user may be shown in fig. 5, where the data asset request end initiates the data asset acquisition request to the gateway with the request parameters (interface routing information, name of the data asset to be acquired, representation of the data asset to be acquired, etc.) and own user name and password, and the gateway performs access rights verification on the data asset request end, such as verifying the name of the data asset and the interface routing information, and verifying whether the data asset request end is in a shared whitelist or not. If the access rights are verified, a request (the request is a data asset acquisition request) is sent to the server through the gateway, and the server sends a request result (namely, the corresponding data asset) to the data asset request end through responding to the data asset acquisition request.
The embodiment can configure the authority of the data asset request terminal, thereby flexibly adjusting the object capable of carrying out data sharing, and an administrator can remove the user from the white list at any time or automatically remove the user from the white list after the data asset applied by the user expires in order to ensure the data security. Thus, in one example, the server may remove the data asset requesting end from the shared whitelist in the gateway by responding to a user removal operation of the data asset issuing end. In another example, the data asset request is removed from the shared whitelist after expiration of the usage validity period and/or the number of requests in the application base information.
In order to facilitate understanding of the embodiments of the present application, a method for data sharing is further provided, where the method for data sharing may include four flows including data asset publishing, data asset application, data asset auditing, and data asset usage, and specifically includes the following schemes:
1. data asset publication. The data sharing issuing end determines to select the data asset to be issued to fill in the basic information by responding to the operation of an administrator, issues the data asset through the server, the asset is displayed on the sharing portal after the data asset is successfully issued, and meanwhile the server can request the gateway to create an interface routing information specific to the asset.
2. Data asset application. The data sharing request terminal determines the data assets which the user applies for and obtains on the sharing portal page by responding to the operation of the user, and determines the data assets which the user wants to apply for by responding to the basic information (comprising the validity period of use and the request times (which can be in units of days, weeks, months and the like)) of the user filling in the application.
3. Data asset auditing. The data sharing issuing end checks, audits and modifies the application of the user by responding to the operation of the administrator. For example, the usage validity period filled by the user may be modified, and the number of requests per day may be modified. After the user applies, the interface route information and the user name password corresponding to the user request are returned to the user, and the user is added into the white list of the gateway.
4. Data asset usage. After the user obtains the interface routing information and the user name password, the gateway initiates a data asset obtaining request, verifies whether the user has access rights, if so, the gateway forwards the data asset obtaining request to a server, and the data asset requested by the server is sent to a data asset request end (namely, the user); if the user has no access rights, the user returns directly that no rights. To ensure data security, the data asset issuing side may respond to an administrator operation so that the user may be removed from the whitelist at any time, or automatically after the data asset applied by the user expires.
Compared with the prior art that the gateway authentication is requested after the token service is requested, the method is higher in efficiency, more convenient to use and better in effect in a scene of needing high-speed sharing of data. Compared with the mode of directly requesting gateway authentication and then forwarding the request, the method is more flexible, the permission of enabling the forbidden user to request data can be modified at any time, the permission of requesting the account can be configured through the gateway, the permission configuration in the gateway can be controlled in real time through the server, meanwhile, the validity period of the user to acquire the data can be configured, and 3, the user-related permission configuration is automatically regulated according to the condition of the validity period and the limitation of the request times, so that the safety and convenience of data sharing are improved.
For the above method embodiment, the embodiment of the present application further provides a data sharing system, where the data sharing system includes a server, and further includes a data asset publishing end, a data asset requesting end and a gateway, which are respectively connected with the server in a communication manner, where the data asset requesting end is connected with the gateway in a communication manner, and a communication connection relationship between devices is as shown in fig. 1, where:
the server is used for responding to the application filling operation initiated by the data asset request terminal and carrying out sharing qualification check on the data asset request terminal; the data asset issuing end is used for sending the pre-configured interface routing information to the data asset requesting end through the data asset issuing end if the sharing qualification check of the data asset requesting end is passed; the gateway is used for verifying the access authority of the data asset request terminal after receiving the data asset acquisition request initiated by the data asset request terminal, and forwarding the data asset acquisition request to the server if the access authority passes the verification; the server is also used for responding to the data asset acquisition request forwarded by the gateway and sending the shared data to the data asset request end; wherein the data asset acquisition request is initiated after receiving the interface routing information for the data asset request.
In some embodiments, the server is further configured to, prior to application completion operations initiated in response to the data asset request,:
receiving a data asset to be shared uploaded from a data asset publishing terminal;
and sending a route creation request to the gateway so that the gateway creates interface route information corresponding to the data asset to be shared.
In some embodiments, the data asset issuing side is further configured to, after sending the preconfigured interface routing information to the data asset requesting side:
the data asset request is added to the shared white list in the gateway.
In some embodiments, the server is further configured to:
and responding to the user removing operation of the data asset issuing end, and removing the data asset requesting end from the shared white list in the gateway.
In some embodiments, the application filling operation initiated by the data asset request end is used for filling application basic information, where the application basic information at least includes a data asset usage validity period and a request number.
In some embodiments, the server is further configured to:
and modifying the application basic information of the data asset request terminal in response to the modification operation of the data asset release terminal on the application basic information filled in by the data asset request terminal.
In some embodiments, the server is further configured to:
and after the expiration of the use validity period and/or the request times in the application basic information, removing the data asset request end from the shared white list.
The implementation principle and the technical effects of the data sharing system provided in the embodiment of the present application are the same as those of the foregoing method embodiment, and for brevity, reference may be made to corresponding contents in the foregoing method embodiment of data sharing where an embodiment portion of the data sharing system is not mentioned.
The embodiment of the present application further provides a server, as shown in fig. 6, which is a schematic structural diagram of the server, where the server 100 includes a processor 61 and a memory 60, where the memory 60 stores computer executable instructions that can be executed by the processor 61, and the processor 61 executes the computer executable instructions to implement a method of sharing any item of data.
In the embodiment shown in fig. 6, the server further comprises a bus 62 and a communication interface 63, wherein the processor 61, the communication interface 63 and the memory 60 are connected by the bus 62.
The memory 60 may include a high-speed random access memory (RAM, random Access Memory), and may further include a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. The communication connection between the system network element and at least one other network element is achieved via at least one communication interface 63 (which may be wired or wireless), and may use the internet, a wide area network, a local network, a metropolitan area network, etc. Bus 62 may be an ISA (Industry Standard Architecture ) bus, a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The bus 62 may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, only one bi-directional arrow is shown in FIG. 6, but not only one bus or type of bus.
The processor 61 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in the processor 61 or by instructions in the form of software. The processor 61 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor 61 reads information in the memory and, in combination with its hardware, performs the steps of the method for data sharing of the previous embodiment.
The embodiment of the application further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, where the computer executable instructions, when invoked and executed by a processor, cause the processor to implement the method for sharing data, and the specific implementation may refer to the foregoing method embodiment and will not be repeated herein.
The computer program product of the data sharing method, system, server and computer readable storage medium provided in the embodiments of the present application includes a computer readable storage medium storing program code, where the instructions included in the program code may be used to execute the method described in the foregoing method embodiment, and specific implementation may refer to the method embodiment and will not be described herein.
The relative steps, numerical expressions and numerical values of the components and steps set forth in these embodiments do not limit the scope of the present application unless specifically stated otherwise.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In the description of the present application, it should be noted that, unless explicitly specified and limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the terms in this application will be understood by those of ordinary skill in the art in a specific context.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A method for sharing data, which is characterized by being applied to a server; the server is respectively in communication connection with a data asset issuing end, a data asset requesting end and a gateway, and the data asset requesting end is in communication connection with the gateway; the method comprises the following steps:
responding to an application filling operation initiated by the data asset request terminal, and carrying out sharing qualification verification on the data asset request terminal;
if the shared qualification of the data asset request end passes, sending pre-configured interface routing information to the data asset request end through a data asset release end;
after the gateway receives a data asset acquisition request initiated by a data asset request end, verifying the access authority of the data asset request end, and if the access authority passes the verification, transmitting shared data to the data asset request end in response to the data asset acquisition request forwarded by the gateway; wherein the data asset acquisition request is initiated after the data asset request receives the interface routing information.
2. The method of data sharing of claim 1, wherein prior to filling in the operation in response to an application initiated by the data asset requesting end, the method further comprises:
receiving the data asset to be shared uploaded from the data asset publishing terminal;
and sending the route creation request to the gateway so that the gateway creates interface route information corresponding to the data asset to be shared.
3. The method of data sharing according to claim 1, wherein after sending the pre-configured interface routing information to the data asset requesting end, the method further comprises:
and adding the data asset request end to a shared white list in the gateway through the data asset issuing end.
4. A method of data sharing according to claim 3, wherein the method further comprises:
and responding to the user removing operation of the data asset issuing end, and removing the data asset requesting end from the shared white list in the gateway.
5. The method according to claim 4, wherein the application filling operation initiated by the data asset request terminal is used for filling application basic information, and the application basic information at least comprises a data asset use validity period and a request number.
6. The method of data sharing according to claim 5, further comprising:
and responding to the modification operation of the data asset issuing end for the application basic information filled in by the data asset requesting end, and modifying the application basic information of the data asset requesting end.
7. The method of data sharing according to claim 5 or 6, further comprising:
and removing the data asset request end from the shared white list after the expiration of the use validity period and/or the request times in the application basic information.
8. The data sharing system is characterized by comprising a server, a data asset issuing end, a data asset requesting end and a gateway, wherein the data asset issuing end, the data asset requesting end and the gateway are respectively in communication connection with the server;
the server is used for responding to the application filling operation initiated by the data asset request terminal and carrying out sharing qualification check on the data asset request terminal;
the data asset issuing end is used for sending the pre-configured interface routing information to the data asset requesting end through the data asset issuing end if the sharing qualification check of the data asset requesting end is passed;
the gateway is used for verifying the access authority of the data asset request terminal after receiving the data asset acquisition request initiated by the data asset request terminal, and forwarding the data asset acquisition request to the server if the access authority passes the verification;
the server is further used for responding to the data asset acquisition request forwarded by the gateway and sending shared data to the data asset request end; wherein the data asset acquisition request is initiated after the data asset request receives the interface routing information.
9. A server comprising a processor and a memory, the memory storing computer executable instructions executable by the processor, the processor executing the computer executable instructions to implement the method of data sharing of any one of claims 1 to 7.
10. A computer readable storage medium storing computer executable instructions which, when invoked and executed by a processor, cause the processor to implement the method of data sharing of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210398944.3A CN114760359B (en) | 2022-04-12 | 2022-04-12 | Method, system, server and computer readable storage medium for data sharing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210398944.3A CN114760359B (en) | 2022-04-12 | 2022-04-12 | Method, system, server and computer readable storage medium for data sharing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114760359A CN114760359A (en) | 2022-07-15 |
| CN114760359B true CN114760359B (en) | 2023-08-01 |
Family
ID=82330371
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210398944.3A Active CN114760359B (en) | 2022-04-12 | 2022-04-12 | Method, system, server and computer readable storage medium for data sharing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114760359B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019019493A1 (en) * | 2017-07-28 | 2019-01-31 | 平安科技（深圳）有限公司 | Data sharing method and device, and computer readable storage medium |
| WO2021057150A1 (en) * | 2019-09-29 | 2021-04-01 | 南京中兴软件有限责任公司 | Port sharing method and apparatus, storage medium and electronic apparatus |
| CN113986132A (en) * | 2021-10-27 | 2022-01-28 | 北京八分量信息科技有限公司 | Method, device and related product for sharing storage resources in heterogeneous network |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100223466A1 (en) * | 2009-02-27 | 2010-09-02 | Third Iris Corp | Shared scalable server to control confidental event traffic among recordation terminals, analysis engines, and a storage farm coupled via a public network |
| US20130067303A1 (en) * | 2011-09-09 | 2013-03-14 | Microsoft Corporation | Distinct Links for Publish Targets |
| US10623406B2 (en) * | 2016-07-22 | 2020-04-14 | Box, Inc. | Access authentication for cloud-based shared content |
| US11263621B2 (en) * | 2018-12-27 | 2022-03-01 | Paypal, Inc. | Parent level token issuance for asynchronous data processing based on device trust levels |
| EP4173232A1 (en) * | 2020-06-29 | 2023-05-03 | Illumina, Inc. | Temporary cloud provider credentials via secure discovery framework |
| AU2021299262A1 (en) * | 2020-06-29 | 2023-01-05 | Illumina, Inc. | Policy-based genomic data sharing for software-as-a-service tenants |
-
2022
- 2022-04-12 CN CN202210398944.3A patent/CN114760359B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019019493A1 (en) * | 2017-07-28 | 2019-01-31 | 平安科技（深圳）有限公司 | Data sharing method and device, and computer readable storage medium |
| WO2021057150A1 (en) * | 2019-09-29 | 2021-04-01 | 南京中兴软件有限责任公司 | Port sharing method and apparatus, storage medium and electronic apparatus |
| CN113986132A (en) * | 2021-10-27 | 2022-01-28 | 北京八分量信息科技有限公司 | Method, device and related product for sharing storage resources in heterogeneous network |
Non-Patent Citations (3)
| Title |
|---|
| Seong-pyo Hong ; Joon Lee."Supporting Secure Authentication and Privacy in Wireless Computing".《2006 International Conference on Hybrid Information Technology》.2011,全文. * |
| 基于Web Service的在线监测系统数据交互研究与实践;吴志鹏;杨苹;姜新宇;崔勇;WU Hui;;电工技术(08);全文 * |
| 基于域分布式文件共享实现方案探讨;车艳艳;;广西电力(05);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114760359A (en) | 2022-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109995755B (en) | Login state control method and device based on applet framework | |
| CN111213339B (en) | Authentication token with client key | |
| US20130247144A1 (en) | Controlling Access to Resources on a Network | |
| CN110784450A (en) | Single sign-on method and device based on browser | |
| CN110764807B (en) | Upgrading method, system, server and terminal equipment | |
| CN109462601B (en) | Multi-platform access method and device based on eSIM | |
| US20160241536A1 (en) | System and methods for user authentication across multiple domains | |
| CN111914194B (en) | Business system changing method and device, electronic equipment and storage medium | |
| CN113726774B (en) | Client login authentication method, system and computer equipment | |
| CN109286620B (en) | User right management method, system, device and computer readable storage medium | |
| CN111431920A (en) | Security control method and system based on dynamic token | |
| CN111064708A (en) | Authorization authentication configuration method, authorization authentication device and electronic equipment | |
| CN111193707A (en) | Pre-verification access method and device based on enterprise browser | |
| CN114760359B (en) | Method, system, server and computer readable storage medium for data sharing | |
| CN113259910A (en) | Activation method and device for vehicle-mounted networking equipment | |
| CN111314355B (en) | Authentication method, device, equipment and medium of VPN (virtual private network) server | |
| CN112187704B (en) | Method, system and network equipment for checking valid time of license | |
| CN110943827B (en) | Data acquisition method and device based on network protocol | |
| CN111355583B (en) | Service providing system, method, device, electronic equipment and storage medium | |
| CN111211902A (en) | Digital signature method and device based on enterprise browser | |
| CN111191202B (en) | Single sign-on method, device and system for mobile application | |
| CN112311716B (en) | Data access control method, device and server based on openstack | |
| CN113395249A (en) | Client login authentication method, system and computer equipment | |
| CN113746932A (en) | Network request merging method and device, electronic device and computer program product | |
| CN112699366A (en) | Cross-platform login-free secure communication method and device and electronic equipment |
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 |