WO2014036854A1

WO2014036854A1 - Cloud pushing method, system and device

Info

Publication number: WO2014036854A1
Application number: PCT/CN2013/078872
Authority: WO
Inventors: 巫国忠; 唐虹刚
Original assignee: 百度在线网络技术（北京）有限公司
Priority date: 2012-09-06
Filing date: 2013-07-05
Publication date: 2014-03-13
Also published as: CN102882936A; CN102882936B

Abstract

The present invention provides a cloud pushing method, comprising the following steps of: receiving a using time and/or a usage scenario for a user using a mobile terminal recorded by the mobile terminal and a property sign of the mobile terminal; calculating a preferable pushing time for the user according to the using time and/or the usage scenario; obtaining pushing content pushed to the user according to the property sign, and pushing the pushing content to the mobile terminal in the preferable pushing time. According to the present invention, the time and the scenario for the user using the mobile terminal are analyzed to provide an individual customized service for the user, and push information to the user at a proper time and place, so that a possibility of the information being clicked is improved, and user experience is improved. The present invention further discloses a cloud pushing device, another cloud pushing method, a mobile terminal and a cloud pushing system.

Description

Cloud push method, system and device

The present invention relates to the field of computer science and technology, and in particular, to a method, system and device for cloud push. Background technique

Traditional Internet access is generally performed by the user and the server returns the result. The push service passively accepts the request to actively send the message, and the server actively sends the message to the client, and the client chooses to receive.

The existing technologies for implementing push services mainly include the following two methods:

A technical solution for real-time push services. Regardless of the actual usage of the user on the mobile terminal, when the information arrives at the server, the server immediately pushes the information to the user. This method is suitable for types of push information with high timeliness, such as weather forecast, traffic conditions, etc. Users expect to receive update information at the first time.

A technical solution for personalized push services. Personalized push services generally focus on content personalization, collecting information and preferences of users in mobile terminals. For users who prefer a tech news type, the server pushes for technology-type information, such as advertisements for technology products. It is also possible to accumulate a large amount of original data by collecting information of the user using the social network or the browsing information of the user using the browser, and cluster the information out of the user's preference or content of interest, for example, implementing personalized recommendation like advertisement push. . Push service can also be carried out according to the geographical location, and the discount information of the surrounding merchants is pushed according to the geographical location where the user moves the device. In general, however, such push services are based on the user's personal information, identifying the user's individual needs and optimizing the push content.

However, in terms of how to collect from a large number of user information and how to use it effectively, current technical solutions do not fully consider the unique nature of mobile devices, such as Spare mobility and fragmentation of users' mobile phone time periods. The time when the user uses the mobile phone is fragmented, and there is a certain regularity in the overall situation. For example, the user may take 10 minutes to watch Weibo in the morning, 15 minutes of news on the way to work, and 30 minutes in the evening. Blogs, etc. The existing push service solutions have not fully utilized these features to improve the product design of the push service, so that the pushed message loses the opportunity to obtain the user's attention at the first time. Once the first point in time is lost, the possibility of the user ignoring the push information will increase, especially if too many new message prompts are accumulated in the user's information center.

The scene of the mobile device user's use of the device also directly affects the operation taken by the user when receiving the push information. For example, when the user is lying on the sofa at home and browsing the news on the mobile phone, if there is push information, the possibility of the user viewing the message is more than normal. In the work, the probability of being on the road is great, so the effect of the push service is better.

Most existing mobile terminals, such as iPhones and Android phones, have a unified message center. All application-related message reminders, new messages, etc. are stored in the message center. When more new messages are accumulated, users often do not have the time and effort to click through to view all new message prompts. In order to improve the visual discomfort caused by messy message reminders, the user may choose to clear all new message reminders at a time, and the information pushed by the server may not be clicked by the user at all.

In summary, the push information needs to push the content that the user is interested in at the right time and in the scene. The prior art does not provide a good solution to this demand.

The object of the present invention is to at least solve one of the above technical drawbacks.

To this end, the first object of the present invention is to provide a cloud push method, which analyzes the time and scene of a user using a mobile terminal, provides a personalized customization service for the user, and pushes information for the user at an appropriate time and place, thereby improving The possibility that the information was clicked improved the user experience.

A second object of the present invention is to provide a cloud push device.

A third object of the present invention is to propose another method of cloud pushing. A fourth object of the present invention is to provide a mobile terminal.

A fifth object of the present invention is to provide a cloud push system.

In order to achieve the above object, an embodiment of the first aspect of the present invention discloses a method for cloud push, comprising the steps of: receiving a usage time and/or a usage scenario of a user recorded by a mobile terminal using the mobile terminal, and the mobile terminal Attribute tag; calculating a preferred push time for the user based on the usage time and/or usage scenario; obtaining a push to the user based on the attribute tag.

In an embodiment of the present invention, by recording and analyzing the user's usage time and/or usage scenario, a preferred push time is obtained, and the push time is personalized for the user according to the record of each user, and is optimized during the push time. The information pushed by the user takes into account the user's usage scenarios and usage habits. Try to push at the time when the user may read the information, thereby increasing the probability that the information is clicked and reading, and avoiding the real-time push may be pushed to the user when the user is inconvenient to read. The inconvenience caused has improved the user experience.

In an embodiment of the invention, the attribute tag of the mobile terminal includes the physical identity of the mobile terminal and/or the identity information of the user.

In an embodiment of the present invention, the usage scenario includes location information of the mobile terminal, posture information when the user uses the mobile terminal, motion information when the user uses the mobile terminal, and the One or more of the light intensity information of the environment in which the mobile terminal is located.

In an embodiment of the present invention, calculating a preferred push time for the user according to the usage time and/or a usage scenario, specifically: calculating, according to the usage time and/or using a scenario, according to an optimization time slice algorithm The preferred push time of the user.

In an embodiment of the present invention, the optimization time slice algorithm includes the following steps: obtaining usage time of the mobile terminal by the user in daily use, and marking and sorting the usage time; The length of time of the use time; calculating a weight value for each use time according to the length of time/or use scenario calculation. In an embodiment of the present invention, the method further includes: obtaining a call record of the user; if the ratio of the user's talk time to the use time is greater than a preset value during the use time, the use time is The corresponding weight value is set to zero.

In an embodiment of the present invention, the method further includes: summarizing weight values of the usage time of the user in N days, to calculate a preferred push time for the user, where N is greater than

An integer of 1.

An embodiment of the second aspect of the present invention discloses a cloud push device, including: a receiving module, configured to receive, by a mobile terminal, a usage time and/or a usage scenario of a user using the mobile terminal and attributes of the mobile terminal a calculation module, configured to calculate a preferred push time for the user according to the usage time and/or a usage scenario; a push module, configured to obtain, according to the attribute tag, push content pushed to the user, and The push content is pushed to the mobile terminal during a preferred push time.

The usage scenario includes location information of the mobile terminal, posture information when the user uses the mobile terminal, motion information when the user uses the mobile terminal, and light intensity information of an environment in which the mobile terminal is located One or more of them.

In one embodiment of the invention, the computing module calculates a preferred push time for the user based on the usage time and/or usage scenario in accordance with an optimized time slice algorithm.

In an embodiment of the present invention, the computing module obtains that the user uses the device every day. Determining the usage time of the mobile terminal, marking and sorting the usage time, calculating a length of time each time the usage time, and calculating a weight for each usage time according to the length of time/or using a scene calculation value.

In an embodiment of the present invention, the calculating module is further configured to obtain a call record of the user, and if a ratio of the user's talk time to the use time is greater than a preset value in use time, The weight value corresponding to the usage time is set to zero.

In an embodiment of the present invention, the calculation module aggregates the weight values of the usage time of the user in the N days to calculate a preferred push time for the user, where N is an integer greater than 1.

An embodiment of the third aspect of the present invention discloses a method for cloud push, comprising the steps of: collecting usage time and/or usage scenario of a user using a mobile terminal; using the usage time and/or usage scenario and the mobile terminal The attribute tag is sent to the cloud server, so that the cloud server calculates a preferred push time for the user according to the usage time and/or a usage scenario, and obtains push content according to the attribute tag; and a receiving module, configured to receive the The push content pushed by the cloud server to the mobile terminal during the preferred push time.

In the embodiment of the present invention, the usage time and/or usage scenario of the user is collected and transmitted to the cloud server, so that the cloud server can obtain the user's usage information, thereby making a judgment on the user's situation and proposing a more accurate service.

An embodiment of the fourth aspect of the present invention discloses a mobile terminal, including: an acquisition module, configured to collect usage time and/or usage scenarios of a user; and a sending module, configured to use the usage time and/or usage scenario and move The attribute tag of the terminal is sent to the cloud server, so that the cloud server calculates a preferred push time for the user according to the usage time and/or a usage scenario, and obtains push content according to the attribute tag; and a receiving module, configured to receive The push content pushed by the cloud server to the mobile terminal during the preferred push time.

In an embodiment of the present invention, the mobile terminal collects and sends the usage time and/or the usage scenario of the user to the cloud server, so that the cloud server can obtain the usage information of the user, thereby The situation makes a judgment and proposes a more precise service.

The embodiment of the fifth aspect of the present invention discloses a cloud push system, comprising: a cloud push device disclosed in the embodiment of the second aspect of the present invention and a mobile terminal disclosed in the embodiment of the fourth aspect of the present invention .

In an embodiment of the present invention, by analyzing and calculating the usage time and/or the usage scenario of the user, a preferred push time is obtained, and the push time is customized for the user according to the record of each user, and is presented to the user in the preferred push time. The pushed information takes into account the user's usage scenarios and usage habits. Try to push at the time when the user may read the information, thereby increasing the probability that the information is clicked and reading, and avoiding the real-time push may be pushed to the user when the user is inconvenient to read. The inconvenience has improved the user experience.

The additional aspects and advantages of the invention will be set forth in part in the description which follows.

The above and/or additional aspects and advantages of the present invention will become apparent and readily understood from

FIG. 1 is a flowchart of a method for cloud push according to an embodiment of the present invention; FIG.

2 and 3 are schematic diagrams showing a state of use of a user according to an embodiment of the present invention;

4 is a schematic diagram of data transmission according to an embodiment of the present invention;

FIG. 5 is a bar graph of user usage time according to an embodiment of the present invention; FIG.

6 is a schematic structural diagram of an apparatus for cloud push according to an embodiment of the present invention;

7 is a flow chart of a method for cloud push according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention; FIG.

FIG. 9 is a schematic structural diagram of a system for cloud push according to an embodiment of the present invention. The embodiments of the present invention are described in detail below, and the examples of the embodiments are illustrated in the drawings, wherein the same or similar reference numerals are used to refer to the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the drawings are intended to be illustrative of the invention and are not to be construed as limiting.

A method for cloud push according to an embodiment of the present invention is described below with reference to FIG. 1, which includes the following steps: Step S110: Receive a usage time and/or a use scenario of a user using the mobile terminal recorded by the mobile terminal and an attribute tag of the mobile terminal.

The attribute tag of the mobile terminal includes the physical identity of the mobile terminal and/or the identity information of the user. The usage scenario includes one or more of location information of the mobile terminal, posture information when the user uses the mobile terminal, motion information when the user uses the mobile terminal, and light intensity information of the environment in which the mobile terminal is located.

In one embodiment of the present invention, each time the user uses the mobile terminal, information is collected and the information parameters defining the user's use of the mobile terminal are as follows:

(a) The device unique attribute tag (UID) consists of two parts:

(1) The physical standard of the mobile terminal is only : 3⁄4. The IMEI (International Mobile Equipment Identity number) number of the mobile phone and the IMSI (International Mobile Subscriber Identification Number) number.

(2) User identity information: For example, the user account, the user account is the user logo of the user on a service system platform, specifically the email address or the account of the website, and the mobile terminal may be used by multiple people, each person Log in with a different account.

The user's identity information is optional. For those who do not set up login on the mobile terminal, the default user identity information can be used. The user is determined by the physical attributes of the mobile terminal and/or the identity information of the user, and the data record associated with it is used.

(b) Start using time point: Identify each lighting of the screen as the starting point of a new user using the mobile terminal, and record the time point, marked as StartTime.

(c) End of use time point: Each time the screen is turned off as the end point of the user's use of the mobile terminal once, the time point is recorded, and is marked as EndTime.

(d) Call time record: Obtain the call time record of the user between [StartTime, EndTime], and separately identify the user's call behavior, marked as CallTime.

(e) Screen click record: Between [StartTime, EndTime], record the operation time point of the user each time the screen is clicked, marked as ClickList.

(f) Attitude information when the user uses the mobile terminal and the motion letter when the user uses the mobile terminal Information: According to the sensor device on the mobile terminal, the position of the user when using the device is recognized, such as "standing", "lying" and "sitting", etc., the position may also include other situations, techniques in the field The personnel can easily expand according to the needs of the user. The value of the motion information when the user uses the mobile terminal is, for example, "stationary" and "moving", and the motion information can also include other values, for example, finely dividing the moving speed. Combine both the body position and the movement information and mark it as BodyStatus, for example: "Standing (still)", "Standing (moving)", "Lying (still)", "Lying (moving)", etc. Wait.

The posture of the user when using the mobile terminal can be sensed by an acceleration sensor on the mobile terminal, such as an accelerometer and a gyroscope, to sense the azimuth, rotation angle, and tilt angle on the horizontal plane. It is possible to detect that the mobile terminal is in a state of positive vertical, vertical vertical, left horizontal, right horizontal, vertical, and downward. The direction sensor is used to determine the position of the user, for example, whether the user is standing or lying. When the user uses the device, the orientation angle of the device is different in different postures of the station and the lying. The direction sensor can distinguish between the two cases. As shown in Fig. 2 and Fig. 3, the judgment of the user's posture "standing" and "lying" is realized by the data returned by the direction sensor. Other postures can also be judged when the mobile terminal is in the vertical, vertical, left horizontal, right horizontal, vertical, and downward directions when the user uses the mobile terminal.

The acceleration sensor can also be used to determine the motion state of the mobile terminal. Acceleration is a spatial vector. By measuring the components on its three axes, you can understand the motion state of the object and guess whether the user is still or moving. For push messages, when the user is at rest, such as lying on a sofa, they are generally more willing to view the new push message. Conversely, in the mobile state, users on the bus may find it inconvenient. However, the above examples are for illustrative purposes only, and are not absolute, such as on a subway, or when the user is more comfortable, it is easier to click on the push message. Because of the uncertainty of BodyStatus, the statistically optimized time slice algorithm is also used to optimize the push effect.

(g) Location information of the mobile terminal: The location information when the user uses the mobile terminal is obtained by base station positioning or GPS (Global Position System) positioning, and the user's location can be inferred based on the time of the user using the mobile terminal. Marked as Place, the values are, for example, "fixed place", "indeterminate place", etc.

Among them, "fixed place" means that users often use mobile terminals in certain fixed geographical locations. For example, users may often use mobile terminals at home, in offices, and in restaurants. When a user uses a mobile terminal in a fixed location, they are generally more willing to receive new messages. "Uncertain place" means other locations than fixed places, such as when the user is on the move, or when going out, there is often no more More time and effort to browse push information.

The method for judging the fixed location of the user is: recording the position coordinates of the mobile terminal at the same time in recording the user's use of the mobile terminal, which may be performed by base station positioning or GPS positioning. Then, according to the change of coordinates, it is identified whether the user is in a certain fixed position. For example, when the user uses the mobile phone at home, the coordinate value obtained each time should be very close, can be regarded as the same position, after collecting a large amount of position information, and then The recurring position coordinates are extracted based on the statistical rule, and these positions are used as a fixed place for the user.

(h) Light intensity information of the environment in which the mobile terminal is located: according to the sensor device on the mobile terminal, the external light condition when the device is used is identified, and is marked as Light, and the value includes, for example, "very bright".

"Generally bright", "dark", dark", etc., the specific value can be divided according to the light intensity, for example, the average is divided into four stages, each of which corresponds to "very bright", "normally bright", "dark" " , 艮 " " , can also be divided according to the actual situation, for example, 艮 "" and 艮 "" occupies a large range of light intensity, etc., it should be understood that in the actual implementation process, according to the actual demand according to the light Multiple values. The ambient light sensor on the mobile terminal collects the light conditions of the location where the mobile terminal is located. The intensity of external light will have an impact on the user's use of the mobile terminal. For example, in the hot sun, the user generally does not click on the received push message, and the user may use the mobile terminal without lights at night, and the push received at this time. The message is more likely to be clicked by the user.

As shown in Table 1 below, the collection of each message can be represented as a row of records. As shown in FIG. 4, FIG. 4 is an illustration of data transmission of the method. The user's mobile device, that is, the mobile terminal, is sent to the cloud server in a batch process after the information is collected. It should be understood that it can also be sent to other servers or devices, and the batch data sent is marked as UserTable. After receiving the data uploaded by the mobile terminal, the cloud server stores the data in the database table corresponding to each user, and forms a mapping relationship by using the unique attribute flag of the user equipment. The data for each user in the table is independent, so each user's push strategy is also independent, thus enabling personalization.

Table 1 Step S120: Calculate the preferred push time for the user according to the usage time and/or the usage scenario. In one embodiment of the invention, the preferred push time for the user may be calculated based on the time of use and/or the usage scenario in accordance with the optimized time slice algorithm.

Specifically, the optimized time slice algorithm includes the following steps: Step S121: Obtain the usage time of the mobile terminal used by the user in daily, and mark and sort the usage time.

Step S122: Calculate the length of time of each use time.

Step S123: Calculate the weight value of each use time according to the length of time / or use the scene calculation. The optimized time slice algorithm is described below with a specific example. It can be understood that this example is for illustrative purposes only, and the embodiment of the present invention is not limited thereto.

(1) The data of the user using the mobile terminal is obtained from the database according to the unique attribute tag (UID) corresponding to the user using the mobile terminal.

(2) Sort the daily data in chronological order, calculate the length of each use time and divide the user's different usage time each day, mark the usage time and related information as TimeRecord, and TimeRecord contains the fields defined in Table 2:

Table 2

(3) Calculate the weight value of the time of use of TimeRecord according to the calculation rule of the weight value. The calculation of the weight value for each time of use in the example is as follows:

The value of the weight value ranges from 0 to 1. The larger the value, the more meaningful the usage time is and the better it is to perform the push. The default value of the weight value is k, and the growth and reduction are 0.1. Different field values in TimeRecord will affect the increase or decrease of the weight value, which is calculated as follows:

The longer the R1 time length, the corresponding weight value is added.

The longer the R2 talk time, the lower the corresponding weight value. If the ratio of the user's talk time to the use time is greater than the preset value during the usage time, the weight value corresponding to the use time is set to zero. For example, if the user's time all calls, it means that the usage time is not suitable for pushing information to the user.

The higher the R3 screen click frequency, the lower the corresponding weight value. For example, the user needs to frequently click on the screen when playing the game, and the usage time is not suitable for pushing the information to the user. Attitude information when the R4 user uses the mobile terminal: When the value is "lying", the corresponding weight value is added, and "Standing (moving)" lowers the corresponding weight value.

R5 Light intensity information of the environment in which the mobile terminal is located: The light is generally bright, and the corresponding weight value is increased, which is brighter, and the corresponding weight value is lowered.

As shown in FIG. 5, each usage time can be represented as a block in FIG. 5. The horizontal axis of the graph represents time, and the vertical axis represents weight values. The area of each square represents the importance of the time of use. It is more suitable for information push during this usage time.

The TimeRecord weight value indicates that the user is in a certain state during the usage time. For example, when the user uses the mobile terminal, the posture information is "lying" and the weight of "standing" is higher, because the user is generally physically and mentally lying while lying down. A more comfortable state, the probability of receiving and clicking on push messages is large.

(4) Summarizing the weight values of the user's usage time in N days to calculate a preferred push time for the user, where N is an integer greater than one. For example, N=30 can be taken, and the usage time period list data of the user using the mobile terminal is counted within 30 days. The usage time in FIG. 5 is expressed in a two-dimensional space in the form of a hash, and the area with the most overlap is counted, that is, the user's use time has been formed to form a certain rule, and the possibility that the user continues to use the mobile terminal during the use time is predicted. Higher.

Specifically, for different days of the week, such as Monday, the program takes out all the data of Monday, and then hashes it into the above two-bit table, and calculates the area where the usage time overlaps and the area with the high time distribution density.

There are many calculation methods, and one possible implementation is described below:

Select the time range [Tn-1, Τη], the sum of all time-use areas in this interval (the overlapping areas need to be repeatedly accumulated to calculate the area), denoted as ∑(η-1,η), in the total time axis [0,24 In the hour, the calculation is performed in steps of m minutes (for example, the value of m can be 5 minutes, 10 minutes, 20 minutes, 30 minutes, etc.), for example, the value is 5 minutes first, and the time axis is calculated for each step increment. The sum of the use time areas of each of the scattered intervals is then sorted from high to low for the use time area of each of the intervals, and a set of preferred push times can be obtained at a given step size. The step size m is then modified to iterate to obtain a set of preferred push times for the next step, for example 10 minutes. By analogy, a set of multiple preferred push times can be obtained under all step value conditions, which can be understood as a time of use suitable for pushing information to the user, and a set of minimum values of the step size can be prioritized.

(5) The sorted usage time is stored in the database to form a user-specific preferred push schedule, as shown in Table 3. The mobile terminal can select the push timing based on the information in this table. Due to the user The status of the seven days of the week may be different, so it is necessary to calculate the mobile terminal usage for different days for the user to more accurately understand the user and perform different push policies according to different dates. The optimization time-of-use algorithm is used to complete the calculation of the user's original data. The result is: A record table that reflects the user's preferred push time, which records the user's 7-day-a-week, which time period within 24 hours is more likely to view the push information. For example, a user uses a mobile phone in a fixed place between 8 and 9 o'clock every Saturday, but the frequency of screen clicks is lower than the frequency of clicks required by the average game. The user is likely to be browsing the web. Priority can be given to pushing messages to users during this time period.

Table 3 In the process of calculation, it is also necessary to consider the interference of national statutory holiday factors. For the time of use that falls within the holiday, it may not be appropriate to calculate the preferred push time based on the previously collected user information. For example, on Mondays of the holiday, the user does not need to go to work, so the time model of the user using the mobile phone may change, and may be closer to the usage model on Saturday and Sunday.

Step S130: Obtain the push content pushed to the user according to the attribute tag, and push the push content to the mobile terminal at the preferred push time.

For example, the push service scheduler can be launched to select the appropriate time to push information for the corresponding user based on the time period range in the preferred push time set. Each user saves a preferred push time table, from which the decision is made to schedule the execution of the push. The preferred push schedule content for each user is generally different, so different users will receive push messages at different points in time.

In addition, at the first time when the user receives the push message, if the user clicks on the message, then the user For this push to be a direct hit, you need to increase the weight value of the corresponding usage time, which is the weight value in TimeRecord. If the user does not view the message at the first time, the weight value is not increased. If the user does not view this message, the weight value of the corresponding usage time is lowered. Through the feedback of the actual situation, we can further understand the user's usage habits and optimize the push time.

The cloud push method according to the embodiment of the present invention collects the time situation of the user using the mobile terminal, and estimates the use scenario by using the time and location information of the mobile terminal, and calculates an optimal time period for pushing the information to the user through an algorithm, which is different. Users provide personalized customization services. Information Push service tries to avoid disturbing users, and chooses to arrive at a more comfortable and appropriate time for users, thereby improving user acceptance and click-through rate and improving user experience.

In order to implement the above embodiments, the present invention also proposes a cloud push device.

An apparatus for cloud push according to an embodiment of the present invention will be described below with reference to FIG. As shown in FIG. 6, the cloud push device includes: a receiving module 11, a calculating module 12, and a pushing module 13. Specifically, the receiving module 11 is configured to receive a usage time of the user using the mobile terminal and/or use the scene and a property tag of the mobile terminal recorded by the mobile terminal. The calculation module 12 is configured to calculate a preferred push time for the user based on the time of use and/or the usage scenario. The push module 13 is configured to obtain the push content pushed to the user based on the attribute tag, and push the push content to the mobile terminal within the preferred push time.

The attribute tag of the mobile terminal includes a physical identifier of the mobile terminal and/or identity information of the user. The usage scenario includes one or more of location information of the mobile terminal, gesture information when the user uses the mobile terminal, a motion message when the user uses the mobile terminal, and light intensity information of the environment in which the mobile terminal is located.

In an embodiment of the present invention, the user receives the usage time and/or usage scenario of the mobile terminal and the attribute tag of the mobile terminal, and collects and defines the user for each time the user uses the information collected by the mobile terminal. The information parameters for using the mobile terminal are as follows:

(a) The device unique attribute tag (UID) consists of two parts:

(1) Physical identification of the mobile terminal: such as the IMEI number and IMSI number of the mobile phone.

(b) Start using time point: recognize each lighting of the screen as a new user usage shift The starting point of the mobile terminal, record the time point, marked as StartTime.

(f) posture information when the user uses the mobile terminal and motion information when the user uses the mobile terminal: According to the sensor device on the mobile terminal, the posture of the user when using the device, such as "standing", "lying" and "Sit" and the like, the positional situation may also include other situations, and those skilled in the art can easily expand according to the needs of the user, and the motion information values when the user uses the mobile terminal are, for example, "stationary" and "mobile", exercise. The information may also include other values, such as a fine division of the speed of movement, and the like. Combine both the body position and the movement information and mark it as BodyStatus, for example: "Standing (still)", "Standing (moving)", "Lying (still)",

"Lying (moving)" and so on.

When the user uses the mobile terminal, the posture can be sensed by an acceleration sensor on the mobile terminal, such as an accelerometer and a gyroscope (induction of the azimuth, rotation angle and tilt angle on the horizontal plane), so that the mobile terminal can be detected to be positive. Vertical, inverted vertical, left horizontal, right horizontal, elevation, and down state. The direction sensor is used to determine the position of the user, for example, whether the user is standing or lying. When the user uses the device, the orientation angle of the device is different in different postures of the station and the lying. The direction sensor can distinguish between the two situations. As shown in Fig. 2 and Fig. 3, the data returned by the direction sensor realizes the judgment of the user's posture "standing" and "lying". Other postures can also be judged when the mobile terminal is in the vertical, vertical, left horizontal, right horizontal, vertical, and downward directions when the user uses the mobile terminal.

The acceleration sensor can also be used to determine the motion state of the mobile terminal. Acceleration is a space vector. By measuring the components on its three axes, you can understand the motion state of the object and guess whether the user is still or moving. For push messages, when the user is at rest, such as lying on a sofa, they are generally more willing to view the new push message. Conversely, in the mobile state, users on the bus may find it inconvenient. However, the above examples are for illustrative purposes only, and are not absolute, such as on a subway, or when the user is more comfortable, it is easier to click on the push message. Because BodyStatus is uncertain, the statistics-based optimization time slice algorithm is also used to optimize the push effect. (g) Location information of the mobile terminal: The location information when the user uses the mobile terminal is obtained by base station positioning or GPS positioning, and combined with the time of the user using the mobile terminal, the location of the user can be inferred, marked as Place, and the value is, for example, " Fixed places", "indeterminate places", etc.

Among them, "fixed place" means that the user often uses the mobile terminal in certain fixed geographical locations, such as the user may often use the mobile terminal at home, office, or restaurant. When a user uses a mobile terminal in a fixed location, they are generally more willing to receive new messages. "Uncertain location" means that other locations than the fixed location, such as when the user is on the move or out, often do not have more time and effort to view the push information.

(h) Light intensity information of the environment in which the mobile terminal is located: According to the sensor device on the mobile terminal, the external light condition of the device is identified, and is marked as Light, and the value includes, for example, "very bright".

As shown in Table 1, each time information collection can be represented as one line record, and the receiving module 11 receives each piece of information recorded by the mobile terminal.

In one embodiment of the invention, the calculation module 12 calculates a preferred push time for the user based on the time of use and/or the usage scenario in accordance with the optimized time slice algorithm.

Specifically, the calculation module 12 obtains the usage time of the user using the mobile terminal in daily, marks and sorts the usage time, calculates the length of time of each use time, and calculates each use according to the length of time/or using the scene calculation. The weight value of time.

The following describes the optimized time slice algorithm with a specific example. It can be understood that This example is for illustrative purposes only, and embodiments of the invention are not limited thereto.

(1) The data of the user using the mobile terminal is obtained from the database according to the unique attribute tag corresponding to the user using the mobile terminal.

(2) Sort the daily data in chronological order, calculate the length of each use time and divide the user's different usage time each day, mark the usage time and related information as

TimeRecord, TimeRecord contains the fields defined in Table 2.

The longer the R1 time length, the corresponding weight value is added.

The higher the R3 screen click frequency, the lower the corresponding weight value. For example, when a user plays a game, the screen needs to be frequently clicked, and the usage time is not suitable for pushing information to the user.

R4 user's attitude information when using the mobile terminal: When the value is "lying", the corresponding weight value is added, and "Standing (moving)" lowers the corresponding weight value.

(4) Summarizing the weight values of the user's usage time in N days to calculate a preferred push time for the user, where N is an integer greater than one. For example, N=30 can be taken, and the user uses the time period list data of the mobile terminal for statistics within 30 days. The usage time in FIG. 5 is expressed in a two-dimensional space in the form of a hash, and the area with the most overlap is counted, that is, the user is considered to use time. A certain law has been formed, and it is highly probable that the user will continue to use the mobile terminal during this usage time.

Select the time range [Τη- Ι, Τη], the sum of all the time-use areas in this interval (the overlapping areas need to be repeatedly accumulated to calculate the area), denoted as ∑(η-1,η), in the total time axis [0,24 In the hour, the calculation is performed in steps of m minutes (for example, the value of m can be 5 minutes, 10 minutes, 20 minutes, 30 minutes, etc.), for example, the value is 5 minutes first, and the time axis is calculated for each step increment. The sum of the use time areas of each of the scattered intervals is then sorted from high to low for the use time area of each of the intervals, and a set of preferred push times can be obtained at a given step size. The step size m is then modified to iterate to obtain a set of preferred push times for the next step, for example 10 minutes. By analogy, a set of multiple preferred push times can be obtained under all step value conditions, which can be understood as a time of use suitable for pushing information to the user, and a set of minimum values of the step size can be prioritized.

(5) The sorted usage time is stored in the database to form a user-specific preferred push time table, as shown in Table 3. The mobile terminal can select the push timing based on the information in this table. Since the user may have different status in seven days of the week, it is necessary to calculate the usage of the mobile terminal for different days for the user to more accurately understand the user and perform different push policies according to different dates. The optimal use time algorithm completes the calculation of the user's original data. The result is: The response user's preferred push time record table records which time periods within 24 hours of the user are more likely to view the push information within 24 hours per day. For example, a user uses a mobile phone in a fixed place between 8 and 9 o'clock every Saturday, but the frequency of screen clicks is lower than the frequency of clicks required by the average game. The user is likely to be browsing the web. Priority can be given to pushing messages to users during this time period.

In the process of calculation, it is also necessary to consider the interference of the national statutory holiday factors. For the time of use that falls within the holiday, it may not be appropriate to calculate the preferred push time based on the previously collected user information. For example, on Mondays of the holiday, the user does not need to go to work, so the time model of the user using the mobile phone may change, and may be closer to the usage model on Saturday and Sunday.

In one embodiment of the present invention, the push module 13 may initiate a push service scheduler to select an appropriate timing to push information for the corresponding user based on the range of time periods in the preferred push time set. Each user saves the preferred push schedule, according to which table determines when to schedule execution push give away. The preferred push schedule content for each user is generally different, so different users will receive push messages at different points in time.

In addition, at the first time when the user receives the push message, if the user clicks on the message, the push is considered to be a direct hit, and the weight value of the corresponding use time, that is, the weight value in TimeRecord, needs to be increased. If the user does not view the message at the first time, the weight value is not increased. If the user does not view this message, the weight value of the corresponding usage time is lowered. The actual situation feedback can further understand the user's usage habits and optimize the push time.

The present invention also proposes another method of cloud push. A method of cloud push according to an embodiment of the present invention is described below with reference to FIG. 7, including the following steps:

S210: Collect usage time and/or usage scenario of the user using the mobile terminal.

The usage scenario includes one or more of location information of the mobile terminal, posture information when the user uses the mobile terminal, motion information when the user uses the mobile terminal, and light intensity information of the environment in which the mobile terminal is located.

S220: Send the usage time and/or the usage scenario and the attribute tag of the mobile terminal to the cloud server, so that the cloud server calculates the preferred push time for the user according to the usage time and/or the usage scenario and obtains the push content according to the attribute tag.

The attribute tag of the mobile terminal includes the physical identity of the mobile terminal and/or the identity information of the user.

S230: Receive the push content that the cloud server pushes to the mobile terminal during the preferred push time. In one embodiment of the present invention, each time the user uses the mobile terminal, information is collected and the information parameters defining the user's use of the mobile terminal are as follows:

(a) The device unique attribute tag (UID) consists of two parts:

(2) User identity information: For example, the user account, the user account is the user logo of the user on a service system platform, specifically the email address or the account of the website, and the mobile terminal may be used by multiple people, each person Log in with a different account. The identity information of the user is optional. For the login that is not set on the mobile terminal, the default user identity information may be used. The user is determined by the physical attributes of the mobile terminal and/or the identity information of the user, and uses the data records associated therewith.

(f) The posture information when the user uses the mobile terminal and the motion information when the user uses the mobile terminal: According to the sensor device on the mobile terminal, the posture of the user when using the device, such as "standing", "lying" and "Sit" and the like, the positional situation may also include other situations, and those skilled in the art can easily expand according to the needs of the user, and the motion information values when the user uses the mobile terminal are, for example, "stationary" and "mobile", exercise. The information may also include other values, such as a fine division of the speed of movement, and the like. Combine both the body position and the movement information and mark it as BodyStatus, for example: "Standing (still)", "Standing (moving)", "Lying (still)", "Lying (moving)", etc. Wait.

The acceleration sensor can also be used to determine the motion state of the mobile terminal. Acceleration is a space vector. By measuring the components on its three axes, you can understand the motion state of the object and guess whether the user is still or moving. For push messages, when the user is at rest, such as lying on a sofa, they are generally more willing to view the new push message. Conversely, in the moving state Next, users on the bus may find it inconvenient. However, the above examples are for illustrative purposes only, and are not absolute, such as on a subway, or when the user is more comfortable, it is easier to click on the push message. Because BodyStatus is uncertain, the statistics-based optimization time slice algorithm is also used to optimize the push effect.

The method for determining the fixed location of the user is: recording the position coordinates of the mobile terminal at the same time in recording the user's use of the mobile terminal, and the method may be through base station positioning or GPS positioning. Then, according to the change of coordinates, it is identified whether the user is in a certain fixed position. For example, when the user uses the mobile phone at home, the coordinate value obtained each time should be very close, can be regarded as the same position, after collecting a large amount of position information, and then The recurring position coordinates are extracted based on the statistical rule, and these positions are used as a fixed place for the user.

As shown in Table 1 below, the collection of each message can be represented as a row of records. As shown in FIG. 4, FIG. 4 is an illustration of data transmission of the method. The user's mobile device, that is, the mobile terminal, after the information is collected, is sent to the cloud server in a batch process, and it should be understood that it can also be sent to the mobile terminal. The bulk data sent by his server or device is marked as UserTable. After receiving the data uploaded by the mobile terminal, the cloud server stores the data in the database table corresponding to each user, and forms a mapping relationship by using the unique attribute flag of the user equipment. The data for each user in the table is independent, so each user's push strategy is also independent, thus enabling personalization.

In order to implement the above embodiments, the present invention also proposes a mobile terminal.

A mobile terminal according to an embodiment of the present invention will be described below with reference to FIG. As shown in FIG. 8, the mobile terminal includes: an acquisition module 21, a transmitting module 22, and a receiving module 23.

Specifically, the acquisition module 21 is configured to collect usage time and/or usage scenarios of the user. The sending module 22 is configured to send the usage time and/or the usage scenario and the attribute tag of the mobile terminal to the cloud server, so that the cloud server calculates the preferred push time for the user according to the usage time and/or the usage scenario, and obtains the push content according to the attribute tag. . The receiving module 23 is configured to receive the push content pushed by the cloud server to the mobile terminal during the preferred push time.

In an embodiment of the present invention, each time the user uses the information collected by the mobile terminal, the information parameters specifically collected and defined by the user using the mobile terminal are as follows:

(a) The device unique attribute tag (UID) consists of two parts:

(c) End of use time point: recognizes the closing of the screen each time as the user uses the mobile terminal once End point, record the time point, marked as EndTime.

"Lying (moving)" and so on.

(g) Location information of the mobile terminal: The location information when the user uses the mobile terminal is obtained by base station positioning or GPS positioning, and the time of the user using the mobile terminal can be inferred. The place, marked as Place, values such as "fixed place", "uncertain place", etc. Among them, "fixed place" means that users often use mobile terminals in certain fixed geographical locations. For example, users may often use mobile terminals at home, in offices, and in restaurants. When a user uses a mobile terminal in a fixed location, they are generally more willing to receive new messages. "Uncertain location" means that other locations than the fixed location, such as when the user is on the move or out, often have less time and effort to view the push information.

(h) Light intensity information of the environment in which the mobile terminal is located: According to the sensor device on the mobile terminal, the external light condition when the device is used is identified, and is marked as Light, and the values include, for example, "very bright" and "normally bright". "dark", dark", etc., the specific value can be divided according to the light intensity, for example, the average is divided into four stages, each stage corresponding to "very bright", "normally bright", "dark", dark" It can also be divided according to the actual situation. For example, the range of light intensity occupied by "bright" and "dark" is relatively large. It should be understood that, in actual implementation, the light is divided into multiple values according to actual needs. The ambient light sensor on the mobile terminal collects the light conditions of the location where the mobile terminal is located. The intensity of external light will have an impact on the user's use of the mobile terminal. For example, in the hot sun, the user generally does not click on the received push message, and the user may use the mobile terminal without lights at night, and the push received at this time. The message is more likely to be clicked by the user.

As shown in Table 1, the collection of each piece of information of the acquisition module 21 can be represented as one line of record. In the embodiment of the present invention, the mobile terminal collects and sends the user's usage time and/or usage scenario to the cloud server, so that the cloud server can obtain the user's usage information, thereby making a judgment on the user's situation and proposing a more accurate service. .

A cloud push system according to an embodiment of the present invention, as shown in FIG. 9, includes a cloud push device 110 according to any of the above-described embodiments of the present invention, and the mobile device described in any of the above embodiments. Terminal 120.

The cloud push system according to the embodiment of the present invention collects a situation in which a user uses a mobile terminal, and estimates a usage scenario by using a time, a location, and the like information of the mobile terminal, and calculates an optimal time period for pushing information to the user through an algorithm, for different users. Personalized customization services are provided. Information push The service information push service tries to avoid disturbing the user as much as possible, and tries to arrive at a more comfortable and appropriate time point for the user, thereby improving the user's acceptance of the information and the click rate, and improving the user experience.

In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" and the like means specific features described in connection with the embodiment or example. A structure, material or feature is included in at least one embodiment or example of the invention. In the present specification, the schematic representation of the above terms does not necessarily mean the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in a suitable manner in any one or more embodiments or examples. In the present invention, the term "plurality" means two or more.

While the embodiments of the present invention have been shown and described, it will be understood by those skilled in the art The scope of the invention is defined by the appended claims and their equivalents.

Claims

claims

1. A cloud push method, characterized by including the following steps:

Receive the usage time and/or usage scenarios of the mobile terminal recorded by the user using the mobile terminal and the attribute tags of the mobile terminal;

Calculate the preferred push time for the user based on the usage time and/or usage scenario; obtain the push content to be pushed to the user based on the attribute tag, and push the push content to the user within the preferred push time the mobile terminal.

2. The cloud push method according to claim 1, characterized in that the attribute mark of the mobile terminal includes the physical identification of the mobile terminal and/or the identity information of the user.

3. The cloud push method according to claim 1 or 2, characterized in that the usage scenario includes location information of the mobile terminal, gesture information of the user when using the mobile terminal, usage of the mobile terminal by the user. One or more of the motion information when the mobile terminal is moved and the light intensity information of the environment in which the mobile terminal is located.

4. The method of cloud push according to any one of claims 1 to 3, characterized in that, calculating the preferred push time for the user based on the usage time and/or usage scenario specifically includes: based on the optimization time The slice algorithm calculates the preferred push time for the user based on the usage time and/or usage scenario.

5. The cloud push method according to claim 4, characterized in that the optimization time slice algorithm includes the following steps:

Obtain the usage time of the user using the mobile terminal every day, and mark and sort the usage time;

Calculate the length of each said use;

Calculate the weight value of each usage time based on the time length/or usage scenario.

6. The cloud push method according to claim 5, further comprising: obtaining the user's call records;

If during the usage time, the ratio of the user's call time to the usage time is greater than the preset value, then the weight value corresponding to the usage time is set to zero.

7. The cloud push method according to claim 5 or 6, further comprising: summarizing the weight values of the user's usage time in N days to calculate the preferred push time for the user , where N is an integer greater than 1.

8. A cloud push device, characterized by including:

A receiving module, configured to receive the usage time and/or usage scenarios of the user using the mobile terminal recorded by the mobile terminal and the attribute tags of the mobile terminal;

A calculation module, configured to calculate the preferred push time for the user based on the usage time and/or usage scenario;

a push module, configured to obtain push content pushed to the user according to the attribute tag, and

9. The cloud push device according to claim 8, wherein the attribute mark of the mobile terminal includes the physical identification of the mobile terminal and/or the identity information of the user.

10. The cloud push device according to claim 8 or 9, wherein the usage scenario includes location information of the mobile terminal, gesture information of the user when using the mobile terminal, usage information of the user One or more of the motion information when the mobile terminal is moved and the light intensity information of the environment in which the mobile terminal is located.

11. The cloud push device according to any one of claims 8 to 10, characterized in that the calculation module calculates the preference for the user according to the usage time and/or usage scenario according to the optimization time slice algorithm. Push time.

12. The cloud push device according to claim 11, wherein the computing module obtains the usage time of the mobile terminal used by the user every day, and marks and sorts the usage time, and Calculate the time length of each usage time, and calculate the weight value of each usage time based on the time length/or usage scenario.

13. The cloud push device according to claim 12, wherein the computing module is also used to obtain the user's call record, and if during the usage time, the user's call time The ratio of time to the usage time is greater than the preset value, then the weight value corresponding to the usage time is set to

14. The cloud push device according to claim 12 or 13, wherein the calculation module summarizes the weight values of the user's usage time in N days to calculate the preferred push for the user. time, where N is an integer greater than 1.

15. A cloud push method, characterized by including the following steps:

Collect the usage time and/or usage scenarios of users using mobile terminals;

Send the usage time and/or usage scenario and the attribute tag of the mobile terminal to the cloud server, so that the cloud server calculates the preferred push time for the user based on the usage time and/or usage scenario and the The attribute tag obtains the push content; the push content is described.

16. The cloud push method according to claim 15, characterized in that the attribute mark of the mobile terminal includes the physical identification of the mobile terminal and/or the identity information of the user.

17. The cloud push method according to claim 15, wherein the usage scenario includes location information of the mobile terminal, gesture information of the user when using the mobile terminal, usage of the mobile terminal by the user. One or more of motion information when moving the terminal and light intensity information of the environment in which the mobile terminal is located.

18. A mobile terminal, characterized in that it includes:

Collection module, used to collect users’ usage time and/or usage scenarios;

A sending module, configured to send the usage time and/or usage scenario and the attribute tag of the mobile terminal to the cloud server, so that the cloud server calculates the preferred push for the user based on the usage time and/or usage scenario. The time and push content are obtained according to the attribute tag; the push content pushed by the terminal.

19. The mobile terminal according to claim 18, characterized in that the attribute of the mobile terminal is: The gender mark includes the physical identification of the mobile terminal and/or the identity information of the user.

20. The mobile terminal of claim 18, wherein the usage scenario includes location information of the mobile terminal, gesture information of the user when using the mobile terminal, One or more of the movement information at the time and the light intensity information of the environment where the mobile terminal is located.

21. A cloud push system, characterized by comprising the cloud server described in any one of claims 8-14 and the mobile terminal described in any one of claims 18-20.