CN114760270A - Method and device for generating user equipment fingerprint - Google Patents
Method and device for generating user equipment fingerprint Download PDFInfo
- Publication number
- CN114760270A CN114760270A CN202110516342.9A CN202110516342A CN114760270A CN 114760270 A CN114760270 A CN 114760270A CN 202110516342 A CN202110516342 A CN 202110516342A CN 114760270 A CN114760270 A CN 114760270A
- Authority
- CN
- China
- Prior art keywords
- address
- client
- url
- fingerprint
- user equipment
- 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.)
- Granted
Links
Images
Classifications
-
- 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]
-
- 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1036—Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The method generates the user equipment fingerprint according to the IP address obtained by analyzing the URL in the process that a DNS is accessed, and the URL can be analyzed into different IP addresses even if different hardware equipment installed by using a standard mirror image accesses the DNS, and further, because the IP address analyzed by each URL is unchanged before the expiration of a cache, the IP address sequence analyzed by accessing the URLs is also kept unchanged before the expiration of the cache, and the user equipment fingerprint generated by the method can realize accurate user tracking.
Description
Technical Field
The present application relates to the field of internet, and in particular, to a method and an apparatus for generating a user equipment fingerprint.
Background
With the wide application of user equipment fingerprint technology in various fields, tracking technology based on user equipment fingerprints has become very popular. Tracking technology is used to identify users across websites and sessions (sessions), the two broadest application areas of which are personalized advertising and monitoring, and thus websites and third party companies are the most entities using this technology.
The most common methods of tracking technology include both tagging and fingerprinting, where the tagging tracking method is to store certain information on the user's device, which is a software device, such as a cookie or the like, for subsequent tracking, but modern browsers allow the user to refuse tagging, and the added tag only works for a particular application or browser, and is not valid for other browsers and applications on the same hardware device used by the same user, and is also not valid for the browser's privacy mode.
Another tracking method, i.e., fingerprinting, is a method of tracking a user by surveying characteristics of the user's machine, application, and browser (such as font), but since different machines installed using standard images produce the same device fingerprint, accurate identification cannot be made to different users on different machines installed using standard images, and user tracking cannot be achieved.
Disclosure of Invention
In order to make up for the defects of the prior tracking technology (such as tracking a machine loaded with a standard mirror image), the method and the device for generating the user equipment fingerprint are provided, the method generates the user equipment fingerprint according to an Internet Protocol (IP) address obtained by analyzing a Uniform Resource Locator (URL) by a Domain Name System (DNS) in an accessing process, and the URL can be analyzed into different IP addresses even if different hardware devices installed by using the standard mirror image access the DNS.
The purpose of this application is to provide the following aspects:
in a first aspect, the present application provides a method for generating a user equipment fingerprint, the method comprising:
the client initiates sequential access to a plurality of different preset URLs;
the client sends a parsing request to a Stub parser (Stub Resolver) according to the access to the preset URL;
the stub resolver feeds back an IP address corresponding to the URL according to the resolution request;
the client side obtains the searched IP address;
and the client generates a user equipment fingerprint according to the IP address.
In one example, the stub parser feeding back the IP address corresponding to the URL according to the parsing request may include: and the stub resolver searches an IP address corresponding to the URL in a cache set according to the resolution request, wherein the cache set is composed of all cache devices between an operating system cache and a DNS cache.
Optionally, the finding, by the stub parser, the IP address corresponding to the URL in the cache set according to the parsing request includes:
caching all the caching devices in the cache set from an operating system to a DNS cache according to the site sequence and sequencing in sequence;
and sequentially searching the IP addresses corresponding to the URLs in the cache set.
In another example, the stub parser feeding back the IP address corresponding to the URL according to the parsing request may further include:
and the DNS system randomly resolves and generates an IP address from a plurality of IP addresses corresponding to each URL according to the resolving request.
In this implementation manner, after the DNS system randomly resolves and generates one IP address from a plurality of IP addresses corresponding to each URL according to the resolution request, the method may further include:
the client acquires cookie information carried by a preset URL;
the client sends the cookie information to a back-end server;
the back-end server searches historical cookie information in a database;
and if the historical cookie information is found in the database, establishing a link between the IP address and the IP address in the historical cookie information.
In one implementation, the IP addresses obtained by the client are cached in the cache set.
Optionally, the client generating the user equipment fingerprint according to the IP address may include:
the client sends an HTTP request to an API server corresponding to the IP address;
the client acquires the character strings replied by the servers;
The client arranges all the character strings replied by all the servers in sequence to generate fingerprint character strings;
and the client generates the user equipment fingerprint, and the user equipment fingerprint is obtained by carrying out hash processing on the fingerprint character string.
Further, the client arranges all the character strings replied by all the servers in sequence to generate the fingerprint character strings, and may arrange the fingerprint character strings according to a preset sequence, for example, according to the number of each server, the fingerprint character strings are arranged in an ascending order or a descending order of the server numbers.
In a second aspect, the present application further provides an apparatus for generating a user equipment fingerprint, the apparatus including:
the client is used for initiating sequential access to a plurality of different preset URLs;
the client is also used for sending a parsing request to a Stub parser (Stub Resolver) according to the access to the preset URL;
the stub resolver is used for feeding back the IP address corresponding to the URL according to the resolution request;
the client is also used for acquiring the searched IP address;
the client is also used for generating user equipment fingerprints according to the IP addresses.
In a third aspect, the present application further provides a program for generating a user equipment fingerprint, where the program is configured to implement the steps of the method for generating a user equipment fingerprint according to the first aspect when executed.
In a fourth aspect, a computer readable storage medium has stored thereon computer instructions which, when executed by a processor, implement the steps of the method for generating a user equipment fingerprint according to the first aspect.
In a fifth aspect, an apparatus for generating a user device fingerprint, the apparatus comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method of generating a user equipment fingerprint of the first aspect.
Compared with the prior art, the method provided by the application has the advantages that a plurality of IP addresses are configured for each URL, one IP address can be obtained through random resolution when the URL is visited, a group of specific sequence combinations formed by the IP addresses are obtained through visiting a plurality of different URLs, and the IP address sequences are used as fingerprints, so that the requests sent from any application and browser on the same machine can be identified. The client temporarily stores the IP address of each URL analyzed by the DNS in each level of cache within a certain time, and the IP address analyzed by each URL is unchanged before the cache expires, so that the IP address sequence cached before the cache expires is kept unchanged, the fingerprint of the user equipment is kept unchanged, and the efficiency can be improved and the load of a DNS system can be reduced by using the cached IP address sequence.
Drawings
FIG. 1 is a schematic diagram illustrating a usage scenario of the present application;
fig. 2 shows a flowchart of a method for generating a user device fingerprint according to the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present invention. Rather, they are merely examples of methods consistent with certain aspects of the invention, as detailed in the appended claims.
The method and apparatus for generating a user equipment fingerprint provided by the present application are described in detail by specific embodiments below.
First, a use scenario of the present solution is briefly introduced.
Fig. 1 is a schematic view illustrating a usage scenario of the present application, as shown in fig. 1, the present application is applied to user tracking, and related hardware devices at least include a user terminal device, a WEB server, and a DNS system, where the user terminal device and the WEB server and the DNS system may communicate with each other respectively.
The WEB server comprises a response value generation server and a data receiving server, wherein the response value generation server is used for generating a response value and returning the generated response value to the user terminal equipment, and the data receiving server is used for receiving the user equipment fingerprint sent by the user terminal equipment.
In this application, software with a user tracking requirement, for example, some APP or some browser, etc., is installed on the user terminal device, and a program for executing the method of the present application, that is, a tracking program, is loaded in the software with a user tracking requirement, for example, may be loaded in Javascript on a client browser, and after the software is started, the tracking program is triggered to be started to calculate a user device fingerprint, and the tracking program is private. And the system is responsible for executing a calculation task and integrating the machine fingerprints, and reporting the generated machine fingerprints, cookie information and device fingerprints to a background machine fingerprint tracking server.
Further, a Stub Resolver (Stub Resolver) matched with the operating system of the user terminal device is also installed on the user terminal device and used for querying a DNS record in a local cache or forwarding a DNS request sent by the tracking program to the DNS system.
The present application utilizes the features of the DNS system to realize machine fingerprint identification, but the setting of the DNS system does not fall into the discussion scope of the present application.
In this application, the DNS system is used to resolve the IP address corresponding to the URL, and the DNS system includes a Recursive Resolver (DNS Recursive Resolver), a Root domain name server (Root Nameserver), a TLD (. com) Nameserver, and an authorative (. example.
It should be noted that, in this example, it is assumed that the DNS is configured with a lifetime, and during the lifetime, the resolved IP address is returned as a result; if the life cycle expires, the resolved IP address is removed from the cache.
In particular, the lifetime of the DNS may vary from a few minutes to a week, depending on the setting, and is typically selected to be in the range of 5 minutes to a week.
In the present application, the WEB server, i.e. the API server, is configured to service the HTTP request and reply a value represented by the API, which is described in detail in the following description.
And the back-end fingerprint tracking server module is used for receiving the data reported by the front end and associating the fingerprint of the related user equipment.
For the purpose of illustrating the technical solution of the present application, the following assumptions are made in the following examples:
There are three preset URLs, x1.example.com, x2.example.com and x3. example.com. Each URL corresponds to five API servers, and thus each URL may be resolved to an IP address of any one of its corresponding five API servers, and each IP address provides a unique response value.
For example, x1.example. com corresponds to a first IP address of 10.1.1.1 with a response value of 1, a second IP address of 10.1.1.2 with a response value of 2, a third IP address of 10.1.1.3 with a response value of 3, a fourth IP address of 10.1.1.4 with a response value of 4, and a fifth IP address of 10.1.1.5 with a response value of 5; the five IP addresses corresponding to x2.example.com are the same as the five IP addresses corresponding to x1.example.com, and the response values are also respectively the same; the five IP addresses corresponding to x3.example.com are the same as the five IP addresses corresponding to x1.example.com, and the response values are also respectively the same.
As can be seen from the above example, if a URL corresponds to multiple IP addresses, the resolved IP address is one of these IP addresses, and the selection of which IP address depends on the configuration of the DNS, a common method is Round robin, and if many users access the same page, the same fingerprint may be generated by different user devices.
It can be understood that the number of fingerprint combination modes NFingerThis can be expressed by the following formula:
Nfinger＝(NU)N clothes
Wherein, NUIndicating the number of visited URLs; n is a radical ofGarmentIndicating the number of servers.
Therefore, the conflict of the machine fingerprints can be reduced by increasing the times of accessing different URLs or increasing the number of IP addresses (API servers) corresponding to the URLs. The above example is taken as an example, the combination mode of the user equipment fingerprints is 3 in total5243 kinds. If 10 URLs are preset and each URL is provided with 10 corresponding servers, the combination of user equipment fingerprints will rise to 1010100 hundred million. Therefore, the more URLs that are pre-set for access, the lower the likelihood of fingerprint collisions; the greater the number of IP addresses per URL, the lower the likelihood of fingerprint collisions. Therefore, the scheme provided by the application can achieve reasonable balance between machine fingerprint conflict and equipment overhead by adjusting the number of the preset accessed URLs and/or the number of the servers corresponding to each URL.
Fig. 2 shows a flowchart of a method for generating a user device fingerprint, as shown in fig. 2, the method includes the following steps S101 to S105:
step S101, the client initiates sequential access to a plurality of different preset URLs.
After a user triggers a client to perform a related operation, for example, after starting an APP to browse, in this example, the client starts the tracking program at the same time as the APP loaded with the tracking program, and after the tracking program is triggered, firstly, accesses are sequentially initiated to all preset URLs, and an access sequence may be preset.
In this example, the client initiates accesses to the three URLs in order, which is, in turn, x1.example.com, x2.example.com, and x3. example.com.
Step S102, the client sends a parsing request to a Stub parser (Stub Resolver) according to the access to the preset URL.
In this example, the parsing requests sent to the stub parser may be sent one by one in sequence, or may be sent in batches.
And step S103, the stub resolver feeds back the IP address corresponding to the URL according to the resolution request.
In this example, the way the stub resolver obtains the IP address corresponding to the URL includes at least the following two ways:
firstly, searching corresponding IP addresses in each level of cache; the second is to randomly select an IP address from a set of IP addresses.
The following describes two ways of obtaining IP addresses:
In the first approach, the finding of the corresponding IP address in each level of cache may include:
and the stub resolver searches an IP address corresponding to the URL in the cache set according to the resolution request.
In this example, the cache set is composed of all cache devices between the operating system cache and the DNS cache, for example, the operating system cache and the DNS cache.
Further, the step of the stub parser searching the IP address corresponding to the URL in the cache set according to the parsing request includes:
sequencing all the cache devices in the cache set in sequence according to a preset sequence;
and sequentially searching the IP address corresponding to the URL in each caching device of the caching set.
In this example, the predetermined sequence of the cache devices may be
Continuing with the above example as an example, if a page is refreshed or revisited, the client will again visit x1.example.com, x2.example.com, and x3.example.com in sequence. The client sends an analysis request to Stub Resolver, and the Stub Resolver queries the cache step by step (including the cache of Stub Resolver and the secure Resolver), finds that there is a corresponding IP address 10.1.1.1, and the IP address is returned as a result of the request, and the client accesses the IP address to obtain a response result value 1. By analogy, the responses obtained by the client from x2.example.com and x3.example.com are value 2 and value 3, respectively, and thus the fingerprint of the user machine remains 123.
In the second approach, the IP address records stored in the cache devices at different levels are cleared after the DNS TTL expires, so that the same URL needs to be re-resolved, that is, an IP address is randomly selected from a set of IP addresses, and the stub resolver may feed back the IP address corresponding to the URL according to the resolution request, where the step of:
and the DNS system randomly resolves and generates an IP address from a plurality of IP addresses corresponding to each URL according to the resolving request.
Continuing with the above example, if the client accesses x1.example. com, the client sends a resolution request to Stub resolve, which continues to send the request to the DNS system, which returns a query result according to the configured rule, where the query result includes the resolved IP address, i.e. one of five IP addresses (10.1.1.1, 10.1.1.2, 10.1.1.3, 10.1.1.4, 10.1.1.5), in this example, it is assumed that the resolved IP address is 10.1.1.1, and the IP addresses are stored in the caches of secure resolve and Stub Server, respectively, for query use.
It will be appreciated that the IP address resulting from the reparse of the same URL is likely to be different from the previous resolution, which will result in different user device fingerprints being generated by the same client, how to associate the two different user device fingerprints? The application uses cookies as a bridge to join two user device fingerprints.
Therefore, after the IP address is cleared, the corresponding IP address can be found according to the cookie information, and it can be understood that the corresponding IP address can also be found according to the cookie information when the IP address is not cleared.
Specifically, the method of joining two user device fingerprints using a cookie may include steps S301 to S304:
step S301, a client acquires cookie information carried by a preset URL;
step S302, the client sends the cookie information to a back-end server;
step S303, the back-end server searches for historical cookie information in a database, for example, the historical cookie information may be a relational database;
step S304, if the historical cookie information is found in the database, the IP address is linked with the IP address in the historical cookie information.
The applicant finds that the cookie is used as an index to query the user equipment fingerprint related to the cookie, and then sequentially queries the database, if the user equipment fingerprint record is found, the user equipment fingerprint record can be used as a query result of the initial user equipment fingerprint, so that the user equipment fingerprints which belong to the same user equipment but are different due to the fact that the IP address is expired in the cache are associated, and the uniqueness of the user equipment fingerprint is guaranteed.
To increase reliability and reduce errors, we use device fingerprints in addition to cookies, which include attributes of the client hardware device and attributes of the browser, such as machine core number, memory capacity, and User Agent, etc., thus ensuring that we can still potentially associate two machine fingerprints when a cookie is deleted.
In this example, the IP address acquired by the client each time is cached in each level of cache for subsequent query.
And step S104, the client acquires the searched IP address.
And step S105, the client generates a user equipment fingerprint according to the IP address.
Optionally, this step may include:
the client sends an HTTP request to an API server corresponding to the IP address;
the client acquires the character strings replied by the API servers;
the client arranges all the character strings replied by all the servers in sequence to generate fingerprint character strings;
and the client generates the user equipment fingerprint, and the user equipment fingerprint is obtained by carrying out hash processing on the fingerprint character string.
Further, the client arranges all the character strings replied by all the servers in sequence to generate the fingerprint character strings, and the fingerprint character strings can be arranged according to a preset sequence.
In this example, after obtaining the IP address corresponding to the URL, the client sends the HTTP request to the API server corresponding to the IP address, and the API server replies a character string, that is, a response value.
Taking the above example as an example, after obtaining the IP address (10.1.1.1) corresponding to the URL, the client sends the HTTP request to the API server with the IP address of 10.1.1.1, and the API server replies with a response value of 1 after receiving the HTTP request.
The client then continues to access x2.example.com and x3.example.com in sequence, assuming that the resulting IP addresses are 10.1.1.2 and 10.1.1.3, respectively, and accordingly accesses the corresponding APIs in sequence, resulting in response values of value 2 and value 3, respectively.
The client can calculate that the user device fingerprint FP of the current device is 123 according to the information, and sends the fingerprint back to the WEB server data receiving server, and the data receiving server receives the information such as the user device fingerprint and the like, but does not send a response value to the user device.
In a second aspect, the present application further provides an apparatus for generating a user equipment fingerprint, the apparatus comprising:
the client is used for initiating sequential access to a plurality of different preset URLs;
the client is also used for sending a parsing request to a Stub parser (Stub Resolver) according to the access to the preset URL;
The stub resolver is used for feeding back the IP address corresponding to the URL according to the resolution request;
the client is also used for acquiring the searched IP address;
the client is also used for generating user equipment fingerprints according to the IP addresses.
In one example, the stub resolver is further configured to search for an IP address corresponding to the URL in a cache set according to the resolution request, where the cache set is formed by all cache devices between an operating system cache and a DNS cache.
In another example, the stub parser may be further specifically configured to:
and the DNS system randomly resolves and generates an IP address from a plurality of IP addresses corresponding to each URL according to the resolving request.
In the manner that can be achieved in the present implementation,
the client side can also be used for acquiring cookie information carried by the preset URL;
the client side can also be used for sending the cookie information to a back-end server;
the back-end server can also search historical cookie information in a database;
and if the historical cookie information is found in the database, establishing a link between the IP address and the IP address in the historical cookie information.
In one implementation, the IP addresses obtained by the client are cached in the cache set.
Optionally, the client may be further configured to send an HTTP request to an API server corresponding to the IP address;
the client can also be used for acquiring character strings replied by the servers;
the client can also be used for arranging all the character strings replied by all the servers in sequence to generate fingerprint character strings;
the client may be further configured to generate the user equipment fingerprint, where the user equipment fingerprint is obtained by performing hash processing on the fingerprint character string.
Further, the client arranges all the character strings replied by all the servers in sequence to generate the fingerprint character strings, and the fingerprint character strings can be arranged according to a preset sequence.
In a third aspect, the present application further provides a program for generating a user equipment fingerprint, where the program is configured to implement the steps of the method for generating a user equipment fingerprint according to the first aspect when executed.
In a fourth aspect, a computer readable storage medium has stored thereon computer instructions which, when executed by a processor, implement the steps of the method for generating a user equipment fingerprint according to the first aspect.
In a fifth aspect, an apparatus for generating a user device fingerprint, the apparatus comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method of generating a user equipment fingerprint of the first aspect.
The scheme can identify the cross-application and browser method on the same machine, the scheme combines the working characteristics of the existing DNS system, if one URL corresponds to a plurality of IP addresses, the URL can be analyzed into different IP addresses each time when the URL is accessed, if a group of URLs are accessed, a group of analyzed unique IP address sequences can be obtained, and the user equipment fingerprint generated by the method can realize accurate user tracking.
The present application has been described in detail with reference to particular embodiments and illustrative examples, but the description is not intended to be construed as limiting the application. Those skilled in the art will appreciate that various equivalent substitutions, modifications or improvements may be made to the embodiments and implementations thereof without departing from the spirit and scope of the present application, and are within the scope of the present application. The protection scope of this application is subject to the appended claims.
Claims (10)
1. A method of generating a user device fingerprint, the method comprising:
the client initiates sequential access to a plurality of different preset URLs;
the client sends a parsing request to a Stub parser (Stub Resolver) according to the access to the preset URL;
The stub resolver feeds back an IP address corresponding to the URL according to the resolution request;
the client side obtains the searched IP address;
and the client generates a user equipment fingerprint according to the IP address.
2. The method of claim 1, wherein the stub parser feeding back an IP address corresponding to the URL according to the parsing request comprises: and the stub resolver searches an IP address corresponding to the URL in a cache set according to the resolution request, wherein the cache set is composed of all cache devices between an operating system cache and a DNS cache.
3. The method of claim 1 or 2, wherein the stub resolver, according to the resolution request, looking up the IP address corresponding to the URL in the cache set comprises:
all caching devices in the cache set are sequentially sorted from the operating system cache to the DNS cache according to the site sequence;
and sequentially searching the IP addresses corresponding to the URLs in the cache set.
4. The method of any of claims 1 to 3, wherein the stub parser feeds back the IP address corresponding to the URL according to the parsing request further comprises:
and the DNS system randomly resolves and generates an IP address from a plurality of IP addresses corresponding to each URL according to the resolving request.
5. The method according to any one of claims 1 to 4, wherein after the DNS system randomly resolves and generates one IP address from the plurality of IP addresses corresponding to each URL according to the resolution request, the method further comprises:
the client acquires cookie information carried by a preset URL;
the client sends the cookie information to a back-end server;
the back-end server searches historical cookie information in a database;
and if the historical cookie information is found in the database, establishing a link between the IP address and the IP address in the historical cookie information.
6. The method of any of claims 1 to 5, wherein the client generating a user device fingerprint from the IP address comprises:
the client sends an HTTP request to an API server corresponding to the IP address;
the client acquires the character strings replied by the servers;
the client arranges all the character strings replied by all the servers in sequence to generate fingerprint character strings;
and the client generates the user equipment fingerprint, and the user equipment fingerprint is obtained by carrying out hash processing on the fingerprint character string.
7. An apparatus for generating a user device fingerprint, the apparatus comprising:
The client is used for initiating sequential access to a plurality of different preset URLs;
the client is also used for sending a parsing request to a Stub parser (Stub Resolver) according to the access to the preset URL;
the stub parser is used for feeding back the IP address corresponding to the URL according to the parsing request;
the client is also used for acquiring the searched IP address;
the client is also used for generating user equipment fingerprints according to the IP addresses.
8. A program for generating a fingerprint of a user equipment, characterized in that the program is adapted to perform the steps of the method for generating a fingerprint of a user equipment as claimed in any one of claims 1 to 6 when executed.
9. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method of generating a user device fingerprint according to any one of claims 1 to 6.
10. An apparatus for generating a user device fingerprint, the apparatus comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method of generating a user device fingerprint of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110516342.9A CN114760270B (en) | 2021-05-12 | 2021-05-12 | Method and device for generating user equipment fingerprint |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110516342.9A CN114760270B (en) | 2021-05-12 | 2021-05-12 | Method and device for generating user equipment fingerprint |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114760270A true CN114760270A (en) | 2022-07-15 |
| CN114760270B CN114760270B (en) | 2023-09-22 |
Family
ID=82325195
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110516342.9A Active CN114760270B (en) | 2021-05-12 | 2021-05-12 | Method and device for generating user equipment fingerprint |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114760270B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080184029A1 (en) * | 2007-01-30 | 2008-07-31 | Sims John B | Method and system for generating digital fingerprint |
| US20150143398A1 (en) * | 2012-05-03 | 2015-05-21 | Enswers Co., Ltd. | System and Method for Providing Image-Based Video Service |
| EP2975547A1 (en) * | 2014-07-17 | 2016-01-20 | Electronics and Telecommunications Research Institute | Method and apparatus for preventing illegitimate outflow of electronic document |
| US20180019961A1 (en) * | 2015-12-18 | 2018-01-18 | Tencent Technology (Shenzhen) Company Limited | Message processing method, processing server, terminal, and storage medium |
| CN107679575A (en) * | 2017-10-10 | 2018-02-09 | 小花互联网金融服务（深圳）有限公司 | A kind of real-time device fingerprint acquisition device based on user |
| CN108804908A (en) * | 2017-05-04 | 2018-11-13 | 腾讯科技（深圳）有限公司 | A kind of device-fingerprint generation method, device and computing device |
| CN109818906A (en) * | 2017-11-21 | 2019-05-28 | 深圳市腾讯计算机系统有限公司 | A kind of device-fingerprint information processing method, device and server |
| CN110866286A (en) * | 2019-10-29 | 2020-03-06 | 武汉极意网络科技有限公司 | Equipment fingerprint generation method and device |
| CN111698082A (en) * | 2020-05-29 | 2020-09-22 | 成都新希望金融信息有限公司 | Method for generating fingerprint identification of hybrid terminal equipment based on JS |
-
2021
- 2021-05-12 CN CN202110516342.9A patent/CN114760270B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080184029A1 (en) * | 2007-01-30 | 2008-07-31 | Sims John B | Method and system for generating digital fingerprint |
| US20150143398A1 (en) * | 2012-05-03 | 2015-05-21 | Enswers Co., Ltd. | System and Method for Providing Image-Based Video Service |
| EP2975547A1 (en) * | 2014-07-17 | 2016-01-20 | Electronics and Telecommunications Research Institute | Method and apparatus for preventing illegitimate outflow of electronic document |
| US20180019961A1 (en) * | 2015-12-18 | 2018-01-18 | Tencent Technology (Shenzhen) Company Limited | Message processing method, processing server, terminal, and storage medium |
| CN108804908A (en) * | 2017-05-04 | 2018-11-13 | 腾讯科技（深圳）有限公司 | A kind of device-fingerprint generation method, device and computing device |
| CN107679575A (en) * | 2017-10-10 | 2018-02-09 | 小花互联网金融服务（深圳）有限公司 | A kind of real-time device fingerprint acquisition device based on user |
| CN109818906A (en) * | 2017-11-21 | 2019-05-28 | 深圳市腾讯计算机系统有限公司 | A kind of device-fingerprint information processing method, device and server |
| CN110866286A (en) * | 2019-10-29 | 2020-03-06 | 武汉极意网络科技有限公司 | Equipment fingerprint generation method and device |
| CN111698082A (en) * | 2020-05-29 | 2020-09-22 | 成都新希望金融信息有限公司 | Method for generating fingerprint identification of hybrid terminal equipment based on JS |
Non-Patent Citations (3)
| Title |
|---|
| TOSHIKI SHIBAHARA等: ""Malicious URL sequence detection using event de-noising convolutional neural network"", 《2017 IEEE INTERNATIONAL CONFERENCE ON COMMUNICATIONS》 * |
| 程洋: ""基于设备指纹的物联网终端接入认证系统的研究与实现"", 《中国优秀硕士学位论文全文数据库》 * |
| 饶亲苗，彭艳兵: ""基于DPI的应用指纹自动提取方法研究"", 《计算机应用与软件》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114760270B (en) | 2023-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10999384B2 (en) | Method and system for identifying website visitors | |
| US10250526B2 (en) | Method and apparatus for increasing subresource loading speed | |
| CN108090064B (en) | Data query method and device, data storage server and system | |
| CN106657044B (en) | It is a kind of for improving the web page address jump method of web station system Prevention-Security | |
| US11044262B2 (en) | Method, apparatus and system for anti-attacking in domain name system (DNS) | |
| CN110430188B (en) | Rapid URL filtering method and device | |
| CN108574742B (en) | Domain name information collection method and domain name information collection device | |
| CN104580540B (en) | The implementation method and device of website visiting | |
| CN102624914A (en) | Method for detecting local DNS (Domain Name Server) used by client side in Web form | |
| CN114205330A (en) | Domain name resolution method, domain name resolution device, server, and storage medium | |
| WO2017166524A1 (en) | Domain name parsing method and apparatus | |
| CN113315852A (en) | Domain name resolution method, device and system | |
| CN113055503A (en) | IPv6 webpage link processing method, device, equipment and readable storage medium | |
| CN114760270B (en) | Method and device for generating user equipment fingerprint | |
| CN105530329B (en) | A kind of novel domain name resolution service method and apparatus for supporting name to search for | |
| CN109241483B (en) | Website discovery method and system based on domain name recommendation | |
| CN114338630B (en) | Domain name access method, device, electronic equipment, storage medium and program product | |
| JP6233846B2 (en) | Variable-length nonce generation | |
| US10333966B2 (en) | Quarantining an internet protocol address | |
| CN110944037B (en) | Method, computer device and storage medium for client cache change configuration | |
| EP3603026A1 (en) | Determining that multiple requests are received from a particular user device | |
| CN111064822B (en) | User tracking method and device and electronic equipment | |
| CN105760396A (en) | Webpage loading method and device | |
| US10659424B2 (en) | Determining status of domain name registration | |
| CN112714078A (en) | Network traffic identification method and device, storage medium and server |
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 |