WO2016082194A1 - 消息处理方法及装置 - Google Patents
消息处理方法及装置 Download PDFInfo
- Publication number
- WO2016082194A1 WO2016082194A1 PCT/CN2014/092524 CN2014092524W WO2016082194A1 WO 2016082194 A1 WO2016082194 A1 WO 2016082194A1 CN 2014092524 W CN2014092524 W CN 2014092524W WO 2016082194 A1 WO2016082194 A1 WO 2016082194A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- privacy
- notification
- receiving
- user
- Prior art date
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 31
- 238000000034 method Methods 0.000 claims abstract description 60
- 238000012545 processing Methods 0.000 claims description 41
- 238000004891 communication Methods 0.000 abstract description 20
- 235000019580 granularity Nutrition 0.000 abstract 1
- 238000012795 verification Methods 0.000 description 53
- 230000008569 process Effects 0.000 description 21
- 230000006870 function Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 11
- 238000012546 transfer Methods 0.000 description 9
- 230000003993 interaction Effects 0.000 description 7
- 238000001514 detection method Methods 0.000 description 4
- 238000013507 mapping Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000011218 segmentation Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000005484 gravity Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 241000699666 Mus <mouse, genus> Species 0.000 description 1
- 241000699670 Mus sp. Species 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000010079 rubber tapping Methods 0.000 description 1
- 230000035945 sensitivity Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
- H04W52/0267—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by controlling user interface components
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/82—Protecting input, output or interconnection devices
- G06F21/84—Protecting input, output or interconnection devices output devices, e.g. displays or monitors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/01—Social networking
-
- 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/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- 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/06—Message adaptation to terminal or network requirements
- H04L51/063—Content adaptation, e.g. replacement of unsuitable content
-
- 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/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
-
- 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
-
- 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
- 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
- H04M1/72436—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 for text messaging, e.g. short messaging services [SMS] or e-mails
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/03—Indexing scheme relating to G06F21/50, monitoring users, programs or devices to maintain the integrity of platforms
- G06F2221/032—Protect output to user by software means
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a message processing method and apparatus.
- Android Android
- iOS iPhone OS, Apple operating system
- Windows Phone devices etc. all have the function of displaying push messages on the lock screen interface. That is, an application (such as a short message, a mailbox, an instant messaging application, etc.) installed by the user on the smart terminal may display the received push message on the lock screen of the smart terminal. After that, the user can access the application corresponding to the push message by clicking the push message entry, and then browse the entire content of the push message.
- an application such as a short message, a mailbox, an instant messaging application, etc.
- the user can access the application corresponding to the push message by clicking the push message entry, and then browse the entire content of the push message.
- various types of push messages received can be displayed on the lock screen interface, there is a risk of leaking the privacy of the user. Therefore, how to perform the display of the push message under the premise of preventing the leakage of the user's personal privacy has become a focus of attention of those skilled in the art.
- the push message there are usually two ways to display the push message.
- the first way for the iOS system, settings are made in the notification center whether each application displays a push message on the lock screen interface.
- the application set to display presents its corresponding push message on the lock screen interface of the smart terminal.
- An application that does not display is not presented with its corresponding push message on the lock screen interface of the smart terminal.
- the second way is to set the push message privacy level of the application in the API (Application Programming Interface) for Android L or the iOS system after jailbreak.
- Push messages of different applications are displayed in different ways according to the set privacy level. For example, a push message of an application with a high privacy level is not displayed on a lock screen interface, and a push message of an application with a low privacy level can be displayed on a lock screen interface.
- an embodiment of the present invention provides a message processing method and apparatus.
- the technical solution is as follows:
- a message processing method comprising:
- the first message is a private message, generating a second message according to the first message, where the second message carries a first privacy tag;
- the determining whether the first message is a private message includes:
- the generating the second message according to the first message includes:
- the determining whether the first message is a private message includes:
- the generating the second message according to the first message includes:
- the displaying, according to the first privacy label, on the notification interface includes:
- a notification preview of the second message is not displayed on the notification interface of the second device.
- a message processing method comprising:
- the first message is a privacy message, generating a second message according to the first message, where the second message does not include at least one piece of private content in the first message;
- the determining whether the first message is a private message includes:
- the generating the second message according to the first message includes:
- a message processing method comprising:
- the second device displays the notification of the second message on the notification interface, the notification preview of the second message is not displayed;
- the notification of the second message is displayed on the notification interface of the second message according to the setting of the user.
- the not displaying the notification preview of the second message includes:
- the specific content of the second message is not displayed, and only the summary notification information that does not include the specific content of the second message is displayed.
- a message processing apparatus comprising:
- a first message receiving module configured to receive a first message that is sent by the first device to the second device
- a privacy message judging module configured to determine whether the first message is a privacy message
- a second message generating module configured to: when the first message is a private message, generate a second message according to the first message, where the second message carries a first privacy tag;
- a second message sending module configured to send the second message to the second device, so that after the second device receives the second message, displaying, by the second device, the notification message on the notification interface The notification of the second message.
- the privacy message determining module is configured to determine, according to the privacy data included in the first message, that the first message is a privacy message
- the second message generating module is configured to generate the second message according to the first message, and set the first privacy tag in the second message.
- the private message determining module is configured to determine, according to the second privacy label included in the first message, that the first message is a private message.
- the second message generating module is configured to generate the second message according to the first message, and set the first privacy tag in the second message.
- the second message sending module is configured to The device sends the second message, so that the second device does not display the notification preview of the second message on the notification interface of the second device after receiving the second message.
- a message processing apparatus comprising:
- a first message receiving module configured to receive a first message that is sent by the first device to the second device
- a privacy message judging module configured to determine whether the first message is a privacy message
- a second message generating module configured to: when the first message is a private message, generate a second message according to the first message, where the second message does not include at least one piece of private content in the first message;
- a second message sending module configured to send the second message to the second device, so that the second device displays the notification of the second message on the notification interface after receiving the second message .
- the privacy message determining module is configured to determine, according to the privacy data included in the first message, that the first message is a privacy message
- the second message generating module is configured to remove at least one piece of the private content in the first message to obtain the second message.
- a message processing apparatus comprising:
- a second message receiving module configured to receive a second message sent to the second device
- a privacy tag determining module configured to determine whether the second message includes a privacy tag
- a first display module configured to: when the second message includes a privacy label, the second device does not display the notification preview of the second message when the notification of the second message is displayed on the notification interface;
- the second display module is configured to display, when the second message does not include a privacy label, a notification of the second message according to a setting of the user on a notification interface of the second message.
- the first display module is configured to not display the specific content of the second message when the notification of the second message is displayed, and only display the Summary notification information describing the specific content of the second message.
- the second message After receiving the first message sent to the second device, determining whether the first message is a privacy message; if the first message is a privacy message, generating a second message carrying the first privacy tag according to the first message Afterwards, the second message is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy label after receiving the second message. After the second message is received by the second device, the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- FIG. 1 is a flowchart of a message processing method according to an embodiment of the present invention
- FIG. 2 is a flowchart of a message processing method according to an embodiment of the present invention.
- FIG. 3 is a flowchart of a message processing method according to an embodiment of the present invention.
- FIG. 4 is a flowchart of a message processing method according to an embodiment of the present invention.
- FIG. 5 is a schematic diagram of an application server registration privacy data according to an embodiment of the present invention.
- FIG. 6 is a flowchart of a message processing method according to an embodiment of the present invention.
- FIG. 7 is a flowchart of a message processing method according to an embodiment of the present invention.
- FIG. 8 is a schematic diagram of a push service registration according to an embodiment of the present invention.
- FIG. 9 is a flowchart of a message processing method according to an embodiment of the present invention.
- FIG. 10 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present invention.
- FIG. 11 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present invention.
- FIG. 12 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present disclosure.
- FIG. 13 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
- FIG. 14 is a schematic structural diagram of an application server according to an embodiment of the present invention.
- FIG. 1 is a flowchart of a message processing method according to an embodiment of the present invention.
- the method process provided by the embodiment of the present invention includes:
- the first device is a message sender
- the second device is a message receiver
- Step 102 Determine whether the first message is a privacy message; if the first message is a privacy message, perform step 102; if the first message is a non-private message, perform step 104 directly.
- the first message is a privacy message
- the application server determines whether the first message is a private message; if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- determining whether the first message is a privacy message includes:
- generating a second message according to the first message includes:
- determining whether the first message is a privacy message includes:
- generating a second message according to the first message includes:
- displaying the notification of the second message on the notification interface according to the first privacy label includes:
- the notification preview of the second message is not displayed on the notification interface of the second device.
- FIG. 2 is a flowchart of a message processing method according to an embodiment of the present invention.
- the method process provided by the embodiment of the present invention includes:
- step 202 Determine whether the first message is a privacy message; if the first message is a privacy message, perform step 203; if the first message is a non-private message, perform step 204 directly.
- the first message is a privacy message
- the application server determines whether the first message is a private message; if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- the determining whether the first message is a privacy message includes:
- the generating the second message according to the first message includes:
- FIG. 3 is a flowchart of a message processing method according to an embodiment of the present invention.
- the method flow provided by the embodiment of the present invention includes:
- step 302. Determine whether the second message includes a privacy label. If the second message includes a privacy label, perform step 303. If the second message does not include a privacy label, perform step 304.
- the notification preview of the second message is not displayed.
- the notification of the second message is displayed according to the setting of the user on the notification interface of the second message.
- the application server determines whether the first message is a private message; if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- the notification preview of the second message is not displayed, including:
- the specific content of the second message is not displayed, and only the display does not include the first Summary notification information of the specific content of the second message.
- FIG. 4 is a flowchart of a message processing method according to an embodiment of the present invention.
- the interaction subject is a first device, a second device, an application server, and a push server.
- the method includes a specified user identifier information and a first message, and the second message does not carry the first privacy label.
- the method process provided by the embodiment of the present invention includes:
- the first device sends a data packet to the application server, where the data packet includes at least specified user identification information and a first message.
- the first device refers to the sender and the sender, and may be a mobile terminal such as a smart phone or a tablet computer, or a fixed receiving device such as a personal computer, or a social application or an instant messaging application. server.
- the type of the first device is not specifically limited in the embodiment of the present invention.
- the specified user identification information is used to indicate the recipient of the first message, which may be a phone number, a login name of an application, a mailbox, etc., and the form of the specified user identification information is also not specifically limited in the embodiment of the present invention.
- the data package may include other content in addition to the specified user identification information and the first message.
- the privacy label, the data packet sending time, and the like are not specifically limited in this embodiment of the present invention.
- the data may be sent in a wired manner or in a wireless manner, which is not specifically limited in the embodiment of the present invention.
- the embodiment of the present invention further includes a process for the application server to perform privacy registration, and the specific process may be divided into the following five small steps.
- the second device sends the specified user identification information to the push server.
- the second device refers to the message receiver.
- the second step after receiving the specified user identification information, the push server calculates the specified registration identity corresponding to the specified user identity information, and sends the specified registration identity to the second device.
- the specified registration identity can be a string containing only letters, or a number
- the character string and the like are mixed, and the embodiment of the present invention does not specifically limit the form of the designated registration identity.
- the second device After the third device receives the specified registration identity, the second device sets a correspondence between the specified user identity and the specified registration identity, and sends a correspondence between the specified user identity information and the specified registration identity to the application server. .
- the second device when the second device sets the correspondence between the specified user identity and the specified registration identity, the second device may generate a corresponding entry as shown in the first row in the following table, that is, the second device generates only the table.
- a single entry in 1 (a line).
- the entire correspondence table shown in Table 1 is composed of corresponding entries sent by multiple devices.
- the application server After receiving the corresponding entry between the specified user identity and the specified registration identity sent by the second device, the application server inserts the entry into the table shown in Table 1 below.
- Registration identity User identification information A Specify registration identity A ?? .
- the second device acquires the privacy data set by the user, and sends the privacy data and the corresponding specified user identifier information to the application server.
- the privacy data can be set by the user himself according to the following rules:
- Rule 1 For any application (for example, communication applications, SMS, WeChat, email, etc.), the user can set the application as private data at the application level, and the push message of the application is always processed according to the privacy message. The specific content of the push message is not displayed when unlocking.
- any application for example, communication applications, SMS, WeChat, email, etc.
- Rule 2 For contacts (eg, privacy contacts, bank customer service, Alipay, etc.), the user can set the above contacts as private data at the contact level, and the contacts can match the application address book and system communication. Record, email contact address book obtained. Messages sent by this contact, whether sent by other communication tools such as email or WeChat, are processed according to the privacy message. The specific content of the push message is not displayed when it is not unlocked.
- contacts eg, privacy contacts, bank customer service, Alipay, etc.
- the user can set the above contacts as private data at the contact level, and the contacts can match the application address book and system communication. Record, email contact address book obtained. Messages sent by this contact, whether sent by other communication tools such as email or WeChat, are processed according to the privacy message. The specific content of the push message is not displayed when it is not unlocked.
- Rule 3 For keywords (eg, transaction amount, receipt of payment receipt, SMS verification code, etc.), the user can set the keyword as private data, and the above keywords can be automatically recognized by the system responsible for private message processing.
- the push message containing the above keywords is always processed according to the privacy message, and the specific content of the push message is not displayed when not unlocked.
- Rule 4 For certain time periods (eg, working hours, party hours, etc.) of the user equipment, the user equipment detects the user and the second through the bound wearable device at certain locations (eg, company, outside, etc.) The location relationship of the device, through the connection relationship of the bound vehicle, smart home and other devices, select different privacy processing methods for the push message. The above-mentioned time period, location, and bound wearable device may be separately judged, and the above factors may also be combined.
- the second device obtains the set privacy data, and uploads the set privacy data together with the specified user identification information to the application server, so as to facilitate the application server to store.
- the application server stores a correspondence between the specified user identity and the specified registration identity, and the correspondence between the privacy data and the specified user identity information.
- the application server may store the foregoing two types of correspondences in a storage medium such as a memory or a flash memory.
- a storage medium such as a memory or a flash memory.
- the embodiment of the present invention does not specifically limit the type of the storage medium.
- the application server determines the designated registration identity according to the correspondence between the specified user identity information, the user identity information, and the registration identity.
- the application server stores a correspondence between the user identification information and the registration identity.
- the application server can store a large number of correspondences, including user identification information and registration identity sent by thousands of receiving devices.
- the application server determines the designated registration identity according to the correspondence between the specified user identification information, the user identification information, and the registration identity
- the application may be implemented in the following manner:
- the registration identity is determined as the specified registration identity.
- the application server determines, according to the correspondence between the specified user identifier information, the stored private data, and the user identifier information, whether the first message is a privacy message.
- the application server since the application server has stored the correspondence between the private data and the user identification information in the foregoing step 401, the application server may receive the data packet sent by the first device according to the specified user.
- the identification information determines whether the first message is a privacy message.
- the privacy message refers to a message that covers private data.
- the application server determines whether the first message is a private message according to the correspondence between the specified user identification information, the stored private data, and the user identification information, and may be implemented in the following manner:
- the first message can be processed by word segmentation to obtain each participle; each participle is separately performed with private data. Alignment; if any participle matches one of the keywords in the privacy data, then the first message is determined to be a private message.
- the second device After the second device is connected to the network, the second device sends the stored registration identity to the push server; after receiving the registration identity, the push server verifies whether the registration identity is legal, and obtains the verification result; after that, returns the verification result to Second device.
- the reason why the push server performs verification on the second device is to determine whether the registered identity identifier stored by the second device is personally granted before the push server. If the registration identity is calculated by the push server and returned to the second device, the registration identity is verified to be valid, and the verification result including the legal information is obtained; and the verification result is returned to the second device. If the registration identity non-pushing server calculates and returns to the second device in advance, verifying that the registration identity is illegal, obtaining a verification result including the illegal information; returning the verification result to the second device, prompting the second device to register the identity Identity verification failed.
- the application server determines that the first message is a privacy message, generate a second message according to the first message, where the second message does not include at least one piece of private content in the first message.
- the method may be implemented by: removing at least one piece of the private content in the first message to obtain the second message.
- the method may be implemented by: removing at least one piece of the private content in the first message to obtain the second message.
- generation manners may be adopted in addition to the manner of generating the second message, which is not specifically limited in the embodiment of the present invention.
- the first message when the first message is a privacy message, the first message may include a plurality of more sensitive private content.
- the first message when the first message is a delivery message of an online payment verification code, the first message may include a plurality of privacy contents such as an amount, a bank card number, and a verification code.
- the partial privacy content in the first message may be replaced, hidden, or modified, so that the second message includes a part of the private content in the first message;
- all the private content in the first message is replaced, hidden or modified, so that the second message does not include any private content in the first message, and the second message has no sensitivity. vocabulary.
- the second message when the second message does not include part of the private content in the first message, the second message may be in the form of “XX gives you a transfer of XXX yuan”, “XX gives you a transfer”, and the like; when the second message does not include the first message, In the case of any private content, the second message may be in the form of “you have a new transfer record” and the like, which is not specifically limited in the embodiment of the present invention.
- the application server generates a data push request according to the specified registration identity and the second message.
- the application server sends the second message to the push server
- the application server After obtaining the second message, the application server also needs to generate a data push request.
- the data push request includes at least a specified registration identity and a second message.
- the data push request may include other content in addition to the above content.
- the generation time of the data push request and the like are not specifically limited in the embodiment of the present invention.
- the application server sends a data push request to the push server.
- the application server when it sends the data push request, it may send the data push request in a wireless or wired manner; or directly send the data push request in a wireless or wired manner.
- the embodiment of the invention is not specifically limited thereto.
- the push server After receiving the data push request, the push server sends the data push request to the second device according to the correspondence between the specified registration identity, the user identifier information, and the registration identity.
- the push server can determine the corresponding designated user according to the specified registration identity after receiving the data push request. Identification information. Further, based on the specified user identification information, it can be determined to which receiving device the second message is transmitted.
- the pushing server sends the data push request to the second device according to the correspondence between the specified registration identity, the user identifier information, and the registration identity, which may be implemented in the following manner:
- the second device After receiving the second message, the second device displays a notification of the second message on the notification interface.
- the notification interface may be a lock screen interface, and may also be a system notification interface, an application main interface, a terminal desktop, and the like in addition to the lock screen interface. limited.
- the second device may directly display the second message on the lock screen interface if it is currently in the lock screen state.
- the notification of the second message can be in the form of "XX gives you a transfer”, "You have a new message”, “You have a new transfer record”, etc., so even if others see the notification, there will be no leaking users.
- the notification preview of the second message may not be displayed on the notification interface, that is, no relevant sensitive vocabulary is displayed. Only the summary notification message in the form of "you have a new message” and “you have a new transfer record” is displayed, which is not specifically limited in the embodiment of the present invention.
- the unlocking prompt information may also be displayed on the lock screen interface to remind the user to perform an unlocking operation to view the details of the second message.
- the second device After the user unlocks the second device, the second device sends a complete push message request to the application server. After receiving the complete push message request, the application server sends a complete second message containing the privacy message to the second device.
- the application server determines whether the first message is a private message; if the first message is a private message, generating the first message according to the first message. a second message of the privacy tag; afterwards, sending the second message to the second device, so that the second device displays the second message on the notification interface according to the first privacy tag after receiving the second message Notification of the message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- FIG. 6 is a flowchart of a message processing method according to an embodiment of the present invention.
- the interaction subject is a first device, a second device, an application server, and a push server.
- the method includes the following steps:
- the first device sends a data packet to the application server, where the data packet includes at least specified user identification information and a first message.
- the first device refers to a message sender, and may be a mobile terminal such as a smart phone or a tablet computer, or a fixed receiving device such as a personal computer, or a server for a social application or an instant messaging application.
- the type of the first device is not specifically limited in the embodiment of the present invention.
- the specified user identification information is used to indicate the recipient of the first message, which may be a phone number, a login name of an application, a mailbox, etc., and the form of the specified user identification information is also not specifically limited in the embodiment of the present invention.
- the data package may include other content in addition to the specified user identification information and the first message.
- the privacy label, the data packet sending time, and the like are not specifically limited in this embodiment of the present invention.
- the data may be sent in a wired manner or in a wireless manner, which is not specifically limited in the embodiment of the present invention.
- the embodiment of the present invention further includes a process for the application server to perform privacy registration, and the specific process may be divided into the following five small steps.
- the second device sends the specified user identification information to the push server.
- the second device refers to the message receiver.
- the second step after receiving the specified user identification information, the push server calculates the specified registration identity corresponding to the specified user identity information, and sends the specified registration identity to the second device.
- the specified registration identity may be a string containing only letters, or a string of numbers and letters, and the like.
- the embodiment of the present invention does not specifically limit the form of the designated registration identity.
- the second device After the third device receives the specified registration identity, the second device sets a correspondence between the specified user identity and the specified registration identity, and sends a correspondence between the specified user identity information and the specified registration identity to the application server. .
- the second device may generate the corresponding entry as shown in the first row in Table 1, that is, the second device generates only the table.
- a single entry in 1 (a line).
- the entire correspondence table shown in Table 1 is composed of corresponding entries sent by multiple devices.
- the second device acquires the privacy data set by the user, and sends the privacy data and the corresponding specified user identifier information to the application server.
- the privacy data can be set by the user himself according to the following rules:
- Rule 1 For any application (for example, communication applications, SMS, WeChat, email, etc.), the user can set the application as private data at the application level, and the push message of the application is always processed according to the privacy message. The specific content of the push message is not displayed when unlocking.
- any application for example, communication applications, SMS, WeChat, email, etc.
- Rule 2 For contacts (eg, privacy contacts, bank customer service, Alipay, etc.), the user can set the above contacts as private data at the contact level, and the contacts can match the application address book and system communication. Record, email contact address book obtained. Messages sent by this contact, whether sent by other communication tools such as email or WeChat, are processed according to the privacy message. The specific content of the push message is not displayed when it is not unlocked.
- contacts eg, privacy contacts, bank customer service, Alipay, etc.
- the user can set the above contacts as private data at the contact level, and the contacts can match the application address book and system communication. Record, email contact address book obtained. Messages sent by this contact, whether sent by other communication tools such as email or WeChat, are processed according to the privacy message. The specific content of the push message is not displayed when it is not unlocked.
- Rule 3 For keywords (eg, transaction amount, receipt of payment receipt, SMS verification code, etc.), the user can set the keyword as private data, and the above keywords can be automatically recognized by the system responsible for private message processing.
- the push message containing the above keywords is always processed according to the privacy message, and the specific content of the push message is not displayed when not unlocked.
- Rule 4 For certain time periods (eg, working hours, party hours, etc.) of the user equipment, the user equipment detects the user and the second through the bound wearable device at certain locations (eg, company, outside, etc.) The location relationship of the device, through the connection relationship of the bound vehicle, smart home and other devices, select different privacy processing methods for the push message.
- the above-mentioned time period, location, and bound wearable device may be separately judged, and the above factors may also be combined for judgment.
- the second device obtains the set privacy data, and uploads the set privacy data together with the specified user identification information to the application server, so as to facilitate the application server to store.
- the application server stores a correspondence between the specified user identity and the specified registration identity, and the correspondence between the privacy data and the specified user identity information.
- the application server may store the foregoing two types of correspondences in a storage medium such as a memory or a flash memory.
- a storage medium such as a memory or a flash memory.
- the embodiment of the present invention does not specifically limit the type of the storage medium.
- the application server determines the designated registration identity according to the correspondence between the specified user identity information, the user identity information, and the registration identity.
- the application server stores a correspondence between the user identification information and the registration identity.
- the application server can store a large number of correspondences, including user identification information and registration identity sent by thousands of receiving devices.
- the application server determines the designated registration identity according to the correspondence between the specified user identification information, the user identification information, and the registration identity
- the application may be implemented in the following manner:
- the application server determines whether the first message is a privacy message. When the first message is a privacy message, performing the following step 604.
- the application server when determining whether the first message is a private message, the application server may be implemented in the following manner:
- Determining whether the first message is a privacy message according to whether the first message includes the privacy data determining that the first message is a privacy message when the first message includes the privacy data; determining the first when the first message does not include the privacy data
- the message is a non-private message.
- the application server may determine whether the first message is determined according to the specified user identification information.
- a privacy message that includes private content.
- the application server determines whether the first message is a private message according to the correspondence between the specified user identification information, the stored private data, and the user identification information, and may be implemented in the following manner:
- the first message can be processed by word segmentation to obtain each participle; each participle is separately performed with private data. Alignment; if any participle matches one of the keywords in the privacy data, then the first message is determined to be a private message.
- the second device After the second device is connected to the network, the second device sends the stored registration identity to the push server; after receiving the registration identity, the push server verifies whether the registration identity is legal, and obtains the verification result; after that, returns the verification result to Second device.
- the reason why the push server performs verification on the second device is to determine whether the registered identity identifier stored by the second device is personally granted before the push server. If the registration identity is calculated by the push server and returned to the second device, the registration identity is verified to be valid, and the verification result including the legal information is obtained; and the verification result is returned to the second device. If the registration identity non-pushing server calculates and returns to the second device in advance, verifying that the registration identity is illegal, obtaining a verification result including the illegal information; returning the verification result to the second device, prompting the second device to register the identity Identity verification failed.
- the application server determines that the first message is a privacy message, generate a second message according to the first message, where the second message carries the first privacy tag.
- the application server when the application server generates the second message according to the first message, the application server may be implemented in the following manner:
- the first privacy tag is inserted in the second message to obtain the second message.
- different privacy tags can be set for the privacy level of the privacy message. For example, set privacy and privacy levels to two different levels of privacy.
- the privacy label with the highest privacy level can be set, that is, the secret privacy label; the push message sent for an application can be set with a privacy level.
- a weak privacy label, that is, a private privacy label is not specifically limited in this embodiment of the present invention.
- the application server when the application server inserts the first privacy label in the second message, the insertion of the header of the second message may also be performed at the end of the second message, or may be implemented by marking or setting a certain preset data bit in the second message, which is not specifically limited in this embodiment of the present invention. .
- the first privacy tag may be set to a specific field in the second message content, and may be one byte, one bit, or any length; the location may be located at the beginning, the end, or the middle of the second message. As long as it can be recognized by the recipient of the message.
- the embodiment of the present invention does not specifically limit the form and location of the first privacy tag.
- the application server sends the second message to the push server
- the application server After obtaining the second message, the application server also needs to generate a data push request.
- the data push request includes at least a specified registration identity and a second message.
- the data push request may include other content in addition to the above content.
- the generation time of the data push request and the like are not specifically limited in the embodiment of the present invention.
- the application server sends a data push request to the push server.
- the application server when it sends the data push request, it may send the data push request in a wireless or wired manner; or directly send the data push request in a wireless or wired manner.
- the embodiment of the invention is not specifically limited thereto.
- the push server After receiving the data push request, the push server sends the data push request to the second device according to the correspondence between the specified registration identity, the user identifier information, and the registration identity.
- the push server can determine the corresponding designated user according to the specified registration identity after receiving the data push request. Identification information. Further, according to the specified user identification information It can be determined to which receiving device the second message is sent.
- the pushing server sends the data push request to the second device according to the correspondence between the specified registration identity, the user identifier information, and the registration identity, which may be implemented in the following manner:
- the second device After receiving the second message, the second device displays the notification of the second message on the notification interface according to the first privacy label.
- the notification preview of the second message is not displayed on the notification interface of the second device.
- the notification preview that does not display the second message refers to: when the notification of the second message is displayed, the specific content of the second message is not displayed, and only the summary notification information of the specific content that does not include the second message is displayed.
- the second device after receiving the second message, the second device checks whether the second message contains a privacy label. Because the second message includes the first privacy label at this time, when the second device displays the notification of the second message, the second message needs to be processed first.
- the second message may include a plurality of more sensitive privacy content.
- the second message when the second message is a delivery message of an online payment verification code, the second message may include a plurality of privacy contents such as an amount, a bank card number, and a verification code.
- the partial privacy content in the second message may be replaced, hidden or modified, so that the second message only includes part of the privacy content when displayed on the notification interface;
- the entire privacy content is replaced, hidden or modified so that the second message does not contain any private content when displayed on the notification interface, and there is no sensitive vocabulary in the second message.
- the notification preview of the second message may not be displayed on the notification interface, that is, no relevant sensitive vocabulary is displayed. Only the summary notification message in the form of "you have a new message” and “you have a new transfer record” is displayed, which is not specifically limited in the embodiment of the present invention.
- the second device may perform different message notification display for different levels of privacy tags for different levels of privacy tags in the second message. For example, if the second message contains the highest level of privacy tag, it will only be displayed to the user "you have a new message", the sender of the message, the application used by the sender, the sending time, the content, etc. are not displayed, and the user uses the first
- the second device itself checks; if the second message contains a privacy tag with a slightly weaker privacy level, it displays to the user "you have a WeChat message from Zhang San", but hides the specific content of the message; if the second message does not contain any privacy tags A full notification of the second message can then be displayed.
- other display processing manners may be adopted in addition to the manner of the above-mentioned privacy label display processing, which is not specifically limited in the embodiment of the present invention.
- the unlocking prompt information may also be displayed on the lock screen interface to remind the user to perform the unlocking operation for message viewing.
- the application server determines whether the first message is a private message; if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- the privacy registration of the above two embodiments is on the application server side, and the privacy settings of the user on different devices can be synchronized.
- the same user's privacy message receiving settings can be synchronized between multiple devices of the user.
- User privacy settings between different applications for the same contact can be synchronized between multiple devices and multiple applications.
- FIG. 7 is a flowchart of a message processing method according to an embodiment of the present invention.
- the interaction subject is the first Device, second device, application server, and push server.
- the method includes a specified user identifier information, a first message, and a second privacy label, and the second message carries the first privacy label as an example.
- the method according to the embodiment of the present invention includes:
- the first device sends a data packet to the application server, where the data packet includes at least specified user identification information, a first message, and a second privacy label.
- the first device refers to a message sender, which may be a mobile terminal such as a smart phone or a tablet computer, or a fixed receiving device such as a personal computer, or a server for a social application or an instant messaging application.
- the type of the first device is not specifically limited in the embodiment of the present invention.
- the specified user identification information is used to indicate the recipient of the first message, which may be a phone number, a login name of an application, a mailbox, etc., and the form of the specified user identification information is also not specifically limited in the embodiment of the present invention.
- the data package may include other content in addition to the specified user identification information, the first message, and the second privacy tag.
- the data packet sending time and the like are not specifically limited in this embodiment of the present invention.
- the data may be sent in a wired manner or in a wireless manner, which is not specifically limited in the embodiment of the present invention.
- the first device before the sending of the data packet, the first device further includes the step of acquiring the privacy data set by the user.
- the privacy data can be set by the user himself according to the following rules:
- Rule 1 For any application (for example, communication applications, SMS, WeChat, email, etc.), the user can set the application as private data at the application level, and the push message of the application is always processed according to the privacy message. The specific content of the push message is not displayed when unlocking.
- any application for example, communication applications, SMS, WeChat, email, etc.
- Rule 2 For contacts (eg, privacy contacts, bank customer service, Alipay, etc.), the user can set the above contacts as private data at the contact level, and the contacts can match the application address book and system communication. Record, email contact address book obtained. Messages sent by this contact, whether sent by other communication tools such as email or WeChat, are processed according to the privacy message. The specific content of the push message is not displayed when it is not unlocked.
- contacts eg, privacy contacts, bank customer service, Alipay, etc.
- the user can set the above contacts as private data at the contact level, and the contacts can match the application address book and system communication. Record, email contact address book obtained. Messages sent by this contact, whether sent by other communication tools such as email or WeChat, are processed according to the privacy message. The specific content of the push message is not displayed when it is not unlocked.
- Rule 3 For keywords (eg, transaction amount, receipt of payment receipt, SMS verification code, etc.), the user can set the keyword as private data, and the above keywords can be handled by the privacy information department. The system is automatically identified. The push message containing the above keywords is always processed according to the privacy message, and the specific content of the push message is not displayed when not unlocked.
- keywords eg, transaction amount, receipt of payment receipt, SMS verification code, etc.
- Rule 4 For certain time periods (eg, working hours, party hours, etc.) of the user equipment, the user equipment detects the user and the second through the bound wearable device at certain locations (eg, company, outside, etc.) The location relationship of the device, through the connection relationship of the bound vehicle, smart home and other devices, select different privacy processing methods for the push message. The above-mentioned time period, location, and bound wearable device may be separately judged, and the above factors may also be combined.
- the second device obtains the set privacy data, and uploads the set privacy data and the specified user identification information to the application server to facilitate the application server to store.
- different privacy tags may be set for the privacy level of the privacy message.
- the second privacy tag with the highest privacy level can be set; the push message sent for an application can set the privacy level to be weaker.
- the second privacy label and the like are not specifically limited in the embodiment of the present invention. It can be set by the user and stored in the application server in advance, or can be automatically set by the system, which is not specifically limited in the embodiment of the present invention.
- the first device when the first device inserts the second privacy tag in the first message, the first device may be inserted in the header of the first message, or inserted in the tail of the first message, or may be in the first message.
- the implementation of this embodiment of the present invention is not specifically limited.
- the second privacy tag may be set to a specific field in the first message content, and may be one byte, one bit, or any length; the location may be located at the beginning, the end, or the middle of the first message. As long as it can be recognized by the recipient of the message.
- the embodiment of the present invention does not specifically limit the form and location of the second privacy tag.
- the embodiment of the present invention further includes a process of pushing service registration, and the specific process may be divided into the following four small steps.
- the second device sends the specified user identification information to the push server.
- the second device refers to the message receiver.
- the second step after receiving the specified user identification information, the push server calculates the specified registration identity corresponding to the specified user identity information, and sends the specified registration identity to the second device.
- the specified registration identity may be a string containing only letters, or a string of numbers and letters, and the like.
- the embodiment of the present invention does not specifically limit the form of the designated registration identity.
- the second device After the third device receives the specified registration identity, the second device sets a correspondence between the specified user identity and the specified registration identity, and sends a correspondence between the specified user identity information and the specified registration identity to the application server. .
- the second device may generate the corresponding entry as shown in the first row in Table 1, that is, the second device generates only the table.
- a single entry in 1 (a line).
- the entire correspondence table shown in Table 1 is composed of corresponding entries sent by multiple devices.
- the application server stores a correspondence between the specified user identity and the specified registration identity.
- the application server may store the foregoing relationship in a storage medium such as a memory or a flash memory.
- a storage medium such as a memory or a flash memory.
- the embodiment of the present invention does not specifically limit the type of the storage medium.
- the application server determines, according to the correspondence between the specified user identification information, the user identifier information, and the registration identity, the specified registration identity.
- the application server stores a correspondence between the user identification information and the registration identity. As the processing power of the server increases, the application server can store a large number of corresponding Relationships, including user identification information and registration identities sent by thousands of receiving devices.
- the application server determines the designated registration identity according to the correspondence between the specified user identification information, the user identification information, and the registration identity
- the application may be implemented in the following manner:
- the registration identity is determined as the specified registration identity.
- the second device After the second device is connected to the network, the second device sends the stored registration identity to the push server; after receiving the registration identity, the push server verifies whether the registration identity is legal, and obtains the verification result; after that, returns the verification result to Second device.
- the reason why the push server performs verification on the second device is to determine whether the registered identity identifier stored by the second device is personally granted before the push server. If the registration identity is calculated by the push server and returned to the second device, the registration identity is verified to be valid, and the verification result including the legal information is obtained; and the verification result is returned to the second device. If the registration identity non-pushing server calculates and returns to the second device in advance, verifying that the registration identity is illegal, obtaining a verification result including the illegal information; returning the verification result to the second device, prompting the second device to register the identity Identity verification failed.
- the application server determines whether the first message is a privacy message. When the first message is a privacy message, performing the following step 704.
- the application server when determining whether the first message is a private message, the application server may be implemented in the following manner:
- Whether the first message is a privacy message is determined according to whether the second message is included in the first message.
- the first message is determined to be a private message, and the following step 704 is performed; when the second message is not included in the first message, it is determined that the first message is not a private message.
- the application server determines that the first message sent by the first device is a privacy message, generate a second message according to the first message, where the second message carries the first privacy tag.
- the application server when the application server generates the second message according to the first message, the application server may adopt the following method:
- the first privacy tag may be set to a specific field in the second message content, and may be one byte, one bit, or any length; the location may be located at the beginning, the end, or the middle of the second message. As long as it can be recognized by the recipient of the message.
- the embodiment of the present invention does not specifically limit the form and location of the second privacy tag.
- the first privacy tag is also set in the second message because there may be a case where the first device and the application server use The relevant protocols may be different, so the first privacy tag may be a second privacy tag after being formatted or otherwise processed.
- the substantive role of the first privacy tag and the second privacy tag are the same, and all the privacy messages are marked. The format has changed only on different devices.
- the application server generates a data push request according to the specified registration identity and the second message.
- the application server sends the second message to the push server
- the application server After obtaining the second message, the application server also needs to generate a data push request.
- the data push request includes at least a specified registration identity and a second message.
- the data push request may include other content in addition to the above content.
- the generation of data push requests The time and the like are not specifically limited in the embodiment of the present invention.
- the application server sends a data push request to the push server.
- the application server when it sends the data push request, it may send the data push request in a wireless or wired manner; or directly send the data push request in a wireless or wired manner.
- the embodiment of the invention is not specifically limited thereto.
- the push server After receiving the data push request, the push server sends the data push request to the second device according to the correspondence between the specified registration identity, the user identifier information, and the registration identity.
- the push server can determine the corresponding designated user according to the specified registration identity after receiving the data push request. Identification information. Further, based on the specified user identification information, it can be determined to which receiving device the second message is transmitted.
- the pushing server sends the data push request to the second device according to the correspondence between the specified registration identity, the user identifier information, and the registration identity, which may be implemented in the following manner:
- the second device After receiving the data push request, the second device displays the notification of the second message on the notification interface according to the first privacy label.
- the notification preview of the second message is not displayed on the notification interface of the second device.
- the notification preview that does not display the second message refers to: when the notification of the second message is displayed, the specific content of the second message is not displayed, and only the summary notification information of the specific content that does not include the second message is displayed.
- the second device after receiving the second message, the second device checks whether the second message is in the second message. Contains a privacy label. Because the second message includes the first privacy label at this time, when the second device displays the notification of the second message, the second message needs to be processed first.
- the second message may include a plurality of more sensitive privacy content. For example, when the second message is a delivery message of an online payment verification code, the second message may include a plurality of privacy contents such as an amount, a bank card number, and a verification code.
- the partial privacy content in the second message may be replaced, hidden or modified, so that the second message only includes part of the privacy content when displayed on the notification interface;
- the entire privacy content is replaced, hidden or modified so that the second message does not contain any private content when displayed on the notification interface, and there is no sensitive vocabulary in the second message.
- the notification preview of the second message may not be displayed on the notification interface, that is, no relevant sensitive vocabulary is displayed. Only the summary notification information in the form of "you have a new message”, “you have a new transfer record”, and the like are displayed, and the embodiment of the present invention does not specifically limit this.
- the second device may perform different message notification display for different levels of privacy tags for different levels of privacy tags in the second message. For example, if the second message contains the highest level of privacy tag, it will only be displayed to the user "you have a new message", the sender of the message, the application used by the sender, the sending time, the content, etc. are not displayed, and the user uses the first
- the second device itself checks; if the second message contains a privacy tag with a slightly weaker privacy level, it displays to the user "you have a WeChat message from Zhang San", but hides the specific content of the message; if the second message does not contain any privacy tags A full notification of the second message can then be displayed.
- other display processing manners may be adopted in addition to the manner of the above-mentioned privacy label display processing, which is not specifically limited in the embodiment of the present invention.
- the unlocking prompt information may also be displayed on the lock screen interface to remind the user to perform the unlocking operation for message viewing.
- the application server determines whether the first message is a private message; if the first message is a private message, generating the first message according to the first message. a second message of the privacy tag; afterwards, sending the second message to the second device, so that the second device displays the second message on the notification interface according to the first privacy tag after receiving the second message Notification of the message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- the first device may send a second message to the application server, where the second message is sent.
- the user does not include any private content in the first message, or includes part of the private content in the first message, and the specific process is as follows: generating a first message; determining whether the first message is a private message; when the first message is a private message, Generating a second message according to the first message, where the second message does not include at least one piece of private content in the first message; sending the second message to the application server, so that the second device receives the second message forwarded by the application server, after
- the notification interface displays the notification in the second message.
- FIG. 9 is a flowchart of a message processing method according to an embodiment of the present invention.
- the interaction subject is a first device, a second device, an application server, a push server, and a proxy device.
- the method includes the following steps:
- the first device sends a data packet to the application server, where the data packet includes at least specified user identification information and a first message.
- the first device refers to a message sender, and may be a mobile terminal such as a smart phone or a tablet computer, or a fixed receiving device such as a personal computer, or a server for a social application or an instant messaging application.
- the type of the first device is not specifically limited in the embodiment of the present invention.
- the specified user identification information is used to indicate the recipient of the first message, which may be a phone number, a login name of an application, a mailbox, etc., and the form of the specified user identification information is also not specifically limited in the embodiment of the present invention.
- the data package may include other content in addition to the specified user identification information and the first message.
- the privacy label, the data packet sending time, and the like are not specifically limited in this embodiment of the present invention.
- the data may be sent in a wired manner or in a wireless manner, which is not specifically limited in the embodiment of the present invention.
- the embodiment of the present invention further includes a process of pushing service registration, and the specific process may be divided into the following four small steps.
- the second device sends the specified user identification information to the push server.
- the second device refers to the message receiver.
- the second step after receiving the specified user identification information, the push server calculates the specified registration identity corresponding to the specified user identity information, and sends the specified registration identity to the second device.
- the specified registration identity may be a string containing only letters, or a string of numbers and letters, and the like.
- the embodiment of the present invention does not specifically limit the form of the designated registration identity.
- the second device After the third device receives the specified registration identity, the second device sets a correspondence between the specified user identity and the specified registration identity, and sends a correspondence between the specified user identity information and the specified registration identity to the application server. .
- the second device may generate the corresponding entry as shown in the first row in Table 1, that is, the second device generates only the table.
- a single entry in 1 (a line).
- the entire correspondence table shown in Table 1 is composed of corresponding entries sent by multiple devices.
- the application server stores a correspondence between the specified user identity and the specified registration identity.
- the application server may store the foregoing relationship in a storage medium such as a memory or a flash memory.
- a storage medium such as a memory or a flash memory.
- the embodiment of the present invention does not specifically limit the type of the storage medium.
- the application server determines, according to the correspondence between the specified user identifier information, the user identifier information, and the registration identity, the specified registration identity.
- the application server stores a correspondence between the user identification information and the registration identity.
- the application server can store a large number of correspondences, including user identification information and registration identity sent by thousands of receiving devices.
- the application server determines the designated registration identity according to the correspondence between the specified user identification information, the user identification information, and the registration identity
- the application may be implemented in the following manner:
- the registration identity is determined as the specified registration identity.
- the second device After the second device is connected to the network, the second device sends the stored registration identity to the push server; after receiving the registration identity, the push server verifies whether the registration identity is legal, and obtains the verification result; after that, returns the verification result to Second device.
- the reason why the push server performs verification on the second device is to determine whether the registered identity identifier stored by the second device is personally granted before the push server. If the registration identity is calculated by the push server and returned to the second device, the registration identity is verified to be valid, and the verification result including the legal information is obtained; and the verification result is returned to the second device.
- the registration identity non-pushing server calculates and returns to the second device in advance, verifying that the registration identity is illegal, obtaining a verification result including the illegal information; returning the verification result to the second device, prompting the second device to register the identity Identity verification failed.
- the application server generates a data push request according to the specified registration identity and the second message.
- the application server sends the second message to the push server
- the application server After obtaining the second message, the application server also needs to generate a data push request.
- the data push request includes at least a specified registration identity and a second message.
- the data push request may include other content in addition to the above content.
- the generation time of the data push request and the like are not specifically limited in the embodiment of the present invention.
- the application server sends a data push request to the push server.
- the application server when it sends the data push request, it may send the data push request in a wireless or wired manner; or directly send the data push request in a wireless or wired manner.
- the embodiment of the invention is not specifically limited thereto.
- the push server After receiving the data push request, the push server sends the data push request to the second device according to the correspondence between the specified registration identity, the user identifier information, and the registration identity.
- the push server can determine the corresponding designated user according to the specified registration identity after receiving the data push request. Identification information. Further, based on the specified user identification information, it can be determined to which receiving device the second message is transmitted.
- the pushing server sends the data push request to the second device according to the correspondence between the specified registration identity, the user identifier information, and the registration identity, which may be implemented in the following manner:
- the second device After receiving the data push request, the second device sends a second message to the proxy device.
- the agent device is a push service of the second device operating system.
- the user's private data is stored on the proxy device.
- the privacy data can be set by the user according to the following rules:
- Rule 1 For any application (for example, communication applications, SMS, WeChat, email, etc.), the user can set the application as private data at the application level, and the push message of the application is always processed according to the privacy message. The specific content of the push message is not displayed when unlocking.
- any application for example, communication applications, SMS, WeChat, email, etc.
- Rule 2 For contacts (eg, privacy contacts, bank customer service, Alipay, etc.), the user can set the above contacts as private data at the contact level, and the contacts can match the application address book and system communication. Record, email contact address book obtained. Messages sent by this contact, whether sent by other communication tools such as email or WeChat, are processed according to the privacy message. The specific content of the push message is not displayed when it is not unlocked.
- contacts eg, privacy contacts, bank customer service, Alipay, etc.
- the user can set the above contacts as private data at the contact level, and the contacts can match the application address book and system communication. Record, email contact address book obtained. Messages sent by this contact, whether sent by other communication tools such as email or WeChat, are processed according to the privacy message. The specific content of the push message is not displayed when it is not unlocked.
- Rule 3 For keywords (eg, transaction amount, receipt of payment receipt, SMS verification code, etc.), the user can set the keyword as private data, and the above keywords can be automatically recognized by the system responsible for private message processing.
- the push message containing the above keywords is always processed according to the privacy message, and the specific content of the push message is not displayed when not unlocked.
- Rule 4 For certain time periods (eg, working hours, party hours, etc.) of the user equipment, the user equipment detects the user and the second through the bound wearable device at certain locations (eg, company, outside, etc.) The location relationship of the device, through the connection relationship of the bound vehicle, smart home and other devices, select different privacy processing methods for the push message. The above-mentioned time period, location, and bound wearable device may be separately judged, and the above factors may also be combined.
- the proxy device determines, according to the stored privacy data, whether the second message is a privacy message.
- the proxy device when the proxy device determines whether the second message is a private message according to the stored private data, the proxy device may be implemented in the following manner:
- the first message can be processed by word segmentation to obtain each participle; each participle is separately performed with private data. Alignment; if any participle matches one of the keywords in the privacy data, then the first message is determined to be a private message.
- the proxy device determines that the second message is a privacy message, process the second message, and send the processed second message to the second device.
- the second message may include a plurality of more sensitive privacy content.
- the second message when the second message is a delivery message of an online payment verification code, the second message may include a plurality of privacy contents such as an amount, a bank card number, and a verification code.
- the partial privacy content in the second message may be replaced, hidden or modified, so that only partial privacy content is included when displaying on the notification interface; and all privacy in the second message may also be selected.
- the content is replaced, hidden, or modified so that no privacy content is included when displayed on the notification interface, and there is no sensitive vocabulary in the second message.
- the second device displays the notification of the processed second message on the notification interface.
- the notification preview of the second message when the second device displays the notification of the processed second message on the notification interface, the notification preview of the second message is not displayed.
- the notification preview that does not display the second message refers to: when the notification of the second message is displayed, the specific content of the second message is not displayed, and only the summary notification information of the specific content that does not include the second message is displayed.
- the notification preview of the second message may not be displayed on the notification interface, that is, no relevant sensitive vocabulary is displayed. Only the summary notification information in the form of "you have a new message”, “you have a new transfer record”, and the like are displayed, and the embodiment of the present invention does not specifically limit this.
- the unlocking prompt information may also be displayed on the lock screen interface to remind the user to perform the unlocking operation for message viewing.
- the application server determines whether the first message is a private message; if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- FIG. 10 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present invention.
- the device is applied to an application server.
- the device includes: a first message receiving module 1001, a privacy message determining module 1002, a second message generating module 1003, and a second message sending module 1004.
- the first message receiving module 1001 is configured to receive a first message sent by the first device to the second device, where the privacy message determining module 1002 is connected to the first message receiving module 1001, and configured to determine whether the first message is a private message.
- the second message generating module 1003 is connected to the privacy message determining module 1002, and is configured to generate a second message according to the first message when the first message is a private message, where the second message carries the first privacy tag; the second message sending module 1004
- the second message generating module 1003 is configured to send a second message to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the privacy message determining module is configured to determine, according to the privacy data included in the first message, that the first message is a privacy message
- the second message generating module is configured to generate a second message according to the first message, and set a first privacy tag in the second message.
- the privacy message determining module is configured to determine, according to the second privacy tag included in the first message, that the first message is a privacy message;
- the second message generating module is configured to generate a second message according to the first message, and set a first privacy tag in the second message.
- the second message sending module is configured to send the second message to the second device, so that the second device does not display the notification preview of the second message on the notification interface of the second device after receiving the second message.
- the application server determines whether the first message is a private message, and if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- FIG. 11 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present invention.
- the device is applied to an application server.
- the device includes: a first message receiving module 1101, a privacy message determining module 1102, a second message generating module 1103, and a second message sending module 1104.
- the first message receiving module 1101 is configured to receive a first message sent by the first device to the second device, where the privacy message determining module 1102 is connected to the first message receiving module 1101, and configured to determine whether the first message is a privacy message;
- the message generating module 1103 is connected to the privacy message judging module 1102, and configured to generate a second message according to the first message when the first message is a private message, where the second message does not include at least one piece of private content in the first message; the second message
- the sending module 1104 is connected to the second message generating module 1103 for Sending a second message to the second device, so that the second device displays the notification of the second message on the notification interface after receiving the second message.
- the privacy message determining module is configured to determine, according to the privacy data included in the first message, that the first message is a privacy message
- the second message generating module is configured to remove at least one piece of the private content in the first message to obtain the second message.
- the application server determines whether the first message is a private message, and if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, the application does not need to run in the background, saving power
- FIG. 12 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present invention.
- the device is applied to the second device.
- the device includes: a second message receiving module 1201, a privacy tag determining module 1202, a first display module 1203, and a second display module 1204.
- the second message receiving module 1201 is configured to receive a second message that is sent to the second device.
- the privacy tag determining module 1202 is connected to determine whether the second message includes a privacy tag.
- the first display module 1203 is connected.
- the second device does not display the notification preview of the second message when the second message is displayed on the notification interface; the second display module 1204 is connected to the second message.
- the notification of the second message is displayed on the notification interface of the second message according to the user's setting.
- the first display module is configured to not display the specific content of the second message when displaying the notification of the second message, and only display the summary notification information of the specific content that does not include the second message.
- the application server determines whether the first message is a private message, and if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- FIG. 13 is a diagram of a terminal, which may be used to execute a message processing method performed by a second device in the foregoing embodiment.
- the terminal 1300 includes:
- RF (Radio Frequency) circuit 110 memory 120 including one or more computer readable storage media, input unit 130, display unit 140, sensor 150, audio circuit 160, WiFi (Wireless Fidelity) module 170.
- a processor 180 having one or more processing cores, and a power supply 190 and the like. It will be understood by those skilled in the art that the terminal structure shown in FIG. 13 does not constitute a limitation to the terminal, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements. among them:
- the RF circuit 110 can be used for transmitting and receiving information or during a call, and receiving and transmitting signals. Specifically, after receiving downlink information of the base station, the downlink information is processed by one or more processors 180. In addition, the data related to the uplink is sent to the base station. .
- the RF circuit 110 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, an LNA (Low Noise Amplifier). , duplexer, etc.
- RF circuitry 110 can also communicate with the network and other devices via wireless communication.
- Wireless communication can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access) Divisional Multiple Access), WCDMA (Wideband Code) Division Multiple Access, LTE (Long Term Evolution), e-mail, SMS (Short Messaging Service), etc.
- GSM Global System of Mobile communication
- GPRS General Packet Radio Service
- CDMA Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- LTE Long Term Evolution
- e-mail Short Messaging Service
- the memory 120 can be used to store software programs and modules, and the processor 180 executes various functional applications and data processing by running software programs and modules stored in the memory 120.
- the memory 120 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to The data created by the use of the terminal 1300 (such as audio data, phone book, etc.) and the like.
- memory 120 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 120 may also include a memory controller to provide access to memory 120 by processor 180 and input unit 130.
- the input unit 130 can be configured to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
- input unit 130 can include touch-sensitive surface 131 as well as other input devices 132.
- Touch-sensitive surface 131 also referred to as a touch display or trackpad, can collect touch operations on or near the user (such as a user using a finger, stylus, etc., on any suitable object or accessory on touch-sensitive surface 131 or The operation near the touch-sensitive surface 131) and driving the corresponding connecting device according to a preset program.
- the touch-sensitive surface 131 can include two portions of a touch detection device and a touch controller.
- the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
- the processor 180 is provided and can receive commands from the processor 180 and execute them.
- the touch-sensitive surface 131 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
- the input unit 130 can also include other input devices 132.
- other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.
- the display unit 140 can be used to display information input by the user or information provided to the user and the terminal Various graphical user interfaces of 1300, which may be composed of graphics, text, icons, video, and any combination thereof.
- the display unit 140 may include a display panel 141.
- the display panel 141 may be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like.
- the touch-sensitive surface 131 may cover the display panel 141, and when the touch-sensitive surface 131 detects a touch operation thereon or nearby, it is transmitted to the processor 180 to determine the type of the touch event, and then the processor 180 according to the touch event The type provides a corresponding visual output on display panel 141.
- touch-sensitive surface 131 and display panel 141 are implemented as two separate components to implement input and output functions, in some embodiments, touch-sensitive surface 131 can be integrated with display panel 141 for input. And output function.
- Terminal 1300 can also include at least one type of sensor 150, such as a light sensor, motion sensor, and other sensors.
- the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 141 according to the brightness of the ambient light, and the proximity sensor may close the display panel 141 when the terminal 1300 moves to the ear. / or backlight.
- the gravity acceleration sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity.
- the terminal 1300 can also be configured with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors, not here Let me repeat.
- the audio circuit 160, the speaker 161, and the microphone 162 can provide an audio interface between the user and the terminal 1300.
- the audio circuit 160 can transmit the converted electrical data of the received audio data to the speaker 161 for conversion to the sound signal output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into an electrical signal by the audio circuit 160. After receiving, it is converted into audio data, and then processed by the audio data output processor 180, transmitted to the terminal, for example, via the RF circuit 110, or outputted to the memory 120 for further processing.
- the audio circuit 160 may also include an earbud jack to provide communication of the peripheral earphones with the terminal 1300.
- WiFi is a short-range wireless transmission technology
- the terminal 1300 can be used by the WiFi module 170. It provides users with wireless broadband Internet access by sending and receiving emails, browsing the web and accessing streaming media.
- the processor 180 is a control center of the terminal 1300 that connects various portions of the entire handset with various interfaces and lines, by running or executing software programs and/or modules stored in the memory 120, and recalling data stored in the memory 120, The various functions and processing data of the terminal 1300 are performed to perform overall monitoring of the mobile phone.
- the processor 180 may include one or more processing cores; preferably, the processor 180 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like.
- the modem processor primarily handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 180.
- the terminal 1300 also includes a power source 190 (such as a battery) for powering various components.
- the power source can be logically coupled to the processor 180 through a power management system to manage functions such as charging, discharging, and power management through the power management system.
- Power supply 190 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
- the terminal 1300 may further include a camera, a Bluetooth module, and the like, and details are not described herein again.
- the display unit of the terminal is a touch screen display
- the terminal further includes a memory, and one or more programs, wherein one or more programs are stored in the memory and configured to be processed by one or more
- the execution of one or more programs includes instructions for performing the following operations:
- the first message is a private message, generating a second message according to the first message, where the second message carries the first privacy tag;
- determining whether the first message is a privacy message includes:
- generating a second message according to the first message includes:
- determining whether the first message is a privacy message includes:
- generating a second message according to the first message includes:
- displaying the notification of the second message on the notification interface according to the first privacy label includes:
- the notification preview of the second message is not displayed on the notification interface of the second device.
- the terminal after receiving the first message sent to the second device, the application server determines whether the first message is a private message; if the first message is a private message, generating the first message according to the first message.
- the second message of the privacy tag is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy tag after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- the server 1400 can vary considerably depending on configuration or performance, and can include one or more central processing units (CPUs) 1422 (eg, one or more processors) and memory 1432.
- CPUs central processing units
- storage media 1430 that store application 1442 or data 1444 (eg, one or one storage device in Shanghai).
- the memory 1432 and the storage medium 1430 may be short-term storage or persistent storage.
- the program stored on storage medium 1430 may include one or more modules (not shown), each of which may include a series of instruction operations in the server.
- the central office The processor 1422 can be arranged to communicate with the storage medium 1430 to perform a series of instruction operations in the storage medium 1430 on the server 1400.
- Server 1400 may also include one or more power sources 1426, one or more wired or wireless network interfaces 1450, one or more input and output interfaces 1458, and/or one or more operating systems 1441, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.
- operating systems 1441 such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.
- the one or more programs configured to be executed by one or more processors include instructions for performing the following operations:
- the second device displays the notification of the second message on the notification interface, the notification preview of the second message is not displayed;
- the notification of the second message is displayed on the notification interface of the second message according to the setting of the user.
- the not displaying the notification preview of the second message includes:
- the specific content of the second message is not displayed, and only the summary notification information that does not include the specific content of the second message is displayed.
- the server provided by the embodiment of the present invention determines whether the first message is a private message after receiving the first message sent to the second device, and generates a first privacy tag according to the first message if the first message is a private message.
- the second message is sent to the second device, so that the second device displays the notification of the second message on the notification interface according to the first privacy label after receiving the second message.
- the second message is displayed according to whether the second message carries the first privacy tag, so that the second device displays the content of the message of different granularity, which not only enables the user to know the important information in time.
- the notification message also prevents user privacy leakage, improves user experience and device usability; in addition, it does not require the application to run in the background, which is more energy efficient.
- the message processing apparatus provided by the foregoing embodiment only uses The division of each of the above functional modules is exemplified. In practical applications, the above function assignments may be completed by different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. .
- the message processing apparatus and the message processing method embodiment provided by the foregoing embodiments are in the same concept, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
- a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
- the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- Human Resources & Organizations (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Bioethics (AREA)
- Operations Research (AREA)
- Computing Systems (AREA)
- Primary Health Care (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
Abstract
本发明实施例提供了一种消息处理方法及装置,涉及通信技术领域,方法包括:接收第一设备发送给第二设备的第一消息;判断所述第一消息是否为隐私消息;如果所述第一消息为隐私消息,则根据所述第一消息生成第二消息,所述第二消息中携带第一隐私标签;向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,根据所述第一隐私标签在通知界面上显示所述第二消息的通知。当第二设备接收到第二消息后,根据第二消息是否携带第一隐私标签来显示第二消息,达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露。
Description
本发明涉及通信技术领域,特别涉及一种消息处理方法及装置。
随着通信技术的飞速发展,Android(安卓)设备、iOS(iPhone OS,苹果操作***)设备、Windows Phone设备等均具有在锁屏界面显示推送消息的功能。即,用户在智能终端上安装的应用程序(比如,短信、邮箱、即时消息应用等)可以将接收到的推送消息呈现的智能终端的锁屏界面上。之后,用户通过点击推送消息条目便可访问推送消息对应的应用,进而浏览该推送消息的全部内容。然而,由于可将接收到的各种类型推送消息均在锁屏界面上进行显示,所以存在泄漏用户个人隐私的风险。因此,在防止用户的个人隐私泄漏的前提下,如何进行推送消息的显示,成为了本领域技术人员较为关注的一个焦点。
现有技术中,通常采取两种方式进行推送消息的显示。第一种方式,针对iOS***,在通知中心分别对每个应用是否在锁屏界面上显示推送消息做出设置。设置为显示的应用将其对应的推送消息呈现在智能终端的锁屏界面上。设置不显示的应用不对其对应的推送消息在智能终端的锁屏界面上进行呈现。第二种方式,针对Android L或越狱后的iOS***,在API(Application Program ming Interface,应用程序编程接口)中设置应用的推送消息隐私级别。根据设置的隐私级别,对不同应用的推送消息进行不同方式的显示。比如,隐私级别高的应用的推送消息不在锁屏界面上进行显示;而隐私级别低的应用的推送消息可在锁屏界面上进行显示。
在实现本发明的过程中,发明人发现现有技术至少存在以下问题:
针对第一种方式,对于不在锁屏界面上呈现推送消息的应用来说,其在锁
屏状态下接收到的所有推送消息均不进行显示,这对用户及时获知重要推送消息造成影响,影响用户的体验度和终端设备的易用性。针对第二种方式,由于由应用程序接收推送消息并确定推送消息是否显示,所以需要应用程序一直在后台运行,较为耗电。
发明内容
为了解决上述问题,本发明实施例提供了一种消息处理方法及装置。所述技术方案如下:
第一方面,提供了一种消息处理方法,所述方法包括:
接收第一设备发送给第二设备的第一消息;
判断所述第一消息是否为隐私消息;
如果所述第一消息为隐私消息,则根据所述第一消息生成第二消息,所述第二消息中携带第一隐私标签;
向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,根据所述第一隐私标签在通知界面上显示所述第二消息的通知。
在第一方面的第一种可能的实现方式中,所述判断所述第一消息是否为隐私消息,包括:
根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;
相应地,所述根据所述第一消息生成第二消息,包括:
根据所述第一消息生成所述第二消息,并在所述第二消息中设置所述第一隐私标签。
结合第一方面,在第一方面的第二种可能的实现方式中,所述判断所述第一消息是否为隐私消息,包括:
根据所述第一消息中包含的第二隐私标签确定所述第一消息为隐私消息;
相应地,所述根据所述第一消息生成第二消息,包括:
根据所述第一消息生成所述第二消息,并在所述第二消息中设置所述第一
隐私标签。
结合第一方面、第一方面的第一种和第二种可能的实现方式,在第一方面的第三种可能的实现方式中,所述根据所述第一隐私标签在通知界面上显示所述第二消息的通知,包括:
在所述第二设备的通知界面上不显示所述第二消息的通知预览。
第二方面,提供了一种消息处理方法,所述方法包括:
接收第一设备发送给第二设备的第一消息;
判断所述第一消息是否为隐私消息;
如果所述第一消息为隐私消息,则根据所述第一消息生成第二消息,所述第二消息不包含所述第一消息中至少一项隐私内容;
向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,在通知界面上显示所述第二消息的通知。
在第二方面的第一种可能的实现方式中,所述判断所述第一消息是否为隐私消息,包括:
根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;
相应地,所述根据所述第一消息生成第二消息,包括:
去除所述第一消息中的至少一项隐私内容,得到所述第二消息。
第三方面,提供了一种消息处理方法,所述方法包括:
接收发送给第二设备的第二消息;
判断所述第二消息中是否包含隐私标签;
当所述第二消息中包含隐私标签时,所述第二设备在通知界面上显示所述第二消息的通知时,不显示所述第二消息的通知预览;
当所述第二消息中不包含隐私标签时,在所述第二消息的通知界面上根据用户的设置显示所述第二消息的通知。
在第三方面的第一种可能的实现方式中,所述不显示所述第二消息的通知预览,包括:
在显示所述第二消息的通知时,不显示所述第二消息的具体内容,仅显示不包含所述第二消息的具体内容的概要通知信息。
第四方面,提供了一种消息处理装置,所述装置包括:
第一消息接收模块,用于接收第一设备发送给第二设备的第一消息;
隐私消息判断模块,用于判断所述第一消息是否为隐私消息;
第二消息生成模块,用于当所述第一消息为隐私消息时,根据所述第一消息生成第二消息,所述第二消息中携带第一隐私标签;
第二消息发送模块,用于向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,根据所述第一隐私标签在通知界面上显示所述第二消息的通知。
在第四方面的第一种可能的实现方式中,所述隐私消息判断模块,用于根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;
相应地,所述第二消息生成模块,用于根据所述第一消息生成所述第二消息,并在所述第二消息中设置所述第一隐私标签。
结合第四方面,在第四方面的第二种可能的实现方式中,所述隐私消息判断模块,用于根据所述第一消息中包含的第二隐私标签确定所述第一消息为隐私消息;
相应地,所述第二消息生成模块,用于根据所述第一消息生成所述第二消息,并在所述第二消息中设置所述第一隐私标签。
结合第四方面、第四方面的第一种和第二种可能的实现方式,在第四方面的第三种可能的实现方式中,所述第二消息发送模块,用于向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,在所述第二设备的通知界面上不显示所述第二消息的通知预览。
第五方面,提供了一种消息处理装置,所述装置包括:
第一消息接收模块,用于接收第一设备发送给第二设备的第一消息;
隐私消息判断模块,用于判断所述第一消息是否为隐私消息;
第二消息生成模块,用于当所述第一消息为隐私消息时,根据所述第一消息生成第二消息,所述第二消息不包含所述第一消息中至少一项隐私内容;
第二消息发送模块,用于向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,在通知界面上显示所述第二消息的通知。
在第五方面的第一种可能的实现方式中,所述隐私消息判断模块,用于根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;
相应地,所述第二消息生成模块,用于去除所述第一消息中的至少一项隐私内容,得到所述第二消息。
第六方面,提供了一种消息处理装置,所述装置包括:
第二消息接收模块,用于接收发送给第二设备的第二消息;
隐私标签判断模块,用于判断所述第二消息中是否包含隐私标签;
第一显示模块,用于当所述第二消息中包含隐私标签时,所述第二设备在通知界面上显示所述第二消息的通知时,不显示所述第二消息的通知预览;
第二显示模块,用于当所述第二消息中不包含隐私标签时,在所述第二消息的通知界面上根据用户的设置显示所述第二消息的通知。
在第六方面的第一种可能的实现方式中,所述第一显示模块,用于在显示所述第二消息的通知时,不显示所述第二消息的具体内容,仅显示不包含所述第二消息的具体内容的概要通知信息。
本发明实施例提供的技术方案的有益效果是:
在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消
息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1是本发明实施例提供的一种消息处理方法的流程图;
图2是本发明实施例提供的一种消息处理方法的流程图;
图3是本发明实施例提供的一种消息处理方法的流程图;
图4是本发明实施例提供的一种消息处理方法的流程图;
图5是本发明实施例提供的一种应用服务器注册隐私数据的示意图;
图6是本发明实施例提供的一种消息处理方法的流程图;
图7是本发明实施例提供的一种消息处理方法的流程图;
图8是本发明实施例提供的一种推送服务注册的示意图;
图9是本发明实施例提供的一种消息处理方法的流程图;
图10是本发明实施例提供的一种消息处理装置的结构示意图;
图11是本发明实施例提供的一种消息处理装置的结构示意图;
图12是本发明实施例提供的一种消息处理装置的结构示意图;
图13是本发明实施例提供的一种终端的结构示意图;
图14是本发明实施例提供的一种应用服务器的结构示意图。
为使本发明的目的、技术方案和优点更加清楚,下面将结合附图对本发明实施方式作进一步地详细描述。
图1是本发明实施例提供的一种消息处理方法的流程图。以应用服务器执行该方法的角度为例,参见图1,本发明实施例提供的方法流程包括:
101、接收第一设备发送给第二设备的第一消息。
其中,第一设备为消息发送方,第二设备为消息接收方。
102、判断第一消息是否为隐私消息;如果第一消息为隐私消息,则执行步骤102;如果第一消息非隐私消息,直接执行步骤104。
103、如果第一消息为隐私消息,则根据第一消息生成第二消息,第二消息中携带第一隐私标签。
104、向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。
本发明实施例提供的方法,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
可选地,判断第一消息是否为隐私消息,包括:
根据第一消息中包含的隐私数据确定第一消息为隐私消息;
相应地,根据第一消息生成第二消息,包括:
根据第一消息生成第二消息,并在第二消息中设置第一隐私标签。
可选地,判断第一消息是否为隐私消息,包括:
根据第一消息中包含的第二隐私标签确定第一消息为隐私消息;
相应地,根据第一消息生成第二消息,包括:
根据第一消息生成第二消息,并在第二消息中设置第一隐私标签。
可选地,根据第一隐私标签在通知界面上显示第二消息的通知,包括:
在第二设备的通知界面上不显示第二消息的通知预览。
上述所有可选技术方案,可以采用任意结合形成本发明的可选实施例,在此不再一一赘述。
图2是本发明实施例提供的一种消息处理方法的流程图。以应用服务器执行该方法的角度为例,参见图2,本发明实施例提供的方法流程包括:
201、接收第一设备发送给第二设备的第一消息。
202、判断所述第一消息是否为隐私消息;如果所述第一消息为隐私消息,则执行步骤203;如果第一消息非隐私消息,直接执行步骤204。
203、如果所述第一消息为隐私消息,则根据所述第一消息生成第二消息,所述第二消息不包含所述第一消息中至少一项隐私内容;
204、向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,在通知界面上显示所述第二消息的通知。
本发明实施例提供的方法,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
可选地,所述判断所述第一消息是否为隐私消息,包括:
根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;
相应地,所述根据所述第一消息生成第二消息,包括:
去除所述第一消息中的至少一项隐私内容,得到所述第二消息。
上述所有可选技术方案,可以采用任意结合形成本发明的可选实施例,在此不再一一赘述。
图3是本发明实施例提供的一种消息处理方法的流程图。以第二设备执行该方法的角度为例,参见图3,本发明实施例提供的方法流程包括:
301、接收发送给第二设备的第二消息。
302、判断第二消息中是否包含隐私标签;如果第二消息中包含隐私标签,则执行步骤303;如果第二消息中不包含隐私标签,则执行步骤304。
303、当第二消息中包含隐私标签时,第二设备在通知界面上显示第二消息的通知时,不显示第二消息的通知预览。
304、当第二消息中不包含隐私标签时,在第二消息的通知界面上根据用户的设置显示第二消息的通知。
本发明实施例提供的方法,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
可选地,不显示第二消息的通知预览,包括:
在显示第二消息的通知时,不显示第二消息的具体内容,仅显示不包含第
二消息的具体内容的概要通知信息。
上述所有可选技术方案,可以采用任意结合形成本发明的可选实施例,在此不再一一赘述。
图4本发明实施例提供的一种消息处理方法的流程图。交互主体为第一设备、第二设备、应用服务器和推送服务器。以数据包中包括指定用户标识信息和第一消息,第二消息不携带第一隐私标签为例,参见图4,本发明实施例提供的方法流程包括:
401、第一设备向应用服务器发送数据包,该数据包中至少包括指定用户标识信息和第一消息。
在本发明实施例中,第一设备指代消+息发送方,既可为智能手机、平板电脑等移动终端、或个人计算机等固定接收设备,也可为社交类应用或即时通讯类应用的服务器。本发明实施例对第一设备的类型不进行具体限定。指定用户标识信息用于指示第一消息的接收方,可为电话号码、某一应用的登录名称、邮箱等等,本发明实施例对指定用户标识信息的形式同样不进行具体限定。
此外,数据包中除包括指定用户标识信息和第一消息外,还可包括其他内容。比如,隐私标签、数据包发送时间等等,本发明实施例对此不进行具体限定。在第一设备向应用服务器发送数据包时,既可以有线的方式进行发送,也可以无线的方式进行发送,本发明实施例对此同样不进行具体限定。
需要说明的是,参见图5,在执行上述步骤401之前,本发明实施例还包括应用服务器进行隐私注册的过程,具体过程可分为下述五个小步骤。
第一步、第二设备向推送服务器发送指定用户标识信息。
在本发明实施例中,第二设备指代消息接收方。
第二步、推送服务器在接收到指定用户标识信息后,计算指定用户标识信息对应的指定注册身份标识,并将指定注册身份标识发送给第二设备。
针对该步骤,指定注册身份标识可为一个仅包含字母的字符串、或一个数
字与字母混合的字符串等,本发明实施例对指定注册身份标识的形式不进行具体限定。推送服务器计算指定用户标识对应的指定注册身份标识时,可参考现有技术实现,此处不再进行赘述。
第三步、第二设备接收到指定注册身份标识后,设置指定用户身份标识与指定注册身份标识之间的对应关系,并向应用服务器发送指定用户标识信息与指定注册身份标识之间的对应关系。
针对该步骤,第二设备在设置指定用户身份标识与指定注册身份标识之间的对应关系时,可生成如下表1中第一行所示的对应表项,即第二设备生成的仅仅是表1中的单条条目(某一行)。表1中所示的整个对应关系表是由多个设备发送的对应表项组成的。应用服务器在接收到第二设备发送的指定用户身份标识与指定注册身份标识之间的对应表项后,将该表项***到如下表1所示的表格中即可。
表1
用户标识信息 | 注册身份标识 |
用户标识信息A | 指定注册身份标识A |
…… | …… |
当然,除上述生成及发送对应关系的方式外,还可采取其他方式,本发明实施例对此不进行具体限定。需要说明的是,上述表1(整张表格)的生成和存储过程可在应用服务器上实现,还可在推送服务器上实现,本发明实施例对此不进行具体限定。本发明实施例仅以应用服务器生成和存储为例进行说明。
第四步、第二设备获取用户设置的隐私数据,向应用服务器发送隐私数据和对应的指定用户标识信息,
针对该步骤,隐私数据可由用户自身按照下述规则进行设置:
规则一、对于任一应用(比如,通信类应用、短信、微信、邮件等)而言,用户可以在应用程序级别将该应用设置为隐私数据,该应用的推送消息一律按隐私消息处理,未解锁时不显示推送消息的具体内容。
规则二、对于联系人(比如,隐私联系人、银行客服、支付宝等)而言,用户可以在联系人级别将上述联系人设置为隐私数据,上述联系人可通过匹配应用程序通讯录、***通讯录、邮箱联系人通讯录获得。该联系人发来的消息,无论是以邮件还是微信等其他通信工具发送的,均按照隐私消息处理。未解锁时不显示推送消息的具体内容。
规则三、对于关键字(比如,交易额、收到支出回执、短信验证码等)而言,用户可以将该关键字设置为隐私数据,上述关键字可以由负责隐私消息处理的***自动识别。包含上述关键字的推送消息一律按照隐私消息处理,未解锁时不显示推送消息的具体内容。
规则四、对于用户设备在某些时间段(比如,工作时段、聚会时段等),用户设备在某些地点(比如,公司、外面等),通过绑定的可穿戴设备检测到用户与第二设备的位置关系,通过绑定的车载、智能家居等设备的连接关系,选择对于推送消息的不同隐私处理方式。可针对上述的时间段,地点,绑定的可穿戴设备分别判断,也可综合上述因素判断。
当用户按照上述规则设置好隐私数据后,第二设备获取设置好的隐私数据,并将设置好的隐私数据和指定用户标识信息一起上传至应用服务器,以方便应用服务器进行存储。
第五步、应用服务器存储指定用户身份标识与指定注册身份标识之间的对应关系、隐私数据与指定用户标识信息之间的对应关系。
针对该步骤,应用服务器在存储上述两种对应关系时,可将其存储在内存或闪存等存储介质中,本发明实施例对存储介质的类型不进行具体限定。
402、应用服务器在接收到该数据包后,根据指定用户标识信息、用户标识信息和注册身份标识之间的对应关系,确定指定注册身份标识。
在本发明实施例中,应用服务器中存储了用户标识信息和注册身份标识之间的对应关系。随着服务器处理能力的增强,应用服务器中可存储海量的对应关系,包括成千上万个接收设备发送的用户标识信息和注册身份标识。
其中,应用服务器在根据指定用户标识信息、用户标识信息和注册身份标识之间的对应关系,确定指定注册身份标识时,具体可采取下述方式实现:
根据指定用户标识信息,在用户标识信息和注册身份标识之间的对应关系中进行搜索查找,确定与指定用户标识信息相匹配的注册身份标识(比如,与指定用户标识信息为于同一表项的注册身份标识),将该注册身份标识确定为指定注册身份标识。
403、应用服务器根据指定用户标识信息、存储的隐私数据与用户标识信息之间的对应关系,判断第一消息是否为隐私消息。
在本发明实施例中,由于在上述步骤401中应用服务器已经存储了隐私数据与用户标识信息之间的对应关系,所以应用服务器在接收到第一设备发送的数据包后,便可根据指定用户标识信息确定第一消息是否为隐私消息。其中,隐私消息是指涵盖了隐私数据的消息。
其中,应用服务器在根据指定用户标识信息、存储的隐私数据与用户标识信息之间的对应关系,判断第一消息是否为隐私消息时,具体可采取下述方式实现:
根据指定用户标识信息在隐私数据与用户标识信息之间的对应关系中进行搜索查找,确定与指定用户标识信息相匹配的隐私数据。判断第一消息是否与隐私数据中的任一数据项相匹配;如果第一消息与隐私数据中的任一数据项相匹配,则确定第一消息是隐私消息,继续执行下述步骤404;如果第一消息与隐私数据中的任一数据项均不匹配,则确定第一消息不是隐私消息,处理流程至此结束。
以隐私数据为较为敏感的关键字(比如,交易额、收到支出回执、短信验证码等)为例,则可将第一消息进行分词处理,得到各个分词;将各个分词分别与隐私数据进行比对;如果任一分词与隐私数据中的一个关键字相匹配,则确定第一消息为隐私消息。
针对其他类型的隐私数据,处理过程与上述过程类似,此处不再赘述。
需要说明的是,在第一设备和应用服务器执行上述步骤401至步骤403时,第二设备和推送服务器之间还包括下述交互步骤。
在第二设备联网后,第二设备向推送服务器发送存储的注册身份标识;推送服务器在接收到该注册身份标识后,验证该注册身份标识是否合法,得到验证结果;之后,将验证结果返回给第二设备。
在本发明实施例中,推送服务器之所以要对第二设备进行验证,是为了确定第二设备所存储的注册身份标识是否为推送服务器之前亲自授予的。如果该注册身份标识为推送服务器事先计算并返回给第二设备的,则验证该注册身份标识合法,得到包括合法信息的验证结果;将该验证结果返回给第二设备。如果该注册身份标识非推送服务器事先计算并返回给第二设备的,则验证该注册身份标识非法,得到包括非法信息的验证结果;将该验证结果返回给第二设备,提示第二设备注册身份标识验证失败。
当然,除了上述验证注册身份标识的方式外,还可采取其他验证方式,本发明实施例对此不进行具体限定。
404、当应用服务器判断第一消息为隐私消息时,根据第一消息生成第二消息,第二消息不包含第一消息中至少一项隐私内容。
其中,在根据第一消息生成第二消息时,具体可采取下述方式实现:去除第一消息中的至少一项隐私内容,得到第二消息。当然,除上述生成第二消息的方式外,还可采取其他生成方式,本发明实施例对此不进行具体限定。
在本发明实施例中,当第一消息为隐私消息时,第一消息中可能包括多项较为敏感的隐私内容。比如,当第一消息为一个网上支付验证码的下发消息时,第一消息中可能包括金额、银行***、验证码等多项隐私内容。
在该种情况下,根据第一消息生成第二消息时,既可选择将第一消息中的部分隐私内容进行替换、隐藏或修改,使得第二消息中包括第一消息中的部分隐私内容;还可选择将第一消息中的全部隐私内容进行替换、隐藏或修改,使得第二消息中不包括第一消息中的任意隐私内容,此时第二消息中无任何敏感
词汇。
比如,当第二消息不包括第一消息中部分隐私内容时,第二消息可为“XX给您转账XXX元”,“XX给您转账”等形式;当第二消息不包括第一消息中任意隐私内容时,第二消息可为“您有新的转账记录”等形式,本发明实施例对此不进行具体限定。
405、应用服务器根据指定注册身份标识和第二消息,生成数据推送请求。
在本发明实施例中,要实现消息推送(Push Notification)需涉及三个对象:
1、接收设备,接收第二消息并根据消息内容进行相应处理;
2、应用服务器,将第二消息发送给推送服务器;
3、推送服务器,接收来自于应用服务器的数据推送请求,并将该数据推送请求发送至接收设备。
基于上述规则,应用服务器在得到第二消息后,还需生成数据推送请求。其中,数据推送请求中至少包括指定注册身份标识和第二消息。当然,数据推送请求中除包括上述内容外,还可包括其他内容。比如,数据推送请求的生成时间等等,本发明实施例对此不进行具体限定。
406、应用服务器向推送服务器发送数据推送请求。
在本发明实施例中,应用服务器在发送数据推送请求时,既可在将数据推送请求打包后,以无线或有线的方式发送;还可直接将数据推送请求以无线或有线的方式发送,本发明实施例对此不进行具体限定。
407、推送服务器在接收到该数据推送请求后,根据指定注册身份标识、用户标识信息和注册身份标识之间的对应关系,将数据推送请求发送至第二设备。
在本发明实施例中,由于推送服务器中存储了用户标识信息和注册身份标识之间的对应关系,所以推送服务器在接收到数据推送请求后,根据指定注册身份标识,便可确定对应的指定用户标识信息。进而,根据指定用户标识信息可确定将第二消息发送至哪一个接收设备。
其中,推送服务器在根据指定注册身份标识、用户标识信息和注册身份标识之间的对应关系,将数据推送请求发送至第二设备时,具体可采取下述方式实现:
根据指定注册身份标识在用户标识信息和注册身份标识之间的对应关系中进行搜索查找,确定与指定注册身份标识相匹配的指定用户标识信息;根据指定用户标识信息将数据推送请求发送至第二设备。
408、第二设备在接收到第二消息后,在通知界面上显示第二消息的通知。
在本发明实施例中,通知界面既可为锁屏界面,还可为除锁屏界面之外的***通知界面、应用主界面、终端桌面等,本发明实施例对通知界面的类型不进行具体限定。
第二设备在接收到第二消息后,如果当前处于锁屏状态,则可直接将第二消息在锁屏界面上进行显示。此时第二消息的通知可为“XX给您转账”、“您有**条新消息”、“您有新的转账记录”等形式,所以即便他人看到该通知也不会存在泄漏用户个人隐私的情况。
优选地,为了防止用户隐私的泄露,可在通知界面上不显示第二消息的通知预览,也即不显示任何相关的敏感词汇。仅显示“您有**条新消息”、“您有新的转账记录”等形式的概要通知消息,本发明实施例对此不进行具体限定。
此外,若当前在锁屏界面显示第二消息,则还可在锁屏界面上显示解锁提示信息,以提醒用户进行解锁操作,以进行第二消息的详情查看。在用户解锁第二设备后,第二设备向应用服务器发送完整推送消息请求。应用服务器在接收到该完整推送消息请求后,将完整的且包含隐私消息的第二消息发送至第二设备。
本发明实施例提供的方法,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二
消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
图6是本发明实施例提供的一种消息处理方法的流程图。交互主体为第一设备、第二设备、应用服务器和推送服务器。以数据包中包括指定用户标识信息和第一消息,第二消息中携带第一隐私标签为例,参见图6,本发明实施例提供的方法流程包括:
601、第一设备向应用服务器发送数据包,该数据包中至少包括指定用户标识信息和第一消息。
在本发明实施例中,第一设备指代消息发送方,可为智能手机、平板电脑等移动终端、或个人计算机等固定接收设备,也可为社交类应用或即时通讯类应用的服务器。本发明实施例对第一设备的类型不进行具体限定。指定用户标识信息用于指示第一消息的接收方,可为电话号码、某一应用的登录名称、邮箱等等,本发明实施例对指定用户标识信息的形式同样不进行具体限定。
此外,数据包中除包括指定用户标识信息和第一消息外,还可包括其他内容。比如,隐私标签、数据包发送时间等等,本发明实施例对此不进行具体限定。在第一设备向应用服务器发送数据包时,既可以有线的方式进行发送,也可以无线的方式进行发送,本发明实施例对此同样不进行具体限定。
需要说明的是,参见图5,在执行上述步骤601之前,本发明实施例还包括应用服务器进行隐私注册的过程,具体过程可分为下述五个小步骤。
第一步、第二设备向推送服务器发送指定用户标识信息。
在本发明实施例中,第二设备指代消息接收方。
第二步、推送服务器在接收到指定用户标识信息后,计算指定用户标识信息对应的指定注册身份标识,并将指定注册身份标识发送给第二设备。
针对该步骤,指定注册身份标识可为一个仅包含字母的字符串、或一个数字与字母混合的字符串等,本发明实施例对指定注册身份标识的形式不进行具体限定。推送服务器计算指定用户标识对应的指定注册身份标识时,可参考现有技术实现,此处不再进行赘述。
第三步、第二设备接收到指定注册身份标识后,设置指定用户身份标识与指定注册身份标识之间的对应关系,并向应用服务器发送指定用户标识信息与指定注册身份标识之间的对应关系。
针对该步骤,第二设备在设置指定用户身份标识与指定注册身份标识之间的对应关系时,可生成如上表1中第一行所示的对应表项,即第二设备生成的仅仅是表1中的单条条目(某一行)。表1中所示的整个对应关系表是由多个设备发送的对应表项组成的。应用服务器在接收到第二设备发送的指定用户身份标识与指定注册身份标识之间的对应表项后,将该表项***到如上表1所示的表格中即可。
当然,除上述生成及发送对应关系的方式外,还可采取其他方式,本发明实施例对此不进行具体限定。
第四步、第二设备获取用户设置的隐私数据,向应用服务器发送隐私数据和对应的指定用户标识信息,
针对该步骤,隐私数据可由用户自身按照下述规则进行设置:
规则一、对于任一应用(比如,通信类应用、短信、微信、邮件等)而言,用户可以在应用程序级别将该应用设置为隐私数据,该应用的推送消息一律按隐私消息处理,未解锁时不显示推送消息的具体内容。
规则二、对于联系人(比如,隐私联系人、银行客服、支付宝等)而言,用户可以在联系人级别将上述联系人设置为隐私数据,上述联系人可通过匹配应用程序通讯录、***通讯录、邮箱联系人通讯录获得。该联系人发来的消息,无论是以邮件还是微信等其他通信工具发送的,均按照隐私消息处理。未解锁时不显示推送消息的具体内容。
规则三、对于关键字(比如,交易额、收到支出回执、短信验证码等)而言,用户可以将该关键字设置为隐私数据,上述关键字可以由负责隐私消息处理的***自动识别。包含上述关键字的推送消息一律按照隐私消息处理,未解锁时不显示推送消息的具体内容。
规则四、对于用户设备在某些时间段(比如,工作时段、聚会时段等),用户设备在某些地点(比如,公司、外面等),通过绑定的可穿戴设备检测到用户与第二设备的位置关系,通过绑定的车载、智能家居等设备的连接关系,选择对于推送消息的不同隐私处理方式。可针对上述的时间段,地点,绑定的可穿戴设备分别判断,也可综合上述因素进行判断。
当用户按照上述规则设置好隐私数据后,第二设备获取设置好的隐私数据,并将设置好的隐私数据和指定用户标识信息一起上传至应用服务器,以方便应用服务器进行存储。
第五步、应用服务器存储指定用户身份标识与指定注册身份标识之间的对应关系、隐私数据与指定用户标识信息之间的对应关系。
针对该步骤,应用服务器在存储上述两种对应关系时,可将其存储在内存或闪存等存储介质中,本发明实施例对存储介质的类型不进行具体限定。
602、应用服务器在接收到该数据包后,根据指定用户标识信息、用户标识信息和注册身份标识之间的对应关系,确定指定注册身份标识。
在本发明实施例中,应用服务器中存储了用户标识信息和注册身份标识之间的对应关系。随着服务器处理能力的增强,应用服务器中可存储海量的对应关系,包括成千上万个接收设备发送的用户标识信息和注册身份标识。
其中,应用服务器在根据指定用户标识信息、用户标识信息和注册身份标识之间的对应关系,确定指定注册身份标识时,具体可采取下述方式实现:
根据指定用户标识信息,在用户标识信息和注册身份标识之间的对应关系中进行搜索查找,确定与指定用户标识信息相匹配的注册身份标识(比如,与指定用户标识信息为于同一表项的注册身份标识),将该注册身份标识确定为
指定注册身份标识。
603、应用服务器判断第一消息是否为隐私消息;当第一消息为隐私消息时,执行下述步骤604。
在本发明实施例中,应用服务器在判断第一消息是否为隐私消息时,可采取下述方式实现:
根据第一消息中是否包含隐私数据确定第一消息是否为隐私消息;当第一消息中包含隐私数据时,确定第一消息为隐私消息;当第一消息中不包含隐私数据时,确定第一消息为非隐私消息。
由于在上述步骤601中应用服务器已经存储了隐私数据与用户标识信息之间的对应关系,所以应用服务器在接收到第一设备发送的数据包后,便可根据指定用户标识信息确定第一消息是否为包括隐私内容的隐私消息。
其中,应用服务器在根据指定用户标识信息、存储的隐私数据与用户标识信息之间的对应关系,判断第一消息是否为隐私消息时,具体可采取下述方式实现:
根据指定用户标识信息在隐私数据与用户标识信息之间的对应关系中进行搜索查找,确定与指定用户标识信息相匹配的隐私数据。判断第一消息是否与隐私数据中的任一数据项相匹配;如果第一消息与隐私数据中的任一数据项相匹配,则确定第一消息是隐私消息,继续执行下述步骤604;如果第一消息与隐私数据中的任一数据项均不匹配,则确定第一消息不是隐私消息,处理流程至此结束。
以隐私数据为较为敏感的关键字(比如,交易额、收到支出回执、短信验证码等)为例,则可将第一消息进行分词处理,得到各个分词;将各个分词分别与隐私数据进行比对;如果任一分词与隐私数据中的一个关键字相匹配,则确定第一消息为隐私消息。
针对其他类型的隐私数据,处理过程与上述过程类似,此处不再赘述。
需要说明的是,在第一设备和应用服务器执行上述步骤601至步骤603时,
第二设备和推送服务器之间还包括下述交互步骤。
在第二设备联网后,第二设备向推送服务器发送存储的注册身份标识;推送服务器在接收到该注册身份标识后,验证该注册身份标识是否合法,得到验证结果;之后,将验证结果返回给第二设备。
在本发明实施例中,推送服务器之所以要对第二设备进行验证,是为了确定第二设备所存储的注册身份标识是否为推送服务器之前亲自授予的。如果该注册身份标识为推送服务器事先计算并返回给第二设备的,则验证该注册身份标识合法,得到包括合法信息的验证结果;将该验证结果返回给第二设备。如果该注册身份标识非推送服务器事先计算并返回给第二设备的,则验证该注册身份标识非法,得到包括非法信息的验证结果;将该验证结果返回给第二设备,提示第二设备注册身份标识验证失败。
当然,除了上述验证注册身份标识的方式外,还可采取其他验证方式,本发明实施例对此不进行具体限定。
604、当应用服务器判断第一消息为隐私消息时,根据第一消息生成第二消息,第二消息中携带第一隐私标签。
在本发明实施例中,应用服务器在根据第一消息生成第二消息时,具体可采取下述方式实现:
根据第一消息生成第二消息,并在第二消息中设置第一隐私标签。
由于在上述步骤603中应用服务器已经判断第一消息为隐私消息,所以为了保护用户的隐私,在第二消息中***第一隐私标签,得到第二消息。其中,针对隐私消息的私密程度可设置不同的隐私标签。比如,设置私人和秘密两个不同程度的隐私标签。针对银行客服、支付宝客服、涉及交易额、短信验证码等跟个人财产相关的隐私消息,可设置隐私级别最高的隐私标签,即秘密隐私标签;针对某一应用发送的推送消息可设置隐私级别稍弱的隐私标签,即私人隐私标签,本发明实施例对此不进行具体限定。
在本发明实施例中,应用服务器在第二消息中***第一隐私标签时,既可
在第二消息的首部***,也可在第二消息的尾部***,也可以通过将第二消息中的某一预设的数据位标记或置位实现,本发明实施例对此不进行具体限定。
其中,第一隐私标签可以设置为第二消息内容中的某一特定字段,长度可以为一个字节、一个比特、或者为任意长度;位置可以位于第二消息的开头、结尾或中间的任意位置,只要能被消息的接收方识别即可。本发明实施例对第一隐私标签的形式和位置均不进行具体限定。
605、根据指定注册身份标识和第二消息,生成数据推送请求。
在本发明实施例中,要实现消息推送(Push Notification)需涉及三个对象:
1、接收设备,接收第二消息并根据消息内容进行相应处理;
2、应用服务器,将第二消息发送给推送服务器;
3、推送服务器,接收来自于应用服务器的数据推送请求,并将该数据推送请求发送至接收设备。
基于上述规则,应用服务器在得到第二消息后,还需生成数据推送请求。其中,数据推送请求中至少包括指定注册身份标识和第二消息。当然,数据推送请求中除包括上述内容外,还可包括其他内容。比如,数据推送请求的生成时间等等,本发明实施例对此不进行具体限定。
606、应用服务器向推送服务器发送数据推送请求。
在本发明实施例中,应用服务器在发送数据推送请求时,既可在将数据推送请求打包后,以无线或有线的方式发送;还可直接将数据推送请求以无线或有线的方式发送,本发明实施例对此不进行具体限定。
607、推送服务器在接收到该数据推送请求后,根据指定注册身份标识、用户标识信息和注册身份标识之间的对应关系,将数据推送请求发送至第二设备。
在本发明实施例中,由于推送服务器中存储了用户标识信息和注册身份标识之间的对应关系,所以推送服务器在接收到数据推送请求后,根据指定注册身份标识,便可确定对应的指定用户标识信息。进而,根据指定用户标识信息
可确定将第二消息发送至哪一个接收设备。
其中,推送服务器在根据指定注册身份标识、用户标识信息和注册身份标识之间的对应关系,将数据推送请求发送至第二设备时,具体可采取下述方式实现:
根据指定注册身份标识在用户标识信息和注册身份标识之间的对应关系中进行搜索查找,确定与指定注册身份标识相匹配的指定用户标识信息;根据指定用户标识信息将数据推送请求发送至第二设备。
608、第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。
其中,在根据第一隐私标签在通知界面上显示第二消息的通知时,具体可采取下述方式实现:
在第二设备的通知界面上不显示第二消息的通知预览。其中,不显示第二消息的通知预览指代:在显示第二消息的通知时,不显示第二消息的具体内容,仅显示不包含第二消息的具体内容的概要通知信息。
在本发明实施例中,第二设备在接收到第二消息后,检查第二消息中是否包含隐私标签。因为此时第二消息中包括第一隐私标签,所以第二设备在显示第二消息的通知时,还需先对第二消息进行处理。其中,第二消息中可能包括多项较为敏感的隐私内容。比如,当第二消息为一个网上支付验证码的下发消息时,第二消息中可能包括金额、银行***、验证码等多项隐私内容。
在该种情况下,既可选择将第二消息中的部分隐私内容进行替换、隐藏或修改,使得第二消息在通知界面上进行显示时仅包含部分隐私内容;还可选择将第二消息中的全部隐私内容进行替换、隐藏或修改,使得第二消息在通知界面上进行显示时不包含任意隐私内容,此时第二消息中无任何敏感词汇。
优选地,为了防止用户隐私的泄露,可在通知界面上不显示第二消息的通知预览,也即不显示任何相关的敏感词汇。仅显示“您有**条新消息”、“您有新的转账记录”等形式的概要通知消息,本发明实施例对此不进行具体限定。
综上所述,第二设备在接收到第二消息后,针对第二消息中的不同级别的隐私标签,可以针对不同级别的隐私标签进行不同的消息通知显示。例如:如果第二消息含有最高级别的隐私标签,则仅显示给用户“你有一条新消息”,消息的发送方,发送方使用的应用,发送时间,内容等均不显示,由用户使用第二设备自行查看;如果第二消息含有隐私级别稍弱的隐私标签,则显示给用户“你有一条来自张三的微信消息”,但是隐藏消息的具体内容;如果第二消息不含有任何隐私标签则可以显示第二消息的完整通知。当然,除了上述的隐私标签显示处理的方式外,还可采取其他显示处理方式,本发明实施例对此不进行具体限定。
此外,若在锁屏界面上显示相关通知后,还可在锁屏界面上显示解锁提示信息,以提醒用户进行解锁操作,以进行消息查看。
本发明实施例提供的方法,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
需要说明的是,上述两个实施例的隐私注册在应用服务器端,可以同步用户在不同设备上的隐私设置。同一个用户的隐私消息接收设置可以在用户的多个设备之间实现同步。用户针对同一个联系人在不同应用之间的隐私设置可以在多个设备和多个应用之间同步。
图7是本发明实施例提供的一种消息处理方法的流程图。交互主体为第一
设备、第二设备、应用服务器和推送服务器。以数据包中包括指定用户标识信息、第一消息和第二隐私标签,第二消息携带第一隐私标签为例,参见图7,本发明实施例提供的方法流程包括:
701、第一设备向应用服务器发送数据包,该数据包中至少包括指定用户标识信息、第一消息和第二隐私标签。
在本发明实施例中,第一设备指代消息发送方,既可为智能手机、平板电脑等移动终端、或个人计算机等固定接收设备,也可为社交类应用或即时通讯类应用的服务器。本发明实施例对第一设备的类型不进行具体限定。指定用户标识信息用于指示第一消息的接收方,可为电话号码、某一应用的登录名称、邮箱等等,本发明实施例对指定用户标识信息的形式同样不进行具体限定。
此外,数据包中除包括指定用户标识信息、第一消息和第二隐私标签外,还可包括其他内容。比如,数据包发送时间等等,本发明实施例对此不进行具体限定。在第一设备向应用服务器发送数据包时,既可以有线的方式进行发送,也可以无线的方式进行发送,本发明实施例对此同样不进行具体限定。
在本发明实施例中,第一设备在发送数据包之前,还包括获取用户设置的隐私数据的步骤。针对该步骤,隐私数据可由用户自身按照下述规则进行设置:
规则一、对于任一应用(比如,通信类应用、短信、微信、邮件等)而言,用户可以在应用程序级别将该应用设置为隐私数据,该应用的推送消息一律按隐私消息处理,未解锁时不显示推送消息的具体内容。
规则二、对于联系人(比如,隐私联系人、银行客服、支付宝等)而言,用户可以在联系人级别将上述联系人设置为隐私数据,上述联系人可通过匹配应用程序通讯录、***通讯录、邮箱联系人通讯录获得。该联系人发来的消息,无论是以邮件还是微信等其他通信工具发送的,均按照隐私消息处理。未解锁时不显示推送消息的具体内容。
规则三、对于关键字(比如,交易额、收到支出回执、短信验证码等)而言,用户可以将该关键字设置为隐私数据,上述关键字可以由负责隐私消息处
理的***自动识别。包含上述关键字的推送消息一律按照隐私消息处理,未解锁时不显示推送消息的具体内容。
规则四、对于用户设备在某些时间段(比如,工作时段、聚会时段等),用户设备在某些地点(比如,公司、外面等),通过绑定的可穿戴设备检测到用户与第二设备的位置关系,通过绑定的车载、智能家居等设备的连接关系,选择对于推送消息的不同隐私处理方式。可针对上述的时间段,地点,绑定的可穿戴设备分别判断,也可综合上述因素判断。
当用户按照上述规则设置好隐私数据后,第二设备获取设置好的隐私数据,并将设置好的隐私数据和指定用户标识信息一并上传至应用服务器,以方便应用服务器进行存储。
其中,针对隐私消息的私密程度可设置不同的第二隐私标签。比如,针对银行客服、支付宝客服、涉及交易额、短信验证码等跟个人财产相关的隐私消息,可设置隐私级别最高的第二隐私标签;针对某一应用发送的推送消息可设置隐私级别稍弱的第二隐私标签等等,本发明实施例对此不进行具体限定。可事先由用户自行进行设置并存储在应用服务器上,也可由***自动进行设置,本发明实施例对此同样不进行具体限定。
在本发明实施例中,第一设备在第一消息中***第二隐私标签时,既可在第一消息的首部***,也可在第一消息的尾部***,也可以通过将第一消息中的某一预设的数据位标记或置位实现,本发明实施例对此不进行具体限定。其中,第二隐私标签可以设置为第一消息内容中的某一特定字段,长度可以为一个字节、一个比特、或者为任意长度;位置可以位于第一消息的开头、结尾或中间的任意位置,只要能被消息的接收方识别即可。本发明实施例对第二隐私标签的形式和位置均不进行具体限定。
需要说明的是,参见图8,在执行上述步骤701之前,本发明实施例还包括推送服务注册的过程,具体过程可分为下述四个小步骤。
第一步、第二设备向推送服务器发送指定用户标识信息。
在本发明实施例中,第二设备指代消息接收方。
第二步、推送服务器在接收到指定用户标识信息后,计算指定用户标识信息对应的指定注册身份标识,并将指定注册身份标识发送给第二设备。
针对该步骤,指定注册身份标识可为一个仅包含字母的字符串、或一个数字与字母混合的字符串等,本发明实施例对指定注册身份标识的形式不进行具体限定。推送服务器计算指定用户标识对应的指定注册身份标识时,可参考现有技术实现,此处不再进行赘述。
第三步、第二设备接收到指定注册身份标识后,设置指定用户身份标识与指定注册身份标识之间的对应关系,并向应用服务器发送指定用户标识信息与指定注册身份标识之间的对应关系。
针对该步骤,第二设备在设置指定用户身份标识与指定注册身份标识之间的对应关系时,可生成如上表1中第一行所示的对应表项,即第二设备生成的仅仅是表1中的单条条目(某一行)。表1中所示的整个对应关系表是由多个设备发送的对应表项组成的。应用服务器在接收到第二设备发送的指定用户身份标识与指定注册身份标识之间的对应表项后,将该表项***到如上表1所示的表格中即可。
当然,除上述生成及发送对应关系的方式外,还可采取其他方式,本发明实施例对此不进行具体限定。
第四步、应用服务器存储指定用户身份标识与指定注册身份标识之间的对应关系。
针对该步骤,应用服务器在存储上述对应关系时,可将其存储在内存或闪存等存储介质中,本发明实施例对存储介质的类型不进行具体限定。
702、应用服务器根据指定用户标识信息、用户标识信息和注册身份标识之间的对应关系,确定指定注册身份标识。
在本发明实施例中,应用服务器中存储了用户标识信息和注册身份标识之间的对应关系。随着服务器处理能力的增强,应用服务器中可存储海量的对应
关系,包括成千上万个接收设备发送的用户标识信息和注册身份标识。
其中,应用服务器在根据指定用户标识信息、用户标识信息和注册身份标识之间的对应关系,确定指定注册身份标识时,具体可采取下述方式实现:
根据指定用户标识信息,在用户标识信息和注册身份标识之间的对应关系中进行搜索查找,确定与指定用户标识信息相匹配的注册身份标识(比如,与指定用户标识信息为于同一表项的注册身份标识),将该注册身份标识确定为指定注册身份标识。
需要说明的是,在第一设备和应用服务器执行上述步骤701至步骤702时,第二设备和推送服务器之间还包括下述交互步骤。
在第二设备联网后,第二设备向推送服务器发送存储的注册身份标识;推送服务器在接收到该注册身份标识后,验证该注册身份标识是否合法,得到验证结果;之后,将验证结果返回给第二设备。
在本发明实施例中,推送服务器之所以要对第二设备进行验证,是为了确定第二设备所存储的注册身份标识是否为推送服务器之前亲自授予的。如果该注册身份标识为推送服务器事先计算并返回给第二设备的,则验证该注册身份标识合法,得到包括合法信息的验证结果;将该验证结果返回给第二设备。如果该注册身份标识非推送服务器事先计算并返回给第二设备的,则验证该注册身份标识非法,得到包括非法信息的验证结果;将该验证结果返回给第二设备,提示第二设备注册身份标识验证失败。
当然,除了上述验证注册身份标识的方式外,还可采取其他验证方式,本发明实施例对此不进行具体限定。
703、应用服务器判断第一消息是否为隐私消息;当第一消息为隐私消息时,执行下述步骤704。
在本发明实施例中,应用服务器在判断第一消息是否为隐私消息时,具体可采取下述方式实现:
根据第一消息中是否包含第二隐私标签,确定第一消息是否为隐私消息。
当第一消息中包含第二隐私标签时,确定第一消息为隐私消息,执行下述步骤704;当第一消息中不包含第二隐私标签时,确定第一消息不是隐私消息。
704、当应用服务器判断第一设备发送的第一消息为隐私消息时,根据第一消息生成第二消息,第二消息中携带第一隐私标签。
在本发明实施例中,应用服务器在根据第一消息生成第二消息时,具体可采取下述方法实现:
根据第一消息生成第二消息,并在第二消息中设置第一隐私标签。
其中,第一隐私标签可以设置为第二消息内容中的某一特定字段,长度可以为一个字节、一个比特、或者为任意长度;位置可以位于第二消息的开头、结尾或中间的任意位置,只要能被消息的接收方识别即可。本发明实施例对第二隐私标签的形式和位置均不进行具体限定。
需要说明的是,在第一消息中携带第二隐私标签的情况下,之所以还要在第二消息中设置第一隐私标签是因为可能存在这样的情况:由于第一设备和应用服务器所使用的相关协议可能不同,所以第一隐私标签可能是经过格式变换或经过其他相关处理后的第二隐私标签。第一隐私标签和第二隐私标签的实质作用是一致的,都是对隐私消息进行标记。只不过在不同的设备上格式有所改变。
705、应用服务器根据指定注册身份标识和第二消息,生成数据推送请求。
在本发明实施例中,要实现消息推送(Push Notification)需涉及三个对象:
1、接收设备,接收第二消息并根据消息内容进行相应处理;
2、应用服务器,将第二消息发送给推送服务器;
3、推送服务器,接收来自于应用服务器的数据推送请求,并将该数据推送请求发送至接收设备。
基于上述规则,应用服务器在得到第二消息后,还需生成数据推送请求。其中,数据推送请求中至少包括指定注册身份标识和第二消息。当然,数据推送请求中除包括上述内容外,还可包括其他内容。比如,数据推送请求的生成
时间等等,本发明实施例对此不进行具体限定。
706、应用服务器向推送服务器发送数据推送请求。
在本发明实施例中,应用服务器在发送数据推送请求时,既可在将数据推送请求打包后,以无线或有线的方式发送;还可直接将数据推送请求以无线或有线的方式发送,本发明实施例对此不进行具体限定。
707、推送服务器在接收到该数据推送请求后,根据指定注册身份标识、用户标识信息和注册身份标识之间的对应关系,将该数据推送请求发送至第二设备。
在本发明实施例中,由于推送服务器中存储了用户标识信息和注册身份标识之间的对应关系,所以推送服务器在接收到数据推送请求后,根据指定注册身份标识,便可确定对应的指定用户标识信息。进而,根据指定用户标识信息可确定将第二消息发送至哪一个接收设备。
其中,推送服务器在根据指定注册身份标识、用户标识信息和注册身份标识之间的对应关系,将数据推送请求发送至第二设备时,具体可采取下述方式实现:
根据指定注册身份标识在用户标识信息和注册身份标识之间的对应关系中进行搜索查找,确定与指定注册身份标识相匹配的指定用户标识信息;根据指定用户标识信息将数据推送请求发送至第二设备。
708、第二设备在接收到该数据推送请求后,根据所述第一隐私标签在通知界面上显示所述第二消息的通知。
其中,在根据第一隐私标签在通知界面上显示第二消息的通知时,具体可采取下述方式实现:
在第二设备的通知界面上不显示第二消息的通知预览。其中,不显示第二消息的通知预览指代:在显示第二消息的通知时,不显示第二消息的具体内容,仅显示不包含第二消息的具体内容的概要通知信息。
在本发明实施例中,第二设备在接收到第二消息后,检查第二消息中是否
包含隐私标签。因为此时第二消息中包括第一隐私标签,所以第二设备在显示第二消息的通知时,还需先对第二消息进行处理。其中,第二消息中可能包括多项较为敏感的隐私内容。比如,当第二消息为一个网上支付验证码的下发消息时,第二消息中可能包括金额、银行***、验证码等多项隐私内容。
在该种情况下,既可选择将第二消息中的部分隐私内容进行替换、隐藏或修改,使得第二消息在通知界面上进行显示时仅包含部分隐私内容;还可选择将第二消息中的全部隐私内容进行替换、隐藏或修改,使得第二消息在通知界面上进行显示时不包含任意隐私内容,此时第二消息中无任何敏感词汇。
优选地,为了防止用户隐私的泄露,可在通知界面上不显示第二消息的通知预览,也即不显示任何相关的敏感词汇。仅显示“您有**条新消息”、“您有新的转账记录”等形式的概要通知信息,本发明实施例对此不进行具体限定。
综上所述,第二设备在接收到第二消息后,针对第二消息中的不同级别的隐私标签,可以针对不同级别的隐私标签进行不同的消息通知显示。例如:如果第二消息含有最高级别的隐私标签,则仅显示给用户“你有一条新消息”,消息的发送方,发送方使用的应用,发送时间,内容等均不显示,由用户使用第二设备自行查看;如果第二消息含有隐私级别稍弱的隐私标签,则显示给用户“你有一条来自张三的微信消息”,但是隐藏消息的具体内容;如果第二消息不含有任何隐私标签则可以显示第二消息的完整通知。当然,除了上述的隐私标签显示处理的方式外,还可采取其他显示处理方式,本发明实施例对此不进行具体限定。
此外,若在锁屏界面显示相关通知后,还可在锁屏界面上显示解锁提示信息,以提醒用户进行解锁操作,以进行消息查看。
本发明实施例提供的方法,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二
消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
需要说明的是,第一设备除了可向应用服务器发送不携带第二隐私标签的第一消息或携带第二隐私标签的第一消息外,还可向应用服务器发送第二消息,该第二消息中不包含第一消息中的任意隐私内容,或包含第一消息中的部分隐私内容,具体过程如下:生成第一消息;判断第一消息是否为隐私消息;当第一消息为隐私消息时,根据第一消息生成第二消息,第二消息不包含第一消息中至少一项隐私内容;向应用服务器发送第二消息,以便于第二设备在接收到应用服务器转发的第二消息后,在通知界面显示第二消息中的通知。其中,每一步的详细解释说明,可参见上述图4、图6和图7所对应的详细实施例部分,此处不再赘述。
图9是本发明实施例提供的一种消息处理方法的流程图。交互主体为第一设备、第二设备、应用服务器、推送服务器和代理设备。以数据包中包括指定用户标识信息和第一消息,第二消息与第一消息包含的内容相同为例,参见图9,本发明实施例提供的方法流程包括:
901、第一设备向应用服务器发送数据包,该数据包中至少包括指定用户标识信息和第一消息。
在本发明实施例中,第一设备指代消息发送方,可为智能手机、平板电脑等移动终端、或个人计算机等固定接收设备,也可为社交类应用或即时通讯类应用的服务器。本发明实施例对第一设备的类型不进行具体限定。指定用户标识信息用于指示第一消息的接收方,可为电话号码、某一应用的登录名称、邮箱等等,本发明实施例对指定用户标识信息的形式同样不进行具体限定。
此外,数据包中除包括指定用户标识信息和第一消息外,还可包括其他内容。比如,隐私标签、数据包发送时间等等,本发明实施例对此不进行具体限定。在第一设备向应用服务器发送数据包时,既可以有线的方式进行发送,也可以无线的方式进行发送,本发明实施例对此同样不进行具体限定。
需要说明的是,参见图8,在执行上述步骤901之前,本发明实施例还包括推送服务注册的过程,具体过程可分为下述四个小步骤。
第一步、第二设备向推送服务器发送指定用户标识信息。
在本发明实施例中,第二设备指代消息接收方。
第二步、推送服务器在接收到指定用户标识信息后,计算指定用户标识信息对应的指定注册身份标识,并将指定注册身份标识发送给第二设备。
针对该步骤,指定注册身份标识可为一个仅包含字母的字符串、或一个数字与字母混合的字符串等,本发明实施例对指定注册身份标识的形式不进行具体限定。推送服务器计算指定用户标识对应的指定注册身份标识时,可参考现有技术实现,此处不再进行赘述。
第三步、第二设备接收到指定注册身份标识后,设置指定用户身份标识与指定注册身份标识之间的对应关系,并向应用服务器发送指定用户标识信息与指定注册身份标识之间的对应关系。
针对该步骤,第二设备在设置指定用户身份标识与指定注册身份标识之间的对应关系时,可生成如上表1中第一行所示的对应表项,即第二设备生成的仅仅是表1中的单条条目(某一行)。表1中所示的整个对应关系表是由多个设备发送的对应表项组成的。应用服务器在接收到第二设备发送的指定用户身份标识与指定注册身份标识之间的对应表项后,将该表项***到如上表1所示的表格即可。
当然,除上述生成及发送对应关系的方式外,还可采取其他方式,本发明实施例对此不进行具体限定。需要说明的是,上述表1(整张表格)的生成和存储过程均可在应用服务器上实现,还可在推送服务器上实现,本发明实施例
对此不进行具体限定。本发明实施例仅以应用服务器生成和存储上述表1为例进行说明。
第四步、应用服务器存储指定用户身份标识与指定注册身份标识之间的对应关系。
针对该步骤,应用服务器在存储上述对应关系时,可将其存储在内存或闪存等存储介质中,本发明实施例对存储介质的类型不进行具体限定。
902、应用服务器根据指定用户标识信息、用户标识信息和注册身份标识之间的对应关系,确定指定注册身份标识。
在本发明实施例中,应用服务器中存储了用户标识信息和注册身份标识之间的对应关系。随着服务器处理能力的增强,应用服务器中可存储海量的对应关系,包括成千上万个接收设备发送的用户标识信息和注册身份标识。
其中,应用服务器在根据指定用户标识信息、用户标识信息和注册身份标识之间的对应关系,确定指定注册身份标识时,具体可采取下述方式实现:
根据指定用户标识信息,在用户标识信息和注册身份标识之间的对应关系中进行搜索查找,确定与指定用户标识信息相匹配的注册身份标识(比如,与指定用户标识信息为于同一表项的注册身份标识),将该注册身份标识确定为指定注册身份标识。
需要说明的是,在第一设备和应用服务器执行上述步骤901至步骤902时,第二设备和推送服务器之间还包括下述交互步骤。
在第二设备联网后,第二设备向推送服务器发送存储的注册身份标识;推送服务器在接收到该注册身份标识后,验证该注册身份标识是否合法,得到验证结果;之后,将验证结果返回给第二设备。
在本发明实施例中,推送服务器之所以要对第二设备进行验证,是为了确定第二设备所存储的注册身份标识是否为推送服务器之前亲自授予的。如果该注册身份标识为推送服务器事先计算并返回给第二设备的,则验证该注册身份标识合法,得到包括合法信息的验证结果;将该验证结果返回给第二设备。如
果该注册身份标识非推送服务器事先计算并返回给第二设备的,则验证该注册身份标识非法,得到包括非法信息的验证结果;将该验证结果返回给第二设备,提示第二设备注册身份标识验证失败。
当然,除了上述验证注册身份标识的方式外,还可采取其他验证方式,本发明实施例对此不进行具体限定。
903、应用服务器根据指定注册身份标识和第二消息,生成数据推送请求。
在本发明实施例中,要实现消息推送(Push Notification)需涉及三个对象:
1、接收设备,接收第二消息并根据消息内容进行相应处理;
2、应用服务器,将第二消息发送给推送服务器;
3、推送服务器,接收来自于应用服务器的数据推送请求,并将该数据推送请求发送至接收设备。
基于上述规则,应用服务器在得到第二消息后,还需生成数据推送请求。其中,数据推送请求中至少包括指定注册身份标识和第二消息。当然,数据推送请求中除包括上述内容外,还可包括其他内容。比如,数据推送请求的生成时间等等,本发明实施例对此不进行具体限定。
904、应用服务器向推送服务器发送数据推送请求。
在本发明实施例中,应用服务器在发送数据推送请求时,既可在将数据推送请求打包后,以无线或有线的方式发送;还可直接将数据推送请求以无线或有线的方式发送,本发明实施例对此不进行具体限定。
905、推送服务器在接收到该数据推送请求后,根据指定注册身份标识、用户标识信息和注册身份标识之间的对应关系,将该数据推送请求发送至第二设备。
在本发明实施例中,由于推送服务器中存储了用户标识信息和注册身份标识之间的对应关系,所以推送服务器在接收到数据推送请求后,根据指定注册身份标识,便可确定对应的指定用户标识信息。进而,根据指定用户标识信息可确定将第二消息发送至哪一个接收设备。
其中,推送服务器在根据指定注册身份标识、用户标识信息和注册身份标识之间的对应关系,将数据推送请求发送至第二设备时,具体可采取下述方式实现:
根据指定注册身份标识在用户标识信息和注册身份标识之间的对应关系中进行搜索查找,确定与指定注册身份标识相匹配的指定用户标识信息;根据指定用户标识信息将数据推送请求发送至第二设备。
906、第二设备在接收到该数据推送请求后,向代理设备发送第二消息。
其中,代理设备(agent)为第二设备操作***的推送服务。代理设备上存储有用户的隐私数据。其中,隐私数据可由用户自身按照下述规则进行设置:
规则一、对于任一应用(比如,通信类应用、短信、微信、邮件等)而言,用户可以在应用程序级别将该应用设置为隐私数据,该应用的推送消息一律按隐私消息处理,未解锁时不显示推送消息的具体内容。
规则二、对于联系人(比如,隐私联系人、银行客服、支付宝等)而言,用户可以在联系人级别将上述联系人设置为隐私数据,上述联系人可通过匹配应用程序通讯录、***通讯录、邮箱联系人通讯录获得。该联系人发来的消息,无论是以邮件还是微信等其他通信工具发送的,均按照隐私消息处理。未解锁时不显示推送消息的具体内容。
规则三、对于关键字(比如,交易额、收到支出回执、短信验证码等)而言,用户可以将该关键字设置为隐私数据,上述关键字可以由负责隐私消息处理的***自动识别。包含上述关键字的推送消息一律按照隐私消息处理,未解锁时不显示推送消息的具体内容。
规则四、对于用户设备在某些时间段(比如,工作时段、聚会时段等),用户设备在某些地点(比如,公司、外面等),通过绑定的可穿戴设备检测到用户与第二设备的位置关系,通过绑定的车载、智能家居等设备的连接关系,选择对于推送消息的不同隐私处理方式。可针对上述的时间段,地点,绑定的可穿戴设备分别判断,也可综合上述因素判断。
907、代理设备根据存储的隐私数据,判断第二消息是否为隐私消息。
在本发明实施例中,代理设备在根据存储的隐私数据,判断第二消息是否为隐私消息时,具体可采取下述方式实现:
判断第二消息是否与隐私数据中的任一数据项相匹配;如果第二消息与隐私数据中的任一数据项相匹配,则确定第二消息是隐私消息;如果第二消息与隐私数据中的任一数据项均不匹配,则确定第二消息不是隐私消息,处理流程至此结束。
以隐私数据为较为敏感的关键字(比如,交易额、收到支出回执、短信验证码等)为例,则可将第一消息进行分词处理,得到各个分词;将各个分词分别与隐私数据进行比对;如果任一分词与隐私数据中的一个关键字相匹配,则确定第一消息为隐私消息。
针对其他类型的隐私数据,处理过程与上述过程类似,此处不再赘述。
908、当代理设备判断第二消息为隐私消息时,将第二消息进行处理,并向第二设备发送处理后的第二消息。
其中,第二消息中可能包括多项较为敏感的隐私内容。比如,当第二消息为一个网上支付验证码的下发消息时,第二消息中可能包括金额、银行***、验证码等多项隐私内容。
在该种情况下,既可选择将第二消息中的部分隐私内容进行替换、隐藏或修改,使得在通知界面上进行显示时仅包含部分隐私内容;还可选择将第二消息中的全部隐私内容进行替换、隐藏或修改,使得在通知界面上进行显示时不包含任意隐私内容,此时第二消息中无任何敏感词汇。
909、第二设备在通知界面上显示处理后的第二消息的通知。
在本发明实施例中,第二设备在通知界面上显示处理后的第二消息的通知时,不显示第二消息的通知预览。其中,不显示第二消息的通知预览指代:在显示第二消息的通知时,不显示第二消息的具体内容,仅显示不包含第二消息的具体内容的概要通知信息。
优选地,为了防止用户隐私的泄露,可在通知界面上不显示第二消息的通知预览,也即不显示任何相关的敏感词汇。仅显示“您有**条新消息”、“您有新的转账记录”等形式的概要通知信息,本发明实施例对此不进行具体限定。
此外,在显示通用消息后,还可在锁屏界面上显示解锁提示信息,以提醒用户进行解锁操作,以进行消息查看。
本发明实施例提供的方法,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
图10是本发明实施例提供的一种消息处理装置的结构示意图。该装置应用于应用服务器,参见图10,该装置包括:第一消息接收模块1001、隐私消息判断模块1002、第二消息生成模块1003、第二消息发送模块1004。
其中,第一消息接收模块1001,用于接收第一设备发送给第二设备的第一消息;隐私消息判断模块1002与第一消息接收模块1001连接,用于判断第一消息是否为隐私消息;第二消息生成模块1003与隐私消息判断模块1002连接,用于当第一消息为隐私消息时,根据第一消息生成第二消息,第二消息中携带第一隐私标签;第二消息发送模块1004与第二消息生成模块1003连接,用于向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。
可选地,隐私消息判断模块,用于根据第一消息中包含的隐私数据确定第一消息为隐私消息;
相应地,第二消息生成模块,用于根据第一消息生成第二消息,并在第二消息中设置第一隐私标签。
可选地,隐私消息判断模块,用于根据第一消息中包含的第二隐私标签确定第一消息为隐私消息;
相应地,第二消息生成模块,用于根据第一消息生成第二消息,并在第二消息中设置第一隐私标签。
可选地,第二消息发送模块,用于向第二设备发送第二消息,以便于第二设备在接收到第二消息后,在第二设备的通知界面上不显示第二消息的通知预览。
本发明实施例提供的装置,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
图11是本发明实施例提供的一种消息处理装置的结构示意图。该装置应用于应用服务器,参见图11,该装置包括:第一消息接收模块1101、隐私消息判断模块1102、第二消息生成模块1103、第二消息发送模块1104。第一消息接收模块1101,用于接收第一设备发送给第二设备的第一消息;隐私消息判断模块1102与第一消息接收模块1101连接,用于判断第一消息是否为隐私消息;第二消息生成模块1103与隐私消息判断模块1102连接,用于当第一消息为隐私消息时,根据第一消息生成第二消息,第二消息不包含第一消息中至少一项隐私内容;第二消息发送模块1104与第二消息生成模块1103连接,用于
向第二设备发送第二消息,以便于第二设备在接收到第二消息后,在通知界面上显示第二消息的通知。
可选地,隐私消息判断模块,用于根据第一消息中包含的隐私数据确定第一消息为隐私消息;
相应地,第二消息生成模块,用于去除第一消息中的至少一项隐私内容,得到第二消息。
本发明实施例提供的装置,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电
图12是本发明实施例提供的一种消息处理装置的结构示意图。该装置应用于第二设备,参见图12,该装置包括:第二消息接收模块1201、隐私标签判断模块1202、第一显示模块1203、第二显示模块1204。
其中,第二消息接收模块1201,用于接收发送给第二设备的第二消息;隐私标签判断模块1202与连接,用于判断第二消息中是否包含隐私标签;第一显示模块1203与连接,用于当第二消息中包含隐私标签时,第二设备在通知界面上显示第二消息的通知时,不显示第二消息的通知预览;第二显示模块1204与连接,用于当第二消息中不包含隐私标签时,在第二消息的通知界面上根据用户的设置显示第二消息的通知。
可选地,第一显示模块,用于在显示第二消息的通知时,不显示第二消息的具体内容,仅显示不包含第二消息的具体内容的概要通知信息。
本发明实施例提供的装置,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
图13是本发明实施例提供的一种终端,该终端可以用于执行上述实施例中第二设备所执行的消息处理方法。参见图13,该终端1300包括:
RF(Radio Frequency,射频)电路110、包括有一个或一个以上计算机可读存储介质的存储器120、输入单元130、显示单元140、传感器150、音频电路160、WiFi(Wireless Fidelity,无线保真)模块170、包括有一个或者一个以上处理核心的处理器180、以及电源190等部件。本领域技术人员可以理解,图13中示出的终端结构并不构成对终端的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。其中:
RF电路110可用于收发信息或通话过程中,信号的接收和发送,特别地,将基站的下行信息接收后,交由一个或者一个以上处理器180处理;另外,将涉及上行的数据发送给基站。通常,RF电路110包括但不限于天线、至少一个放大器、调谐器、一个或多个振荡器、用户身份模块(SIM)卡、收发信机、耦合器、LNA(Low Noise Amplifier,低噪声放大器)、双工器等。此外,RF电路110还可以通过无线通信与网络和其他设备通信。无线通信可以使用任一通信标准或协议,包括但不限于GSM(Global System of Mobile communication,全球移动通讯***)、GPRS(General Packet Radio Service,通用分组无线服务)、CDMA(Code Division Multiple Access,码分多址)、WCDMA(Wideband Code
Division Multiple Access,宽带码分多址)、LTE(Long Term Evolution,长期演进)、电子邮件、SMS(Short Messaging Service,短消息服务)等。
存储器120可用于存储软件程序以及模块,处理器180通过运行存储在存储器120的软件程序以及模块,从而执行各种功能应用以及数据处理。存储器120可主要包括存储程序区和存储数据区,其中,存储程序区可存储操作***、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等;存储数据区可存储根据终端1300的使用所创建的数据(比如音频数据、电话本等)等。此外,存储器120可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。相应地,存储器120还可以包括存储器控制器,以提供处理器180和输入单元130对存储器120的访问。
输入单元130可用于接收输入的数字或字符信息,以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。具体地,输入单元130可包括触敏表面131以及其他输入设备132。触敏表面131,也称为触摸显示屏或者触控板,可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触敏表面131上或在触敏表面131附近的操作),并根据预先设定的程式驱动相应的连接装置。可选的,触敏表面131可包括触摸检测装置和触摸控制器两个部分。其中,触摸检测装置检测用户的触摸方位,并检测触摸操作带来的信号,将信号传送给触摸控制器;触摸控制器从触摸检测装置上接收触摸信息,并将它转换成触点坐标,再送给处理器180,并能接收处理器180发来的命令并加以执行。此外,可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触敏表面131。除了触敏表面131,输入单元130还可以包括其他输入设备132。具体地,其他输入设备132可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种。
显示单元140可用于显示由用户输入的信息或提供给用户的信息以及终端
1300的各种图形用户接口,这些图形用户接口可以由图形、文本、图标、视频和其任意组合来构成。显示单元140可包括显示面板141,可选的,可以采用LCD(Liquid Crystal Display,液晶显示器)、OLED(Organic Light-Emitting Diode,有机发光二极管)等形式来配置显示面板141。进一步的,触敏表面131可覆盖显示面板141,当触敏表面131检测到在其上或附近的触摸操作后,传送给处理器180以确定触摸事件的类型,随后处理器180根据触摸事件的类型在显示面板141上提供相应的视觉输出。虽然在图13中,触敏表面131与显示面板141是作为两个独立的部件来实现输入和输出功能,但是在某些实施例中,可以将触敏表面131与显示面板141集成而实现输入和输出功能。
终端1300还可包括至少一种传感器150,比如光传感器、运动传感器以及其他传感器。具体地,光传感器可包括环境光传感器及接近传感器,其中,环境光传感器可根据环境光线的明暗来调节显示面板141的亮度,接近传感器可在终端1300移动到耳边时,关闭显示面板141和/或背光。作为运动传感器的一种,重力加速度传感器可检测各个方向上(一般为三轴)加速度的大小,静止时可检测出重力的大小及方向,可用于识别手机姿态的应用(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等;至于终端1300还可配置的陀螺仪、气压计、湿度计、温度计、红外线传感器等其他传感器,在此不再赘述。
音频电路160、扬声器161,传声器162可提供用户与终端1300之间的音频接口。音频电路160可将接收到的音频数据转换后的电信号,传输到扬声器161,由扬声器161转换为声音信号输出;另一方面,传声器162将收集的声音信号转换为电信号,由音频电路160接收后转换为音频数据,再将音频数据输出处理器180处理后,经RF电路110以发送给比如另一终端,或者将音频数据输出至存储器120以便进一步处理。音频电路160还可能包括耳塞插孔,以提供外设耳机与终端1300的通信。
WiFi属于短距离无线传输技术,终端1300通过WiFi模块170可以帮助用
户收发电子邮件、浏览网页和访问流式媒体等,它为用户提供了无线的宽带互联网访问。
处理器180是终端1300的控制中心,利用各种接口和线路连接整个手机的各个部分,通过运行或执行存储在存储器120内的软件程序和/或模块,以及调用存储在存储器120内的数据,执行终端1300的各种功能和处理数据,从而对手机进行整体监控。可选的,处理器180可包括一个或多个处理核心;优选的,处理器180可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作***、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器180中。
终端1300还包括给各个部件供电的电源190(比如电池),优选的,电源可以通过电源管理***与处理器180逻辑相连,从而通过电源管理***实现管理充电、放电、以及功耗管理等功能。电源190还可以包括一个或一个以上的直流或交流电源、再充电***、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。
尽管未示出,终端1300还可以包括摄像头、蓝牙模块等,在此不再赘述。具体在本实施例中,终端的显示单元是触摸屏显示器,终端还包括有存储器,以及一个或者一个以上的程序,其中一个或者一个以上程序存储于存储器中,且经配置以由一个或者一个以上处理器执行述一个或者一个以上程序包含用于进行以下操作的指令:
接收第一设备发送给第二设备的第一消息;
判断第一消息是否为隐私消息;
如果第一消息为隐私消息,则根据第一消息生成第二消息,第二消息中携带第一隐私标签;
向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。
可选地,判断第一消息是否为隐私消息,包括:
根据第一消息中包含的隐私数据确定第一消息为隐私消息;
相应地,根据第一消息生成第二消息,包括:
根据第一消息生成第二消息,并在第二消息中设置第一隐私标签。
可选地,判断第一消息是否为隐私消息,包括:
根据第一消息中包含的第二隐私标签确定第一消息为隐私消息;
相应地,根据第一消息生成第二消息,包括:
根据第一消息生成第二消息,并在第二消息中设置第一隐私标签。
可选地,根据第一隐私标签在通知界面上显示第二消息的通知,包括:
在第二设备的通知界面上不显示第二消息的通知预览。
本发明实施例提供的终端,应用服务器在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
本实施例提供了一种应用服务器,该应用服务器可以用于执行上述实施例中提供的消息处理方法。参见图14,该服务器1400可因配置或性能不同而产生比较大的差异,可以包括一个或一个以***处理器(central processing units,CPU)1422(例如,一个或一个以上处理器)和存储器1432,一个或一个以上存储应用程序1442或数据1444的存储介质1430(例如一个或一个以上海量存储设备)。其中,存储器1432和存储介质1430可以是短暂存储或持久存储。存储在存储介质1430的程序可以包括一个或一个以上模块(图示没标出),每个模块可以包括对服务器中的一系列指令操作。更进一步地,中央处
理器1422可以设置为与存储介质1430通信,在服务器1400上执行存储介质1430中的一系列指令操作。
服务器1400还可以包括一个或一个以上电源1426,一个或一个以上有线或无线网络接口1450,一个或一个以上输入输出接口1458,和/或,一个或一个以上操作***1441,例如Windows ServerTM,Mac OS XTM,UnixTM,LinuxTM,FreeBSDTM等等。
具体在本实施例中,经配置以由一个或者一个以上处理器执行述一个或者一个以上程序包含用于进行以下操作的指令:
接收发送给第二设备的第二消息;
判断所述第二消息中是否包含隐私标签;
当所述第二消息中包含隐私标签时,所述第二设备在通知界面上显示所述第二消息的通知时,不显示所述第二消息的通知预览;
当所述第二消息中不包含隐私标签时,在所述第二消息的通知界面上根据用户的设置显示所述第二消息的通知。
可选地,所述不显示所述第二消息的通知预览,包括:
在显示所述第二消息的通知时,不显示所述第二消息的具体内容,仅显示不包含所述第二消息的具体内容的概要通知信息。
本发明实施例提供的服务器,在接收到发送给第二设备的第一消息后,判断第一消息是否为隐私消息;如果第一消息为隐私消息,则根据第一消息生成携带第一隐私标签的第二消息;之后,向第二设备发送第二消息,以便于第二设备在接收到第二消息后,根据第一隐私标签在通知界面上显示第二消息的通知。在第二设备接收到第二消息后,由于可根据第二消息是否携带第一隐私标签来显示第二消息,因此达到了第二设备显示不同粒度消息内容的目的,不但可使用户及时获知重要通知消息,还防止了用户隐私泄露,提升了用户体验度和设备易用性;另外,无需应用程序一直在后台运行,较为省电。
需要说明的是:上述实施例提供的消息处理装置在进行消息处理时,仅以
上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将装置的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。另外,上述实施例提供的消息处理装置与消息处理方法实施例属于同一构思,其具体实现过程详见方法实施例,这里不再赘述。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成,也可以通过程序来指令相关的硬件完成,所述的程序可以存储于一种计算机可读存储介质中,上述提到的存储介质可以是只读存储器,磁盘或光盘等。
以上所述仅为本发明的较佳实施例,并不用以限制本发明,凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。
Claims (16)
- 一种消息处理方法,其特征在于,所述方法包括:接收第一设备发送给第二设备的第一消息;判断所述第一消息是否为隐私消息;如果所述第一消息为隐私消息,则根据所述第一消息生成第二消息,所述第二消息中携带第一隐私标签;向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,根据所述第一隐私标签在通知界面上显示所述第二消息的通知。
- 根据权利要求1所述的方法,其特征在于,所述判断所述第一消息是否为隐私消息,包括:根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;相应地,所述根据所述第一消息生成第二消息,包括:根据所述第一消息生成所述第二消息,并在所述第二消息中设置所述第一隐私标签。
- 根据权利要求1所述的方法,其特征在于,所述判断所述第一消息是否为隐私消息,包括:根据所述第一消息中包含的第二隐私标签确定所述第一消息为隐私消息;相应地,所述根据所述第一消息生成第二消息,包括:根据所述第一消息生成所述第二消息,并在所述第二消息中设置所述第一隐私标签。
- 根据权利要求1-3中任一权利要求所述的方法,所述根据所述第一隐私标签在通知界面上显示所述第二消息的通知,包括:在所述第二设备的通知界面上不显示所述第二消息的通知预览。
- 一种消息处理方法,其特征在于,所述方法包括:接收第一设备发送给第二设备的第一消息;判断所述第一消息是否为隐私消息;如果所述第一消息为隐私消息,则根据所述第一消息生成第二消息,所述第二消息不包含所述第一消息中至少一项隐私内容;向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,在通知界面上显示所述第二消息的通知。
- 根据权利要求5所述的方法,其特征在于,所述判断所述第一消息是否为隐私消息,包括:根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;相应地,所述根据所述第一消息生成第二消息,包括:去除所述第一消息中的至少一项隐私内容,得到所述第二消息。
- 一种消息处理方法,其特征在于,所述方法包括:接收发送给第二设备的第二消息;判断所述第二消息中是否包含隐私标签;当所述第二消息中包含隐私标签时,所述第二设备在通知界面上显示所述第二消息的通知时,不显示所述第二消息的通知预览;当所述第二消息中不包含隐私标签时,在所述第二消息的通知界面上根据用户的设置显示所述第二消息的通知。
- 根据权利要求7所述的方法,其特征在于,所述不显示所述第二消息的通知预览,包括:在显示所述第二消息的通知时,不显示所述第二消息的具体内容,仅显示 不包含所述第二消息的具体内容的概要通知信息。
- 一种消息处理装置,其特征在于,所述装置包括:第一消息接收模块,用于接收第一设备发送给第二设备的第一消息;隐私消息判断模块,用于判断所述第一消息是否为隐私消息;第二消息生成模块,用于当所述第一消息为隐私消息时,根据所述第一消息生成第二消息,所述第二消息中携带第一隐私标签;第二消息发送模块,用于向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,根据所述第一隐私标签在通知界面上显示所述第二消息的通知。
- 根据权利要求9所述的装置,其特征在于,所述隐私消息判断模块,用于根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;相应地,所述第二消息生成模块,用于根据所述第一消息生成所述第二消息,并在所述第二消息中设置所述第一隐私标签。
- 根据权利要求9所述的装置,其特征在于,所述隐私消息判断模块,用于根据所述第一消息中包含的第二隐私标签确定所述第一消息为隐私消息;相应地,所述第二消息生成模块,用于根据所述第一消息生成所述第二消息,并在所述第二消息中设置所述第一隐私标签。
- 根据权利要求9-11中任一权利要求所述的装置,所述第二消息发送模块,用于向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,在所述第二设备的通知界面上不显示所述第二消息的通知预览。
- 一种消息处理装置,其特征在于,所述装置包括:第一消息接收模块,用于接收第一设备发送给第二设备的第一消息;隐私消息判断模块,用于判断所述第一消息是否为隐私消息;第二消息生成模块,用于当所述第一消息为隐私消息时,根据所述第一消息生成第二消息,所述第二消息不包含所述第一消息中至少一项隐私内容;第二消息发送模块,用于向所述第二设备发送所述第二消息,以便于所述第二设备在接收到所述第二消息后,在通知界面上显示所述第二消息的通知。
- 根据权利要求13所述的装置,其特征在于,所述隐私消息判断模块,用于根据所述第一消息中包含的隐私数据确定所述第一消息为隐私消息;相应地,所述第二消息生成模块,用于去除所述第一消息中的至少一项隐私内容,得到所述第二消息。
- 一种消息处理装置,其特征在于,所述装置包括:第二消息接收模块,用于接收发送给第二设备的第二消息;隐私标签判断模块,用于判断所述第二消息中是否包含隐私标签;第一显示模块,用于当所述第二消息中包含隐私标签时,所述第二设备在通知界面上显示所述第二消息的通知时,不显示所述第二消息的通知预览;第二显示模块,用于当所述第二消息中不包含隐私标签时,在所述第二消息的通知界面上根据用户的设置显示所述第二消息的通知。
- 根据权利要求15所述的装置,其特征在于,所述第一显示模块,用于在显示所述第二消息的通知时,不显示所述第二消息的具体内容,仅显示不包含所述第二消息的具体内容的概要通知信息。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2014/092524 WO2016082194A1 (zh) | 2014-11-28 | 2014-11-28 | 消息处理方法及装置 |
EP14906889.2A EP3200487B1 (en) | 2014-11-28 | 2014-11-28 | Message processing method and apparatus |
US15/521,160 US10187855B2 (en) | 2014-11-28 | 2014-11-28 | Message processing method and apparatus |
CN201480059535.4A CN105900466B (zh) | 2014-11-28 | 2014-11-28 | 消息处理方法及装置 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2014/092524 WO2016082194A1 (zh) | 2014-11-28 | 2014-11-28 | 消息处理方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016082194A1 true WO2016082194A1 (zh) | 2016-06-02 |
Family
ID=56073388
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/092524 WO2016082194A1 (zh) | 2014-11-28 | 2014-11-28 | 消息处理方法及装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10187855B2 (zh) |
EP (1) | EP3200487B1 (zh) |
CN (1) | CN105900466B (zh) |
WO (1) | WO2016082194A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2559830A (en) * | 2017-02-17 | 2018-08-22 | Google Llc | Transitioning between private and non-private state |
US11144668B2 (en) * | 2019-08-15 | 2021-10-12 | International Business Machines Corporation | Cognitively hiding sensitive content on a computing device |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104144110B (zh) * | 2014-01-24 | 2016-11-09 | 腾讯科技(深圳)有限公司 | 推送消息的方法和*** |
US10417447B2 (en) * | 2015-06-15 | 2019-09-17 | Arris Enterprises Llc | Selective display of private user information |
KR101835588B1 (ko) * | 2016-05-24 | 2018-03-07 | 라인 가부시키가이샤 | 메시지 제공 방법을 실행하기 위하여 기록 매체에 저장된 컴퓨터 프로그램 및 방법 |
US20210366270A1 (en) * | 2018-01-18 | 2021-11-25 | Hewlett-Packard Development Company, L.P. | Learned quiet times for digital assistants |
US10374994B1 (en) * | 2018-02-21 | 2019-08-06 | King.Com Ltd. | Messaging system |
CN109802994B (zh) * | 2018-12-13 | 2022-03-01 | 平安科技(深圳)有限公司 | 一种基于内容分发网络的消息推送方法及*** |
CN109842611B (zh) * | 2018-12-14 | 2023-04-18 | 平安科技(深圳)有限公司 | 身份验证方法、装置、计算机设备和存储介质 |
CN109819026B (zh) * | 2019-01-21 | 2021-12-24 | 北京百度网讯科技有限公司 | 用于传输信息的方法及装置 |
CN110098845B (zh) * | 2019-05-10 | 2023-06-06 | 努比亚技术有限公司 | 消息处理方法、可穿戴设备、移动终端及可读存储介质 |
CN110781513B (zh) * | 2019-09-17 | 2024-05-03 | 上海掌门科技有限公司 | 一种信息显示方法与设备 |
WO2021077353A1 (en) * | 2019-10-24 | 2021-04-29 | Citrix Systems, Inc. | Content protection in electronic messaging systems |
CN110958315A (zh) * | 2019-11-28 | 2020-04-03 | 上海掌门科技有限公司 | 一种呈现消息通知的方法与设备 |
CN111490979B (zh) * | 2020-03-27 | 2022-03-15 | 广州酷狗计算机科技有限公司 | 信息交互方法、装置及存储介质 |
CN113886295A (zh) * | 2020-07-02 | 2022-01-04 | 北京瀚海云星科技有限公司 | 一种标签数据高效且低延时的传输方法及相关装置、*** |
CN112187879A (zh) * | 2020-09-10 | 2021-01-05 | 南京酷派软件技术有限公司 | 通知消息的控制方法、装置、存储介质及终端 |
US11990116B1 (en) * | 2020-09-22 | 2024-05-21 | Amazon Technologies, Inc. | Dynamically rendered notifications and announcements |
CN112380588A (zh) * | 2020-11-17 | 2021-02-19 | 惠州Tcl移动通信有限公司 | 隐私信息显示方法、装置、存储介质及移动终端 |
CN113360231A (zh) * | 2021-05-31 | 2021-09-07 | 北京达佳互联信息技术有限公司 | 提示信息的展示方法、装置以及电子设备 |
CN114374545B (zh) * | 2021-12-21 | 2024-05-14 | 北京北信源软件股份有限公司 | 防止消息泄露的方法、服务器、装置和电子设备 |
CN116095224B (zh) * | 2022-08-31 | 2023-10-31 | 荣耀终端有限公司 | 通知显示方法和终端设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102752730A (zh) * | 2012-07-19 | 2012-10-24 | 腾讯科技(深圳)有限公司 | 消息处理的方法及装置 |
CN103428652A (zh) * | 2013-08-06 | 2013-12-04 | 北京华恒铭圣科技发展有限责任公司 | 一种手机信息推送方法及装置 |
CN103561152A (zh) * | 2013-11-05 | 2014-02-05 | 广东欧珀移动通信有限公司 | 一种推送消息处理方法和移动终端 |
CN103595766A (zh) * | 2013-10-23 | 2014-02-19 | 北京奇虎科技有限公司 | 实现扩展应用程序的推送通知的方法及装置 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040143632A1 (en) * | 2003-01-18 | 2004-07-22 | International Business Machines Corporation | Method and system for publication of instant messaging privacy codes |
US7917589B2 (en) * | 2006-08-24 | 2011-03-29 | International Business Machines Corporation | Instant messages with privacy notices |
CN103002124B (zh) * | 2012-11-01 | 2015-09-02 | 小米科技有限责任公司 | 一种通信数据的处理方法、装置 |
CN103064585B (zh) | 2012-12-24 | 2017-10-17 | 东莞宇龙通信科技有限公司 | 终端解锁的方法及终端 |
US20140256288A1 (en) | 2013-03-11 | 2014-09-11 | International Business Machines Corporation | On-Screen Notification Privacy and Confidentiality in Personal Devices |
CN104125141B (zh) * | 2013-04-28 | 2017-03-01 | 腾讯科技(深圳)有限公司 | 一种通知消息的推送方法、服务器及*** |
US20150007351A1 (en) * | 2013-06-27 | 2015-01-01 | Maher Janajri | Mobile Messaging Enhanced with Concealable and Selectively Revealable Text, Image, and Video Messages |
US9959431B2 (en) * | 2013-09-16 | 2018-05-01 | Google Technology Holdings LLC | Method and apparatus for displaying potentially private information |
-
2014
- 2014-11-28 US US15/521,160 patent/US10187855B2/en active Active
- 2014-11-28 WO PCT/CN2014/092524 patent/WO2016082194A1/zh active Application Filing
- 2014-11-28 EP EP14906889.2A patent/EP3200487B1/en active Active
- 2014-11-28 CN CN201480059535.4A patent/CN105900466B/zh active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102752730A (zh) * | 2012-07-19 | 2012-10-24 | 腾讯科技(深圳)有限公司 | 消息处理的方法及装置 |
CN103428652A (zh) * | 2013-08-06 | 2013-12-04 | 北京华恒铭圣科技发展有限责任公司 | 一种手机信息推送方法及装置 |
CN103595766A (zh) * | 2013-10-23 | 2014-02-19 | 北京奇虎科技有限公司 | 实现扩展应用程序的推送通知的方法及装置 |
CN103561152A (zh) * | 2013-11-05 | 2014-02-05 | 广东欧珀移动通信有限公司 | 一种推送消息处理方法和移动终端 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3200487A4 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2559830A (en) * | 2017-02-17 | 2018-08-22 | Google Llc | Transitioning between private and non-private state |
US10439966B2 (en) | 2017-02-17 | 2019-10-08 | Google Llc | Transitioning between private and non-private state |
US11153241B2 (en) | 2017-02-17 | 2021-10-19 | Google Llc | Transitioning between private and non-private state |
US11695716B2 (en) | 2017-02-17 | 2023-07-04 | Google Llc | Transitioning between private and non-private state |
US11144668B2 (en) * | 2019-08-15 | 2021-10-12 | International Business Machines Corporation | Cognitively hiding sensitive content on a computing device |
Also Published As
Publication number | Publication date |
---|---|
EP3200487A1 (en) | 2017-08-02 |
EP3200487B1 (en) | 2019-09-25 |
EP3200487A4 (en) | 2017-11-01 |
US10187855B2 (en) | 2019-01-22 |
US20170325171A1 (en) | 2017-11-09 |
CN105900466A (zh) | 2016-08-24 |
CN105900466B (zh) | 2020-04-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016082194A1 (zh) | 消息处理方法及装置 | |
US11057376B2 (en) | Method, apparatus, and system for controlling intelligent device, and storage medium | |
US10880746B2 (en) | Network connection method, apparatus, storage medium and terminal | |
CN105824958B (zh) | 一种查询日志的方法、装置和*** | |
US9703971B2 (en) | Sensitive operation verification method, terminal device, server, and verification system | |
US10304461B2 (en) | Remote electronic service requesting and processing method, server, and terminal | |
US20150319173A1 (en) | Co-verification method, two dimensional code generation method, and device and system therefor | |
CN104519485B (zh) | 一种终端之间的通信方法、装置和*** | |
CN104852885B (zh) | 一种进行验证码验证的方法、装置和*** | |
WO2017067137A1 (zh) | 资源使用权限判断***及方法 | |
WO2015058512A1 (zh) | 一种nfc数据传输方法、终端设备及服务器 | |
JP6492184B2 (ja) | 情報の推薦を管理するための方法、デバイス、およびシステム | |
CN106709347B (zh) | 应用运行的方法及装置 | |
WO2014206143A1 (zh) | 未读消息数目显示方法、装置和设备 | |
CN104683301B (zh) | 一种密码保存的方法及装置 | |
US11017066B2 (en) | Method for associating application program with biometric feature, apparatus, and mobile terminal | |
CN104580177B (zh) | 资源提供方法、装置和*** | |
US20190205976A1 (en) | Account number registration method, apparatus, and system | |
WO2018095216A1 (zh) | 关系链处理方法、终端及存储介质 | |
CN107465802A (zh) | 一种显示通讯消息的方法、装置和*** | |
CN110474864A (zh) | 一种注册、登录移动应用程序的方法及电子设备 | |
CN105553718B (zh) | 引导信息显示方法及装置 | |
CN105488433B (zh) | 终端密钥生成方法及装置 | |
WO2015058514A1 (zh) | 一种nfc数据传输方法、装置及终端设备 | |
CN109728918B (zh) | 虚拟物品发送方法、虚拟物品接收方法、装置及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14906889 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15521160 Country of ref document: US |
|
REEP | Request for entry into the european phase |
Ref document number: 2014906889 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |