CN111865576B - Method and device for synchronizing URL classification data - Google Patents

Method and device for synchronizing URL classification data Download PDF

Info

Publication number
CN111865576B
CN111865576B CN202010630843.5A CN202010630843A CN111865576B CN 111865576 B CN111865576 B CN 111865576B CN 202010630843 A CN202010630843 A CN 202010630843A CN 111865576 B CN111865576 B CN 111865576B
Authority
CN
China
Prior art keywords
url
synchronization
url classification
server
data
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
Application number
CN202010630843.5A
Other languages
Chinese (zh)
Other versions
CN111865576A (en
Inventor
齐军
叶晨
康新强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Skyguard Network Security Technology Co ltd
Chengdu Sky Guard Network Security Technology Co ltd
Original Assignee
Chengdu Sky Guard Network Security Technology Co ltd
Beijing Skyguard Network Security Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Chengdu Sky Guard Network Security Technology Co ltd, Beijing Skyguard Network Security Technology Co ltd filed Critical Chengdu Sky Guard Network Security Technology Co ltd
Priority to CN202010630843.5A priority Critical patent/CN111865576B/en
Publication of CN111865576A publication Critical patent/CN111865576A/en
Application granted granted Critical
Publication of CN111865576B publication Critical patent/CN111865576B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0869—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving random numbers or seeds
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/906—Clustering; Classification
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
    • 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]
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • 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
    • 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/3247—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 digital signatures

Abstract

The invention discloses a method and a device for synchronizing URL classified data, and relates to the technical field of computers. One embodiment of the method comprises: sending an authentication request to a server to obtain an authorization token; respectively calculating the synchronization strategy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client; and acquiring URL classification data from the server side by using the authorization token based on the synchronization policy of each URL classification. The implementation mode can solve the technical problems of large network broadband consumption or large resource occupation.

Description

Method and device for synchronizing URL classification data
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for synchronizing URL classified data.
Background
The access to the internet through the enterprise network becomes the main daily behavior of the staff, and the staff access to the internet sites in the working time, so that the working efficiency of the staff is reduced, potential safety hazards exist, and even enterprise information assets can be stolen, leaked and damaged. In order to standardize the access behavior of the staff and protect the security of the enterprise data, the URLs of the staff access sites must be subjected to feature classification, and different security control is performed for different URL classifications.
Meanwhile, a large number of new network sites and web pages are generated in the internet every day, and a large number of sites are closed or the content of web pages of the sites is updated. Therefore, a URL classification feature library needs to be established at the cloud end, static classification and cloud end intelligent classification are carried out on massive Internet sites, and accuracy of URL classification is guaranteed. How to safely, timely and accurately synchronize URL classified data from the cloud to the local on an enterprise safety management platform becomes a key problem of enterprise safety prevention and control.
The client side synchronizes data from the cloud URL classification library, and at present, there are two ways: firstly, synchronizing full data; secondly, the latest incremental data is synchronized, namely only the condition is satisfied: cloud base update time > last synchronization time of the local base.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
the first method has low synchronization efficiency and poor stability: the URL classification comprises dozens of major classes, each major class comprises a plurality of subcategories, each subcategorie comprises various characteristic information and massive URLs, and the synchronization of the full data at each time greatly consumes network bandwidth and storage resources. Once network jitter or full storage resource conditions occur, the synchronization process can be interrupted and difficult to automatically recover.
The second way solves the disadvantages of the first way, but for the client, the computing resources are greatly occupied, and other services of the system are unstable. The client-side needs to calculate two cloud-end increment and local mass data sets in each synchronization, so that the data needing to be newly added, the data needing to be updated and the data needing to be deleted are determined, and the local library can be updated after the data are merged.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for synchronizing URL classification data, so as to solve the technical problem of large network bandwidth consumption or large resource occupation.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method of synchronizing URL classification data, including:
sending an authentication request to a server to obtain an authorization token;
respectively calculating the synchronization strategy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client;
and acquiring URL classification data from the server side by using the authorization token based on the synchronization policy of each URL classification.
Optionally, sending an authentication request to the server to obtain the authorization token, including:
sending a first authentication request carrying a first authentication parameter to a server so that the server verifies the first authentication parameter; the first authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number and the code of a first initial key;
receiving a second random number returned by the server to verify the digit of the second random number;
if the verification is passed, sending a second authentication request carrying a second authentication parameter to the server so that the server verifies the second authentication parameter; the second authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number, a second random number and the code of a second initial key;
and receiving the authorization token returned by the server.
Optionally, the device information includes a device identifier and a device type;
the first initial key is: taking the device information, the serial number of the license and the first random number as messages, and signing the messages through a built-in fixed key to obtain a character string;
the second initial key is: and taking the device information, the serial number of the license, the first random number and the second random number as messages, and signing the messages through a built-in fixed key to obtain a character string.
Optionally, the calculating, according to the historical access data of the client, the historical synchronization data, and the attribute features of each URL classification, a synchronization policy of each URL classification includes:
according to historical access data of a client, calculating the access quantity and the access duration of each URL classification, and thus calculating the access frequency score of each URL classification;
calculating the updating frequency of each URL classification according to the historical synchronous data of the client, so as to calculate the updating frequency score of each URL classification;
calculating a security level score of each URL classification according to the security level attribute of each URL classification;
calculating the number of URLs contained in each URL classification according to the URLs contained in each URL classification;
and respectively calculating the synchronization strategy of each URL classification based on the access frequency score, the update frequency score, the security level score and the number of the contained URLs of each URL classification.
Optionally, the calculating, based on the access frequency score, the update frequency score, the security level score, and the number of URLs included in each URL classification, a synchronization policy for each URL classification includes:
based on the access frequency scores, the updating frequency scores, the safety level scores and weights corresponding to the number of contained URLs, carrying out weighted summation on the access frequency scores, the updating frequency scores, the safety level scores and the number of contained URLs of each URL classification to obtain synchronous scores of each URL classification;
matching a corresponding synchronization strategy of each URL classification according to the synchronization score of each URL classification; the synchronization strategy comprises a synchronization mode, a synchronization frequency, a synchronization start time, a synchronization end time and a synchronization interval time in each synchronization process.
Optionally, the obtaining, by using the authorization token, URL classification data from the server based on the synchronization policy of each URL classification includes:
for each URL classification, obtaining a version number of the URL classification from the server using the authorization token based on a synchronization policy of the URL classification;
judging whether the version number of the URL classification acquired from the server side is higher than the version number of the URL classification local to the client side;
if yes, based on the URL classified synchronization strategy, the authorization token is used for acquiring the URL classified data from the server side;
if not, the process is ended.
Optionally, based on the synchronization policy of the URL classification, using the authorization token to obtain the data of the URL classification from the server side includes:
based on the synchronization policy of the URL classification, acquiring the total size of the URL classified data from the server by using the authorization token;
dividing the data classified by the URL into a plurality of fragments according to the total size of the data classified by the URL;
and acquiring the URL classified data from the server side by using the authorization token piece by piece until the last piece.
In addition, according to another aspect of the embodiments of the present invention, there is provided an apparatus for synchronizing URL classification data, including:
the acquisition module is used for sending an authentication request to the server to acquire an authorization token;
the calculation module is used for respectively calculating the synchronization strategies of all the URL classifications according to the historical access data, the historical synchronization data and the attribute characteristics of all the URL classifications of the client;
and the synchronization module is used for acquiring URL classification data from the server by using the authorization token based on the synchronization strategy of each URL classification.
Optionally, the obtaining module is further configured to:
sending a first authentication request carrying a first authentication parameter to a server so that the server verifies the first authentication parameter; the first authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number and the code of a first initial key;
receiving a second random number returned by the server to verify the digit of the second random number;
if the verification is passed, sending a second authentication request carrying a second authentication parameter to the server so that the server verifies the second authentication parameter; the second authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number, a second random number and the code of a second initial key;
and receiving the authorization token returned by the server.
Optionally, the device information includes a device identifier and a device type;
the first initial key is: taking the device information, the serial number of the license and the first random number as messages, and signing the messages through a built-in fixed key to obtain a character string;
the second initial key is: and taking the equipment information, the serial number of the license, the first random number and the second random number as messages, and signing the messages through the built-in fixed key to obtain a character string.
Optionally, the computing module is further configured to:
according to historical access data of a client, calculating the access quantity and the access duration of each URL classification, and thus calculating the access frequency score of each URL classification;
calculating the updating frequency of each URL classification according to the historical synchronous data of the client, thereby calculating the updating frequency score of each URL classification;
calculating the security level score of each URL classification according to the security level attribute of each URL classification;
calculating the number of URLs contained in each URL classification according to the URLs contained in each URL classification;
and respectively calculating the synchronization strategy of each URL classification based on the access frequency score, the update frequency score, the security level score and the number of the contained URLs of each URL classification.
Optionally, the computing module is further configured to:
based on the access frequency scores, the updating frequency scores, the safety level scores and the weights corresponding to the contained URL numbers, carrying out weighted summation on the access frequency scores, the updating frequency scores, the safety level scores and the contained URL numbers of the URL classifications to obtain synchronous scores of the URL classifications;
matching a corresponding synchronization strategy of each URL classification according to the synchronization score of each URL classification; the synchronization strategy comprises a synchronization mode, a synchronization frequency, a synchronization starting time, a synchronization ending time and a synchronization interval time in each synchronization process.
Optionally, the synchronization module is further configured to:
for each URL category, a version number of the URL category obtained from the server using the authorization token based on a synchronization policy of the URL category;
judging whether the version number of the URL classification acquired from the server side is higher than the version number of the URL classification local to the client side;
if yes, based on the URL classified synchronization strategy, the authorization token is used for acquiring the URL classified data from the server side;
if not, the process is ended.
Optionally, the synchronization module is further configured to:
based on the synchronization policy of the URL classification, acquiring the total size of the URL classified data from the server by using the authorization token;
dividing the data classified by the URL into a plurality of fragments according to the total size of the data classified by the URL;
and acquiring the URL classified data from the server side by using the authorization token piece by piece until the last piece.
According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including:
one or more processors;
a storage device to store one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any of the embodiments described above.
According to another aspect of the embodiments of the present invention, there is also provided a computer readable medium, on which a computer program is stored, which when executed by a processor implements the method of any of the above embodiments.
One embodiment of the above invention has the following advantages or benefits: because the synchronization strategy of each URL classification is respectively calculated according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client, the technical means of acquiring the URL classification data from the server by using the authorization token based on the synchronization strategy of each URL classification is adopted, and the technical problems of high network broadband consumption or large resource occupation in the prior art are solved. The embodiment of the invention ensures the communication and data security by a perfect security authentication mechanism and various means of certificate public key, license and initial key signature, respectively calculates the synchronous strategy of each URL classification according to the historical access data, the historical synchronous data and the attribute characteristics of each URL classification of the client, and synchronizes the URL classified data based on the synchronous strategy, thereby overcoming the defect of a single synchronous mode, not only safely and quickly synchronizing the data, but also reducing the occupation of the system resources of the client, and further improving the integral stability of the system.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of a main flow of a method of synchronizing URL classification data according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a main flow of a method of synchronizing URL classification data according to one referenceable embodiment of the present invention;
FIG. 3 is a schematic diagram of the main flow of a method of synchronizing URL classification data according to another referenceable embodiment of the present invention;
FIG. 4 is a schematic diagram of the main flow of a method of synchronizing URL classification data according to yet another referential embodiment of the present invention;
FIG. 5 is a schematic diagram of the main modules of an apparatus for synchronizing URL classification data according to an embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
FIG. 1 is a schematic diagram of the main flow of a method for synchronizing URL classification data according to an embodiment of the present invention. As an embodiment of the present invention, as shown in fig. 1, the method for synchronizing URL classification data may include:
step 101, sending an authentication request to a server to obtain an authorization token.
Firstly, a client sends an authentication request to a server to obtain an authorization token, and in the subsequent steps, the authorization token is required to be used for acquiring URL classification data from the server so as to ensure that the URL classification data are safely synchronized.
Optionally, step 101 may comprise: sending a first authentication request carrying a first authentication parameter to a server so that the server verifies the first authentication parameter; the first authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number and the code of a first initial key; receiving a second random number returned by the server to verify the digit of the second random number; if the verification is passed, sending a second authentication request carrying a second authentication parameter to the server so that the server verifies the second authentication parameter; the second authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, the first random number, the second random number and the code of a second initial key; and receiving the authorization token returned by the server. Optionally, the device information includes a device identifier and a device type; the first initial key is: taking the device information, the serial number of the license and the first random number as messages, and signing the messages through a built-in fixed key to obtain a character string; the second initial key is: and taking the device information, the serial number of the license, the first random number and the second random number as messages, and signing the messages through a built-in fixed key to obtain a character string.
Firstly, a client sends a first authentication request to a server, and the request needs to contain the following information: device ID (deviceID), device type (deviceType), base64 code of client certificate public key (key), serial number of license (sn), hexadecimal value of client 512bit random number (cnonce), and base64 code (signature) after calculating client first initial key using HMAC-SHA256 algorithm. The first initial key is a character string obtained by signing a device ID (deviceID), a device type (deviceType), a serial number (sn) of a license and a hexadecimal value (cnonce) of a client 512bit random number by using a built-in fixed key.
And after receiving the first authentication request, the server verifies the first authentication parameters carried in the request, and if the verification is passed, the server returns the second random number (nonce) to the client.
And after receiving a second random number issued by the server, the client verifies the digit of the second random number, and if the verification is passed, a second authentication request carrying a second authentication parameter is sent to the server. The second authentication parameter includes the second random number and the first authentication parameter, and at this time, the first authentication parameter includes: a device ID (deviceID), a device type (deviceType), a base64 code (key) of a client certificate public key, a serial number (sn) of a license, a hexadecimal value (cnonce) of a client 512bit random number, a second random number (nonce), and a base64 code (signature) after calculating a client second initial key using HMAC-SH a256 algorithm; the second initial key is a character string obtained by signing the device ID (deviceID), the device type (deviceType), the serial number (sn) of the license, the hexadecimal value (cnonce) of the client 512bit random number and the second random number (nonce) by using a built-in fixed key.
And after receiving the second authentication request, the server verifies the second authentication parameters carried in the request, and if the second authentication parameters pass the verification, the server returns an authorization token (token) and expiration time to the client.
Before the expiration time, the client and the server directly use the authorization token to communicate; after the expiration time, the client needs to resend the authentication request according to the above steps to obtain a new authorization token.
The authorization interface may be as follows:
Figure BDA0002568599170000101
Figure BDA0002568599170000111
and 102, respectively calculating the synchronization strategy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client.
According to the embodiment of the invention, the synchronization strategies of all URL classifications are respectively calculated according to the historical access data, the historical synchronization data and the attribute characteristics of all URL classifications, so that different URL classifications correspond to different synchronization strategies, and the traditional fixed mode synchronization method is used instead.
And (4) URL classification: the method comprises the steps of classifying URLs of internet sites, wherein the URLs comprise tens of major categories such as portal websites, society and life, job hunting and recruitment, illegal or bad websites and network security, and the like, and a plurality of sub-categories are arranged below each major category, such as sub-categories including shopping, tourism, trip, blog microblog and the like below the society and life. Each subcategory comprises attributes such as name, description, URL address and the like, and according to different categories, risk level attributes are extended, such as the highest risk level of network security and illegal or bad websites.
Optionally, step 102 may comprise: according to historical access data of a client, calculating the access number and the access duration of each URL classification, and therefore calculating the access frequency score of each URL classification; calculating the updating frequency of each URL classification according to the historical synchronous data of the client, so as to calculate the updating frequency score of each URL classification; calculating the security level score of each URL classification according to the security level attribute of each URL classification; calculating the number of URLs contained in each URL classification according to the URLs contained in each URL classification; and respectively calculating the synchronization strategy of each URL classification based on the access frequency score, the update frequency score, the security level score and the number of the contained URLs of each URL classification.
And the client carries out aggregation statistics on historical data of sites visited by the user in a recent period of time, calculates the visit number and the time-length ratio of each URL classification, and further calculates the visit frequency score of each URL classification in a weighting manner. And the client side counts the updating frequency of different URL classifications according to the historical synchronous data, and converts the updating frequency score of each URL classification according to the value. The client gives each URL classification a different security level score based on the security level attributes of the URL classification. And the client counts the number of URLs contained in each URL classification. The synchronization policies for each URL category may then be calculated based on the access frequency scores, update frequency scores, security level scores, and the number of URLs included for each URL category, respectively.
Optionally, the calculating, based on the access frequency score, the update frequency score, the security level score, and the number of URLs included in each URL classification, a synchronization policy for each URL classification includes: based on the access frequency scores, the updating frequency scores, the safety level scores and the weights corresponding to the contained URL numbers, carrying out weighted summation on the access frequency scores, the updating frequency scores, the safety level scores and the contained URL numbers of the URL classifications to obtain synchronous scores of the URL classifications; matching a corresponding synchronization strategy of each URL classification according to the synchronization score of each URL classification; the synchronization strategy comprises a synchronization mode (full-quantity synchronization or incremental synchronization), a synchronization frequency, a synchronization starting time and a synchronization ending time, and a synchronization interval time in each synchronization process. Generally, the URL classification of the security class uses a full-volume synchronization method, and the URL classification with low security requirement may use an incremental synchronization method.
In the embodiment of the invention, different weights can be configured for the access frequency score, the update frequency score, the security level score and the number of contained URLs, and then the four factors of the access frequency score, the update frequency score, the security level score and the number of contained URLs are weighted and summed to calculate the synchronous score of each URL classification. And finally, matching the corresponding synchronization strategies of all URL classifications according to the synchronization scores.
Alternatively, the synchronization frequency may be once a day, three times a day, once every two days, once a week, etc.; the synchronization start time and the synchronization end time can be 0; the synchronization interval time in each synchronization process may be 10 minutes, 20 minutes, 30 minutes, or the like.
For example, the synchronization frequency is once a day, the synchronization start time and the synchronization end time are 0-00, and the synchronization interval time in each synchronization process is 30 minutes, then the client needs to perform synchronization every half hour until the synchronization end time, so that the synchronization stability can be ensured.
Step 103, based on the synchronization policy of each URL classification, using the authorization token to obtain URL classification data from the server.
And after the client calculates the synchronous strategy of each URL classification, the client acquires the classification data of each URL classification from the server by using the authorization token.
Optionally, step 103 may include: for each URL classification, obtaining a version number of the URL classification from the server using the authorization token based on a synchronization policy of the URL classification; judging whether the version number of the URL classification acquired from the server side is higher than the version number of the URL classification local to the client side; if yes, based on the URL classified synchronization strategy, the authorization token is used for acquiring the URL classified data from the server side; if not, the process is ended.
Optionally, based on the synchronization policy of the URL classification, using the authorization token to obtain the data of the URL classification from the server side includes: based on the synchronization policy of the URL classification, acquiring the total size of the URL classified data from the server by using the authorization token; dividing the data classified by the URL into a plurality of fragments according to the total size of the data classified by the URL; and acquiring the URL classified data from the server side by using the authorization token piece by piece until the last piece. First, the client sends a head request by using the authorization token to obtain the total size of the update data of the server. And then dividing the data into different fragments according to the total size of the synchronous data, requesting the data of only one fragment by the client at each time, synchronizing the data from the server, entering a URL (uniform resource locator) classified local library of the client, and repeating the steps until the last fragment. The embodiment of the invention adopts a fragmentation mode to synchronize data from the server, only small amount of data is synchronized each time, thereby reducing the system load and synchronization pressure of the client and ensuring the stability and reliability of the system.
Server URL classification library: the URL classification library is large and can be changed at any time, and a large amount of resources are required to be invested for operation and maintenance, so that the client security system generally only initializes a basic library and synchronously updates the server according to business requirements at a later stage.
Client-side URL classification local library: if the enterprise wants to manage and control the user behavior through URL classification, for example, the shopping website can be accessed only 3 times in working hours, and each time lasts for 10 minutes; or forbidding access to illegal or bad websites, the security system of the client needs to be configured with a policy related to URL classification to realize the access. A large number of requests of enterprise users can identify corresponding URL classifications, and in order to accelerate the processing speed of the security gateway, URL classification data needs to be locally persisted, namely, the latest URL classification data is synchronized into a local library from a server.
According to the various embodiments, it can be seen that the embodiment of the present invention respectively calculates the synchronization policy of each URL classification according to the historical access data, the historical synchronization data of the client and the attribute characteristics of each URL classification, so that the technical means of obtaining the URL classification data from the server by using the authorization token based on the synchronization policy of each URL classification solves the technical problems of large network broadband consumption or large resource occupation in the prior art. The embodiment of the invention ensures the communication and data security by a perfect security authentication mechanism and a plurality of means of certificate public key, license and initial key signature, respectively calculates the synchronization strategy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client, synchronizes the URL classification data based on the synchronization strategy, solves the defect of a single synchronization mode, can safely and quickly synchronize the data, and can reduce the occupation of the system resources of the client, thereby improving the overall stability of the system.
FIG. 2 is a schematic diagram of the main flow of a method for synchronizing URL classification data according to one referential embodiment of the present invention. As another embodiment of the present invention, as shown in fig. 2, the step of sending, by the client, an authentication request to the server to obtain the authorization token may include:
step 201, a first authentication request carrying a first authentication parameter is sent to a server, so that the server verifies the first authentication parameter.
The first authentication parameter comprises equipment information of the client, the code of the certificate public key, the serial number of the license, the first random number and the code of the first initial key. The device information includes a device identifier and a device type, and the first initial key is: and taking the device information, the serial number of the license and the first random number as messages, and signing the messages through a built-in fixed key to obtain a character string.
Step 202, receiving a second random number returned by the server to verify the digit of the second random number. If the verification is passed, go to step 203; if not, the verification is not passed, and then the method is ended.
Step 203, sending a second authentication request carrying a second authentication parameter to the server, so that the server verifies the second authentication parameter.
The second authentication parameter includes device information of the client, an encoding of a certificate public key, a serial number of a license, a first random number, a second random number, and an encoding of a second initial key. The device information includes a device identifier and a device type, and the second initial key is: and taking the device information, the serial number of the license, the first random number and the second random number as messages, and signing the messages through a built-in fixed key to obtain a character string.
And step 204, receiving the authorization token and the expiration time returned by the server.
Before the expiration time, the client and the server directly use the authorization token to communicate; after the expiration time, the client needs to resend the authentication request according to the above steps to obtain a new authorization token.
In addition, in a reference embodiment of the present invention, the detailed implementation of the method for synchronizing URL classification data is described in detail above, and therefore the repeated description is omitted here.
FIG. 3 is a diagram illustrating the main flow of a method for synchronizing URL classification data according to another exemplary embodiment of the present invention. As another embodiment of the present invention, as shown in fig. 3, the step of calculating the synchronization policy for each URL category may include:
step 301, according to the historical access data of the client, calculating the access number and the access duration of each URL classification, thereby calculating the access frequency score of each URL classification.
Step 302, calculating the update frequency of each URL classification according to the historical synchronization data of the client, thereby calculating the update frequency score of each URL classification.
Step 303, calculating the security level score of each URL classification according to the security level attribute of each URL classification.
Step 304, calculating the number of the contained URLs of each URL classification according to the contained URLs under each URL classification.
And 305, carrying out weighted summation on the access frequency score, the update frequency score, the security level score and the number of the contained URLs based on the access frequency score, the update frequency score, the security level score and the weight corresponding to the number of the contained URLs to obtain the synchronous score of each URL classification.
And step 306, matching the corresponding synchronization strategies of the URL classifications according to the synchronization scores of the URL classifications.
The synchronization strategy comprises a synchronization mode, a synchronization frequency, a synchronization starting time, a synchronization ending time and a synchronization interval time in each synchronization process.
It should be noted that the execution sequence of steps 301 to 304 is not unique, and may be executed in any order or simultaneously, and the embodiment of the present invention is not limited to this.
In addition, in another embodiment of the present invention, the method for synchronizing URL classification data is described in detail in the above-mentioned method for synchronizing URL classification data, and therefore, the repeated description is omitted.
FIG. 4 is a diagram illustrating a main flow of a method for synchronizing URL classification data according to still another exemplary embodiment of the present invention. As still another embodiment of the present invention, as shown in fig. 4, the method for synchronizing URL classification data may include:
step 401, sending an authentication request to a server to obtain an authorization token.
Step 402, respectively calculating the synchronization strategy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client.
Step 403, for each URL class, based on the synchronization policy of the URL class, obtaining the version number of the URL class from the server using the authorization token.
Step 404, determining whether the version number of the URL classification obtained from the server is higher than the version number of the URL classification local to the client; if yes, go to step 405; if not, ending.
Step 405, based on the synchronization policy of the URL classification, obtaining the total size of the URL classified data from the server side using the authorization token.
Step 406, dividing the data classified by the URL into a plurality of segments according to the total size of the data classified by the URL.
Step 407, obtaining the URL classified data from the server by using the authorization token piece by piece until the last piece.
In addition, in another embodiment of the present invention, the method for synchronizing URL classification data is described in detail in the above-mentioned method for synchronizing URL classification data, and therefore, the repeated description is omitted.
FIG. 5 is a schematic diagram of the main modules of an apparatus for synchronizing URL classification data according to an embodiment of the present invention, as shown in FIG. 5, the apparatus 500 for synchronizing URL classification data includes an acquisition module 501, a calculation module 502 and a synchronization module 503; the obtaining module 501 is configured to send an authentication request to a server to obtain an authorization token; the calculation module 502 is configured to calculate a synchronization policy for each URL classification according to historical access data of the client, historical synchronization data, and attribute features of each URL classification; the synchronization module 503 is configured to obtain URL classification data from the server using the authorization token based on the synchronization policy of each URL classification.
Optionally, the obtaining module 501 is further configured to:
sending a first authentication request carrying a first authentication parameter to a server so that the server verifies the first authentication parameter; the first authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number and the code of a first initial key;
receiving a second random number returned by the server to verify the digit of the second random number;
if the verification is passed, sending a second authentication request carrying a second authentication parameter to the server so that the server verifies the second authentication parameter; the second authentication parameters comprise equipment information of the client, codes of a certificate public key, a serial number of a license, a first random number, a second random number and codes of a second initial key;
and receiving the authorization token returned by the server.
Optionally, the device information includes a device identifier and a device type;
the first initial key is: taking the device information, the serial number of the license and the first random number as messages, and signing the messages through a built-in fixed key to obtain a character string;
the second initial key is: and taking the device information, the serial number of the license, the first random number and the second random number as messages, and signing the messages through a built-in fixed key to obtain a character string.
Optionally, the calculating module 502 is further configured to:
according to historical access data of a client, calculating the access quantity and the access duration of each URL classification, and thus calculating the access frequency score of each URL classification;
calculating the updating frequency of each URL classification according to the historical synchronous data of the client, so as to calculate the updating frequency score of each URL classification;
calculating the security level score of each URL classification according to the security level attribute of each URL classification;
calculating the number of URLs contained in each URL classification according to the URLs contained in each URL classification;
and respectively calculating the synchronization strategy of each URL classification based on the access frequency score, the update frequency score, the security level score and the number of the contained URLs of each URL classification.
Optionally, the calculating module 502 is further configured to:
based on the access frequency scores, the updating frequency scores, the safety level scores and the weights corresponding to the contained URL numbers, carrying out weighted summation on the access frequency scores, the updating frequency scores, the safety level scores and the contained URL numbers of the URL classifications to obtain synchronous scores of the URL classifications;
matching a corresponding synchronization strategy of each URL classification according to the synchronization score of each URL classification; the synchronization strategy comprises a synchronization mode, a synchronization frequency, a synchronization starting time, a synchronization ending time and a synchronization interval time in each synchronization process.
Optionally, the synchronization module 503 is further configured to:
for each URL classification, obtaining a version number of the URL classification from the server using the authorization token based on a synchronization policy of the URL classification;
judging whether the version number of the URL classification acquired from the server side is higher than the version number of the URL classification local to the client side;
if yes, based on the synchronous strategy of the URL classification, the authorization token is used for obtaining the data of the URL classification from the server side;
if not, the process is ended.
Optionally, the synchronization module 503 is further configured to:
based on the synchronization policy of the URL classification, acquiring the total size of the URL classified data from the server by using the authorization token;
dividing the data classified by the URL into a plurality of fragments according to the total size of the data classified by the URL;
and acquiring the URL classified data from the server side by using the authorization token piece by piece until the last piece.
According to the various embodiments, it can be seen that the embodiment of the present invention respectively calculates the synchronization policy of each URL classification according to the historical access data, the historical synchronization data of the client and the attribute characteristics of each URL classification, so that the technical means of obtaining the URL classification data from the server by using the authorization token based on the synchronization policy of each URL classification solves the technical problems of large network broadband consumption or large resource occupation in the prior art. The embodiment of the invention ensures the communication and data security by a perfect security authentication mechanism and various means of certificate public key, license and initial key signature, respectively calculates the synchronous strategy of each URL classification according to the historical access data, the historical synchronous data and the attribute characteristics of each URL classification of the client, and synchronizes the URL classified data based on the synchronous strategy, thereby overcoming the defect of a single synchronous mode, not only safely and quickly synchronizing the data, but also reducing the occupation of the system resources of the client, and further improving the integral stability of the system.
It should be noted that, in the implementation of the apparatus for synchronizing URL classification data according to the present invention, the above-mentioned method for synchronizing URL classification data has been described in detail, and therefore, the repeated description is omitted here.
Fig. 6 illustrates an exemplary system architecture 600 of a method of synchronizing URL classification data or an apparatus for synchronizing URL classification data to which embodiments of the present invention may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. The terminal devices 601, 602, 603 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 601, 602, 603. The background management server may analyze and otherwise process the received data such as the item information query request, and feed back a processing result (for example, target push information, item information — just an example) to the terminal device.
It should be noted that the method for synchronizing URL classification data provided by the embodiment of the present invention may be executed by the terminal devices 601, 602, 603, and accordingly, the apparatus for synchronizing URL classification data may be disposed in the terminal devices 601, 602, 603.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer programs according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes an acquisition module, a computation module, and a synchronization module, where the names of the modules do not in some cases constitute a limitation on the modules themselves.
As another aspect, the present invention also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, implement the method of: sending an authentication request to a server to obtain an authorization token; respectively calculating the synchronization strategy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client; and acquiring URL classification data from the server side by using the authorization token based on the synchronization policy of each URL classification.
According to the technical scheme of the embodiment of the invention, the synchronization strategy of each URL classification is respectively calculated according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client, so that the technical means of acquiring the URL classification data from the server by using the authorization token based on the synchronization strategy of each URL classification is adopted, and the technical problems of high network broadband consumption or large resource occupation in the prior art are solved. The embodiment of the invention ensures the communication and data security by a perfect security authentication mechanism and a plurality of means of certificate public key, license and initial key signature, respectively calculates the synchronization strategy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client, synchronizes the URL classification data based on the synchronization strategy, solves the defect of a single synchronization mode, can safely and quickly synchronize the data, and can reduce the occupation of the system resources of the client, thereby improving the overall stability of the system.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (9)

1. A method of synchronizing URL classification data, comprising:
sending an authentication request to a server to obtain an authorization token;
respectively calculating the synchronization strategy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client;
based on the synchronous strategy of each URL classification, acquiring URL classification data from the server side by using the authorization token;
wherein, sending an authentication request to a server to obtain an authorization token comprises:
sending a first authentication request carrying a first authentication parameter to a server so that the server verifies the first authentication parameter; the first authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number and the code of a first initial key;
receiving a second random number returned by the server to verify the digit of the second random number;
if the verification is passed, sending a second authentication request carrying a second authentication parameter to the server so that the server verifies the second authentication parameter; the second authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number, a second random number and the code of a second initial key;
and receiving the authorization token returned by the server.
2. The method of claim 1, wherein the device information comprises a device identification and a device type;
the first initial key is: taking the device information, the serial number of the license and the first random number as messages, and signing the messages through a built-in fixed key to obtain a character string;
the second initial key is: and taking the device information, the serial number of the license, the first random number and the second random number as messages, and signing the messages through a built-in fixed key to obtain a character string.
3. The method of claim 1, wherein calculating the synchronization policy of each URL classification according to the historical access data, the historical synchronization data and the attribute characteristics of each URL classification of the client respectively comprises:
according to historical access data of a client, calculating the access quantity and the access duration of each URL classification, and thus calculating the access frequency score of each URL classification;
calculating the updating frequency of each URL classification according to the historical synchronous data of the client, so as to calculate the updating frequency score of each URL classification;
calculating the security level score of each URL classification according to the security level attribute of each URL classification;
calculating the number of URLs contained in each URL classification according to the URLs contained in each URL classification;
and respectively calculating the synchronization strategy of each URL classification based on the access frequency score, the update frequency score, the security level score and the number of the contained URLs of each URL classification.
4. The method of claim 3, wherein calculating the synchronization policy for each URL classification based on the visit frequency score, update frequency score, security level score, and number of URLs included in each URL classification comprises:
based on the access frequency scores, the updating frequency scores, the safety level scores and the weights corresponding to the contained URL numbers, carrying out weighted summation on the access frequency scores, the updating frequency scores, the safety level scores and the contained URL numbers of the URL classifications to obtain synchronous scores of the URL classifications;
matching a corresponding synchronization strategy of each URL classification according to the synchronization score of each URL classification; the synchronization strategy comprises a synchronization mode, a synchronization frequency, a synchronization start time, a synchronization end time and a synchronization interval time in each synchronization process.
5. The method of claim 1, wherein obtaining URL classification data from the server using the authorization token based on a synchronization policy for each of the URL classifications comprises:
for each URL classification, obtaining a version number of the URL classification from the server using the authorization token based on a synchronization policy of the URL classification;
judging whether the version number of the URL classification acquired from the server side is higher than the version number of the URL classification local to the client side;
if yes, based on the URL classified synchronization strategy, the authorization token is used for acquiring the URL classified data from the server side;
if not, the process is ended.
6. The method of claim 5, wherein obtaining the URL-categorized data from the server using the authorization token based on the URL-categorized synchronization policy comprises:
based on the synchronization policy of the URL classification, acquiring the total size of the URL classified data from the server by using the authorization token;
dividing the data classified by the URL into a plurality of fragments according to the total size of the data classified by the URL;
and acquiring the URL classified data from the server side by using the authorization token piece by piece until the last piece.
7. An apparatus for synchronizing URL classification data, comprising:
the acquisition module is used for sending an authentication request to the server to acquire an authorization token;
the calculation module is used for respectively calculating the synchronization strategies of all the URL classifications according to the historical access data, the historical synchronization data and the attribute characteristics of all the URL classifications of the client;
a synchronization module, configured to obtain URL classification data from the server using the authorization token based on a synchronization policy of each URL classification;
wherein the obtaining module is further configured to:
sending a first authentication request carrying a first authentication parameter to a server so that the server verifies the first authentication parameter; the first authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number and the code of a first initial key;
receiving a second random number returned by the server to verify the digit of the second random number;
if the verification is passed, sending a second authentication request carrying a second authentication parameter to the server so that the server verifies the second authentication parameter; the second authentication parameter comprises equipment information of the client, the code of a certificate public key, the serial number of a license, a first random number, a second random number and the code of a second initial key;
and receiving the authorization token returned by the server.
8. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
the one or more programs, when executed by the one or more processors, implement the method of any of claims 1-6.
9. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-6.
CN202010630843.5A 2020-07-03 2020-07-03 Method and device for synchronizing URL classification data Active CN111865576B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010630843.5A CN111865576B (en) 2020-07-03 2020-07-03 Method and device for synchronizing URL classification data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010630843.5A CN111865576B (en) 2020-07-03 2020-07-03 Method and device for synchronizing URL classification data

Publications (2)

Publication Number Publication Date
CN111865576A CN111865576A (en) 2020-10-30
CN111865576B true CN111865576B (en) 2023-02-28

Family

ID=73153312

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010630843.5A Active CN111865576B (en) 2020-07-03 2020-07-03 Method and device for synchronizing URL classification data

Country Status (1)

Country Link
CN (1) CN111865576B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113904803B (en) * 2021-09-06 2023-09-08 河南信大网御科技有限公司 Service processing method and system based on mimicry defense

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104010231A (en) * 2014-04-30 2014-08-27 小米科技有限责任公司 Data synchronizing method and device
CN105631056A (en) * 2016-03-24 2016-06-01 北京奇虎科技有限公司 Advertisement flow filtering method and device and server
CN107103067A (en) * 2017-04-18 2017-08-29 北京思特奇信息技术股份有限公司 A kind of method of data synchronization and system based on search engine
CN110263574A (en) * 2019-06-06 2019-09-20 深圳前海微众银行股份有限公司 Data managing method, device, system and readable storage medium storing program for executing

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9736126B2 (en) * 2014-12-04 2017-08-15 International Business Machines Corporation Authenticating mobile applications using policy files

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104010231A (en) * 2014-04-30 2014-08-27 小米科技有限责任公司 Data synchronizing method and device
CN105631056A (en) * 2016-03-24 2016-06-01 北京奇虎科技有限公司 Advertisement flow filtering method and device and server
CN107103067A (en) * 2017-04-18 2017-08-29 北京思特奇信息技术股份有限公司 A kind of method of data synchronization and system based on search engine
CN110263574A (en) * 2019-06-06 2019-09-20 深圳前海微众银行股份有限公司 Data managing method, device, system and readable storage medium storing program for executing

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
面向用户体验的大型网站网页分类更新策略;欧阳柳波等;《华中科技大学学报(自然科学版)》;20100915(第09期);第1-3节 *

Also Published As

Publication number Publication date
CN111865576A (en) 2020-10-30

Similar Documents

Publication Publication Date Title
CN110019211A (en) The methods, devices and systems of association index
US10547618B2 (en) Method and apparatus for setting access privilege, server and storage medium
CN109784058A (en) Version strong consistency method of calibration, client, server and storage medium
CN109564527A (en) The security configuration of cloud computing node
CN105472045A (en) Database migration method and database migration device
CN112527649A (en) Test case generation method and device
CN107844488B (en) Data query method and device
CN109918191A (en) A kind of method and apparatus of the anti-frequency of service request
CN115344841A (en) Meta-universe access method based on block chain network and block chain network device
CN110909022A (en) Data query method and device
CN111865576B (en) Method and device for synchronizing URL classification data
CN113761565B (en) Data desensitization method and device
CN112650804B (en) Big data access method, device, system and storage medium
CN110928594A (en) Service development method and platform
US10764399B2 (en) Customized web services gateway
CN107634942B (en) Method and device for identifying malicious request
CN115423030A (en) Equipment identification method and device
CN113824675B (en) Method and device for managing login state
CN110705935B (en) Logistics document processing method and device
CN113114611B (en) Blacklist management method and device
CN113626472A (en) Method and device for processing order data
CN109657481B (en) Data management method and device
CN110019671B (en) Method and system for processing real-time message
CN109087097B (en) Method and device for updating same identifier of chain code
CN112732789A (en) Searchable encryption method based on block chain 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
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20210319

Address after: 100176 8660, 6 / F, building 3, No.3, Yongchang North Road, Beijing Economic and Technological Development Zone, Daxing District, Beijing

Applicant after: BEIJING SKYGUARD NETWORK SECURITY TECHNOLOGY Co.,Ltd.

Applicant after: Chengdu sky guard Network Security Technology Co.,Ltd.

Address before: 100176 8660, 6 / F, building 3, No.3, Yongchang North Road, Beijing Economic and Technological Development Zone, Beijing

Applicant before: BEIJING SKYGUARD NETWORK SECURITY TECHNOLOGY Co.,Ltd.

GR01 Patent grant
GR01 Patent grant