CN113079188A

CN113079188A - Client identification processing method, device, terminal, server, system and medium

Info

Publication number: CN113079188A
Application number: CN202010005853.XA
Authority: CN
Inventors: 路华生; 刘林
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2020-01-03
Filing date: 2020-01-03
Publication date: 2021-07-06
Anticipated expiration: 2040-01-03
Also published as: CN113079188B

Abstract

The application discloses a client identifier processing method, a client identifier processing device, a user terminal, a server and a medium, and relates to the technical field of intelligent search. The method comprises the following steps: receiving a first client identifier of a first search client sent by a second search client; the first search client is configured on the first user terminal, and the second search client is configured on the second user terminal; establishing a binding relationship between the first client identifier and a second client identifier of a second search client; the first client identification is obtained from a probe request sent by a first search client when a second search client monitors the probe request. Through the scheme, the first search client can be associated with the second search client, so that the search results corresponding to the search requests initiated by the user at the first search client and/or the second search client are optimized.

Description

Client identification processing method, device, terminal, server, system and medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a terminal, a server, and a medium for processing a client identifier.

Background

With the development of internet technology, the same user can initiate information search on a mobile phone and also can initiate information search on a PC.

For a scene in which information search is performed without account login, it is impossible to know whether a user initiating search at a search client on a PC and a user initiating search at a search client on a mobile phone are the same user.

Disclosure of Invention

The client identifier processing method, device, terminal, server, system and medium provided by the embodiment of the application realize the establishment of the binding relationship between a first search client on a first user terminal and a second search client on a second user terminal, so that whether users initiating searches on different clients are the same user can be determined based on the binding relationship.

The embodiment of the application discloses a client identifier processing method, which is applied to a server and comprises the following steps:

receiving a first client identifier of a first search client sent by a second search client; the first search client is configured on the first user terminal, and the second search client is configured on the second user terminal;

establishing a binding relationship between the first client identifier and a second client identifier of a second search client;

the first client identification is obtained from a probe request sent by a first search client when a second search client monitors the probe request.

The above embodiment has the following advantages or beneficial effects: by receiving the first client identifier, the binding relationship between the first search client and the second search client is established, so that whether different clients are associated or not can be determined based on the established binding relationship, that is, whether users initiating searches on different clients are the same user or not can be determined, and further, search results corresponding to search requests initiated by the users at the first search client and/or the second search client can be optimized based on the established binding relationship.

Further, before receiving the first client identifier sent by the second search client, the method further includes:

receiving a search request sent by a first search client when a search trigger operation is detected;

and returning a search response message carrying a preset code segment to the first search client, so that the first search client acquires a first client identifier of the first search client by executing the preset code segment and sends a detection request carrying the first client identifier.

Accordingly, the above-described embodiments have the following advantages or advantageous effects: the server side returns the preset code segment to the first search client side, so that the first search client side can rapidly acquire the first client side identification, and the binding relationship between the first search client side and the second search client side is established according to the first client side identification.

Further, after establishing the binding relationship between the first client identifier and the second client identifier, the method further includes:

when a first search request sent by a first search client is received, acquiring a first search result list according to a first search word in the first search request;

acquiring second historical search related information of a second search client based on the binding relationship, and optimizing the first search result list according to the second historical search related information; returning the optimized first search result list to the first search client for displaying; and/or the presence of a gas in the gas,

when a second search request sent by a second search client is received, a second search result list is obtained according to a second search word in the second search request;

based on the binding relationship, acquiring first historical search related information of the first search client, and performing optimization processing on the second search result list according to the first historical search related information; and returning the optimized second search result list to the second search client for displaying.

Accordingly, the above-described embodiments have the following advantages or advantageous effects: based on the binding relationship, the search result is optimized according to the historical search related information of the search client with the binding relationship, so that the search result contains the result related information of the historical search of the user, and the search result is richer and more comprehensive.

Further, the optimizing the first search result list according to the second historical search related information includes:

acquiring second search result information from the second historical search related information, and adding the second search result information to the first search result list; and/or the presence of a gas in the gas,

acquiring click information of the user on second search result information from the second historical search related information, and processing the search results in the first search result list according to the click information;

correspondingly, the optimizing processing of the second search result list according to the first historical search information includes:

acquiring first search result information from the first historical search related information, and adding the first search result information to a second search result list; and/or the presence of a gas in the gas,

acquiring click information of a user on first search result information from the first historical search related information, and processing search results in the second search result list according to the click information;

the first search result information is history search result information obtained aiming at history search words sent by the first search client, and the second search result information is history search result information obtained aiming at history search words sent by the second search client.

Accordingly, the above-described embodiments have the following advantages or advantageous effects: the search results of other search clients related to the search client are processed through the search result information and/or the click information of the search results of the user, so that the search results of the other search clients comprise the search result information of the search client or the search tendency of the user, the search results can fully reflect the reading tendency of the user to the search results, the interested search results are displayed to the user, and the optimization of the search results of the other search clients is realized.

The embodiment of the application discloses a client identifier processing method, which is applied to a first search client configured in a first user terminal and comprises the following steps:

acquiring a first client identifier of a first search client;

sending a detection request carrying a first client identifier so that a second search client sends the first client identifier to a server when monitoring the detection request; the second search client is configured at the second user terminal.

The above embodiment has the following advantages or beneficial effects: by acquiring the first client identifier and sending the detection request carrying the first client identifier to enable the second search terminal to send the detection request to the server, the server can establish a binding relationship between the first search client and the second search client, so that whether different clients are associated or not can be determined based on the established binding relationship, that is, whether users initiating searches on different clients are the same user or not can be determined, and further, search results corresponding to search requests initiated by users on the first search client and/or the second search client can be optimized based on the established binding relationship.

Further, before obtaining the first client identifier of the first search client, the method further includes:

when a search triggering operation is detected, sending a search request to a server;

receiving a search response message returned by a server, wherein the search response message carries a preset code segment;

correspondingly, obtaining a first client identifier of a first search client, and sending a probe request carrying the first client identifier includes:

acquiring a preset code segment in the search response message;

and acquiring a first client identifier of the first search client by executing the preset code segment, and sending a detection request carrying the first client identifier.

Accordingly, the above-described embodiments have the following advantages or advantageous effects: the first client identifier is obtained through the preset code segment returned by the server, so that the first client identifier can be quickly obtained, and the binding relationship between the first search client and the second search client can be conveniently established subsequently according to the first client identifier.

Further, acquiring a first client identifier of the first search client by executing the preset code segment includes:

and searching identification data corresponding to the client identification field in a local cookie file by executing the preset code segment, and taking the searched identification data as a first client identification of the first search client.

Accordingly, the above-described embodiments have the following advantages or advantageous effects: by searching the identification data corresponding to the client identification field in the cookie file and using the identification data as the first client identification, the first client identification representing the identity of the first search client is quickly acquired, so that the binding relationship between the first search client and the second search client is established according to the first client identification in the following process.

Further, sending a probe request carrying the first client identifier includes:

sending a probe request carrying a first client identifier for multiple times, wherein the probe request sent each time also carries an IP address in a preset IP address range, and a monitoring port number used for monitoring the probe request on a second search client, and the IP addresses in different probe requests are polled and increased progressively in the preset IP address range, so that the second search client monitors the probe request carrying the IP address matched with the IP address of the second search client; wherein the preset IP address range is an address range consisting of IP addresses that the second search client may have.

Accordingly, the above-described embodiments have the following advantages or advantageous effects: the method and the device can enable the probe request sent by the first search client to contain the IP address and the monitoring port number which are matched with the IP address and the monitoring port number of the second search client, so that the second search client can monitor the probe request sent by the first search client.

Further, the first user terminal is a PC, and the second user terminal is a mobile terminal.

Accordingly, the above-described embodiments have the following advantages or advantageous effects: the first search terminal on the PC can be associated with the second search terminal on the mobile terminal, so that the search result of the search performed on the PC by the user and/or the search result of the search performed on the terminal by the user can be optimized.

The embodiment of the application discloses a client identifier processing method, which is applied to a second search client configured on a second user terminal and comprises the following steps:

monitoring a detection request which is sent by a first search client and carries a first client identifier; the first search client is configured at the first user terminal;

and when the detection request is monitored, the first client identifier is sent to the server, so that the server establishes a binding relationship between the first client identifier and a second client identifier of a second search client.

The above embodiment has the following advantages or beneficial effects: the method comprises the steps of monitoring a detection request carrying a first client identifier, obtaining the first client identifier, and sending the first client identifier to a server, so that the server establishes a binding relationship between a first search client and a second search client, whether different clients are related or not can be determined based on the established binding relationship, whether users initiating searches on different clients are the same user or not can be determined, and then search results corresponding to search requests initiated by the users on the first search client and/or the second search client can be optimized based on the established binding relationship.

Further, monitoring a probe request carrying a first client identifier sent by a first search client, including:

monitoring a detection request which is sent by a first search client and carries a first client identifier, an IP address of a second search client and a monitoring port number; wherein the listening port number is a listening port number on the second search client for listening to probe requests.

Accordingly, the above-described embodiments have the following advantages or advantageous effects: the method comprises the steps of monitoring a detection request carrying a first client identifier, an IP address of a second search client and a monitoring port number, so that the IP address and the monitoring port number are accurately matched, and the first client identifier is quickly obtained.

The embodiment of the present application further discloses a client identifier processing apparatus, configured in the server, where the apparatus includes:

the first client identification receiving module is used for receiving a first client identification of the first search client sent by the second search client; the first search client is configured on the first user terminal, and the second search client is configured on the second user terminal;

the binding module is used for establishing a binding relationship between the first client identifier and a second client identifier of a second search client;

when monitoring a probe request sent by a first search client, a second search client obtains a first client identifier from the probe request.

Further, the apparatus further comprises:

the search request receiving module is used for receiving a search request sent by a first search client when the search triggering operation is detected;

and the search response message sending module is used for returning a search response message carrying a preset code segment to the first search client so that the first search client acquires a first client identifier of the first search client by executing the preset code segment and sends a detection request carrying the first client identifier.

Further, the apparatus further comprises:

the first optimization processing module is used for acquiring a first search result list according to a first search word in a first search request when the first search request sent by a first search client is received;

the second optimization processing module is used for acquiring a second search result list according to a second search word in a second search request when the second search request sent by a second search client is received;

Further, the first optimization processing module includes:

a first adding unit, configured to acquire second search result information from the second history search related information, and add the second search result information to the first search result list; and/or the presence of a gas in the gas,

the first result processing unit is used for acquiring click information of the user on the second search result information from the second historical search related information and processing the search results in the first search result list according to the click information;

correspondingly, the second optimization processing module includes:

the second adding unit is used for acquiring the first search result information from the first historical search related information and adding the first search result information to the second search result list; and/or the presence of a gas in the gas,

the second result processing unit is used for acquiring click information of the user on the first search result information from the first historical search related information and processing the search results in the second search result list according to the click information;

The embodiment of the present application further discloses a client identifier processing apparatus, configured at a first user terminal, where the apparatus includes:

the first client identification acquisition module is used for acquiring a first client identification of a first search client;

the detection request sending module is used for sending a detection request carrying a first client identifier so as to enable a second search client to send the first client identifier to a server when monitoring the detection request; the second search client is configured at the second user terminal.

Further, the apparatus further comprises:

the search request sending module is used for sending a search request to the server when the search triggering operation is detected;

the search response message receiving module is used for receiving a search response message returned by the server, wherein the search response message carries a preset code segment;

correspondingly, the probe request sending module includes:

a preset code segment acquiring unit, configured to acquire a preset code segment in the search response message;

and the preset code segment execution unit is used for acquiring a first client identifier of the first search client by executing the preset code segment, and sending a detection request carrying the first client identifier.

Further, the preset code segment execution unit is specifically configured to:

Further, the probe request sending module includes:

the multi-time sending unit is used for sending the detection request carrying the first client identifier for multiple times, wherein the detection request sent each time also carries an IP address in a preset IP address range, the monitoring port number used for monitoring the detection request is arranged on the second search client, and the IP addresses in different detection requests are progressively inquired in the preset IP address range, so that the second search client monitors the detection request carrying the IP address matched with the IP address of the second search client; wherein the preset IP address range is an address range consisting of IP addresses that the second search client may have.

The embodiment of the present application further discloses a client identifier processing apparatus configured at a second user terminal, the apparatus includes:

the monitoring module is used for monitoring a detection request which is sent by the first search client and carries the first client identifier; the first search client is configured at the first user terminal;

and the sending module is used for sending the first client identifier to the server side when the detection request is monitored, so that the server side establishes a binding relationship between the first client identifier and a second client identifier of the second search client.

Further, the listening module includes:

the detection request monitoring unit is used for monitoring a detection request which is sent by a first search client on a first user terminal and carries a first client identifier, an IP address of a second search client and a monitoring port number; wherein the listening port number is a listening port number on the second search client for listening to probe requests. The embodiment of the present application further discloses a user terminal, which includes: a first user terminal or a second user terminal, the first user terminal or the second user terminal comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor, when located at a first user terminal, to perform a method applied to a first search client on the first user terminal;

or enabling the at least one processor, when located at the second user terminal, to perform a method applied to a second search client configured at the second user terminal.

The embodiment of the present application further discloses a server, which includes:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method applied to a server as described in any one of the embodiments of the present application.

The embodiment of the present application further discloses a system, which is characterized by comprising: the system comprises a first user terminal, a second user terminal and a server;

the first user terminal is used for acquiring a first client identifier of a first search client; sending a detection request carrying a first client identifier;

the second user terminal is used for sending the first client identifier to the server side when the second search client monitors the detection request;

the server is used for receiving the first client identifier and establishing a binding relationship between the first client identifier and a second client identifier of a second search client;

the first search client is configured on the first user terminal, and the second search client is configured on the second user terminal.

Also disclosed in embodiments of the present application is a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the method applied to a first search client configured to a first user terminal, or applied to a second search client configured to a second user terminal, or applied to a server, as described in any one of the embodiments of the present application.

Other effects of the above-described alternative will be described below with reference to specific embodiments.

Drawings

The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:

fig. 1 is a flowchart illustrating a client identifier processing method applied to a first search client configured on a first user terminal according to an embodiment of the present application;

fig. 2 is a flowchart illustrating another client identifier processing method applied to a first search client configured on a first user terminal according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a client identifier processing method applied to a second search client configured on a second user terminal according to an embodiment of the present application;

fig. 4 is a flowchart illustrating a client identifier processing method applied to a server according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a client identifier processing apparatus configured at a first user terminal according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a client identifier processing apparatus configured in a second user terminal according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a client identifier processing apparatus configured in a server according to an embodiment of the present application;

FIG. 8 is a block diagram of a system for implementing a client identification processing method of an embodiment of the present application;

fig. 9 is a block diagram of a user terminal for implementing the client identifier processing method according to the embodiment of the present application.

Detailed Description

The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Fig. 1 is a flowchart illustrating a client identifier processing method applied to a first search client configured on a first user terminal according to an embodiment of the present application. The embodiment can be applied to the optimization of the search results of the search client. Typically, the present embodiment is applicable to a case where the search results of other search clients bound to the search client are optimized according to the search result information of the search client. The client identifier processing disclosed in this embodiment may be executed by a client identifier processing apparatus, which may be implemented by software and/or hardware and configured in the first user terminal. Referring to fig. 1, the client identifier processing method applied to the first search client configured on the first user terminal provided in this embodiment includes:

s110, a first client identification of the first search client is obtained.

The first user terminal may be a PC or a mobile terminal. Correspondingly, the corresponding second user terminal may also be a PC or a mobile terminal. In the embodiment of the present application, in order to explain the scheme in the embodiment in view of different situations of the user terminals, the first user terminal is a PC, and the second user terminal is a mobile terminal. The embodiment of the application is also suitable for the case that the first user terminal is a PC, the second user terminal is a PC, or the first user terminal is a mobile terminal, and the second user terminal is a mobile terminal. The first search client may be a client installed on the first user terminal for searching information. The first client identification is used to mark the identity of the first search client, such as the first search client IP address, network media type and MAC address or client ID, etc.

Specifically, in order to enable the search result of the client and the search result of the client bound to the client to be mutually optimized, the clients in the local area network are bound or associated. Different clients can be bound according to the client identification, so that the first client identification of the first search client is obtained, and the user marks the unique identity of the first client, thereby facilitating the subsequent establishment of binding relations with other clients.

S120, sending a detection request carrying a first client identifier, so that when a second search client monitors the detection request, the first client identifier is sent to a server, and the server establishes a binding relationship between the first client identifier and a second client identifier of the second search client; the second search client is configured at the second user terminal.

Wherein the probe request may be transmitted in a broadcast form so that the second search client in the local area network can listen to the probe request. The detection request carries a first client identifier, so that a binding relationship between the first search client and the second search client is established according to the second client identifier.

For example, if the second search client can listen to the probe request sent by the first search client, it may be considered that an association exists between the first search client and the second search client, and the association may be bound to the first search client and the second search client. The first search client and the second search client may be search clients used by the same user and initiating a search, or search clients used by different users and initiating a search. Therefore, when the second search client monitors the detection request, the first client identifier carried in the detection request is sent to the server, the second client identifier of the second search client is sent to the server, and the server establishes a binding relationship between the first client identifier and the second client identifier. In addition, since the second search client can access the server when initiating a search, the server can obtain the user identifier of the second search client, and the server can establish a binding relationship between the first client identifier sent by the second search client and the user identifier of the second search client, thereby associating the first search client with the second search client.

Optionally, sending the probe request carrying the first client identifier includes: sending a probe request carrying a first client identifier for multiple times, wherein the probe request sent each time also carries an IP address in a preset IP address range, and a monitoring port number used for monitoring the probe request on a second search client, and the IP addresses in different probe requests are polled and increased progressively in the preset IP address range, so that the second search client monitors the probe request carrying the IP address matched with the IP address of the second search client; wherein the preset IP address range is an address range consisting of IP addresses that the second search client may have.

For example, since the first search client does not necessarily have to be monitored by the second search client in the local area network when sending the probe request once, the first search client sends the probe request carrying the identifier of the first search client many times, so that the second search client can monitor the next probe request sent by the first search client when not monitoring the current probe request. In addition, since the second search client can listen to the probe request if the IP address and the listening port number carried by the probe request match the IP address and the listening port number of the second search client. Therefore, each probe request sent by the first search client carries an IP address in a preset address range, for example, the IP address is 192.168.1.20, and the listening port number of the second search client is, for example, 12345, so that the second search client can listen to the probe request according to the IP address and the listening port number. Because the first search client cannot know which IP address and monitoring port number of the second search client monitors the probe request, the polling of the IP addresses in the probe request sent by the first search client is increased progressively to match the IP addresses of the second search client one by one, so that the second search client accurately monitors the probe request.

According to the technical scheme of the embodiment of the application, the first client identification of the first search client is obtained, the detection request carrying the first client identification is sent, so that the second search client on the second user terminal monitors the detection request, the first client identification is sent to the server, the server establishes a binding relationship between the first client identification and the second client identification of the second search client, whether the different clients are related or not can be known based on the established binding relationship, whether users initiating searches on the different clients are the same user can be known, and then the search results corresponding to the search requests initiated by the users at the first search client and/or the second search client can be optimized based on the established binding relationship.

Fig. 2 is a flowchart illustrating another client identifier processing method applied to a first search client configured on a first user terminal according to an embodiment of the present application. The present embodiment is an alternative proposed on the basis of the above-described embodiments. Referring to fig. 2, the client identifier processing method provided in this embodiment includes:

s210, when the search triggering operation is detected, a search request is sent to the server.

The search triggering operation may be an operation that a user acts on the user terminal to trigger the user terminal to perform a search. When detecting the search trigger operation, the first search client on the first user terminal sends a search request to the server, so that the server returns a corresponding search response message according to the search request.

S220, receiving a search response message returned by the server, wherein the search response message carries the preset code segment.

For example, in order to enable the first search client to obtain the first client identifier, the server responds to a search request sent by the first search client, and sends a search response message carrying a preset code segment, which is generated in response to the search request, to the first search client, and the first search client receives the search response message carrying the preset code segment, so that the first search client can obtain the first client identifier subsequently according to the preset code segment.

And S230, acquiring a preset code segment in the search response message.

Illustratively, the first search client obtains the preset code segment from the search response message, so as to facilitate obtaining the first client identifier through the preset code segment subsequently.

S240, acquiring a first client identifier of the first search client by executing the preset code segment, and sending a detection request carrying the first client identifier, so that when a second search client on the second user terminal monitors the detection request, the first client identifier is sent to the server, and the server establishes a binding relationship between the first client identifier and a second client identifier of the second search client.

Illustratively, the preset code segment may be used to obtain a first client identifier of the first search client, and the first search client executes the preset code segment to obtain the first client identifier thereof, so as to send a probe request carrying the first client identifier, so that the second search client receives the probe request carrying the first client identifier, and sends the first client identifier to the server for binding.

Optionally, the obtaining a first client identifier of the first search client by executing the preset code segment includes: and searching identification data corresponding to the client identification field in a local cookie file by executing the preset code segment, and taking the searched identification data as a first client identification of the first search client.

The cookie file may be used to identify the identity of the client, and therefore, the cookie file may include identification data for identifying the identity of the first search client, and the identification data is used as the first client identifier of the first search client to clarify the identity of the first search client.

According to the embodiment of the application, the search response message returned by the server is received, the preset code segment in the search response message is obtained, and the preset code segment is executed to obtain the first client identifier, so that the first client identifier is obtained quickly and efficiently, the server can conveniently establish the binding relationship between the first client identifier and the second client identifier of the second search client, whether different clients are associated or not can be obtained based on the established binding relationship, that is, whether users initiating searches on different clients are the same user or not can be obtained, and then the search results corresponding to the search requests initiated by the users at the first search client and/or the second search client can be optimized based on the established binding relationship.

Fig. 3 is a flowchart illustrating a client identifier processing method applied to a second search client configured on a second user terminal according to an embodiment of the present application. The embodiment can be applied to the optimization of the search results of the search client. Typically, the present embodiment is applicable to a case where the search results of other search clients bound to the search client are optimized according to the search result information of the search client. The client identifier processing disclosed in this embodiment may be executed by a client identifier processing apparatus, which may be implemented by software and/or hardware and configured in the second user terminal. For details that are not described in detail, for example, the term concept explanation and the like are described in detail in the above embodiments, referring to fig. 3, the client identifier processing method applied to the client provided in this embodiment includes:

s310, monitoring a detection request which is sent by a first search client and carries a first client identifier; the first search client is configured at the first user terminal.

For example, the second user terminal is in a probe request monitoring state, and may monitor a probe request carrying a first client identifier sent by a first search client of the first user terminal in the local area network.

Optionally, monitoring a probe request carrying a first client identifier sent by a first search client includes: monitoring a detection request which is sent by a first search client on a first user terminal and carries a first client identifier, an IP address of a second search client and a monitoring port number; wherein the listening port number is a listening port number on the second search client for listening to probe requests.

For example, in order to monitor the probe request sent by the first search client in time, the second search client monitors the probe request, and determines whether to match the IP and the monitoring port number of the second search client, which are carried in the probe request, according to the IP and the monitoring port number of the second search client. And if the matching is carried out, monitoring the detection request to acquire the first client identifier carried in the detection request.

S320, when the detection request is monitored, the first client identifier is sent to the server, so that the server establishes a binding relationship between the first client identifier and a second client identifier of a second search client.

For example, if the second search client on the second user terminal can listen to the probe request sent by the first search client, it may be considered that an association exists between the first search client and the second search client, and the association may be bound to the first search client and the second search client. Therefore, when the second search client on the second user terminal monitors the probe request, the first client identifier carried in the probe request is sent to the server, the second client identifier of the second search client can be sent to the server, and the server establishes the binding relationship between the first client identifier and the second client identifier. The second search client may obtain the second client identifier in the same manner as the first search client identifier, or may directly execute the corresponding code segment to obtain the code segment. In addition, since the second search client can access the server when initiating a search, the server can obtain the user identifier of the second search client, and the server can establish a binding relationship between the first client identifier sent by the second search client and the user identifier of the second search client, thereby associating the first search client with the second search client.

According to the technical scheme of the embodiment of the application, the detection request carrying the first client identifier is monitored, the first client identifier is obtained, and the first client identifier is sent to the server, so that the server establishes the binding relationship between the first search client and the second search client, whether the different clients are related or not can be known based on the established binding relationship, whether users initiating searches on the different clients are the same user or not can be known, and then the search results corresponding to the search requests initiated by the users at the first search client and/or the second search client can be optimized based on the established binding relationship.

Fig. 4 is a flowchart illustrating a client identifier processing method applied to a server according to an embodiment of the present application. The embodiment can be applied to the optimization of the search results of the search client. Typically, the present embodiment is applicable to a case where the search results of other search clients bound to the search client are optimized according to the search result information of the search client. The client identification processing disclosed in this embodiment may be performed by a client identification processing apparatus, which may be implemented by software and/or hardware and configured in a server. For details that are not described in detail, for example, the term concept explanation and the like are described in detail in the above embodiments, referring to fig. 4, the method for processing the client identifier applied to the server provided in this embodiment includes:

s410, receiving a first client identifier of the first search client sent by the second search client. The first search client is configured on the first user terminal, and the second search client is configured on the second user terminal.

Illustratively, a first search client acquires a first client identifier of the first search client and sends a detection request carrying the first client identifier in a broadcast manner, and a second search client monitors the detection request carrying the first client identifier sent by the first search client and sends the first client identifier to a server when monitoring the detection request. And the server receives a first client identifier of the first search client sent by a second search client on the second user terminal. The second search client may obtain the second client identifier and send the second client identifier to the server. Since the second search client can access the server when initiating a search, the server can also obtain the user identifier of the second search client.

S420, establishing a binding relationship between the first client identifier and a second client identifier of a second search client; when monitoring a probe request sent by a first search client, a second search client obtains a first client identifier from the probe request.

For example, in order to associate the first search client with the second search client, and to bind the search result of the client bound to the first search client according to the search result of one of the clients, the server receives the first client identifier of the first search client on the first user terminal sent by the second search client on the second user terminal, and establishes a binding relationship, thereby facilitating mutual optimization processing of the search results of the search clients having the binding relationship.

The second client identifier may be, for example, an application identifier of the second search client, or may be an identifier of a user who logs in the second search client. If the second search client can monitor the probe request sent by the first search client, it may be considered that there is a relationship between the first search client and the second search client, for example, a first user terminal where the first search client is located and a second user terminal where the second search client is located are in the same local area network, and thus, they may be bound. The first search client and the second search client may be search clients used by the same user and initiating a search, or search clients used by different users and initiating a search. Therefore, when the second search client monitors the detection request, the first client identifier carried in the detection request is sent to the server, the second client identifier of the second search client is sent to the server, and the server establishes a binding relationship between the first client identifier and the second client identifier. In addition, since the second search client can access the server when initiating a search, the server can obtain the user identifier of the second search client, and the server can establish a binding relationship between the first client identifier sent by the second search client and the user identifier of the second search client, thereby associating the first search client with the second search client.

Optionally, before receiving the first client identifier sent by the second search client, the method further includes: receiving a search request sent by a first search client when a search trigger operation is detected; and returning a search response message carrying a preset code segment to the first search client, so that the first search client acquires a first client identifier of the first search client by executing the preset code segment and sends a detection request carrying the first client identifier.

For example, the search triggering operation may be an operation that the user acts on the user terminal to trigger the user terminal to perform a search. When detecting a search trigger operation, a first search client on a first user terminal sends a search request to a server, and the server returns a corresponding search response message carrying a preset code segment according to the search request. And the first search client acquires a first client identifier of the first search client by executing the preset code segment, and sends a detection request carrying the first client identifier.

Optionally, after establishing a binding relationship between the first client identifier and the second client identifier or the user identifier logged in the second search client, the method further includes: when a first search request sent by a first search client is received, acquiring a first search result list according to a first search word in the first search request; acquiring second historical search related information of a second search client based on the binding relationship, and optimizing the first search result list according to the second historical search related information; returning the optimized first search result list to the first search client for displaying; and/or when a second search request sent by a second search client is received, acquiring a second search result list according to a second search word in the second search request; based on the binding relationship, acquiring first historical search related information of the first search client, and performing optimization processing on the second search result list according to the first historical search related information; and returning the optimized second search result list to the second search client for displaying.

The first historical search related information may be historical search result information generated in response to a historical search request acted on the first search client by a user, and the second historical search related information may be historical search result information generated in response to a historical search request acted on the second search client by a user, such as a search result and the like. Illustratively, the server obtains a search result list corresponding to a first search request according to the first search request sent by the first search client to be displayed to the user, or the server obtains a search result list corresponding to a second search request according to the second search request sent by the second search client to be displayed to the user. Since the search result list is not necessarily the optimal search result list, and may not meet the search requirement of the user, the search result list needs to be optimized. Because the second search client bound with the first search client is in the same local area network and monitors the first search client, the first search client and the second search client have relevance, and the search result list of the first search client can be optimized according to the second historical search related information of the second search client. Or optimizing the search result list of the second search client according to the first search related information of the first search client.

Optionally, performing optimization processing on the first search result list according to the second historical search related information includes: acquiring second search result information from the second historical search related information, and adding the second search result information to the first search result list; and/or acquiring click information of the user on the second search result information from the second historical search related information, and processing the search result in the first search result list according to the click information; correspondingly, the optimizing processing of the second search result list according to the first historical search information includes: acquiring first search result information from the first historical search related information, and adding the first search result information to a second search result list; and/or acquiring click information of the user on the first search result information from the first historical search related information, and processing the search results in the second search result list according to the click information; the first search result information is history search result information obtained aiming at history search words sent by the first search client, and the second search result information is history search result information obtained aiming at history search words sent by the second search client.

For example, the second search result information in the second search related information of the second search client may be directly added to the first search result list to supplement the first search result list, or click information of the user on the second search result information, such as click rate, may be determined, and the second search result information with high click rate may be added to the first search result list. Or, the first search result information in the first search related information of the first search client may be directly added to the second search result list to supplement the second search result list, or click information of the user on the first search result information, such as a click rate, may be determined, and the first search result information with a high click rate is added to the second search result list.

According to the technical scheme of the embodiment of the application, the server receives the first client identifier and establishes the binding relationship between the first search client and the second search client, so that whether different clients are associated or not can be known based on the established binding relationship, that is, whether users initiating searches on different clients are the same user or not can be known, and further, the search results corresponding to the search requests initiated by the users at the first search client and/or the second search client can be optimized based on the established binding relationship.

Fig. 5 is a schematic structural diagram of a client identifier processing apparatus configured at a first user terminal according to an embodiment of the present application. Referring to fig. 5, an embodiment of the present application discloses a client identifier processing apparatus 500 configured at a first user terminal, where the apparatus 500 includes: a first client identity obtaining module 501 and a probe request sending module 502.

The first client identifier obtaining module 501 is configured to obtain a first client identifier of a first search client;

a probe request sending module 502, configured to send a probe request carrying a first client identifier, so that when a second search client monitors the probe request, the first client identifier is sent to a server, so that the server establishes a binding relationship between the first client identifier and a second client identifier of the second search client; the second search client is configured at the second user terminal.

Further, the apparatus further comprises:

accordingly, the probe request sending module 502 includes:

Further, the preset code segment execution unit is specifically configured to:

Further, the probe request sending module 502 includes:

The client identifier processing apparatus provided in the embodiment of the present application may execute the client identifier processing method applied to the first search client configured in the first user terminal provided in any embodiment of the present application, and has functional modules and beneficial effects corresponding to the execution method.

Fig. 6 is a schematic structural diagram of a client identifier processing apparatus configured in a second user terminal according to an embodiment of the present application. Referring to fig. 6, an embodiment of the present application discloses a client identifier processing apparatus 600 configured at a second user terminal, where the apparatus 600 includes: a listening module 601 and a sending module 602.

A monitoring module 601, configured to monitor a probe request carrying a first client identifier sent by a first search client; the first search client is configured at the first user terminal;

a sending module 602, configured to send the first client identifier to the server when the probe request is monitored, so that the server establishes a binding relationship between the first client identifier and a second client identifier of a second search client.

Further, the listening module 601 includes:

the detection request monitoring unit is used for monitoring a detection request which is sent by a first search client on a first user terminal and carries a first client identifier, an IP address of a second search client and a monitoring port number; wherein the listening port number is a listening port number on the second search client for listening to probe requests.

The client identifier processing apparatus provided in the embodiment of the present application may execute the client identifier processing method applied to the second search client configured in the second user terminal provided in any embodiment of the present application, and has functional modules and beneficial effects corresponding to the execution method.

Fig. 7 is a schematic structural diagram of a client identifier processing apparatus configured in a server according to an embodiment of the present application. Referring to fig. 7, an embodiment of the present application discloses a client identifier processing apparatus 700 configured on a server, where the apparatus 700 includes: a first client identity receiving module 701 and a binding module 702.

The first client identifier receiving module 701 is configured to receive a first client identifier of a first search client sent by a second search client; the first search client is configured on the first user terminal, and the second search client is configured on the second user terminal;

a binding module 702, configured to establish a binding relationship between the first client identifier and a second client identifier of a second search client;

Further, the apparatus further comprises:

Further, the device also comprises:

Further, the first optimization processing module includes:

correspondingly, the second optimization processing module includes:

The client identifier processing device provided by the embodiment of the application can execute the client identifier processing method applied to the server and provided by any embodiment of the application, and has corresponding functional modules and beneficial effects of the execution method.

According to an embodiment of the present application, there is also provided a system, as shown in fig. 8, fig. 8 is a block diagram of a system for implementing a client identifier processing method according to an embodiment of the present application, where the system 800 includes: a first user terminal 801, a second user terminal 802, and a server 803;

the first user terminal 801 is configured to execute a client identifier processing method applied to a first search client configured in the first user terminal 801, and includes:

acquiring a first client identifier of a first search client;

and sending a detection request carrying the first client identifier so that the second search client sends the first client identifier to the server when monitoring the detection request, and the server establishes a binding relationship between the first client identifier and the second client identifier of the second search client. The second search client is configured at the second user terminal 802.

Further, the first user terminal 801 is further configured to, before obtaining the first client identifier of the first search client:

correspondingly, the first user terminal 801 is specifically configured to:

acquiring a preset code segment in the search response message;

Further, the first user terminal 801 is specifically configured to:

Further, the first user terminal 801 is a PC, and the second user terminal 802 is a mobile terminal.

The second user terminal 802 is configured to execute a client identifier processing method applied to a second search client on the second user terminal 802, including:

monitoring a detection request which is sent by a first search client and carries a first client identifier; wherein, the first search client is configured at the first user terminal 801;

Further, the second user terminal 802 is specifically configured to:

The server 803 is configured to execute a client identifier processing method applied to a server, and includes:

receiving a first client identifier of a first search client sent by a second search client; the first search client is configured on the first user terminal 801, and the second search client is configured on the second user terminal 802;

Further, the server 803 is further configured to, before receiving the first client identifier sent by the second search client:

Further, the server 803 is further configured to, after establishing the binding relationship between the first client identifier and the second client identifier or the user identifier of the logged-in second search client:

Further, the server 803 is specifically configured to:

According to the embodiment of the application, the first client identification of the first search client is obtained through the first user terminal, the detection request carrying the first client identification is sent, the second search client on the second user terminal monitors the detection request, the first client identification is sent to the server, the server establishes the binding relationship between the first client identification and the second client identification of the second search client, whether the different clients are related or not can be known based on the established binding relationship, whether the users initiating the search on the different clients are the same user can be known, and then the search results corresponding to the search requests initiated by the users at the first search client and/or the second search client can be optimized based on the established binding relationship.

According to an embodiment of the present application, a user terminal and a readable storage medium are also provided.

As shown in fig. 9, fig. 9 is a block diagram of a user terminal for implementing the client identifier processing method according to the embodiment of the present application. The user terminal includes: a first user terminal or a second user terminal. User terminals are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The user terminal may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable servers, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.

As shown in fig. 9, the user terminal includes: one or more processors 901, memory 902, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the server, including instructions stored in or on the memory to display graphical information of the GUI on an external input/output device (such as a display server coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple servers may be connected, with each server providing portions of the necessary operations (e.g., as an array of servers, a group of blade servers, or a multi-processor system). Fig. 9 illustrates an example of a processor 901.

Memory 902 is a non-transitory computer readable storage medium as provided herein. The memory stores instructions executable by the at least one processor to cause the at least one processor to perform a user terminal identification processing method applied to a first search client configured to a first user terminal or a user terminal identification processing method applied to a second search client configured to a second user terminal as provided herein. A non-transitory computer-readable storage medium of the present application stores computer instructions for causing a computer to execute a user terminal identification processing method applied to a first search client configured to a first user terminal or a user terminal identification processing method applied to a second search client configured to a second user terminal, as provided by the present application.

The memory 902 may be used as a non-transitory computer readable storage medium for storing non-transitory software programs, non-transitory computer executable programs, and modules, such as a user terminal identifier processing method applied to a first search client configured to a first user terminal or program instructions/modules corresponding to a user terminal identifier processing method applied to a second search client configured to a second user terminal (for example, the first user terminal identifier obtaining module 501 and the probe request sending module 502 shown in fig. 5, or the listening module 601 and the sending module 602 shown in fig. 6) in the embodiments of the present application. The processor 901 executes various functional applications and searches of the server by running non-transitory software programs, instructions and modules stored in the memory 902, that is, implementing the user terminal identification processing method applied to the first search client configured to the first user terminal or the user terminal identification processing method applied to the second search client configured to the second user terminal in the above method embodiments.

The memory 902 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the searched server, and the like. Further, the memory 902 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 902 may optionally include memory located remotely from the processor 901, which may be connected to a search service via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The user terminal of the client identifier processing method may further include: an input device 903 and an output device 904. The processor 901, the memory 902, the input device 903 and the output device 904 may be connected by a bus or other means, and fig. 9 illustrates the connection by a bus as an example.

The input device 903 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the searched server, such as an input device such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointing stick, one or more mouse buttons, a track ball, a joystick, etc. The output devices 904 may include a display server, auxiliary lighting devices (e.g., LEDs), tactile feedback devices (e.g., vibrating motors), and the like. The display service may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some embodiments, the display server may be a touch screen.

Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, server, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), the internet, and blockchain networks.

The computer system may include a user terminal and a server. The user terminal and the server are generally remote from each other and typically interact through a communication network. The relationship of user terminal and server arises by virtue of computer programs running on the respective computers and having a user terminal-server relationship to each other.

According to an embodiment of the present application, a server and a readable storage medium are also provided.

The server includes:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform client identification processing applied to a server.

The readable storage medium terminates storage of computer instructions for causing a computer to perform client identification processing applied to a server.

A block diagram and a detailed explanation of a server and a readable storage medium are the same as those of the first user terminal and the readable storage medium applied to the client identification processing method of the first search client configured to the first user terminal or the second user terminal and the readable storage medium applied to the client identification processing method of the second search client configured to the second user terminal, see the above-described embodiments.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.

The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A client identification processing method is applied to a server and comprises the following steps:

establishing a binding relationship between the first client identification and a second client identification of a second search client;

2. The method of claim 1, wherein prior to receiving the first client identification sent by the second search client, the method further comprises:

3. The method of claim 1, wherein after establishing the binding relationship between the first client identifier and the second client identifier, the method further comprises:

acquiring second historical search related information of a second search client based on the binding relationship, and optimizing the first search result list according to the second historical search related information;

returning the optimized first search result list to the first search client for displaying; and/or the presence of a gas in the gas,

based on the binding relationship, acquiring first historical search related information of the first search client, and performing optimization processing on the second search result list according to the first historical search related information;

and returning the optimized second search result list to the second search client for displaying.

4. The method of claim 3, wherein optimizing the first search result list based on the second historical search related information comprises:

5. A method for processing a client identifier, applied to a first search client configured in a first user terminal, includes:

acquiring a first client identifier of a first search client;

and sending a detection request carrying the first client identifier so that a second search client sends the first client identifier to a server when monitoring the detection request, wherein the second search client is configured at a second user terminal.

6. The method of claim 5, wherein prior to obtaining the first client identification of the first search client, the method further comprises:

acquiring a preset code segment in the search response message;

7. The method of claim 6, wherein obtaining the first client identifier of the first search client by executing the preset code segment comprises:

8. The method of claim 5, wherein sending the probe request carrying the first client identifier comprises:

9. The method of claim 5, wherein the first user terminal is a PC and the second user terminal is a mobile terminal.

10. A client identification processing method is applied to a second search client configured on a second user terminal, and comprises the following steps:

11. The method of claim 10, wherein monitoring a probe request carrying a first client identifier sent by a first search client comprises:

12. A client identifier processing apparatus, configured to a server, the apparatus comprising:

13. A client identifier processing apparatus, configured to be disposed in a first user terminal, the apparatus comprising:

and the detection request sending module is used for sending a detection request carrying the first client identifier so as to enable a second search client to send the first client identifier to the server when monitoring the detection request, wherein the second search client is configured at a second user terminal.

14. A client identifier processing apparatus, configured to be provided in a second user terminal, the apparatus comprising:

15. A user terminal, comprising: a first user terminal or a second user terminal, the first user terminal or the second user terminal comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to cause the at least one processor, when located in a first user terminal, to perform a method as claimed in any of claims 5 to 9 applied to a first search client deployed at the first user terminal; alternatively, the first and second electrodes may be,

enabling the at least one processor, when located at a second user terminal, to perform the method of any of claims 10-11 applied to a second search client configured at the second user terminal.

16. A server, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-4 applied to a server.

17. A system, comprising: the system comprises a first user terminal, a second user terminal and a server;

the server is used for receiving the first client identifier and establishing a binding relationship between the first client identifier and a second client identifier of a second search client; the first search client is configured on the first user terminal, and the second search client is configured on the second user terminal.

18. A non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the method of any one of claims 5 to 9 applied to a first search client configured to a first user terminal, or the method of any one of claims 10 to 11 applied to a second search client configured to a second user terminal, or the method of any one of claims 1 to 4 applied to a server.