WO2017202281A1 - 一种通知栏消息的处理方法及装置 - Google Patents

一种通知栏消息的处理方法及装置 Download PDF

Info

Publication number
WO2017202281A1
WO2017202281A1 PCT/CN2017/085435 CN2017085435W WO2017202281A1 WO 2017202281 A1 WO2017202281 A1 WO 2017202281A1 CN 2017085435 W CN2017085435 W CN 2017085435W WO 2017202281 A1 WO2017202281 A1 WO 2017202281A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
target
type
target message
application
Prior art date
Application number
PCT/CN2017/085435
Other languages
English (en)
French (fr)
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 WO2017202281A1 publication Critical patent/WO2017202281A1/zh
Priority to US15/982,495 priority Critical patent/US11095739B2/en

Links

Images

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/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/226—Delivery according to priorities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing a notification bar message.
  • the terminal notification bar is increasingly important as a user interaction scenario.
  • the various applications installed and used by the user on the terminal usually push the various types of messages to the terminal notification bar, which may come from the application itself or from various software development kits integrated by the application (software development). Kit, SDK).
  • Kit software development kits integrated by the application
  • Various applications are constantly sending various types of messages, which makes the user's notification bar very easy to be filled, which brings great interference to the user and is not conducive to the user to find useful push messages.
  • the terminal may perform the push type identification based on the push message content of the notification bar, and then perform classification display according to the push message type.
  • this method initially achieves the purpose of classification management according to the push message type, There are some problems that cannot be solved: the content of the push message is relatively short, which makes it difficult to avoid the problem of not extracting valid information through the content, thus affecting further type recognition, and some push messages are just one picture, and there is no text information at all. Unable to sort by content.
  • the embodiment of the present invention provides a method and a device for processing a notification bar message, which can determine a target type of the target message according to a target interface identifier corresponding to the jump interface of the target message, and the accuracy is relatively high.
  • the first aspect of the present application provides a method for processing a notification bar message, including:
  • the target message is displayed in the notification bar according to the type of the target message.
  • the second aspect of the present application provides a processing device for a notification bar message, including:
  • a detecting module configured to detect a target message received by the terminal notification bar
  • a first acquiring module configured to acquire a target interface identifier included in the target message
  • a first determining module configured to determine, according to the target interface identifier, a type of the target message
  • a display module configured to display the target message in the notification bar according to the type of the target message.
  • the target message received by the terminal notification bar is detected, the target interface identifier included in the target message is obtained, and the type of the target message is determined according to the target interface identifier, according to the type of the target message, in the notification bar.
  • the target message is displayed.
  • the method determines the target type of the target message according to the target interface identifier corresponding to the jump interface of the target message, and does not limit the existence form of the target message, and the accuracy is relatively high.
  • FIG. 1 is a flowchart of a method for processing a notification bar message according to an embodiment of the present application
  • FIG. 2 is a flowchart of another method for processing a notification bar message according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of a storage form of a push message according to an embodiment of the present application.
  • FIG. 4 is a flowchart of establishing a preset rule base according to an embodiment of the present application.
  • FIG. 5 is a flowchart of processing a notification bar message according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a device for processing a notification bar message according to an embodiment of the present disclosure.
  • FIG. 1 is a flowchart of a method for processing a notification bar message according to an embodiment of the present application; the method may include the following steps S100 - S103 .
  • the various applications installed in the terminal can push messages to the notification bar of the terminal (the message is also referred to as a target message in the present application), and the messages can include text information, pictures or network links, etc., to trigger the user to click on their own feelings.
  • the target message may be a push message related to the terminal application, or may be an SDK-related push message integrated by the terminal.
  • the terminal may be a mobile terminal device such as a mobile phone, a PAD (tablet computer), a smart wearable device, or a mobile terminal device.
  • the application can be installed and run in the terminal, and the application can include, but is not limited to, an SNS (Social Networking Services) application, an instant messaging application, and the like.
  • SNS Social Networking Services
  • Target messages are often used to present relatively brief information that draws the user's attention and directs the user into a specific functional interface.
  • the user can click or delete the target message displayed in the notification bar of the terminal.
  • the terminal automatically jumps to the function interface corresponding to the message (ie, the target interface or the jump destination interface).
  • An example of a functional interface is a web page.
  • the target interface identifier corresponding to the target interface to be jumped by the target message is obtained, and the target interface identifier may include a package name and a class name of the target interface.
  • the target interface ID is included in the target message.
  • this destination jump is encapsulated into a PendingIntent structure that holds the Intent that will be triggered when the user triggers a push message click and cancel.
  • the destination jump of the push message can be judged as the main factor of the push message type division.
  • the terminal is installed with the A application and the B application, and the application between the A application and the B application has cooperation, and the messages pushed by the two are all a function interface of the B application. . Therefore, the source of a push message received by the notification bar may be an A application or a B application, but no matter who sends it, the final jump to the function interface in B. Therefore, the embodiment of the present application obtains the target interface identifier included in the push message.
  • the package name in the target interface identifier can distinguish which application the push message is pushed by.
  • the target interface identifier may be matched with at least one preset interface identifier in the preset rule base, and the message type corresponding to the matching preset interface identifier is determined as the type of the target message. (This type is also referred to as the target type in this application).
  • the preset rule base includes a correspondence between the preset interface identifier and the message type. It should be noted that each correspondence may be a first correspondence or a second correspondence.
  • the preset interface identifier in the first correspondence relationship matches the interface identifier included in the application-related push message installed by the terminal; the preset interface identifier in the second correspondence relationship is related to the software development kit SDK related to the terminal. The included interface identifiers match. .
  • the target message may be determined to be a push message of the application installed by the terminal; if the target interface identifier and the second corresponding relationship are preset interfaces, The identifier matching may determine that the target message is a push message of a software development kit SDK integrated by the terminal.
  • the correspondences in the preset rule base may all be the first correspondence, or all of the second correspondences, or the first correspondence and the second correspondence are included. It should be noted that the first correspondence relationship and the second correspondence relationship in the embodiment of the present application are only the category distinction of the correspondence relationship, and the first correspondence relationship and the second correspondence relationship in the preset rule base are mainly for determining a certain push.
  • the starting source of the message is from the application or the SDK.
  • the message type corresponding to the preset interface identifier that matches the target interface identifier in the preset rule base is determined as the type of the target message.
  • Push message type division can have multiple criteria. For example, according to whether the push message is resident in the notification bar, the push message can be divided into: resident class and cleanable class; then, according to the purpose of the push message, the push message can be divided into : System class, function class, information class, ie general class, advertising class Categories, each category is divided into the following small types:
  • System class Power network, storage, permissions, security Functional class Reminders, charge d'effort, mail, weather, traffic, navigation, finance, calendar, app updates, downloads Information class News, reading, video, information General class SMS, instant messaging, social updates, comment reminders Advertising class Advertising, promotion, recommendation
  • the type of the push message in the embodiment of the present application may be a small type in the above table, or may be a large type in the above table (ie, a system class, a function class, an information class, a generic class, an advertisement class).
  • the different types of the target message correspond to different display modes
  • the target message may be displayed in the notification bar according to the target type of the target message, for example, the display may be folded, displayed separately, or the like. It should be noted that it is necessary to set a display mode corresponding to different types in advance.
  • step S104 may also be performed before displaying the target message according to the target message type
  • the display priority may include a high priority or a low priority.
  • displaying the target message in the notification bar according to the type of the target message specifically includes:
  • the target message is merged and displayed with other messages in the notification bar, and the type of the other message is the same as the type of the target message;
  • the target message is directly displayed on the notification bar.
  • priorities corresponding to different types are set in advance. For example, advertisements and information classes have lower priority for push messages with greater user harassment, that is, pass, system, and function messages have higher priority. It should be noted that, if the type of the target message is a small type under the large types of the system class, the function class, the information class, the general class, and the advertisement class, when determining the priority, it is also necessary to determine the small type of the target message. Corresponding large types, which in turn determine the priority of the type of the target message.
  • each step described above may be performed by the terminal, or the above steps may be performed cooperatively by the terminal and the server (the terminal and the server are connected through a network).
  • the terminal cooperates with the server
  • part of the steps are performed by the terminal, and partially by the server, for example, by the server.
  • Steps 102 and 104 are performed while other steps are performed by the terminal.
  • the terminal may report the operation of the user to the push message to the server, and the server adjusts the priority of each type according to the statistics of the usage state of the user. For example, when a large number of users choose to cancel (don't care) for a certain type of push message, the priority of the push message of the type is lowered; when a large number of users select a click (care) for a certain type of push message, the type is raised. The priority of the push message. When adjusting the priority of each type, you can take a percentile measure, which is the percentage of users who care about this type of push message, ranging from 0-100. When the percentage of users who care about a certain type of push message is greater than a preset threshold (such as 50%), the priority of the type of push message is raised.
  • the server sends the re-determined priority of each type to the terminal.
  • the target message is merged with other messages and displayed in the notification bar.
  • the merged folding display is that the target message is combined with other messages and displayed in a notification bar, and the notification bar is only The total number of the target message and other messages is displayed, as well as the application or SDK from which each message comes from. When the user clicks on the notification bar, the content of each message is displayed separately.
  • the target message is directly displayed in the notification bar, that is, the content of the target message is displayed in the notification bar, and the user can directly obtain the content of the target message from the notification bar.
  • the processing method of the notification bar message may be implemented by a third-party application management application.
  • the SDK related push message is pushed by an application associated with the SDK.
  • the target message received by the terminal notification bar is detected, the target interface identifier included in the target message is obtained, and the type of the target message is determined according to the target interface identifier, and displayed in the notification bar according to the type of the target message.
  • the target message determines the type of the target message according to the target interface identifier, and does not limit the existence form of the target message, and the accuracy is relatively high.
  • FIG. 2 it is a flowchart of a method for processing a notification bar message according to an embodiment of the present application. As shown in the figure, the method for processing a notification bar message in this embodiment includes steps S200 to S209.
  • the installed application list of the terminal is obtained according to the system interface, and the application list includes at least one application.
  • the terminal has a notification management tool application, and after the notification management tool application is started, obtains a list of installed applications of the terminal according to the system interface, where the application list includes at least one application.
  • S201 Send an application identifier of the at least one application to a server, so that the server sets a preset rule base, where the preset rule base includes at least one first correspondence of each application in the at least one application, and a second correspondence of the SDKs associated with the plurality of applications in the at least one application.
  • the terminal sends the application identifier of the at least one application in the application list to the server, so that the server sets a preset rule base, where the application identifier may be the application package name.
  • the server stores a large number of interface identifiers (ie, Push Jump destinations) and the correspondence between the types of messages.
  • the correspondence may include the following: a package name, an identifier of the push message (Push id), whether the push message is sent by the SDK, and a default recommendation.
  • Push id an identifier of the push message
  • the optional correspondence can be organized as follows:
  • the terminal sends the related information of the push message to the server, where the information includes: the purpose of the Push jump, the identifier of the push message (Push id or Pushld), the copy, and whether the push message is The notification bar is resident and generates the application for Push.
  • the optional terminal sends the information to the server in the form of a table as follows:
  • the server receives the information of the multiple push messages, stores them according to the table shown in FIG. 3, and then performs classification preprocessing based on the preset keywords and the text of the push message by a classification algorithm (for example, Bayesian classification) to obtain the push.
  • a classification algorithm for example, Bayesian classification
  • the type of suggestion corresponding to the message is not limited to Bayesian classification, and other classification algorithms are also possible, such as: LR algorithm, decision tree algorithm, and the like.
  • the copy described above may be text information, pictures and/or web links contained in the push message, and the like.
  • the server initially determines the type of the recommendation corresponding to the push message according to the interface identifier of the jump destination interface (the specific determination method may also determine the classification algorithm according to the preset interface identifier keyword), and if the recommendation type is determined according to the push message copy If the type of the recommendation is the same as that determined by the purpose of the jump, the type of the recommendation is determined to be the corresponding type. If the type is different, the type of the pushed message is manually checked to determine the corresponding type.
  • Figure 4 shows the preset rule library Flow chart.
  • the push message corresponding to the interface identifier is considered to be an SDK-related message, and the interface is The identifier is extracted as an interface identifier corresponding to the SDK.
  • the terminal detects the push message, obtains the push message content information (including the interface identifier), and sends the information to the server, if the server If the interface identifier is not stored, it is saved to the result database.
  • the server periodically processes the data in the result library to form the type corresponding to the interface identifier, and after manual review, it is added to the rule base for later use.
  • the server obtains the first correspondence corresponding to the corresponding application identifier from the rule base, and the second correspondence corresponding to the SDK associated with the application.
  • step S202 of the embodiment of the present application please refer to the step S100 of the embodiment of FIG. 1 , and details are not described herein again.
  • the method further includes steps S203 to S205.
  • the target identifier of the target application that pushes the target message may be obtained, and the target identifier of the target application may be the package name of the target application.
  • determining, according to the matched application identifier, the message identifier that matches the target message may include searching, in the first correspondence relationship of the matched application identifier, whether a message identifier matching the target message exists. If yes, the message type corresponding to the matched message identifier determines the type of the target message.
  • the first correspondence corresponding to the matched application identifier is further searched for whether there is a message identifier matching the target message, and if yes, the matching identifier is matched.
  • the message type corresponding to the message identifier is determined as the type of the target message. If there is no message identifier matching the target message in the first correspondence, the target message may be an SDK-related push message, and the preset interface identifier in the preset rule base needs to be further matched.
  • the target interface identifier may be matched with at least one preset interface identifier in the preset rule base, and the message type corresponding to the matching preset interface identifier is determined as the type of the target message.
  • steps S206-S208 of the embodiment of the present application please refer to the steps S101-S103 of the embodiment of FIG. 1 , and details are not described herein again.
  • the method further includes step S209.
  • S209 Determine, if the user prohibits the push command of the target message, determine a plurality of applications associated with the SDK in the second correspondence, and control the plurality of applications to prohibit pushing the target message.
  • the target message is an SDK-related push message
  • the target message is an SDK-related push message
  • the push command acquires a plurality of applications associated with the SDK in the second correspondence, and controls the plurality of applications to prohibit pushing the target message, so that the user is not required to manually prohibit all related applications from prohibiting the push of the target message, which is very convenient to use.
  • the target message received by the terminal notification bar is detected, the target interface identifier included in the target message is obtained, and the type of the target message is determined according to the target interface identifier, and displayed in the notification bar according to the type of the target message.
  • the target message determines the type of the target message according to the target interface identifier, and does not limit the existence form of the target message, and the accuracy is relatively high.
  • FIG. 5 is a flowchart of processing a notification bar message according to an embodiment of the present application, as shown in the figure.
  • the application list is obtained according to the system interface, and then the application list is reported to the background, and the Push rule corresponding to the application (that is, the list of the interface identifier and the type correspondence) is pulled.
  • the server After receiving the terminal request, the server retrieves the rule corresponding to each package name from the rule base according to the package name, and delivers the rule to the terminal.
  • the Push information existing in the current notification bar is read to perform intelligent classification, and the Push that appears in the future is monitored.
  • a processing apparatus for a notification bar message provided by an embodiment of the present application will be described in detail below with reference to FIG.
  • FIG. 6 is a schematic structural diagram of a processing apparatus for a notification bar message according to an embodiment of the present disclosure.
  • the processing apparatus of the notification bar message includes a detection module 100, a first obtaining module 101, and a first determining module. 102 and display module 103.
  • the detecting module 100 is configured to detect a target message received by the terminal notification bar.
  • Various applications installed in the terminal can push target messages to the notification bar of the terminal, and the messages can include text information, pictures or network links, etc., to trigger the user to click on the content of interest.
  • the target message may be a push message related to the terminal application, or may be an SDK-related push message integrated by the terminal.
  • the terminal may be a mobile terminal device such as a mobile phone, a PAD (tablet computer), a smart wearable device, or a mobile terminal device.
  • the application can be installed and run in the terminal, and the application can include, but is not limited to, an SNS (Social Networking Services) application, an instant messaging application, and the like.
  • SNS Social Networking Services
  • the first obtaining module 101 is configured to acquire a target interface identifier included in the target message.
  • Target messages are often used to present relatively brief information that draws the user's attention and directs the user into a specific functional interface.
  • the user can click or delete the target message displayed in the notification bar of the terminal.
  • the terminal automatically jumps to the function interface corresponding to the message (ie, the target interface or the jump destination interface).
  • An example of a functional interface is a web page.
  • the first obtaining module 101 After detecting that the terminal notification bar receives the target message, the first obtaining module 101 acquires a target interface identifier corresponding to the target interface to be jumped by the target message, and the target interface identifier may include a package name and a class name of the target interface. . Typically, the target interface ID is included in the target message.
  • this purpose jump is encapsulated into a knot of PendingIntent Constructs an Intent that will be triggered when the user triggers a push message click and cancel.
  • PendingIntent Constructs an Intent that will be triggered when the user triggers a push message click and cancel.
  • the destination jump for the message does not change. Therefore, the destination jump of the push message can be judged as the main factor of the push message type division.
  • the terminal is installed with the A application and the B application, and the application between the A application and the B application has cooperation, and the messages pushed by the two are all of the B application.
  • Functional interface Therefore, the source of a push message received by the notification bar may be an A application or a B application, but no matter who sends it, the final jump to the function interface in B. Therefore, the embodiment of the present application obtains the target interface identifier included in the push message.
  • the package name in the target interface identifier can distinguish which application the push message is pushed by.
  • the first determining module 102 is configured to determine, according to the target interface identifier, a type of the target message.
  • the target interface identifier may be matched with at least one preset interface identifier in the preset rule base, and the message type corresponding to the matching preset interface identifier is determined as the target of the target message. Types of.
  • the preset rule base includes a correspondence between the preset interface identifier and the message type. It should be noted that each correspondence may be a first correspondence or a second correspondence.
  • the preset interface identifier in the first correspondence relationship matches the interface identifier included in the application-related push message installed by the terminal; the preset interface identifier in the second correspondence relationship is related to the software development kit SDK related to the terminal. The included interface identifiers match.
  • the target message may be determined to be a push message of the application installed by the terminal; if the target interface identifier and the second corresponding relationship are preset interfaces, The identifier matching may determine that the target message is a push message of a software development kit SDK integrated by the terminal.
  • the correspondences in the preset rule base may all be the first correspondence, or all of the second correspondences, or the first correspondence and the second correspondence are included. It should be noted that the first correspondence relationship and the second correspondence relationship in the embodiment of the present application are only the category distinction of the correspondence relationship, and the first correspondence relationship and the second correspondence relationship in the preset rule base are mainly for determining a certain push.
  • the starting source of the message is from the application or the SDK.
  • the message class corresponding to the preset interface identifier matching the target interface identifier in the preset rule base The type is determined as the type of the target message.
  • Push message type division can have multiple criteria. For example, according to whether the push message is resident in the notification bar, the push message can be divided into: resident class and cleanable class; then, according to the purpose of the push message, the push message can be divided into : System class, function class, information class, ie general class, advertising class, several major categories, each category is divided into the following small types:
  • System class Power network, storage, permissions, security Functional class Reminders, charge d'effort, mail, weather, traffic, navigation, finance, calendar, app updates, downloads Information class News, reading, video, information General class SMS, instant messaging, social updates, comment reminders Advertising class Advertising, promotion, recommendation
  • the type of the push message in the embodiment of the present application may be a small type in the above table, or may be a large type in the above table (ie, a system class, a function class, an information class, a generic class, an advertisement class).
  • the display module 103 is configured to display the target message in the notification bar according to the type of the target message.
  • the different types of the target message correspond to different display modes
  • the target message may be displayed in the notification bar according to the target type of the target message, for example, the display may be folded, displayed separately, or the like. It should be noted that it is necessary to set a display mode corresponding to different types in advance.
  • the processing device of the notification bar message further includes a second obtaining module 104 and a sending module 105;
  • the second obtaining module 104 is configured to acquire at least one application installed by the terminal.
  • the second obtaining module 104 acquires an installed application list of the terminal according to the system interface, where the application list includes at least one application.
  • the terminal has a notification management tool application, and after the notification management tool application is started, obtains a list of installed applications of the terminal according to the system interface, where the application list includes at least one application.
  • the sending module 105 is configured to send the application identifier of the at least one application to the server, so that the server sets a preset rule base, where the preset rule base includes at least one of each application in the at least one application a correspondence relationship and a second correspondence relationship of the SDKs associated with the plurality of applications in the at least one application.
  • the terminal sends the application identifier of the at least one application in the application list to the service.
  • the application identifier can be the package name of the application.
  • the server stores a large number of interface identifiers (Push Jump destinations) and the correspondence between the types of messages.
  • the correspondence may include the following: a package name, an identifier of the push message (Push id), whether the push message is sent by the SDK, and a default recommendation.
  • Push id an identifier of the push message
  • the optional correspondence can be organized as follows:
  • the terminal obtains the push message related information and sends the information to the server, where the information includes: a Push jump destination, a push message identifier (Push id), a copy, and a push message notification bar.
  • the application that is stationed and generates Push.
  • the optional terminal sends the information to the server in the form of a table as follows:
  • the server receives information of multiple push messages and stores them, and then performs classification preprocessing based on a predetermined keyword and a text of the push message by using a classification algorithm (for example, Bayesian classification) to obtain the The type of recommendation corresponding to the push message.
  • a classification algorithm for example, Bayesian classification
  • the classification algorithm is not limited to Bayesian classification, and other classification algorithms are also possible, such as: LR algorithm, decision tree algorithm, and the like.
  • the copy described above may be text information, pictures and/or web links contained in the push message, and the like.
  • the server initially determines the type of the recommendation corresponding to the push message according to the interface identifier of the jump destination interface (the specific determination method may also determine the classification algorithm according to the preset interface identifier keyword), and if the recommendation type is determined according to the push message copy If the type of the recommendation is the same as that determined by the purpose of the jump, the type of the recommendation is determined to be the corresponding type. If the type is different, the type of the pushed message is manually checked to determine the corresponding type.
  • the push message corresponding to the interface identifier is considered to be an SDK-related message, and the interface is The identifier is extracted as an interface identifier corresponding to the SDK.
  • the terminal detects the push message and obtains the push message content information (including the interface identifier), and Sent to the server, if the server does not store the interface identifier, save to the result library
  • the server periodically processes the data in the result library to form the type corresponding to the interface identifier, and after manual review, joins the rule base for later use.
  • the server obtains the first correspondence corresponding to the corresponding application identifier from the rule base, and the second correspondence corresponding to the SDK associated with the application.
  • the processing device of the notification bar message further includes a third obtaining module 106, a determining module 107, and a second determining module 108.
  • the third obtaining module 106 is configured to acquire a target identifier of the target application that pushes the target message.
  • the target identifier of the target application that pushes the target message may be obtained, and the target identifier of the target application may be the package name of the target application.
  • the determining module 107 is configured to determine whether an application identifier matching the target identifier exists in the preset rule base.
  • the second determining module 108 is configured to determine, if yes, a message identifier that matches the target message according to the matched application identifier.
  • determining, according to the matched application identifier, the message identifier that matches the target message may include searching, in the first correspondence relationship of the matched application identifier, whether a message identifier matching the target message exists. If yes, the message type corresponding to the matched message identifier determines the type of the target message.
  • the first correspondence corresponding to the matched application identifier is further searched for whether there is a message identifier matching the target message, and if yes, the matching identifier is matched.
  • the message type corresponding to the message identifier is determined as the type of the target message. If there is no message identifier matching the target message in the first correspondence, the target message may be an SDK-related push message, and the preset interface identifier in the preset rule base needs to be further matched.
  • the first obtaining module 101 is configured to acquire a target interface identifier included in the target message if the application identifier does not match the target identifier in the rule base.
  • the processing device of the notification bar message further includes a control module 109.
  • the control module 109 is configured to: if detecting a prohibition push instruction of the target message by the user, determine a plurality of applications associated with the SDK in the second correspondence, and control the multiple applications to prohibit pushing the target Message.
  • the target message is an SDK-related push message
  • the control module 109 controls the plurality of applications to prohibit pushing the target message, so that the user does not need to manually prohibit all related applications from prohibiting the push of the target message, and the use Very convenient.
  • the processing device of the notification bar message further includes a fourth obtaining module 110.
  • the fourth obtaining module 110 is configured to determine a display priority corresponding to the type of the target message.
  • the display priority may include a high priority or a low priority.
  • the display module 103 is specifically configured to: if the display priority corresponding to the type of the target message is a low priority, merge and display the target message with other messages in the notification bar, and the type of the other message is The target messages are of the same type.
  • the target message is directly displayed on the notification bar.
  • priorities corresponding to different types are set in advance. For example, advertisements and information classes have lower priority for push messages with greater user harassment, that is, pass, system, and function messages have higher priority. It should be noted that if the type of the target message is a small type under the large types of the system class, the function class, the information class, the general class, and the advertisement class, when determining the priority, it is also necessary to determine the corresponding size of the target type. The type, which in turn determines the priority of the type of the target message.
  • the terminal may report the operation of the user to the push message to the server, and the server adjusts the priority of each type according to the statistics of the usage state of the user. For example, when a large number of users choose to cancel (don't care) for a certain type of push message, the priority of the push message of the type is lowered; when a large number of users select a click (care) for a certain type of push message, the type is raised. The priority of the push message. When adjusting the priority of each type, you can take a percentile measure, which is the percentage of users who care about this type of push message, ranging from 0-100. When the percentage of users who care about a certain type of push message is greater than a preset threshold (such as 50%), the priority of the type of push message is raised.
  • the server sends the re-determined priority of each type to the terminal.
  • the target message is merged with other messages and displayed in the notification bar.
  • the merged folding display is that the target message is combined with other messages and displayed in a notification bar, and the notification bar is only Display the total number of target messages and other messages and each message From the application or SDK, when the user clicks on the notification bar, the content of each message will be displayed separately.
  • the target message is directly displayed in the notification bar, that is, the content of the target message is displayed in the notification bar, and the user can directly obtain the content of the target message from the notification bar.
  • the processing method of the notification bar message may be implemented by a third-party application management application.
  • the SDK related push message is pushed by an application associated with the SDK.
  • the target message received by the terminal notification bar is detected, the target interface identifier included in the target message is obtained, and the type of the target message is determined according to the target interface identifier, and displayed in the notification bar according to the type of the target message.
  • the target message determines the type of the target message according to the target interface identifier, and does not limit the existence form of the target message, and the accuracy is relatively high.
  • the program corresponding to the processing device of the notification bar message shown in FIG. 6 may be stored in a readable storage medium of the terminal (and/or server) and executed by at least one of the terminals (and/or the server) to implement the above A method of processing a notification bar message, the method comprising the process described in the method embodiment of Figures 1-2.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Information Transfer Between Computers (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请实施例提供一种通知栏消息的处理方法及装置，其中的方法可包括：检测终端通知栏接收的目标消息；获取所述目标消息所包含的目标界面标识；根据所述目标界面标识，确定所述目标消息的类型；根据所述目标消息的类型，在所述通知栏显示所述目标消息。采用本申请实施例可根据目标消息的跳转界面对应的目标界面标识确定该目标消息的目标类型，准确率比较高。

Description

一种通知栏消息的处理方法及装置
本申请要求于2016年5月24日提交中国专利局，申请号为201610349340.4，发明名称为“一种通知栏消息的处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，具体涉及一种通知栏消息的处理方法及装置。
背景技术
随着智能终端的普及和发展，终端通知栏作为用户交互场景的地位越来越重要。然而，用户在终端上安装使用的各种应用通常会向终端通知栏推送(Push)各类消息，这些消息可能来自应用本身，也可能来自于应用所集成的各种软件开发工具包(software development kit，SDK)。各种应用都在不停的发送各类消息，就导致用户的通知栏非常容易被占满，既给用户带了很大的干扰，又十分不利于用户发现有用的推送消息。
为了管理推送消息，终端可以以通知栏的推送消息内容为基础进行推送类型的识别，然后根据推送消息类型进行分类展示，这种方式虽然初步达到了按推送消息类型进行分类管理的目的，但仍存在如下一些问题无法解决：推送消息的内容比较简短，这就难以避免通过内容提取不到有效信息的问题，从而影响进一步的类型识别，并且有些推送消息只是一张图片，完全没有文字信息，也无法按内容进分类。
发明内容
本申请实施例提供一种通知栏消息的处理方法及装置，可根据目标消息的跳转界面对应的目标界面标识确定该目标消息的目标类型，准确率比较高。
本申请第一方面提供一种通知栏消息的处理方法，包括：
检测终端通知栏接收的目标消息；
获取所述目标消息所包含的目标界面标识；
根据所述目标界面标识，确定所述目标消息的类型；
根据所述目标消息的类型，在所述通知栏显示所述目标消息。
本申请第二方面提供一种通知栏消息的处理装置，包括：
检测模块，用于检测终端通知栏接收的目标消息；
第一获取模块，用于获取所述目标消息所包含的目标界面标识；
第一确定模块，用于根据所述目标界面标识，确定所述目标消息的类型；
显示模块，用于根据所述目标消息的类型，在所述通知栏显示所述目标消息。
实施本申请实施例，具有如下有益效果：
本申请实施例，检测终端通知栏接收的目标消息，获取该目标消息所包含的目标界面标识，根据所述目标界面标识，确定所述目标消息的类型，根据该目标消息的类型，在通知栏显示目标消息，这种方式根据目标消息的跳转界面对应的目标界面标识确定该目标消息的目标类型，不限定目标消息的存在形式，并且准确率比较高。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种通知栏消息的处理方法的流程图；
图2为本申请实施例提供的另一种通知栏消息的处理方法的流程图；
图3为本申请实施例提供的推送消息的存储形式示意图；
图4为本申请实施例提供的一种预设规则库建立流程图；
图5为本申请实施例提供的一种通知栏消息处理流程图；
图6为本申请实施例提供的一种通知栏消息的处理装置结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清 楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
下面将结合附图1-附图5，对本申请实施例提供的通知栏消息的处理方法进行详细介绍。
请参照图1，为本申请实施例提供的一种通知栏消息的处理方法的流程图；该方法可包括以下步骤S100-步骤S103。
S100，检测终端通知栏接收的目标消息。
终端中所安装的各种应用可以向终端的通知栏推送消息(该消息在本申请中也称作目标消息)，这些消息可以包含文本信息、图片或者网络链接等等，以触发用户点击自己感兴趣的内容。需要说明的是，该目标消息可以是终端应用相关的推送消息，也可以是终端所集成的SDK相关的推送消息。
本申请实施例中，终端可以是手机、PAD(平板电脑)、智能可穿戴设备等便携式终端设备或移动终端设备。终端中可安装并运行应用程序，此应用程序可包括但不限于：SNS(Social Networking Services，社会性网络服务)应用程序、即时通信应用程序等等。
S101，获取所述目标消息所包含的目标界面标识。
目标消息通常用于展示比较简短的信息，引起用户的关注，从而将用户引导进具体的功能界面当中。用户可以点击或者删除终端通知栏所显示的目标消息，当用户点击通知栏所显示的目标消息时，则终端会自动跳转到该消息对应的功能界面(即目标界面或跳转目的界面)。功能界面的一个示例是网页。
当检测到终端通知栏接收到目标消息后，获取该目标消息所确定的要跳转的目标界面对应的目标界面标识，该目标界面标识可以包括该目标界面的包名和类名。通常，目标界面标识包含在目标消息中。
对于安卓(Android)操作系统，这种目的跳转被封装成PendingIntent的结构，其中保存了在用户触发推送消息点击和取消时将会触发的Intent。对于一条推送消息来说，无论其发出者是哪个应用，推送此消息的应用的身份可能会发生变化，但该消息对应的目的跳转却是不会发生变化的。因此，可以将推送消息的目的跳转作为推送消息类型划分的主因素进行判断。
以应用间互发推送消息为例继续阐述：终端安装有A应用和B应用，A应用与B应用的厂商之间有合作，二者推送的消息跳转的都是B应用的某个功能界面。因此通知栏接收的某个推送消息的来源可能是A应用也可能是B应用，但无论是谁发出，最终要跳转到的都是B中的功能界面。因此本申请实施例获取推送消息包含的目标界面标识。
进一步可选的，通过目标界面标识中的包名可以区分该推送消息是由哪个应用推送的。
S102，根据所述目标界面标识，确定所述目标消息的类型。
本申请实施例中，可以将所述目标界面标识与预设规则库中的至少一个预设界面标识进行匹配，并将匹配一致的预设界面标识对应的消息类型确定为所述目标消息的类型(该类型在本申请中也称作目标类型)。
该预设规则库中包括预设界面标识与消息类型之间的对应关系。需要说明的是，每个对应关系可以为第一对应关系或者第二对应关系。第一对应关系中的预设界面标识与终端所安装应用相关推送消息所包含的界面标识匹配；该第二对应关系中的预设界面标识与终端所集成的软件开发工具包SDK相关推送消息所包含的界面标识匹配。。因此，如果所述目标界面标识与第一对应关系的预设界面标识匹配，可以确定所述目标消息是终端所安装应用的推送消息；如果所述目标界面标识与第二对应关系的预设界面标识匹配，可以确定所述目标消息是终端所集成的软件开发工具包SDK的推送消息。
该预设规则库中的对应关系可以全部为第一对应关系，或者全部为第二对应关系，或者第一对应关系和第二对应关系均包括。需要说明的是，本申请实施例的第一对应关系和第二对应关系仅仅是对应关系的类别区分，预设规则库中区分第一对应关系和第二对应关系主要是为了能够确定某一条推送消息的最起始的来源，是来自于应用或者SDK。
将该预设规则库中与目标界面标识匹配一致的预设界面标识对应的消息类型确定为目标消息的类型。
推送消息类型划分可以有多种标准，例如首先根据推送消息是否在通知栏常驻可以将推送消息分为：常驻类和可清理类；然后进一步根据推送消息的用途，将推送消息可以分为：系统类、功能类、信息类、即通类、广告类几个大 的类别，每个类别具体划分为如下一些小的类型：
系统类 电量、网络、存储空间、权限、安全
功能类 提醒、代办、邮件、天气、路况、导航、财务、日程、应用更新、下载
信息类 新闻、阅读、视频、资讯
即通类 短信、即时通信消息、社交动态、评论提醒
广告类 广告、促销、推荐
可选的，本申请实施例的推送消息类型可以为上述表格中的小类型，也可以为上述表格中的大类型(即系统类、功能类、信息类、即通类、广告类)。
S103，根据目标消息的类型，在所述通知栏显示所述目标消息。
本申请实施例中，目标消息的不同类型对应不同的显示方式，可以根据目标消息的目标类型，在通知栏显示该目标消息，例如可以折叠显示，单独显示等等。需要说明的是，预先需要设定不同类型对应的显示方式。
可选的，在根据目标消息类型显示目标消息之前还可以执行步骤S104；
S104，确定所述目标消息的类型对应的显示优先级。
所述显示优先级可以包括高优先级或者低优先级。
本申请实施例中，根据目标消息的类型，在通知栏显示目标消息具体包括：
若所述目标消息的类型对应的显示优先级为低优先级，则将所述目标消息与其它消息合并折叠显示于所述通知栏，所述其它消息的类型与所述目标消息的类型相同；
若所述目标消息的类型对应的显示优先级为高优先级，则将所述目标消息直接显示于所述通知栏。
本申请实施例中，预先设定不同类型对应的优先级，比如，广告、信息类对用户骚扰比较大的推送消息优先级较低，即通、系统、功能类消息优先级较高。需要说明的是，若目标消息的类型为系统类、功能类、信息类、即通类、广告类这些大类型下的小类型，在确定优先级时，还需要判断该目标消息的小类型所对应的大类型，进而确定该目标消息的类型的优先级。
在本申请的实施例中，可以由终端执行上述各个步骤，或者由终端与服务器(终端与服务器通过网络连接)协作执行上述各个步骤。在终端与服务器协作的情形下，部分步骤由终端执行，部分由服务器执行，例如可以由服务器执 行步骤102和104，而其他步骤由终端执行。
在本申请的实施例中，终端可以将用户对推送消息的操作上报到服务器，服务器根据用户使用状态的统计，对每个类型的优先级进行调整。例如当有大量用户对某一类推送消息都选择取消(不关心)时，则下调该类型推送消息的优先级；当大量用户对某一类推送消息选择点击(关心)时，则上调该类型推送消息的优先级。在调整每个类型的优先级时，可以采取百分制衡量，取值为关心该类型推送消息的用户百分比，取值范围为0-100。当关心某个类型推送消息的用户百分比大于预设阈值(比如50％)，则上调该类型推送消息的优先级。服务器将重新确定的各个类型的优先级发送至终端。
若目标消息的类型对应的显示优先级为低优先级，则将目标消息与其它消息合并折叠显示于通知栏，合并折叠显示即是目标消息与其它消息合并在一个通知栏显示，该通知栏仅仅显示目标消息与其它消息总的条数以及各条消息所来自的应用或者SDK，当用户点击该通知栏时，才会分别显示各条消息的内容。
若目标消息的类型对应的显示优先级为高优先级，则直接将目标消息显示于通知栏，即是将目标消息的内容显示于通知栏，用户可以直接从通知栏获取目标消息的内容。
本申请一个可选的实施例中，通知栏消息的处理方法可由第三方应用管理类应用程序运行实现。本申请一个可选的实施例中，SDK相关推送消息是由与该SDK关联的应用推送的。
本申请实施例，检测终端通知栏接收的目标消息，获取该目标消息包含的目标界面标识，根据所述目标界面标识，确定所述目标消息的类型，根据该目标消息的类型，在通知栏显示目标消息，这种方式根据目标界面标识确定该目标消息的类型，不限定目标消息的存在形式，准确率比较高。
请参照图2，为本申请实施例提供的另一种通知栏消息的处理方法的流程图，如图所示，本实施例的通知栏消息的处理方法包括步骤S200～S209。
S200，获取终端安装的至少一个应用。
本申请实施例中，根据系统接口获取终端已安装应用列表，该应用列表包括至少一个应用。
可选的，终端具有通知管理工具应用程序，在该通知管理工具应用程序启动后，根据系统接口获取终端已安装应用列表，该应用列表包括至少一个应用。
S201，将所述至少一个应用的应用标识发送至服务器，以使所述服务器组建预设规则库，所述预设规则库包含所述至少一个应用中每个应用的至少一个第一对应关系以及所述至少一个应用中多个应用关联的SDK的第二对应关系。
本申请实施例中，终端将应用列表中至少一个应用的应用标识发送至服务器，以使服务器组建预设规则库，该应用标识可以是应用的包名。
服务器存储了大量界面标识(即Push跳转目的)与消息的类型之间的对应关系。可选的，除了Push跳转目的与消息的类型之外，该对应关系可以包括以下内容：包名、推送消息的标识符(Push id)、推送消息是否SDK发出、默认建议。可选的该对应关系可以按如下的表格组织：
Figure PCTCN2017085435-appb-000001
可选的，终端在监控到推送消息产生后，会获取推送消息的相关信息发送至服务器，这些信息包括：Push跳转目的、推送消息的标识符(Push id或Pushld)、文案、推送消息是否通知栏常驻、产生Push的应用。可选的终端将该信息以如下的表格的形式发送给服务器：
跳转目的 Push id 文案 是否通知栏常驻 产生Push的应用
服务器接收到多个推送消息的信息，按照图3所示表格进行存储，然后基于预设的关键词与推送消息的文案，以分类算法(例如贝叶斯分类)进行分类预处理，得到该推送消息对应的建议类型。需要说明的是，该对文案进行预处理分类时，分类算法不局限于贝叶斯分类，其他分类算法也是可以的，如：LR算法、决策树算法等。上文所述文案可以是推送消息包含的文本信息、图片和/或网络链接等等。
同时，服务器根据跳转目的界面的界面标识，初步确定出推送消息对应的建议类型(具体确定方法也可以根据预设界面标识关键词进行分类算法确定)，若根据推送消息文案确定出的建议类型和根据跳转目的确定出的建议类型相同，则将该建议类型确定为对应的类型，若不同，需要人工对预处理后的推送消息类型进行审核，从而确定出对应的类型。其中，图4示出了预设规则库建 立流程图。
进一步，对所形成的对应关系进行确认时，若发现存在多个应用的推送消息对应的跳转目的界面的界面标识相同，则认为该界面标识对应的推送消息为SDK相关的消息，将该界面标识提取出来作为SDK对应的界面标识。
当服务器已经存储多个界面标识与类型之间的对应关系(即是多个Push规则)，则后期终端检测到推送消息，获取推送消息内容信息(包括界面标识)，并发送给服务器，若服务器未存储该界面标识，则保存至结果库中，服务器定期对结果库中的数据进行自动化处理，形成该界面标识对应的类型，并经过人工审核后，加入规则库中，便于后期使用。
当终端向服务器请求应用标识的对应关系时，服务器从规则库中获取相应的应用标识对应的第一对应关系，以及应用关联的SDK对应的第二对应关系。
S202，检测终端通知栏接收的目标消息。
本申请实施例步骤S202请参照图1的实施例步骤S100，在此不再赘述。
可选的，该方法还包括步骤S203～S205。
S203，获取推送所述目标消息的目标应用的目标标识。
本申请实施例中，在确定目标消息的目标类型时，可以获取推送该目标消息的目标应用的目标标识，目标应用的目标标识可以是该目标应用的包名。
S204，判断预设规则库中是否存在与所述目标标识匹配的应用标识。
S205，若存在，则根据所述匹配的应用标识确定与所述目标消息匹配的消息标识。
本申请实施例中，根据所述匹配的应用标识确定与所述目标消息匹配的消息标识可以包括在所述匹配的应用标识的第一对应关系中查找是否存在与所述目标消息匹配的消息标识，若存在，则将该匹配的消息标识对应的消息类型确定所述目标消息的类型。
本申请实施例中，当目标标识与规则库中的某个应用标识匹配，进一步包括匹配的应用标识的第一对应关系中查找是否存在与目标消息匹配的消息标识，若存在，则将匹配的消息标识对应的消息类型确定为目标消息的类型。若在该第一对应关系中不存在与目标消息匹配的消息标识，则可能该目标消息为SDK相关的推送消息，需要进一步用预设规则库中的预设界面标识进行匹配。
S206，若所述规则库中没有应用标识与所述目标标识匹配，则获取所述目标消息所包含的目标界面标识。
S207，根据所述目标界面标识，确定所述目标消息的类型。
可以将所述目标界面标识与预设规则库中的至少一个预设界面标识进行匹配，并将匹配一致的预设界面标识对应的消息类型确定为所述目标消息的类型。
S208，根据所述目标消息的类型，在所述通知栏显示所述目标消息。
本申请实施例步骤S206-S208请参照图1的实施例步骤S101-S103，在此不再赘述。
可选的，若所述目标界面标识与所述预设规则库的所述第二对应关系中的预设界面标识匹配；所述方法还包括步骤S209。
S209，若检测到用户对所述目标消息的禁止推送指令，则确定与所述第二对应关系中的SDK关联的多个应用，并控制所述多个应用禁止推送所述目标消息。
本申请实施例中，目标界面标识与预设规则库中的第二对应关系中的预设界面标识匹配，则说明该目标消息为SDK相关的推送消息，若检测到用户对该目标消息的禁止推送指令，则获取该第二对应关系中SDK关联的多个应用，控制该多个应用禁止推送所述目标消息，这样不需要用户手动去禁止所有相关应用禁止推送该目标消息，使用非常方便。
本申请实施例，检测终端通知栏接收的目标消息，获取该目标消息包含的目标界面标识，根据所述目标界面标识，确定所述目标消息的类型，根据该目标消息的类型，在通知栏显示目标消息，这种方式根据目标界面标识确定该目标消息的类型，不限定目标消息的存在形式，准确率比较高。
请参照图5，为本申请实施例提供的通知栏消息的处理流程图，如图所示，
(1)在终端通知管理工具应用启动后，根据系统接口获取已安装应用列表，然后将应用列表上报到后台，拉取应用对应的Push规则(即是界面标识与类型对应关系的列表)。
(2)服务器接收到终端请求后，根据包名从规则库中检索各包名对应的规则，并下发到终端。
(3)在通知管理工具中，通过用户引导的方式，引导用户对通知管理工具进行“通知管理权限”的授权。
(4)在成功拉取到应用的规则，并且取得授权后，开始读取当前通知栏存在的Push信息进行智能分类，并对未来出现的Push进行监控。
(5)然后根据Push的等级做分类展示和折叠处理等。
下面将结合附图6，对本申请实施例提供的一种通知栏消息的处理装置进行详细介绍。
请参照图6，为本申请实施例提供的一种通知栏消息的处理装置结构示意图，如图所示，该通知栏消息的处理装置包括检测模块100、第一获取模块101、第一确定模块102以及显示模块103。
检测模块100，用于检测终端通知栏接收的目标消息。
终端中所安装的各种应用可以向终端的通知栏推送目标消息，这些消息可以包含文本信息、图片或者网络链接等等，以触发用户点击自己感兴趣的内容。需要说明的是，该目标消息可以是终端应用相关的推送消息，也可以是终端所集成的SDK相关的推送消息。
本申请实施例中，终端可以是手机、PAD(平板电脑)、智能可穿戴设备等便携式终端设备或移动终端设备。终端中可安装并运行应用程序，此应用程序可包括但不限于：SNS(Social Networking Services，社会性网络服务)应用程序、即时通信应用程序等等。
第一获取模块101，用于获取所述目标消息所包含的目标界面标识。
目标消息通常用于展示比较简短的信息，引起用户的关注，从而将用户引导进具体的功能界面当中。用户可以点击或者删除终端通知栏所显示的目标消息，当用户点击通知栏所显示的目标消息时，则终端会自动跳转到该消息对应的功能界面(即目标界面或跳转目的界面)。功能界面的一个示例是网页。
当检测到终端通知栏接收到目标消息后，第一获取模块101获取该目标消息所确定的要跳转的目标界面对应的目标界面标识，该目标界面标识可以包括该目标界面的包名和类名。通常，目标界面标识包含在目标消息中。
对于安卓(Android)操作系统，这种目的跳转被封装成PendingIntent的结 构，其中保存了在用户触发推送消息点击和取消时将会触发的Intent。对于一条推送消息来说，无论其发出者是哪个应用，推送此消息的应用的身份可能会发生变化，但该消息对应的目的跳转却是不会发生变化的。因此，可以将推送消息的目的跳转作为推送消息类型划分的主因素进行判断。
以应用间互发推送消息的列子为例继续阐述：终端安装有A应用和B应用，A应用与B应用的厂商之间有合作，二者推送的消息跳转的都是B应用的某个功能界面。因此通知栏接收的某个推送消息的来源可能是A应用也可能是B应用，但无论是谁发出，最终要跳转到的都是B中的功能界面。因此本申请实施例获取推送消息包含的目标界面标识。
进一步可选的，通过目标界面标识中的包名可以区分该推送消息是由哪个应用推送的。
第一确定模块102，用于根据所述目标界面标识，确定所述目标消息的类型。
本申请实施例中，可以将所述目标界面标识与预设规则库中的至少一个预设界面标识进行匹配，并将匹配一致的预设界面标识对应的消息类型确定为所述目标消息的目标类型。
该预设规则库中包括预设界面标识与消息类型之间的对应关系。需要说明的是，每个对应关系可以为第一对应关系或者第二对应关系。第一对应关系中的预设界面标识与终端所安装应用相关推送消息所包含的界面标识匹配；该第二对应关系中的预设界面标识与终端所集成的软件开发工具包SDK相关推送消息所包含的界面标识匹配。因此，如果所述目标界面标识与第一对应关系的预设界面标识匹配，可以确定所述目标消息是终端所安装应用的推送消息；如果所述目标界面标识与第二对应关系的预设界面标识匹配，可以确定所述目标消息是终端所集成的软件开发工具包SDK的推送消息。
该预设规则库中的对应关系可以全部为第一对应关系，或者全部为第二对应关系，或者第一对应关系和第二对应关系均包括。需要说明的是，本申请实施例的第一对应关系和第二对应关系仅仅是对应关系的类别区分，预设规则库中区分第一对应关系和第二对应关系主要是为了能够确定某一条推送消息的最起始的来源，是来自于应用或者SDK。
将该预设规则库中与目标界面标识匹配一致的预设界面标识对应的消息类 型确定为目标消息的类型。
推送消息类型划分可以有多种标准，例如首先根据推送消息是否在通知栏常驻可以将推送消息分为：常驻类和可清理类；然后进一步根据推送消息的用途，将推送消息可以分为：系统类、功能类、信息类、即通类、广告类几个大的类别，每个类别具体划分为如下一些小的类型：
系统类 电量、网络、存储空间、权限、安全
功能类 提醒、代办、邮件、天气、路况、导航、财务、日程、应用更新、下载
信息类 新闻、阅读、视频、资讯
即通类 短信、即时通信消息、社交动态、评论提醒
广告类 广告、促销、推荐
可选的，本申请实施例的推送消息类型可以为上述表格中的小类型，也可以为上述表格中的大类型(即系统类、功能类、信息类、即通类、广告类)。
显示模块103，用于根据所述目标消息的类型，在所述通知栏显示所述目标消息。
本申请实施例中，目标消息的不同类型对应不同的显示方式，可以根据目标消息的目标类型，在通知栏显示该目标消息，例如可以折叠显示，单独显示等等。需要说明的是，预先需要设定不同类型对应的显示方式。
可选的，所述通知栏消息的处理装置还包括第二获取模块104和发送模块105；
第二获取模块104，用于获取终端安装的至少一个应用。
本申请实施例中，第二获取模块104根据系统接口获取终端已安装应用列表，该应用列表包括至少一个应用。
可选的，终端具有通知管理工具应用程序，在该通知管理工具应用程序启动后，根据系统接口获取终端已安装应用列表，该应用列表包括至少一个应用。
发送模块105，用于将所述至少一个应用的应用标识发送至服务器，以使所述服务器组建预设规则库，所述预设规则库包含所述至少一个应用中每个应用的至少一个第一对应关系以及所述至少一个应用中多个应用关联的SDK的第二对应关系。
本申请实施例中，终端将应用列表中至少一个应用的应用标识发送至服务 器，以使服务器组建预设规则库，该应用标识可以是应用的包名。
服务器存储了大量界面标识(Push跳转目的)与消息的类型之间的对应关系。可选的，除了Push跳转目的与消息的类型之外，该对应关系可以包括以下内容：包名、推送消息的标识符(Push id)、推送消息是否SDK发出、默认建议。可选的该对应关系可以按如下的表格组织：
Figure PCTCN2017085435-appb-000002
可选的，终端在监控到推送消息产生后，会获取推送消息相关信息发送至服务器，这些信息包括：Push跳转目的、推送消息的标识符(Push id)、文案、推送消息是否通知栏常驻、产生Push的应用。可选的终端将该信息以如下的表格的形式发送给服务器：
跳转目的 Push id 文案 是否通知栏常驻 产生Push的应用
如图3所示，服务器接收到多个推送消息的信息，并进行存储，然后基于预设的关键词与推送消息的文案，以分类算法(例如贝叶斯分类)进行分类预处理，得到该推送消息对应的建议类型。需要说明的是，该对文案进行预处理分类时，分类算法不局限于贝叶斯分类，其他分类算法也是可以的，如：LR算法、决策树算法等。上文所述文案可以是推送消息包含的文本信息、图片和/或网络链接等等。
同时，服务器根据跳转目的界面的界面标识，初步确定出推送消息对应的建议类型(具体确定方法也可以根据预设界面标识关键词进行分类算法确定)，若根据推送消息文案确定出的建议类型和根据跳转目的确定出的建议类型相同，则将该建议类型确定为对应的类型，若不同，需要人工对预处理后的推送消息类型进行审核，从而确定出对应的类型。
进一步，对所形成的对应关系进行确认时，若发现存在多个应用的推送消息对应的跳转目的界面的界面标识相同，则认为该界面标识对应的推送消息为SDK相关的消息，将该界面标识提取出来作为SDK对应的界面标识。
如图4所示，当服务器已经存储多个界面标识与类型之间的对应关系(即是多个Push规则)，则后期终端检测到推送消息，获取推送消息内容信息(包括界面标识)，并发送给服务器，若服务器未存储该界面标识，则保存至结果库 中，服务器定期对结果库中的数据进行自动化处理，形成该界面标识对应的类型，并经过人工审核后，加入规则库中，便于后期使用。
当终端向服务器请求应用标识的对应关系时，服务器从规则库中获取相应的应用标识对应的第一对应关系，以及应用关联的SDK对应的第二对应关系。
可选的，所述通知栏消息的处理装置还包括第三获取模块106、判断模块107以及第二确定模块108。
第三获取模块106，用于获取推送所述目标消息的目标应用的目标标识。
本申请实施例中，在确定目标消息的目标类型时，可以获取推送该目标消息的目标应用的目标标识，目标应用的目标标识可以是该目标应用的包名。
判断模块107，用于判断预设规则库中是否存在与所述目标标识匹配的应用标识。
第二确定模块108，用于若存在，则根据所述匹配的应用标识确定与所述目标消息匹配的消息标识。
本申请实施例中，根据所述匹配的应用标识确定与所述目标消息匹配的消息标识可以包括在所述匹配的应用标识的第一对应关系中查找是否存在与所述目标消息匹配的消息标识，若存在，则将该匹配的消息标识对应的消息类型确定所述目标消息的类型。
本申请实施例中，当目标标识与规则库中的某个应用标识匹配，进一步包括匹配的应用标识的第一对应关系中查找是否存在与目标消息匹配的消息标识，若存在，则将匹配的消息标识对应的消息类型确定为目标消息的类型。若在该第一对应关系中不存在与目标消息匹配的消息标识，则可能该目标消息为SDK相关的推送消息，需要进一步用预设规则库中的预设界面标识进行匹配。
所述第一获取模块101，具体用于若所述规则库中没有应用标识与所述目标标识匹配，则获取所述目标消息所包含的目标界面标识。
可选的，若所述目标界面标识与所述预设规则库的所述第二对应关系中的预设界面标识匹配；所述通知栏消息的处理装置还包括控制模块109。
控制模块109，用于若检测到用户对所述目标消息的禁止推送指令，则确定与所述第二对应关系中的SDK关联的多个应用，并控制所述多个应用禁止推送所述目标消息。
本申请实施例中，目标界面标识与预设规则库中的第二对应关系中的预设界面标识匹配，则说明该目标消息为SDK相关的推送消息，若检测到用户对该目标消息的禁止推送指令，则获取该第二对应关系中SDK关联的多个应用，控制模块109控制该多个应用禁止推送所述目标消息，这样不需要用户手动去禁止所有相关应用禁止推送该目标消息，使用非常方便。
可选的，所述通知栏消息的处理装置还包括第四获取模块110。
第四获取模块110，用于确定所述目标消息的类型对应的显示优先级。
所述显示优先级可以包括高优先级或者低优先级。
所述显示模块103具体用于若所述目标消息的类型对应的显示优先级为低优先级，则将所述目标消息与其它消息合并折叠显示于所述通知栏，所述其它消息的类型与所述目标消息的类型相同。
若所述目标消息的类型对应的显示优先级为高优先级，则将所述目标消息直接显示于所述通知栏。
本申请实施例中，预先设定不同类型对应的优先级，比如，广告、信息类对用户骚扰比较大的推送消息优先级较低，即通、系统、功能类消息优先级较高。需要说明的是，若目标消息的类型为系统类、功能类、信息类、即通类、广告类这些大类型下的小类型，在确定优先级时，还需要判断该目标类型所对应的大类型，进而确定该目标消息的类型的优先级。
在本申请的实施例中，终端可以将用户对推送消息的操作上报到服务器，服务器根据用户使用状态的统计，对每个类型的优先级进行调整。例如当有大量用户对某一类推送消息都选择取消(不关心)时，则下调该类型推送消息的优先级；当大量用户对某一类推送消息选择点击(关心)时，则上调该类型推送消息的优先级。在调整每个类型的优先级时，可以采取百分制衡量，取值为关心该类型推送消息的用户百分比，取值范围为0-100。当关心某个类型推送消息的用户百分比大于预设阈值(比如50％)，则上调该类型推送消息的优先级。服务器将重新确定的各个类型的优先级发送至终端。
若目标消息的类型对应的显示优先级为低优先级，则将目标消息与其它消息合并折叠显示于通知栏，合并折叠显示即是目标消息与其它消息合并在一个通知栏显示，该通知栏仅仅显示目标消息与其它消息总的条数以及各条消息所 来自的应用或者SDK，当用户点击该通知栏时，才会分别显示各条消息的内容。
若目标消息的类型对应的显示优先级为高优先级，则直接将目标消息显示于通知栏，即是将目标消息的内容显示于通知栏，用户可以直接从通知栏获取目标消息的内容。
本申请一个可选的实施例中，通知栏消息的处理方法可由第三方应用管理类应用程序运行实现。本申请一个可选的实施例中，SDK相关推送消息是由与该SDK关联的应用推送的。
本申请实施例，检测终端通知栏接收的目标消息，获取该目标消息包含的目标界面标识，根据所述目标界面标识，确定所述目标消息的类型，根据该目标消息的类型，在通知栏显示目标消息，这种方式根据目标界面标识确定该目标消息的类型，不限定目标消息的存在形式，准确率比较高。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，附图6所示通知栏消息的处理装置对应的程序可存储在终端(和/或服务器)的可读存储介质内，并被该终端(和/或服务器)中的至少一个处理器执行，以实现上述通知栏消息的处理方法，该方法包括图1-图2中方法实施例所述的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所揭露的仅为本申请较佳实施例而已，当然不能以此来限定本申请之权利范围，因此依本申请权利要求所作的等同变化，仍属本申请所涵盖的范围。

Claims (16)

  1. 一种通知栏消息的处理方法，包括：
    检测终端通知栏接收的目标消息；
    获取所述目标消息所包含的目标界面标识；
    根据所述目标界面标识，确定所述目标消息的类型；
    根据所述目标消息的类型，在所述通知栏显示所述目标消息。
  2. 如权利要求1所述的方法，其中，根据所述目标界面标识，确定所述目标消息的类型包括：
    将所述目标界面标识与预设规则库中的预设界面标识进行匹配，所述预设规则库中包括预设界面标识与消息类型之间的对应关系，将匹配一致的预设界面标识对应的消息类型确定为所述目标消息的类型。
  3. 如权利要求2所述的方法，其中，每个所述对应关系为第一对应关系或者第二对应关系；
    如果所述目标界面标识与第一对应关系的预设界面标识匹配，确定所述目标消息是终端所安装应用的推送消；
    如果所述目标界面标识与第二对应关系的预设界面标识匹配，确定所述目标消息是终端所集成的软件开发工具包SDK的推送消息。
  4. 如权利要求1所述的方法，其中，所述检测终端通知栏接收的目标消息之前，还包括：
    获取终端安装的至少一个应用；
    将所述至少一个应用的应用标识发送至服务器，以使所述服务器组建预设规则库，所述预设规则库包含所述至少一个应用中每个应用的至少一个第一对应关系以及所述至少一个应用中多个应用关联的SDK的第二对应关系。
  5. 如权利要求1所述的方法，
    其中，获取所述目标消息所包含的目标界面标识之前，还包括：
    获取推送所述目标消息的目标应用的目标标识；
    判断预设规则库中是否存在与所述目标标识匹配的应用标识；
    若存在，则根据所述匹配的应用标识确定与所述目标消息匹配的消息标识，将该匹配的消息标识对应的消息类型确定为所述目标消息的类型；
    若不存在，则获取所述目标消息所包含的目标界面标识。
  6. 如权利要求4所述的方法，其中，若所述目标界面标识与所述预设规则库的所述第二对应关系中的预设界面标识匹配，所述方法还包括：
    若检测到用户对所述目标消息的禁止推送指令，则确定与所述第二对应关系中的SDK关联的多个应用，并控制所述多个应用禁止推送所述目标消息。
  7. 如权利要求1-6任意一项所述的方法，其中，所述根据所述目标消息的类型，在所述通知栏显示所述目标消息之前，还包括：
    确定所述目标消息的类型对应的显示优先级，所述显示优先级包括高优先级或者低优先级，
    所述根据所述目标消息的类型，在所述通知栏显示所述目标消息，包括：
    若所述目标消息的类型对应的显示优先级为低优先级，则将所述目标消息与其它消息合并折叠显示于所述通知栏，所述其它消息的类型与所述目标消息的类型相同；
    若所述目标消息的类型对应的显示优先级为高优先级，则将所述目标消息直接显示于所述通知栏。
  8. 一种通知栏消息的处理装置，包括：
    检测模块，用于检测终端通知栏接收的目标消息；
    第一获取模块，用于获取所述目标消息所包含的目标界面标识；
    第一确定模块，用于根据所述目标界面标识，确定所述目标消息的类型；
    显示模块，用于根据所述目标消息的类型，在所述通知栏显示所述目标消息。
  9. 如权利要求8所述的装置，其中，根据所述目标界面标识，确定所述目标消息的类型包括：
    将所述目标界面标识与预设规则库中的预设界面标识进行匹配，所述预设规则库中包括预设界面标识与消息类型之间的对应关系，将匹配一致的预设界面标识对应的消息类型确定为所述目标消息的类型。
  10. 如权利要求8所述的装置，其中，每个所述对应关系为第一对应关系或者第二对应关系；
    如果所述目标界面标识与第一对应关系的预设界面标识匹配，确定所述目标消息是终端所安装应用的推送消息；
    如果所述目标界面标识与第二对应关系的预设界面标识匹配，确定所述目标消息是终端所集成的软件开发工具包SDK的推送消息。
  11. 如权利要求8所述的装置，还包括：
    第二获取模块，用于获取终端安装的至少一个应用；
    发送模块，用于将所述至少一个应用的应用标识发送至服务器，以使所述服务器组建预设规则库，所述预设规则库包含所述至少一个应用中每个应用的至少一个第一对应关系以及所述至少一个应用中多个应用关联的SDK的第二对应关系。
  12. 如权利要求8所述的装置，还包括：
    第三获取模块，用于获取推送所述目标消息的目标应用的目标标识；
    判断模块，用于判断预设规则库中是否存在与所述目标标识匹配的应用标识；
    第二确定模块，用于若存在，则根据所述匹配的应用标识确定与所述目标消息的匹配的消息标识，将该匹配的消息标识对应的消息类型确定为所述目标消息的类型；
    所述第一获取模块，具体用于若不存在，则获取所述目标消息所包含的目 标界面标识。
  13. 如权利要求11所述的装置，其中，若所述目标界面标识与所述预设规则库的所述第二对应关系中的预设界面标识匹配，所述装置还包括：
    控制模块，用于若检测到用户对所述目标消息的禁止推送指令，则确定与所述第二对应关系中的SDK关联的多个应用，并控制所述多个应用禁止推送所述目标消息。
  14. 如权利要求8-13任意一项所述的装置，其中，所述装置还包括：
    第四获取模块，用于确定所述目标消息的类型对应的显示优先级，所述显示优先级包括高优先级或者低优先级；
    所述显示模块具体用于若所述目标消息的类型对应的显示优先级为低优先级，则将所述目标消息与其它消息合并折叠显示于所述通知栏，所述其它消息的类型与所述目标消息的类型相同；
    若所述目标消息的类型对应的显示优先级为高优先级，则将所述目标消息直接显示于所述通知栏。
  15. 一种通知栏消息的处理装置，包括：
    一个或多个处理器；和
    存储器，所述存储器存储程序指令，所述指令当由处理器执行时配置所述装置执行根据权利要求1-7中任一项所述的方法。
  16. 一种计算机可读存储介质，存储有程序指令，所述指令当由计算装置的处理器执行时配置所述装置执行根据权利要求1-7中任一项所述的方法。
PCT/CN2017/085435 2016-05-24 2017-05-23 一种通知栏消息的处理方法及装置 WO2017202281A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/982,495 US11095739B2 (en) 2016-05-24 2018-05-17 Notification column message processing method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610349340.4 2016-05-24
CN201610349340.4A CN107426079B (zh) 2016-05-24 2016-05-24 一种通知栏消息的处理方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/982,495 Continuation US11095739B2 (en) 2016-05-24 2018-05-17 Notification column message processing method and device

Publications (1)

Publication Number Publication Date
WO2017202281A1 true WO2017202281A1 (zh) 2017-11-30

Family

ID=60411083

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/085435 WO2017202281A1 (zh) 2016-05-24 2017-05-23 一种通知栏消息的处理方法及装置

Country Status (3)

Country Link
US (1) US11095739B2 (zh)
CN (1) CN107426079B (zh)
WO (1) WO2017202281A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110297621A (zh) * 2019-05-22 2019-10-01 深圳壹账通智能科技有限公司 应用消息通知管理的方法、装置、设备及存储介质
WO2019201129A1 (zh) * 2018-04-18 2019-10-24 维沃移动通信有限公司 一种通知栏消息的处理方法及移动终端
CN114125049A (zh) * 2021-11-17 2022-03-01 珠海优特电力科技股份有限公司 遥测消息处理方法、装置、设备及存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105426398A (zh) * 2015-10-29 2016-03-23 小米科技有限责任公司 信息处理方法及装置
CN106411723A (zh) * 2016-12-12 2017-02-15 郑州云海信息技术有限公司 一种消息处理方法及装置
CN107222632A (zh) * 2017-06-23 2017-09-29 北京金山安全软件有限公司 即时通信方法及装置
CN112202966B (zh) * 2018-04-13 2021-09-21 青岛海信移动通信技术股份有限公司 通讯信息的通知方法、装置及计算机可读存储介质
CN109146021A (zh) * 2018-07-19 2019-01-04 珠海格力电器股份有限公司 交互方法、装置及智能终端
CN110324432B (zh) * 2019-07-30 2021-10-01 网易（杭州）网络有限公司 应用于终端的数据处理方法、装置、介质和计算设备
CN110528198A (zh) * 2019-09-24 2019-12-03 杰克缝纫机股份有限公司 缝纫设备的控制系统及方法
CN110750204B (zh) * 2019-10-25 2021-04-02 维沃移动通信有限公司 通知栏消息显示的方法和移动终端
CN114119008A (zh) * 2020-05-07 2022-03-01 支付宝(杭州)信息技术有限公司 一种基于图形码识别的信息展示方法及装置
CN112162869A (zh) * 2020-09-09 2021-01-01 北京如影智能科技有限公司 一种消息提示方法及装置
CN112351330B (zh) * 2020-10-26 2023-06-23 深圳Tcl新技术有限公司 显示设备的留言方法、显示设备及计算机可读存储介质
CN114721747A (zh) * 2022-06-09 2022-07-08 北京搜狐新动力信息技术有限公司 一种应用程序启动方法及装置、存储介质及电子设备

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140089848A1 (en) * 2012-09-27 2014-03-27 Kaseya International Limited Data network notification bar user interface
CN103973875A (zh) * 2013-02-01 2014-08-06 腾讯科技（深圳）有限公司 移动终端通知中心推送消息处理方法和装置
CN104238878A (zh) * 2014-09-05 2014-12-24 广东欧珀移动通信有限公司 一种启动应用程序或应用程序功能的方法及装置
CN104579847A (zh) * 2015-01-22 2015-04-29 网易（杭州）网络有限公司 通信消息的监测方法和设备
CN105450505A (zh) * 2015-11-03 2016-03-30 北京金山安全软件有限公司 通知消息处理方法、装置及终端设备
CN105786313A (zh) * 2016-02-25 2016-07-20 北京金山安全软件有限公司 一种应用通知消息的显示方法及装置
CN106095463A (zh) * 2016-06-22 2016-11-09 北京金山安全软件有限公司 通知栏消息处理方法、装置和终端设备

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102333105B (zh) * 2010-07-14 2014-02-19 华为技术有限公司 业务通信的方法、系统、推送客户端和用户设备
US20120016861A1 (en) * 2010-07-16 2012-01-19 Research In Motion Limited Registration of applications and unified media search
US8723823B2 (en) * 2011-02-07 2014-05-13 Qualcomm Incorporated System and method for providing notifications on a mobile computing device
WO2015184359A2 (en) * 2014-05-30 2015-12-03 Interdigital Technology Corporation Personalized notifications for mobile applications users
CN104020926A (zh) * 2014-05-30 2014-09-03 北京金山安全软件有限公司 一种通知栏显示方法和终端
CN104238882A (zh) * 2014-09-10 2014-12-24 北京金山安全软件有限公司 通知栏的管理方法、装置及移动终端
CN104407827B (zh) * 2014-10-31 2018-01-23 广东欧珀移动通信有限公司 一种通知栏中显示消息的方法及移动终端
CN104506715B (zh) * 2014-12-05 2018-10-12 小米科技有限责任公司 通知消息显示方法及装置
CN104572942A (zh) * 2014-12-30 2015-04-29 小米科技有限责任公司 推送消息显示方法及装置
US9946436B2 (en) * 2015-02-27 2018-04-17 Appelago Inc. Interactive dynamic push notifications
CN105100483A (zh) * 2015-07-31 2015-11-25 小米科技有限责任公司 通知的设置方法、装置及终端
CN105227626B (zh) * 2015-08-25 2019-01-22 北京金山安全软件有限公司 一种内容推送方法、装置及终端
CN105162981B (zh) * 2015-09-06 2018-07-06 北京金山安全软件有限公司 终端中通知栏的管理方法、装置和终端
CN105468232B (zh) * 2015-11-11 2019-05-28 北京金山安全软件有限公司 显示通知消息的方法、装置和移动终端
US10225357B2 (en) * 2015-11-12 2019-03-05 Facebook, Inc. Compact data structures for push notifications

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140089848A1 (en) * 2012-09-27 2014-03-27 Kaseya International Limited Data network notification bar user interface
CN103973875A (zh) * 2013-02-01 2014-08-06 腾讯科技（深圳）有限公司 移动终端通知中心推送消息处理方法和装置
CN104238878A (zh) * 2014-09-05 2014-12-24 广东欧珀移动通信有限公司 一种启动应用程序或应用程序功能的方法及装置
CN104579847A (zh) * 2015-01-22 2015-04-29 网易（杭州）网络有限公司 通信消息的监测方法和设备
CN105450505A (zh) * 2015-11-03 2016-03-30 北京金山安全软件有限公司 通知消息处理方法、装置及终端设备
CN105786313A (zh) * 2016-02-25 2016-07-20 北京金山安全软件有限公司 一种应用通知消息的显示方法及装置
CN106095463A (zh) * 2016-06-22 2016-11-09 北京金山安全软件有限公司 通知栏消息处理方法、装置和终端设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019201129A1 (zh) * 2018-04-18 2019-10-24 维沃移动通信有限公司 一种通知栏消息的处理方法及移动终端
CN110297621A (zh) * 2019-05-22 2019-10-01 深圳壹账通智能科技有限公司 应用消息通知管理的方法、装置、设备及存储介质
CN114125049A (zh) * 2021-11-17 2022-03-01 珠海优特电力科技股份有限公司 遥测消息处理方法、装置、设备及存储介质
CN114125049B (zh) * 2021-11-17 2023-08-25 珠海优特电力科技股份有限公司 遥测消息处理方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN107426079B (zh) 2020-06-16
US11095739B2 (en) 2021-08-17
US20180295200A1 (en) 2018-10-11
CN107426079A (zh) 2017-12-01

Similar Documents

Publication Publication Date Title
WO2017202281A1 (zh) 一种通知栏消息的处理方法及装置
US20220156227A1 (en) Context-based file selection
US10257127B2 (en) Email personalization
US10931611B2 (en) Message propriety determination and alert presentation on a computing device
US10789078B2 (en) Method and system for inputting information
US9104768B2 (en) Person-based information aggregation
US11734366B2 (en) Automatic generation of markers based on social interaction
US10372469B2 (en) Method and device for displaying information
US10911565B2 (en) Method, device and system for associating a service account
US9559992B2 (en) System and method for updating information in an instant messaging application
US11775605B2 (en) Determining relevance of points of interest to a user
WO2019091367A1 (zh) App的推送方法、装置、电子设备及计算机可读存储介质
US20150186455A1 (en) Systems and methods for automatic electronic message annotation
US20160092441A1 (en) File Acquiring Method and Device
US10599380B2 (en) Method and system for automatically managing content in an electronic device
CN111695004B (zh) 应用程序信息处理方法、装置、计算机设备和存储介质
CN108874827B (zh) 一种搜索方法及相关装置
WO2018125331A1 (en) Techniques for enhanced pasteboard usage
WO2014176896A1 (en) System and method for updating information in an instant messaging application
WO2020000783A1 (zh) 通讯录云处理方法、装置、计算机设备及可读存储介质
CN105874874B (zh) 一种处理信息的方法及装置
CN105653533B (zh) 一种更新分类关联词集合的方法和装置
CN108306812B (zh) 一种数据处理方法以及服务器
CN114063795A (zh) 一种交互方法、装置、电子设备和存储介质
CN106469112A (zh) 一种信息处理系统、方法及电子设备

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17802127

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17802127

Country of ref document: EP

Kind code of ref document: A1