CN111130789B - Data interaction method and device and data control center - Google Patents
Data interaction method and device and data control center Download PDFInfo
- Publication number
- CN111130789B CN111130789B CN201811284471.4A CN201811284471A CN111130789B CN 111130789 B CN111130789 B CN 111130789B CN 201811284471 A CN201811284471 A CN 201811284471A CN 111130789 B CN111130789 B CN 111130789B
- Authority
- CN
- China
- Prior art keywords
- data
- token
- consumer
- producer
- request
- 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
Images
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/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
- H04L9/3213—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority using tickets or tokens, e.g. Kerberos
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Telephonic Communication Services (AREA)
- Storage Device Security (AREA)
Abstract
The invention is suitable for the technical field of communication, and provides a data interaction method and device and a data control center, wherein the interaction method comprises the following steps: receiving a data request of a data consumer, wherein the data request carries a corresponding token; obtaining corresponding data based on the token, wherein the data corresponds to a unique token; and feeding the data back to the data consumer. In the invention, data interaction is carried out by taking the token as a carrier, so that the complexity of data transmission is reduced and the transmission efficiency is improved.
Description
Technical Field
The invention belongs to the technical field of communication, and particularly relates to a data interaction method and device and a data control center.
Background
With the development of information technology, data interaction becomes wide, for example, data interaction between a system and data interaction between a server and a client become a normal state, and cross-system interaction usually requires a large number of service parameters to be transmitted. For example, the parameter passing between background services, usually needs to strongly depend on the parameter type definition, which is contrary to the low coupling principle between systems. Parameter passing between foreground systems typically relies on URLs, which limits the length of the parameters and the user can tamper with the URL parameter content at will. If the URL contains sensitive information, there is also a significant security risk. Parameters between systems are stateless and prone to idempotent problems under retry mechanisms.
Disclosure of Invention
The embodiment of the invention provides a data interaction method and device and a data control center, and aims to solve the problem that data transmission efficiency is influenced by the dependence on parameter types during data interaction in the prior art.
A data interaction method comprises the following steps:
receiving a data request of a data consumer, wherein the data request carries a corresponding token;
obtaining corresponding data based on the token, wherein the data corresponds to a unique token;
and feeding the data back to the data consumer.
Preferably, after receiving the data request of the data consumer and before acquiring the corresponding data based on the token, the method further comprises:
and checking whether the token is invalid, and turning to a data acquisition step when the token is not invalid.
Preferably, obtaining corresponding data based on the token comprises:
querying a state of corresponding data based on the token;
when the corresponding data is in an effective state, acquiring the corresponding data;
and decrypting the acquired data based on the token to obtain decrypted data.
Preferably, after feeding back the data to the data consumer, the method further comprises:
receiving a data destruction request of the data consumer, wherein the data destruction request carries the token;
destroying data corresponding to the token based on the data destruction request.
Preferably, after feeding back the data to the data consumer, the method further comprises:
receiving a data destruction instruction of the data producer, wherein the data destruction instruction carries the token;
destroying data corresponding to the token based on the data destruction indication.
Preferably, before receiving the data request of the data consumer, the method further comprises:
receiving a data generation request of a data producer;
authenticating with the data producer;
when the authentication is passed, receiving and storing the data transmitted by the data producer;
and returning the corresponding token to the data producer.
Preferably, the receiving and storing the data transmitted by the data producer comprises:
receiving data transmitted by the data producer;
and carrying out encrypted storage on the received data.
The invention also provides a data interaction device, which comprises:
the receiving unit is used for receiving a data request of a data consumer, wherein the data request carries a corresponding token;
the acquisition unit is used for acquiring corresponding data based on the token, and the data corresponds to a unique token;
and the feedback unit is used for feeding back the data to the data consumer.
The invention also provides a data control center, which comprises a data interaction device, wherein the interaction device comprises:
the receiving unit is used for receiving a data request of a data consumer, wherein the data request carries a corresponding token;
the acquisition unit is used for acquiring corresponding data based on the token, wherein the data corresponds to a unique token;
and the feedback unit is used for feeding back the data to the data consumer.
The invention also provides a memory storing a computer program executed by a processor to perform the steps of:
receiving a data request of a data consumer, wherein the data request carries a corresponding token;
obtaining corresponding data based on the token, wherein the data corresponds to a unique token;
and feeding the data back to the data consumer.
The invention also provides a service terminal, which comprises a memory, a processor and a computer program which is stored in the memory and can run on the processor, wherein the processor executes the computer program to realize the following steps:
receiving a data request of a data consumer, wherein the data request carries a corresponding token;
obtaining corresponding data based on the token, wherein the data corresponds to a unique token;
and feeding the data back to the data consumer.
In the embodiment of the invention, the unique token is set for each data, the data is acquired based on the token, and the token is used as a carrier, so that the convenience of data interaction and the transmission efficiency can be improved.
Drawings
Fig. 1 is a flowchart of a data interaction method according to a first embodiment of the present invention;
FIG. 2 is a flow chart of a preferred mode of the data interaction method according to the first embodiment of the present invention;
FIG. 3 is a flow chart of another preferred mode of the data interaction method provided by the first embodiment of the present invention;
FIG. 4 is a flow chart of another preferred mode of the data interaction method provided by the first embodiment of the present invention;
FIG. 5 is a block diagram of a data interaction device according to a second embodiment of the present invention;
fig. 6 is a structural diagram of a service terminal according to a third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In an embodiment of the present invention, a data interaction method includes: receiving a data request of a data consumer, wherein the data request carries a corresponding token; obtaining corresponding data based on the token, wherein the data corresponds to a unique token; and feeding the data back to the data consumer.
In order to illustrate the technical means of the present invention, the following description is given by way of specific examples.
The first embodiment is as follows:
fig. 1 shows a flowchart of an interaction method for data provided by a first embodiment of the present invention, where the interaction method includes:
step S1, receiving a data request of a data consumer;
specifically, when a data consumer needs to consume data, for example, needs to use GPS navigation data, a data request needs to be initiated first, and the request carries a corresponding token. The data consumer communicates with the data producer in advance to obtain the authority, the authority is that the data producer distributes a corresponding token to the data consumer, the token is the only token of the data required to be used, after the data consumer pays the data producer, the data producer distributes the token to the data consumer, and the data consumer acquires the data based on the token without directly acquiring the data from the data producer, so that the simple token can be used as a carrier for interaction, the complexity of data transmission is reduced, and the transmission efficiency is improved.
Step S2, acquiring corresponding data based on the token;
specifically, corresponding data is obtained from a database based on the token;
step S3, feeding back data to the data consumer;
specifically, after the corresponding data are obtained, the data are transmitted to the data consumer, so that the data consumer can conveniently consume the data.
Preferably, the data is fed back to the data consumer in JSON format.
In the embodiment, data interaction is performed by using the token as a carrier, so that the complexity of data transmission is reduced, and the transmission efficiency is improved.
In a preferable embodiment of this embodiment, after step S1 and before step S2, the method further includes:
step S4, checking whether the token is invalid;
specifically, when a data request is received, it is first checked whether the token carried by the request is invalid, and since each token is time-efficient, that is, each token has a lifetime, when the lifetime is over, it is determined that the token is invalid. When the verification is not failed, go to step S2, otherwise the process is stopped.
In a preferred embodiment of this embodiment (see fig. 2), the step S3 may further include:
step S5, receiving a data destruction request of a data consumer;
specifically, after the data consumer consumes the data, a data destruction request can be initiated, and the data destruction request also carries a corresponding and unique token;
step S6, destroying the data corresponding to the token based on the data destroying request;
specifically, after the data destruction request is received, the data corresponding to the token is found and destroyed.
In a further preferred embodiment of this embodiment, before data destruction is performed, a data state corresponding to the token needs to be queried, whether the data has been destroyed is checked, if the data has been destroyed, destruction does not need to be performed, and if the data has not been destroyed, destruction can be performed.
In another preferred embodiment of this embodiment (see fig. 3), after step S3, the method may further include:
step S7, receiving a data destruction instruction of a data producer;
specifically, if a data producer destroys previously produced data according to a requirement, a data destruction instruction is sent out, and the instruction carries a unique token corresponding to the data to be destroyed;
step S8, destroying the data corresponding to the token based on the data destruction instruction;
specifically, after the data destruction instruction is received, the data corresponding to the token is found and destroyed.
In a further preferred embodiment of this embodiment, before data destruction is performed, a data state corresponding to the token needs to be queried, whether the data has been destroyed is checked, if the data has been destroyed, destruction does not need to be performed, and if the data has not been destroyed, destruction can be performed.
In a preferable embodiment of this embodiment, the step S1 may further include (see fig. 4):
step S9, receiving a data generation request of a data producer;
specifically, when a data producer needs to produce data, a data production request needs to be initiated, wherein the production request carries account information of the data producer;
step S10, authenticating with the data producer;
specifically, firstly, authenticating a data producer, authenticating a user based on account information of the data producer, identifying whether the data producer has authority, and going to step S11 when the data producer passes the authority, otherwise, stopping the process;
step S11, receiving and storing data transmitted by a data producer;
specifically, when authentication is passed, data produced by a data producer is received and stored, and preferably, the produced data can be received by using one of three access modes, namely dubbo, client jar and restful;
further, the data incoming from the production data side is received first, and then the received data is encrypted and stored, preferably, the data is encrypted and stored by using the AES128 encryption method.
Step S12, returning the corresponding token to the data producer;
specifically, when the received production data is encrypted and stored, a corresponding and unique token is generated and then fed back to the data producer, so that the data consumer authorized by the data producer can distribute the token for data consumption. Because the data is stored in the AES128 encryption mode, even if the data is leaked in the storage process, the real data cannot be exposed, and the data security is improved.
It should be noted that, after the data generated is input, the data generating side may set the validity period of the data, for example, a week, etc., and the data receiving side (for example, the data interaction center) may also set the validity period of the data. Preferably, an expiry date is set by the data producer, the expiry date of the token corresponding to the expiry date of the data.
In a preferable solution of this embodiment, the step S2 specifically includes:
querying a state of corresponding data based on the token;
specifically, when a data consumption request of a data consumer is received, the state of corresponding data is queried based on a corresponding token to judge whether the corresponding data is in a valid state, and if the corresponding data is invalid or destroyed, the process is stopped; when the effective, go to the next step;
acquiring corresponding data;
specifically, when the corresponding data is valid, the corresponding data is directly acquired, and the data is encrypted in an AES128 encryption mode when being stored.
Decrypting the acquired data based on the token to obtain decrypted data;
specifically, the obtained data is decrypted based on the token to obtain decrypted data, and then format conversion is performed to convert the decrypted data into a JSON format to be transmitted to the data consumer.
In the embodiment, data interaction is performed by taking the token as a carrier, so that the complexity of data transmission is reduced, and the transmission efficiency is improved.
Secondly, the data is encrypted and stored, so that the safety of the data can be improved.
The second embodiment:
based on the first embodiment, as shown in fig. 5, a structure diagram of a data interaction device provided for the second embodiment of the present invention is shown, where the data interaction device includes: receiving unit 1, acquisition unit 2 connected with receiving unit 1, feedback unit 3 connected with acquisition unit 2, wherein:
a receiving unit 1 for receiving a data request of a data consumer;
specifically, when a data consumer needs to consume data, for example, needs to use GPS navigation data, a data request needs to be initiated first, and the request carries a corresponding token. The data consumer communicates with the data producer in advance to obtain the authority, the authority is that the data producer distributes a corresponding token to the data consumer, the token is the only token of the data required to be used, after the data consumer pays the data producer, the data producer distributes the token to the data consumer, and the data consumer acquires the data based on the token without directly acquiring the data from the data producer, so that the simple token can be used as a carrier for interaction, the complexity of data transmission is reduced, and the transmission efficiency is improved.
An obtaining unit 2, configured to obtain corresponding data based on the token;
specifically, corresponding data is obtained from a database based on the token;
a feedback unit 3 for feeding back data to the data consumer;
specifically, after the corresponding data is acquired, the data is transmitted to the data consumer, so that the data consumer can conveniently consume the data.
Preferably, the data is fed back to the data consumer in JSON format.
In the embodiment, data interaction is performed by taking the token as a carrier, so that the complexity of data transmission is reduced, and the transmission efficiency is improved.
In a preferred aspect of this embodiment, the interaction device may include: a verification unit 4 connected to both the receiving unit 1 and the obtaining unit 2, wherein:
a checking unit 4 for checking whether the token is invalid;
specifically, when a data request is received, it is first checked whether the token carried by the request is invalid, and since each token is time-efficient, that is, each token has a lifetime, when the lifetime is over, it is determined that the token is invalid. And when the verification is not invalid, feeding back to the acquisition unit 2, otherwise, stopping the process.
In a preferable solution of this embodiment, the receiving unit 1 is further configured to:
receiving a data destruction request of a data consumer;
specifically, after the data consumer consumes the data, a data destruction request can be initiated, and the data destruction request also carries a corresponding and unique token;
the interaction device may further include: a destruction unit 5 connected with the receiving unit 1, wherein:
a destruction unit 5 configured to destroy the data corresponding to the token based on the data destruction request;
specifically, after the data destruction request is received, the data corresponding to the token is found and destroyed.
In a further preferred embodiment of this embodiment, before data destruction is performed, a data state corresponding to the token needs to be queried, whether the data has been destroyed is checked, if the data has been destroyed, destruction does not need to be performed, and if the data has not been destroyed, destruction can be performed.
In another preferred aspect of this embodiment, the receiving unit 1 is further configured to:
receiving a data destruction indication of a data producer;
specifically, if a data producer destroys previously produced data according to a requirement, a data destruction instruction is sent out, and the instruction carries a unique token corresponding to the data to be destroyed;
the destruction unit 5 is also adapted to: destroying data corresponding to the token based on the data destruction indication;
specifically, after the data destruction instruction is received, the data corresponding to the token is found and destroyed.
In a further preferred embodiment of this embodiment, before data destruction is performed, a data state corresponding to the token needs to be queried, whether the data has been destroyed is checked, if the data has been destroyed, destruction does not need to be performed, and if the data has not been destroyed, destruction can be performed.
In a preferable aspect of this embodiment, the transmission device further includes: a producer data processing unit, wherein:
the producer data processing unit is used for receiving a data generation request of a data producer;
specifically, when a data producer needs to produce data, a data production request needs to be initiated, wherein the production request carries account information of the data producer;
and is further configured to: receiving and storing data transmitted by a data producer;
specifically, when authentication is passed, data produced by a data producer is received and stored, and preferably, the produced data can be received by using one of three access modes, namely dubbo, client jar and restful;
further, the data transmitted by the production data side is received first, and then the received data is encrypted and stored, preferably, the data is encrypted and stored by using an AES128 encryption method.
Returning the corresponding token to the data producer;
specifically, when the received production data is encrypted and stored, a corresponding and unique token is generated and then fed back to the data producer, so that the data consumer authorized by the data producer can distribute the token for data consumption. Because the data is stored in the AES128 encryption mode, even if the data is leaked in the storage process, the real data cannot be exposed, and the data security is improved.
After the data is input, the data producer may set the validity period of the data, for example, a week, and the data receiver (for example, a data interaction center) may set the validity period of the data. Preferably, an expiry date is set by the data producer, the expiry date of the token corresponding to the expiry date of the data.
In a preferred embodiment of this embodiment, the obtaining unit 2 specifically includes: inquiry subunit, the acquisition subunit and the decryption subunit that are connected with the inquiry subunit, wherein:
a query subunit, configured to query a state of corresponding data based on the token;
specifically, when a data consumption request of a data consumer is received, the state of corresponding data is queried based on a corresponding token to judge whether the corresponding data is in a valid state, and if the corresponding data is invalid or destroyed, the process is stopped; when the data is valid, feeding back to the obtaining subunit;
the acquisition subunit is used for acquiring corresponding data;
specifically, when the corresponding data is valid, the corresponding data is directly acquired, and the data is encrypted in an AES128 encryption mode when being stored.
The decryption subunit is used for decrypting the acquired data based on the token to obtain decrypted data;
specifically, the obtained data is decrypted based on the token to obtain decrypted data, and then format conversion is carried out to convert the decrypted data into a JSON format to be transmitted to the data consumer.
In the embodiment, data interaction is performed by taking the token as a carrier, so that the complexity of data transmission is reduced, and the transmission efficiency is improved.
And secondly, the data is encrypted and stored, so that the safety of the data can be improved.
The invention further provides a data control center, which includes the data interaction device described in the above second embodiment, and the specific structure, the working principle, and the technical effects of the interaction transmission device are consistent with the description of the above second embodiment, and are not described herein again.
Example three:
fig. 6 is a block diagram illustrating a service terminal according to a third embodiment of the present invention, where the service terminal includes: a memory (memory)61, a processor (processor)62, a communication Interface (communication Interface)63 and a bus 64, wherein the processor 62, the memory 61 and the communication Interface 63 complete mutual communication through the bus 64.
A memory 61 for storing various data;
specifically, the memory 61 is used for storing various data, such as data in communication, received data, and the like, and is not limited herein, and the memory further includes a plurality of computer programs.
A communication interface 63 for information transmission between communication devices of the service terminal;
the processor 62 is used for calling various computer programs in the memory 61 to execute the data interaction method provided by the first embodiment, for example:
receiving a data request of a data consumer, wherein the data request carries a corresponding token;
obtaining corresponding data based on the token, wherein the data corresponds to a unique token;
and feeding the data back to the data consumer.
In this embodiment, data interaction is performed by using the token as a carrier, so that complexity of data transmission is reduced, and transmission efficiency is improved.
The invention also provides a memory, wherein the memory stores a plurality of computer programs, and the computer programs are called by the processor to execute the data interaction method in the first embodiment.
In the invention, data interaction is carried out by taking the token as a carrier, so that the complexity of data transmission is reduced and the transmission efficiency is improved.
And secondly, the data is encrypted and stored, so that the safety of the data can be improved.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation.
Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present invention, and shall cover the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for data interaction, characterized in that,
the method comprises the following steps:
receiving a data request of a data consumer, wherein the data request carries a corresponding token, the data consumer communicates with a data producer in advance to obtain a right, the right is the corresponding token distributed to the data consumer by the data producer, the token is a unique token of data required to be used, after the data consumer pays the data producer, the data producer distributes the token to the data consumer, and the data consumer acquires data based on the token without directly acquiring the data from the data producer;
obtaining corresponding data based on the token, wherein the data corresponds to a unique token;
feeding back the data to the data consumer; and
and receiving a data destruction request of the data consumer, wherein the data destruction request carries the token, and destroying data corresponding to the token based on the data destruction request.
2. The interaction method according to claim 1,
after receiving the data request of the data consumer and before acquiring the corresponding data based on the token, the method further comprises the following steps:
and checking whether the token is invalid, and turning to a data acquisition step when the token is not invalid.
3. The interaction method according to claim 1,
obtaining corresponding data based on the token includes:
querying a state of corresponding data based on the token;
when the corresponding data is in an effective state, acquiring the corresponding data;
and decrypting the acquired data based on the token to obtain decrypted data.
4. The interaction method according to claim 1,
after the data is fed back to the data consumer, the method further comprises the following steps:
receiving a data destruction instruction of the data producer, wherein the data destruction instruction carries the token;
destroying data corresponding to the token based on the data destruction indication.
5. The interaction method according to claim 1,
before receiving a data request of a data consumer, the method further comprises:
receiving a data generation request of a data producer;
authenticating with the data producer;
when the authentication is passed, receiving and storing the data transmitted by the data producer;
and returning the corresponding token to the data producer.
6. The interaction method according to claim 1,
receiving and storing the data incoming from the data producer includes:
receiving data transmitted by the data producer;
and carrying out encrypted storage on the received data.
7. A data interaction device is characterized in that,
the method comprises the following steps:
the receiving unit is used for receiving a data request of a data consumer, wherein the data request carries a corresponding token, the data consumer communicates with a data producer in advance to obtain a right, the right is the corresponding token distributed to the data consumer by the data producer, the token is a unique token of data needing to be used, after the data consumer pays the data producer, the data producer distributes the token to the data consumer, and the data consumer acquires data based on the token without directly acquiring the data from the data producer;
the acquisition unit is used for acquiring corresponding data based on the token, wherein the data corresponds to a unique token;
the feedback unit is used for feeding the data back to the data consumer;
and the destroying unit is used for destroying the data corresponding to the token based on the data destroying request, wherein after the data destroying request is received, the data corresponding to the token is found for destroying.
8. A data control center, characterized in that,
interactive apparatus comprising a data as claimed in claim 7.
9. A memory storing a computer program, characterized in that,
the computer program is executed by a processor for the steps of:
receiving a data request of a data consumer, wherein the data request carries a corresponding token, the data consumer communicates with a data producer in advance to obtain a permission, the permission is the corresponding token distributed to the data consumer by the data producer, the token is a unique token of data required to be used, after the data consumer pays for the data producer, the data producer distributes the token to the data consumer, and the data consumer acquires data based on the token without directly acquiring the data from the data producer;
obtaining corresponding data based on the token, wherein the data corresponds to a unique token;
feeding back the data to the data consumer; and
and receiving a data destruction request of the data consumer, wherein the data destruction request carries the token, and destroying data corresponding to the token based on the data destruction request.
10. A service terminal comprising a memory, a processor and a computer program stored in said memory and executable on said processor,
the processor, when executing the computer program, implements the steps of the method of interacting the data of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811284471.4A CN111130789B (en) | 2018-10-30 | 2018-10-30 | Data interaction method and device and data control center |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811284471.4A CN111130789B (en) | 2018-10-30 | 2018-10-30 | Data interaction method and device and data control center |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111130789A CN111130789A (en) | 2020-05-08 |
| CN111130789B true CN111130789B (en) | 2022-06-24 |
Family
ID=70485273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811284471.4A Active CN111130789B (en) | 2018-10-30 | 2018-10-30 | Data interaction method and device and data control center |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111130789B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104821937A (en) * | 2015-03-26 | 2015-08-05 | 腾讯科技（北京）有限公司 | Token acquisition method, device and system |
| CN106302546A (en) * | 2016-10-18 | 2017-01-04 | 青岛海信电器股份有限公司 | The method and apparatus realizing server access |
-
2018
- 2018-10-30 CN CN201811284471.4A patent/CN111130789B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104821937A (en) * | 2015-03-26 | 2015-08-05 | 腾讯科技（北京）有限公司 | Token acquisition method, device and system |
| CN106302546A (en) * | 2016-10-18 | 2017-01-04 | 青岛海信电器股份有限公司 | The method and apparatus realizing server access |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111130789A (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20120216300A1 (en) | Method and client agent for monitoring the use of protected content | |
| TWI420339B (en) | Software authorization system and method | |
| EP2251810B1 (en) | Authentication information generation system, authentication information generation method, and authentication information generation program utilizing a client device and said method | |
| EP3780484B1 (en) | Cryptographic operation and working key creation method and cryptographic service platform and device | |
| CN111708991A (en) | Service authorization method, service authorization device, computer equipment and storage medium | |
| CN111680305A (en) | Data processing method, device and equipment based on block chain | |
| CN105991563B (en) | Method and device for protecting security of sensitive data and three-party service system | |
| CN106936588B (en) | Hosting method, device and system of hardware control lock | |
| US20120117380A1 (en) | Method for Granting Authorization to Access a Computer-Based Object in an Automation System, Computer Program, and Automation System | |
| CN101526985A (en) | Client system and method of digital rights management and digital rights management system | |
| CN109714171B (en) | Safety protection method, device, equipment and medium | |
| CN111107063B (en) | Login method and device | |
| CN113704210A (en) | Data sharing method and electronic equipment | |
| CN111475823A (en) | Data sharing method, equipment, server and readable storage medium | |
| KR20000024445A (en) | User Authentication Algorithm Using Digital Signature and/or Wireless Digital Signature with a Portable Device | |
| CN112669104A (en) | Data processing method of rental equipment | |
| CN113872940B (en) | Access control method, device and equipment based on NC-Link | |
| CN111130789B (en) | Data interaction method and device and data control center | |
| CN111510421B (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| JP2008176741A (en) | Client terminal, service providing server, service providing system, control method, and service providing method | |
| CN107004071B (en) | Software processing apparatus, server system and method thereof | |
| CN109740321B (en) | Method for revoking manager lock of encryption machine, encryption machine and manufacturer server | |
| CN117375803B (en) | Key derivation interface registration method, calling method, related equipment and storage medium | |
| CN117375804B (en) | Key derivation method, related equipment and storage medium | |
| CN115827785B (en) | Data storage method, device, equipment 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 | ||
| CB02 | Change of applicant information |
Address after: 200438 9 / F, 10 / F, 11 / F, 12 / F, 38 Lane 1688, Guoquan North Road, Yangpu District, Shanghai Applicant after: QIANXUN SPATIAL INTELLIGENCE Inc. Address before: Room j165, 1st floor, building 64, 1436 Jungong Road, Yangpu District, Shanghai, 200433 Applicant before: QIANXUN SPATIAL INTELLIGENCE Inc. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |