CN106874471B - Information pushing method and device - Google Patents
Information pushing method and device Download PDFInfo
- Publication number
- CN106874471B CN106874471B CN201710083553.1A CN201710083553A CN106874471B CN 106874471 B CN106874471 B CN 106874471B CN 201710083553 A CN201710083553 A CN 201710083553A CN 106874471 B CN106874471 B CN 106874471B
- Authority
- CN
- China
- Prior art keywords
- identifier
- client
- user
- user identifier
- website
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
Abstract
The application discloses an information pushing method and device. One embodiment of the method comprises: receiving a sharing request for a target webpage sent by a first client, wherein the sharing request comprises a first user identifier and a page identifier of the target webpage; generating a first identifier based on the first user identifier and the page identifier, and generating a first website with the first identifier for indicating the target webpage; in response to receiving a first webpage query request containing the first website sent by a second client, determining a second user identifier, and executing the following mapping establishment steps: generating a second identifier based on the second user identifier and the page identifier; establishing mapping between the first identifier and the second identifier; and pushing preset information to each client associated with the established mapping. The embodiment realizes targeted information push.
Description
Technical Field
The application relates to the technical field of computers, in particular to the technical field of internet, and particularly relates to an information pushing method and device.
Background
With the development of computer technology, the functions of websites and client applications are more and more abundant. Existing websites may include Social Networking Sites (SNS) and non-Social websites, and existing client applications may include Social applications (e.g., microblog-like applications, instant messaging-like applications, etc.) and non-Social applications (e.g., tool-like applications, reading-like applications, image-like applications, etc.).
For a non-social network site and a non-social client application, because each user is independent of each other, a server cannot directly obtain user relationships among a plurality of users from usage behavior data of the users, and thus, an existing method for pushing information to the users is generally to directly push information to randomly selected users. Therefore, the existing information pushing method has the problem of lack of pertinence in information pushing.
Disclosure of Invention
The present application aims to provide an improved information pushing method and apparatus to solve the technical problems mentioned in the above background section.
In a first aspect, the present application provides an information pushing method, including: receiving a sharing request for a target webpage sent by a first client, wherein the sharing request comprises a first user identifier and a page identifier of the target webpage; generating a first identifier based on the first user identifier and the page identifier, and generating a first website with the first identifier for indicating a target webpage; in response to receiving a first webpage query request containing a first website sent by a second client, determining a second user identifier, and executing the following mapping establishment steps: generating a second identifier based on the second user identifier and the page identifier; establishing mapping of a first identifier and a second identifier; and pushing preset information to each client associated with the established mapping.
In some embodiments, the mapping establishing step further comprises: and establishing mapping of the first user identification and the second user identification.
In some embodiments, the method further comprises: generating a second website with a second identifier for indicating the target webpage; and returning the second website to the second client side so that the second client side displays the target webpage indicated by the second website.
In some embodiments, the method further comprises: determining a third user identifier in response to receiving a second webpage query request containing a second website sent by a third client; and taking the third user identification as a second user identification and the second identification as a first identification, and continuing to execute the mapping establishing step.
In some embodiments, generating the first identity based on the first user identity and the page identity comprises: and combining the first user identification and the page identification to generate a first identification.
In some embodiments, generating the first identity based on the first user identity and the page identity comprises: combining the first user identification and the page identification to generate a combined identification; and processing the combined identifier by using an encryption algorithm to generate a first identifier.
In some embodiments, determining the second user identifier in response to receiving the first web page query request containing the first web address sent by the second client includes: in response to receiving a first webpage query request which is sent by a second client and contains a first website, determining whether the first webpage query request contains a user identifier; in response to determining that the first webpage query request contains the user identifier, matching the user identifier contained in the first webpage query request with the first user identifier; in response to a mismatch, the user identification contained in the first web page query request is determined to be the second user identification.
In some embodiments, determining the second user identifier in response to receiving a first web page query request containing the first web address sent by the second client further includes: in response to determining that the user identification is not included in the first web page query request, a second user identification associated with the second client is randomly generated.
In some embodiments, the first client installs a target application, and the sharing request is sent by the first client through the target application; and after receiving a first webpage query request containing a first website sent by a second client, the method further comprises the following steps: and sending an opening instruction of the target application to the second client.
In some embodiments, before sending the opening instruction of the target application to the second client, the method further comprises: generating a download address of an installation package of a target application with a first user identifier and a first identifier; and sending the download address to the second client so that the second client installs or updates the target application.
In a second aspect, the present application provides an information pushing apparatus, including: the device comprises a receiving unit and a processing unit, wherein the receiving unit is configured to receive a sharing request for a target webpage sent by a first client, and the sharing request comprises a first user identifier and a page identifier of the target webpage; the first generation unit is configured to generate a first identifier based on the first user identifier and the page identifier, and generate a first website with the first identifier for indicating the target webpage; the first determining unit is configured to determine a second user identifier in response to receiving a first webpage query request containing a first website sent by a second client, and execute the following mapping establishing steps: generating a second identifier based on the second user identifier and the page identifier; establishing mapping of a first identifier and a second identifier; and the pushing unit is configured to push the preset information to each client associated with the established mapping.
In some embodiments, the first determining unit is further configured to: and establishing mapping of the first user identification and the second user identification.
In some embodiments, the apparatus further comprises: the second generation unit is used for generating a second website with a second identifier for indicating the target webpage; and the returning unit is configured to return the second website to the second client, so that the second client displays the target webpage indicated by the second website.
In some embodiments, the apparatus further comprises: the second determining unit is configured to determine a third user identifier in response to receiving a second webpage query request containing a second website sent by a third client; and the execution unit is configured to take the third user identifier as a second user identifier and take the second identifier as a first identifier, so that the first determination unit continues to execute the mapping establishing step.
In some embodiments, the first generating unit is further configured to: and combining the first user identification and the page identification to generate a first identification.
In some embodiments, the first generating unit is further configured to: combining the first user identification and the page identification to generate a combined identification; and processing the combined identifier by using an encryption algorithm to generate a first identifier.
In some embodiments, the first determination unit comprises: the first determining module is configured to determine whether a first webpage query request containing a first website sent by a second client contains a user identifier or not in response to receiving the first webpage query request; the matching module is configured to match the user identifier contained in the first webpage query request with the first user identifier in response to the fact that the first webpage query request contains the user identifier; and the second determining module is configured to determine the user identifier contained in the first webpage query request as the second user identifier in response to the mismatch.
In some embodiments, the first determination unit further comprises: and the generating module is configured to randomly generate a second user identifier associated with the second client in response to determining that the first webpage query request does not contain the user identifier.
In some embodiments, the first client installs a target application, and the sharing request is sent by the first client through the target application; and the apparatus further comprises: and the first sending unit is configured to send an opening instruction of the target application to the second client.
In some embodiments, the apparatus further comprises: the third generation unit is used for generating a download address of the installation package of the target application with the first user identification and the first identification; and the second sending unit is configured to send the download address to the second client so that the second client installs or updates the target application.
According to the information pushing method and device, first identification and a first website are generated based on a first user identification and a page identification in a sharing request sent by a first client; then, in response to receiving a first webpage query request sent by a second client, determining a second user identifier so as to generate a second identifier and establish mapping between the first identifier and the second identifier; and finally, the preset information is pushed to each client associated with the mapping, so that a plurality of users are associated, and further targeted information pushing is realized.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of an information push method according to the present application;
FIG. 3 is an exploded flow chart of the map building step in the flow chart of FIG. 2;
FIG. 4 is a schematic diagram of an application scenario of an information push method according to the present application;
FIG. 5 is a flow diagram of yet another embodiment of an information push method according to the present application;
FIG. 6 is a schematic diagram of yet another application scenario of an information push method according to the present application;
FIG. 7 is a flow diagram of yet another embodiment of an information push method according to the present application;
FIG. 8 is a schematic diagram of an embodiment of an information pushing device according to the present application;
FIG. 9 is a block diagram of a computer system suitable for use in implementing a server according to embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 shows an exemplary system architecture 100 to which the information push method or the information push apparatus of the present application can be applied.
As shown in fig. 1, the system architecture 100 may include first terminal devices 101, 102, 103, networks 104, 106, a server 105 and second terminal devices 107, 108, 109. The networks 104, 106 are used to provide a medium for communication links between the first terminal devices 101, 102, 103, the server 105, and the second terminal devices 107, 108, 109. The networks 104, 106 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may use the first terminal device 101, 102, 103 to interact with the server 105 through the network 104, and send information such as a sharing request. In addition, the user may use the second terminal device 107, 108, 109 to interact with the server 105 via the network 106 to send information such as a web page query request. Various communication client applications, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the first terminal device 101, 102, 103 and the second terminal device 107, 108, 109. It should be noted that the terminal device may include a plurality of clients, for example, a first client, a second client, and the like.
The first terminal devices 101, 102, 103 and the second terminal devices 107, 108, 109 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, motion Picture Experts compression standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, motion Picture Experts compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background server providing support for applications or web pages displayed on the first terminal device 101, 102, 103 and the second terminal device 107, 108, 109. The background server may analyze and otherwise process the received data such as the sharing request and the web page query request, generate an identifier, a map, and the like, and may also push information to the first terminal devices 101, 102, and 103 and the second terminal devices 107, 108, and 109 through the networks 104 and 106.
It should be noted that the information pushing method provided in the embodiment of the present application is generally executed by the server 105, and accordingly, the information pushing apparatus is generally disposed in the server 105.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of first terminal devices, second terminal devices, networks, and servers, as desired for implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of an information push method according to the present application is shown. The information pushing method comprises the following steps:
In this embodiment, an electronic device (for example, a server shown in fig. 1) on which an information push method operates may receive, through a wired connection manner or a wireless connection manner, a sharing request for a target webpage sent by a first client (for example, first terminal devices 101, 102, and 103 shown in fig. 1), where the sharing request includes a first user identifier and a page identifier of the target webpage. It should be noted that, the electronic device may determine the user who sends the sharing request through the first client as a first user, and the first user identifier may be a character string composed of various characters (e.g., letters, numbers, symbols, etc.) for indicating and uniquely determining the first user; the page identifier may be a character string composed of various characters for distinguishing and determining the page. The electronic device may determine the first user id as a user id associated with the first client. It should be noted that the wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future.
In practice, the target webpage may be a webpage opened in a non-social client application (e.g., a browser application, a tool application, a reading application, an image application, etc.) installed by the first client. Generally, when browsing a web page through the client application, a first user may send a sharing request for the web page to the electronic device by clicking a sharing button in an interface presented by the client application and selecting a social platform, so as to share the web page to the selected social platform.
In this embodiment, the electronic device may first generate a first identifier based on the first user identifier and the web page identifier by using various character string processing manners; then, the electronic device may generate a first website with the first identifier for indicating the target webpage. Here, the electronic device may first obtain a source website of the target page, then parse the source website, and add the first identifier to generate the first website. In practice, the web address is generally represented by a Uniform Resource Locator (URL).
In some optional implementation manners of this embodiment, the electronic device may combine the first user identifier and the page identifier to generate a first identifier. For example, if the first user identifier is a character string "1234 abcd" and the page identifier is a character string "5678 efgh", the first user identifier and the page identifier may be combined before and after the first user identifier and the page identifier to generate a character string "1234 abcd5678 efgh", and the generated character string may be determined as the first identifier. It should be noted that the first user identifier and the page identifier may be combined in any order.
In some optional implementation manners of this embodiment, the electronic device may first combine the first user identifier and the page identifier in any order to generate a combined identifier; then, the electronic device may process the combined identifier by using various encryption algorithms to generate a first identifier. As an example, the above encryption Algorithm may be MD5(Message Digest Algorithm, fifth edition). The electronic device may perform processing such as grouping, cascading, and the like on the combined identifier in sequence, generate a hash value, and determine the hash value as the first identifier. It should be noted that the above encryption algorithm is a well-known technology widely studied and applied at present, and is not described herein again.
In practice, after the electronic device generates the first website, the link of the target page indicated by the first website may be sent to the social platform selected by the first user. Typically, the user may browse the target web page by querying the first web address or clicking on the link.
In this embodiment, in response to receiving the first web query request containing the first website sent by the second client (e.g., the second terminal device 107, 108, 109 shown in fig. 1), the electronic device may determine the second user identifier in various ways. It should be noted that, the electronic device may determine, as the second user, the user who sends the first web page query request through the second client, and the second user identifier may be a character string used to indicate and uniquely determine the second user. The electronic device may determine the second user identifier as a user identifier associated with the second client. It is noted that the number of the second clients may be multiple, and for each second client, the electronic device may determine a second user identifier associated with the second client.
In practice, after the electronic device pushes the link of the target page indicated by the first website to the social platform selected by the first user, when the second user enters the interface of the social platform through the second client and clicks the link presented in the interface, the second client sends a first web query request to the electronic device.
In some optional implementation manners of this embodiment, in response to receiving a first web page query request that includes the first website and is sent by the second client, the electronic device may first determine whether the first web page query request includes a user identifier, where the user identifier may be a personal account of a website to which the target web page that a user logs in belongs. Then, in response to determining that the first webpage query request includes the user identifier, the electronic device may match the user identifier included in the first webpage query request with the first user identifier. In response to determining that the first webpage query request does not match, the electronic device may determine the user identifier included in the first webpage query request as a second user identifier.
In some optional implementations of this embodiment, in response to determining that the first web page query request does not include a user identifier, the electronic device may randomly generate a second user identifier associated with the second client.
It should be noted that, after determining the second user identifier, the electronic device may send the second user identifier to the second client. In practice, after receiving the second user identifier, the second client may store the second user identifier in a small text file (cookies) of a browser application installed in the second client.
In this embodiment, after determining the second ue, the electronic device may perform the following mapping step. With further reference to fig. 3, fig. 3 is an exploded flow chart of the mapping establishment step in step 203 described above. In fig. 3, the mapping establishment step is decomposed into 2 sub-steps as follows: step 2031 and step 2032.
In this embodiment, the electronic device may generate the second identifier based on the second user identifier and the page identifier by using various character string processing manners. As an example, the electronic device may generate a second identifier by combining the second user identifier with the page identifier; the electronic device may further combine the second user identifier with the page identifier, and then process the combined character string by using various encryption algorithms to generate a second identifier. It should be noted that the generation method of the second identifier is basically the same as the generation method of the first identifier in step 202, and is not described herein again.
In this embodiment, the electronic device may establish a mapping between the first identifier and the second identifier, and store the mapping locally.
In some optional implementations of this embodiment, the mapping establishing step may further include step 2033.
The electronic device may establish a mapping between the first identifier and the second identifier, and store the mapping locally.
It should be noted that there may be a plurality of second clients, and thus the mapping between the first identifier and the second identifier may be established in a plurality of numbers.
In this embodiment, the electronic device may first determine the respective identities that form the established mapping. Since each identifier is generated based on a user identifier, the electronic device may pre-store a mapping between the identifiers and the user identifiers (e.g., a mapping of the first identifier and the first user identifier). Then, the electronic device may determine to generate a user identifier for each identifier based on the mapping; finally, the electronic device may determine the client associated with each determined user identifier as the client associated with the established mapping, and push the preset information to each client associated with the established mapping. Here, the preset information may be any preset information, for example, product introduction information, advertisement, hot news, and the like.
With continuing reference to fig. 4, fig. 4 is a schematic diagram of an application scenario of the information push method according to the present embodiment. In the application scenario of fig. 4, first, a first client 401 sends a sharing request 403 containing a first user identifier and a page identifier to a server 402 for a target web page. Then, the server 402 generates a first identifier based on the first user identifier and the page identifier, and generates a first website with the first identifier for indicating the target webpage. Then, the second client 404 clicks the link of the target web page indicated by the first website, and sends a first web page query request 405 including the first website to the server 402. Then, the server 402 determines a second user identifier associated with the second client, generates a second identifier based on the second user identifier and the page identifier, and establishes a mapping between the first identifier and the second identifier. Finally, the electronic device pushes preset information 406 to the first client 401 and the second client 404.
In the method provided by the embodiment of the application, first, a first identifier and a first website are generated based on a first user identifier and a page identifier in a sharing request sent by a first client; then, in response to receiving a first webpage query request sent by a second client, determining a second user identifier so as to generate a second identifier and establish mapping between the first identifier and the second identifier; and finally, the preset information is pushed to each client associated with the mapping, so that a plurality of users are associated, and further targeted information pushing is realized.
With further reference to fig. 5, a flow 500 of yet another embodiment of an information push method is shown. The process 500 of the information pushing method includes the following steps:
In this embodiment, an electronic device (for example, a server shown in fig. 1) on which an information push method operates may receive a sharing request for a target webpage sent by a first client (for example, first terminal devices 101, 102, and 103 shown in fig. 1), where the sharing request includes a first user identifier and a page identifier of the target webpage. Here, the electronic device may determine the user who sends the sharing request through the first client as a first user, and the first user identifier may be used to indicate and uniquely determine the first user.
In this embodiment, the electronic device may combine the first user identifier and the page identifier to generate a first identifier; then, the electronic device may generate a first website with the first identifier for indicating the target webpage.
In this embodiment, in response to receiving a first web page query request including the first website sent by the second client (e.g., the second terminal device 107, 108, 109 shown in fig. 1), the electronic device may first determine whether the first web page query request includes a user identifier. Then, in response to determining that the first web page query request does not include the user identifier, the electronic device may randomly generate a second user identifier associated with the second client. In response to determining that the first web page query request includes the user identifier, the electronic device may match the user identifier included in the first web page query request with the first user identifier. In response to determining that the first webpage query request does not match, the electronic device may determine the user identifier included in the first webpage query request as a second user identifier. It should be noted that, the electronic device may determine, as the second user, the user who sends the first web page query request through the second client, and the second user identifier may be used to indicate and uniquely determine the second user.
In this embodiment, after determining the second ue, the electronic device may perform the following mapping step: first, a second identifier is generated based on the second user identifier and the page identifier. And then establishing the mapping between the first identifier and the second identifier. It should be noted that the electronic device may further establish a mapping between the first user identifier and the second user identifier.
It should be noted that the specific operations in the steps 501-503 are substantially the same as the specific operations in the steps 201-203, and are not described herein again.
In this embodiment, the electronic device may analyze the first website obtained in step 503, add the second identifier, and generate the second website.
In this embodiment, the electronic device may return the second website generated in step 504 to the second client, and send a redirection instruction to the second client, so that the second client displays the target webpage indicated by the second website. In practice, the second client may invoke a browser application to render the target web page. The redirect instruction may be a 302 redirect instruction. The 302 redirect instruction may indicate a different URL that the browser is required to display, for use when a web page has undergone a short-term URL change.
In this embodiment, after the second website is returned to the second client, if the electronic device receives the sharing request for the target webpage sent by the second client, the link of the target page indicated by the second website may be sent to the sharing location indicated by the sharing request of the second client. The sharing location may be various social platforms. It should be noted that the sharing request may include the second user identifier and the page identifier of the target webpage.
In this embodiment, in response to receiving a second web page query request containing the second website sent by a third client, the electronic device may first determine whether the second web page query request contains a user identifier. Then, in response to determining that the second web page query request does not include the user identifier, the electronic device may randomly generate a third user identifier associated with the third client. In response to determining that the second web page query request includes the user identifier, the electronic device may match the user identifier included in the second web page query request with the first user identifier and the second user identifier. In response to determining that the user id included in the second web page query request is not the third user id, the electronic device may determine the user id included in the second web page query request as the third user id.
It should be noted that, the electronic device may determine, as the third user, the user who sends the second web page query request through the third client, and the third user identifier may be used to indicate and uniquely determine the third user.
In practice, after the electronic device pushes the link of the target page indicated by the second website to the social platform selected by the second user, when the third user enters the interface of the social platform through a third client and clicks the link displayed in the interface, the third client sends a second webpage query request to the electronic device.
It should be noted that, after determining the third user id, the electronic device may send the third user id to the third client. In general, after receiving the third user id, the third client may store the third user id in cookies of a browser application installed in the third client.
And 507, taking the third user identifier as a second user identifier and the second identifier as a first identifier, and continuing to execute the mapping establishing step.
In this embodiment, after determining the third user identifier, the electronic device may use the third user identifier as a second user identifier and use the second identifier generated in step 503 as a first identifier, continue to perform the mapping establishing step described in step 503 to generate a new second identifier, and establish a mapping between the first identifier (i.e., the original second identifier) and the second identifier (i.e., the new second identifier). It should be noted that there may be a plurality of the second clients and the third clients, and thus, the mapping established between the first identifier and the second identifier may be a plurality of. The established mapping of the first subscriber identity and the second subscriber identity may also be multiple.
It should be noted that, the electronic device may further generate a new second website with the second identifier for indicating the target webpage, and return the new second website to the third client, so that the third client displays the target webpage indicated by the new second website. In practice, after the electronic device receives a new second web page query request with the new second web address sent by the next client, the steps of establishing the mapping and the like can be repeatedly executed to form the multilayer mapping.
In this embodiment, the electronic device may first determine each identifier forming the established mapping; then, since each identifier is generated based on the user identifier, the electronic device may determine the user identifier for generating each identifier; finally, the electronic device may determine the client associated with each determined user identifier as the client associated with the established mapping, and push the preset information to each client associated with the established mapping.
With continuing reference to fig. 6, fig. 6 is a schematic diagram of an application scenario of the information push method according to the present embodiment.
In the application scenario of fig. 6, first, a first client 601 sends a sharing request containing a first user identifier and a page identifier to a server 604 for a target webpage. After receiving the sharing request, the server 604 generates a first identifier based on the first user identifier and the page identifier, and generates a first website with the first identifier for indicating the target webpage.
Then, the second client 602 sends a first web page query request containing the first web address to the server 604 after clicking the link of the target web page indicated by the first web address. After receiving the first web page query request, the server 604 sequentially performs the following processing operations: determining a second user identifier associated with the second client 602, generating a second identifier, creating a mapping between the first identifier and the second identifier, generating a second website with the second identifier for indicating the target webpage, and returning the second website to the second client 602. After receiving the second website, the second client 602 displays a target webpage indicated by the second website.
Then, the second client 602 shares the target webpage indicated by the second website, and the third client 603 clicks the link of the target webpage indicated by the second website, and then sends a second webpage query request including the second website to the server 604. Thereafter, the server 604 sequentially performs the processing operations. When the server 604 receives a new second web page query request sent by the next client, the above processing operations are repeatedly executed.
Finally, the server 604 pushes the preset information to each client of each formed mapping.
As can be seen from fig. 5, compared with the embodiment corresponding to fig. 2, the flow 500 of the information pushing method in this embodiment highlights a processing step of the second web page query request sent by the third client. Therefore, the scheme described in the embodiment can establish more mappings, realize the association of multi-layer users, and further realize the targeted information push.
With further reference to fig. 7, a flow 700 of yet another embodiment of an information push method is shown. The process 700 of the information push method includes the following steps:
In this embodiment, an electronic device (for example, a server shown in fig. 1) on which an information push method operates may receive a sharing request for a target webpage sent by a first client (for example, first terminal devices 101, 102, and 103 shown in fig. 1), where the sharing request includes a first user identifier and a page identifier of the target webpage. Here, the electronic device may determine the user who sends the sharing request through the first client as a first user, and the first user identifier may be used to indicate and uniquely determine the first user.
In this embodiment, the first client is installed with a target application, and the sharing request is sent by the first client through the target application. In practice, the target application may be a non-social client application (e.g., a browser application, a tool-class application, a reading-class application, an image-class application, etc.). In addition, the first user identifier may be an account for logging in a target application installed by the first client.
In this embodiment, the electronic device may combine the first user identifier and the page identifier to generate a first identifier; then, the electronic device may generate a first website with the first identifier for indicating the target webpage.
In this embodiment, in response to receiving a first web query request containing the first web address sent by the second client (e.g., the second terminal device 107, 108, 109 shown in fig. 1), the electronic device may generate a download address of the installation package of the target application with the first user identifier and the first identifier.
In some optional implementation manners of this embodiment, after the electronic device receives a first webpage query request containing the first website sent by the second client, step 705 may also be directly performed.
In this embodiment, the electronic device may send the download address to the second client, so that the second client automatically installs or updates the target application, or so that a user manually installs or updates the target application. As an example, after the electronic device sends the download address, the second client may present a page for guiding downloading or updating of the target application, where a download or update key may be displayed in the page, and when the user clicks the download or update key, the second client may download or update the target application.
In this embodiment, the electronic device may send an open instruction to the target application to the second client, so that the second client automatically runs the target application, or a user manually opens the target application. As an example, after the electronic device sends the opening instruction, the second client may present a page for guiding to open the target application, where an opening key may be displayed in the page, and when the user clicks the opening key, the second client may run the target application.
It should be noted that, after the second client opens the target application, a target page indicated by the first website may be presented.
In this embodiment, after sending the opening instruction of the target application to the second client, the electronic device may obtain an account of a user logging in the target application. In response to the successful acquisition, the account may be matched with the first user identifier. If there is a match, the account may be determined to be the second subscriber identity. In response to the acquisition failure, the electronic device may randomly generate a second user identification associated with the second client.
In this embodiment, after determining the second ue, the electronic device may perform the following mapping step: first, a second identifier is generated based on the second user identifier and the page identifier. And then establishing the mapping between the first identifier and the second identifier. It should be noted that the electronic device may further establish a mapping between the first user identifier and the second user identifier.
In this embodiment, the electronic device may first determine each identifier forming the established mapping; then, since each identifier is generated based on the user identifier, the electronic device may determine the user identifier for generating each identifier; finally, the electronic device may determine the client associated with each determined user identifier as the client associated with the established mapping, and push the preset information to each client associated with the established mapping. Here, the preset information may be any preset information, for example, product introduction information, advertisement, hot news, and the like.
It should be noted that the specific operations in steps 701, 702, 706, and 707 are substantially the same as those in steps 201 to 204, and are not described herein again.
As can be seen from fig. 7, compared with the embodiment corresponding to fig. 2, the flow 700 of the information pushing method in this embodiment highlights steps of generating and sending a download address of the target application, and the like. Therefore, the scheme described in the embodiment can establish mapping between users using non-social applications, and further realizes targeted information push.
With further reference to fig. 8, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of an information pushing apparatus, which corresponds to the embodiment of the method shown in fig. 2, and which can be applied in various electronic devices.
As shown in fig. 8, the information pushing apparatus 800 of the present embodiment includes: a receiving unit 801 configured to receive a sharing request for a target webpage sent by a first client, where the sharing request includes a first user identifier and a page identifier of the target webpage; a first generating unit 802, configured to generate a first identifier based on the first user identifier and the page identifier, and generate a first website with the first identifier for indicating the target webpage; a first determining unit 803, configured to determine, in response to receiving a first web page query request containing the first website sent by a second client, a second user identifier, and perform the following mapping establishing steps: generating a second identifier based on the second user identifier and the page identifier; establishing a mapping between the first identifier and the second identifier; a pushing unit 804 configured to push preset information to the respective clients associated with the established mapping.
In this embodiment, the receiving unit 801 of the information pushing apparatus 800 may receive, through a wired connection manner or a wireless connection manner, a sharing request for a target webpage sent by a first client (for example, the first terminal device 101, 102, 103 shown in fig. 1), where the sharing request includes a first user identifier and a page identifier of the target webpage.
In this embodiment, the first generating unit 802 may first generate a first identifier based on the first user identifier and the web page identifier by using various character string processing manners; thereafter, the first generating unit 802 may generate a first website with the first identifier for indicating the target webpage.
In some optional implementation manners of this embodiment, the first generating unit 802 may be further configured to combine the first user identifier and the page identifier to generate the first identifier.
In some optional implementation manners of this embodiment, the first generating unit 802 may be further configured to combine the first user identifier and the page identifier to generate a combined identifier; and processing the combined identifier by using an encryption algorithm to generate a first identifier.
In this embodiment, in response to receiving a first web page query request containing the first website sent by the second client (e.g., the second terminal device 107, 108, 109 shown in fig. 1), the first determining unit 803 may determine the second user identifier in various ways. In this embodiment, after determining the second ue, the first determining unit 803 may perform the following mapping step: first, a second identifier may be generated based on a second user identifier and the page identifier; thereafter, a mapping of the first identity and the second identity may be established.
In some optional implementations of the present embodiment, the first determining unit 803 may include a first determining module, a matching module, and a second determining module (not shown in the figure). The first determining module may be configured to determine, in response to receiving a first web page query request that includes the first website and is sent by a second client, whether the first web page query request includes a user identifier; the matching module may be configured to, in response to determining that the first web page query request includes a user identifier, match the user identifier included in the first web page query request with the first user identifier; the second determining module may be configured to determine, in response to a mismatch, the user identifier included in the first web page query request as the second user identifier.
In some optional implementations of the present embodiment, the first determining unit 803 further includes a generating module (not shown in the figure). The generating module may be configured to randomly generate a second user identifier associated with the second client in response to determining that the first web page query request does not include a user identifier.
In some optional implementations of this embodiment, the first determining unit 803 may be further configured to establish a mapping between the first user identifier and the second user identifier.
In some optional implementations of the present embodiment, the information pushing apparatus 800 may further include a second generating unit and a returning unit (not shown in the figure). The second generating unit may be configured to generate a second website with the second identifier, which is used for indicating the target webpage; the returning unit may be configured to return the second website to the second client, so that the second client displays the target webpage indicated by the second website.
In some optional implementations of the present embodiment, the information pushing apparatus 800 may further include a second determining unit and an executing unit (not shown in the figure). The second determining unit may be configured to determine, in response to receiving a second web page query request including the second web address sent by a third client, a third user identifier associated with the third client; the executing unit may be configured to use the third user identifier as a second user identifier and use the second identifier as a first identifier, so that the first determining unit continues to execute the mapping step.
In some optional implementation manners of this embodiment, the first client may have a target application installed thereon, and the sharing request may be sent by the first client through the target application; and the information pushing apparatus 800 may further include a first sending unit (not shown in the figure). The first sending unit may be configured to send an open instruction of the target application to the second client.
In some optional implementations of the present embodiment, the information pushing apparatus 800 may further include a third generating unit and a second sending unit (not shown in the figure). The third generating unit may be configured to generate a download address of the installation package of the target application with the first user identifier and the first identifier; the second sending unit may be configured to send the download address to the second client, so that the second client installs or updates the target application.
In this embodiment, the pushing unit 804 may first determine each identifier forming the established mapping; then, since each identifier is generated based on the user identifier, the pushing unit 804 may determine the user identifier for generating each identifier; finally, the client associated with each determined user identity may be determined as the client associated with the established mapping, and the preset information may be pushed to the respective clients associated with the established mapping.
In the apparatus provided in the foregoing embodiment of the present application, first generating unit 802 generates a first identifier and a first website based on a first user identifier and a page identifier in a sharing request sent by a first client and received by receiving unit 801; then, the first determining unit 803 determines the second user identifier in response to receiving the first web page query request sent by the second client, so as to generate the second identifier and establish a mapping between the first identifier and the second identifier; finally, the pushing unit 804 pushes the preset information to each client associated with the mapping, so that multiple users are associated, and further targeted information pushing is realized.
Referring now to FIG. 9, shown is a block diagram of a computer system 900 suitable for use in implementing a server according to embodiments of the present application. The terminal device/server shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU)901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The above-described functions defined in the method of the present application are executed when the computer program is executed by a Central Processing Unit (CPU) 901. It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a receiving unit, a first generating unit, a first determining unit, and a pushing unit. The names of the units do not form a limitation on the units themselves under certain conditions, for example, the receiving unit may also be described as a "unit that receives a sharing request for a target webpage sent by a first client".
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be present separately and not assembled into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: receiving a sharing request for a target webpage sent by a first client, wherein the sharing request comprises a first user identifier and a page identifier of the target webpage; generating a first identifier based on the first user identifier and the page identifier, and generating a first website with the first identifier for indicating the target webpage; in response to receiving a first webpage query request containing the first website sent by a second client, determining a second user identifier, and executing the following mapping establishment steps: generating a second identifier based on the second user identifier and the page identifier; establishing mapping between the first identifier and the second identifier; and pushing preset information to each client associated with the established mapping.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (16)
1. An information pushing method, characterized in that the method comprises:
receiving a sharing request for a target webpage sent by a first client, wherein the sharing request comprises a first user identifier and a page identifier of the target webpage;
generating a first identifier based on the first user identifier and the page identifier, and generating a first website with the first identifier for indicating the target webpage;
in response to receiving a first webpage query request containing the first website sent by a second client, determining a second user identifier, and executing the following mapping establishment steps: generating a second identifier based on the second user identifier and the page identifier; establishing a mapping of the first identifier and the second identifier;
pushing preset information to each client associated with the established mapping;
generating a first identifier based on the first user identifier and the page identifier includes:
combining the first user identifier and the page identifier to generate a combined identifier, wherein the combined identifier is a character string; and processing the combined identifier by using an encryption algorithm to generate a first identifier, wherein the first identifier is a hash value.
2. The information pushing method according to claim 1, wherein the mapping step further comprises:
and establishing mapping of the first user identification and the second user identification.
3. The information pushing method according to claim 1, further comprising:
generating a second website with the second identifier for indicating the target webpage;
and returning the second website to the second client to enable the second client to display the target webpage indicated by the second website.
4. The information pushing method according to claim 3, further comprising:
determining a third user identifier in response to receiving a second webpage query request containing the second website and sent by a third client;
and taking the third user identification as a second user identification and the second identification as a first identification, and continuing to execute the mapping establishing step.
5. The information pushing method according to claim 1, wherein the determining a second user identifier in response to receiving a first web query request containing the first web address sent by a second client includes:
in response to receiving a first webpage query request which is sent by a second client and contains the first website, determining whether the first webpage query request contains a user identifier;
in response to determining that the first webpage query request contains a user identifier, matching the user identifier contained in the first webpage query request with the first user identifier;
and in response to the mismatch, determining the user identifier contained in the first webpage query request as a second user identifier.
6. The information pushing method according to claim 5, wherein the determining a second user identifier in response to receiving a first web query request containing the first web address sent by a second client, further comprises:
in response to determining that the first web page query request does not include a user identification, randomly generating a second user identification associated with the second client.
7. The information pushing method according to claim 1, wherein a target application is installed on the first client, and the sharing request is sent by the first client through the target application; and
after the response of receiving a first webpage query request containing the first website sent by a second client, the method further comprises the following steps:
and sending an opening instruction of the target application to the second client.
8. The information pushing method according to claim 7, wherein before sending the opening instruction of the target application to the second client, the method further comprises:
generating a download address of the installation package of the target application with the first user identification and the first identification;
and sending the download address to the second client to enable the second client to install or update the target application.
9. An information pushing apparatus, characterized in that the apparatus comprises:
the device comprises a receiving unit and a processing unit, wherein the receiving unit is configured to receive a sharing request for a target webpage sent by a first client, and the sharing request comprises a first user identifier and a page identifier of the target webpage;
the first generation unit is configured to generate a first identifier based on the first user identifier and the page identifier, and generate a first website with the first identifier, which is used for indicating the target webpage;
a first determining unit, configured to determine, in response to receiving a first web page query request including the first website sent by a second client, a second user identifier, and execute the following mapping establishing step: generating a second identifier based on the second user identifier and the page identifier; establishing a mapping of the first identifier and the second identifier;
a pushing unit configured to push preset information to each client associated with the established mapping;
the first generating unit is further configured to:
combining the first user identifier and the page identifier to generate a combined identifier, wherein the combined identifier is a character string; and processing the combined identifier by using an encryption algorithm to generate a first identifier, wherein the first identifier is a hash value.
10. The information pushing apparatus according to claim 9, wherein the first determining unit is further configured to:
and establishing mapping of the first user identification and the second user identification.
11. The information pushing apparatus according to claim 9, further comprising:
the second generation unit is used for generating a second website with the second identification for indicating the target webpage;
and the returning unit is configured to return the second website to the second client, so that the second client displays the target webpage indicated by the second website.
12. The information push device according to claim 11, further comprising:
the second determining unit is configured to determine a third user identifier in response to receiving a second webpage query request which is sent by a third client and contains the second website;
and the execution unit is configured to use the third user identifier as a second user identifier and use the second identifier as a first identifier, so that the first determination unit continues to execute the mapping establishing step.
13. The information pushing apparatus according to claim 9, wherein the first determining unit includes:
the first determining module is configured to determine whether a first webpage query request containing the first website sent by a second client contains a user identifier or not in response to receiving the first webpage query request;
the matching module is configured to match the user identifier contained in the first webpage query request with the first user identifier in response to determining that the first webpage query request contains the user identifier;
and the second determining module is configured to determine the user identifier contained in the first webpage query request as a second user identifier in response to the mismatch.
14. The information pushing apparatus according to claim 13, wherein the first determining unit further includes:
a generating module configured to randomly generate a second user identifier associated with the second client in response to determining that the first web page query request does not include a user identifier.
15. A server, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.
16. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710083553.1A CN106874471B (en) | 2017-02-16 | 2017-02-16 | Information pushing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710083553.1A CN106874471B (en) | 2017-02-16 | 2017-02-16 | Information pushing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106874471A CN106874471A (en) | 2017-06-20 |
| CN106874471B true CN106874471B (en) | 2020-12-08 |
Family
ID=59167109
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710083553.1A Active CN106874471B (en) | 2017-02-16 | 2017-02-16 | Information pushing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106874471B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729537A (en) * | 2017-10-31 | 2018-02-23 | 阿里巴巴集团控股有限公司 | page data processing method and device, client, server |
| CN109829123A (en) * | 2017-11-22 | 2019-05-31 | 阿里巴巴集团控股有限公司 | A kind of method for sending information and device |
| CN110413920A (en) * | 2018-04-25 | 2019-11-05 | 北京京东尚科信息技术有限公司 | Method and apparatus for generating the page |
| CN108600378B (en) * | 2018-04-28 | 2021-05-28 | 武汉斗鱼网络科技有限公司 | File downloading method, device, terminal and storage medium |
| CN108848161B (en) * | 2018-06-14 | 2022-04-12 | 百度在线网络技术（北京）有限公司 | Network information processing method, device, equipment and computer readable storage medium |
| CN110673886B (en) * | 2018-07-03 | 2023-10-03 | 百度在线网络技术（北京）有限公司 | Method and device for generating thermodynamic diagrams |
| CN111538922B (en) * | 2019-01-18 | 2023-11-21 | 百度在线网络技术（北京）有限公司 | Link jump method, application client, device and storage medium |
| CN110232591A (en) * | 2019-05-24 | 2019-09-13 | 深圳市轱辘汽车维修技术有限公司 | A kind of page promotion method, page extension system and server |
| CN110457610B (en) * | 2019-06-27 | 2022-04-19 | 五八有限公司 | Information recommendation method, device, terminal, server and storage medium |
| CN110636106B (en) * | 2019-08-15 | 2023-04-07 | 平安普惠企业管理有限公司 | Information pushing method and device, computer equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001856A (en) * | 2012-12-05 | 2013-03-27 | 华为软件技术有限公司 | Information sharing method and system and instant messaging (IM) client and server |
| CN103078830A (en) * | 2011-10-25 | 2013-05-01 | 阿里巴巴集团控股有限公司 | Website information provision and sharing methods, friend addition method and corresponding equipment |
| CN104601712A (en) * | 2015-01-27 | 2015-05-06 | 黄瑞锋 | Resource push method and system |
| CN104683410A (en) * | 2013-12-02 | 2015-06-03 | 深圳市迅雷网络技术有限公司 | Resource sharing method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104852936A (en) * | 2014-02-13 | 2015-08-19 | 中兴通讯股份有限公司 | Method for sharing personal information on mobile terminal, and device thereof |
| CN105338084B (en) * | 2015-11-02 | 2018-11-23 | 北京金山安全软件有限公司 | Advertisement information pushing method and server |
-
2017
- 2017-02-16 CN CN201710083553.1A patent/CN106874471B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103078830A (en) * | 2011-10-25 | 2013-05-01 | 阿里巴巴集团控股有限公司 | Website information provision and sharing methods, friend addition method and corresponding equipment |
| CN103001856A (en) * | 2012-12-05 | 2013-03-27 | 华为软件技术有限公司 | Information sharing method and system and instant messaging (IM) client and server |
| CN104683410A (en) * | 2013-12-02 | 2015-06-03 | 深圳市迅雷网络技术有限公司 | Resource sharing method and device |
| CN104601712A (en) * | 2015-01-27 | 2015-05-06 | 黄瑞锋 | Resource push method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106874471A (en) | 2017-06-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106874471B (en) | Information pushing method and device | |
| US10635735B2 (en) | Method and apparatus for displaying information | |
| CN105721462B (en) | Information pushing method and device | |
| US11011163B2 (en) | Method and apparatus for recognizing voice | |
| CN107390994B (en) | Interface presentation method and device | |
| CN111580820B (en) | Applet generation method and device | |
| CN108846753B (en) | Method and apparatus for processing data | |
| US20170109371A1 (en) | Method and Apparatus for Processing File in a Distributed System | |
| CN107302597B (en) | Message file pushing method and device | |
| CN105516246B (en) | A kind of method and server of anti-application program downloading abduction | |
| US11244153B2 (en) | Method and apparatus for processing information | |
| CN107329963B (en) | Method and device for accelerating webpage access | |
| CN110471848B (en) | Method and device for dynamically returning message | |
| CN113568699B (en) | Content display method, device, equipment and storage medium | |
| CN107844488B (en) | Data query method and device | |
| CN108549586B (en) | Information processing method and device | |
| CN108880923A (en) | The method and apparatus that policer operation applied to application server is requested | |
| CN108667915B (en) | Information pushing system, method and device | |
| US20190166214A1 (en) | Method and apparatus for pushing information | |
| US11368297B2 (en) | Method and apparatus for updating digital certificate | |
| CN110619101B (en) | Method and apparatus for processing information | |
| CN111787041A (en) | Method and apparatus for processing data | |
| CN107634942B (en) | Method and device for identifying malicious request | |
| US10482397B2 (en) | Managing identifiers | |
| CN106790176B (en) | Method and system for accessing network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |