CN114760270B - Method and device for generating user equipment fingerprint - Google Patents
Method and device for generating user equipment fingerprint Download PDFInfo
- Publication number
- CN114760270B CN114760270B CN202110516342.9A CN202110516342A CN114760270B CN 114760270 B CN114760270 B CN 114760270B CN 202110516342 A CN202110516342 A CN 202110516342A CN 114760270 B CN114760270 B CN 114760270B
- Authority
- CN
- China
- Prior art keywords
- address
- client
- fingerprint
- url
- 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.)
- Active
Links
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
Abstract
The application provides a method and a device for generating user equipment fingerprints, wherein the method generates the user equipment fingerprints according to the IP address obtained by analyzing the URL in the process of being accessed by a DNS, even if different hardware devices installed by using standard mirror images are used for analyzing the URL into different IP addresses in the process of accessing the DNS, further, because the IP address analyzed by each URL is unchanged before the expiration of a cache, the IP address sequence analyzed by the access URLs is also unchanged before the expiration of the cache, and the user equipment fingerprints generated by the method can realize accurate user tracking.
Description
Technical Field
The application belongs to the field of Internet, and particularly relates to a method and a device for generating a user equipment fingerprint.
Background
With the widespread use 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 in cross-web and cross-session (session), the two most widely used areas of which are personalized advertising and monitoring, and therefore web sites and third party companies are the most used entities for 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 a user's device, such as a software device, such as a cookie, for subsequent tracking, but modern browsers allow the user to reject tagging, and the added tag only works for a particular application or browser, and is not effective for other browsers and applications on the same hardware device for the same user, and in addition, is also ineffective for the privacy mode of the browser.
Another tracking method, fingerprint technology, is a method of tracking a user by surveying the characteristics of the user's machine, application, and browser (such as fonts), but since different machines installed using standard images produce the same device fingerprint, accurate identification cannot be made for different users on different machines installed using standard images, and thus 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 for loading standard images), the application provides a method and a device for generating user equipment fingerprints, wherein the method generates the user equipment fingerprints according to internet protocol (Internet Protocol, IP) addresses obtained by analyzing a uniform resource locator (Uniform Resource Locator, URL) in the accessed process by a domain name system (Domain Name System, DNS), even if different hardware devices installed by using the standard images are used for analyzing the URL into different IP addresses in the process of accessing the DNS, further, because the IP address analyzed by each URL is unchanged before the buffer expires, the IP address sequence analyzed by accessing URLs is also unchanged before the buffer expires, and the user equipment fingerprints generated by the method can realize accurate user tracking.
The application aims to provide the following aspects:
in a first aspect, the present application provides a method of generating a user equipment fingerprint, the method comprising:
the client initiates sequential access to a plurality of different preset URLs;
the client sends an analysis request to a Stub Resolver (Stub Resolver) according to access to a preset URL;
the stub parser feeds back the IP address corresponding to the URL according to the parsing request;
the client acquires 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 parse request may include: the stub parser searches the IP address corresponding to the URL in a cache set according to the parsing request, wherein the cache set is composed of all cache devices between an operating system cache and a DNS cache.
Optionally, the stub parser searches the cache set for the IP address corresponding to the URL according to the parse request includes:
all the cache devices in the cache set are sequentially ordered from the operation system cache to the DNS cache according to the site order;
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 parse request may further include:
and the DNS system randomly analyzes and generates an IP address from a plurality of IP addresses corresponding to each URL according to the analysis request.
In this implementation manner, after the DNS system randomly parses the plurality of IP addresses corresponding to each URL according to the parsing request to generate one IP address, 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 the historical cookie information in the database;
if the history cookie information is found in the database, the IP address is linked with the IP address in the history cookie information.
In one implementation, the IP addresses acquired by the client are all cached in the cache set.
Optionally, the generating, by the client, 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 character strings replied by the servers;
the client side sequentially arranges all character strings replied by all servers 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 may arrange all the strings replied by all the servers in order to generate the fingerprint strings according to a preset order, for example, according to the numbers of the servers in ascending order or descending order of the numbers of the servers.
In a second aspect, the present application also provides an apparatus for generating a fingerprint of a user equipment, the apparatus comprising:
the client is used for initiating sequential access to a plurality of different preset URLs;
the client is further used for sending an analysis request to a Stub Resolver (Stub Resolver) according to 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 a user equipment fingerprint according to the IP address.
In a third aspect, the present application also provides a program for generating a user equipment fingerprint, the program being adapted to implement the steps of the method for generating a user equipment fingerprint according to the first aspect.
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 fingerprint of a user equipment described in the first aspect.
In a fifth aspect, an apparatus for generating a user equipment 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 one processor to cause the at least one processor to perform the method of generating a user device fingerprint of the first aspect described above.
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 randomly resolved by accessing the IP address to obtain one IP address, a group of specific sequence combinations formed by the IP addresses are obtained by accessing 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. Because the client temporarily stores the IP address resolved by the DNS for each URL in each level of cache within a certain time, and the IP address resolved by each URL is unchanged before the cache is expired, the IP address sequence cached before the cache is expired is kept unchanged, so that the fingerprint of the user equipment is kept unchanged, and the efficiency can be improved and the DNS system load can be reduced by using the cached IP address sequence.
Drawings
FIG. 1 shows a schematic view of the use scenario of the inventive solution;
fig. 2 shows a flow chart of a method of generating a user device fingerprint according to the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of methods consistent with aspects of the application as detailed in the accompanying claims.
The method and the device for generating the user equipment fingerprint provided by the application are explained in detail below through specific embodiments.
First, a brief description will be given of a usage scenario of the present solution.
Fig. 1 shows a schematic diagram of a scenario of use of the scheme of the present application, as shown in fig. 1, the present application is applied to user tracking, and the related hardware device at least includes a user terminal device, a WEB server and a DNS system, where the user terminal device, the WEB server and the DNS system can 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 the application, software with user tracking requirements, such as an APP or a browser, is installed on the user terminal equipment, and a program for executing the method, namely a tracking program, is loaded in the software with the user tracking requirements, such as Javascript which can be loaded on a client browser, and is triggered to be started to calculate the fingerprint of the user equipment after the software is started, wherein the tracking program is private. And the machine fingerprint tracking server is responsible for executing calculation tasks and integrating machine fingerprints, and reporting the generated machine fingerprints, cookie information and device fingerprints to the background machine fingerprint tracking server.
Further, a Stub Resolver (Stub Resolver) matched with the operating system is also installed on the user terminal device, and is used for querying the DNS record in the local cache or forwarding the DNS request sent by the tracking program to the DNS system.
The application utilizes the characteristics of the DNS system to realize the fingerprint identification of the identification machine, but the setting of the DNS system does not belong to the discussion scope of the application.
In the present application, the DNS system is used to resolve an IP address corresponding to a URL, and the DNS system includes a recursive resolver (DNS Recursive Resolver), a Root name server (Root name server), a TLD (com) name server, and an authentification (example. Com) name server, etc.
Notably, in this example, it is assumed that the DNS is configured with a lifecycle, and that the resolved IP address is returned as a result during the lifecycle; if the life cycle expires, the resolved IP address is removed from the cache.
In particular, the life cycle of DNS may vary from a few minutes to one week depending on the setting, and typically will be selected in the range of 5 minutes to one week.
In the present application, the WEB server, i.e. the API server, is configured to serve the HTTP request and reply to the value represented by the API, which will be described in detail below.
And the back-end fingerprint tracking server module is used for receiving the data reported by the front end, associating the related user equipment fingerprints and the like.
For the purpose of illustrating the technical solution of the present application, the following assumptions are made in the following examples:
the preset URLs are three, namely x1. Sample. Com, x2. Sample. Com and x3. Sample. Com. Each URL corresponds to five API servers, and thus each URL can be resolved to an IP address of any 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, 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 the same, respectively; 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 the same, respectively.
As can be seen from the above examples, if one URL corresponds to a plurality of IP addresses, the IP address obtained by parsing is one of these IP addresses, and which IP address is selected depends on the DNS configuration, a common method is Round robin, and if many users access the same page, it may happen that different user devices generate the same fingerprint.
It can be appreciated that the number of fingerprint combinations N Finger means The following formula can be used to represent:
N finger means ＝(N U ) N clothes
Wherein N is U Representing the number of access URLs; n (N) Clothes with a pair of wearing articles Representing the number of servers.
It can be seen that increasing the number of accesses to different URLs, or increasing the number of IP addresses (API servers) corresponding to URLs, can reduce machine fingerprint collisions. The above example is an example, and the combination mode of the user equipment fingerprints is 3 in total 5 =243. If 10 preset URLs are provided and 10 corresponding servers are configured for each URL, the combination mode of the fingerprints of the user equipment is increased to 10 10 =100 hundred million. Therefore, the more URLs the preset accesses, the lower the probability of fingerprint collision; the greater the number of IP addresses corresponding to each URL, the lower the likelihood of fingerprint collision. Therefore, the scheme provided by the application can achieve reasonable balance between one machine fingerprint conflict and equipment cost by adjusting the number of the URL of the preset access and/or the number of the corresponding servers of each URL.
Fig. 2 shows a flowchart of a method for generating a fingerprint of a user equipment according to the present application, as shown in fig. 2, the method includes the following steps S101 to S105:
step S101, a 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 a certain APP is started to browse, the client, in this example, the APP loaded with a tracking program simultaneously starts the tracking program, after the tracking program is triggered, first, sequentially initiates accesses to all preset URLs, and the order of the accesses may be preset.
In this example, the client sequentially initiates accesses to three URLs, where the access order is x1. Sample. Com, x2. Sample. Com, and x3. Sample. Com.
Step S102, the client sends an analysis request to a Stub Resolver (Stub Resolver) according to access to a 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.
Step S103, the stub parser feeds back the IP address corresponding to the URL according to the parsing request.
In this example, the way the stub parser obtains the IP address corresponding to the URL includes at least two of the following:
firstly, searching corresponding IP addresses in each level of cache; and secondly, randomly selecting one IP address from the set of IP addresses.
The following describes two implementations of the approach to obtaining IP addresses, respectively:
in the first way, the searching the corresponding IP address in each level of cache, and the stub parser feeding back the IP address corresponding to the URL according to the parsing request may include:
and the stub parser searches the IP address corresponding to the URL in the cache set according to the parsing request.
In this example, the cache set is made up of all cache devices between the operating system cache and the DNS cache, e.g., the operating system cache and the DNS cache.
Further, the stub parser searching for the IP address corresponding to the URL in the cache set according to the parse request includes:
sequentially sequencing all cache devices in a cache set according to a preset sequence;
and sequentially searching the IP address corresponding to the URL in each cache device in the cache set.
In this example, the preset order of the cache devices may be
Continuing with the above example, if the page is refreshed or revisited, the client will again access x1. Sample. Com, x2. Sample. Com, and x3. Sample. Com in sequence. The client sends an analysis request to the Stub server, the Stub server queries the caches step by step (including the caches of the Stub server and Recursive Resolver), finds that the corresponding IP address 10.1.1.1 is found, 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. Similarly, the responses that the client gets from x2.Example. Com and x3.Example. Com are value=2 and value=3, respectively, so the fingerprint of the user machine remains 123.
In a second way, the IP address record stored in each level of cache device is cleared after the DNS TTL expires, so that the same URL needs to be re-resolved, i.e. an IP address is randomly selected from a set of IP addresses, where the stub resolver feeds back, according to the resolution request, an IP address corresponding to the URL, where the method may include:
and the DNS system randomly analyzes and generates an IP address from a plurality of IP addresses corresponding to each URL according to the analysis request.
Continuing with the example above, if the client accesses x1. Sample. Com, the client will send a resolution request to the Stub Server, which will continue to send the request to the DNS system, which returns a query result including 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), according to the rule of configuration, in this example, it is assumed that the resolved IP address is 10.1.1.1, and the IP address will be stored in the buffers of Recursive Resolver and Stub Server, respectively, for query use.
It will be appreciated that re-resolving the same URL will likely result in a different IP address than the previous resolution, which will result in the same client generating different user device fingerprints, how will these two different user device fingerprints be associated? The application adopts cookie as bridge for connecting two user equipment fingerprints.
Therefore, after the IP address is cleared, the corresponding IP address may be found according to the cookie information, and it may be understood that when the IP address is not cleared, the corresponding IP address may also be found according to the cookie information.
Specifically, the method of joining two user device fingerprints using cookies 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 backend server searches the database for the history cookie information, for example, may be a relational database;
step S304, if the history cookie information is found in the database, the IP address is linked with the IP address in the history cookie information.
The inventor finds that using a cookie as an index to inquire the user equipment fingerprint related to the cookie, and then sequentially inquires the database, if the user equipment fingerprint record is found, the user equipment fingerprint record can be used as the inquiry result of the original user equipment fingerprint, so that the user equipment fingerprints which are the same as the user equipment but are different due to the expiration of the IP address in the cache are associated, and the uniqueness of the user equipment fingerprints is ensured.
To increase reliability and reduce errors we use device fingerprints in addition to cookies, including properties of the client hardware device and browser, e.g. machine core number, memory capacity and User Agent, etc., ensuring that we still have the possibility to link the two machine fingerprints when cookies are deleted.
In this example, the IP address acquired by the client each time is cached in each level of cache for subsequent query use.
Step S104, the client acquires the searched IP address.
Step S105, the client generates a user equipment fingerprint according to the IP address.
Optionally, the step may include:
the client sends an HTTP request to an API server corresponding to the IP address;
the client acquires character strings replied by the API servers;
the client side sequentially arranges all character strings replied by all servers 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 side arranges all the character strings replied by all the servers in sequence to generate 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, where the API server replies a 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 after receiving the HTTP request, the API server replies with a response value of 1.
Then, the client continues to access x2.example.com and x3.example.com in sequence, and the IP addresses obtained respectively are assumed to be 10.1.1.2 and 10.1.1.3, and correspondingly, the corresponding APIs are sequentially accessed, so as to obtain response values of value=2 and value=3 respectively.
The client can calculate the fingerprint FP of the user equipment of the current device as 123 according to the above, and send the fingerprint back to the WEB server data receiving server, which receives the information such as the fingerprint of the user equipment, but does not send a response value to the user equipment.
In a second aspect, the present application also provides an apparatus for generating a fingerprint of a user equipment, the apparatus comprising:
the client is used for initiating sequential access to a plurality of different preset URLs;
the client is further used for sending an analysis request to a Stub Resolver (Stub Resolver) according to 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 a user equipment fingerprint according to the IP address.
In one example, the stub parser is further configured to search, according to the parse request, an IP address corresponding to the URL in a cache set, 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 analyzes and generates an IP address from a plurality of IP addresses corresponding to each URL according to the analysis request.
In the manner that this can be achieved,
the client can also be used for acquiring cookie information carried by a preset URL;
the client may also be configured to send the cookie information to a back-end server;
the back-end server can also search the historical cookie information in the database;
if the history cookie information is found in the database, the IP address is linked with the IP address in the history cookie information.
In one implementation, the IP addresses acquired by the client are all 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 may also be configured to obtain the character strings replied by the servers;
the client can also be used for sequentially arranging all character strings replied by all servers 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 hashing the fingerprint string.
Further, the client side arranges all the character strings replied by all the servers in sequence to generate fingerprint character strings, and the fingerprint character strings can be arranged according to a preset sequence.
In a third aspect, the present application also provides a program for generating a user equipment fingerprint, the program being adapted to implement the steps of the method for generating a user equipment fingerprint according to the first aspect.
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 fingerprint of a user equipment described in the first aspect.
In a fifth aspect, an apparatus for generating a user equipment 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 one processor to cause the at least one processor to perform the method of generating a user device fingerprint of the first aspect described above.
The scheme provided by the application can identify a cross-application and browser method on the same machine, combines the working characteristics of the existing DNS system, if one URL corresponds to a plurality of IP addresses, the URL can be resolved into different IP addresses each time, if one group of URLs is accessed, a group of resolved unique IP address sequences can be obtained, and the user equipment fingerprint generated by the method can realize accurate user tracking.
The application has been described in detail in connection with the specific embodiments and exemplary examples thereof, but such description is not to be construed as limiting the application. It will be understood by those skilled in the art that various equivalent substitutions, modifications or improvements may be made to the technical solution of the present application and its embodiments without departing from the spirit and scope of the present application, and these fall within the scope of the present application. The scope of the application is defined by the appended claims.
Claims (8)
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 an analysis request to a Stub Resolver (Stub Resolver) according to access to a preset URL;
the stub parser feeds back the IP address corresponding to the URL according to the parsing request;
the client acquires the searched IP address;
the client sends an HTTP request to an API server corresponding to the IP address;
the client acquires character strings replied by the servers;
the client side sequentially arranges all character strings replied by all servers 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.
2. The method of claim 1, wherein the stub parser feeding back the IP address corresponding to the URL according to the parse request comprises: the stub parser searches the IP address corresponding to the URL in a cache set according to the parsing request, wherein the cache set is composed of all cache devices between an operating system cache and a DNS cache.
3. The method according to claim 1 or 2, wherein the stub parser, according to the parse request, looking up in a cache set an IP address corresponding to the URL comprises:
all the cache devices in the cache set are sequentially ordered from the operation system cache to the DNS cache according to the site order;
and sequentially searching the IP addresses corresponding to the URLs in the cache set.
4. The method of claim 3, wherein the stub parser feeding back the IP address corresponding to the URL according to the parse request further comprises:
and the DNS system randomly analyzes and generates an IP address from a plurality of IP addresses corresponding to each URL according to the analysis request.
5. The method of claim 4, wherein after the DNS system randomly resolves 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 the historical cookie information in the database;
if the history cookie information is found in the database, the IP address is linked with the IP address in the history cookie information.
6. 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 further used for sending an analysis request to a Stub Resolver (Stub Resolver) according to 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 sends an HTTP request to an API server corresponding to the IP address;
the client acquires character strings replied by the servers;
the client side sequentially arranges all character strings replied by all servers 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. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method of generating a user equipment fingerprint as claimed in any of claims 1 to 5.
8. An apparatus for generating a fingerprint of a user device, 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 one processor to cause the at least one processor to perform the method of generating a user equipment fingerprint of any one of claims 1 to 5.
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 CN114760270A (en) | 2022-07-15 |
| CN114760270B true 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 (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2975547A1 (en) * | 2014-07-17 | 2016-01-20 | Electronics and Telecommunications Research Institute | Method and apparatus for preventing illegitimate outflow of electronic document |
| 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 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8689300B2 (en) * | 2007-01-30 | 2014-04-01 | The Boeing Company | Method and system for generating digital fingerprint |
| KR101404596B1 (en) * | 2012-05-03 | 2014-06-11 | (주)엔써즈 | System and method for providing video service based on image data |
| CN105577777B (en) * | 2015-12-18 | 2019-12-13 | 腾讯科技（深圳）有限公司 | message processing method, device and system |
-
2021
- 2021-05-12 CN CN202110516342.9A patent/CN114760270B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2975547A1 (en) * | 2014-07-17 | 2016-01-20 | Electronics and Telecommunications Research Institute | Method and apparatus for preventing illegitimate outflow of electronic document |
| 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 |
|---|
| "Malicious URL sequence detection using event de-noising convolutional neural network";Toshiki Shibahara等;《2017 IEEE International Conference on Communications》;全文 * |
| "基于DPI的应用指纹自动提取方法研究";饶亲苗，彭艳兵;《计算机应用与软件》;全文 * |
| "基于设备指纹的物联网终端接入认证系统的研究与实现";程洋;《中国优秀硕士学位论文全文数据库》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114760270A (en) | 2022-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10250526B2 (en) | Method and apparatus for increasing subresource loading speed | |
| CN108090064B (en) | Data query method and device, data storage server and system | |
| US7802014B2 (en) | Method and system for class-based management of dynamic content in a networked environment | |
| US9021022B2 (en) | Method and system for identifying website visitors | |
| CN108574742B (en) | Domain name information collection method and domain name information collection device | |
| JP6802571B2 (en) | How to process data, devices and computer programs, and zone files for hierarchical Domain Name System | |
| US20190394217A1 (en) | Method, apparatus and system for anti-attacking in domain name system (dns) | |
| AU2010263076B2 (en) | Characterizing unregistered domain names | |
| CN109067936B (en) | Domain name resolution method and device | |
| US10360292B2 (en) | Lightweight web page generation | |
| CN111698345B (en) | Domain name query method, recursive server and storage medium | |
| US20150100563A1 (en) | Method for retaining search engine optimization in a transferred website | |
| CN114205330A (en) | Domain name resolution method, domain name resolution device, server, and storage medium | |
| WO2017166524A1 (en) | Domain name parsing method and apparatus | |
| CN113055503B (en) | IPv6 webpage link processing method, device, equipment and readable storage medium | |
| CN114760270B (en) | Method and device for generating user equipment fingerprint | |
| CN114338630B (en) | Domain name access method, device, electronic equipment, storage medium and program product | |
| JP6233846B2 (en) | Variable-length nonce generation | |
| WO2018178727A1 (en) | Determining that multiple requests are received from a particular user device | |
| CN110944037B (en) | Method, computer device and storage medium for client cache change configuration | |
| CN114500456A (en) | DNS scheduling optimization method and device based on full-network sniffing and computing equipment | |
| US10659424B2 (en) | Determining status of domain name registration | |
| CN112714078A (en) | Network traffic identification method and device, storage medium and server | |
| CN111064822B (en) | User tracking method and device and electronic equipment | |
| CN109086428B (en) | Forwarding information access frequency counting method and device |
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 |