CN107528717B - Event processing method and device - Google Patents

Event processing method and device Download PDF

Info

Publication number
CN107528717B
CN107528717B CN201610597138.3A CN201610597138A CN107528717B CN 107528717 B CN107528717 B CN 107528717B CN 201610597138 A CN201610597138 A CN 201610597138A CN 107528717 B CN107528717 B CN 107528717B
Authority
CN
China
Prior art keywords
application
event
resource
preemption
event time
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201610597138.3A
Other languages
Chinese (zh)
Other versions
CN107528717A (en
Inventor
李飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201610597138.3A priority Critical patent/CN107528717B/en
Publication of CN107528717A publication Critical patent/CN107528717A/en
Application granted granted Critical
Publication of CN107528717B publication Critical patent/CN107528717B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/146Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0896Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/54Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services

Abstract

The invention discloses an event processing method and device. The event processing method comprises the following steps: receiving indication information for indicating an event time point from a server; recording an event time point indicated by the indication information in the first application; when the event time point is reached, displaying a reminding message in the first application, wherein the reminding message is used for indicating that the target event is being executed, the reminding message comprises a preemption identification, and the preemption identification is used for preempting the target event resource of the target event; judging whether touch operation executed on the preemption identification is detected; and under the condition that the touch operation is detected, responding to the touch operation to indicate that the target event resource is preempted in the first application, and displaying a preemption result of the target event resource in the first application. The invention solves the technical problem of increasing the flow consumption caused by continuously monitoring whether the target event is executed in each application in the related art.

Description

Event processing method and device
Technical Field
The invention relates to the field of event processing, in particular to an event processing method and device.
Background
With the popularization of intelligent terminals, applications are increasing, many applications have a function of target event execution, and since a plurality of applications have a function of target event execution, if a user wants to seize a target event resource at a time point when a target event is executed, the user needs to enter a plurality of applications continuously to monitor whether the target event is executed, and the operation method of continuously monitoring whether the target event is executed wastes traffic.
For example, more and more users gradually develop the habit of using social software, and a red envelope are also a new social mode, the red envelope can be preempted in a variety of applications, such as instant messaging applications like WeChat, QQ, etc., especially in groups of instant messaging applications, there may be a plurality of group-sending red packets, and if the user does not want to miss the message that needs to check each group in real time, the traffic consumption is caused, therefore, some red packet assistants have appeared to help users get a red packet, for example, millet red packet alarm clocks and charm red packet assistants, however, the millet and charm red packet assistants monitor red packet events of a plurality of instant messaging applications all the time, and then help users seize the events through own red packet grabbing modules, and popping up a floating window to remind a user when a red packet event is monitored, and the user can enter an application with a red packet to take the red packet by clicking the floating window.
However, in the product dimension, after the red envelope is reminded, the user needs to enter the corresponding application inner red envelope, and the user does not get the red envelope more conveniently. From the technical dimension, the red packet events of multiple applications are monitored continuously, so that traffic loss and power consumption are increased, potential safety hazards are easily caused by monitoring external red packet events, and property loss is caused by malicious use.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the invention provides an event processing method and device, which are used for at least solving the technical problem that the related art continuously monitors whether a target event is executed or not so as to increase the flow consumption.
According to an aspect of an embodiment of the present invention, there is provided an event processing method, including: receiving indication information for indicating an event time point from a server; recording the event time point indicated by the indication information in a first application, wherein the event time point is used for indicating the time point of the target event to be executed in a second application; when the event time point is reached, displaying a reminding message in the first application, wherein the reminding message is used for indicating that the target event is executed, the reminding message comprises a preemption identification, and the preemption identification is used for preempting a target event resource of the target event; judging whether touch operation executed on the preemption identification is detected; and under the condition that the touch operation is detected, responding to the touch operation to indicate to preempt the target event resource in the first application, and displaying a preemption result of the target event resource in the first application.
According to another aspect of the embodiments of the present invention, there is also provided an event processing apparatus, including: a receiving unit for receiving indication information indicating an event time point from a server; a recording unit, configured to record the event time point indicated by the indication information in a first application, where the event time point is used to indicate a time point at which a target event to be executed is executed in a second application; a display unit, configured to display a reminding message in the first application when the event time point is reached, where the reminding message is used to indicate that the target event is executing, the reminding message includes a preemption identifier, and the preemption identifier is used to preempt a target event resource of the target event; a judging unit, configured to judge whether a touch operation performed on the preemption identifier is detected; and an indicating unit, configured to, in a case that the touch operation is detected, indicate, in response to the touch operation, that the target event resource is to be preempted in the first application, and display, in the first application, a preemption result for preempting the target event resource.
In the embodiment of the present invention, by receiving indication information indicating a time point from the server, then recording in the first application a point in time indicating that the target event was executed in the second application, displaying a reminding message after reaching the corresponding time point, reminding that the target event is executing, displaying a preemption identification reminding the user to preempt the target event resource, when detecting the touch operation of the preemption identification, the target event resource is preempted in the first application, so that the aim of preempting the target event resource in the second application in the first application is fulfilled, thereby realizing the technical effect of monitoring and preempting the target event of the second application in the first application so as to reduce the traffic consumption, and the technical problem that the related art increases the traffic consumption by continuously monitoring whether the target event is executed in each application is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a schematic diagram of a hardware environment for an event processing method according to an embodiment of the present invention;
FIG. 2 is a flow diagram of an alternative event processing method according to an embodiment of the invention;
FIG. 3 is a flow diagram of an alternative event processing method according to an embodiment of the invention;
FIG. 4 is a flow diagram of an alternative event processing method according to an embodiment of the invention;
FIG. 5 is a schematic diagram of an alternative red packet alarm entry page according to an embodiment of the invention;
FIG. 6 is a schematic diagram of an enterprise red envelope reminder interface, according to an embodiment of the invention;
FIG. 7 is a schematic diagram of a friend red envelope reminder interface, according to an embodiment of the invention;
FIG. 8 is a schematic diagram of a red packet alarm clock province flow core module according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of an alternative event processing device according to an embodiment of the present invention; and
fig. 10 is a block diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
According to an embodiment of the present invention, an embodiment of an event processing method is provided.
Alternatively, in the present embodiment, the event processing method described above may be applied to a hardware environment formed by the server 102 and the terminal 104 as shown in fig. 1. As shown in fig. 1, a server 102 is connected to a terminal 104 via a network including, but not limited to: the terminal 104 is not limited to a PC, a mobile phone, a tablet computer, etc. in a wide area network, a metropolitan area network, or a local area network. The event processing method according to the embodiment of the present invention may be executed by the server 102, the terminal 104, or both the server 102 and the terminal 104. The event processing method of the embodiment of the present invention executed by the terminal 104 may also be executed by a client installed thereon.
The event processing method of the embodiment of the invention mainly comprises the following processes that a first application and a second application are applied to the same terminal 104, the first application is an application for preempting event resources, the second application can be an instant messaging application, wherein the first application uses a first account number to log in, the first application receives a time point of a target event executed in the second application from a server 102, after a touch operation executed on a preemption identifier is detected in the first application, the second account number in the second application is indicated in the first application to preempt the target event resources, and the account number corresponding to the first account number in the second application is the second account number; the first account and the second account can be the same account or related accounts, and the first application sends out a prompt at an event time point to prompt a user to seize event resources in the second application. And displaying resource indication information in the first application, wherein the resource indication information is used for indicating a preemption result of a third account and a second account in the second application for preempting the target event resource, and the third account and the second account have an association relationship in the second application.
Fig. 2 is a flowchart of an alternative event processing method according to an embodiment of the present invention, and as shown in fig. 2, the method may include the following steps:
in step S202, indication information indicating an event time point is received from the server.
The event time point may be multiple types of events, for example, a resource preemption event, the indication information is used to indicate a time point when the event occurs, the indication information carries the event time point, the indication information used to indicate the event time point is received from the server, or the indication information used to indicate the event time point is received from the server by the application, for example, the application receives the indication information used to indicate the event time point from the server through the wireless network.
Step S204, recording the event time point indicated by the indication information in the first application.
The first application may be an application installed on the mobile terminal, for example, a first application installed on a mobile phone, a tablet computer, or the like. The second application is not the same application as the first application, and the event time point is used for indicating the time point when the target event to be executed is executed in the second application. The target event may be multiple types of events, and in general, the target event needs to be preempted, where the event time point is a time point set in the first application, and the event time point represents a time point at which the target event in the second application will be executed, and the event time point indicated by the recording indication information in the first application may be one time point recorded in the first application, or may be multiple time points recorded in the first application, and the event time points are stored in the first application, and optionally, one or more recorded event time points are displayed in the first application, and further, one or more events corresponding to the event time points may also be displayed. The number of event time points in the first application may be one or more, and the plurality of event time points may represent event time points in a plurality of second applications or may represent a plurality of event time points in one second application.
Step S206, when the event time point is reached, a reminding message is displayed in the first application.
The method comprises the steps that after an event time point is set in a first application, the first application monitors the event time point, and when the event time point is reached, a reminding message is displayed in the first application, wherein the reminding message is used for indicating that a target event is executed, the reminding message comprises a preemption identification, and the preemption identification is used for preempting a target event resource of the target event.
Since the target event needs to be preempted, in the second application, multiple account numbers may preempt the same target event, so that when the event time point is reached, a reminding message is displayed in the first application to remind a user to preempt the target event resource, the reminding message includes a preemption identification, the preemption identification can be displayed on a terminal, and the preemption identification can be multiple types of identifications, for example, a circular pattern, or an identification corresponding to the target event in the second application can be adopted to distinguish different target events from different applications. Optionally, the reminder message may include other reminding manners besides the preemption identification, such as ringing or vibrating other reminding information. Taking a mobile phone as an example, the reminding message in the first application can wake up the mobile phone when the mobile phone is dormant and locked and display the reminding message on the screen of the mobile phone when the mobile phone is bright.
Step S208 is to determine whether a touch operation performed on the preemption identification is detected.
After the prompt message is displayed in the first application, it is determined whether the touch operation performed on the preemption identifier is detected, for example, after the preemption identifier is displayed in the first application, the user sees the preemption identifier displayed in the first application, clicks the preemption identifier, and the first application or the terminal detects whether the touch operation performed on the preemption identifier is detected. The touch operation performed on the preemption identifier may be a touch operation input by a user manually clicking a mobile phone screen, or a touch operation input through other input devices, for example, a touch operation input through a mouse, or a gesture touch operation input through a gesture recognition device.
Step S210, in a case that the touch operation is detected, indicating to preempt the target event resource in the first application in response to the touch operation, and displaying a preemption result of the target event resource in the first application.
After the touch operation executed on the preemption identification is detected, indicating to preempt the target event resource in the first application in response to the touch operation, and displaying a preemption result of the target event resource in the first application. After the touch operation of the preemption identification is detected in the first application, the target event resource is instructed to be preempted in the first application, and after the preemption is completed, the preemption result of the target event resource is still displayed in the first application, for example, the target event resource is not preempted or the number of the preempted target event resource is. Optionally, the preemption result may also display the preemption result of the target event resource in which application is specifically displayed.
The event processing method of this embodiment may also be used as an event resource preemption method, and performs preprocessing before preemption of event resources, so as to make preemption of event resources more convenient, and since a time point at which a target event in the second application is executed is monitored in the first application, preemption of the target event resources is instructed when the time point is reached, and a preemption result is displayed, preemption of the target event resources can be instructed in the first application without jumping to the second application, and since an event time point is preset, it is not necessary to continuously scan the second application to obtain the time point at which the target event is executed, so that network interaction times can be reduced, network traffic consumption is reduced to the greatest extent, and meanwhile, usage of a mobile phone memory can be reduced, and user experience is improved.
Through the above steps S202 to S210, by receiving the indication information for indicating the time point from the server, then recording in the first application a point in time indicating that the target event was executed in the second application, displaying a reminding message after reaching the corresponding time point, reminding that the target event is executing, displaying a preemption identification reminding the user to preempt the target event resource, when detecting the touch operation of the preemption identification, the target event resource is preempted in the first application, so that the aim of preempting the target event resource in the second application in the first application is fulfilled, thereby realizing the technical effect of monitoring and preempting the target event of the second application in the first application so as to reduce the traffic consumption, and the technical problem that the related art increases the traffic consumption by continuously monitoring whether the target event is executed in each application is solved.
As an alternative embodiment, the indication information is used to indicate a plurality of event time points, and recording the event time points indicated by the indication information in the first application may be performed by: the method comprises the steps of recording an event time sequence in a first application, wherein the event time sequence comprises a plurality of event time points arranged in a time sequence, and each event time point is used for indicating the time point when a target event to be executed is executed in a second application.
In this embodiment, the first application may be a "red envelope housekeeper" and the event may be a robbery red envelope event, where red envelope refers to a traditional physical red envelope virtualized by internet means to be transmitted between social platforms such as friends of an instant messaging application, commonly referred to as internet red envelope. The first application receives indication information from the server, wherein the indication information is used for indicating a plurality of event time points, the event can be a plurality of events, the events all have time points, the time points of the events are stored in the server, for example, the first application can be obtained from the server, or the indication information pushed by the server can be received, in some applications, for example, instant messaging applications, there are enterprise or star red packet events at times, the events all have event times, the event times are stored in the server, the first application can receive the indication information of the corresponding event time points from the server, then set an event time sequence according to the indication information of the event time points, that is, the event time points are arranged according to the time sequence, for example, the resource is issued in 18:00 mindset in 2 months and 11 months in the first instant messaging application, and (3) a company 19:00 in No. 2/12 sends event resources to a second instant messaging application, a first application sets an event time sequence after acquiring corresponding event time points, and the time points occupied by a plurality of event resources to be generated are displayed on an interface of the first application.
Taking the first application as a red packet steward as an example, displaying a red packet robbing time sequence of a plurality of applications in the red packet steward, for example, red packet robbing times of different instant messaging applications, and the like, when the corresponding time is reached, displaying a reminding message in the red packet steward to remind that a red packet robbing event is in progress, displaying a red packet robbing identifier in an interface of the red packet steward, when a user clicks the preemption identifier, not jumping to the corresponding instant messaging application, but indicating an instant messaging application red packet in the red packet steward, after the red packet is robbed, sending a red packet robbing result to the red packet steward by the corresponding instant messaging application, displaying the red packet result in the red packet steward, and not switching to the corresponding instant messaging application to check the red packet result.
As an alternative embodiment, the time sequence of events is updated after it is recorded in the first application. For example, the time for issuing the red packet in the first instant messaging application in the morning of the mindset is adjusted from 18:00 at month No. 2 to 19:00 at month No. 2 to 11: 00 at month No. 2, so that the first application updates the event time sequence at every preset time, and during the updating, the whole updating mode can be adopted, or only the changed part can be updated, for example, only the changed parts such as the red packet sender, the red packet sending time, the red packet amount and the like are updated, or the indication information of all event time points can be obtained from the server again, and then the event time sequence is set according to the indication information of a plurality of event time points. The accuracy of the event processing method can be improved by updating the event time sequence, and the red packet robbing time sequence is updated by taking the red packet robbing as an example, so that the accuracy of the red packet robbing can be improved, and the efficiency and the success rate are improved.
As an alternative embodiment, updating the time series of events includes any one of: firstly, when a terminal where a first application is located is connected to a wireless network, updating an event time sequence; secondly, updating the event time sequence when the terminal where the first application is located is in an idle state; and thirdly, updating the event time sequence when the terminal where the first application is located is connected to the wireless network and is in an idle state.
As an alternative embodiment, the wireless network may be a wireless local area network, such as a WIFI network, or may also be a mobile communication network, such as a 2G, 3G, or 4G mobile network. The event time sequence is updated only when the terminal where the first application is located is connected to a wireless network, taking a mobile phone terminal as an example, the event time sequence can be updated only when the mobile phone is connected to the wireless network, and if the mobile phone is not connected to the wireless network, the event time sequence is not updated, so that the memory consumption of the mobile phone is saved. When the terminal transitions from an unconnected state to a state of connecting to the wireless network, the first application detects that the terminal is connected to the wireless network and updates the time sequence of events. Optionally, the first application updates the event time sequence when detecting that the terminal is connected to the WIFI wireless network, so that the usage of the mobile network traffic can be reduced to the greatest extent, and the traffic is saved for the user.
As another alternative embodiment, the terminal where the first application is located is in an idle state, and updates the event time sequence, where the idle state of the terminal may be a state in which the CPU occupancy of the terminal is lower than a preset value, for example, when the CPU occupancy of the terminal is lower than 50%, the terminal is in the idle state, or when the terminal is not in a state of playing video, audio, video, or taking pictures, the terminal is in the idle state. The event time sequence is updated when the terminal is in an idle state, so that the CPU occupation of the terminal can be reduced, and the running speed of the terminal is improved.
As another optional embodiment, when the terminal where the first application is located is connected to the wireless network and is in an idle state, the event time sequence is updated, and this scheme can reduce the usage of the mobile network traffic, save traffic for the user, and reduce the CPU occupation of the terminal.
The updating of the event time sequence may be performed according to a setting of a user, for example, the user may set that the event time sequence is updated when the terminal where the first application is located is connected to the wireless network, or the event time sequence is updated when the terminal where the first application is located is set in an idle state when the terminal where the first application is located is connected to the wireless network. This embodiment saves the traffic consumption and power consumption caused by monitoring multiple second applications in real time by the first application updating the event time sequence at the appropriate time.
As an alternative embodiment, the preempting the target event resource in the first application in response to the touch operation may be: indicating a second application to seize a target event resource in the first application; and receiving a preemption result sent by a second application in the first application, wherein the preempted event resources indicated by the preemption result in the target event resources are transferred to a preset resource account, and the preset resource account and a preset login account of the second application have a binding relationship, or the preempted event resources are transferred to the preset login account of the second application.
The step of instructing, in response to the touch operation, to preempt the target event in the first application may be that the first application instructs, after detecting that the touch identifier of the red packet is touched, the corresponding instant messaging application to preempt the red packet, and then the instant messaging application sends the red packet preempting result to the first application, and the first application receives the red packet preempting result. And then transferring the amount of the robbed red packet to a preset login account or a preset resource account of the corresponding instant messaging application. Optionally, in this embodiment, before the red envelope is dug, the corresponding red envelope application needs to be logged in by using a preset account. The preset resource account number can be a preset resource account number such as a bank card or a credit card, the preset resource account number can be bound with a login account number of the instant messaging application, and after the instant messaging application seizes resources, the seized resources are transferred to the preset resource account number.
Fig. 3 is a flowchart of another alternative event processing method according to an embodiment of the present invention, which may be used as a preferred embodiment of the foregoing embodiment, and as shown in fig. 3, the method may include the following steps:
and step S301, starting to use a red packet alarm clock.
The first application can be a red packet alarm clock application, the red packet alarm clock can be set to be used or not used at the terminal, and in the embodiment of the invention, the red packet alarm clock is required to be set to be used.
Step S302, networking and pre-downloading red packet time sequence.
When the terminal where the red packet alarm clock is located is networked, the red packet event time sequence is downloaded, wherein the red packet event time sequence can be downloaded, then the red packet event time points are arranged according to the time sequence to obtain the red packet time sequence, and optionally, the red packet time sequence is stored in the first application or the terminal where the first application is located.
Step S303, determine whether the set red packet event time point is reached.
It is determined whether the set red packet event time point is reached, and if the set red packet event time point is reached, step S304 is performed. The judgment of whether the set red packet event time point is reached can be carried out based on the time of the server, and can also be carried out based on the terminal where the first application is located.
And step S304, carrying out red packet reminding.
And if the set red packet event time point is reached, the first application sends a prompt to prompt the user that the red packet robbing operation can be performed currently. The reminding information can be sent out at a certain preset time in advance, for example, the user can be reminded to rush the red envelope 30 seconds in advance, or the reminding can be carried out only when the set red envelope event time point is reached without reminding in advance.
In step S305, the time series is updated uniformly when idle.
After the first application networking downloads the red packet event time sequence in advance, the time sequence is updated uniformly when the terminal is idle, the time sequence can be updated to obtain the changed time for robbing the red packet event in time, the newly-appeared red packet event robbing is prevented from being missed, and the accuracy of the red packet alarm clock is improved.
According to the embodiment, real-time monitoring behaviors of a plurality of applications are reduced by presetting the time sequence of the red packet events, the operation steps of a user for receiving the red packet are reduced by the aid of the front red packet receiving module, the mobile network traffic usage of the user for receiving the red packet is reduced by the aid of the preset time sequence of the red packet events, and finally the purpose of reducing traffic loss of the mobile network is achieved.
Fig. 4 is a flowchart of another alternative event processing method according to an embodiment of the present invention, which may be used as a preferred embodiment of the foregoing embodiment, and as shown in fig. 4, the method may include the following steps:
and step S401, starting to use the red packet alarm clock.
Step S402, judging whether the set time point of the red packet event is reached.
It is determined whether the current time reaches the set time point of the red packet event, and if the current time reaches the set time point of the red packet event, step S403 is performed. And if the set time point of the red packet event is not reached, continuously monitoring the current time and judging whether the set time point of the red packet event is reached.
And step S403, popping up a red packet reminding floating window.
If the current time reaches the time point of the set red packet event, a red packet reminding floating window pops up, wherein the red packet reminding floating window pops up by a red packet alarm clock application, can pop up on the desktop of the mobile terminal, can also pop up on a red packet alarm clock interface, and optionally can pop up when the mobile terminal executes other operations.
And step S404, the red envelope is successfully obtained.
After popping up the red packet reminding floating window, the user can click the red packet reminding floating window to get the red packet. The user can click the neglected floating window and does not get the red packet corresponding to the current prompt, at the moment, the red packet alarm clock continues to monitor other red packet events in the time sequence of the red packet events, and whether the current time point of the set red packet events is reached is judged.
The embodiment can be used as a flow chart for the user to get the red envelope, and as an optional implementation mode, the user can select whether to get the red envelope to remind the corresponding red envelope.
Fig. 5 is a schematic diagram of an optional red packet alarm clock entry page according to an embodiment of the present invention, and as shown in fig. 5, the first application may be a red packet alarm clock, a red packet reminder of an enterprise or a star may be displayed on the entry page of the red packet alarm clock, and may be arranged according to a time sequence, where the reminder includes an application of the red packet, a time for grabbing the red packet, and other information for grabbing the red packet, such as a total amount or number of the red packet. For example, in the enterprise and star red packet reminding time sequence, a red packet from a first instant messaging application is displayed, the time for grabbing the red packet is 18:00 at 11 days of 2 months, the red packet item is millions of red packets sent by plum morning of the star, the time for red packets from a second instant messaging application is 18:00 at 12 days of 2 months, hundreds of millions of red packets and gift certificate red packets are displayed, wherein a trigger for prompting the user to "upgrade" is displayed on the right side of the reminder, the user can click on the trigger to upgrade the application, a red packet from a third instant messaging application is displayed, the time is 19:00 at 12 days of 2 months, the red packet item is millions of red packets sent by star and katy, and finally a red packet from a fourth instant messaging application is displayed, the time is 20:00 at 12 days of 2 months, the red packet item is hundreds of millions of red packets and gift certificate red packets, a trigger for prompting the user to "download" is displayed on the right side, the user may click on the trigger to download the application.
And a reminding trigger for reminding the user to start the first instant messaging application and the second instant messaging application red packages is also displayed above the interface, the user can set friend red package reminding from the first instant messaging application and the second instant messaging application by clicking the trigger, and reminding information can be received in time when the friends of the instant messaging applications send the red packages.
Fig. 6 is a schematic diagram of an enterprise red envelope reminding interface according to an embodiment of the present invention, as shown in fig. 6, a red envelope from a first instant messaging application is displayed on a screen of a mobile terminal, a "hectareca remind you" to send billions of red envelopes and cash vouchers to the first instant messaging application, and the preemption time of the red envelope is displayed to be 21:00, wherein a trigger identifier of "view details" is provided in the reminding information, and a user can click the trigger identifier to view details of the red envelopes, which is a prompt in advance, for example, after the first application obtains the robbing red envelope event from a server, the user can be reminded that the hectareca cola will send hundreds of red envelopes and cash vouchers to the first instant messaging application at 21:00, and the user can be reminded to prepare in advance. At time 21:00, the first application may issue the alert again.
Fig. 7 is a schematic diagram of a friend red envelope reminding interface according to an embodiment of the present invention, and as shown in fig. 7, a "guanxiao" from a "waysian chart and waysian" group is displayed on an interface of a mobile terminal and is red envelope, so as to remind a user to click on the trigger and immediately grab a red envelope.
Fig. 8 is a schematic diagram of a flow-saving core module of a red packet alarm clock according to an embodiment of the present invention, as shown in fig. 8, in the mobile phone steward red packet alarm clock, the red packet event time sequence module, a built-in red packet leading module, and a data compression transmission module are included, where the red packet event time sequence module is updated when cloud control is idle, and by cloud control transmission of the red packet event, the post error correction capability is more powerful and efficient, the built-in red packet leading module is a system layer module, and the data compression transmission module is used for encrypting data in a data compression transmission process, so that the security of the data transmission process is improved, and the guarantee of the security of user properties is also improved. Meanwhile, the mobile phone housekeeper red packet alarm clock avoids scanning the network by presetting the red packet event time sequence, thereby reducing the use of the mobile phone memory and improving the user experience.
The mobile phone steward red packet alarm clock in the embodiment omits red packet events of a plurality of instant messaging application platforms which continuously scan main red packets by using a preset red packet event time sequence, the time sequence can be uniformly updated under an idle WIFI condition, and the use of mobile network flow is reduced to the greatest extent. The mobile phone steward red packet alarm clock is provided with the red packet getting module in a built-in mode, so that the trouble that a user receives a red packet reminder and needs to jump to other applications to get the red packet is avoided, and the red packet is directly got at the red packet alarm clock. The red packet alarm clock is compressed and encrypted on transmission data when a network scanning event is avoided, and flow is saved on the basis of safety.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
Example 2
According to the embodiment of the invention, the event processing device for implementing the event processing method is also provided. Fig. 9 is a schematic diagram of an alternative event processing apparatus according to an embodiment of the present invention, and as shown in fig. 9, the apparatus may include:
a receiving unit 10, configured to receive indication information indicating an event time point from the server.
A recording unit 20, configured to record, in the first application, an event time point indicated by the indication information, where the event time point is used to indicate a time point at which a target event to be executed is executed in the second application.
The display unit 30 is configured to display, when the event time point is reached, a reminder message in the first application, where the reminder message is used to indicate that the target event is executing, and the reminder message includes a preemption identifier, and the preemption identifier is used to preempt a target event resource of the target event.
And a judging unit 40, configured to judge whether a touch operation performed on the preemption identifier is detected.
An indicating unit 50, configured to, in a case where the touch operation is detected, indicate, in response to the touch operation, that the target event resource is to be preempted in the first application, and display, in the first application, a preemption result for preempting the target event resource.
It should be noted that the receiving unit 10 in this embodiment may be configured to execute step S202 in embodiment 1 of this application, the recording unit 20 in this embodiment may be configured to execute step S204 in embodiment 1 of this application, the display unit 30 in this embodiment may be configured to execute step S206 in embodiment 1 of this application, the determining unit 40 in this embodiment may be configured to execute step S208 in embodiment 1 of this application, and the indicating unit 50 in this embodiment may be configured to execute step S210 in embodiment 1 of this application.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of embodiment 1 described above. It should be noted that the modules described above as a part of the apparatus may operate in a hardware environment as shown in fig. 1, and may be implemented by software or hardware.
Through the module, the technical problem that the traffic consumption is increased due to the fact that whether the monitoring target event is executed or not is solved in each application, and the technical effect of reducing the traffic consumption when the monitoring target event is executed or not is achieved.
Alternatively, the indication information is used to indicate a plurality of event time points, and the recording unit 20 includes: the recording module is used for recording an event time sequence in the first application, wherein the event time sequence comprises a plurality of event time points which are arranged in a time sequence, and each event time point is used for indicating the time point of a target event to be executed in a second application.
Optionally, the apparatus further comprises: and the updating unit is used for updating the event time sequence after the event time sequence is recorded in the first application.
Optionally, the update unit comprises one of: the first updating module is used for updating the event time sequence when the terminal where the first application is located is connected to the wireless network; the second updating module is used for updating the event time sequence when the terminal where the first application is located is in an idle state; and the third updating module is used for updating the event time sequence when the terminal where the first application is located is connected to the wireless network and is in an idle state.
Optionally, the indication unit 50 includes: the indicating module is used for indicating the second application to seize the target event resource in the first application; and the receiving module is used for receiving the preemption result sent by the second application in the first application, wherein the preempted event resource indicated by the preemption result in the target event resource is transferred to a preset resource account, the preset resource account and a preset login account of the second application have a binding relationship, or the preempted event resource is transferred to the preset login account of the second application.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of embodiment 1 described above. It should be noted that the modules described above as a part of the apparatus may be operated in a hardware environment as shown in fig. 1, and may be implemented by software, or may be implemented by hardware, where the hardware environment includes a network environment.
Example 3
According to the embodiment of the invention, the invention also provides a server or a terminal for implementing the event processing method.
Fig. 10 is a block diagram of a terminal according to an embodiment of the present invention, and as shown in fig. 10, the terminal may include: one or more processors 201 (only one of which is shown), a memory 203, and a transmission device 205 (such as the transmission device in the above embodiment), as shown in fig. 10, the terminal may further include an input/output device 207.
The memory 203 may be used to store software programs and modules, such as program instructions/modules corresponding to the event processing method and apparatus in the embodiments of the present invention, and the processor 201 executes various functional applications and data processing by running the software programs and modules stored in the memory 203, that is, implements the event processing method. The memory 203 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 203 may further include memory located remotely from the processor 201, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 205 is used for receiving or sending data via a network, and can also be used for data transmission between a processor and a memory. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 205 includes a Network adapter (NIC) that can be connected to a router via a Network cable and other Network devices to communicate with the internet or a local area Network. In one example, the transmission device 205 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
Wherein the memory 203 is specifically used for storing application programs.
The processor 201 may call the application stored in the memory 203 via the transmission means 205 to perform the following steps: receiving indication information for indicating an event time point from a server; recording an event time point indicated by the indication information in the first application, wherein the event time point is used for indicating a time point at which a target event to be executed is executed in the second application; when the event time point is reached, displaying a reminding message in the first application, wherein the reminding message is used for indicating that the target event is being executed, the reminding message comprises a preemption identification, and the preemption identification is used for preempting the target event resource of the target event; judging whether touch operation executed on the preemption identification is detected; and under the condition that the touch operation is detected, responding to the touch operation to indicate that the target event resource is preempted in the first application, and displaying a preemption result of the target event resource in the first application.
The processor 201 is further configured to perform the following steps: the method comprises the steps of recording an event time sequence in a first application, wherein the event time sequence comprises a plurality of event time points arranged in a time sequence, and each event time point is used for indicating the time point when a target event to be executed is executed in a second application.
The processor 201 is further configured to perform the following steps: after the event time series is set in the first application in response to the indication information, the event time series is updated.
The processor 201 is further configured to perform the following steps: updating the event time sequence when the terminal where the first application is located is connected to the wireless network; updating the event time sequence when the terminal where the first application is located is in an idle state; and updating the event time sequence when the terminal where the first application is located is connected to the wireless network and is in an idle state.
The processor 201 is further configured to perform the following steps: indicating a second application to seize a target event resource in the first application; and receiving a preemption result sent by a second application in the first application, wherein the preempted event resources indicated by the preemption result in the target event resources are transferred to a preset resource account, and the preset resource account and a preset login account of the second application have a binding relationship, or the preempted event resources are transferred to the preset login account of the second application.
The embodiment of the invention provides a scheme of an event processing method. By receiving indication information indicating a time point from the server, and then recording the time point indicating that the target event is executed in the second application in the first application, displaying a reminding message after reaching the corresponding time point, reminding that the target event is executing, displaying a preemption identification reminding the user to preempt the target event resource, when detecting the touch operation of the preemption identification, preempts the target event resource in the first application and displays the preemption result of the target event resource in the first application, thereby achieving the purpose of preempting the resource of the target event in the second application in the first application, thereby realizing the technical effect of monitoring and preempting the target event of the second application in the first application so as to reduce the traffic consumption, and the technical problem that the related art increases the traffic consumption by continuously monitoring whether the target event is executed in each application is solved.
Optionally, the specific examples in this embodiment may refer to the examples described in embodiment 1 and embodiment 2, and this embodiment is not described herein again.
It will be understood by those skilled in the art that the structure shown in fig. 10 is merely an illustration, and the terminal may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, and a Mobile Internet Device (MID), a PAD, etc. Fig. 10 is a diagram illustrating a structure of the electronic device. For example, the terminal may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 10, or have a different configuration than shown in FIG. 10.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
Example 4
The embodiment of the invention also provides a storage medium. Alternatively, in this embodiment, the storage medium may be a program code for executing the event processing method.
Optionally, in this embodiment, the storage medium may be located on at least one of a plurality of network devices in a network shown in the above embodiment.
Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:
s1, receiving indication information indicating an event time point from the server;
s2, recording an event time point indicated by the indication information in the first application, wherein the event time point is used for indicating the time point of the target event to be executed in the second application;
s3, when the event time point is reached, displaying a reminding message in the first application, wherein the reminding message is used for indicating that the target event is being executed, the reminding message comprises a preemption identification, and the preemption identification is used for preempting the target event resource of the target event;
s4, judging whether the touch operation executed on the preemption identification is detected;
and S5, under the condition that the touch operation is detected, responding to the touch operation to indicate that the target event resource is preempted in the first application, and displaying a preempt result of the target event resource in the first application.
Optionally, the storage medium is further arranged to store program code for performing the steps of: the method comprises the steps of recording an event time sequence in a first application, wherein the event time sequence comprises a plurality of event time points arranged in a time sequence, and each event time point is used for indicating the time point when a target event to be executed is executed in a second application.
Optionally, the storage medium is further arranged to store program code for performing the steps of: after the event time series is set in the first application in response to the indication information, the event time series is updated.
Optionally, the storage medium is further arranged to store program code for performing the steps of: updating the event time sequence when the terminal where the first application is located is connected to the wireless network; updating the event time sequence when the terminal where the first application is located is in an idle state; and updating the event time sequence when the terminal where the first application is located is connected to the wireless network and is in an idle state.
Optionally, the storage medium is further arranged to store program code for performing the steps of: indicating a second application to seize a target event resource in the first application; and receiving a preemption result sent by a second application in the first application, wherein the preempted event resources indicated by the preemption result in the target event resources are transferred to a preset resource account, and the preset resource account and a preset login account of the second application have a binding relationship, or the preempted event resources are transferred to the preset login account of the second application.
Optionally, the specific examples in this embodiment may refer to the examples described in embodiment 1 and embodiment 2, and this embodiment is not described herein again.
Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing one or more computer devices (which may be personal computers, servers, network devices, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention.
In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims (8)

1. An event processing method, comprising:
receiving indication information carrying a time point of a resource preemption event from a server; the indication information is used for indicating a resource preemption event time point;
recording a resource preemption event time point indicated by the indication information in the first application, wherein the resource preemption event time point is used for indicating a time point at which a target event to be executed is executed in the second application; the recording, in the first application, the resource preemption event time point indicated by the indication information includes: recording an event time sequence in the first application, wherein the event time sequence comprises a plurality of resource preemption event time points arranged in a time sequence;
updating the resource preemption event time series after recording the event time series in the first application, the updating the event time series comprising one of: updating the event time sequence when the terminal where the first application is located is connected to a wireless network; updating the event time sequence when the terminal where the first application is located is in an idle state; updating the event time sequence when the terminal where the first application is located is connected to a wireless network and is in an idle state;
displaying the recorded multiple resource preemption event time points and one or more events corresponding to the resource preemption event time points in the first application, and displaying a trigger identifier and a target event resource total amount of the target event to be executed, wherein the target event resource total amount is indicated by the resource preemption event time points, and the trigger identifier is used for indicating to upgrade or download the second application;
displaying an advance reminder message in the first application, wherein the advance reminder message is used for indicating that the target event is executed at the resource preemption event time point when the preset time is earlier than the resource preemption event time point;
when the time point of the resource preemption event is reached, displaying a reminding message in the first application, wherein the reminding message is used for indicating that the target event is being executed, the reminding message comprises a preemption identification, the preemption identification is used for preempting the target event resource of the target event, and the preemption identification adopts an identification corresponding to the target event in the second application to distinguish different target events from different applications;
judging whether touch operation executed on the preemption identification is detected;
and under the condition that the touch operation is detected, responding to the touch operation to indicate the second application to preempt the target event resource in the second application in the first application, and receiving and displaying a preempt result sent by the second application and preempted the target event resource in the first application.
2. The method according to claim 1, wherein said indication information is used to indicate said plurality of said resource preemption event time points, wherein each of said resource preemption event time points is used to indicate a time point at which one of said target events to be executed is executed in one of said second applications.
3. The method of claim 1,
and transferring the preempted event resource indicated by the preemption result in the target event resource to a preset resource account, wherein the preset resource account and the preset login account of the second application have a binding relationship, or transferring the preempted event resource to the preset login account of the second application.
4. An event processing apparatus, comprising:
a receiving unit, configured to receive, from a server, indication information carrying a resource preemption event time point, where the indication information is used to indicate the resource preemption event time point;
a recording unit, configured to record, in the first application, a resource preemption event time point indicated by the indication information, where the resource preemption event time point is used to indicate a time point at which a target event to be executed is executed in the second application;
a display unit, configured to display an advance warning message in the first application, where the advance warning message is used to indicate that the target event is executed at the resource preemption event time point at a predetermined time earlier than the resource preemption event time point;
the display unit is further configured to display a prompting message in the first application when the resource preemption event time point is reached, where the prompting message is used to indicate that the target event is executing, the prompting message includes a preemption identifier, the preemption identifier is used to preempt a target event resource of the target event, and the preemption identifier uses an identifier corresponding to the target event in the second application to distinguish different target events from different applications;
a judging unit, configured to judge whether a touch operation performed on the preemption identifier is detected;
an indicating unit, configured to, in a case that the touch operation is detected, indicate, in the first application, to preempt the target event resource in response to the touch operation, and display a preemption result of the target event resource in the first application;
wherein the indication unit includes: an indicating module, configured to indicate, in the first application, that the second application preempts a target event resource in the second application; a receiving module, configured to receive, in the first application, the preemption result sent by the second application;
the recording unit includes: a recording module, configured to record an event time sequence in the first application, where the event time sequence includes a plurality of resource preemption event time points arranged in a time sequence;
the device further comprises: an updating unit, configured to update the event time series after recording the event time series in the first application; the update unit includes one of: the first updating module is used for updating the event time sequence when the terminal where the first application is located is connected to a wireless network; the second updating module is used for updating the event time sequence when the terminal where the first application is located is in an idle state; the third updating module is used for updating the event time sequence when the terminal where the first application is located is connected to a wireless network and is in an idle state;
the apparatus is further configured to: displaying, in the first application, the recorded one or more resource preemption event time points and one or more events corresponding to the resource preemption event time points, and displaying, in the first application, a trigger and a target event resource total of the target event to be executed, where the target event resource total is indicated by the resource preemption event time points, where the trigger is used to indicate to upgrade or download the second application.
5. The apparatus according to claim 4, wherein said indication information is used to indicate said plurality of said resource preemption event time points, wherein each of said resource preemption event time points is used to indicate a time point at which one of said target events to be executed is executed in one of said second applications.
6. The apparatus of claim 4,
and transferring the preempted event resource indicated by the preemption result in the target event resource to a preset resource account, wherein the preset resource account and the preset login account of the second application have a binding relationship, or transferring the preempted event resource to the preset login account of the second application.
7. A computer-readable storage medium comprising a stored program, wherein the program, when executed by a processor, performs the method of any of claims 1 to 3.
8. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 3 by means of the computer program.
CN201610597138.3A 2016-07-26 2016-07-26 Event processing method and device Active CN107528717B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610597138.3A CN107528717B (en) 2016-07-26 2016-07-26 Event processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610597138.3A CN107528717B (en) 2016-07-26 2016-07-26 Event processing method and device

Publications (2)

Publication Number Publication Date
CN107528717A CN107528717A (en) 2017-12-29
CN107528717B true CN107528717B (en) 2020-08-25

Family

ID=60748493

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610597138.3A Active CN107528717B (en) 2016-07-26 2016-07-26 Event processing method and device

Country Status (1)

Country Link
CN (1) CN107528717B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104468760A (en) * 2014-11-28 2015-03-25 小米科技有限责任公司 Method and device for pushing reminding information
CN104821987A (en) * 2015-04-16 2015-08-05 小米科技有限责任公司 Alarm clock-based reminding method and device
CN105138229A (en) * 2015-09-29 2015-12-09 联想(北京)有限公司 Information processing method and electronic equipment
CN105630499A (en) * 2015-12-24 2016-06-01 北京奇虎科技有限公司 Method and device for processing information

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8943146B2 (en) * 2010-09-21 2015-01-27 Benbria Corporation Method and system and apparatus for mass notification and instructions to computing devices

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104468760A (en) * 2014-11-28 2015-03-25 小米科技有限责任公司 Method and device for pushing reminding information
CN104821987A (en) * 2015-04-16 2015-08-05 小米科技有限责任公司 Alarm clock-based reminding method and device
CN105138229A (en) * 2015-09-29 2015-12-09 联想(北京)有限公司 Information processing method and electronic equipment
CN105630499A (en) * 2015-12-24 2016-06-01 北京奇虎科技有限公司 Method and device for processing information

Also Published As

Publication number Publication date
CN107528717A (en) 2017-12-29

Similar Documents

Publication Publication Date Title
EP2682863B1 (en) Installing applications remotely
CN110035004B (en) User name card sharing method, friend adding method and related device
US9497142B2 (en) Triggering actions on a computing device
CN109936621B (en) Information security multi-page message pushing method, device, equipment and storage medium
CN107786601B (en) Information processing method, terminal and server
CN105516246B (en) A kind of method and server of anti-application program downloading abduction
WO2017084531A1 (en) Method and device for data display
EP3076290B1 (en) Method and device for remotely updating application program
WO2017201965A1 (en) Notification message display method and device, and terminal
CN104639423A (en) Information interaction method, information interaction device and terminals
CN105786839A (en) Application data acquisition method and apparatus
CN104426960B (en) A kind of trial method and device of payment applications
WO2017166906A1 (en) Method of managing euicc subscription profile and associated apparatus
CN110826965A (en) Intelligent warehouse management method and device, handheld device and storage medium
EP3506599B1 (en) Method for synchronizing contact information, apparatus and medium
CN107360179B (en) Risk information sharing method, terminal and computer readable storage medium
CN108462734B (en) Message receiving method and device
CN108763311A (en) Interface display method, device, intelligent interaction tablet and storage medium
CN106686204B (en) Event-handling method and device
CN104346460B (en) Carry out the method, apparatus and browser client of file download
CN109343944A (en) Data processing method, device, terminal and the storage medium of eSIM card
CN107528717B (en) Event processing method and device
CN111107147B (en) Message pushing method and device
CN110752963B (en) Event processing method and device, storage medium and electronic device
CN107545413A (en) Event-handling method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant