CN107819845B - Light application pushing method and device and server - Google Patents
Light application pushing method and device and server Download PDFInfo
- Publication number
- CN107819845B CN107819845B CN201711080602.2A CN201711080602A CN107819845B CN 107819845 B CN107819845 B CN 107819845B CN 201711080602 A CN201711080602 A CN 201711080602A CN 107819845 B CN107819845 B CN 107819845B
- Authority
- CN
- China
- Prior art keywords
- client
- light application
- server
- pushed
- information
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a light application pushing method, a light application pushing device and a server. The method comprises the following steps: receiving a trigger message for light application data from a first client; judging whether the first client sends the trigger message to the server for the first time or not according to a light application history push list prestored in the server; and determining the light application pushed to the first client according to the webpage address information of the current webpage under the condition that the first client sends the trigger message to the server for the first time. According to one embodiment of the invention, the user experience can be improved.
Description
Technical Field
The invention relates to the technical field of light applications, in particular to a light application pushing method, a light application pushing device and a server.
Background
In recent years, with the rapid development of mobile internet technology, light applications gradually come into the sight of people.
The light application is an application App which can be used as a search without downloading. It can be easily acquired and retrieved. Furthermore, light applications are also easily maintained.
The light applications are Native App based applications, which may be HTML 5 applications, for example. The light applications are based on the development framework and components provided by the native application platform. The light application may exhibit a similar user experience as the native application. This includes visual effects and interactive experiences similar to native applications (this is based on icons, text, animations, progress bars, forms, navigation, maps, audio, pictures, video, etc. provided by the platform). In some cases, the light application is also capable of acquiring various underlying system functions that are beneficial to enhancing the user experience (e.g., this is based on network requests, file operations, data caching, location acquisition, network status, system information, gravity sensing, compasses, signature encryption, user information, payments, template messages, etc. provided by the platform).
At present, a user actively obtains a light application mainly by scanning a two-dimensional code, searching and the like. For light applications, this approach is passive, which is detrimental to the popularity of light applications.
Therefore, it is desirable to provide a new technical solution, which is improved in view of at least one of the technical problems in the prior art.
Disclosure of Invention
It is an object of the present invention to provide a new technical solution for light application push.
According to a first aspect of the present invention, there is provided a light application push method, including: receiving a trigger message for light application data from a first client, wherein the trigger message carries identification information of the first client and webpage address information of a current webpage browsed by a user by using the first client; judging whether the first client sends the trigger message to the server for the first time or not according to a light application history push list prestored in the server, wherein the light application history push list comprises identification information of the client which sends the trigger message to the server once; and determining the light application pushed to the first client according to the webpage address information of the current webpage under the condition that the first client sends the trigger message to the server for the first time.
Optionally or alternatively, the light application history push list further includes a correspondence between the identification information and light application information pushed to a client by the server, and the method further includes: under the condition that the first client sends the trigger message to the server once, inquiring information of the light application pushed to the first client by the server based on the light application history pushing list; determining a second client based on the light application history push list, wherein the light application pushed to the second client has higher similarity with the light application pushed to the first client; and determining the light application pushed to the first client by utilizing the light application information pushed to the first client and the second client by the server.
Optionally or alternatively, the identification information of the first client is IP address information of a host where the first client is located or user name information corresponding to the first client.
Optionally or alternatively, the light applications are divided into at least one type, and determining the light applications to be pushed to the first client according to the webpage address information of the current webpage further comprises: determining the webpage type of the current webpage according to the webpage address information of the current webpage; and determining the light application pushed to the first client by utilizing the webpage type of the current webpage and the type of the light application.
Optionally or alternatively, determining the second client based on the light application history push list further comprises: generating a first vector based on information of the light application pushed by the server to the first client, respectively generating a plurality of second vectors based on information of the light application pushed by the server to a plurality of other clients, respectively calculating distances between the first vector and the plurality of second vectors to determine similarity of the first vector and the plurality of second vectors, and determining a second client based on the similarity; and determining the light application pushed to the first client by using the light application information pushed to the first client and the second client by the server once further comprises: and determining the light application pushed to the first client according to the information of the light application corresponding to the second vector of the second client.
Optionally or alternatively, determining, according to the information of the light application corresponding to the second vector of the second client, the light application pushed to the first client further includes: obtaining light applications which are not pushed to the first client from the information of the light applications corresponding to the second vector of the second client; and determining the light application which is not pushed to the first client as the light application which is pushed to the first client.
Optionally or alternatively, the method further comprises: and returning a response message of the server to the first client, wherein the response message carries the download address information of the light application pushed to the first client by the server.
According to a second aspect of the present invention, there is provided a light application pushing apparatus, comprising: the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving a trigger message for light application data from a first client, and the trigger message carries identification information of the first client and webpage address information of a current webpage browsed by a user by using the first client; the judging module is used for judging whether the first client sends the trigger message to the server for the first time according to a light application history push list prestored in the server, wherein the light application history push list comprises identification information of the client which sends the trigger message to the server once; and a light application determining module, configured to determine, according to the web page address information of the current web page, a light application to be pushed to the first client when the first client sends the trigger message to the server for the first time.
Optionally or alternatively, the light application history push list further includes a correspondence between the identification information and light application information pushed to a client by the server, and the light application pushing apparatus further includes: the system comprises a query module and a second client determining module, wherein the query module is used for querying information of the light application pushed to the first client by the server based on the light application history push list under the condition that the first client sends the trigger message to the server once, and the second client determining module is used for determining a second client based on the light application history push list, wherein the light application pushed to the second client has higher similarity with the light application pushed to the first client; and the light application determining module is further used for determining the light application pushed to the first client by utilizing the light application information pushed to the first client and the second client by the server.
According to a third aspect of the present invention, there is provided a server comprising: a memory and a processor, wherein the memory includes machine executable instructions for controlling the processor to perform any of the methods described above.
According to one embodiment of the invention, the light application pushed to the user who uses the first client to browse the webpage is close to the requirement of the user, and the user experience is improved.
Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 shows a schematic flow diagram of a light application push method according to an embodiment of the invention.
Fig. 2 shows a schematic flow diagram of a light application push method according to another embodiment of the invention.
Fig. 3 shows a schematic structural diagram of a light application pushing device according to another embodiment of the invention.
Fig. 4 shows a schematic structural diagram of a light application pushing device according to another embodiment of the invention.
Fig. 5 shows a schematic block diagram of a server according to another embodiment of the invention.
Detailed Description
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
Various embodiments and examples according to the present invention are described below with reference to the accompanying drawings.
< method >
Fig. 1 shows a schematic flow diagram of a light application push method according to an embodiment of the invention.
As shown in fig. 1, in step S1100, a trigger message for light application data is received from a first client, where the trigger message carries identification information of the first client and web page address information of a current web page browsed by a user using the first client.
For example, the first client may agree in advance with the server on the format of the client's trigger message for the light application data and the server's response message. For example, the following information is set in advance: the communication interface format, the parameter list, the coding mode and/or the encryption mode of the first client and the server, the format of the data returned by the server, the successful and failed response mode and the like.
In one example, HTTPS protocol may be employed to transfer data between the first client and the server, describe the data in JSON (JavaScript object notation) format, and encode the data in Base64 format. The parameter list is transmitted to the server in a post manner. The parameter list includes identification information of the first client and web page address information of a current web page browsed by the user using the first client. For example, the identification information of the first client may be IP address information of a host where the first client is located. The IP Address refers to an Internet Protocol Address (Internet Protocol Address). IP addresses are a unified address format provided by the IP protocol that assigns a logical address to each network and/or each host on the internet. Optionally, the identification information of the first client may also be user name information corresponding to the first client. For example, the username information is information entered on a login interface when the user logs into the first client. For example, user name information is set by the user himself.
In one example, the sending of the trigger message may be triggered by source address information.
For example, a first white list is set in the first client, and the first white list comprises source address information. The source address information refers to a web address of a source web page of the current web page. For example, the user clicks on a link corresponding to web page B in web page a of the client, and the client displays the current web page B. In this case, the web page a is a source web page of the current web page B, and the address information of the web page a is source address information.
And under the condition that the first white list comprises the source address information of the current webpage, the first client determines to send a trigger message for the light application data to the server.
In addition, the server may also determine to push the light application to the first client based on the source address information. For example, in addition to the trigger message, the first client sends an HTTP refer message to the server. The HTTP refer message may carry the source address information.
A second white list may be set in the server. The first whitelist and the second whitelist may be synchronized periodically or aperiodically as desired. In an instance in which the second whitelist includes source address information received by the server, the server may push the light application to the first client.
The method for pushing the light applications based on the source address information can avoid the trouble of pushing excessive light applications to users.
Furthermore, this may reduce the processing load of client push.
Furthermore, in this push approach, it can be determined whether to recommend a light application based on the trustworthiness of the source, so that existing trust information can be utilized (the source web address is trustworthy).
In addition, for the provider of the source website, the method can make the user pay more attention to the source website, thereby increasing the stickiness of the user to the source website.
In one example, the first client may be, for example, a browser client.
In step S1200, it is determined whether the first client sends the trigger message to the server for the first time according to a light application history push list pre-stored in the server, where the light application history push list includes identification information of the client that has sent the trigger message to the server once.
In a case where a light application history push list pre-stored by the server includes identification information of the first client, it is determined that the first client has sent a trigger message for light application data to the server. And under the condition that a light application history push list prestored in the server does not comprise identification information of the first client, determining that the first client sends a trigger message for light application data to the server for the first time.
In step S1300, when the first client sends the trigger message to the server for the first time, the light application pushed to the first client is determined according to the web page address information of the current web page.
In one example, the light applications are divided into at least one type, e.g., news, science, entertainment, sports, etc. After receiving the trigger message from the first client, the server may determine the web page type of the current web page according to the web page address information of the current web page carried in the trigger message. Then, the server determines the light application pushed to the first client by using the webpage type of the current webpage and the type of the light application. For example, the server determines, according to the web page address information of the current web page, that the current web page browsed by the user using the first client is a sports-type web page, and may regard the user as a potential client of the sports-type light application, so that the server determines that the light application pushed to the first client is the sports-type light application.
In the case where the first client does not send the trigger message to the server for the first time, the server may not perform any processing, and may also push the light application to the first client based on the light application history push list. Fig. 2 shows a schematic flow diagram of a light application push method according to another embodiment of the invention. Fig. 2 differs from fig. 1 in that steps S1400, S1500, and S1600 are further included. Steps S1100, S1200 and S1300 in fig. 2 are similar to the corresponding steps in fig. 1 and are not repeated here.
Referring to fig. 2, in step S1400, in a case where the first client has sent the trigger message to the server once, the information of the light application pushed by the server to the first client is queried based on the light application history push list.
The light application history push list not only includes identification information of a client that has sent the trigger message to the server once, but also includes a corresponding relationship between the identification information of the client and light application information pushed to the client by the server. For example, the client with the IP address of 118.198.136.172 of the host sends a trigger message to the server for three times, after receiving the trigger message for three times, the server pushes a light application a, a light application B, and a light application C to the client, and the history push list of the light application in the server includes not only the identification information of the client (118.198.136.172), but also the correspondence between the identification information of the client and the light application a, the light application B, and the light application C pushed to the client.
Table 1 shows a light application history push list of one embodiment of the present invention. The light application history push list shown in table 1 includes the correspondence between the identification information of the client that has sent the trigger message for the light application data to the server and the light application that the server has pushed to the client that has sent the trigger message.
Referring to table 1, the light application history push list includes identification information of three clients and information of light applications pushed by the server to the three clients. The light application history push list distinguishes whether the server has pushed a certain light application to the client by "1" and "0". "1" represents that the server pushed some light application to the client, and "0" represents that the server did not push some light application to the client. Taking the client a as an example for explanation, the server pushes the light application 1 and the light application 3 to the client a, and does not push the light application 2 and the light application 4 to the client a.
TABLE 1
| Light applications 1 | Light applications 2 | Light applications 3 | Light applications 4 | |
| Identification information of client a | 1 | 0 | 1 | 0 |
| Identification information of client B | 1 | 1 | 1 | 0 |
| Identification information of client C | 1 | 0 | 0 | 0 |
In step S1500, a second client is determined based on the light application history push list, wherein the light application pushed to the second client has a higher similarity to the light application pushed to the first client.
In one example, a first vector (e.g., a vector generated per each row of table 1) may be generated based on information of the light application pushed by the server to the first client, for example. Then, a plurality of second vectors (e.g., vectors generated per each row of table 1) are respectively generated based on information of the light applications pushed by the server to the plurality of other clients. Then, the distances of the first vector and the plurality of second vectors are respectively calculated to determine the similarity of the first vector and the plurality of second vectors. And determining the second client based on the similarity of the first vector and a plurality of second vectors, wherein the second vector generated by the information of the light application pushed to the second client by the server has the highest similarity with the first vector generated by the information of the light application pushed to the first client.
In one example, distances of the first vector and the plurality of second vectors are calculated, respectively, based on the following calculation formula (1) to determine similarities of the first vector and the plurality of second vectors,
wherein A isiRepresents a first vector, BiRepresenting the second vector, n representing the dimensions of the first and second vectors, cos θ representing the first vector AiAnd a second vector BiThe distance of (c). The larger the cos theta value is, the closer the distance between the first vector and the second vector is, and the higher the similarity between the first vector and the second vector is determined.
Taking the above table 1 as an example, the client a is the first client, and the clients B and C are the other clients. First vector A generated based on information of light application pushed by server to first client4Is (1,0,1, 0). Second vector B generated based on information of light application pushed by server to other two clients4Respectively (1,1,1,0) and (1,0,0, 0). And (3) respectively calculating the distance between the first vector and the two second vectors based on the calculation formula (1), so as to obtain the closest distance between the first vector and the second vector corresponding to the client B, and further determine that the similarity value between the first vector and the second vector corresponding to the client B is higher.
Step S1600, determining the light application pushed to the first client by using the light application information that the server has pushed to the first client and the second client.
The second vector generated by the information of the light application pushed to the second client by the server has the highest similarity with the first vector generated by the information of the light application pushed to the first client, so that the requirement of a user using the second client is closer to the requirement of a user using the first client, and the light application pushed to the first client by the server can be determined.
Here, the light application not pushed to the first client may be obtained from information of the light application corresponding to the second vector of the second client, and determined as the light application pushed to the first client.
Taking the above table 1 as an example, the client a is the first client, and the clients B and C are the other clients. Based on the above calculation formula (1), the similarity value of the first vector corresponding to the first client and the second vector corresponding to the client B is calculated to be higher. And determining the light application pushed to the client A according to the information of the light application pushed to the client B by the server. The light applications that the server has pushed to the client B include light application 1, light application 2, and light application 3, and the light applications that the server has pushed to the client a include light application 1 and light application 3. Regarding the push, the server selects a light application 2 that is not pushed to the client a from light applications that were pushed to the client B once, and determines that the light application 2 is a light application pushed to the first client.
It should be noted that the number of light applications pushed by the server to the first client is not limited to one of the above examples, and may be two or even more.
The server may return a response message to the first client, where the response message carries the download address information of the light application pushed by the server to the first client. And the response message of the server is returned to the first client according to the agreed format.
And after receiving the response message, the first client analyzes the response message to obtain the pushed download address information of the light application. The first client displays the download address information on a preset recommendation interface of the first client, so that a user can select whether to use the pushed light application according to the requirement of the user.
The user can click the pushed download address of the light application according to the self requirement. Optionally, the user may also close the interface that presents the pushed light application, or do nothing.
When the user operates the pushed light application according to the self requirement, the first client side can perform grading operation on the pushed light application and return a grading result to the server. For example, when the user clicks on the pushed light application, the first client scores 2 for the pushed light application. When the user closes the interface showing the pushed light application, the first client scores-2 for the pushed light application. When the user neither clicks the pushed light application nor closes the interface on which the pushed light application is presented, the first client scores 1 for the pushed light application. And after receiving a scoring result generated by the first client to the pushed light application, the server records the scoring result of the pushed light application in a light application history pushing list. Referring to table 2, the light application history push list includes identification information of three clients and information of light applications pushed by the server to the three clients. The light application history push list determines the information of the pushed light application by using the grading result of the pushed light application returned by the client. "0" represents that the server does not push some light application to the client. "1" represents that the user does not do anything with the light application pushed by the server. And 2 represents that the user clicks the light application pushed by the server. "-2" represents a user closing the interface of the light application pushed by the presentation server.
TABLE 2
| Light applications 1 | Light applications 2 | Light applications 3 | Light applications 4 | |
| Identification information of client a | 1 | 0 | 2 | 0 |
| Identification information of client B | 0 | 1 | 1 | 1 |
| Identification information of client C | 2 | 0 | -2 | 0 |
In one example, taking the above table 2 as an example, the client a is the first client, and the clients B and C are the other clients. First vector A generated based on information of light application pushed by server to first client4Is (1,0,2, 0). Second vector B generated based on information of light application pushed by server to other two clients4Are (0,1,1,1) and (2, 0) respectively2,0). Based on the above calculation formula (1), similarity values of the first vector and the two second vectors are calculated, respectively. And determining the second client based on the similarity of the first vector and the two second vectors, wherein the second vector generated by the information of the light application pushed to the second client by the server has the highest similarity with the first vector generated by the information of the light application pushed to the first client. Then, the light application pushed to the first client is determined by utilizing the light application information which is pushed to the first client and the second client by the server.
< apparatus >
Those skilled in the art will appreciate that in the field of electronics, the above-described methods may be embodied in articles of manufacture by software, hardware, and combinations of software and hardware. The person skilled in the art will easily be able to produce a light application pushing device based on the method disclosed above. The apparatus may include means for implementing the operations in the foregoing light application push method.
Referring to fig. 3, the light application pushing device 3000 may include: a receiving module 3010, configured to receive a trigger message for the light application data from the first client, where the trigger message carries identification information of the first client and webpage address information of a current webpage browsed by the user using the first client; a judging module 3020, configured to judge, according to a light application history push list pre-stored in the server, whether the first client sends the trigger message to the server for the first time, where the light application history push list includes identification information of a client that has sent the trigger message to the server at one time; and a light application determining module 3030, configured to determine, according to the web page address information of the current web page, a light application to be pushed to the first client when the first client sends the trigger message to the server for the first time.
In one example, the light application history push list further includes a correspondence between the identification information and the light application information pushed by the server to the client. In the case where the first client has sent the trigger message to the server once, referring to fig. 4, the light application push apparatus 3000 further includes: a query module 3040, configured to, when the first client sends the trigger message to the server once, query, based on the light application history push list, information of the light application pushed by the server to the first client; and a second client determining module 3050, configured to determine a second client based on the history of the light applications pushed to the second client, where the light applications pushed to the second client have a higher similarity to the light applications pushed to the first client; the light application determining module 3030 is further configured to determine the light application pushed to the first client by using the light application information that the server has pushed to the first client and the second client.
< Server >
Fig. 5 shows a schematic block diagram of a server according to an embodiment of the invention. Referring to fig. 5, server 5000 may include processor 5010, storage 5020, interface 5030, communications 5040, display 5050, input 5060, speakers 5070, microphone 5080, and the like.
The processor 5010 may be, for example, a central processing unit CPU, a microprocessor MCU, or the like.
The memory 5020 includes, for example, a ROM (read only memory), a RAM (random access memory), a nonvolatile memory such as a hard disk, and the like.
The interface device 5030 includes, for example, a USB interface, a headphone interface, and the like.
The communication device 5040 can perform wired or wireless communication, for example.
The display device 5050 is, for example, a liquid crystal display screen, a touch display screen, or the like.
The input device 5060 may include, for example, a touch screen, a keyboard, and the like.
A user can input/output voice information through the speaker 5070 and the microphone 5080.
The server illustrated in FIG. 5 is illustrative only and is not intended to limit the present invention, its application, or uses in any way.
In this embodiment, the memory 5020 is used to store instructions that control the processor 5010 to operate to perform the light application push method shown in fig. 1.
It should be understood by those skilled in the art that although a plurality of devices are shown in fig. 5, the present invention may relate to only some of the devices, such as the processor 5010 and the memory 5020. The skilled person can design the instructions according to the disclosed solution. How the instructions control the operation of the processor is well known in the art and will not be described in detail herein.
The present invention may be a system, method and/or computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied therewith for causing a processor to implement various aspects of the present invention.
The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: 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), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
The computer program instructions for carrying out operations of the present invention may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
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 invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). 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. It is well known to those skilled in the art that implementation by hardware, by software, and by a combination of software and hardware are equivalent.
Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.
Claims (10)
1. A light application push method, comprising:
receiving a trigger message for light application data from a first client, wherein the trigger message carries identification information of the first client and webpage address information of a current webpage browsed by a user by using the first client, and the first client sends the trigger message when a first white list contains source address information of the current webpage;
judging whether the first client sends the trigger message to the server for the first time or not according to a light application history push list prestored in the server, wherein the light application history push list comprises identification information of the client which has sent the trigger message to the server once, and under the condition that the light application history push list does not comprise the identification information of the first client, determining that the first client sends the trigger message to the server for the first time; and
and under the condition that the first client sends the trigger message to the server for the first time, determining the light application pushed to the first client according to the webpage address information of the current webpage.
2. The method of claim 1, wherein the light application history push list further comprises a correspondence of the identification information and light application information pushed by the server to a client, an
Wherein the method further comprises:
under the condition that the first client sends the trigger message to the server once, inquiring information of the light application pushed to the first client by the server based on the light application history pushing list;
determining a second client based on the light application history push list, wherein the light application pushed to the second client has higher similarity with the light application pushed to the first client; and
and determining the light application pushed to the first client by utilizing the light application information pushed to the first client and the second client by the server.
3. The method according to claim 1, wherein the identification information of the first client is IP address information of a host where the first client is located or user name information corresponding to the first client.
4. The method of claim 1, wherein the light applications are classified into at least one type, an
Determining the light application pushed to the first client according to the webpage address information of the current webpage further comprises:
determining the webpage type of the current webpage according to the webpage address information of the current webpage; and
and determining the light application pushed to the first client by utilizing the webpage type of the current webpage and the type of the light application.
5. The method of claim 2, wherein determining the second client based on the light application history push list further comprises:
generating a first vector based on information of a light application pushed by the server to the first client,
respectively generating a plurality of second vectors based on the light application information pushed by the server to a plurality of other clients,
calculating distances of the first vector and the plurality of second vectors, respectively, to determine similarities of the first vector and the plurality of second vectors, an
Determining a second client based on the similarity; and
wherein, determining the light application pushed to the first client by using the light application information pushed to the first client and the second client by the server once further comprises:
and determining the light application pushed to the first client according to the information of the light application corresponding to the second vector of the second client.
6. The method of claim 5, wherein determining the light application to be pushed to the first client according to the information of the light application corresponding to the second vector of the second client further comprises:
obtaining light applications which are not pushed to the first client from the information of the light applications corresponding to the second vector of the second client; and
determining the light application which is not pushed to the first client as the light application which is pushed to the first client.
7. The method of any of claims 1-6, wherein the method further comprises:
and returning a response message of the server to the first client, wherein the response message carries the download address information of the light application pushed to the first client by the server.
8. A light application pushing device comprising:
a receiving module, configured to receive a trigger message for light application data from a first client, where the trigger message carries identification information of the first client and web page address information of a current web page browsed by a user using the first client, and the first client sends the trigger message when a first white list includes source address information of the current web page;
a judging module, configured to judge whether the first client sends the trigger message to the server for the first time according to a light application history push list pre-stored by the server, where the light application history push list includes identification information of a client that has sent the trigger message to the server, and when the light application history push list does not include the identification information of the first client, determine that the first client sends the trigger message to the server for the first time; and
and the light application determining module is used for determining the light application pushed to the first client according to the webpage address information of the current webpage under the condition that the first client sends the trigger message to the server for the first time.
9. The light application push apparatus according to claim 8, wherein the light application history push list further includes a correspondence of the identification information and light application information pushed by the server to a client, and,
the light application pushing device further comprises:
the query module is used for querying the information of the light application pushed to the first client by the server based on the light application history push list under the condition that the first client sends the trigger message to the server once; and
a second client determining module for determining a second client based on the light application history push list, wherein the light application pushed to the second client has higher similarity with the light application pushed to the first client,
the light application determining module is further configured to determine the light application pushed to the first client by using the light application information that the server has pushed to the first client and the second client.
10. A server, comprising: a memory and a processor, wherein the memory comprises machine executable instructions for controlling the processor to perform the method of any one of claims 1-7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711080602.2A CN107819845B (en) | 2017-11-06 | 2017-11-06 | Light application pushing method and device and server |
| PCT/CN2018/105840 WO2019085664A1 (en) | 2017-11-06 | 2018-09-14 | Light app push method and apparatus, server, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711080602.2A CN107819845B (en) | 2017-11-06 | 2017-11-06 | Light application pushing method and device and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107819845A CN107819845A (en) | 2018-03-20 |
| CN107819845B true CN107819845B (en) | 2021-01-26 |
Family
ID=61603918
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711080602.2A Active CN107819845B (en) | 2017-11-06 | 2017-11-06 | Light application pushing method and device and server |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107819845B (en) |
| WO (1) | WO2019085664A1 (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107819845B (en) * | 2017-11-06 | 2021-01-26 | 阿里巴巴（中国）有限公司 | Light application pushing method and device and server |
| CN108848122B (en) * | 2018-05-10 | 2021-11-30 | 上海掌门科技有限公司 | Method and equipment for pushing information and showing information |
| CN109189976B (en) * | 2018-09-20 | 2022-04-08 | 腾讯音乐娱乐科技（深圳）有限公司 | Method and apparatus for searching audio data |
| CN110703967B (en) * | 2019-09-29 | 2021-04-09 | 维沃移动通信有限公司 | Short message processing method and terminal equipment thereof |
| CN111399860B (en) * | 2020-03-06 | 2023-07-07 | 金蝶蝶金云计算有限公司 | Light application deployment method, light application deployment device, computer equipment and storage medium |
| CN111598628A (en) * | 2020-05-26 | 2020-08-28 | 北京学之途网络科技有限公司 | Information pushing method and device based on user identification information |
| CN114500641A (en) * | 2022-02-10 | 2022-05-13 | 阿里巴巴（中国）有限公司 | Message communication method, device and readable medium |
| CN114553949A (en) * | 2022-02-15 | 2022-05-27 | 北京京东乾石科技有限公司 | Page message pushing method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102647462A (en) * | 2012-03-29 | 2012-08-22 | 奇智软件（北京）有限公司 | Application acquisition and sending method and device |
| CN103973737A (en) * | 2013-01-30 | 2014-08-06 | 腾讯科技（深圳）有限公司 | Method, server and browser for actively pushing messages |
| CN104899220A (en) * | 2014-03-06 | 2015-09-09 | 腾讯科技（深圳）有限公司 | Application program recommendation method and system |
| CN105787061A (en) * | 2016-02-29 | 2016-07-20 | 广东顺德中山大学卡内基梅隆大学国际联合研究院 | Information pushing method |
| CN107016603A (en) * | 2017-04-24 | 2017-08-04 | 南京华苏科技有限公司 | The method that App recommendations are carried out based on social networks leader |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104023073A (en) * | 2014-06-13 | 2014-09-03 | 北京奇虎科技有限公司 | Resource pushing method, system and device |
| CN104158722B (en) * | 2014-07-21 | 2016-11-09 | 小米科技有限责任公司 | For light information push method, device, terminal and the server applied |
| CN104270429B (en) * | 2014-09-19 | 2017-12-08 | 北京奇虎科技有限公司 | A kind of method and apparatus for pushing VAS application -to-terminal service |
| CN107819845B (en) * | 2017-11-06 | 2021-01-26 | 阿里巴巴（中国）有限公司 | Light application pushing method and device and server |
-
2017
- 2017-11-06 CN CN201711080602.2A patent/CN107819845B/en active Active
-
2018
- 2018-09-14 WO PCT/CN2018/105840 patent/WO2019085664A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102647462A (en) * | 2012-03-29 | 2012-08-22 | 奇智软件（北京）有限公司 | Application acquisition and sending method and device |
| CN103973737A (en) * | 2013-01-30 | 2014-08-06 | 腾讯科技（深圳）有限公司 | Method, server and browser for actively pushing messages |
| CN104899220A (en) * | 2014-03-06 | 2015-09-09 | 腾讯科技（深圳）有限公司 | Application program recommendation method and system |
| CN105787061A (en) * | 2016-02-29 | 2016-07-20 | 广东顺德中山大学卡内基梅隆大学国际联合研究院 | Information pushing method |
| CN107016603A (en) * | 2017-04-24 | 2017-08-04 | 南京华苏科技有限公司 | The method that App recommendations are carried out based on social networks leader |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107819845A (en) | 2018-03-20 |
| WO2019085664A1 (en) | 2019-05-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107819845B (en) | Light application pushing method and device and server | |
| US10565800B2 (en) | Virtual doorbell augmentations for communications between augmented reality and virtual reality environments | |
| US9537925B2 (en) | Browser notifications | |
| CN106911693B (en) | Method and device for detecting hijacking of webpage content and terminal equipment | |
| US20140372403A1 (en) | Methods and systems for information matching | |
| JP2014519632A (en) | Customized launch of application | |
| CN107016055B (en) | Method and device for mining entity alias and electronic device | |
| US11360640B2 (en) | Method, device and browser for presenting recommended news, and electronic device | |
| US10956473B2 (en) | Article quality scoring method and device, client, server, and programmable device | |
| TW201539322A (en) | Compressed serialization of data for communication from a client-side application | |
| US11044222B2 (en) | Automated connection of electronic messaging and social networking services method and apparatus | |
| US20160164819A1 (en) | System and method for triaging in a message system on send flow | |
| US11523260B2 (en) | Delivery of configuration information for cross-platform application integration | |
| Al Abid et al. | Cross-platform development for an online food delivery application | |
| US20150142931A1 (en) | Systems and methods for content browsing, generation, and interaction | |
| CN108449255B (en) | Comment interaction method and equipment, client device and electronic equipment | |
| CN107193819B (en) | Method and equipment for webpage pre-reading, browser and client equipment | |
| CN111381819A (en) | List creation method and device, electronic equipment and computer-readable storage medium | |
| US11238524B2 (en) | Social network initiated listings | |
| CN107918552B (en) | Light application calling method and device, client device and electronic equipment | |
| US20200036749A1 (en) | Web browser incorporating social and community features | |
| US10380614B1 (en) | User reset voting to identify unwanted settings values in client software | |
| US20170161237A1 (en) | Method for creating a hyperlink in a video-playing page and electronic device | |
| US20190384465A1 (en) | Dynamic web actions palette | |
| CN111753177A (en) | Personalized recommendation method and device and computer storage medium |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200527 Address after: 310051 room 508, floor 5, building 4, No. 699, Wangshang Road, Changhe street, Binjiang District, Hangzhou City, Zhejiang Province Applicant after: Alibaba (China) Co.,Ltd. Address before: 510627 Guangdong city of Guangzhou province Whampoa Tianhe District Road No. 163 Xiping Yun Lu Yun Ping square B radio tower 12 layer self unit 01 Applicant before: GUANGZHOU SHENMA MOBILE INFORMATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |