WO2014036854A1 - Procédé, système et dispositif de distribution automatique dans le nuage - Google Patents

Procédé, système et dispositif de distribution automatique dans le nuage Download PDF

Info

Publication number
WO2014036854A1
WO2014036854A1 PCT/CN2013/078872 CN2013078872W WO2014036854A1 WO 2014036854 A1 WO2014036854 A1 WO 2014036854A1 CN 2013078872 W CN2013078872 W CN 2013078872W WO 2014036854 A1 WO2014036854 A1 WO 2014036854A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
mobile terminal
time
push
usage
Prior art date
Application number
PCT/CN2013/078872
Other languages
English (en)
Chinese (zh)
Inventor
巫国忠
唐虹刚
Original Assignee
百度在线网络技术（北京）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 百度在线网络技术（北京）有限公司 filed Critical 百度在线网络技术（北京）有限公司
Publication of WO2014036854A1 publication Critical patent/WO2014036854A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • 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
  • 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.
  • Personalized push services generally focus on content personalization, collecting information and preferences of users in mobile terminals.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 .
  • 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.
  • FIG. 1 is a flowchart of a method for cloud push according to an embodiment of the present invention
  • FIGS. 2 and 3 are schematic diagrams showing a state of use of a user according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 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. 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.
  • 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.
  • 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:
  • the device unique attribute tag (a) The device unique attribute tag (UID) consists of two parts:
  • the physical standard of the mobile terminal is only : 3 ⁇ 4.
  • the IMEI International Mobile Equipment Identity number
  • IMSI International Mobile Subscriber Identification Number
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the cloud server After receiving the data uploaded by the mobile terminal, 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.
  • 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.
  • 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.
  • 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.
  • UID unique attribute tag
  • TimeRecord contains the fields defined in Table 2:
  • 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 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 light is generally bright, and the corresponding weight value is increased, which is brighter, and the corresponding weight value is lowered.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the cloud push method 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.
  • the present invention also proposes a cloud push device.
  • the cloud push device includes: a receiving module 11, a calculating module 12, and a pushing module 13.
  • 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.
  • 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:
  • the device unique attribute tag (a) The device unique attribute tag (UID) consists of two parts:
  • 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.
  • 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.
  • 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)”,
  • 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.
  • 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.
  • the direction sensor is used to determine the position of the user, for example, whether the user is standing or lying.
  • 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.
  • 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.
  • 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.
  • fixed 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 is the weight value of time.
  • 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.
  • TimeRecord contains the fields defined in Table 2.
  • 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 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.
  • 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.
  • the light is generally bright, and the corresponding weight value is increased, which is brighter, and the corresponding weight value is lowered.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • information is collected and the information parameters defining the user's use of the mobile terminal are as follows:
  • the device unique attribute tag (a) The device unique attribute tag (UID) consists of two parts:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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 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.
  • 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.
  • 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.
  • fixed 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.
  • 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.
  • 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.
  • 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.
  • the cloud server After receiving the data uploaded by the mobile terminal, 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.
  • 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.
  • the present invention also proposes a mobile terminal.
  • the mobile terminal includes: an acquisition module 21, a transmitting module 22, and a receiving module 23.
  • 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.
  • 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.
  • the information parameters specifically collected and defined by the user using the mobile terminal are as follows:
  • the device unique attribute tag (a) The device unique attribute tag (UID) consists of two parts:
  • 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.
  • 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.
  • 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.
  • 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)”,
  • 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.
  • 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.
  • the direction sensor is used to determine the position of the user, for example, whether the user is standing or lying.
  • 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 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.
  • 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.
  • "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.
  • 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.
  • 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.
  • the collection of each piece of information of the acquisition module 21 can be represented as one line of record.
  • 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 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 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.
  • 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.
  • the schematic representation of the above terms does not necessarily mean the same embodiment or example.
  • the particular features, structures, materials, or characteristics described may be combined in a suitable manner in any one or more embodiments or examples.
  • the term “plurality” means two or more.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

La présente invention concerne un procédé de distribution automatique dans le nuage, comprenant les étapes suivantes consistant à : recevoir un temps d'utilisation et/ou un scénario d'utilisation pour un utilisateur utilisant un terminal mobile enregistré par le terminal mobile et un signe de propriété du terminal mobile ; calculer un temps de distribution automatique préférable pour l'utilisateur en fonction du temps d'utilisation et/ou du scénario d'utilisation ; obtenir un contenu de distribution automatique distribué automatiquement à l'utilisateur en fonction du signe de propriété, et distribuer le contenu de distribution automatique au terminal mobile dans le temps de distribution automatique préférable. Selon la présente invention, le temps et le scénario pour l'utilisateur utilisant le terminal mobile sont analysés afin de fournir un service personnalisé individuel à l'utilisateur, et distribuer automatiquement des informations à l'utilisateur en temps et lieu opportuns, de sorte que la possibilité de cliquer sur les informations est améliorée, et l'expérience utilisateur est améliorée. La présente invention concerne en outre un dispositif de distribution automatique dans le nuage, un autre procédé de distribution automatique dans le nuage, un terminal mobile et un système de distribution automatique dans le nuage.
PCT/CN2013/078872 2012-09-06 2013-07-05 Procédé, système et dispositif de distribution automatique dans le nuage WO2014036854A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210328616.2 2012-09-06
CN201210328616.2A CN102882936B (zh) 2012-09-06 2012-09-06 云推送的方法、系统和装置

Publications (1)

Publication Number Publication Date
WO2014036854A1 true WO2014036854A1 (fr) 2014-03-13

Family

ID=47484078

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/078872 WO2014036854A1 (fr) 2012-09-06 2013-07-05 Procédé, système et dispositif de distribution automatique dans le nuage

Country Status (2)

Country Link
CN (1) CN102882936B (fr)
WO (1) WO2014036854A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105282014A (zh) * 2015-11-17 2016-01-27 中国建设银行股份有限公司 一种信息推送方法和装置
CN108259588A (zh) * 2018-01-09 2018-07-06 上海创图网络科技股份有限公司 一种基于大数据的文化云平台的推送方法及装置
WO2019019891A1 (fr) * 2017-07-28 2019-01-31 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé, terminal mobile, et support de stockage non transitoire lisible par ordinateur, utilisés pour ajuster la fréquence de balayage d'un écran tactile
US10764379B2 (en) 2013-09-06 2020-09-01 Nokia Technologies Oy Method, apparatus and system for enhancing a user's engagement with a service

Families Citing this family (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102882936B (zh) * 2012-09-06 2015-11-25 百度在线网络技术（北京）有限公司 云推送的方法、系统和装置
CN104052714B (zh) * 2013-03-12 2019-02-26 腾讯科技（深圳）有限公司 多媒体信息的推送方法及服务器
CN104168174A (zh) * 2013-05-16 2014-11-26 阿里巴巴集团控股有限公司 一种传输信息的方法及装置
TWI533265B (zh) * 2013-11-11 2016-05-11 Chunghwa Telecom Co Ltd Method of presenting a recommendation message on a map
US10467641B2 (en) 2013-12-20 2019-11-05 Ncr Corporation Mobile proximity-based analytics
CN104750464B (zh) * 2013-12-25 2019-09-10 中国移动通信集团公司 一种用户状态感知、管理方法及设备
CN104754112A (zh) * 2013-12-31 2015-07-01 中兴通讯股份有限公司 用户信息获取方法及移动终端
JP2015162162A (ja) * 2014-02-28 2015-09-07 東芝テック株式会社 情報配信装置、情報配信プログラム
CN104980327B (zh) * 2014-04-03 2019-05-03 腾讯科技（深圳）有限公司 一种消息推送方法及装置
CN104065565B (zh) * 2014-06-12 2017-04-05 北京奇虎科技有限公司 推送消息的方法、服务器、客户端装置和系统
CN104063457A (zh) * 2014-06-25 2014-09-24 北京智谷睿拓技术服务有限公司 信息通信方法和系统及终端
CN104063462A (zh) * 2014-06-25 2014-09-24 北京智谷睿拓技术服务有限公司 信息通信方法、装置和系统
CN104065729B (zh) * 2014-06-27 2017-12-05 广州猎豹网络科技有限公司 信息推送方法及装置
CN104980480B (zh) * 2014-09-15 2018-09-07 腾讯科技（北京）有限公司 数据信息分享方法及装置
DE112015004331B4 (de) 2014-09-23 2024-10-10 Google LLC (n.d.Ges.d. Staates Delaware) Benachrichtigen von Nutzern über relevante Inhalte
CN104363302A (zh) * 2014-11-27 2015-02-18 北京奇艺世纪科技有限公司 一种离线下载文件的方法及装置
CN105791352B (zh) * 2014-12-24 2020-05-29 深圳市腾讯计算机系统有限公司 应用的消息推送方法和系统
CN104836724B (zh) * 2015-03-31 2018-02-09 北京奇艺世纪科技有限公司 内容更新提醒方法及装置
CN106156462A (zh) * 2015-04-01 2016-11-23 时云医疗科技（上海）有限公司 一种基于体征数据的行为信息推送方法及系统
CN104852842A (zh) * 2015-04-29 2015-08-19 小米科技有限责任公司 信息播报的方法及装置
CN104994062B (zh) * 2015-05-18 2019-04-30 百度在线网络技术（北京）有限公司 一种信息推送方法及装置
CN104793980B (zh) * 2015-05-19 2019-01-25 北京奇虎科技有限公司 应用程序更新通知方法及其装置
CN106294410A (zh) * 2015-05-22 2017-01-04 苏宁云商集团股份有限公司 一种个性化信息推送时间的确定方法及确定系统
CN105099870B (zh) * 2015-05-28 2019-02-15 努比亚技术有限公司 一种消息推送方法及装置
CN106257886B (zh) 2015-06-17 2020-06-23 腾讯科技（深圳）有限公司 一种信息处理方法、装置、终端及服务器
CN105095465B (zh) * 2015-07-31 2020-08-07 北京金山安全软件有限公司 一种信息推荐方法、系统及装置
CN106407239A (zh) * 2015-08-03 2017-02-15 阿里巴巴集团控股有限公司 用于推荐及辅助推荐信息的方法及装置
CN105653580A (zh) * 2015-12-18 2016-06-08 北京奇虎科技有限公司 特征信息确定、判定方法及装置以及其应用方法和系统
CN105610929A (zh) * 2015-12-24 2016-05-25 北京奇虎科技有限公司 一种个性化的数据推送方法和装置
JP6653774B2 (ja) * 2016-06-23 2020-02-26 コーニンクレッカ フィリップス エヌ ヴェＫｏｎｉｎｋｌｉｊｋｅ Ｐｈｉｌｉｐｓ Ｎ．Ｖ． 通知に対するユーザ可用性又は受容性を測定する方法、装置及び機械可読媒体
CN106096059A (zh) * 2016-07-11 2016-11-09 上海亿保健康管理有限公司 一种基于场景推送信息的方法
CN106557292A (zh) * 2016-11-11 2017-04-05 珠海市魅族科技有限公司 信息显示方法及装置
CN108093121B (zh) * 2016-11-23 2020-09-11 阿里巴巴集团控股有限公司 一种终端设备的提醒控制方法、装置以及电子设备
CN106487664B (zh) * 2016-12-08 2020-07-03 宇龙计算机通信科技(深圳)有限公司 一种信息推荐的方法、装置及移动终端
CN108199948A (zh) * 2016-12-08 2018-06-22 北京京东尚科信息技术有限公司 消息推送方法及装置
CN106779844B (zh) * 2016-12-15 2020-12-29 北京金山安全软件有限公司 一种获取增值业务信息的方法、装置及电子设备
CN106815361A (zh) * 2017-01-24 2017-06-09 维沃移动通信有限公司 一种浏览器页面显示方法及移动终端
CN108123999A (zh) * 2017-11-28 2018-06-05 维沃移动通信有限公司 一种消息推送方法及移动终端
CN108234290A (zh) * 2017-12-26 2018-06-29 珠海市魅族科技有限公司 消息推送方法及装置、计算机装置和计算机可读存储介质
CN109978575B (zh) * 2017-12-27 2021-06-04 中国移动通信集团广东有限公司 一种挖掘用户流量经营场景的方法及装置
CN108769157B (zh) * 2018-05-16 2021-03-19 北京奇虎科技有限公司 消息弹窗的展示方法、装置、计算设备及计算机存储介质
CN109118069A (zh) * 2018-07-27 2019-01-01 重庆工程职业技术学院 一种工程进度及造价管理系统的管理方法
CN109598576A (zh) * 2018-10-25 2019-04-09 阿里巴巴集团控股有限公司 服务推荐方法、装置及设备
CN109714399A (zh) * 2018-12-11 2019-05-03 浙江口碑网络技术有限公司 通知消息的推送方法及装置、存储介质、电子装置
WO2020252639A1 (fr) * 2019-06-17 2020-12-24 深圳市欢太科技有限公司 Procédé de poussée de contenu et produit associé
CN110493306A (zh) * 2019-07-05 2019-11-22 口碑(上海)信息技术有限公司 信息推送方法及客户端、服务端、系统
CN110351371A (zh) * 2019-07-15 2019-10-18 星联云服科技有限公司 一种在云存储系统中进行数据推送的方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102300163A (zh) * 2011-09-22 2011-12-28 宇龙计算机通信科技(深圳)有限公司 信息推送方法、移动终端和系统
CN102486786A (zh) * 2010-12-02 2012-06-06 腾讯科技（深圳）有限公司 一种向移动终端投放信息的方法及信息投放装置
CN102546777A (zh) * 2011-12-27 2012-07-04 广东宇天科技有限公司 移动终端桌面信息推送系统及其方法
CN102882936A (zh) * 2012-09-06 2013-01-16 百度在线网络技术（北京）有限公司 云推送的方法、系统和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7817983B2 (en) * 2005-03-14 2010-10-19 Qualcomm Incorporated Method and apparatus for monitoring usage patterns of a wireless device
CN1972468B (zh) * 2006-10-26 2010-05-12 Ut斯达康通讯有限公司 一种信息推送装置和方法
CN101217569A (zh) * 2008-01-15 2008-07-09 杭州华三通信技术有限公司 一种页面的推送方法、系统和装置
CN101600167A (zh) * 2008-06-06 2009-12-09 瞬联软件科技（北京）有限公司 面向移动应用的信息自适应交互系统及其实现方法
CN101751448B (zh) * 2009-07-22 2012-06-27 中国科学院自动化研究所 一种基于情景信息的个性化资源信息的推荐方法
CN101620625B (zh) * 2009-07-30 2012-10-31 腾讯科技（深圳）有限公司 一种搜索关键词排序方法、装置和搜索引擎

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102486786A (zh) * 2010-12-02 2012-06-06 腾讯科技（深圳）有限公司 一种向移动终端投放信息的方法及信息投放装置
CN102300163A (zh) * 2011-09-22 2011-12-28 宇龙计算机通信科技(深圳)有限公司 信息推送方法、移动终端和系统
CN102546777A (zh) * 2011-12-27 2012-07-04 广东宇天科技有限公司 移动终端桌面信息推送系统及其方法
CN102882936A (zh) * 2012-09-06 2013-01-16 百度在线网络技术（北京）有限公司 云推送的方法、系统和装置

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10764379B2 (en) 2013-09-06 2020-09-01 Nokia Technologies Oy Method, apparatus and system for enhancing a user's engagement with a service
CN105282014A (zh) * 2015-11-17 2016-01-27 中国建设银行股份有限公司 一种信息推送方法和装置
WO2019019891A1 (fr) * 2017-07-28 2019-01-31 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé, terminal mobile, et support de stockage non transitoire lisible par ordinateur, utilisés pour ajuster la fréquence de balayage d'un écran tactile
US10761642B2 (en) 2017-07-28 2020-09-01 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method, mobile terminal and non-transitory computer-readable storage medium for adjusting scanning frequency of touch screen
CN108259588A (zh) * 2018-01-09 2018-07-06 上海创图网络科技股份有限公司 一种基于大数据的文化云平台的推送方法及装置

Also Published As

Publication number Publication date
CN102882936B (zh) 2015-11-25
CN102882936A (zh) 2013-01-16

Similar Documents

Publication Publication Date Title
WO2014036854A1 (fr) Procédé, système et dispositif de distribution automatique dans le nuage
TWI428564B (zh) 個人化距離之判定及顯示系統與方法
US20190158609A1 (en) System and method for improved mapping and routing
US11887164B2 (en) Personalized information from venues of interest
CN109376313B (zh) 信息推荐方法、装置、终端及存储介质
US20130304685A1 (en) Behaviour pattern analysis system, mobile terminal, behaviour pattern analysis method, and program
US10275530B2 (en) System and method for communal search
CN108960785B (zh) 一种信息提示方法及装置
US20200118191A1 (en) Apparatus and method for recommending place
EP3627806A1 (fr) Procédé de génération de portrait d'utilisateur, et terminal
US11595329B2 (en) Location based content system for mobile applications
WO2010039378A2 (fr) Système et procédé destinés à la création d'une publicité améliorée contextuelle
WO2013192591A2 (fr) Classement de destinations à proximité sur la base de probabilités de visite et prédiction de futures visites d'endroits dans un historique d'emplacements
Niforatos et al. Understanding the potential of human–machine crowdsourcing for weather data
US11436293B2 (en) Characterizing a place by features of a user visit
US20220078135A1 (en) Signal upload optimization
JP6396686B2 (ja) 行動判定装置、行動判定方法及びプログラム
JP6378994B2 (ja) 配信装置及び配信方法
EP3036929B1 (fr) Système et procédé de communication d'informations dans un système basé sur la localisation
JP6698720B2 (ja) 通信制御プログラム、通信制御装置、通信制御方法、管理サーバ、管理方法及び管理プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13836058

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13836058

Country of ref document: EP

Kind code of ref document: A1