CN110213247B - Method and system for improving safety of pushed information - Google Patents
Method and system for improving safety of pushed information Download PDFInfo
- Publication number
- CN110213247B CN110213247B CN201910405388.6A CN201910405388A CN110213247B CN 110213247 B CN110213247 B CN 110213247B CN 201910405388 A CN201910405388 A CN 201910405388A CN 110213247 B CN110213247 B CN 110213247B
- Authority
- CN
- China
- Prior art keywords
- client
- encryption key
- long connection
- encrypted
- encryption
- 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/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Abstract
The invention discloses a method for improving the safety of push information, wherein a server receives a long connection request sent by a client, and the long connection request comprises an encryption key randomly generated by the client; the server side authenticates the long connection request, and if the authentication is passed, a long connection relation with the client side is established; the server side binds an encryption key in a mapping relation with the client side; the invention authenticates the long connection request sent by the client after the server receives the long connection request through the encryption key randomly generated by the client, establishes the long connection with the client after the authentication is passed, and binds the encryption key into the mapping relation with the client, so that the client uses the randomly generated encryption key to perform encryption and decryption operations in each subsequent session long connection, namely, the encryption key is dynamically generated, the encryption keys of the session long connections in each time are inconsistent, and the reliability and the safety of data in the push message are ensured.
Description
Technical Field
The invention relates to the technical field of data pushing, in particular to a method and a system for improving the safety of pushed information.
Background
In many systems or APPs today, there is a functionality that uses message push. In practice, the number of clients of a general APP system can reach hundreds of thousands or even millions. So many APPs each need to maintain a long connection with the server, and thus millions of long connections need to be connected to the server. Meanwhile, the APP with the established long connection needs to send heartbeat packets to the server at regular intervals, and the server determines the identifier of whether the APP equipment is disconnected.
Under such scenarios, many push systems typically authenticate and establish long links as such. After the client starts the application, the application sends a request for establishing the long link, the request comprises a user name and a password, when the authentication of the server is passed, the long link is established, and after the long link is established, the server and the client can communicate and send related information. Generally, the security of the push message is that the client and the server default or uniformly specify an encryption/decryption key, and the encryption/decryption of the transmission data is uniformly performed through the key, or the encryption/decryption is not required at all for the suddenness, and the plaintext is directly transmitted.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the method and the system for improving the safety of the pushed information are provided, and the safety of the pushed information is improved by dynamically generating an encryption key.
In order to solve the technical problems, the invention adopts the technical scheme that:
a method for improving the safety of push information comprises the following steps:
s1, the server receives a long connection request sent by the client, wherein the long connection request comprises an encryption key randomly generated by the client;
s2, the server side authenticates the long connection request, and if the authentication is passed, the long connection relation with the client side is established;
and S3, the server side binds the encryption key in the mapping relation with the client side.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a system for improving security of pushed information, comprising a server, wherein the server comprises a first memory, a first processor, and a first computer program stored in the first memory and executable on the first processor, and the first processor implements the following steps when executing the first computer program:
s1, receiving a long connection request sent by a client, wherein the long connection request comprises an encryption key randomly generated by the client;
s2, authenticating the long connection request, and if the authentication is passed, establishing a long connection relation with the client;
s3, binding the encryption key in the mapping relation with the client.
The invention has the beneficial effects that: a method and a system for improving the security of push information are provided, wherein a client randomly generates an encryption key, a server side authenticates the long connection request sent by the client after receiving the long connection request, long connection with the client is established after the authentication is passed, and the encryption key is bound to a mapping relation with the client, so that the client uses the randomly generated encryption key to perform encryption and decryption operations in each subsequent session long connection, namely, the encryption key is dynamically generated, the encryption keys of each session long connection are inconsistent, the reliability and the security of data in a push message are ensured, and the data transmission security of a related push system is improved to a greater extent.
Drawings
Fig. 1 is a schematic flowchart of a method for improving security of pushed information according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a system for improving security of push information according to an embodiment of the present invention.
Description of reference numerals:
1. a system for improving the security of push information; 2. a server; 3. a first processor; 4. a first memory; 5. a client; 6. a second processor; 7. a second memory.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
Before this, in order to facilitate understanding of the technical solution of the present invention, the english abbreviations, devices and the like referred to in the present invention are described as follows:
(1) and APP: in the present invention, the abbreviation of Application, wherein the text is interpreted as an Application program.
(2) And key: in the present invention, it is interpreted as a key, and the encrypted key is an encryption key.
(3) id: the invention is an abbreviation of Identity, and in the invention, the abbreviation is a website, a port number, an operation instruction of a client, a physical address and a logical address of a network card or a registration number of software, and the like.
(4) And hashcode: in the present invention, the hash code is interpreted as a numerical value of int type calculated by jdk according to the address or character string or number of the object.
(5) Sk: the key is used for encrypting the plaintext string of the security parameter, and is a key negotiated in advance by the client and the server and stored in the client and the server respectively.
(6) DES: in the present invention, the Data Encryption Standard, in which the text is interpreted as a Data Encryption Standard, is a block algorithm using key Encryption.
Referring to fig. 1, an abbreviation of a method for improving security of push information includes the following steps:
s1, the server receives a long connection request sent by the client, wherein the long connection request comprises an encryption key randomly generated by the client;
s2, the server side authenticates the long connection request, and if the authentication is passed, the long connection relation with the client side is established;
and S3, the server side binds the encryption key in the mapping relation with the client side.
From the above description, the beneficial effects of the present invention are: the encryption key is randomly generated by the client, the server authenticates the long connection request sent by the client after receiving the long connection request, establishes long connection with the client after the authentication is passed, and binds the encryption key to a mapping relation with the client, so that the client uses the randomly generated encryption key to perform encryption and decryption operations in each subsequent session long connection, namely, the dynamically generated encryption key is adopted, the encryption keys of the session long connections in each time are inconsistent, the reliability and the safety of data in a push message are ensured, and the data transmission safety of a related push system is improved to a greater extent.
Further, the step S1 includes before the step of:
s01, the client acquires the real-time timestamp, the equipment id, the fixed character string and the application service parameter to form a unique character string;
s02, the client calculates the unique character string according to the hashcode to obtain an encryption key, and generates a security parameter with a plaintext format of encryption key _ timestamp _ user name;
s03, the client side carries out DES encryption on the security parameters through an encryption sk key to obtain encrypted parameters, and the encryption sk key is stored in the client side and the server side in advance;
s04, the client generates a long connection request including the encrypted parameters and authentication parameters, wherein the authentication parameters include a user name and a password.
As can be seen from the above description, generating hash codes by hashcode can be performed without repetition in as large a space as possible to satisfy millions of long connection requests between the client and the server.
Further, between the step S2 and the step S3, the method further includes:
s21, the server side carries out DES decryption on the encrypted parameters through the encryption sk key to obtain the security parameters;
s22, the server judges whether the user name in the security parameter is consistent with the user name of the authentication parameter, if so, judges whether the difference between the time stamp in the security parameter and the current time of the server is less than the preset time, if so, acquires the encryption key, and if the user name in the security parameter is inconsistent with the user name of the authentication parameter or the difference between the time stamp in the security parameter and the current time of the server is greater than or equal to the preset time, judges that the long connection request is an invalid request.
As can be seen from the above description, after the encrypted sk key is obtained, it is also necessary to verify whether the identity of the encrypted parameter is legal according to the user name, and verify the timeliness of the encrypted parameter according to the timestamp, so that the reliability and the security of the encrypted parameter are ensured.
Further, the step S3 is followed by:
s41, the client generates a service request message, encrypts the service request message through the encryption key to obtain and send the encrypted request message;
s42, the server receives the encrypted request message, extracts the encryption key in the mapping relation, decrypts the encrypted request message through the encryption key to obtain a service request message, generates a service response message responding to the service request message, encrypts the service response message through the encryption key to obtain and send the encrypted response message;
s43, the client receives the encrypted response message, and decrypts the encrypted response message through the encryption key to obtain the service response message.
From the above description, it can be known that, by using the randomly generated encryption key to perform encryption and decryption operations on each long connection message, it is ensured that the data in each subsequent push message has higher reliability and security.
Further, the step S2 is followed by the step of:
and the client judges whether the long connection is disconnected, if so, the second long connection request is regenerated according to the steps from S01 to S04, and the encryption key in the second security parameter in the second long connection request is different from the encryption key in the security parameter in the long connection request.
It can be known from the above description that, when the client disconnects the network or switches the network or other abnormal conditions cause the long connection to be disconnected, and the client needs to reestablish the long connection with the server, the above steps are repeated, and the client regenerates the random encryption key and establishes the long connection, at this time, after the long connection is established, a new encryption key is used to ensure that the encryption keys bound to the long connection established each time are different, so as to implement a dynamic encryption mechanism.
As shown in fig. 2, a system for improving security of pushed information includes a server, where the server includes a first memory, a first processor, and a first computer program stored in the first memory and executable on the first processor, and the first processor implements the following steps when executing the first computer program:
s1, receiving a long connection request sent by a client, wherein the long connection request comprises an encryption key randomly generated by the client;
s2, authenticating the long connection request, and if the authentication is passed, establishing a long connection relation with the client;
s3, binding the encryption key in the mapping relation with the client.
From the above description, the beneficial effects of the present invention are: the encryption key is randomly generated by the client, the server authenticates the long connection request sent by the client after receiving the long connection request, establishes long connection with the client after the authentication is passed, and binds the encryption key to a mapping relation with the client, so that the client uses the randomly generated encryption key to perform encryption and decryption operations in each subsequent session long connection, namely, the dynamically generated encryption key is adopted, the encryption keys of the session long connections in each time are inconsistent, the reliability and the safety of data in a push message are ensured, and the data transmission safety of a related push system is improved to a greater extent.
Further, the client comprises a second memory, a second processor and a second computer program which is stored on the second memory and can run on the second processor;
before the step S1, the second processor, when executing the second computer program, implements the following steps:
s01, acquiring a real-time timestamp, a device id, a fixed character string and an application service parameter to form a unique character string;
s02, calculating the unique character string according to the hash code to obtain an encryption key, and generating a security parameter with a plaintext format of encryption key _ timestamp _ user name;
s03, DES encryption is carried out on the security parameters through an encryption sk key to obtain encrypted parameters, and the encryption sk key is stored in the client and the server in advance;
s04, generating a long connection request comprising the encrypted parameters and authentication parameters, wherein the authentication parameters comprise a user name and a password.
As can be seen from the above description, generating hash codes by hashcode can be performed without repetition in as large a space as possible to satisfy millions of long connection requests between the client and the server.
Further, between the step S2 and the step S3, the first processor, when executing the first computer program, further implements the steps of:
s21, DES decryption is carried out on the encrypted parameters through the encryption sk key to obtain the security parameters;
and S22, judging whether the user name in the security parameter is consistent with the user name of the authentication parameter, if so, judging whether the difference between the time stamp in the security parameter and the current time of the server is less than the preset time, if so, acquiring the encryption key, and if not, judging that the long connection request is an invalid request.
As can be seen from the above description, after the encrypted sk key is obtained, it is also necessary to verify whether the identity of the encrypted parameter is legal according to the user name, and verify the timeliness of the encrypted parameter according to the timestamp, so that the reliability and the security of the encrypted parameter are ensured.
Further, after the step S3, the first processor, when executing the first computer program, further implements the following steps:
s42, receiving an encrypted request message, extracting the encryption key in the mapping relation, decrypting the encrypted request message through the encryption key to obtain a service request message, generating a service response message responding to the service request message, encrypting the service response message through the encryption key to obtain and send an encrypted response message;
after the step S3, the second processor, when executing the second computer program, further implements the following steps:
s41, generating a service request message, encrypting the service request message through the encryption key to obtain and send the encrypted request message;
s43, receiving the encrypted response message, and decrypting the encrypted response message through the encryption key to obtain a service response message.
From the above description, it can be known that, by using the randomly generated encryption key to perform encryption and decryption operations on each long connection message, it is ensured that the data in each subsequent push message has higher reliability and security.
Further, after the step S2, the second processor, when executing the second computer program, further implements the following steps:
and judging whether the long connection is disconnected, if so, regenerating a second time long connection request according to the steps from S01 to S04, wherein the encryption key in the second time security parameter in the second time long connection request is different from the encryption key in the security parameter in the long connection request.
It can be known from the above description that, when the client disconnects the network or switches the network or other abnormal conditions cause the long connection to be disconnected, and the client needs to reestablish the long connection with the server, the above steps are repeated, and the client regenerates the random encryption key and establishes the long connection, at this time, after the long connection is established, a new encryption key is used to ensure that the encryption keys bound to the long connection established each time are different, so as to implement a dynamic encryption mechanism.
Referring to fig. 1, a first embodiment of the present invention is:
a method for improving the safety of push information comprises the following steps:
s1, the server receives a long connection request sent by the client, wherein the long connection request comprises an encryption key randomly generated by the client, namely the client generates a non-repeated random number through a preset random algorithm;
s2, the server side authenticates the long connection request, if the authentication is passed, the long connection relation with the client side is established;
s3, the server side binds the encryption key in the mapping relation with the client side, and thus the encryption key is used for encrypting and decrypting data in subsequent push messages.
Referring to fig. 1, the second embodiment of the present invention is:
a method for improving the security of the pushed information, further comprising, before step S1, the following steps:
s01, the client acquires the real-time timestamp, the equipment id, the fixed character string and the application service parameter to form a unique character string, the equipment id is the unique identification information of the client, the fixed character string can be preset, and the application service parameter is the unique identification information of the application program;
s02, the client calculates the unique character string according to the hash code to obtain an encryption key, and generates a security parameter with a plaintext format of encryption key _ timestamp _ user name, namely, a hash code is generated by adopting the hash code to serve as the unique encryption key;
s03, the client side carries out DES encryption on the security parameters through the encryption sk key to obtain encrypted parameters, and the encryption sk key is stored in the client side and the server side in advance;
s04, the client generates a long connection request including encrypted parameters and authentication parameters, where the authentication parameters include a user name and a password, i.e., the user identity is authenticated according to the user name and the password.
Further included between step S2 and step S3 is:
s21, the server side carries out DES decryption on the encrypted parameters through the encryption sk key to obtain security parameters;
s22, the server determines whether the user name in the security parameter is consistent with the user name of the authentication parameter, if so, determines whether a difference between a timestamp in the security parameter and the current time of the server is less than a preset time, and if so, obtains an encryption key, and if the user name in the security parameter is not consistent with the user name of the authentication parameter or the difference between the timestamp in the security parameter and the current time of the server is greater than or equal to the preset time, determines that the long connection request is an invalid request, where in this embodiment, the preset time is 10 minutes.
Further included after step S3 is:
s41, the client generates a service request message, encrypts the service request message through an encryption key to obtain and send the encrypted request message;
s42, the server receives the encrypted request message, extracts the encryption key in the mapping relation, decrypts the encrypted request message through the encryption key to obtain the service request message, generates a service response message responding to the service request message, encrypts the service response message through the encryption key to obtain and send the encrypted response message;
s43, the client receives the encrypted response message, and decrypts the encrypted response message through the encryption key to obtain the service response message.
Meanwhile, after step S2, after the server establishes the long connection relationship with the client, the method further includes the steps of:
and the client judges whether the long connection is disconnected, if so, the second long connection request is regenerated according to the steps from S01 to S04, and the encryption key in the second security parameter in the second long connection request is different from the encryption key in the security parameter in the long connection request, namely, the encryption keys are not repeated.
Referring to fig. 2, a third embodiment of the present invention is:
a system 1 for improving the security of pushed information comprises a server 2, wherein the server 2 comprises a first memory 4, a first processor 3 and a first computer program stored in the first memory 4 and operable on the first processor 3, and the first processor 3 implements the steps of the first embodiment when executing the first computer program.
Referring to fig. 2, a fourth embodiment of the present invention is:
a system 1 for improving the security of pushed information further includes a client 5 based on the third embodiment, where the client includes a second memory 7, a second processor 6 and a second computer program stored in the second memory 7 and capable of running on the second processor 6, the first processor 3 implements the relevant steps of the second embodiment when executing the first computer program, and the second processor 6 implements the relevant steps of the second embodiment when executing the second computer program.
In summary, according to the method and system for improving the security of the push information provided by the present invention, the client randomly generates the encryption key, the server authenticates the long connection request sent by the client after receiving the long connection request, establishes the long connection with the client after the authentication is passed, and binds the encryption key to the mapping relationship with the client, so that the client performs the encryption and decryption operations by using the randomly generated encryption key in each subsequent session long connection, that is, the dynamic generation of the encryption key is adopted, thereby realizing the inconsistency of the encryption keys of the session long connections each time, ensuring the reliability and the security of the data in the push information, and improving the security of the data transmission of the related push system to a greater extent; the hash code is generated through the hash code, and the hash code can not be repeated in a space as large as possible so as to meet millions of long connection requests between the client and the server; the identity of the encrypted parameter is verified to be legal through the user name, the timeliness of the encrypted parameter is verified through the timestamp, the reliability and the safety of the encrypted parameter are guaranteed, and the reliability and the safety of data in a push message are indirectly guaranteed; when the long connection between the client and the server is disconnected, the client regenerates the random encryption key and establishes the long connection, i.e. the encryption keys bound to the established long connection are different each time, so as to realize a dynamic encryption mechanism.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (8)
1. A method for improving the safety of push information is characterized by comprising the following steps:
s1, the server receives a long connection request sent by the client, wherein the long connection request comprises an encryption key randomly generated by the client;
s2, the server side authenticates the long connection request, and if the authentication is passed, the long connection relation with the client side is established;
s3, the server side binds the encryption key in the mapping relation with the client side;
the step S1 includes:
s01, the client acquires the real-time timestamp, the equipment id, the fixed character string and the application service parameter to form a unique character string;
s02, the client calculates the unique character string according to the hashcode to obtain an encryption key, and generates a security parameter with a plaintext format of encryption key _ timestamp _ user name;
s03, the client side carries out DES encryption on the security parameters through an encryption sk key to obtain encrypted parameters, and the encryption sk key is stored in the client side and the server side in advance;
s04, the client generates a long connection request including the encrypted parameters and authentication parameters, wherein the authentication parameters include a user name and a password.
2. The method of claim 1, wherein between the step S2 and the step S3, further comprising:
s21, the server side carries out DES decryption on the encrypted parameters through the encryption sk key to obtain the security parameters;
s22, the server judges whether the user name in the security parameter is consistent with the user name of the authentication parameter, if so, judges whether the difference between the time stamp in the security parameter and the current time of the server is less than the preset time, if so, acquires the encryption key, and if the user name in the security parameter is inconsistent with the user name of the authentication parameter or the difference between the time stamp in the security parameter and the current time of the server is greater than or equal to the preset time, judges that the long connection request is an invalid request.
3. The method for improving the security of the pushed information according to claim 1, wherein the step S3 is further followed by:
s41, the client generates a service request message, encrypts the service request message through the encryption key to obtain and send the encrypted request message;
s42, the server receives the encrypted request message, extracts the encryption key in the mapping relation, decrypts the encrypted request message through the encryption key to obtain a service request message, generates a service response message responding to the service request message, encrypts the service response message through the encryption key to obtain and send the encrypted response message;
s43, the client receives the encrypted response message, and decrypts the encrypted response message through the encryption key to obtain the service response message.
4. The method for improving the security of the pushed information according to claim 1, wherein the step S2 is further followed by the step of:
and the client judges whether the long connection is disconnected, if so, the second long connection request is regenerated according to the steps from S01 to S04, and the encryption key in the second security parameter in the second long connection request is different from the encryption key in the security parameter in the long connection request.
5. A system for improving security of pushed information, comprising a server, wherein the server comprises a first memory, a first processor, and a first computer program stored in the first memory and executable on the first processor, and wherein the first processor implements the following steps when executing the first computer program:
s1, receiving a long connection request sent by a client, wherein the long connection request comprises an encryption key randomly generated by the client;
s2, authenticating the long connection request, and if the authentication is passed, establishing a long connection relation with the client;
s3, binding the encryption key in the mapping relation with the client;
the client comprises a second memory, a second processor and a second computer program which is stored on the second memory and can run on the second processor;
before the step S1, the second processor, when executing the second computer program, implements the following steps:
s01, acquiring a real-time timestamp, a device id, a fixed character string and an application service parameter to form a unique character string;
s02, calculating the unique character string according to the hash code to obtain an encryption key, and generating a security parameter with a plaintext format of encryption key _ timestamp _ user name;
s03, DES encryption is carried out on the security parameters through an encryption sk key to obtain encrypted parameters, and the encryption sk key is stored in the client and the server in advance;
s04, generating a long connection request comprising the encrypted parameters and authentication parameters, wherein the authentication parameters comprise a user name and a password.
6. The system of claim 5, wherein between the step S2 and the step S3, the first processor further implements the following steps when executing the first computer program:
s21, DES decryption is carried out on the encrypted parameters through the encryption sk key to obtain the security parameters;
and S22, judging whether the user name in the security parameter is consistent with the user name of the authentication parameter, if so, judging whether the difference between the time stamp in the security parameter and the current time of the server is less than the preset time, if so, acquiring the encryption key, and if not, judging that the long connection request is an invalid request.
7. The system according to claim 5, wherein after the step S3, the first processor executes the first computer program to further implement the following steps:
s42, receiving an encrypted request message, extracting the encryption key in the mapping relation, decrypting the encrypted request message through the encryption key to obtain a service request message, generating a service response message responding to the service request message, encrypting the service response message through the encryption key to obtain and send an encrypted response message;
after the step S3, the second processor, when executing the second computer program, further implements the following steps:
s41, generating a service request message, encrypting the service request message through the encryption key to obtain and send the encrypted request message;
s43, receiving the encrypted response message, and decrypting the encrypted response message through the encryption key to obtain a service response message.
8. The system according to claim 5, wherein after the step S2, the second processor executes the second computer program to further implement the following steps:
and judging whether the long connection is disconnected, if so, regenerating a second time long connection request according to the steps from S01 to S04, wherein the encryption key in the second time security parameter in the second time long connection request is different from the encryption key in the security parameter in the long connection request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910405388.6A CN110213247B (en) | 2019-05-16 | 2019-05-16 | Method and system for improving safety of pushed information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910405388.6A CN110213247B (en) | 2019-05-16 | 2019-05-16 | Method and system for improving safety of pushed information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110213247A CN110213247A (en) | 2019-09-06 |
| CN110213247B true CN110213247B (en) | 2021-10-01 |
Family
ID=67787342
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910405388.6A Active CN110213247B (en) | 2019-05-16 | 2019-05-16 | Method and system for improving safety of pushed information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110213247B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110740128B (en) * | 2019-09-27 | 2022-08-23 | 武汉虹识技术有限公司 | Offline data encryption method and device |
| CN112202792A (en) * | 2020-09-30 | 2021-01-08 | 京东数字科技控股股份有限公司 | Communication method and device for establishing long connection between client and server |
| CN113259132B (en) * | 2021-06-30 | 2021-09-28 | 平安普惠企业管理有限公司 | Data transmission encryption and decryption method and device, computer equipment and storage medium |
| CN113472792B (en) * | 2021-07-01 | 2023-05-05 | 北京玩蟹科技有限公司 | Communication encryption method and system for long-connection network |
| CN116260653B (en) * | 2023-03-20 | 2023-10-13 | 浪潮智慧科技有限公司 | Data transmission method, device and medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105337935A (en) * | 2014-07-09 | 2016-02-17 | 阿里巴巴集团控股有限公司 | Method of establishing long connection of client and server and apparatus thereof |
| CN106658493A (en) * | 2016-10-17 | 2017-05-10 | 东软集团股份有限公司 | Key management method, device and system |
| CN108881256A (en) * | 2018-06-29 | 2018-11-23 | 北京旅居四方科技有限公司 | Key exchange method, device, water power stake and the network equipment |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104506483A (en) * | 2014-10-21 | 2015-04-08 | 中兴通讯股份有限公司 | Method for encrypting and decrypting information and managing secret key as well as terminal and network server |
| CN106230587B (en) * | 2016-08-05 | 2019-01-22 | 浪潮软件股份有限公司 | A kind of method of long connection anti-replay-attack |
| CN107819768B (en) * | 2017-11-15 | 2020-07-31 | 厦门安胜网络科技有限公司 | Method for server to actively disconnect illegal long connection, terminal equipment and storage medium |
-
2019
- 2019-05-16 CN CN201910405388.6A patent/CN110213247B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105337935A (en) * | 2014-07-09 | 2016-02-17 | 阿里巴巴集团控股有限公司 | Method of establishing long connection of client and server and apparatus thereof |
| CN106658493A (en) * | 2016-10-17 | 2017-05-10 | 东软集团股份有限公司 | Key management method, device and system |
| CN108881256A (en) * | 2018-06-29 | 2018-11-23 | 北京旅居四方科技有限公司 | Key exchange method, device, water power stake and the network equipment |
Non-Patent Citations (1)
| Title |
|---|
| 税费实时划缴系统的研究与实现;黄建兵;《中国优秀博硕士学位论文全文数据库 (硕士)信息科技辑》;20061215;第4.6.3、4.7.4节 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110213247A (en) | 2019-09-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110213247B (en) | Method and system for improving safety of pushed information | |
| CN109347835B (en) | Information transmission method, client, server, and computer-readable storage medium | |
| CN110380852B (en) | Bidirectional authentication method and communication system | |
| CN110621014B (en) | Vehicle-mounted equipment, program upgrading method thereof and server | |
| CN103166931A (en) | Method, device and system of transmitting data safely | |
| CN113067828A (en) | Message processing method and device, server, computer equipment and storage medium | |
| CN111935712A (en) | Data transmission method, system and medium based on NB-IoT communication | |
| CN110690966B (en) | Method, system, equipment and storage medium for connecting terminal and service server | |
| CN111884811B (en) | Block chain-based data evidence storing method and data evidence storing platform | |
| CN105491073B (en) | Data downloading method, device and system | |
| CN111030814A (en) | Key negotiation method and device | |
| CN111181723B (en) | Method and device for offline security authentication between Internet of things devices | |
| CN104836784A (en) | Information processing method, client, and server | |
| CN111130798A (en) | Request authentication method and related equipment | |
| CN110839240B (en) | Method and device for establishing connection | |
| CN110740038B (en) | Blockchain and communication method, gateway, communication system and storage medium thereof | |
| CN111654503A (en) | Remote control method, device, equipment and storage medium | |
| CN113163399A (en) | Communication method and device of terminal and server | |
| CN115913618A (en) | Method, medium and terminal for guaranteeing TCP communication safety based on hybrid encryption | |
| CN112887983B (en) | Equipment identity authentication method, device, equipment and medium | |
| CN113922973B (en) | Ciphertext-based login method and equipment | |
| CN113079506B (en) | Network security authentication method, device and equipment | |
| CN111865956A (en) | System, method, device and storage medium for preventing service hijacking | |
| CN112637140A (en) | Password transmission method, terminal, server and readable storage medium | |
| CN113726720B (en) | Internet of things equipment communication method, equipment, server and communication system |
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 |