WO2013044569A1

WO2013044569A1 - Network user identification method and application server thereof

Info

Publication number: WO2013044569A1
Application number: PCT/CN2011/085016
Authority: WO
Inventors: 郑芳只; 罗峰; 黄苏支
Original assignee: 北京亿赞普网络技术有限公司
Priority date: 2011-09-30
Filing date: 2011-12-30
Publication date: 2013-04-04
Also published as: CN102333092A; CN102333092B

Abstract

The present invention provides a network user identification method and an application server thereof. The method specifically comprises: when a cookie does not exist in user network-accessing behavior information of a corresponding client user, obtaining a corresponding user identity through query according to a user identifier and a user agent of the corresponding client user; recovering the corresponding cookie according to the user identity; and obtaining the information of the corresponding client user through identification according to the user identity in the recovered cookie. The present invention can improve user identification accuracy under the condition that the cookie is deleted.

Description

Method for network user identification and application server thereof

The present application relates to the field of network communication technologies, and in particular, to a method for network user identification and an application server thereof. Background technique

At present, the rapid growth of Internet scale and coverage has brought about information overload problems: excessive information and reduced. In order to reduce the cost of the user's enjoyment of information, it is necessary to recommend the required information to the user. Among them, the first step in recommending information to the user is to identify the user, because only each user is identified, and the information can be further mined, calculated, and recommended based on the user's past behavior.

Taking the website as an example, after identifying each user, it is not only clearer how many users have visited the website, but also who they are (user ID, email, gender age, etc.); Users, find their behavior characteristics, hobbies and personalized settings, in order to better grasp the user needs and enhance the user experience.

A typical user identification method of the prior art is user identification based on a cookie (a small text file for storing user private information). When user cookies are obtained by customizing the Apache log format or JavaScript, a very effective means of user identification has been found. The cookie can be considered to be bound to a certain access client computer without being cleared, so the accuracy of cookie-based user identification is relatively high.

However, cookie-based user identification is of course also flawed. Because the browser automatically saves the cookie to a local directory corresponding to the client, the most common defect is that the cookie is deleted by the client user and the client user cannot The original record implementation corresponds; at the same time, because the client computer will be shared, or the client user will access the website on different computers, the cookie cannot directly correspond to the client user.

In summary, a technical problem that needs to be solved urgently by those skilled in the art is: How to achieve higher-precision user identification in the case where a cookie is deleted. Summary of the invention

The technical problem to be solved by the present application is to provide a method for network user identification and an application server, which can improve the accuracy of user identification when a cookie is deleted. In order to solve the above problem, the present application discloses a method for network user identification, including the following steps:

When the cookie does not exist in the online behavior information of the user of the corresponding client user, the corresponding user identity certificate is obtained according to the user identifier and the user agent of the corresponding client user;

Recovering the corresponding cookie according to the user identity certificate;

According to the user identity certificate in the recovered cookie, the information of the corresponding client user is identified.

Preferably, the step of querying the corresponding user identity certificate according to the user identifier and the user agent of the corresponding client user includes:

Query whether there is a corresponding client user in the local cache of the application server according to the user identifier and the user agent;

When the cache hit succeeds, obtaining the user identity certificate of the client user according to the user identifier and the user agent;

When the cache hit fails, according to the user identifier and the user agent, the remote server is queried whether there is a corresponding client user;

When a corresponding client user exists in the remote server, the user identity of the client user is obtained according to the user identifier and the user agent;

When there is no corresponding client user in the remote server, a new client user's user identity is generated in the remote server according to the user identity and the user agent.

Preferably, before the step of obtaining the corresponding user identity certificate according to the user identifier and the user agent of the corresponding client user, when the cookie does not exist in the online behavior information of the user of the corresponding client user, the method further Includes:

When the cookie exists in the user's online behavior information, the latest user agent is obtained according to the user identity certificate in the cookie. Preferably, the step of obtaining the latest user agent according to the user identity certificate in the cookie includes:

Query whether the corresponding client user exists in the local cache of the application server according to the user identity certificate in the cookie;

When the cache hit succeeds, the local cache user information of the application server is obtained according to the local cache query result of the application server, where the local cache user information of the application server includes a user agent;

Matching the user agent in the local cache user information of the application server with the user agent in the user's online behavior information. If the matching is successful, the user agent in the locally cached user information of the application server is used as the latest user agent. If the matching fails, updating the user agent in the locally cached user information of the application server according to the user agent in the online behavior information of the user;

When the cache hit fails, the identification information of the corresponding client user is queried in the remote server according to the user identity certificate in the cookie, and the remote storage user information is obtained according to the query result, where the remote storage user information includes the user agent;

Matching the user agent in the remote storage user information with the user agent in the online behavior information of the user, and if the matching is successful, using the user agent in the remote storage user information as the latest user agent; if the matching fails And updating the user agent in the remote storage user information according to the user agent in the user online behavior information.

Preferably, the method further includes:

The user identity, the user identity, and the current user agent are stored in association on the application server side and/or the remote server side in the presence of the user identity certificate.

Preferably, the user identifier comprises: a network user name, and/or a user IP address of the dedicated line user. In another aspect, the application also discloses an application server, including:

The first querying device is configured to: when the cookie does not exist in the online behavior information of the user of the corresponding client user, according to the user identifier of the corresponding client user and the user agent, the query is used accordingly Household identification certificate;

a recovery device, configured to restore a corresponding cookie according to the user identity certificate;

The identifying means is configured to identify the information of the corresponding client user according to the user identity certificate in the restored cookie.

Preferably, the first query device includes:

a first cache searching module, configured to query, according to the user identifier and the user agent, whether the corresponding client user exists in the local cache of the application server;

a first obtaining module, configured to acquire, according to the user identifier and the user agent, a user identity certificate of the client user when the cache hit succeeds;

a first query requesting module, configured to send a first query request to the remote server when the cache hit fails;

The remote server includes:

a first remote querying device, configured to query, according to the first query request, by the user identifier and the user agent, whether a corresponding client user exists in the remote server;

a certificate obtaining device, configured to obtain a user identity certificate of the client user according to the user identifier and the user agent when a corresponding client user exists in the remote server;

a certificate generating device, configured to generate a user identity certificate of a new client user according to the user identifier and the user agent in the remote server when the corresponding client user does not exist in the remote server;

And a first returning device, configured to return the user identity certificate outputted by the certification obtaining device or the certification generating device to the application server.

Preferably, the application server further includes:

The user agent obtaining means is configured to obtain the latest user agent according to the user identity certificate in the cookie when the cookie exists in the online behavior information of the user before the first querying device performs the query operation.

Preferably, the user agent obtaining device includes:

a second cache lookup module, configured to query, in the local cache of the application server, whether a corresponding client user exists according to the user identity certificate in the cookie; a second obtaining module, configured to obtain local cache user information of the application server according to the local cache query result of the application server, where the local cache user information of the application server includes a user agent;

a local matching module, configured to match a user agent in the local cache user information of the application server with a user agent in the online behavior information of the user, and if the matching is successful, the user in the local cache user information of the application server The agent acts as the latest user agent; if the match fails, the user agent in the locally cached user information of the application server is updated according to the user agent in the user's online behavior information;

a second query requesting module, configured to send a second query request to the remote server when the cache hit fails;

The remote server includes:

a second remote search device, configured to: when the cache hit fails, query the identification information of the corresponding client user in the remote server according to the user identity certificate in the cookie, and obtain remote storage user information according to the query result, where the remote storage user The information includes a user agent;

a remote matching device, configured to match a user agent in the remote storage user information with a user agent in the user online behavior information, and if the matching is successful, use the user agent in the remote storage user information as the latest a user agent; if the matching fails, updating the user agent in the remote storage user information according to the user agent in the user online behavior information; and the second returning device is configured to output the latest information of the remote matching device User agent, returned to the application server.

Preferably, the application server further includes:

The association storage device is configured to store the user identity certificate, the user identifier, and the current user agent on the application server side in the presence of the user identity certificate.

Preferably, the user identifier comprises: a network user name, and/or a user IP of the leased line user. The present application also provides a computer readable recording medium on which a program for performing the above-described method of network user identification is recorded. Compared with the prior art, the present application has the following advantages:

In the case where the cookie is deleted, the application first recovers the deleted cookie according to the user identifier and the user agent, and then identifies the information of the corresponding client user according to the user identity certificate in the restored cookie; The accuracy of the identification is higher than the accuracy of the user identification based on the IP+ user agent, so the application can improve the accuracy of the user identification in the case where the cookie is deleted;

Secondly, since the application can overcome the problem of low user identification accuracy caused by the cookie deletion problem in the prior art, accurately locate and track the client-based user; thus, the user can further recommend the most effective and valuable value according to the recognition result. Information, which can solve the problem of user information overload and reduce the cost of users enjoying information;

Furthermore, the application can also obtain the latest user agent according to the user identity certificate in the cookie, and obtain the corresponding user identity certificate according to the user identifier of the corresponding client user and the latest user agent query, so as to avoid the user agent changing the cookie. The impact of recovery can further improve the accuracy of user identification. DRAWINGS

1 is a flowchart of Embodiment 1 of a method for network user identification according to the present application;

2 is a flow chart of a remote server querying based on a user identifier and a user agent according to the present application;

3 is a flowchart of Embodiment 2 of a method for network user identification according to the present application;

4 is a flow chart of a remote server querying based on a user identity certificate in a cookie;

FIG. 5 is an example of a user identification timing chart of the present application; FIG.

FIG. 6 is a schematic diagram of interaction between a client 6A and an application server 6B according to the present application; FIG. 7 is a structural diagram of an application server embodiment of the present application. detailed description

The above described objects, features and advantages of the present application will become more apparent and understood. One of the core concepts of the embodiment of the present application is that, in the case that the client user cookie is deleted, the deleted cookie is restored on the application server according to the user identifier and the user agent; specifically, when the cookie is in the corresponding client user When the user's online behavior information does not exist, firstly, according to the user identifier and the user agent of the corresponding client user, the corresponding server user identification (UID, User Identification) is obtained, and then the corresponding user identity certificate is restored according to the user identity certificate. The cookie finally identifies the information of the corresponding client user according to the user identity certificate in the restored cookie. Thus, the present application can improve the accuracy of user identification in the case where the cookie is deleted.

First, a brief introduction to the origin of cookies. In order to identify the user and perform session (session) tracking, some websites use cookies to store user private information (usually encrypted) on the client; wherein the most important user private information in the cookie is the user identity that is uniquely identified by the user. prove.

In practice, when the client user first accesses the application server of the website, the application server assigns a unique user identity to the client user, generates a cookie according to the user identity certificate, and then passes the cookie to the response message. Client user. The browser will automatically save the cookie to a local directory. In this way, the cookie can be passed to the application server in each subsequent access request, and the application server can know which client user the access request was sent based on the user identity in the cookie.

The technical solutions of the present application are specifically described below through the preferred embodiments. It should be noted that the preferred embodiments are not to be construed as limiting the present application. Additionally, the steps illustrated in the flowchart of the figures may be performed in a computer system, such as a set of computer-executable instructions, and, although the logical order is illustrated in the flowchart, in some cases, may be different The steps shown or described are performed in the order herein. Referring to FIG. 1 , a flowchart of Embodiment 1 of a method for network user identification according to the present application is shown, which may specifically include:

Step 101: When the cookie does not exist in the online behavior information of the user of the corresponding client user, according to the user identifier of the corresponding client user and the user agent, the corresponding user ID is obtained. Bright.

Specifically, the application server may, according to the packet data in the user access request, parse the online behavior information of the user according to the packet data in the user access request, where the user online behavior information may generally include the user IP ( User—ip), User Agent (UA, User Agent), cookie, access to website domain (host), access to website page information (Uniform Resource Locator), and/or user's last referee.

User agents are information that helps the server identify the operating system and version of its client, CPU type, browser and version, browser rendering engine, browser language, browser plug-in, and so on.

If there is no cookie in the user's online behavior information parsed by the application server, it is considered that the cookie data does not carry the cookie. At this time, one possibility is that the user's cookie is deleted by the client user, and another possibility is that the client The user's identity is a new user or the first time the site is accessed. At this time, the identity of the client user can be identified by applying the present application, further recovering the user and generating a new user.

For an Internet user, its user ID is unique and does not change. Specifically, in practice, the user ID of the private line user can be used as the user identifier of the client user because the user IP address is fixed and does not change, and the unique user can be identified. For non-dedicated users such as ADSL (Asymmetric Digital Subscriber Line), since the IP is dynamic, it cannot be uniquely marked, and the ADSL account network user name (user_name) is fixed, and The unique user can be identified, so at this time, the ADSL account network user name can be used as the user identifier of the client user.

In practice, when receiving the Internet access request from the client user, the AAA (Authentication, Authorization, Accounting, Accounting) server generates a corresponding accounting message; and the application server receives the accounting After the fee packet, the user basic information may be parsed according to the billing message, and the user basic information may specifically include a network user name (ie, an ADSL account network user name) and/or a user IP address.

In some cases, the application server may obtain the network user name or user IP as the user identifier directly from the user basic information for the client user, and access the online behavior from the user. The user agent is obtained from the information, and then, according to the corresponding user identifier and the user agent, the corresponding user identity certificate can be obtained by querying the application server.

In this case, in order to facilitate online query, in a preferred embodiment of the present application, the user identity certificate, the user identifier, and the current user agent may be stored in association in an offline situation, and correspondingly, the method It can also include:

In the case where the user identity exists, the user identity, the user identity, and the current user agent are stored in association at the application server and/or the remote server.

In this way, the user identification can be queried by performing a query matching in the application server and/or the remote server-side database by using the combined keyword of the user identifier and the current user agent.

In some special cases, the application server may not be able to directly obtain the network user name and user agent. Then, according to the user IP association, the network user name and user agent need to be found, and then the corresponding user identity is obtained according to the corresponding user identifier and user agent query. Proof can be.

In this case, in order to facilitate the online query, in a preferred embodiment of the present application, the user identity certificate, the user identifier, and the current user agent may be associated and stored in an offline situation, and the method may also be performed. Includes:

In the case where the user identity exists, the user IP, the user identity, the user identity, and the current user agent are stored in association at the application server and/or the remote server.

An example of a storage structure in this case is shown below:

Typedef struct user— identification— info— s

{

Char user_name[USER_NAME_MAX_LEN] ;/*network username */ char UA[UA— MAX— LEN];/*UA*/

Unsigned int user— ip;/*user ip*/

Unsigned long long user— id;/*UID*/

In a preferred embodiment of the present application, the step 101 may further include: when the cookie does not exist in the online behavior information of the user of the corresponding client user, according to the user The identifier and the user agent query whether the corresponding client user exists in the local cache of the application server. If the cache hit succeeds, the user identity of the client user is obtained according to the user identifier and the user agent.

It should be noted that the local cache of the application server only retains recent data, such as retaining only

The data of 1 day or 2 days can also retain only the online user data that is currently online, and the rest of the historical data is stored in the remote server, for example, the user who is currently offline.

The preferred embodiment searches the local cache of the application server for the client user based on the user identifier and the user agent. If it can be found, it indicates that the client user recently appears in the application server, and thus can obtain the unique identifier as the user. The user identification (the user identification in the cookie information, as part of the cookie content), also proves that the client user deleted the cookie information and needs to further restore the cookie. In another preferred embodiment of the present application, the step of obtaining the corresponding user identity certificate according to the user identifier of the corresponding client user and the user agent query may further include:

When the cache hit fails, the user identifier and the user agent are queried according to the user identifier to check whether there is a corresponding client user; it should be noted that when the cache hit fails, that is, when the application server's local cache cannot be found. , indicating that the client user has not appeared in the application server recently, so it is necessary to query the historical data of the remote server;

When a corresponding client user exists in the remote server, the user identity of the client user is obtained according to the user identifier and the user agent; that is, when there is no corresponding client user in the remote server, in the remote server A user identity certificate of a new client user is generated according to the user identifier and the user agent.

In the actual application, a cookie is generated based on the user identity and then the cookie is passed to the application server in the response message.

In a specific implementation, the remote server may include a UDC (user data center). For example, the corresponding client user can be found in the UDC database based on the network user name and the user agent, and if found, the user information [network user name, user agent, user-ip, and user identity certificate] is obtained, and the user identity is obtained. Prove feedback to the application server, also said If the client user deletes the cookie information, the user's cookie needs to be further restored. If it is not found, the client user is a new user, and the application server is accessed for the first time. Therefore, a user who globally uniquely identifies a user is assigned. The identity certificate, and initialize the user information [network user name, user agent, user-ip and user identity certificate], and feed the user identity certificate to the application server.

Referring to FIG. 2, a flow chart of a remote server based on a user identifier and a user agent is performed, which may specifically include:

Step 201: Receive an adaptation message from an application server, where the adaptation message includes a network user name and a user agent.

Step 202: Query whether there is a corresponding client user in the database based on the network user name and the user agent, and if yes, go to step 203; otherwise, go to step 204;

Step 203: Obtain user information: a network user name, a user agent, a cookie, and go to step 206;

When the client user exists, it indicates that the client user has entered the application server, the user cookie is deleted, and the cookie can be recovered through the network user name and the user agent.

Step 204: Generate, according to the network user name and the user agent, a user unique identifier user identity certificate in the database;

Step 205, filling the network user name, user agent, cookie in the user table entry of the database, and proceeds to step 206;

Step 206: Return the user identity certificate in the cookie to the application server. Step 102: Restore a corresponding cookie according to the user identity certificate;

In a specific implementation, the step of restoring the corresponding cookie according to the user identity certificate may be: the application server generates a corresponding cookie according to the user identity certificate, and grows the cookie to the client. In this way, when the client user accesses the application server again, the client user will carry the cookie information, so that the application server knows which client user sent the access request. The planting process may be: storing a cookie in a fixed text of a client through a P3P protocol (Private preference platform, Platform for Privacy Preferences), where P3P allows a network site to announce them. An agreement collected about browsing users' intent to use them. Step 103: Identify, according to the user identity certificate in the restored cookie, the information of the corresponding client user.

In practice, the information of the client user as a result of the identification may typically include one or more of the following information:

(1) User identification information:

Specifically, it may include a network user name, a user IP, a user agent, a cookie, and the like.

(2) Base information static attributes:

These can include: age, education, salary, school and occupation.

(3) Dynamic information:

Specifically, it may include an interest group, a delivery advertisement status, and the like.

In a practical application, for a website that requires a user ID to register and log in, the user unique identifier may be selected in the following order: When the user registers to log in, the user ID is taken as the user, and when the user browses in the unlogged state, the user's The cookie is used, and the method is used when the user is not logged in and the cookie is deleted, so as to improve the accuracy of the user identification.

Although the prior art can perform user identification based on the IP+ user agent in the case where the cookie is deleted, since the IP and the user agent are constantly changing, the user cannot be accurately located and identified, resulting in low accuracy of recognition. In the case where the cookie is deleted, the application first recovers the deleted cookie according to the user identifier and the user agent, and then identifies the information of the corresponding client user according to the user identity certificate in the restored cookie; The accuracy of the user identification is higher than the accuracy of the user identification based on the IP+ user agent, so the application can improve the accuracy of the user identification in the case where the cookie is deleted.

Further, since the application can overcome the problem of low user identification accuracy caused by the cookie deletion problem in the prior art, accurately locate and track the client-based user; thus, the user can further recommend the most effective and valuable value according to the recognition result. Information, which can solve the problem of user information overload and reduce the cost of users enjoying information. Referring to FIG. 3, a flowchart of Embodiment 2 of a method for network user identification according to the present application is shown, which may specifically include:

Step 301: When a cookie exists in the online behavior information of the user, obtain the latest user agent according to the user identity certificate in the cookie;

Step 302: When the cookie does not exist in the online behavior information of the user of the corresponding client user, the user identity certificate is obtained according to the user identifier of the corresponding client user and the latest user agent, and the corresponding user identity certificate is obtained;

Step 303: Restore the corresponding cookie according to the user identity certificate;

Step 304: Identify, according to the user identity certificate in the restored cookie, the information of the corresponding client user.

Since the user agent represents browser information, plug-in information, operating system information, etc., when any of the information changes, the user agent content will change, such as version upgrade, install plug-in, or plug-in upgrade, etc., resulting in user agent content. A change has occurred.

In order to avoid the impact of the change of the user agent content on the cookie recovery, the embodiment obtains the latest user agent according to the user identity certificate in the cookie, and updates the user agent in real time to ensure that the user agent is always in the latest state, so that According to the user ID of the corresponding client user and the latest user agent query, the corresponding user identity certificate is obtained to avoid the change of the user agent and affect the cookie recovery, thereby further improving the accuracy of the user identification.

In a preferred embodiment of the present application, the step of obtaining the latest user agent according to the user identity certificate in the cookie may further include:

When the cache hit succeeds, the local cache user information of the application server is obtained according to the local cache query result of the application server, where the local cache user information of the application server may include a user agent;

Matching the user agent in the local cache user information of the application server with the user agent in the user's online behavior information. If the matching is successful, the user agent in the locally cached user information of the application server is used as the latest user agent. It should be noted that the match can be successful. Note that the user agent has not changed, and the user agent in the local cache user information of the application server can be used;

If the matching fails, the user agent in the local cache user information of the application server is updated according to the user agent in the user's online behavior information. It should be noted that the matching failure indicates that the user agent has changed, so it needs to be performed. Update

When the cache hit fails, the identification information of the corresponding client user is queried in the remote server according to the user identity certificate in the cookie, and the remote storage user information is obtained according to the query result, where the remote storage user information may include a user agent;

Matching the user agent in the remote storage user information with the user agent in the user online behavior information, and if the matching is successful, using the user agent in the remote storage user information as the latest user agent; here, matching Successfully stated that the user agent has not changed, so the user agent in the remote storage user information can be used;

If the matching fails, the user agent in the remote storage user information is updated according to the user agent in the user's online behavior information. Here, the match identification indicates that the user agent has changed, so an update is required.

In a specific implementation, the remote server may include a UDC (user data center). For example, a corresponding client user can be found based on a cookie in the UDC's database.

Referring to FIG. 4, a flow chart of a remote server based on a user identity certificate in a cookie is shown in the following, and specifically includes:

Step 401: Receive an adaptation message from an application server, where the adaptation message includes a cookie.

Step 402: Query, according to the user identity certificate in the cookie, the identification information of the corresponding client user in the database;

The presence of a cookie indicates that the corresponding client user has accessed the application server.

Step 403: Obtain user information according to the query result.

Step 404, the user agent in the user information is matched with the user agent in the user's online behavior information, if the matching fails, step 405 is performed; if the matching is successful, step 407 is performed; Step 405: Update the user agent in the online behavior information of the user as the latest user agent to the corresponding user entry.

Here, the user entry is used to store user information in a database;

Step 406: Return the latest user agent to the application server.

Step 407: The user agent in the user information is used as the latest user agent, and is returned to the application server.

It should be noted that after the application server receives the latest user agent, the user identity certificate, the user identity, and the latest user agent may be stored in association. In this way, when the user agent changes, the application server and the UDC update and associate the user information of the client user to improve the accuracy and real-time of the subsequent user identification.

Therefore, in the present application, the user identity certificate, the user identity, and the current user agent are stored in association, and the execution entity of the association store may include one or more of an application server and a UDC, and in addition, the user identity When the proof, the user ID, and any of the current user agents change, the execution subject performs corresponding update and association processing. For a better understanding of the present application, the application of the present application in the actual application is shown in FIG. 5, and the user identification timing diagram may specifically include: Step (1), AAA Server receiving The charging request from the client user obtains the fee or balance of the user account according to the network user name in the charging request, and determines whether the client user is allowed to access the Internet further. If allowed, perform step (2) and (3), otherwise, the client user is denied access to the Internet due to insufficient fees;

Step (2), allowing the client user to access the Internet;

Step (3): When the user's fee and balance allow the user to access the Internet, the AAA Server synchronizes the basic information of the user to the Web server (that is, the application server in this embodiment), and the basic information of the user is parsed by the Web server, that is, the network user name. The user IP and the online and offline status, and cache the basic information of the user on the local server; wherein, the network user name is a unique identifier of the user, and does not change;

Step (4), when the client user browses the Internet, the Web Server according to the corresponding access request The user online behavior information may be analyzed, where the user online behavior information may include: a user IP, a user agent, a cookie, a website i or a name, a website page information, a referer information, and the like;

At the same time, the Web Server determines the cookie information. If the cookie exists, the Web Server queries the user information through the user identity certificate in the cookie, and queries whether the client user exists. If yes, the matching user's online behavior carries the user agent and passes the user identity certificate. The user agent in the user identity information is matched, and if the matching is successful, the user agent does not change; if the matching is unsuccessful, the user is carried in the Internet to carry the user agent to update the user agent information in the query result, and step (7) is performed; If yes, perform step (5);

If the cookie does not exist, the Web Server obtains the network user name and the user agent through the IP association, and then queries the network user name and the user agent to check whether the client user exists. If yes, the user identity information is obtained, that is, through the network user. Name and user agent associate the user, and perform step (7); if not, perform step (5);

Step (5), UDC (user data center, user data center) according to the message type, the partition is based on the network user name + user agent query, or based on the user identity certificate (user_id) query;

The query based on the user identity certificate may include: querying the client user by using the user identity certificate [indicating that the client user has entered the system], obtaining the network user name and the user agent in the user information, and the user carrying the network user this time The name is matched with the user agent. If the matching is successful, step (6) is performed; if the matching is unsuccessful, the network user name and the latest user agent are updated to the user information [user-agent change, association processing], and steps are performed (6) );

The query based on the network user name + user agent may specifically include: querying by using the network user name and the user agent. If the database does not exist, it indicates that the client user is a new user, that is, the first time entering the system, the client needs to be the client. The user newly produces a new user identity certificate; if it exists, it indicates that the client user has deleted the planting cookie, so it can be associated with the user agent through the network user name to obtain the user's original user identity certificate, and turn (6);

Step (6), the UDC synchronizes the association result to the Web server for convenient service processing; Step (7), the Web Server performs user behavior identification according to the identified user information, User interest analysis and accumulation, and analyze the user's required information and interesting information from the user's accumulated information, website content, time and other dimensions, and send it to the user;

Steps (8) and (9), when the client user is not accessing the Internet for the first time, since the Web server has stored the user information in the local cache of the application server, the associated storage structure based on the local cache of the application server can be performed. Business processing

Step (10), when the client user goes offline, the AAA Server synchronizes the corresponding offline message to the Web Server;

Step (11), when the Web Server receives the offline message, parses the corresponding user information: the network user name, the user IP, and the offline state; and, for the information persistence requirement, the user information is synchronized to the UDC. , ;

Step (12), for the requirement of information persistence, the Web Server synchronizes the user information of the client to the UDC, so as to store the latest user information in the user table in the UDC database to avoid user information loss. Happening.

It should be noted that any of the foregoing method steps of the user identification method may be implemented as executable software instructions stored on a computer readable medium, wherein the computer readable medium may also include a transmission type medium.

In order to explain the application environment of the foregoing user identification method embodiment, referring to FIG. 6, a schematic diagram of interaction between the client 6A and the application server 6B is shown. When the application server 6B receives the access request of the client 6A, The user's online behavior information may be parsed according to the packet data in the access request. When the cookie exists in the user's online behavior information of the corresponding client user, the application server 6B may directly return a response to the client 6A according to the cookie. Information; when the cookie does not exist in the user's online behavior information of the corresponding client user, the application server 6B first restores the deleted cookie according to the user identifier and the user agent, and then according to the user identity certificate in the restored cookie, to the client End 6A returns a response message. Corresponding to the foregoing method embodiments, the present application further discloses an application server embodiment. Referring to FIG. 7, specifically, the method may include:

The first querying device 701 is configured to: when the cookie is in the online behavior of the user of the corresponding client user When the information does not exist, according to the user ID and user agent of the corresponding client user, the query obtains the corresponding user identity certificate;

The recovery device 702 is configured to restore the corresponding cookie according to the user identity certificate;

The identifying means 703 is configured to identify the information of the corresponding client user according to the user identity certificate in the restored cookie.

In the embodiment of the present application, preferably, the user identifier may include: a network user name, and/or a user IP of the private line user.

In a preferred embodiment of the present application, the first querying apparatus 701 may further include:

The obtaining module is configured to obtain the user identity of the client user according to the user identifier and the user agent when the cache hit succeeds.

In another preferred embodiment of the present application, the first querying apparatus 701 may further include: a first query requesting module, configured to send a first query request to the remote server when the cache hit fails;

In this case, the remote server may specifically include:

In another preferred embodiment of the present application, the application server may further include: a user agent obtaining means, configured to be a cookie before the first querying device performs the query operation When the user's online behavior information exists, the latest user agent is obtained according to the user identity certificate in the cookie.

In still another preferred embodiment of the present application, the user agent obtaining apparatus may further include:

a second cache lookup module, configured to query, according to the user identity certificate in the cookie, whether the corresponding client user exists in the local cache of the application server;

a second obtaining module, configured to obtain local cache user information of the application server according to a local cache query result of the application server, where the local cache user information of the application server includes a user agent;

The remote server includes:

In the embodiment of the present application, the application server may further include: an association storage device, configured to be in the application server end in the presence of the user identity certificate The user identity certificate, the user identity, and the current user agent are stored in association.

For the application server embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

Based on the above, the present application also provides a computer readable recording medium on which a program for performing the above-described method of network user identification is recorded. For details of the method for the network user identification, refer to the content of the method embodiment, which is not described herein.

The computer readable recording medium includes any mechanism for storing or transmitting information in a form readable by a computer (e.g., a computer). For example, a machine-readable medium includes a read only memory (ROM), a random access memory (RAM), a magnetic disk storage medium, an optical storage medium, a flash storage medium, an electrical, optical, acoustic, or other form of propagated signal (eg, a carrier wave) , infrared signals, digital signals, etc.).

This application can be used in a variety of general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, networked personal computers, small computers, mainframe computers, A distributed computing environment, including any of the above systems or devices.

The application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. The present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including storage devices.

In the present application, "component", "device", "system," and the like refer to related entities applied to a computer, such as hardware, a combination of hardware and software, software or software in execution, etc. In detail, for example, A component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable component, a thread of execution, a program, and/or a computer.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments can be referred to each other.

The above is a method for network user identification provided by the application and an application server thereof. In the detailed description, the principles and implementations of the present application are explained in the specific examples. The description of the above embodiments is only for helping to understand the method of the present application and its core ideas; and, for a person of ordinary skill in the art The present invention is not limited by the scope of the present application.

Claims

Claim

A method for network user identification, comprising the steps of:

Recovering the corresponding cookie according to the user identity certificate;

The method according to claim 1, wherein the step of obtaining a corresponding user identity certificate according to the user identifier and the user agent of the corresponding client user comprises: according to the user identifier and the user agent, Query whether there is a corresponding client user in the local cache of the application server;

3. The method according to claim 1, wherein when the cookie does not exist in the online behavior information of the user of the corresponding client user, the query is obtained according to the user identifier of the corresponding client user and the user agent. Before the step of authenticating the user identity, the method further comprises: when the cookie exists in the online behavior information of the user, obtaining the latest user agent according to the user identity certificate in the cookie.

4. The method according to claim 3, wherein the step of obtaining the latest user agent according to the user identity certificate in the cookie comprises:

When the cache hit succeeds, the application service is obtained according to the local cache query result of the application server. The local cache user information of the requester, the local cache user information of the application server includes a user agent;

The method according to any one of claims 1 to 4, further comprising: authenticating the user identity on the application server side and/or the remote server end in the presence of the user identity certificate, The user ID is stored in association with the current user agent.

The method according to any one of claims 1 to 4, wherein the user identification comprises: a network user name, and/or a user IP address of the private line user.

7. An application server, comprising:

The first querying device is configured to: when the cookie does not exist in the online behavior information of the user of the corresponding client user, obtain a corresponding user identity certificate according to the user identifier and the user agent of the corresponding client user;

The application server according to claim 7, wherein the first querying device comprises: The first cache lookup module is configured to query, in the local cache of the application server, whether a corresponding client user exists according to the user identifier and the user agent;

The remote server includes:

9. The application server of claim 7, further comprising:

The application server according to claim 9, wherein the user agent obtaining means comprises:

a local matching module, configured to use a user agent in the local cache user information of the application server The user agent in the online behavior information of the user performs matching, and if the matching is successful, the user agent in the locally cached user information of the application server is used as the latest user agent; if the matching fails, according to the user The user agent in the online behavior information updates the user agent in the locally cached user information of the application server;

The remote server includes:

The application server according to any one of claims 7 to 10, further comprising:

The application server according to any one of claims 7 to 10, wherein the user identifier comprises: a network user name, and/or a user IP of the private line user.

A computer readable recording medium having recorded thereon a program for executing the method of claim 1.