The application is a divisional application of an invention patent application with the application number of 201510598869.5, the application date of 2015, 09 and 18 and the name of 'a method and a device for pushing information'.
Detailed Description
The embodiment of the application provides an information pushing method and device. The information pushing method can be applied to any electronic device capable of achieving information pushing, such as an electronic device capable of achieving information pushing, for example, a mobile smart phone, a tablet electronic device, a portable computer (e.g., a laptop, etc.), a Personal Digital Assistant (PDA), an intelligent wearable device, etc., or a computer device such as a merchant POS machine, a service server, etc.
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Specific implementations of the embodiments of the present application are described below with specific examples.
The following first introduces an embodiment of a method for pushing information in the present application. Fig. 1 is a schematic flowchart of an embodiment of an information pushing method provided in the present application. For a user who needs to obtain the push information provided in the embodiment of the present application, the information push function provided in the embodiment of the present application may be run on one or more processors of the electronic device in a background program, a plug-in, or the like. Although the flow described below includes operations that occur in a particular order, it should be appreciated that the processes may include more or less operations that are performed sequentially or in parallel (e.g., using parallel processors or a multi-threaded environment). Specifically, as shown in fig. 1, the method may include:
s110: and acquiring the historical path track of the user.
In the application, the historical path track of the user can be obtained. In some embodiments, the obtaining the historical path trajectory of the user may include:
and calculating to obtain the historical path track of the user according to the acquired historical path information of the user.
Specifically, the historical path information may include geographical location information and may also include time information, and in general, the geographical location information may generally correspond to the time information, for example, the historical path information may include geographical location information of a user arriving at a certain location L and time information of arriving at the location L. In some other embodiments, the historical path information may further include information of a merchant corresponding to the geographic location information.
Further, the calculating the historical path trajectory of the user according to the acquired historical path information of the user may include calculating a correlation between geographical location information in the acquired historical path information of the user, and using the historical path information of the user corresponding to the geographical location information with the correlation as the historical path trajectory of the user. In a specific application scenario, for example, the correlation between the geographic location information may be calculated according to the time of arrival at the geographic location. For example, it may be obtained that the user frequently arrives at the geographic location a, the geographic location B, and the geographic location C between 5:00 and 6:00, and then it may be determined that the geographic location a, the geographic location B, and the geographic location C have a correlation therebetween, so that in this embodiment, historical path information corresponding to the geographic location a, the geographic location B, and the geographic location C may be used as a historical path trajectory of the user. Further, a path identifier may be set for the historical path trajectory corresponding to the geographic location a, the geographic location B, and the geographic location C, where the path identifier may include identification information corresponding to the historical path trajectory, so that a user may identify different historical path trajectories, for example, the path identifier may be "go home from work", and the like.
In some embodiments, the historical path information may include automatically collected recorded path information, and particularly, may include path information collected using a preset positioning device (e.g., GPS), or may include path information collected through a mobile communication network. In practical applications, for example, when a user arrives at a certain location L at a certain time T, the geographic location information of the time T and the location L may be acquired automatically, and the geographic location information of the time T and the location L may be used as the historical path information. In other scenarios, for example, a user may pass a certain road in a certain time period, may acquire the time period and the geographical location information of the certain road, and may use the time period and the geographical location information of the certain road as the historical path information.
In some other embodiments of the present application, the obtaining the historical path trajectory of the user may include:
and calculating a plurality of historical path tracks of the user according to the acquired historical path information of the user, and taking one historical path track selected or set by the user as the historical path track of the user.
In a specific application scenario, a plurality of historical path trajectories can be calculated according to the acquired historical path information of the user, and the user can directly select one of the historical path trajectories from the plurality of historical path trajectories as the historical path trajectory of the user. Alternatively, the user may select or set a historical path track in the map interface. For example, a user may click a starting position of a certain track path in a map interface on the map interface, drag the track path along the starting position, and click an ending position of the track path; or clicking a preset selection start button in a map interface by a user, selecting a starting position and an ending position of a certain track path in the map interface, and clicking an operation of selecting an ending button.
S120: and determining a target merchant on the historical path track and push information corresponding to the target merchant according to the historical path track.
In this embodiment, after the historical path track of the user is obtained, the target merchant on the historical path track and the push information corresponding to the target merchant may be determined according to the historical path track. Specifically, the push information may include preset event service information of the target merchant, for example, preferential information such as a day 7 in the supermarket B of the target merchant, a year 5 in which yogurt is played at this night, and the like. Certainly, the push information may also include other preset interaction information, such as interaction information of check-in, coupon picking, chat, and the like.
FIG. 2 is a schematic flow chart of determining a target merchant on a historical path track in an embodiment of the information push method of the present application; in some embodiments, as shown in fig. 2, the determining, according to the historical path trajectory, the target merchant on the historical path trajectory may include:
s210: and judging whether the frequency of the target geographical position information in the historical path track is greater than a first threshold value.
In some embodiments, the first threshold may be preset according to the specific application requirement, for example, the first threshold may be set to 10 times. When the number of times of occurrence of the geographical location information in the historical path track is judged to be greater than the first threshold, it can be shown that the number of times that the user reaches the merchant corresponding to the geographical location information is greater than 10, and it can be judged that the merchant is the merchant that the user frequently goes to.
S220: and setting the merchant corresponding to the geographical position information of which the occurrence frequency is greater than the first threshold value as the target merchant according to the judgment result.
As described above, when the number of times of occurrence of the geographic location information is greater than the first threshold, it may be determined that the merchant corresponding to the geographic location information is a merchant that the user frequently goes to, and in this implementation, the merchant that the user frequently goes to may be determined as the target merchant.
In addition, in some embodiments, the merchant corresponding to the geographical location information that appears in the historical path trajectory less than or equal to the first threshold may be only a certain merchant that the user passes through, and not a merchant that the user needs.
FIG. 3 is a schematic flowchart illustrating a process of determining a target merchant on a historical path track according to an embodiment of the information push method of the present application; in some embodiments, as shown in fig. 3, the determining, according to the historical path trajectory, a target merchant on the historical path trajectory may include:
s310: and judging whether the occurrence frequency of the geographical position information in the historical path track is greater than a second threshold value.
In some embodiments, the second threshold may be preset according to the specific application requirement, for example, the second threshold may be set to 8 times. When the number of times of occurrence of the geographic position information in the historical path track is judged to be greater than or equal to the second threshold, the number of times that the user arrives at a merchant corresponding to the geographic position information can be represented to be greater than or equal to 8, and the merchant can be judged to be a merchant that the user frequently visits.
S320: and determining the merchant corresponding to the geographical location information with the occurrence frequency larger than the second threshold value as a pre-selected target merchant according to the judgment result, and calculating the time range of the user reaching the pre-selected target merchant according to the time information corresponding to the geographical location information of the pre-selected target merchant.
In this embodiment, when the number of times of occurrence of the geographic location information is greater than the second threshold, it may be determined that the merchant corresponding to the geographic location information may be a merchant that the user frequently visits, and the merchant corresponding to the geographic location information whose number of times of occurrence is greater than or equal to the second threshold may be determined as the preselected target merchant. Then, the time range of the user arriving at the preselected target merchant can be calculated according to the recorded time information of the user arriving at the preselected target merchant.
S330: and setting the preselected target merchants with the span values of the time range smaller than the preset time span values as target merchants.
In this embodiment, the preset time span value may be preset according to a specific application, for example, the preset time span value is set to 2 hours. When the time range of the user reaching the preselected target merchant is calculated, the span value of the time range can be determined, and when the span value of the time range is smaller than the preset time span value, the preselected target merchant can be judged to be a merchant frequently visited by the user within a certain time range, and then the preselected target merchant can be determined to be a target merchant. Specifically, for example, if the time from 10 times of the user to a certain merchant is 17:30, 17:35, 18:25, 17:39, 17:25, 17:50, 17:40, 17:45, 18:20, and 18:05 in sequence, the time range may be 17:25 to 18:25, and accordingly, the span value of the time range is 1 hour. The time span value of 1 hour is less than the preset time span value of 2 hours, so that the merchant can be judged to be a merchant that the user frequently goes in a certain time span, and the merchant can be determined to be a target merchant.
In addition, in some embodiments, when the span value of the time range is greater than or equal to the preset time span value, it may be determined that the preselected target merchant may be a merchant that the user visits many times in a short period due to a special condition, and is not a merchant that the user often visits. Specifically, for example, the time from 10 times of the user to a certain merchant is 8:30, 10:35, 15:25, 17:39, 11:25, 9:50, 20:30, 17:45, 10:20, and 13:05 in sequence, the time range is 8: 30-20: 30, and correspondingly, the time range span value is 12 hours, and the time range span value is greater than the preset time span value. Therefore, it can be determined that the merchant is likely to be a merchant that the user has visited many times in a short period of time due to a particular situation, and is not a merchant that the user has frequently visited.
The mode of determining the target merchant in the embodiment can determine the merchant meeting the requirement of the user, and can also exclude merchants which are visited by the user for many times in a short period due to a special condition, so that the target merchant meeting the actual requirement of the user can be screened out.
In addition, in the embodiment of the present application, an implementation manner of determining a target merchant on the historical path track according to the historical path track is not limited to the foregoing manner, and in practical application, the target merchant may also be determined in other manners according to a practical application scenario, and the present application is not limited to the foregoing embodiment.
S130: and pushing the push information of the target merchant to the user.
In some embodiments, the pushing the push information of the target merchant to the user may include:
and prompting the pushing information of the target merchant to a user on the historical path track displayed on a map interface.
In some embodiments, prompting the push information of the target merchant to the user on the historical path track displayed on the map interface may include recording and displaying the push information at a preset information identifier of geographic position information corresponding to the push information in the historical path track displayed on the map interface, and displaying the push information at the preset information identifier. Specifically, for example, the preset message identifier may be preset in the geographic location information of the historical route track displayed on the map interface.
Furthermore, the map interface can record and display the path identifier of the historical path track. In practical application, for example, when the user is going to go home from work, the user can directly check the corresponding interface according to the path identifier of 'go home from work' to obtain the push information corresponding to the interface, so that the user can quickly determine the push information which is likely to reach the merchant, and better user experience is provided. Fig. 4 is a schematic diagram of a push information presentation interface provided in an embodiment of the present application. As can be seen from the figure, when the user clicks the route identifier of "go home from work", the push information of the target merchant in the historical route track corresponding to the route identifier of "go home from work" may be prompted to the user on the map interface. In the specific application, after a user goes home, the user can check a corresponding interface according to the path identifier of 'going home after work', then the user can haircut at the hairdressing room A and then go to the supermarket B for shopping, wherein the hairdressing room A and the supermarket B are both on a historical path track on the way of the user going home after work, the classification recommendation of the push information is carried out according to the historical path track, the life circle of the user can be connected in series, a series of recommendations of different scenes are carried out, and the user experience is effectively improved.
In some embodiments, prompting the user for the push information of the target merchant on the historical path track presented on the map interface may include:
and sequencing the push information of the target merchant on the historical path track and prompting the push information to a user in a list interface corresponding to the historical path track.
It is understood that in some application scenarios, the execution subject of each step may be a user handheld device, such as a mobile terminal, or the like, or the execution subject may also be a server, such as an information push server, or the user handheld device and the server interact with each other to implement each step.
Fig. 5 is another schematic diagram of a push information presentation interface provided in an embodiment of the present application. As can be seen from the figure, when the user clicks the path identifier of "go home from work", the push information of the target merchant in the historical path track corresponding to the path identifier of "go home from work" may be prompted to the user in the form of a list.
In addition, the display form for implementing the push information in the embodiment of the present application is not limited to the above-mentioned manner, and in practical applications, there may be other forms according to specific application scenarios, for example, the push information may be displayed in a list manner, and the present application is not limited to the embodiment.
Therefore, in the embodiment of the information pushing method, the historical path track of the user is obtained, and the target merchant meeting the user requirement and the pushing information corresponding to the target merchant are determined on the historical path track according to the historical path track; and then pushing the push information of the target merchant to the user for the user to select. Compared with the prior art, the technical scheme of the embodiment of the application can be used for pushing information based on the historical path track meeting the requirements of the user, so that the shop arrival rate of the user can be effectively improved, and meanwhile, the user experience is also effectively improved.
An embodiment of an information pushing apparatus according to the present application is described below, and fig. 6 is a schematic diagram of an information pushing apparatus according to the present application. As shown in fig. 6, the apparatus 600 may include:
a path track obtaining module 610, configured to obtain a historical path track of a user;
the information determining module 620 may be configured to determine, according to the historical path trajectory, a target merchant on the historical path trajectory and push information corresponding to the target merchant;
the information pushing module 630 may be configured to push the pushed information of the target merchant to the user.
In a preferred embodiment, the path trajectory acquisition module may include:
the first calculating unit may be configured to calculate a historical path track of the user according to the acquired historical path information of the user;
the second calculating unit may be configured to calculate a plurality of historical path trajectories of the user according to the acquired historical path information of the user, and use one historical path trajectory selected or set by the user as the historical path trajectory of the user.
In a preferred embodiment, the information determining module may include:
the first judging unit may be configured to judge whether the number of times that the target geographic location information appears in the historical path trajectory is greater than a first threshold;
the first setting unit may be configured to set, as the target merchant, the merchant corresponding to the target geographic location information whose occurrence frequency is greater than the first threshold as the determination result.
In a preferred embodiment, the information determining module may include:
the second judging unit may be configured to judge whether the number of times that the target geographic location information appears in the historical path trajectory is greater than a second threshold;
the data processing unit may be configured to determine, as a preselected target merchant, a merchant corresponding to the geographic location information whose occurrence frequency is greater than a second threshold as a result of the determination, and calculate, according to time information corresponding to the geographic location information of the preselected target merchant, a time range in which the user reaches the preselected target merchant;
and the second setting unit can be used for setting the preselected target merchants with the span values of the time range smaller than the preset time span value as the target merchants.
In a preferred embodiment, the information pushing module may include at least one of the following:
the first information prompting unit can be used for prompting the pushing information of the target merchant to a user on the historical path track displayed on a map interface;
the second information prompting unit may be configured to sort the push information of the target merchant on the historical path track and then prompt the sorted push information to the user in a list interface corresponding to the historical path track.
Therefore, in the embodiment of the information pushing method and device, the historical path track of the user is obtained, and the target merchant meeting the user requirement and the pushing information corresponding to the target merchant are determined on the historical path track according to the historical path track; and then pushing the push information of the target merchant to the user for the user to select. Compared with the prior art, the technical scheme of the embodiment of the application can be used for pushing information based on the historical path track meeting the requirements of the user, so that the shop arrival rate of the user can be effectively improved, and meanwhile, the user experience is also effectively improved.
Although the present application refers to the description of data acquisition, processing, such as LBS, GPS, mobile communication network, etc., the present application is not limited to the case where it is necessary to be a complete standard or the data processing application environment mentioned. The above description referred to in the various embodiments of the present application is only applicable in some embodiments of the present application. Of course, other non-inventive variations of the processing method steps described in the above embodiments consistent with the present application may still be implemented in the same application, and are not described herein again.
Although the present application provides method steps as described in an embodiment or flowchart, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or client product executes, it may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures.
The above embodiments illustrate means or modules, which may be embodied by a computer chip or entity, or by an article of manufacture having some functionality. For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, in implementing the present application, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units.
Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may therefore be considered as a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, classes, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a mobile terminal, a server, or a network device) to execute the method according to the embodiments or some parts of the embodiments of the present application.
The embodiments in the present specification are described in a progressive manner, and the same or similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. The application is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, mobile communication terminals, multiprocessor systems, microprocessor-based systems, programmable electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
While the present application has been described with examples, those of ordinary skill in the art will appreciate that there are numerous variations and permutations of the present application without departing from the spirit of the application, and it is intended that the appended claims encompass such variations and permutations without departing from the spirit of the application.