WO2019129003A1 - 通知提醒方法、群组添加方法、装置、终端及存储介质 - Google Patents

通知提醒方法、群组添加方法、装置、终端及存储介质 Download PDF

Info

Publication number
WO2019129003A1
WO2019129003A1 PCT/CN2018/123577 CN2018123577W WO2019129003A1 WO 2019129003 A1 WO2019129003 A1 WO 2019129003A1 CN 2018123577 W CN2018123577 W CN 2018123577W WO 2019129003 A1 WO2019129003 A1 WO 2019129003A1
Authority
WO
WIPO (PCT)
Prior art keywords
contact
notification
group
mode
preset
Prior art date
Application number
PCT/CN2018/123577
Other languages
English (en)
French (fr)
Inventor
刘齐虎
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201711418894.6A external-priority patent/CN107864297B/zh
Priority claimed from CN201711419886.3A external-priority patent/CN108156303B/zh
Priority claimed from CN201711421116.2A external-priority patent/CN108055404B/zh
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to KR1020207018008A priority Critical patent/KR102322542B1/ko
Priority to JP2020533712A priority patent/JP7043604B2/ja
Priority to EP18894393.0A priority patent/EP3723352B1/en
Priority to AU2018393399A priority patent/AU2018393399B2/en
Publication of WO2019129003A1 publication Critical patent/WO2019129003A1/zh
Priority to US16/885,859 priority patent/US11272051B2/en
Priority to US17/590,591 priority patent/US20220159119A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M19/00—Current supply arrangements for telephone systems
    • H04M19/02—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone
    • H04M19/04—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone the ringing-current being generated at the substations
    • H04M19/045—Call privacy arrangements, e.g. timely inhibiting the ring signal
    • 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/72484—User interfaces specially adapted for cordless or mobile telephones wherein functions are triggered by incoming communication events
    • 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/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72463—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device
    • 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
    • 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/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72451—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to schedules, e.g. using calendar applications
    • 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/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72454—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to context-related or environment-related conditions
    • 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/725—Cordless telephones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M19/00—Current supply arrangements for telephone systems
    • H04M19/02—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone
    • H04M19/04—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone the ringing-current being generated at the substations

Definitions

  • the embodiment of the present invention relates to the field of notification and reminding, and particularly relates to a notification reminding method, a group adding method, a device, a terminal, and a storage medium.
  • the user In order to prevent sudden incoming calls or text messages from interfering with important transactions, the user usually sets the terminal to the DND mode when performing important transactions.
  • the terminal provides a DND setting entry in the system setting, and the user can quickly set the terminal to enter the DND mode through the portal.
  • the terminal When receiving an incoming call or text message in DND mode, the terminal will not make a sound or vibration alert to the incoming call or SMS.
  • the embodiment of the present application provides a notification reminding method, a group adding method, a device, a terminal, and a storage medium, and the technical solution is as follows:
  • a notification reminding method comprising:
  • the contact corresponding to the notification is identified, and the notification is at least one of an incoming call notification, a short message notification, or an application notification;
  • the notification is notified in a predetermined manner
  • the preset contact group is a group that allows notification reminders in the DND mode by default.
  • a notification reminding device comprising:
  • the identification module is configured to: in the DND mode, when receiving the notification, identify a contact corresponding to the notification, and the notification is at least one of an incoming call notification, a short message notification, or an application notification;
  • the reminding module is configured to: when the contact belongs to the preset contact group, use a predetermined manner to notify the reminder;
  • the reminder module is disabled, and when the contact does not belong to the preset contact group, the notification reminder is not performed;
  • the preset contact group is a group that allows notification reminders in the DND mode by default.
  • a group adding method comprising:
  • the contact information includes name information and/or historical communication information
  • the group adding prompt is used to prompt to add the contact to a preset contact group, where the preset contact group is By default, groups that allow notification alerts in DND mode are allowed.
  • a group adding device comprising:
  • An obtaining module configured to obtain contact information corresponding to the contact, where the contact information includes name information and/or historical communication information;
  • An identification module configured to identify, according to the contact information, whether the contact is an important contact
  • a display module configured to display a group adding prompt if the contact is the important contact, and the group adding prompt is used to prompt to add the contact to a preset contact group
  • the preset A contact group is a group that allows notification reminders in DND mode by default.
  • a notification reminding method comprising:
  • the contact corresponding to the notification is identified, and the notification is at least one of an incoming call notification, a short message notification, or an application notification;
  • the importance level of each contact is the same in the same preset contact group, and the important levels corresponding to different preset contact groups are different.
  • a notification reminding device comprising:
  • the identification module is configured to: in the DND mode, when receiving the notification, identify a contact corresponding to the notification, where the notification is at least one of an incoming call notification, a short message notification, or an application notification;
  • a level determining module configured to determine an important level of the contact according to the preset contact group to which the contact belongs;
  • a reminding module configured to determine whether to perform a notification reminder according to the important level
  • the importance level of each contact is the same in the same preset contact group, and the important levels corresponding to different preset contact groups are different.
  • a terminal comprising a processor and a memory, the memory storing at least one instruction loaded by the processor and executed to implement a notification alert as described in the above aspect Method, or, group add method.
  • a computer readable storage medium having stored therein at least one instruction loaded by a processor and executed to implement a notification reminder method as described in the above aspects, or a group Add a method.
  • FIG. 1 and 2 are block diagrams showing the structure of a terminal provided by an exemplary embodiment of the present application.
  • FIG. 3 is a flowchart of a notification reminding method provided by an exemplary embodiment of the present application.
  • FIG. 4 is a flowchart of a notification reminding method provided by another exemplary embodiment of the present application.
  • 5 and 6 are schematic diagrams of interfaces of a contact information interface
  • FIG. 7 is a schematic diagram of an interface of an incoming call disconnection interface
  • FIG. 8 is a flowchart of a notification reminding method provided by an exemplary embodiment of the present application.
  • FIG. 9 is a flowchart of a notification reminding method provided by another exemplary embodiment of the present application.
  • FIG. 10 is a schematic diagram of an interface prompting to adjust a contact group
  • FIG. 11 is a flowchart showing a group adding method provided by an exemplary embodiment of the present application.
  • FIG. 12 is a flowchart of a group adding method provided by another exemplary embodiment of the present application.
  • FIG. 13 to 15 are schematic diagrams showing an interface for adding group information
  • FIG. 16 is a structural block diagram of a notification reminding apparatus provided by an exemplary embodiment of the present application.
  • FIG. 17 is a structural block diagram of a notification reminding apparatus provided by another exemplary embodiment of the present application.
  • FIG. 18 is a structural block diagram of a notification reminding apparatus provided by an exemplary embodiment of the present application.
  • FIG. 19 is a structural block diagram of a notification reminding apparatus provided by another exemplary embodiment of the present application.
  • FIG. 20 is a structural block diagram of a group adding apparatus provided by an exemplary embodiment of the present application.
  • FIG. 21 is a structural block diagram of a group adding apparatus provided by another exemplary embodiment of the present application.
  • FIG. 1 and FIG. 2 there is shown a block diagram showing the structure of a terminal 100 provided by an exemplary embodiment of the present application.
  • the terminal 100 can be a smartphone, a tablet, a laptop, or the like.
  • the terminal 100 in this application may include one or more of the following components: a processor 110, a memory 120, and a touch display screen 130.
  • the memory 120 stores at least one instruction, which is loaded and executed by the processor 110 to implement the notification reminding method described in the following embodiments, or a group adding method.
  • Processor 110 can include one or more processing cores.
  • the processor 110 connects various portions of the entire terminal 100 using various interfaces and lines, and executes the terminal by running or executing an instruction, program, code set or instruction set stored in the memory 120, and calling data stored in the memory 120. 100 various functions and processing data.
  • the processor 110 may use at least one of a digital signal processing (DSP), a field-programmable gate array (FPGA), and a programmable logic array (PLA).
  • DSP digital signal processing
  • FPGA field-programmable gate array
  • PDA programmable logic array
  • a form of hardware is implemented.
  • the processor 110 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a modem, and the like.
  • the CPU mainly processes the operating system, the user interface, the application, and the like; the GPU is responsible for rendering and rendering of the content that the display screen 130 needs to display; the modem is used to process wireless communication. It can be understood that the above modem may also be integrated into the processor 110 and implemented by a single chip.
  • the memory 120 may include a random access memory (RAM), and may also include a read-only memory.
  • the memory 120 includes a non-transitory computer-readable storage medium.
  • Memory 120 can be used to store instructions, programs, code, code sets, or sets of instructions.
  • the memory 120 may include a storage program area and a storage data area, wherein the storage program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), The instructions for implementing the various method embodiments described below, etc.; the storage data area can store data (such as audio data, phone book) created according to the use of the terminal 100, and the like.
  • the memory 120 stores a Linux kernel layer 220, a system runtime layer 240, an application framework layer 260, and an application layer 280.
  • the Linux kernel layer 220 provides the underlying drivers for various hardware of the terminal 100, such as display drivers, audio drivers, camera drivers, Bluetooth drivers, Wi-Fi drivers, power management, and the like.
  • the system runtime layer 240 provides major features support for the Android system through some C/C++ libraries. For example, the SQLite library provides support for the database, the OpenGL/ES library provides support for 3D graphics, and the Webkit library provides support for the browser kernel.
  • the Android runtime library 242 (Android Runtime) is also provided in the system runtime layer 240. It mainly provides some core libraries, which can allow developers to write Android applications using the Java language.
  • the application framework layer 260 provides various APIs that may be used when building an application. Developers can also build their own applications by using these APIs, such as event management, window management, view management, notification management, content providers, Package management, call management, resource management, location management.
  • the application layer 280 runs at least one application, which may be a contact program, an SMS program, a clock program, a camera application, etc. that is provided by the operating system; or an application developed by a third-party developer, such as an instant. Communication programs, photo landscaping programs, etc.
  • the IOS system includes: a core operating system layer 320 (Core OS layer), a core service layer 340 (Core Services layer), and a media layer. 360 (Media layer), touchable layer 380 (Cocoa Touch Layer).
  • the core operating system layer 320 includes an operating system kernel, drivers, and an underlying program framework that provide functionality closer to the hardware for use by the program framework located at the core service layer 340.
  • the core service layer 340 provides system services and/or program frameworks required by the application, such as a Foundation framework, an account framework, an advertising framework, a data storage framework, a network connectivity framework, a geographic location framework, a motion framework, and the like.
  • the media layer 360 provides an interface for the audiovisual aspect of the application, such as a graphic image related interface, an audio technology related interface, a video technology related interface, and an audio and video transmission technology wireless play (AirPlay) interface.
  • the touch layer 380 provides various commonly used interface related frameworks for application development, and the touch layer 380 is responsible for user touch interaction operations on the terminal 100. Such as local notification service, remote push service, advertising framework, game tool framework, message user interface (UI) framework, user interface UIKit framework, map framework and so on.
  • frameworks related to most applications include, but are not limited to, the base framework in core service layer 340 and the UIKit framework in touchable layer 380.
  • the underlying framework provides many basic object classes and data types, providing the most basic system services for all applications, regardless of the UI.
  • the classes provided by the UIKit framework are the basic UI class libraries for creating touch-based user interfaces. iOS applications can provide UI based on the UIKit framework, so it provides the application infrastructure for building user interfaces, drawing , handling and user interaction events, responsive gestures, and more.
  • the touch display 130 is used to display a user interface of various applications, as well as a touch operation for receiving a user's use of a finger, a stylus, or the like on or near any suitable object.
  • the touch display screen 130 is typically disposed at the front panel of the terminal 100.
  • the touch display 130 can be designed as a full screen, a curved screen, or a profiled screen.
  • the touch display screen 130 can also be designed as a combination of a full screen and a curved screen, and the combination of the special screen and the curved screen is not limited in this embodiment.
  • the structure of the terminal 100 shown in the above figure does not constitute a limitation on the terminal 100, and the terminal may include more or less components than the illustration, or a combination of some Parts, or different parts.
  • the terminal 100 further includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (WiFi) module, a power supply, a Bluetooth module, and the like, and details are not described herein.
  • WiFi wireless fidelity
  • the terminal When receiving a new message, the terminal will promptly remind the user of the new message by means of a notification bar, pop-up window, ringing, vibration, and the like. However, if the user is currently in the process of a meeting, sleep, meeting, game, etc., it is likely that they do not want to be disturbed by outside messages. To this end, the terminal may be provided with a DND mode. If the user chooses to enter the DND mode, the terminal enables the DND mechanism, that is, stops the notification bar reminder, popup reminder, ring alert, vibration alert and/or the received message. Or other reminders. When the DND mode is ended, the terminal resumes the normal reminder mode, and can also provide supplementary reminder for the message received during the DND mode.
  • the DND mode satisfies the need for users not to be disturbed by outside messages at specific times, but introduces new problems. For example, if the user sets the terminal to the DND mode while watching a movie, the terminal receives an important call during the movie, and the ringing of the important call is prohibited by the DND mode, the user is likely to miss the important call. And then face a big loss.
  • a global preset contact group is set in the terminal, and the user can add an important contact to the group in order to ensure that the user does not miss the important notification.
  • the terminal In the do not disturb mode, when receiving the notification of the important contact in the preset contact group, the terminal bypasses the DND mechanism to implement the notification reminder for the important contact; meanwhile, the contact is not for the preset contact group.
  • the person's notification that the terminal still enables the DND mechanism to prevent such interference to the user.
  • FIG. 3 shows a flowchart of a notification reminding method provided by an exemplary embodiment of the present application.
  • This embodiment is exemplified by applying the method to the terminal provided in FIG. 1 or FIG. 2 described above.
  • the method includes:
  • Step 301 In the DND mode, when the notification is received, the contact corresponding to the notification is identified, and the notification is at least one of an incoming call notification, a short message notification, or an application notification.
  • the DAP mechanism in the DND mode, when the terminal receives the notification, the DAP mechanism is directly enabled to perform the DND process, and the corresponding notification reminder is prohibited.
  • the important contact is The notification reminds that when receiving the notification in the DND mode, the terminal does not directly enable the DND mechanism, but first identifies the contact corresponding to the notification.
  • the terminal when receiving an incoming call notification or a short message notification, acquires a phone number corresponding to the caller or the sender of the short message, and then identifies the corresponding contact according to the phone number.
  • the terminal detects whether the phone number is stored in the address book. If the phone number is not stored, the terminal determines that the notification is from a strange contact, and enables the DND mechanism to perform the DND process on the notification; if the phone number is stored, The terminal determines that the notification is from the contact in the address book, and further detects whether the contact belongs to the preset contact group. If yes, the following step 302 is performed. If not, the following step 303 is performed.
  • the terminal when the terminal receives the incoming call notification, the terminal identifies the incoming call notification "Zhang San" of the corresponding address book terminal according to the telephone number of the caller.
  • the terminal when receiving an application notification of an application push (such as an email notification pushed by a mail application, an instant communication message notification or an audio and video request pushed by an instant messaging application, etc.), the terminal acquires a notification corresponding to the application notification.
  • the party identifies and determines the contact corresponding to the notification according to the notification party identifier.
  • the notification party identifier may be an email address of the sender or an instant messaging account of the sender of the instant messaging message.
  • the terminal searches for the application notification in the address book according to the notification party identifier. Contact.
  • the notification reminding method may also be applied to a specific application (application level). That is, the contact corresponding to the notification is determined based on the contact list in the application, which is not limited in this embodiment.
  • Step 302 If the contact belongs to the preset contact group, the notification is notified in a predetermined manner.
  • the predetermined manner includes at least one of a screen display reminder, a sound reminder, and a vibration reminder.
  • a preset contact group is set in the terminal, and the preset contact group is a group that allows notification reminders in the DND mode by default.
  • the contacts in the preset contact group are preset. Added manually by the user.
  • the preset contact group is a group set by default in the terminal system, and is not manually created by the user, and the user can only add or remove contacts to the preset contact group.
  • the preset contact group is a global group, and the terminal allows the notification in the preset contact group to be notified regardless of the type of the DND mode of the terminal, without the user being in various Manual setting in DND mode.
  • the terminal sets a corresponding preset group identifier for each contact in the preset contact group.
  • the terminal detects whether the contact is There is a corresponding preset group identifier, and if yes, it is determined that the contact belongs to the preset contact group, thereby bypassing the DND mechanism and performing notification notification.
  • the terminal sets a preset group identifier “VIP” for each contact in the preset contact group, and when it is detected that the contact “Zhang San” corresponds to the “VIP” identifier, it is determined that “Zhang San” belongs to the pre- Set up a contact group and call to remind you of the call of "Zhang San”.
  • step 303 if the contact does not belong to the preset contact group, the notification reminder is not performed.
  • the terminal determines that the current contact is not an important contact, thereby enabling the DND mechanism to perform the DND process on the received notification.
  • the terminal when performing the DND process, does not display the notification processing interface, and does not perform sound and vibration reminders.
  • the preset contact group that allows the notification reminder in the DND mode is preset in the terminal, and the preset contact group is received in the DND mode.
  • the terminal can skip the DND mechanism and notify the notification of the notification, thereby avoiding the omission of the notification of the important contact; meanwhile, when the terminal is in the DND mode, the terminal is allowed to default to the preset contact group.
  • the contact notifications are not required to be manually set by the user, which simplifies the process of setting the DND mode.
  • the corresponding contact information interface of each contact is provided with a corresponding control, and the user can use the control to The contact is added to the preset contact group, or the contact is removed from the preset contact group.
  • FIG. 4 shows a flowchart of a notification reminding method provided by another exemplary embodiment of the present application. The method includes the following steps.
  • Step 401 When the target contact does not belong to the preset contact group, the add control is displayed in the contact information interface corresponding to the target contact.
  • Each contact in the address book corresponds to a respective contact information interface
  • the contact information interface includes information such as a contact name, a note, a phone number, an address, a mailbox, and the like, and the user can update the information included in the contact information interface.
  • the terminal when receiving the operation of viewing the target contact corresponding contact information interface, the terminal detects whether the target contact belongs to the preset contact group, wherein detecting whether the target contact belongs to the preset contact For the manner of the group of people, see step 302 above. This embodiment is not described here.
  • the terminal displays an add control in the current contact information interface, and the added control may be an add button.
  • the terminal detects whether “Zhang San” belongs to a VIP contact group (ie, a preset contact group). When "Zhang San” does not belong to the VIP contact group, the terminal displays the add control 511 in the contact information interface 51.
  • a VIP contact group ie, a preset contact group
  • Step 402 Add a target contact to the preset contact group when receiving a click operation on the added control.
  • the user can add the target contact to the preset contact group through the add control, and correspondingly, the terminal receives the click operation on the added control, and adds the target contact to the preset Set up a contact group.
  • the terminal when receiving a click operation on the added control, the terminal sets a preset group identifier corresponding to the preset contact group for the target contact, for example, the terminal sets “VIP” for the target contact. "Identification.
  • the terminal After the terminal adds the target contact to the preset contact group, stop displaying the add control in the contact information interface.
  • the terminal replaces the add control in the contact information interface with a remove control, so that the user moves the target contact out of the preset contact group.
  • Step 403 When the target contact belongs to the preset contact group, the second removal control is displayed in the contact information interface corresponding to the target contact.
  • the terminal displays the removal control in the contact information interface, so that the user removes the target contact from the preset contact group through the removal control. group.
  • the terminal when the contact information interface 51 corresponding to the contact "Zhang San” is opened, the terminal detects that "Zhang San” belongs to the VIP contact group, thereby displaying in the contact information interface 51. Control 512 is removed.
  • Step 404 When the click operation on the second removal control is received, the target contact is removed from the preset contact group.
  • the user can move the target contact to the preset contact group through the removal control, and correspondingly, the terminal receives the click operation on the removal control, and the target Contacts are removed from the default contact group.
  • the terminal when receiving a click operation on the removal control, deletes the preset group identifier corresponding to the target contact, for example, the terminal deletes the “VIP” identifier of the target contact.
  • the display control is stopped in the contact information interface.
  • the terminal replaces the removal control in the contact information interface with an add control, so that the user re-adds the target contact to the preset contact group.
  • the terminal is provided with a preset contact group management interface, where the user can perform unified management on the contacts in the preset contact group.
  • the interface is provided with a removal control, by which the user can remove the existing contacts in the preset contact group; the interface also has an add control, through which the control is added. The user can also add a contact to the preset contact group.
  • the embodiment of the present application does not limit the specific manner of managing the preset contact group.
  • Step 405 In the DND mode, when the notification is received, the contact corresponding to the notification is identified, and the notification is at least one of an incoming call notification, a short message notification, or an application notification.
  • Step 406 If the contact belongs to the preset contact group, the notification processing interface corresponding to the notification is displayed, and the group identifier of the preset contact group is included in the notification processing interface.
  • the terminal When the contact belongs to the preset contact group, the terminal displays a corresponding notification processing interface according to the notification type, prompting the user to process the notification.
  • the notification type is an incoming call
  • the terminal displays an incoming call hang-up interface
  • the notification type is a short message
  • the terminal displays a short message reading reply interface.
  • the terminal displays the group identifier of the preset contact group in the notification processing interface.
  • step 407 an audible alert and/or a vibrating alert is provided to the notification.
  • the terminal performs an audible reminder and/or a vibrating reminder to the notification while displaying the notification processing interface.
  • the terminal can provide the DND mode for different scenarios, and the user does not perceive the sound and vibration in different DND modes, in order to enable the user to perceive the sound and vibration, the terminal is based on the current DND.
  • the mode type of the mode enabling the corresponding beep parameters and/or vibration parameters for sound reminders and/or vibrating reminders.
  • the step includes the following steps.
  • the mode type of the DND mode is obtained.
  • the terminal system provides a variety of DND modes, and when the terminal enters the DND mode, the terminal is in the DND state.
  • the mode types of the DND mode include: silent mode, conference mode, game mode, and sleep mode.
  • the terminal determines the mode type of the current DND mode.
  • the mode type belongs to the first mode type, performing a sound reminding according to the first prompt sound parameter, and/or performing a vibration reminding according to the first vibration parameter, the first working mode including at least one of a sleep mode and a silent mode .
  • the mode type belongs to the second mode type, performing a sound reminding according to the second prompt sound parameter, and/or performing a vibration reminding according to the second vibration parameter, where the second working mode includes at least one of a game mode and a meeting mode.
  • the terminal sets different prompt sound parameters and vibration parameters for different types of DND modes in advance. After determining the mode type of the current DND mode, the terminal further acquires the prompt tone parameter and the vibration parameter corresponding to the mode type, so as to perform sound and vibration prompts based on the acquired parameters.
  • the terminal Since the user's ability to perceive sound and vibration in a sleep state is weak, and the user usually sets the terminal to a sleep mode or a silent mode (ie, the first mode type) while sleeping, the terminal sets the first mode for the first mode type.
  • the tone parameter and the second vibration parameter are weak, and the user usually sets the terminal to a sleep mode or a silent mode (ie, the first mode type) while sleeping.
  • the terminal When the user plays a game or conducts a conference, the ability to perceive sound and vibration is strong, and when the user plays the game, the terminal is usually set to the game mode (ie, the second mode type), and when the conference is performed, the terminal is usually set.
  • the conference mode ie, the second mode type
  • the terminal sets the second prompt tone parameter and the second vibration parameter for the second mode type.
  • the sound volume indicated by the first prompt sound parameter is greater than the sound volume indicated by the second prompt sound parameter; the vibration frequency indicated by the first vibration parameter is greater than the vibration frequency indicated by the second vibration parameter.
  • Tone parameter Vibration parameter First mode type (sleep mode, silent mode) 40dB 5 times / sec Second mode type (meeting mode, game mode) 30dB 3 times / sec
  • the prompt tone parameter further includes a parameter such as a prompt tone
  • the vibration parameter further includes a parameter such as a vibration amplitude, which is not limited in this embodiment.
  • the terminal when in the first mode type, in order to improve the probability that the user notices the notification reminder, the terminal strongly reminds the notification according to the first prompt sound parameter and/or the first vibration parameter; when in the second mode type, the terminal The notification is given an ordinary reminder according to the second prompt sound parameter and/or the second vibration parameter.
  • the terminal may set different prompt sounds for various mode types.
  • the parameters and vibration parameters are not limited in this embodiment.
  • Step 408 When receiving a click operation on the first removal control in the notification processing interface, the contact is removed from the preset contact group.
  • the contact information interface corresponding to the contact needs to be operated.
  • the notification processing interface displayed by the terminal is further provided with a first removal control, and the user can quickly remove the current contact from the pre-selection by using the first removal control. Set the contact group to remove.
  • the terminal displays a removal control 522 in the incoming call answering interface 52.
  • the remove control 522 When the user clicks the remove control 522, the contact "Zhang San” is removed from the VIP contact group. .
  • step 409 if the contact does not belong to the preset contact group, the notification reminder is not performed.
  • the terminal displays an add or remove control on the contact information interface, so that the user can quickly add the contact to the preset contact group or remove the preset contact group; thereby improving the preset contact group. Further, the terminal displays the removal control in the notification processing interface, so that when the user receives the notification reminder, the current contact is quickly moved out of the preset contact group, thereby further improving the management efficiency of the preset contact group.
  • the terminal sets different prompt sound parameters and vibration parameters for different modes of the DND mode according to the user's ability to perceive sound and vibration in different DND modes, so as to perform parameters according to the current DND mode.
  • Sound and/or vibration reminders improve the user's ability to perceive notification alerts in various DND modes, further reducing the probability of users missing important contact notifications.
  • only one preset contact group is set in the terminal, and the notification of each contact in the preset contact group is not restricted by the DND mechanism.
  • the user may desire to only alert the notifications of some of the contacts in the preset contact group.
  • a plurality of preset contact groups corresponding to different importance levels are set in the terminal, and the user may add the preset contact groups to the corresponding preset contact groups according to the importance degree of the contacts.
  • the terminal determines the importance level according to the preset contact group to which the contact belongs, and then determines whether to perform the notification reminder according to the important level. The following description is made using the illustrative embodiments.
  • FIG. 8 shows a flowchart of a notification reminding method provided by an exemplary embodiment of the present application.
  • the method includes the following steps.
  • Step 801 In the DND mode, when the notification is received, the contact corresponding to the notification is identified, and the notification is at least one of an incoming call notification, a short message notification, or an application notification.
  • the terminal when receiving an incoming call notification or a short message notification, acquires a phone number corresponding to the caller or the sender of the short message, and then identifies the corresponding contact according to the phone number.
  • the terminal detects whether the phone number is stored in the address book. If the phone number is not stored, the terminal determines that the notification is from a strange contact, and enables the DND mechanism to perform the DND process on the notification; if the phone number is stored, The terminal determines that the notification is from the contact in the address book, and further determines the preset contact group to which the contact belongs, and performs the following step 802; if the contact does not belong to any preset contact group, the terminal enables the do not disturb The mechanism performs DND processing on notifications.
  • the terminal when receiving an application notification of an application push (such as an email notification pushed by a mail application, an instant communication message notification or an audio and video request pushed by an instant messaging application, etc.), the terminal acquires an application notification correspondingly.
  • the notification party identifier, and the contact corresponding to the notification is determined according to the notification party identifier.
  • the notification party identifier may be an email address of the sender or an instant messaging account of the sender of the instant messaging message.
  • the terminal searches for the application notification in the address book according to the notification party identifier. Contact.
  • Step 802 Determine an important level of the contact according to the preset contact group to which the contact belongs, where the important level of each contact is the same in the same preset contact group, and different preset contact groups correspond to each other. The importance levels are different.
  • At least two preset contact groups are preset in the terminal, and each preset contact group corresponds to a respective important level. Accordingly, the user manually adds the contact to the corresponding one according to the importance degree of the contact in the address book. In the default contact group.
  • the terminal recognizes that the contact corresponding to the notification is “Zhang San”, and determines the importance level of the contact “Zhang San” to one level according to the correspondence relationship shown in Table 2.
  • the terminal sets different group identifiers for contacts in different preset contact groups, and the terminal is corresponding to the contact corresponding to the contact.
  • the group ID determines the preset contact group to which it belongs.
  • the terminal sets the group identifiers "VIP1", “VIP2”, and “VIP3" for the contacts in the first contact group, the second contact group, and the third contact group, respectively.
  • the terminal determines that it belongs to the first contact group according to the group identifier “VIP1” corresponding to the contact “Zhang San”.
  • step 803 it is determined whether to perform a notification reminder according to the importance level.
  • the importance level of the contact that allows the notification reminder is different, and correspondingly, the mode type of the terminal according to the current DND working mode and the importance of the contact. Level, determine whether to make a notification reminder.
  • the foregoing step 302. The implementation manner of the terminal for prohibiting the notification of the notification is referred to the foregoing step 303, which is not described herein again.
  • the important level of the contact that allows the notification reminder is ⁇ one level; in the conference mode, the important level of the contact that allows the notification reminder is ⁇ two; in the sleep mode, the notification reminder is allowed.
  • the importance level of the contact is ⁇ three. According to the data in Table 2, when receiving the incoming call notification of the contact "Zhang San" in the game mode, the terminal performs an incoming call reminder; when receiving the incoming call notification of the contact "Zhang San" in the conference mode or the sleep mode The terminal does not make a call alert.
  • multiple preset contact groups corresponding to different important levels are preset in the terminal, and when receiving the notification in the DND mode, the terminal is based on the preset contact to which the current contact belongs.
  • the group determines the importance level of the current contact, and then determines whether to perform the notification reminder according to the important level;
  • the hierarchical control mechanism enables the terminal to implement fine-grained notification reminder management, avoiding the user missing the important contact call message while avoiding the user Being disturbed by other contacts other than the important contact improves the accuracy of the notification reminder, making the notification reminder in the DND mode more in line with the user's expectations.
  • the terminal pre-establishes a correspondence between the different important levels and the target DND mode, and correspondingly, the terminal is not disturbed according to the current DND mode and the target contact important level corresponding to the target. Mode to determine whether to make a notification reminder.
  • FIG. 9 shows a flowchart of a notification reminding method provided by another exemplary embodiment of the present application.
  • the method includes the following steps.
  • Step 901 In the DND mode, when the notification is received, the contact corresponding to the notification is identified, and the notification is at least one of an incoming call notification, a short message notification, or an application notification.
  • Step 902 Determine an important level of the contact according to the preset contact group to which the contact belongs, where the important level of each contact is the same in the same preset contact group, and different preset contact groups correspond to each other. The importance levels are different.
  • the terminal further obtains the current DND mode; if the current contact does not belong to any preset contact group, the terminal Then do not disturb the notification.
  • Step 903 Acquire a DND mode in which the terminal is currently located.
  • the terminal system provides multiple DND modes for different scenarios.
  • the terminal When the terminal enters the DND mode, the terminal is in the DND state.
  • the DND mode includes: silent mode, conference mode, game mode, and sleep mode.
  • Step 904 determining a target DND mode corresponding to the importance level.
  • DND mode For contacts with a higher level of importance, users usually want to be able to make notifications in various DND modes. For contacts with lower levels of importance, users want to be notified in part of DND mode. Notifications are not made in DND mode.
  • the terminal presets a correspondence between different important levels and a target DND mode, and the target DND mode is a DND mode that allows a notification reminder.
  • the number of target DND modes corresponding to different important levels is different, and the important level is positively correlated with the number of target DND modes, that is, the higher the important level, the more types of corresponding target DND modes.
  • the silent mode and the game mode are determined to determine the target do not disturb mode.
  • a contact with a level of importance is the least important, so the terminal will only notify you when it receives an incoming call or text message from the contact in silent mode or game mode.
  • the silent mode, the game mode, and the conference mode are determined as the target DND mode.
  • contacts with a priority level of two are more important. Therefore, in addition to notification notifications in silent mode and game mode, in conference mode, the terminal will also The contact's call or text message is notified.
  • the silent mode, the game mode, the conference mode, and the sleep mode are determined as the target DND mode.
  • the terminal determines the target DND mode for all DND modes, ensuring that the user can receive incoming calls and text messages from the contact in silent mode, game mode, conference mode, and sleep mode.
  • the terminal may set two or more preset contact groups. This embodiment is not correct. This constitutes a limitation.
  • step 903 and step 904 can be performed simultaneously, and the implementation does not limit the execution timing of the two.
  • the terminal After the target DND mode is acquired through the above steps 903 and 904, and the DND mode currently in which the terminal is currently located, the terminal further detects whether the (current) DND mode belongs to the target DND mode. If yes, the following steps 905 to 908 are performed, and if not, the following step 909 is performed.
  • step 905 if the DND mode belongs to the target DND mode, a notification reminder is performed.
  • the terminal If the current DND mode of the terminal belongs to the target DND mode corresponding to the current contact, the terminal performs a notification reminder by using a predetermined manner.
  • the terminal displays the corresponding notification processing interface, and performs a sound reminder and/or a vibration reminder, wherein the notification processing interface includes a group identifier of the preset contact group to which the contact belongs.
  • the voice reminder and the vibration reminder manner are different for the contact of the different important levels.
  • the terminal acquires the corresponding prompt sound parameter and the vibration parameter according to the important level of the current contact. Then, the notification reminder is performed according to the obtained parameters.
  • the step includes the following steps.
  • the DND mode belongs to the target DND mode, the prompt tone parameters and/or vibration parameters corresponding to the important level are obtained.
  • the important level is positively correlated with the volume of the prompt sound indicated by the prompt sound parameter, and the important level is positively correlated with the vibration frequency indicated by the vibration parameter.
  • the higher the importance level of the contact the higher the volume of the prompt sound when the notification is made, and the higher the vibration frequency.
  • Tone parameter Vibration parameter First level 30dB 2 times / sec Secondary 40dB 4 times / sec Third level 50dB 6 times / sec
  • the terminal when receiving the incoming call or short message of the contact "Zhang San", the terminal obtains the prompt sound parameter of 30 dB and the vibration parameter of 2 times/second according to the data recorded in Table 2 and Table 4.
  • the terminal performs sound reminding and vibration reminding.
  • the user may also set respective corresponding prompt sounds and/or vibration modes for different important levels, which is not limited in this embodiment.
  • Step 906 when the notification reminder is made, receives the operation of the notification.
  • the terminal After the notification reminder is performed, the terminal receives the user's operation of the notification through the notification processing interface.
  • the notification is an incoming call notification
  • the terminal receives the answering or hanging operation through the notification processing interface
  • the notification is the short message communication
  • the terminal receives the reply operation or the delete operation through the short message processing interface.
  • Step 907 Determine a target contact group of the contact according to the operation type of the operation.
  • the terminal updates the contact contact group of the contact according to the type of operation of receiving the operation.
  • the terminal defines an answer operation and an hang up operation, and the terminal defines a reply operation and a delete operation for the short message notification.
  • the terminal determines that the important level corresponding to the target contact group is greater than or equal to the important level corresponding to the preset contact group; when the operation type is the hang up or delete operation, the terminal determines the target contact.
  • the important level corresponding to the group is less than or equal to the important level corresponding to the preset contact group.
  • the terminal counts the number of operations of each type of operation, and when the number of operations reaches the threshold, re-determines the target contact group to which the contact belongs. group.
  • the threshold can be 10 times.
  • the terminal counts the number of times the user answers an incoming call, hangs up an incoming call, replies to a short message, and deletes a short message.
  • the terminal determines the importance level of the target contact group ⁇ the important level of the preset contact group to which the contact currently belongs; when the number of times the user hangs up or deletes the short message Threshold, the terminal determines the importance level of the target contact group ⁇ the importance level of the preset contact group to which the contact currently belongs.
  • Step 908 If the preset contact group and the target contact group to which the contact belongs are different, the group adjustment prompt is displayed in the contact information interface corresponding to the contact.
  • the terminal displays a corresponding group adjustment prompt, prompting the user to adjust the contact to the target contact group.
  • the terminal displays a group adjustment prompt in the contact information interface corresponding to the contact, so that the user adjusts the group where the contact is located in the contact information interface.
  • the number of times the user answers the call of the contact "Zhang San” reaches 10 times.
  • the terminal displays
  • the group adjustment prompt 512 prompts the user to upgrade the contact "Zhang San” from VIP1 (corresponding to the important level to the first level) to VIP2 (corresponding to the important level is the second level).
  • the terminal may automatically adjust the contact according to the determined target contact group, which is not limited in this embodiment.
  • step 909 if the DND mode does not belong to the target DND mode, the notification reminder is not performed.
  • step 303 For the detailed implementation of this step, refer to step 303 above, and the embodiment is not described herein again.
  • the terminal acquires corresponding prompt sound parameters and vibration parameters according to the important level corresponding to the current contact, thereby performing sound reminding and vibration reminding according to the obtained parameters, thereby improving the user's sensing ability for important contact notifications. , further reducing the probability of users missing important contact notifications.
  • the terminal re-determines the target contact group of the contact according to the type of operation performed by the user on the notification, and when the target contact group is inconsistent with the current group of the contact,
  • the group adjustment prompt is convenient for the user to adjust the important level of the contact in real time, thereby improving the accuracy of the subsequent notification reminder.
  • the importance of the contacts in the address book is determined by the user, and the user manually adds the important contacts to the preset contact group.
  • the generated preset contact group has a low coverage rate (the user manually adds an omission), resulting in a lower accuracy rate for subsequent notification notifications based on the preset contact group.
  • the present application provides a group adding method.
  • FIG. 11 shows a flowchart of a group adding method provided by an exemplary embodiment of the present application.
  • the method includes the following steps.
  • Step 1101 Obtain contact information corresponding to the contact, where the contact information includes name information and/or historical communication information.
  • the terminal For each contact in the address book, the terminal acquires contact information corresponding to each contact, and the contact information includes name information of the contact and historical communication information with the contact.
  • the terminal acquires contact information every predetermined time interval. For example, the terminal obtains contact information every 10 days.
  • the name information includes at least one of a contact note and a contact name;
  • the historical communication information includes (historical) call information and (historical) short message sending content.
  • the name information obtained by the terminal includes the contact name “Zhang San” and the remark “Manager”, and the obtained historical communication information includes the call information in the last 10 days and the content of the short message transmission.
  • Step 1102 Identify, according to the contact information, whether the contact is an important contact.
  • the terminal analyzes it to determine whether the contact is an important contact.
  • the terminal determines, according to the name information of each contact, a social relationship between the user and each contact, thereby identifying an important contact, and/or, the terminal analyzes historical communication information with each contact, and further, from the call.
  • the frequency, the duration of the call, the duration of the call, the proportion of the call-through, the number of callbacks, and the content of the text message are sent to identify important contacts.
  • Step 1103 If the contact is an important contact, the group adding prompt is displayed, and the group adding prompt is used to prompt to add the contact to the preset contact group, and the preset contact group is allowed to be exempted by default. Groups that notify notifications in the Disturb mode.
  • the terminal displays the group addition prompts in a predetermined manner for adding important contacts to the preset contact groups according to the prompts.
  • the terminal automatically adds the identified contact to the preset contact group, and marks or prompts the added contact, which is not limited in this embodiment.
  • the terminal After the user adds a contact to the preset contact group according to the group adding prompt, the terminal determines whether to receive the notification according to the preset contact group in the DND mode, and the detailed notification reminding process is referred to The notification reminding method provided by the foregoing embodiments is not described herein again.
  • the terminal obtains contact information of the contact, and identifies an important contact based on the contact information, thereby displaying a group adding prompt, so that the user adds an important contact according to the group adding prompt.
  • the terminal Adding to a preset contact group; in the subsequent process, the terminal allows notification of the contact of the preset contact group in the DND mode based on the preset contact group, thereby preventing the user from missing important contacts.
  • the notification of the person; compared with the user automatically determining the importance of the contact, and manually adding the contact to the preset contact group, the coverage rate and the accuracy rate of the preset contact group generated in the implementation are higher. This further improves the accuracy of subsequent notification reminders based on the group.
  • the terminal integrated name information and the historical communication information determine important contacts.
  • FIG. 12 shows a flowchart of a group adding method provided by another exemplary embodiment of the present application. The method includes the following steps.
  • Step 1201 Obtain contact information corresponding to the contact, where the contact information includes name information and/or historical communication information.
  • step 1101 For the detailed implementation of this step, refer to step 1101 above, and the embodiment is not described herein again.
  • the terminal acquires name information and historical communication information of each contact.
  • Step 1202 Obtain a note and/or a contact name included in the name information.
  • the name information set by the user for the contact can reflect the social relationship between the user and the contact, and the importance of the different social relationships is different. Therefore, the terminal can determine the importance degree of the contact according to the name information of the contact.
  • the name information obtained by the terminal includes the contact name "Zhang San” and the remark "Manager”.
  • step 1203 if the note or the contact name belongs to the preset vocabulary, the contact is determined as an important contact.
  • the terminal detects whether the note or the contact name belongs to the preset vocabulary, and if so, determines that the contact is an important contact, and if not, determines that the contact is not an important contact.
  • the preset vocabulary is generated based on the name information of the added important contacts in the preset contact group.
  • the preset vocabulary includes name information of the added important contact, and associated name information corresponding to the name information.
  • the name information of the added important contacts includes the manager and the chairman, and the terminal acquires the vocabulary associated with the manager and the chairman, such as the boss, the leader, and the representative, thereby generating a preset vocabulary
  • the default vocabulary contains: manager, chairman, boss, leader and representative.
  • the terminal may also obtain a preset vocabulary from the server by means of configuration update, which is not limited in this embodiment.
  • Step 1204 Acquire call information included in the historical communication information, where the call information includes at least one of a frequency of a call, a duration of a call, a duration of a call, a number of answers, a number of hangups, and a number of callbacks.
  • the terminal identifies an important contact based on the call information in the historical communication information.
  • the terminal obtains the call information (5 days) corresponding to the contact "Zhang San” as shown in Table 5.
  • the call information obtained by the terminal may also include information such as the number of calls, the location of the call, and the like, which is not limited in this embodiment.
  • Step 1205 If the call information meets the preset condition, determine whether the contact is an important contact.
  • the preset condition includes at least one of the following conditions.
  • the frequency of the call is greater than the first threshold.
  • the higher the degree of importance of the contact the higher the frequency and frequency of the call with the user. Therefore, when the frequency of the call with the contact is greater than the first threshold, the terminal determines that the contact is an important contact, for example, the first A threshold is 1 time/day.
  • the terminal counts the frequency of the call with each contact, and calculates the average frequency of the call, and then determines the first threshold based on the average frequency of the call, wherein the first threshold ⁇ the average frequency of the call.
  • the duration of the call is greater than the second threshold.
  • the terminal can also judge the importance of the contact from the duration of the call.
  • the terminal determines that the contact is an important contact, for example, the second threshold is 5 minutes/time.
  • the terminal counts the duration of the call with each contact, and calculates an average value of the call duration, and then determines the second threshold based on the average duration of the call, wherein the second threshold is ⁇ the average duration of the call.
  • the terminal calculates that the call duration with the contact Zhang San is >5 minutes/time, and therefore, the terminal determines the contact Zhang San as an important contact.
  • the number of calls in the predetermined time period is greater than the third threshold.
  • the terminal analyzes the active period and the inactive period of the user according to the power consumption time distribution, and determines the inactive period as the predetermined period.
  • the predetermined time period is: 0:00 to 07:00.
  • the terminal determines that the contact is an important contact.
  • the third threshold is 1 time.
  • the terminal calculates that the number of calls with the contact member Zhang in the period from 0:00 to 07:00 is 5>1 times (third threshold), therefore, the terminal will contact the contact person three Determined to be an important contact.
  • the ratio of the number of times of receiving and the number of hanging times is greater than the fourth threshold.
  • the terminal collects the proportion of the connection hangup corresponding to each contact ((the number of answers +1) / (the number of hangs +1)), and calculates the average value of the answer hangup, and then based on the answer
  • the hang-up ratio average determines the fourth threshold, wherein the fourth threshold ⁇ picks up the hang-up ratio average.
  • the terminal calculates that the contact hangup ratio of the contact person Zhang 3 is 5>2.5 (the fourth threshold value), and therefore, the terminal determines the contact person Zhang as an important contact.
  • the number of callbacks is greater than the fifth threshold.
  • the terminal counts the number of callbacks corresponding to each contact (call back immediately after answering the call) and calculates the average number of callback times, and then determines the fifth threshold based on the average number of callback times.
  • the fifth threshold ⁇ the average number of callback times.
  • the terminal calculates that the number of callbacks corresponding to the contact person Zhang 3 is 1>0.8 (the fifth threshold), and therefore, the terminal determines the contact person Zhang as an important contact.
  • Step 1206 Acquire the content of the short message sent in the historical communication information.
  • the sent message content usually contains certain words, so the terminal can analyze the content of the message to identify important contacts.
  • the terminal obtained the text message sent to Zhang San: Hello, Manager Zhang, I don't know if you are free this afternoon?
  • Step 1207 If the content of the short message includes a preset vocabulary, the contact is determined to be an important contact, and the preset vocabulary includes an honorific vocabulary and a distinguished vocabulary.
  • the terminal stores the honorific vocabulary and the honorary vocabulary (for example, you, please, please, etc.), and when detecting that the content of the short message includes the honorific vocabulary or the distinguished vocabulary, the terminal determines that the contact is an important contact. people.
  • the honorific vocabulary and the honor vocabulary are obtained based on the content of the short message sent with the important contact added.
  • Step 1208 If the contact is an important contact, the group adding prompt is displayed in the contact information interface corresponding to the contact.
  • the terminal displays a group addition prompt in the contact information interface corresponding to the contact, prompting the user to add the contact to the preset contact group.
  • the terminal recognizes "Zhang San” as an important contact, thereby displaying the group addition prompt 513 in the contact information interface 51.
  • Step 1209 If the contact is an important contact, when receiving the contact call, or calling the contact, the group addition prompt is displayed in the call interface.
  • the user needs to display the contact information interface to know the identified important contacts.
  • the terminal displays the group in the call interface. Add a prompt to prompt the user to add the important contact to the default contact group.
  • the terminal recognizes “Zhang San” as an important contact.
  • the terminal displays a group addition prompt 523 in the call interface 52, and displays a quick add control 524, which is convenient for the user. Quickly add Zhang San to the VIP contact group.
  • step 1210 if the contact is an important contact, a group addition prompt is displayed in the location corresponding to the contact in the address book.
  • the terminal displays a group adding prompt in the address book corresponding to the important contact in the address book, when When the user opens the address book, he or she can add a prompt according to the group to complete the group addition.
  • the terminal determines that the contacts "Chen Qi” and "Zhang San” are important contacts, so that when the address book 53 is displayed, the corresponding entries in "Chen Qi” and “Zhang San” are respectively displayed.
  • a group addition prompt 531 is displayed.
  • the preset contact group editing interface is set in the terminal, and when the user selects to add a new contact to the preset contact group in the interface, the determined display is displayed in the interface.
  • Important contacts so users can add quickly. For example, when a user triggers adding a contact to a preset contact group, a drop-down box is displayed in the interface, and the determined drop-down box preferentially displays the determined important contact.
  • the terminal identifies whether the contact is an important contact according to the name information (including the contact name and the note name), and/or the historical call information, and/or the short message sending content, and performs grouping on the important contact. Groups add hints to improve the accuracy of group add hints, thus avoiding the omissions caused by users manually identifying and manually adding important contacts.
  • the terminal displays the group adding prompt in the contact information interface, the call interface or the address book, so that the user can quickly add the important contact to the preset contact group, thereby improving the group.
  • the efficiency of group addition is the group adding prompt in the contact information interface, the call interface or the address book, so that the user can quickly add the important contact to the preset contact group, thereby improving the group. The efficiency of group addition.
  • FIG. 16 is a structural block diagram of a notification reminding apparatus provided by an exemplary embodiment of the present application.
  • the notification reminding device includes an identification module 1610, a reminding module 1620, and a prohibiting reminding module 1630.
  • the identification module 1610 is configured to identify a contact corresponding to the notification when the notification is received in the do not disturb mode, where the notification is at least one of an incoming call notification, a short message notification, or an application notification;
  • the reminding module 1620 is configured to: when the contact belongs to the preset contact group, use a predetermined manner to notify the reminder;
  • the reminding module 1630 is configured to not notify the reminder when the contact does not belong to the preset contact group
  • the preset contact group is a group that allows notification reminders in the DND mode by default.
  • the reminder module 1620 includes:
  • a display unit 1621 configured to display a notification processing interface corresponding to the notification, where the notification processing interface includes a group identifier of the preset contact group;
  • the reminding unit 1622 is configured to perform an audible reminder and/or a vibrating reminder to the notification.
  • the reminding unit 1622 is specifically configured to:
  • the mode type belongs to the first mode type, performing a sound reminding according to the first prompt sound parameter, and/or performing a vibration reminding according to the first vibration parameter, where the first mode type includes at least at least one of a sleep mode and a silent mode One type;
  • the mode type belongs to the second mode type, performing a sound reminding according to the second prompt sound parameter, and/or performing a vibration reminding according to the second vibration parameter, where the second mode type includes at least at least a game mode and a conference mode One type;
  • the volume of the prompt sound indicated by the first prompt sound parameter is greater than the volume of the prompt sound indicated by the second prompt sound parameter; the vibration frequency indicated by the first vibration parameter is greater than the vibration frequency indicated by the second vibration parameter.
  • a first removal control is set in the notification processing interface
  • the device further includes:
  • the first removing module 1640 is configured to remove the contact from the preset contact group when receiving a click operation on the first removal control.
  • the device further includes:
  • the first display module 1650 is configured to: when the target contact does not belong to the preset contact group, display an add control in the contact information interface corresponding to the target contact;
  • the adding module 1660 is configured to add the target contact to the preset contact group when receiving a click operation on the added control.
  • the device further includes:
  • the second display module 1670 is configured to: when the target contact belongs to the preset contact group, display a second removal control in the contact information interface corresponding to the target contact;
  • the second removal module 1680 is configured to remove the target contact from the preset contact group when receiving a click operation on the second removal control.
  • FIG. 18 is a structural block diagram of a group adding apparatus provided by an exemplary embodiment of the present application.
  • the group adding device includes an obtaining module 1810, an identifying module 1820, and a display module 1830.
  • the obtaining module 1810 is configured to obtain contact information corresponding to the contact, where the contact information includes name information and/or historical communication information;
  • the identifying module 1820 is configured to identify, according to the contact information, whether the contact is an important contact;
  • the display module 1830 is configured to: if the contact is the important contact, display a group adding prompt, the group adding prompt is used to prompt to add the contact to the preset contact group, the pre- Set a contact group to be a group that allows notification reminders in DND mode by default.
  • the contact information includes the name information
  • the identification module 1820 includes:
  • a first obtaining unit 1821 configured to acquire a note and/or a contact name included in the name information
  • the first determining unit 1822 is configured to determine the contact as the important contact if the note or the contact name belongs to the pre-device vocabulary.
  • the contact information includes the historical communication information
  • the identification module 1820 includes:
  • the second obtaining unit 1823 is configured to acquire the call information included in the historical communication information, where the call information includes at least one of a frequency of a call, a duration of a call, a duration of a call, a number of times of receiving, a number of hangups, and a number of callbacks;
  • the second determining unit 1824 is configured to determine whether the contact is the important contact if the call information meets a preset condition.
  • the preset condition includes at least one of the following:
  • the frequency of the call is greater than the first threshold; or,
  • the duration of the call is greater than a second threshold; or,
  • the number of calls in the predetermined time period is greater than a third threshold; or,
  • the ratio of the number of times of receiving to the number of times of hanging up is greater than a fourth threshold
  • the number of callbacks is greater than a fifth threshold.
  • the identifying module 1820 further includes:
  • the third obtaining unit 1825 is configured to acquire the short message sending content included in the historical communication information
  • the third determining unit 1826 is configured to determine that the contact is the important contact, if the preset content includes the preset vocabulary, and the preset vocabulary includes an honorific vocabulary and a distinguished vocabulary.
  • the display module 1830 includes:
  • the first display unit 1831 is configured to display the group addition prompt in a contact information interface corresponding to the contact;
  • the second display unit 1832 is configured to display the group adding prompt in the call interface when receiving the contact call, or when calling the contact;
  • the third display unit 1833 is configured to display the group addition prompt in a location corresponding to the contact in the address book.
  • FIG. 20 is a structural block diagram of a notification reminding apparatus provided by an exemplary embodiment of the present application.
  • the notification reminding device includes an identification module 2010, a level determining module 2020, and a reminding module 2030.
  • the identification module 2010 is configured to identify, when the notification is received, a contact corresponding to the notification, where the notification is at least one of an incoming call notification, a short message notification, or an application notification;
  • the level determining module 2020 is configured to determine an important level of the contact according to the preset contact group to which the contact belongs;
  • the reminding module 2030 is configured to determine whether to perform a notification reminder according to the important level
  • the importance level of each contact is the same in the same preset contact group, and the important levels corresponding to different preset contact groups are different.
  • the reminding module 2030 includes:
  • the obtaining unit 2031 is configured to acquire the DND mode in which the terminal is currently located;
  • a determining unit 2032 configured to determine a target DND mode corresponding to the important level
  • the reminding unit 2033 is configured to: if the DND mode belongs to the target DND mode, perform a notification reminder;
  • the reminding unit 2034 is configured to not notify the reminder if the DND mode does not belong to the target DND mode
  • the number of the target DND modes corresponding to different importance levels is different, and the important level is positively correlated with the number of the target DND modes.
  • the determining unit 2032 is configured to:
  • the silent mode and the game mode are determined to be the target DND mode
  • the silent mode, the game mode, the conference mode, and the sleep mode are determined as the target do not disturb mode.
  • the reminding unit 2033 is configured to:
  • the importance level is positively correlated with the volume of the prompt sound indicated by the prompt sound parameter, and the important level is positively correlated with the vibration frequency indicated by the vibration parameter.
  • the device further includes:
  • the receiving module 2040 is configured to receive an operation on the notification when the notification reminder is performed
  • a group determining module 2050 configured to determine a target contact group of the contact according to an operation type of the operation
  • the prompting module 2060 is configured to display a group adjustment prompt in the contact information interface corresponding to the contact if the preset contact group and the target contact group to which the contact belongs are different;
  • the important level corresponding to the target contact group is greater than or equal to the important level corresponding to the preset contact group, when the operation type is an answering or replying operation; When the operation is hanged up or deleted, the importance level corresponding to the target contact group is less than or equal to the important level corresponding to the preset contact group.
  • the embodiment of the present application further provides a computer readable medium storing at least one instruction, the at least one instruction being loaded and executed by the processor to implement the notification reminding method described in the foregoing embodiments. , or, group add method.
  • the embodiment of the present application further provides a computer program product, where the computer program product stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the notification reminding method described in the foregoing embodiments, or , group add method.

Abstract

本申请实施例公开了一种通知提醒方法、群组添加方法、装置、终端及存储介质，属于通知提醒领域，所述方法包括：免打扰模式下，当接收到通知时，识别通知对应的联系人，通知为来电通知、短信通知或应用通知中的至少一种；若联系人属于预设联系人群组，则采用预定方式进行通知提醒；若联系人不属于预设联系人群组，则不进行通知提醒；其中，预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。本申请实例中，当在免打扰模式下接收到该预设联系人群组内联系人的通知时，终端能够跳过免打扰机制，对通知进行通知提醒，从而避免遗漏重要联系人的通知。

Description

通知提醒方法、群组添加方法、装置、终端及存储介质
本申请实施例要求于2017年12月25日提交，申请号为201711421116.2、发明名称为“通知提醒方法、装置、终端及存储介质”的中国专利申请，申请号为201711418894.6、发明名称为“群组添加方法、装置、终端及存储介质”的中国专利申请，以及申请号为201711419886.3、发明名称为“通知提醒方法、装置、终端及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请实施例中。
技术领域
本申请实施例涉及通知提醒领域，特别涉及一种通知提醒方法、群组添加方法、装置、终端及存储介质。
背景技术
为了避免突如其来的来电或短信对当前进行的重要事务造成干扰，在进行重要事务时，用户通常会将终端设置成免打扰模式。
相关技术中，终端在系统设置中提供了免打扰设置入口，用户通过该入口即可快速设置终端进入免打扰模式。当在免打扰模式下接收到来电或短信时，终端将不会对来电或短信进行声音或振动提醒。
发明内容
本申请实施例提供了一种通知提醒方法、群组添加方法、装置、终端及存储介质，技术方案如下：
一方面，提供了一种通知提醒方法，所述方法包括：
免打扰模式下，当接收到通知时，识别通知对应的联系人，通知为来电通知、短信通知或应用通知中的至少一种；
若联系人属于预设联系人群组，则采用预定方式进行通知提醒；
若联系人不属于预设联系人群组，则不进行通知提醒；
其中，预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。
另一方面，提供了一种通知提醒装置，所述装置包括：
识别模块，用于免打扰模式下，当接收到通知时，识别通知对应的联系人，通知为来电通知、短信通知或应用通知中的至少一种；
提醒模块，用于当联系人属于预设联系人群组时，采用预定方式进行通知提醒；
禁止提醒模块，用于当联系人不属于预设联系人群组时，不进行通知提醒；
其中，预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。
另一方面，提供了一种群组添加方法，所述方法包括：
获取联系人对应的联系人信息，所述联系人信息包括名称信息和/或历史通信信息；
根据所述联系人信息识别所述联系人是否为重要联系人；
若所述联系人为所述重要联系人，则显示群组添加提示，所述群组添加提示用于提示将所述联系人添加到预设联系人群组，所述预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。
另一方面，提供了一种群组添加装置，所述装置包括：
获取模块，用于获取联系人对应的联系人信息，所述联系人信息包括名称信息和/或历史通信信息；
识别模块，用于根据所述联系人信息识别所述联系人是否为重要联系人；
显示模块，用于若所述联系人为所述重要联系人，则显示群组添加提示，所述群组添加提示用于提示将所述联系人添加到预设联系人群组，所述预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。
另一方面，提供了一种通知提醒方法，所述方法包括：
免打扰模式下，当接收到通知时，识别所述通知对应的联系人，所述通知为来电通知、短信通知或应用通知中的至少一种；
根据所述联系人所属的预设联系人群组，确定所述联系人的重要等级；
根据所述重要等级确定是否进行通知提醒；
其中，同一预设联系人群组中，各个联系人的所述重要等级相同，且不同预设联系人群组对应的所述重要等级不同。
另一方面，提供了一种通知提醒装置，所述装置包括：
识别模块，用于免打扰模式下，当接收到通知时，识别所述通知对应的联系人，所述通知为来电通知、短信通知或应用通知中的至少一种；
等级确定模块，用于根据所述联系人所属的预设联系人群组，确定所述联系人的重要等级；
提醒模块，用于根据所述重要等级确定是否进行通知提醒；
其中，同一预设联系人群组中，各个联系人的所述重要等级相同，且不同预设联系人群组对应的所 述重要等级不同。
另一方面，提供了一种终端，所述终端包括处理器和存储器，所述存储器中存储有至少一条指令，所述指令由所述处理器加载并执行以实现如上述方面所述的通知提醒方法，或，群组添加方法。
另一方面，提供了一种计算机可读存储介质，所述存储介质中存储有至少一条指令，所述指令由处理器加载并执行以实现如上述方面所述的通知提醒方法，或，群组添加方法。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1和图2是本申请一个示例性实施例提供的终端的结构方框图；
图3示出了本申请一个示例性实施例提供的通知提醒方法的流程图；
图4示出了本申请另一个示例性实施例提供的通知提醒方法的流程图；
图5和图6是联系人信息界面的界面示意图；
图7是来电挂断接听界面的界面示意图；
图8示出了本申请一个示例性实施例提供的通知提醒方法的流程图；
图9示出了本申请另一个示例性实施例提供的通知提醒方法的流程图；
图10是提示调整联系人群组的界面示意图；
图11示出了本申请一个示例性实施例提供的群组添加方法的流程图；
图12示出了本申请另一个示例性实施例提供的群组添加方法的流程图；
图13至图15是显示群组添加信息的界面示意图；
图16示出了本申请一个示例性实施例提供的通知提醒装置的结构框图；
图17示出了本申请另一个示例性实施例提供的通知提醒装置的结构框图；
图18示出了本申请一个示例性实施例提供的通知提醒装置的结构框图；
图19示出了本申请另一个示例性实施例提供的通知提醒装置的结构框图；
图20示出了本申请一个示例性实施例提供的群组添加装置的结构框图；
图21示出了本申请另一个示例性实施例提供的群组添加装置的结构框图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
参考图1和图2所示，其示出了本申请一个示例性实施例提供的终端100的结构方框图。该终端100可以智能手机、平板电脑、笔记本电脑等。本申请中的终端100可以包括一个或多个如下部件：处理器110、存储器120和触摸显示屏130。其中，存储器120中存储有至少一条指令，所述指令由处理器110加载并执行以实现下述实施例所述的通知提醒方法，或，群组添加方法。
处理器110可以包括一个或者多个处理核心。处理器110利用各种接口和线路连接整个终端100内的各个部分，通过运行或执行存储在存储器120内的指令、程序、代码集或指令集，以及调用存储在存储器120内的数据，执行终端100的各种功能和处理数据。可选地，处理器110可以采用数字信号处理(Digital Signal Processing，DSP)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)、可编程逻辑阵列(Programmable Logic Array，PLA)中的至少一种硬件形式来实现。处理器110可集成中央处理器(Central Processing Unit，CPU)、图像处理器(Graphics Processing Unit，GPU)和调制解调器等中的一种或几种的组合。其中，CPU主要处理操作系统、用户界面和应用程序等；GPU用于负责触摸显示屏130所需要显示的内容的渲染和绘制；调制解调器用于处理无线通信。可以理解的是，上述调制解调器也可以不集成到处理器110中，单独通过一块芯片进行实现。
存储器120可以包括随机存储器(Random Access Memory，RAM)，也可以包括只读存储器(Read-Only Memory)。可选地，该存储器120包括非瞬时性计算机可读介质(non-transitory computer-readable storage medium)。存储器120可用于存储指令、程序、代码、代码集或指令集。存储器120可包括存储程序区和存储数据区，其中，存储程序区可存储用于实现操作系统的指令、用于至少一个功能的指令(比如触控功能、声音播放功能、图像播放功能等)、用于实现下述各个方法实施例的 指令等；存储数据区可存储根据终端100的使用所创建的数据(比如音频数据、电话本)等。
以操作系统为安卓(Android)系统为例，存储器120中存储的程序和数据如图1所示，存储器120中存储有Linux内核层220、系统运行库层240、应用框架层260和应用层280。Linux内核层220为终端100的各种硬件提供了底层的驱动，如显示驱动、音频驱动、摄像头驱动、蓝牙驱动、Wi-Fi驱动、电源管理等。系统运行库层240通过一些C/C++库来为Android系统提供了主要的特性支持。如SQLite库提供了数据库的支持，OpenGL/ES库提供了3D绘图的支持，Webkit库提供了浏览器内核的支持等。在系统运行库层240中还提供有Android运行时库242(Android Runtime)，它主要提供了一些核心库，能够允许开发者使用Java语言来编写Android应用。应用框架层260提供了构建应用程序时可能用到的各种API，开发者也可以通过使用这些API来构建自己的应用程序，比如活动管理、窗口管理、视图管理、通知管理、内容提供者、包管理、通话管理、资源管理、定位管理。应用层280中运行有至少一个应用程序，这些应用程序可以是操作系统自带的联系人程序、短信程序、时钟程序、相机应用等；也可以是第三方开发者所开发的应用程序，比如即时通信程序、相片美化程序等。
以操作系统为IOS系统为例，存储器120中存储的程序和数据如图2所示，IOS系统包括：核心操作系统层320(Core OS layer)、核心服务层340(Core Services layer)、媒体层360(Media layer)、可触摸层380(Cocoa Touch Layer)。核心操作系统层320包括了操作系统内核、驱动程序以及底层程序框架，这些底层程序框架提供更接近硬件的功能，以供位于核心服务层340的程序框架所使用。核心服务层340提供给应用程序所需要的系统服务和/或程序框架，比如基础(Foundation)框架、账户框架、广告框架、数据存储框架、网络连接框架、地理位置框架、运动框架等等。媒体层360为应用程序提供有关视听方面的接口，如图形图像相关的接口、音频技术相关的接口、视频技术相关的接口、音视频传输技术的无线播放(AirPlay)接口等。可触摸层380为应用程序开发提供了各种常用的界面相关的框架，可触摸层380负责用户在终端100上的触摸交互操作。比如本地通知服务、远程推送服务、广告框架、游戏工具框架、消息用户界面接口(User Interface，UI)框架、用户界面UIKit框架、地图框架等等。
在图2所示出的框架中，与大部分应用程序有关的框架包括但不限于：核心服务层340中的基础框架和可触摸层380中的UIKit框架。基础框架提供许多基本的对象类和数据类型，为所有应用程序提供最基本的系统服务，和UI无关。而UIKit框架提供的类是基础的UI类库，用于创建基于触摸的用户界面，iOS应用程序可以基于UIKit框架来提供UI，所以它提供了应用程序的基础架构，用于构建用户界面，绘图、处理和用户交互事件，响应手势等等。
触摸显示屏130用于显示各个应用程序的用户界面，以及用于接收用户使用手指、触摸笔等任何适合的物体在其上或附近的触摸操作。触摸显示屏130通常设置在终端100的前面板。触摸显示屏130可被设计成为全面屏、曲面屏或异型屏。触摸显示屏130还可被设计成为全面屏与曲面屏的结合，异型屏与曲面屏的结合，本实施例对此不加以限定。
除此之外，本领域技术人员可以理解，上述附图所示出的终端100的结构并不构成对终端100的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。比如，终端100中还包括射频电路、输入单元、传感器、音频电路、无线保真(Wireless Fidelity，WiFi)模块、电源、蓝牙模块等部件，在此不再赘述。
终端在接收到新消息时，往往会即时采用通知栏、弹窗、响铃、振动等方式向用户提醒该新消息。但是，若用户当前正处于开会、睡眠、会议、游戏等过程中，则很可能不希望被外界消息打扰。为此，终端可以设置有免打扰模式，若用户选择进入免打扰模式，则终端启用免打扰机制，即停止对接收到的消息进行通知栏提醒、弹窗提醒、响铃提醒、振动提醒和/或其它提醒。在结束免打扰模式时，终端恢复正常的提醒方式，还可以对免打扰模式持续期间接收到的消息进行补充提醒。
免打扰模式满足了用户在特定时间场合不被外界消息打扰的需求，但也引入了新的问题。例如，若用户在看电影时将终端设置为免打扰模式，在电影过程中终端又接到了重要来电，而该重要来电的响铃又被免打扰模式禁止，则用户很可能会错过该重要来电，进而面临较大损失。
为了在保证免打扰效果的同时，避免用户遗漏重要通知，本申请实施例中，终端中设置有全局的预设联系人群组，用户可以将重要联系人添加到该群组。免打扰模式下，当接收到该预设联系人群组内重 要联系人的通知时，终端绕过免打扰机制，实现针对重要联系人的通知提醒；同时，对于预设联系人群组以外联系人的通知，终端仍旧启用免打扰机制，从而避免此类对用户造成干扰。下面采用示意性的实施例进行说明。
请参考图3，其示出了本申请一个示例性实施例提供的通知提醒方法的流程图。本实施例以该方法应用于上述图1或图2提供的终端中来举例说明。所述方法包括：
步骤301，免打扰模式下，当接收到通知时，识别通知对应的联系人，通知为来电通知、短信通知或应用通知中的至少一种。
相关技术中，免打扰模式下，终端接收到通知时直接启用免打扰机制进行免打扰处理，禁止进行相应的通知提醒；而本申请实施例中，为了实现在免打扰模式下，对重要联系人的通知进行提醒，在免打扰模式下接收到通知时，终端并非直接启用免打扰机制，而是首先识别该通知对应的联系人。
在一种可能的实施方式中，当接收到来电通知或短信通知时，终端获取来电方或短信发送方对应的电话号码，进而根据电话号码识别对应的联系人。
可选的，终端检测通讯录中是否存储有该电话号码，若未存储该电话号码，终端确定通知来自陌生联系人，并启用免打扰机制对通知进行免打扰处理；若存储有该电话号码，终端确定通知来自通讯录中的联系人，并进一步检测该联系人是否属于预设联系人群组，若属于，则执行下述步骤302，若不属于，则执行下述步骤303。
示意性的，终端接收到来电通知时，根据来电方的电话号码识别来电通知对应通讯录终端的联系人“张三”。
在其他可能的实施方式中，当接收到应用推送的应用通知时(比如邮件应用推送的邮件通知，即时通信应用推送的即时通信消息通知或音视频请求等等)，终端获取应用通知对应的通知方标识，并根据该通知方标识确定通知对应的联系人。其中，该通知方标识可以为发件方的邮箱地址或即时通信消息发送方的即时通信帐号。
针对根据通知方标识确定联系人的方式，可选的，当终端通讯录中包含联系人对应的邮箱地址、即时通信帐号等信息时，终端即根据通知方标识，在通讯录中查找应用通知对应的联系人。
需要说明的是，本实施例仅以基于通讯录确定联系人为例进行示意性说明(系统级)，在其他可能的实施方式中，该通知提醒方法还可以应用于具体应用中(应用级)，即基于应用中的联系人列表确定通知对应的联系人，本实施例并不对此构成限定。
步骤302，若联系人属于预设联系人群组，则采用预定方式进行通知提醒。
可选的，预定方式包括屏幕显示提醒、声音提醒和振动提醒中的至少一种。
终端中设置有预设联系人群组，该预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组，可选的，预设联系人群组中的联系人由用户手动添加。
可选的，该预设联系人群组是终端系统默认设置的群组，而非用户手动创建，用户仅能够向该预设联系人群组中添加或移除联系人。并且，该预设联系人群组为全局群组，不论终端处于何种类型的免打扰模式，终端均允许对该预设联系人群组中的联系人进行通知提醒，而无需用户在各种免打扰模式下进行手动设置。
在一种可能的实施方式中，终端为预设联系人群组中各个联系人设置相应的预设群组标识，在检测联系人是否属于预设联系人群组时，终端即检测联系人是否存在对应有预设群组标识，若存在，则确定联系人属于预设联系人群组，进而绕过免打扰机制，进行通知提醒。
可选的，终端为预设联系人群组中各个联系人设置预设群组标识“VIP”，当检测到联系人“张三”对应“VIP”标识时，即确定“张三”属于预设联系人群组，并对“张三”的来电进行来电提醒。
步骤303，若联系人不属于预设联系人群组，则不进行通知提醒。
当检测到联系人不属于预设联系人群组时，终端确定当前联系人并非重要联系人，从而启用免打扰机制对接收到的通知进行免打扰处理。
可选的，进行免打扰处理时，终端不显示通知处理界面，并不进行声音和振动提醒。
综上所述，本实施例中，终端中预先设置默认情况下，允许在免打扰模式下进行通知提醒的预设联系人群组，当在免打扰模式下接收到该预设联系人群组内联系人的通知时，终端能够跳过免打扰机制， 对通知进行通知提醒，从而避免遗漏重要联系人的通知；同时，终端处于免打扰模式时，即默认允许对预设联系人群组中的联系人进行通知提醒，无需用户手动设置，从而简化了设置免打扰模式的操作过程。
为了方便用户对预设联系人群组中的联系人进行管理，在一种可能的实施方式中，每个联系人对应的联系人信息界面中均设置有相应控件，用户通过该控件即可将联系人添加到预设联系人群组，或，将联系人从预设联系人群组中移除。请参考图4，其示出了本申请另一个示例性实施例提供的通知提醒方法的流程图。该方法包括如下步骤。
步骤401，当目标联系人不属于预设联系人群组时，在目标联系人对应的联系人信息界面中显示添加控件。
通讯录中各个联系人对应各自的联系人信息界面，该联系人信息界面中包含联系人名称、备注、电话号码、住址、邮箱等信息，且用户可以对联系人信息界面中包含的信息进行更新。
在一种可能的实施方式中，当接收到查看目标联系人对应联系人信息界面的操作时，终端检测目标联系人是否属于预设联系人群组，其中，检测目标联系人是否属于预设联系人群组的方式详见上述步骤302，本实施例在此不再赘述。
当检测到目标联系人不属于预设联系人群组时，为了方便用户将目标联系人添加至预设联系人群组，终端在当前联系人信息界面显示添加控件，该添加控件可以为添加按钮。
示意性的，如图5所示，当打开联系人“张三”对应的联系人信息界面51时，终端检测“张三”是否属于VIP联系人群组(即预设联系人群组)，当“张三”不属于VIP联系人群组时，终端即在联系人信息界面51中显示添加控件511
步骤402，当接收到对添加控件的点击操作时，将目标联系人添加到预设联系人群组。
当目标联系人为重要联系人时，用户即可通过该添加控件将目标联系人添加到预设联系人群组中，相应的，终端接收对添加控件的点击操作，并将目标联系人添加到预设联系人群组中。
在一种可能的实施方式中，当接收到对添加控件的点击操作时，终端为目标联系人设置预设联系人群组对应的预设群组标识，比如，终端为目标联系人设置“VIP”标识。
终端将目标联系人添加到预设联系人群组后，停止在联系人信息界面中显示添加控件。可选的，终端将联系人信息界面中的添加控件替换为移除控件，以便用户将目标联系人移出预设联系人群组。
步骤403，当目标联系人属于预设联系人群组时，在目标联系人对应的联系人信息界面中显示第二移除控件。
与上述步骤401相反的，当目标联系人已经属于预设联系人群组时，终端在联系人信息界面中显示移除控件，以便用户通过该移除控件将目标联系人移出预设联系人群组。
示意性的，如图6所示，当打开联系人“张三”对应的联系人信息界面51时，终端检测到“张三”属于VIP联系人群组，从而在联系人信息界面51中显示移除控件512。
步骤404，当接收到对第二移除控件的点击操作时，将目标联系人从预设联系人分组中移除。
相应的，当目标联系人并非重要联系人时，用户即可通过该移除控件将目标联系人移出到预设联系人群组，相应的，终端接收对移除控件的点击操作，并将目标联系人从预设联系人群组中移除。
在一种可能的实施方式中，当接收到对移除控件的点击操作时，终端删除目标联系人对应的预设群组标识，比如，终端删除目标联系人的“VIP”标识。
终端将目标联系人移出到预设联系人群组后，停止在联系人信息界面中显示移除控件。可选的，终端将联系人信息界面中的移除控件替换为添加控件，以便用户重新将目标联系人添加到预设联系人群组。
在其他可能的实施方式中，终端中设置有预设联系人群组管理界面，用户在该界面中可以对预设联系人群组中的联系人进行统一管理。可选的，该界面中设置有移除控件，通过该移除控件，用户可以移除预设联系人群组中已有的联系人；该界面中还设置有添加控件，通过该添加控件，用户也可以向预设联系人群组中新增联系人，本申请实施例并不对管理预设联系人群组的具体方式进行限定。
步骤405，免打扰模式下，当接收到通知时，识别通知对应的联系人，通知为来电通知、短信通知或应用通知中的至少一种。
本步骤的实施方式与上述步骤301相似，本实施例在此不再赘述。
步骤406，若联系人属于预设联系人群组，则显示通知对应的通知处理界面，通知处理界面中包含预设联系人群组的群组标识。
当联系人属于预设联系人群组时，终端根据通知类型，显示相应的通知处理界面，提示用户对通知进行处理。其中，当通知类型为来电时，终端即显示来电挂断接听界面；当通知类型为短信时，终端即显示短信阅读回复界面。
可选的，为了使用户知悉当前通知来自预设联系人群组中的联系人，终端在通知处理界面中显示预设联系人群组的群组标识。
示意性的，如图7所示，当在免打扰模式下接收到联系人“张三”的来电时，由于“张三”属于VIP联系人群组，因此，终端绕过免打扰机制显示来电挂断接听界面52，并在来电挂断接听界面52中显示群组标识521。
步骤407，对通知进行声音提醒和/或振动提醒。
为了进一步提高提醒效果，终端在显示通知处理界面的同时，对通知进行声音提醒和/或振动提醒。
由于终端可以提供适用于不同场景下免打扰模式，且不同免打扰模式下，用户对声音和振动的感知程度不同，因此，为了使用户能够感知到声音和振动，终端根据当前所处的免打扰模式的模式类型，启用相应的提示音参数和/或振动参数进行声音提醒和/或振动提醒。
在一种可能的实施方式中，本步骤包括如下步骤。
一、获取免打扰模式的模式类型。
终端系统提供多种免打扰模式，当终端进入免打扰模式时，终端即处于免打扰状态。可选的，免打扰模式的模式类型包括：静音模式、会议模式、游戏模式和睡眠模式。
若当前的联系人属于预设联系人群组时，终端即确定当前所处的免打扰模式的模式类型。
二、若模式类型属于第一模式类型，则根据第一提示音参数进行声音提醒，和/或，根据第一振动参数进行振动提醒，第一工作模式包括睡眠模式和静音模式中的至少一种。
三、若模式类型属于第二模式类型，则根据第二提示音参数进行声音提醒，和/或，根据第二振动参数进行振动提醒，第二工作模式包括游戏模式和会议模式中的至少一种。
根据不同免打扰模式下用户对声音和振动的感知能力，终端预先针对不同类型的免打扰模式设置不同的提示音参数和振动参数。确定出当前所处的免打扰模式的模式类型后，终端进一步获取模式类型对应的提示音参数和振动参数，从而基于获取到的参数进行声音和振动提示。
由于用户在睡眠状态下感知声音和振动的能力较弱，且用户在睡眠时，通常将终端设置成睡眠模式或静音模式(即第一模式类型)，因此，终端为第一模式类型设置第一提示音参数和第二振动参数。
而用户在进行游戏或进行会议时，感知声音和振动的能力较强，且用户在进行游戏时，通常将终端设置成游戏模式(即第二模式类型)，在进行会议时，通常将终端设置成会议模式(即第二模式类型)，因此，终端为第二模式类型设置第二提示音参数和第二振动参数。其中，第一提示音参数指示的提示音音量大于第二提示音参数指示的提示音音量；第一振动参数指示的振动频率大于第二振动参数指示的振动频率。
示意性的，免打扰模式的模式类型、提示音参数以及振动参数的三者时间的对应关系如表一所示。
表一
模式类型 提示音参数 振动参数
第一模式类型(睡眠模式、静音模式) 40dB 5次/秒
第二模式类型(会议模式、游戏模式) 30dB 3次/秒
可选的，提示音参数中还包括提示音音调等参数，振动参数中还包括振动幅度等参数，本实施例并不对此进行限定。
相应的，当处于第一模式类型时，为了提高用户注意到通知提醒的概率，终端根据第一提示音参数和/或第一振动参数对通知进行强提醒；当处于第二模式类型时，终端根据第二提示音参数和/或第二振动参数对通知进行普通提醒。
需要说明的是，上述实施例仅以两类模式类型(对应两组提示音参数和振动参数)为例进行说明，在其他可能的实施方式中，终端可以针对各种模式类型设置不同的提示音参数和振动参数，本实施例并 不对此构成限定。
步骤408，当接收到对通知处理界面中第一移除控件的点击操作时，将联系人从预设联系人分组中移除。
上述步骤403至404中，将联系人移出预设联系人群组时，需要在联系人对应的联系人信息界面中进行操作。为了提高移除联系人的效率，在一种可能的实施方式中，终端显示的通知处理界面中还设置有第一移除控件，用户通过第一移除控件即可快速将当前联系人从预设联系人群组中移除。
示意性的，如图7所示，终端在来电挂断接听界面52中显示移除控件522，当用户点击移除控件522后，联系人“张三”即从VIP联系人群组中移除。
步骤409，若联系人不属于预设联系人群组，则不进行通知提醒。
本步骤的实施方式与上述步骤303相似，本实施例在此不再赘述。
本实施例中，终端在联系人信息界面显示添加或移除控件，使得用户能够快速将联系人添加到预设联系人群组或移出预设联系人群组；从而提高预设联系人群组的管理效率；进一步的，终端在通知处理界面显示移除控件，方便用户接收到通知提醒时，快速将当前联系人移出预设联系人群组，进一步提高预设联系人群组的管理效率。
本实施例中，终端根据不同免打扰模式下用户对声音和振动的感知能力，预先针对不同模式类型的免打扰模式设置不同的提示音参数和振动参数，从而根据当前免打扰模式对应的参数进行声音和/或振动提醒，提高了各种免打扰模式下，用户对通知提醒的感知能力，进一步降低了用户遗漏重要联系人通知的概率。
上述实施例中，终端中仅设置有一个预设联系人群组，该预设联系人群组中各个联系人的通知均不受免打扰机制限制。然而，在某些特定场景下，用户可能期望仅对预设联系人群组中部分联系人的通知进行提醒。
在一种可能的实施方式中，终端中设置有对应不同重要等级的多个预设联系人群组，用户可以根据联系人的重要程度将其添加到相应的预设联系人群组中。在免打扰模式下接收到通知时，终端即根据联系人所属的预设联系人群组确定其重要等级，进而根据重要等级确定是否进行通知提醒。下面采用示意性的实施例进行说明。
请参考图8，其示出了本申请一个示例性实施例提供的通知提醒方法的流程图。该方法包括如下步骤。
步骤801，免打扰模式下，当接收到通知时，识别通知对应的联系人，通知为来电通知、短信通知或应用通知中的至少一种。
在一种可能的实施方式中，当接收到来电通知或短信通知时，终端获取来电方或短信发送方对应的电话号码，进而根据电话号码识别对应的联系人。
可选的，终端检测通讯录中是否存储有该电话号码，若未存储该电话号码，终端确定通知来自陌生联系人，并启用免打扰机制对通知进行免打扰处理；若存储有该电话号码，终端确定通知来自通讯录中的联系人，并进一步确定该联系人所属的预设联系人群组，执行下述步骤802；若该联系人不属于任何预设联系人群组，终端启用免打扰机制对通知进行免打扰处理。
在另一种可能的实施方式中，当接收到应用推送的应用通知时(比如邮件应用推送的邮件通知，即时通信应用推送的即时通信消息通知或音视频请求等等)，终端获取应用通知对应的通知方标识，并根据该通知方标识确定通知对应的联系人。其中，该通知方标识可以为发件方的邮箱地址或即时通信消息发送方的即时通信帐号。
针对根据通知方标识确定联系人的方式，可选的，当终端通讯录中包含联系人对应的邮箱地址、即时通信帐号等信息时，终端即根据通知方标识，在通讯录中查找应用通知对应的联系人。
步骤802，根据联系人所属的预设联系人群组，确定联系人的重要等级，其中，同一预设联系人群组中，各个联系人的重要等级相同，且不同预设联系人群组对应的重要等级不同。
终端中预先设置有至少两个预设联系人群组，每个预设联系人群组对应各自的重要等级，相应的，用户根据通讯录中联系人的重要程度，手动将联系人添加到相应的预设联系人群组中。
示意性的，不同预设联系人群组与重要等级的对应关系如表二所示。
表二
预设联系人群组 重要程度 联系人
第一联系人群组 一级 刘一、陈二、张三
第二联系人群组 二级 李四、王五、赵六、孙七
第三联系人群组 三级 周八、吴九、郑十
示意性的，终端识别出通知对应的联系人为“张三”，并根据表二所示的对应关系确定联系人“张三”对应的重要程度为一级。
针对确定联系人所属预设联系人群组的方式，在一种可能的实施方式中，终端为不同预设联系人群组中的联系人设置不同的群组标识，终端即根据联系人对应的群组标识确定其所属的预设联系人群组。
比如，终端分别为第一联系人群组、第二联系人群组和第三联系人群组中的联系人设置群组标识“VIP1”、“VIP2”和“VIP3”。终端根据联系人“张三”对应的群组标识“VIP1”确定其属于第一联系人群组。
步骤803，根据重要等级确定是否进行通知提醒。
在一种可能的实施方式中，不同类型的免打扰工作模式下，允许进行通知提醒的联系人的重要等级不同，相应的，终端根据当前所处免打扰工作模式的模式类型和联系人的重要等级，确定是否进行通知提醒。
其中，终端进行通知提醒的实施方式可以参考上述步骤302，终端禁止进行通知提醒的实施方式开参考上述步骤303，本实施例在此不再赘述。
比如，静音模式和游戏模式下，允许进行通知提醒的联系人的重要等级≥一级；会议模式下，允许进行通知提醒的联系人的重要等级≥二级；睡眠模式下，允许进行通知提醒的联系人的重要等级≥三级。结合表二中的数据，当在游戏模式下接收到联系人“张三”的来电通知时，终端进行来电提醒；当在会议模式或睡眠模式下接收到联系人“张三”的来电通知时，终端则不进行来电提醒。
综上所述，本实施例中，终端中预先设置对应不同重要等级的多个预设联系人群组，在免打扰模式下接收到通知时，终端即根据当前联系人所属的预设联系人群组，确定当前联系人的重要等级，进而根据该重要等级确定是否进行通知提醒；借助分级控制机制，终端实现细粒度的通知提醒管理，在避免用户遗漏重要联系人来电短信的同时，避免用户被重要联系人以外其他联系人打扰，提高了通知提醒的准确性，使得免打扰模式下的通知提醒更加符合用户预期。
在一种可能的实施方式中，终端预先建立不同重要等级与目标免打扰模式的对应关系，相应的，终端即根据当前所处的免打扰模式，以及当前联系人重要等级所对应的目标免打扰模式，确定是否进行通知提醒。
请参考图9，其示出了本申请另一个示例性实施例提供的通知提醒方法的流程图。该方法包括如下步骤。
步骤901，免打扰模式下，当接收到通知时，识别通知对应的联系人，通知为来电通知、短信通知或应用通知中的至少一种。
步骤902，根据联系人所属的预设联系人群组，确定联系人的重要等级，其中，同一预设联系人群组中，各个联系人的重要等级相同，且不同预设联系人群组对应的重要等级不同。
上述步骤901至902的详细实施方式可以参考上述步骤801至802，本实施例在此不再赘述。
在一种可能的实施方式中，若当前联系人属于某一预设联系人群组，终端则进一步获取当前所处的免打扰模式；若当前联系人不属于任何预设联系人群组，终端则对通知进行免打扰处理。
步骤903，获取终端当前所处的免打扰模式。
终端系统提供适用于不同场景的多种免打扰模式，当终端进入免打扰模式时，终端即处于免打扰状态。可选的，免打扰模式包括：静音模式、会议模式、游戏模式和睡眠模式。
步骤904，确定重要等级对应的目标免打扰模式。
对于重要等级较高的联系人，用户通常希望在各种免打扰模式下均能够进行通知提醒；而对于重要等级较低的联系人，用户则希望在部分免打扰模式下进行通知提醒，在特定免打扰模式下不进行通知提醒。
因此，终端预先设置不同重要等级与目标免打扰模式的对应关系，该目标免打扰模式即为允许进行 通知提醒的免打扰模式。其中，不同重要等级对应的目标免打扰模式的数量不同，且重要等级与目标免打扰模式的数量呈正相关关系，即重要等级越高，对应的目标免打扰模式的类型越多。
在一种可能的实施方式中，不同重要等级与目标免打扰模式的对应关系如表三所示。
表三
重要等级 目标免打扰模式
一级 静音模式、游戏模式
二级 静音模式、游戏模式、会议模式
三级 静音模式、游戏模式、会议模式、睡眠模式
当重要等级为一级时，将静音模式和游戏模式确定目标免打扰模式。
重要等级为一级的联系人的重要程度的最低，因此，仅在静音模式或游戏模式下接收到该联系人的来电或短信时，终端才会进行通知提醒。
当重要等级为二级时，将静音模式、游戏模式和会议模式确定为目标免打扰模式。
相较于重要等级为一级的联系人，重要等级为二级的联系人的重要程度更高，因此，除了在静音模式和游戏模式下进行通知提醒外，在会议模式下，终端也会对该联系人的来电或短信进行通知提醒。
当重要等级为三级时，将静音模式、游戏模式、会议模式和睡眠模式确定为目标免打扰模式。
对于重要等级最高的联系人，终端将所有免打扰模式均确定目标免打扰模式，确保在静音模式、游戏模式、会议模式和睡眠模式下，用户均能够接收到该联系人的来电和短信。
本实施例仅以设置三个预设联系人群组为例进行示意性说明，在其他可能的实施方式中，终端可以设置两个或三个以上预设联系人群组，本实施例并不对此构成限定。
需要说明的是，上述步骤903与904之间不存在严格的先后关系，即步骤903和步骤904可以同时执行，本实施并不对两者的执行时序进行限定。
通过上述步骤903和904，获取到目标免打扰模式，以及终端当前所处的免打扰模式后，终端进一步检测(当前的)免打扰模式是否属于目标免打扰模式。若属于，则执行下述步骤905至908，若不属于，则执行下述步骤909。
步骤905，若免打扰模式属于目标免打扰模式，则进行通知提醒。
若终端当前所处的免打扰模式属于当前联系人对应的目标免打扰模式，终端则通过预定方式进行通知提醒。
可选的，终端显示通知对应的通知处理界面，并进行声音提醒和/或振动提醒，其中，通知处理界面中包含联系人所属预设联系人群组的群组标识。
在一种可能的实施方式中，不同重要等级的联系人对应的声音提醒和振动提醒方式不同，在进行通知提醒时，终端根据当前联系人的重要等级，获取相应的提示音参数以及振动参数，进而根据获取到的参数进行通知提醒。可选的，本步骤包括如下步骤。
一、若免打扰模式属于目标免打扰模式，则获取重要等级对应的提示音参数和/或振动参数。
为了针对重要联系人达到更好的提醒效果，重要等级与提示音参数指示的提示音音量呈正相关关系，重要等级与振动参数指示的振动频率呈正相关关系。简单来讲，联系人的重要等级越高，进行通知提醒时的提示音音量越高，且振动频率越高。
示意性的，重要等级、提示音参数和振动参数三者之间的对应关系如表四所示。
表四
重要等级 提示音参数 振动参数
一级 30dB 2次/秒
二级 40dB 4次/秒
三级 50dB 6次/秒
比如，当接收到联系人“张三”的来电或短信时，终端根据表二和表四中记载的数据，获取到提示音参数为30dB，振动参数为2次/秒。
二、根据提示音参数进行声音提醒，和/或，根据振动参数进行振动提醒。
进一步的，根据获取到的提示音参数和振动参数，终端进行声音提醒以及振动提醒。
在其他可能的实施方式中，用户还可以针对不同的重要等级设置各自对应的提示音和/或振动方式，本实施例并不对此进行限定。
步骤906，当进行通知提醒时，接收对通知的操作。
进行通知提醒后，终端通过通知处理界面接收用户对通知的操作。可选的，当通知为来电通知时，终端通过通知处理界面接收接听或挂断操作；当通知为短信通信时，终端通过短信处理界面接收回复操作或删除操作。
步骤907，根据操作的操作类型，确定联系人的目标联系人群组。
由于联系人的重要程度可能会发生变化，因此，为了提高通知提醒的准确性，终端根据接收到操作的操作类型，更新联系人的目标联系人群组。
可选的，针对来电通知，终端定义接听操作和挂断操作，针对短信通知，终端定义回复操作和删除操作。当操作类型为接听或回复操作时，终端确定目标联系人群组对应的重要等级大于等于预设联系人群组对应的重要等级；当操作类型为挂断或删除操作时，终端确定目标联系人群组对应的重要等级小于等于预设联系人群组对应的重要等级。
为了提高确定出的目标联系人群组的准确性，在一种可能的实施方式中，终端统计各类操作的操作次数，并在操作次数达到阈值时，重新确定联系人所属的目标联系人群组。比如，该阈值可以为10次。
示意性的，针对各个联系人，终端统计用户接听来电、挂断来电、回复短信以及删除短信的次数。当用户接听来电或回复短信的次数达到阈值时，终端确定目标联系人群组的重要等级≥联系人当前所属的预设联系人群组的重要等级；当用户挂断来电或删除短信的次数达到阈值，终端确定目标联系人群组的重要等级≤联系人当前所属的预设联系人群组的重要等级。
步骤908，若联系人所属的预设联系人群组和目标联系人群组不同，则在联系人对应的联系人信息界面中显示群组调整提示。
当终端确定出的目标联系人群组与联系人当前所属的预设联系人群组不一致时，终端则显示相应的群组调整提示，提示用户将该联系人调整至目标联系人群组。
在一种可能的实施方式中，终端在联系人对应的联系人信息界面中显示群组调整提示，以便用户在联系人信息界面调整联系人所在的群组。
示意性的，如图10所示，在免打扰模式下，用户接听联系人“张三”来电的次数达到10次，当进入联系人“张三”对应的联系人信息界面51时，终端显示群组调整提示512，提示用户将联系人“张三”由VIP1(对应重要等级为一级)提升至VIP2(对应重要等级为二级)。
在其他可能的实施方式中，终端可以根据确定出的目标联系人群组对联系人进行自动调整，本实施例并不对此进行限定。
步骤909，若免打扰模式不属于目标免打扰模式，则不进行通知提醒。
本步骤的详细实施方式参见上述步骤303，本实施例在此不再赘述。
本实施例中，终端根据当前联系人对应的重要等级，获取相应的提示音参数和振动参数，从而根据获取到的参数进行声音提醒和振动提醒，进而提高了用户对重要联系人通知的感知能力，进一步降低了用户遗漏重要联系人通知的概率。
本实施例中，进行通知提醒后，终端根据用户对通知执行操作的操作类型，重新确定联系人的目标联系人群组，并在目标联系人群组与联系人当前所属群组不一致时，进行群组调整提示，方便用户实时调整联系人的重要等级，进而提高了后续通知提醒的准确性。
上述各个实施例中，通讯录中联系人的重要程度由用户自行判断，并由用户手动将重要联系人添加到预设联系人群组中。采用这种群组添加方式，生成的预设联系人群组的覆盖率较低(用户手动添加存在遗漏)，导致后续基于该预设联系人群组进行通知提醒的准确率也较低。为了进一步提高预设联系人群组的覆盖率，从而提高后续通知提醒的准确率，本申请提供了一种群组添加方法。
请参考图11，其示出了本申请一个示例性实施例提供的群组添加方法的流程图。该方法包括如下步骤。
步骤1101，获取联系人对应的联系人信息，联系人信息包括名称信息和/或历史通信信息。
对于通讯录中的各个联系人，终端获取各个联系人对应的联系人信息，该联系人信息包含联系人的名称信息以及与该联系人的历史通信信息。
由于联系人信息会随时间发生变更，因此，在一种可能的实施方式中，终端每隔预定时间间隔获取联系人信息。比如，终端每隔10天获取一次联系人信息。
可选的，名称信息包括联系人的备注和联系人名称中的至少一种；历史通信信息包括(历史)通话信息和(历史)短信发送内容。
比如，终端获取到的名称信息包括联系人名称“张三”以及备注“经理”，获取到的历史通信信息包括最近10天内的通话信息以及短信发送内容。
步骤1102，根据联系人信息识别联系人是否为重要联系人。
对于获取到的联系人信息，终端对其进行分析，从而判断联系人是否为重要联系人。
可选的，终端根据各个联系人的名称信息，确定用户与各个联系人之间的社交关系，进而识别出重要联系人，和/或，终端分析与各个联系人的历史通信信息，进而从通话频次、通话时长、通话时段、接听挂断比例、回拨次数和短信发送内容等维度识别出重要联系人。
步骤1103，若联系人为重要联系人，则显示群组添加提示，群组添加提示用于提示将联系人添加到预设联系人群组，预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。
对于识别出的重要联系人，终端采用预定方式显示群组添加提示，以便用于根据提示将重要联系人添加到预设联系人群组中。
在其他可能的实施方式中，对于识别出的重要联系人，终端自动将其添加到预设联系人群组中，并对添加的联系人进行标记或提示，本实施例并不对此进行限定。
用户根据群组添加提示向预设联系人群组中添加联系人后，终端在免打扰模式下即基于预设联系人群组，确定是否对接收到的通知进行提醒，详细的通知提醒过程参见上述各个实施例提供的通知提醒方法，本实施例在此不再赘述。
综上所述，本实施例中，终端通过获取联系人的联系人信息，并基于该联系人信息识别出重要联系人，从而显示群组添加提示，以便用户根据群组添加提示将重要联系人添加到预设联系人群组；后续过程中，终端基于该预设联系人群组，允许在免打扰模式下对该预设联系人群组的联系人进行通知提醒，从而避免用户遗漏重要联系人的通知；相较于用户自动判断联系人的重要程度，并向预设联系人群组中手动添加联系人，本实施中生成的预设联系人群组的覆盖率和准确率更高，进而提高了后续基于该群组进行通知提醒的准确性。
在一种可能的实施方式中，为了提高群组添加提示的准确性，终端综合名称信息和历史通信信息确定重要联系人。请参考图12，其示出了本申请另一个示例性实施例提供的群组添加方法的流程图。该方法包括如下步骤。
步骤1201，获取联系人对应的联系人信息，联系人信息包括名称信息和/或历史通信信息。
本步骤的详细实施方式参见上述步骤1101，本实施例在此不再赘述。
本实施例中，终端获取到各个联系人的名称信息和历史通信信息。
步骤1202，获取名称信息中包含的备注和/或联系人名称。
通常情况下，用户为联系人设置的名称信息能够反映出用户与联系人间的社交关系，而不同社交关系对应的重要程度不同，因此，终端可以根据联系人的名称信息确定联系人的重要程度。
示意性的，终端获取到的名称信息包括联系人名称“张三”以及备注“经理”。
步骤1203，若备注或联系人名称属于预设词库，则将联系人确定为重要联系人。
进一步的，终端检测备注或联系人名称是否属于预设词库，若属于，则确定该联系人为重要联系人，若不属于，则确定该联系人并非重要联系人。
在一种可能的实施方式中，该预设词库基于预设联系人群组中，已添加的重要联系人的名称信息生成。可选的，该预设词库中包含已添加的重要联系人的名称信息，以及该名称信息对应的关联名称信息。
比如，预设联系人群组中，已添加的重要联系人的名称信息包括经理和主席，终端即获取与经理和主席关联的词汇，比如上司、领导、代表，从而生成预设词库，该预设词库中即包含：经理、主席、上司、领导和代表。
在其他可能的实施方式中，终端还可以通过配置更新的方式从服务器处获取预设词库，本实施例并不对此进行限定。
示意性的，由于联系人“张三”的备注属于预设词库，因此，终端将张三确定重要联系人。
步骤1204，获取历史通信信息中包含的通话信息，通话信息包括通话频次、通话时长、通话时段、接听次数、挂断次数和回拨次数中的至少一种。
通常情况下，用户间的社交关系越密切，用户间的通话越频繁。因此，在一种可能的实施方式中，终端基于历史通信信息中的通话信息，识别出重要联系人。
在一个示意性的例子中，终端获取到联系人“张三”对应的通话信息(5天)如表五所示。
表五
通话时段 通话时长 接听 挂断 回拨
2017.12.6 10:16:20 12:56 √ × ×
2017.12.7 14:46:27 20:13 √ × ×
2017.12.7 19:02:30 7:16 √ × ×
2017.12.9 09:16:20 9:15 × × √
2017.12.9 14:18:12 0:00 × √ ×
2017.12.10 01:52:49 2:13 √ × ×
2017.12.10 05:46:18 5:09 √ × ×
可选的，终端获取到的通话信息还可以包括主叫次数、通话地点等信息，本实施例对此并不进行限定。
步骤1205，若通话信息符合预设条件，则确定联系人是否为重要联系人。
可选的，预设条件包括如下条件中的至少一条。
一、通话频次大于第一阈值。
通常情况下，联系人的重要程度越高，用户与其通话的频率和次数越高，因此，当与联系人的通话频次大于第一阈值时，终端确定该联系人为重要联系人，比如，该第一阈值为1次/天。
在一种可能的实施方式中，终端统计与各个联系人的通话频次，并计算得到通话频次平均值，进而基于通话频次平均值确定该第一阈值，其中，第一阈值≥通话频次平均值。
结合表五中的通话信息，终端计算得到与联系人张三的通话频次为7÷5＝1.4次/天＞1次/天，因此，终端将联系人张三确定为重要联系人。
二、通话时长大于第二阈值。
除了从通话频次判断联系人的重要程度外，终端还可以从通话时长判断联系人的重要程度。当与联系人的通话时长大于第二阈值时，终端确定该联系人为重要联系人，比如，该第二阈值为5分钟/次。
在一种可能的实施方式中，终端统计与各个联系人的通话时长，并计算得到通话时长平均值，进而基于通话时长平均值确定该第二阈值，其中，第二阈值≥通话时长平均值。
结合表五中的通话信息，终端计算得到与联系人张三的通话时长＞5分钟/次，因此，终端将联系人张三确定为重要联系人。
三、在预定时段内的通话次数大于第三阈值。
在一种可能的实施方式中，终端根据电量消耗时间分布，分析出用户的活跃时段和非活跃时段，并将非活跃时段确定为预定时段。比如，该预定时段为：0:00至07:00。
当检测到用户与联系人在预定时段内的通话次数大于第三阈值时，终端确定该联系人为重要联系人。比如，该第三阈值为1次。
结合表五中的通话信息，终端计算得到与联系人张三在0:00至07:00这一时段内的通话次数为5＞1次(第三阈值)，因此，终端将联系人张三确定为重要联系人。
四、接听次数与挂断次数的比例大于第四阈值。
在一种可能的实施方式中，终端统计各个联系人对应的接听挂断比例((接听次数+1)/(挂断次数+1))，并计算得到接听挂断比例平均值，进而基于接听挂断比例平均值确定该第四阈值，其中，第四阈值≥接听挂断比例平均值。
结合表五中的通话信息，终端计算得到联系人张三对应的接听挂断比例为5＞2.5(第四阈值)，因此，终端将联系人张三确定为重要联系人。
五、回拨次数大于第五阈值。
在一种可能的实施方式中，终端统计各个联系人对应的回拨次数(未接听电话后立即回拨)并计算得到回拨次数平均值，进而基于回拨次数平均值确定该第五阈值，其中，第五阈值≥回拨次数平均值。
结合表五中的通话信息，终端计算得到联系人张三对应的回拨次数为1＞0.8(第五阈值)，因此，终端将联系人张三确定为重要联系人。
本实施例仅以上述五种可能的实施方式为例进行说明，但并不对本申请构成限定。
步骤1206，获取历史通信信息中包含的短信发送内容。
用户向重要联系人发送短信时，发送的短信内容中通常会包含某些特定词汇，因此终端可以对短信发送内容进行分析，从而识别出重要联系人。
示意性的，终端获取到向张三发送的短信内容为：张经理您好，不知道您今天下午是否有空？
步骤1207，若短信发送内容中包含预设词汇，则确定联系人为重要联系人，预设词汇中包括敬语词汇和尊称词汇。
可选的，终端中存储有敬语词汇和尊称词汇(比如，您，请，拜托等等)，当检测到短信发送内容中包含敬语词汇或尊称词汇时，终端即确定该联系人为重要联系人。
可选的，该敬语词汇和尊称词汇基于与已添加重要联系人的短信发送内容得到。
步骤1208，若联系人为重要联系人，在联系人对应的联系人信息界面中显示群组添加提示。
当联系人为重要联系人时，终端即在该联系人对应的联系人信息界面中显示群组添加提示，提示用户将该联系人添加到预设联系人群组。
示意性的，如图13所示，终端识别“张三”为重要联系人，从而在联系人信息界面51中显示群组添加提示513。
步骤1209，若联系人为重要联系人，在接收到联系人来电，或，主呼联系人时，在通话界面中显示群组添加提示。
上述步骤1208中，用户需要在显示联系人信息界面才能知悉识别出的重要联系人。为了进一步提高群组添加效率，在一种可能的实施方式中，当接收到重要联系人来电(非免打扰模式下)，或，主动呼叫重要联系人时，终端即在通话界面中显示群组添加提示，提示用户将该重要联系人添加到预设联系人群组。
示意性的，如图14所示，终端识别“张三”为重要联系人，当主动呼叫张三时，终端在通话界面52中显示群组添加提示523，并显示快速添加控件524，方便用户快速将张三添加到VIP联系人群组中。
步骤1210，若联系人为重要联系人，在通讯录中联系人对应的位置显示群组添加提示。
在另一种可能的实施方式中，对于识别出的重要联系人(尚未添加到预设联系人群组中)，终端在通讯录中，重要联系人对应的位置处显示群组添加提示，当用户打开通讯录时，即可根据该群组添加提示完成群组添加。
示意性的，如图15所示，终端确定联系人“陈七”和“张三”为重要联系人，从而在显示通讯录53时，在“陈七”和“张三”各自对应的条目处显示群组添加提示531。
在其他可能的实施方式中，终端中设置有预设联系人群组编辑界面，当用户在该界面中选择向预设联系人群组中新增联系人时，该界面中即显示确定出的重要联系人，以便用户快速添加。比如，用户触发向预设联系人群组中添加联系人时，界面中显示下拉框，该下拉框中即优先显示确定出的重要联系人。
本实施例中，终端根据名称信息(包含联系人名称和备注名称)，和/或，历史通话信息，和/或，短信发送内容识别联系人是否为重要联系人，并对重要联系人进行群组添加提示，从而提高了群组添加提示的准确性，进而避免用户人为识别并手动添加重要联系人时造成的遗漏。
进一步的，对于识别出的重要联系人，终端在联系人信息界面、通话界面或通讯录中显示群组添加提示，方便用户快速将重要联系人添加到预设联系人群组中，提高了群组添加的效率。
请参考图16，其示出了本申请一个示例性实施例提供的通知提醒装置的结构框图。该通知提醒装置包括：识别模块1610、提醒模块1620和禁止提醒模块1630。
识别模块1610，用于免打扰模式下，当接收到通知时，识别所述通知对应的联系人，所述通知为 来电通知、短信通知或应用通知中的至少一种；
提醒模块1620，用于当所述联系人属于预设联系人群组时，采用预定方式进行通知提醒；
禁止提醒模块1630，用于当所述联系人不属于所述预设联系人群组时，不进行通知提醒；
其中，所述预设联系人群组是默认情况下，允许在所述免打扰模式下进行通知提醒的群组。
如图17所示，可选的，所述提醒模块1620，包括：
显示单元1621，用于显示所述通知对应的通知处理界面，所述通知处理界面中包含所述预设联系人群组的群组标识；
提醒单元1622，用于对所述通知进行声音提醒和/或振动提醒。
可选的，所述提醒单元1622，具体用于：
获取所述免打扰模式的模式类型；
若所述模式类型属于第一模式类型，则根据第一提示音参数进行声音提醒，和/或，根据第一振动参数进行振动提醒，所述第一模式类型包括睡眠模式和静音模式中的至少一种；
若所述模式类型属于第二模式类型，则根据第二提示音参数进行声音提醒，和/或，根据第二振动参数进行振动提醒，所述第二模式类型包括游戏模式和会议模式中的至少一种；
其中，所述第一提示音参数指示的提示音音量大于所述第二提示音参数指示的提示音音量；所述第一振动参数指示的振动频率大于所述第二振动参数指示的振动频率。
可选的，所述通知处理界面中设置有第一移除控件；
所述装置，还包括：
第一移除模块1640，用于当接收到对所述第一移除控件的点击操作时，将所述联系人从所述预设联系人分组中移除。
可选的，所述装置还包括：
第一显示模块1650，用于当目标联系人不属于所述预设联系人群组时，在所述目标联系人对应的联系人信息界面中显示添加控件；
添加模块1660，用于当接收到对所述添加控件的点击操作时，将所述目标联系人添加到所述预设联系人群组。
可选的，所述装置还包括：
第二显示模块1670，用于当目标联系人属于所述预设联系人群组时，在所述目标联系人对应的联系人信息界面中显示第二移除控件；
第二移除模块1680，用于当接收到对所述第二移除控件的点击操作时，将所述目标联系人从所述预设联系人分组中移除。
请参考图18，其示出了本申请一个示例性实施例提供的群组添加装置的结构框图。该群组添加装置包括：获取模块1810、识别模块1820和显示模块1830。
获取模块1810，用于获取联系人对应的联系人信息，所述联系人信息包括名称信息和/或历史通信信息；
识别模块1820，用于根据所述联系人信息识别所述联系人是否为重要联系人；
显示模块1830，用于若所述联系人为所述重要联系人，则显示群组添加提示，所述群组添加提示用于提示将所述联系人添加到预设联系人群组，所述预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。
如图19所示，可选的，所述联系人信息中包括所述名称信息；
所述识别模块1820，包括：
第一获取单元1821，用于获取所述名称信息中包含的备注和/或联系人名称；
第一确定单元1822，用于若所述备注或所述联系人名称属于预设备注词库，则将所述联系人确定为所述重要联系人。
可选的，所述联系人信息中包括所述历史通信信息；
所述识别模块1820，包括：
第二获取单元1823，用于获取所述历史通信信息中包含的通话信息，所述通话信息包括通话频次、通话时长、通话时段、接听次数、挂断次数和回拨次数中的至少一种；
第二确定单元1824，用于若所述通话信息符合预设条件，则确定所述联系人是否为所述重要联系人。
可选的，所述预设条件包括如下至少一种：
所述通话频次大于第一阈值；或，
所述通话时长大于第二阈值；或，
在预定时段内的通话次数大于第三阈值；或，
所述接听次数与所述挂断次数的比例大于第四阈值；或，
所述回拨次数大于第五阈值。
可选的，所述识别模块1820，还包括：
第三获取单元1825，用于获取所述历史通信信息中包含的短信发送内容；
第三确定单元1826，用于若所述短信发送内容中包含预设词汇，则确定所述联系人为所述重要联系人，所述预设词汇中包括敬语词汇和尊称词汇。
可选的，所述显示模块1830，包括：
第一显示单元1831，用于在所述联系人对应的联系人信息界面中显示所述群组添加提示；
或，
第二显示单元1832，用于在接收到所述联系人来电，或，主呼所述联系人时，在通话界面中显示所述群组添加提示；
或，
第三显示单元1833，用于在通讯录中所述联系人对应的位置显示所述群组添加提示。
请参考图20，其示出了本申请一个示例性实施例提供的通知提醒装置的结构框图。该通知提醒装置包括：识别模块2010、等级确定模块2020和提醒模块2030。
识别模块2010，用于免打扰模式下，当接收到通知时，识别所述通知对应的联系人，所述通知为来电通知、短信通知或应用通知中的至少一种；
等级确定模块2020，用于根据所述联系人所属的预设联系人群组，确定所述联系人的重要等级；
提醒模块2030，用于根据所述重要等级确定是否进行通知提醒；
其中，同一预设联系人群组中，各个联系人的所述重要等级相同，且不同预设联系人群组对应的所述重要等级不同。
如图21所示，可选的，所述提醒模块2030，包括：
获取单元2031，用于获取终端当前所处的所述免打扰模式；
确定单元2032，用于确定所述重要等级对应的目标免打扰模式；
提醒单元2033，用于若所述免打扰模式属于所述目标免打扰模式，则进行通知提醒；
禁止提醒单元2034，用于若所述免打扰模式不属于所述目标免打扰模式，则不进行通知提醒；
其中，不同重要等级对应的所述目标免打扰模式的数量不同，且所述重要等级与所述目标免打扰模式的数量呈正相关关系。
可选的，所述确定单元2032，用于：
当所述重要等级为一级时，将静音模式和游戏模式确定所述目标免打扰模式；
当所述重要等级为二级时，将所述静音模式、所述游戏模式和会议模式确定为所述目标免打扰模式；
当所述重要等级为三级时，将所述静音模式、所述游戏模式、所述会议模式和睡眠模式确定为所述目标免打扰模式。
可选的，所述提醒单元2033，用于：
若所述免打扰模式属于所述目标免打扰模式，则获取所述重要等级对应的提示音参数和/或振动参数；
根据所述提示音参数进行声音提醒，和/或，根据所述振动参数进行振动提醒；
其中，所述重要等级与所述提示音参数指示的提示音音量呈正相关关系，所述重要等级与所述振动参数指示的振动频率呈正相关关系。
可选的，所述装置还包括：
接收模块2040，用于当进行通知提醒时，接收对所述通知的操作；
群组确定模块2050，用于根据所述操作的操作类型，确定所述联系人的目标联系人群组；
提示模块2060，用于若所述联系人所属的所述预设联系人群组和所述目标联系人群组不同，则在所述联系人对应的联系人信息界面中显示群组调整提示；
其中，当所述操作类型为接听或回复操作时，所述目标联系人群组对应的所述重要等级大于等于所述预设联系人群组对应的所述重要等级；当所述操作类型为挂断或删除操作时，所述目标联系人群组对应的所述重要等级小于等于所述预设联系人群组对应的所述重要等级。
本申请实施例还提供了一种计算机可读介质，该计算机可读介质存储有至少一条指令，所述至少一条指令由所述处理器加载并执行以实现如上各个实施例所述的通知提醒方法，或，群组添加方法。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品存储有至少一条指令，所述至少一条指令由所述处理器加载并执行以实现如上各个实施例所述的通知提醒方法，或，群组添加方法。

Claims (40)

  1. 一种通知提醒方法，其特征在于，所述方法包括：
    免打扰模式下，当接收到通知时，识别所述通知对应的联系人，所述通知为来电通知、短信通知或应用通知中的至少一种；
    若所述联系人属于预设联系人群组，则采用预定方式进行通知提醒；
    若所述联系人不属于所述预设联系人群组，则不进行通知提醒；
    其中，所述预设联系人群组是默认情况下，允许在所述免打扰模式下进行通知提醒的群组。
  2. 根据权利要求1所述的方法，其特征在于，所述采用预定方式进行通知提醒，包括：
    显示所述通知对应的通知处理界面，所述通知处理界面中包含所述预设联系人群组的群组标识；
    对所述通知进行声音提醒和/或振动提醒。
  3. 根据权利要求2所述的方法，其特征在于，所述对所述通知进行声音提醒和/或振动提醒，包括：
    获取所述免打扰模式的模式类型；
    若所述模式类型属于第一模式类型，则根据第一提示音参数进行声音提醒，和/或，根据第一振动参数进行振动提醒，所述第一模式类型包括睡眠模式和静音模式中的至少一种；
    若所述模式类型属于第二模式类型，则根据第二提示音参数进行声音提醒，和/或，根据第二振动参数进行振动提醒，所述第二模式类型包括游戏模式和会议模式中的至少一种；
    其中，所述第一提示音参数指示的提示音音量大于所述第二提示音参数指示的提示音音量；所述第一振动参数指示的振动频率大于所述第二振动参数指示的振动频率。
  4. 根据权利要求2所述的方法，其特征在于，所述通知处理界面中设置有第一移除控件；
    所述显示所述通知对应的通知处理界面之后，所述方法还包括：
    当接收到对所述第一移除控件的点击操作时，将所述联系人从所述预设联系人分组中移除。
  5. 根据权利要求1至3任一所述的方法，其特征在于，所述识别所述通知对应的联系人之前，所述方法还包括：
    当目标联系人不属于所述预设联系人群组时，在所述目标联系人对应的联系人信息界面中显示添加控件；
    当接收到对所述添加控件的点击操作时，将所述目标联系人添加到所述预设联系人群组。
  6. 根据权利要求1至3任一所述的方法，其特征在于，所述识别所述通知对应的联系人之前，所述方法还包括：
    当目标联系人属于所述预设联系人群组时，在所述目标联系人对应的联系人信息界面中显示第二移除控件；
    当接收到对所述第二移除控件的点击操作时，将所述目标联系人从所述预设联系人分组中移除。
  7. 一种通知提醒装置，其特征在于，所述装置包括：
    识别模块，用于免打扰模式下，当接收到通知时，识别所述通知对应的联系人，所述通知为来电通知、短信通知或应用通知中的至少一种；
    提醒模块，用于当所述联系人属于预设联系人群组时，采用预定方式进行通知提醒；
    禁止提醒模块，用于当所述联系人不属于所述预设联系人群组时，不进行通知提醒；
    其中，所述预设联系人群组是默认情况下，允许在所述免打扰模式下进行通知提醒的群组。
  8. 根据权利要求7所述的装置，其特征在于，所述提醒模块，包括：
    显示单元，用于显示所述通知对应的通知处理界面，所述通知处理界面中包含所述预设联系人群组的群组标识；
    提醒单元，用于对所述通知进行声音提醒和/或振动提醒。
  9. 根据权利要求8所述的装置，其特征在于，所述提醒单元，具体用于：
    获取所述免打扰模式的模式类型；
    若所述模式类型属于第一模式类型，则根据第一提示音参数进行声音提醒，和/或，根据第一振动参数进行振动提醒，所述第一模式类型包括睡眠模式和静音模式中的至少一种；
    若所述模式类型属于第二模式类型，则根据第二提示音参数进行声音提醒，和/或，根据第二振动参数进行振动提醒，所述第二模式类型包括游戏模式和会议模式中的至少一种；
    其中，所述第一提示音参数指示的提示音音量大于所述第二提示音参数指示的提示音音量；所述第一振动参数指示的振动频率大于所述第二振动参数指示的振动频率。
  10. 根据权利要求8所述的装置，其特征在于，所述通知处理界面中设置有第一移除控件；
    所述装置，还包括：
    第一移除模块，用于当接收到对所述第一移除控件的点击操作时，将所述联系人从所述预设联系人 分组中移除。
  11. 根据权利要求7至9任一所述的装置，其特征在于，所述装置还包括：
    第一显示模块，用于当目标联系人不属于所述预设联系人群组时，在所述目标联系人对应的联系人信息界面中显示添加控件；
    添加模块，用于当接收到对所述添加控件的点击操作时，将所述目标联系人添加到所述预设联系人群组。
  12. 根据权利要求7至9任一所述的装置，其特征在于，所述装置还包括：
    第二显示模块，用于当目标联系人属于所述预设联系人群组时，在所述目标联系人对应的联系人信息界面中显示第二移除控件；
    第二移除模块，用于当接收到对所述第二移除控件的点击操作时，将所述目标联系人从所述预设联系人分组中移除。
  13. 一种终端，其特征在于，所述终端包括处理器和存储器，所述存储器中存储有至少一条指令，所述指令由所述处理器加载并执行以实现如权利要求1至6任一所述的通知提醒方法。
  14. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有至少一条指令，所述指令由处理器加载并执行以实现如权利要求1至6任一所述的通知提醒方法。
  15. 一种群组添加方法，其特征在于，所述方法包括：
    获取联系人对应的联系人信息，所述联系人信息包括名称信息和/或历史通信信息；
    根据所述联系人信息识别所述联系人是否为重要联系人；
    若所述联系人为所述重要联系人，则显示群组添加提示，所述群组添加提示用于提示将所述联系人添加到预设联系人群组，所述预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。
  16. 根据权利要求15所述的方法，其特征在于，所述联系人信息中包括所述名称信息；
    所述根据所述联系人信息识别所述联系人是否为重要联系人，包括：
    获取所述名称信息中包含的备注和/或联系人名称；
    若所述备注或所述联系人名称属于预设备注词库，则将所述联系人确定为所述重要联系人。
  17. 根据权利要求15所述的方法，其特征在于，所述联系人信息中包括所述历史通信信息；
    所述根据所述联系人信息识别所述联系人是否为重要联系人，包括：
    获取所述历史通信信息中包含的通话信息，所述通话信息包括通话频次、通话时长、通话时段、接听次数、挂断次数和回拨次数中的至少一种；
    若所述通话信息符合预设条件，则确定所述联系人是否为所述重要联系人。
  18. 根据权利要求17所述的方法，其特征在于，所述预设条件包括如下至少一种：
    所述通话频次大于第一阈值；或，
    所述通话时长大于第二阈值；或，
    在预定时段内的通话次数大于第三阈值；或，
    所述接听次数与所述挂断次数的比例大于第四阈值；或，
    所述回拨次数大于第五阈值。
  19. 根据权利要求17所述的方法，其特征在于，所述根据所述联系人信息识别所述联系人是否为重要联系人，还包括：
    获取所述历史通信信息中包含的短信发送内容；
    若所述短信发送内容中包含预设词汇，则确定所述联系人为所述重要联系人，所述预设词汇中包括敬语词汇和尊称词汇。
  20. 根据权利要求15至19任一所述的方法，其特征在于，所述显示群组添加提示，包括：
    在所述联系人对应的联系人信息界面中显示所述群组添加提示；或，
    在接收到所述联系人来电，或，主呼所述联系人时，在通话界面中显示所述群组添加提示；或，在通讯录中所述联系人对应的位置显示所述群组添加提示。
  21. 一种群组添加装置，其特征在于，所述装置包括：
    获取模块，用于获取联系人对应的联系人信息，所述联系人信息包括名称信息和/或历史通信信息；
    识别模块，用于根据所述联系人信息识别所述联系人是否为重要联系人；
    显示模块，用于若所述联系人为所述重要联系人，则显示群组添加提示，所述群组添加提示用于提示将所述联系人添加到预设联系人群组，所述预设联系人群组是默认情况下，允许在免打扰模式下进行通知提醒的群组。
  22. 根据权利要求21所述的装置，其特征在于，所述联系人信息中包括所述名称信息；
    所述识别模块，包括：
    第一获取单元，用于获取所述名称信息中包含的备注和/或联系人名称；
    第一确定单元，用于若所述备注或所述联系人名称属于预设备注词库，则将所述联系人确定为所述重要联系人。
  23. 根据权利要求21所述的装置，其特征在于，所述联系人信息中包括所述历史通信信息；
    所述识别模块，包括：
    第二获取单元，用于获取所述历史通信信息中包含的通话信息，所述通话信息包括通话频次、通话时长、通话时段、接听次数、挂断次数和回拨次数中的至少一种；
    第二确定单元，用于若所述通话信息符合预设条件，则确定所述联系人是否为所述重要联系人。
  24. 根据权利要求23所述的装置，其特征在于，所述预设条件包括如下至少一种：
    所述通话频次大于第一阈值；或，
    所述通话时长大于第二阈值；或，
    在预定时段内的通话次数大于第三阈值；或，
    所述接听次数与所述挂断次数的比例大于第四阈值；或，
    所述回拨次数大于第五阈值。
  25. 根据权利要求23所述的装置，其特征在于，所述识别模块，还包括：
    第三获取单元，用于获取所述历史通信信息中包含的短信发送内容；
    第三确定单元，用于若所述短信发送内容中包含预设词汇，则确定所述联系人为所述重要联系人，所述预设词汇中包括敬语词汇和尊称词汇。
  26. 根据权利要求21至25任一所述的装置，其特征在于，所述显示模块，包括：
    第一显示单元，用于在所述联系人对应的联系人信息界面中显示所述群组添加提示；或，
    第二显示单元，用于在接收到所述联系人来电，或，主呼所述联系人时，在通话界面中显示所述群组添加提示；或，
    第三显示单元，用于在通讯录中所述联系人对应的位置显示所述群组添加提示。
  27. 一种终端，其特征在于，所述终端包括处理器和存储器，所述存储器中存储有至少一条指令，所述指令由所述处理器加载并执行以实现如权利要求15至20任一所述的群组添加方法。
  28. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有至少一条指令，所述指令由处理器加载并执行以实现如权利要求15至20任一所述的群组添加方法。
  29. 一种通知提醒方法，其特征在于，所述方法包括：
    免打扰模式下，当接收到通知时，识别所述通知对应的联系人，所述通知为来电通知、短信通知或应用通知中的至少一种；
    根据所述联系人所属的预设联系人群组，确定所述联系人的重要等级；
    根据所述重要等级确定是否进行通知提醒；
    其中，同一预设联系人群组中，各个联系人的所述重要等级相同，且不同预设联系人群组对应的所述重要等级不同。
  30. 根据权利要求29所述的方法，其特征在于，所述根据所述重要等级确定是否进行通知提醒，包括：
    获取终端当前所处的所述免打扰模式；
    确定所述重要等级对应的目标免打扰模式；
    若所述免打扰模式属于所述目标免打扰模式，则进行通知提醒；
    若所述免打扰模式不属于所述目标免打扰模式，则不进行通知提醒；
    其中，不同重要等级对应的所述目标免打扰模式的数量不同，且所述重要等级与所述目标免打扰模式的数量呈正相关关系。
  31. 根据权利要求30所述的方法，其特征在于，所述确定所述重要等级对应的目标免打扰模式，包括：
    当所述重要等级为一级时，将静音模式和游戏模式确定所述目标免打扰模式；
    当所述重要等级为二级时，将所述静音模式、所述游戏模式和会议模式确定为所述目标免打扰模式；
    当所述重要等级为三级时，将所述静音模式、所述游戏模式、所述会议模式和睡眠模式确定为所述目标免打扰模式。
  32. 根据权利要求30或31所述的方法，其特征在于，所述若所述免打扰模式属于所述目标免打扰模式，则进行通知提醒，包括：
    若所述免打扰模式属于所述目标免打扰模式，则获取所述重要等级对应的提示音参数和/或振动参数；
    根据所述提示音参数进行声音提醒，和/或，根据所述振动参数进行振动提醒；
    其中，所述重要等级与所述提示音参数指示的提示音音量呈正相关关系，所述重要等级与所述振动参数指示的振动频率呈正相关关系。
  33. 根据权利要求29至31任一所述的方法，其特征在于，所述根据所述重要等级确定是否进行通知提醒之后，所述方法还包括：
    当进行通知提醒时，接收对所述通知的操作；
    根据所述操作的操作类型，确定所述联系人的目标联系人群组；
    若所述联系人所属的所述预设联系人群组和所述目标联系人群组不同，则在所述联系人对应的联系人信息界面中显示群组调整提示；
    其中，当所述操作类型为接听或回复操作时，所述目标联系人群组对应的所述重要等级大于等于所述预设联系人群组对应的所述重要等级；当所述操作类型为挂断或删除操作时，所述目标联系人群组对应的所述重要等级小于等于所述预设联系人群组对应的所述重要等级。
  34. 一种通知提醒装置，其特征在于，所述装置包括：
    识别模块，用于免打扰模式下，当接收到通知时，识别所述通知对应的联系人，所述通知为来电通知、短信通知或应用通知中的至少一种；
    等级确定模块，用于根据所述联系人所属的预设联系人群组，确定所述联系人的重要等级；
    提醒模块，用于根据所述重要等级确定是否进行通知提醒；
    其中，同一预设联系人群组中，各个联系人的所述重要等级相同，且不同预设联系人群组对应的所述重要等级不同。
  35. 根据权利要求34所述的装置，其特征在于，所述提醒模块，包括：
    获取单元，用于获取终端当前所处的所述免打扰模式；
    确定单元，用于确定所述重要等级对应的目标免打扰模式；
    提醒单元，用于若所述免打扰模式属于所述目标免打扰模式，则进行通知提醒；
    禁止提醒单元，用于若所述免打扰模式不属于所述目标免打扰模式，则不进行通知提醒；
    其中，不同重要等级对应的所述目标免打扰模式的数量不同，且所述重要等级与所述目标免打扰模式的数量呈正相关关系。
  36. 根据权利要求35所述的装置，其特征在于，所述确定单元，用于：
    当所述重要等级为一级时，将静音模式和游戏模式确定所述目标免打扰模式；
    当所述重要等级为二级时，将所述静音模式、所述游戏模式和会议模式确定为所述目标免打扰模式；
    当所述重要等级为三级时，将所述静音模式、所述游戏模式、所述会议模式和睡眠模式确定为所述目标免打扰模式。
  37. 根据权利要求35或36所述的装置，其特征在于，所述提醒单元，用于：
    若所述免打扰模式属于所述目标免打扰模式，则获取所述重要等级对应的提示音参数和/或振动参数；
    根据所述提示音参数进行声音提醒，和/或，根据所述振动参数进行振动提醒；
    其中，所述重要等级与所述提示音参数指示的提示音音量呈正相关关系，所述重要等级与所述振动参数指示的振动频率呈正相关关系。
  38. 根据权利要求34至36任一所述的装置，其特征在于，所述装置还包括：
    接收模块，用于当进行通知提醒时，接收对所述通知的操作；
    群组确定模块，用于根据所述操作的操作类型，确定所述联系人的目标联系人群组；
    提示模块，用于若所述联系人所属的所述预设联系人群组和所述目标联系人群组不同，则在所述联系人对应的联系人信息界面中显示群组调整提示；
    其中，当所述操作类型为接听或回复操作时，所述目标联系人群组对应的所述重要等级大于等于所述预设联系人群组对应的所述重要等级；当所述操作类型为挂断或删除操作时，所述目标联系人群组对应的所述重要等级小于等于所述预设联系人群组对应的所述重要等级。
  39. 一种终端，其特征在于，所述终端包括处理器和存储器，所述存储器中存储有至少一条指令，所述指令由所述处理器加载并执行以实现如权利要求29至33任一所述的通知提醒方法。
  40. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有至少一条指令，所述指令由处理器加载并执行以实现如权利要求29至33任一所述的通知提醒方法。
PCT/CN2018/123577 2017-12-25 2018-12-25 通知提醒方法、群组添加方法、装置、终端及存储介质 WO2019129003A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020207018008A KR102322542B1 (ko) 2017-12-25 2018-12-25 통지 리마인더 방법, 단말기 및 저장 매체
JP2020533712A JP7043604B2 (ja) 2017-12-25 2018-12-25 通知リマインド方法、グループ追加方法、装置、端末、および記憶媒体
EP18894393.0A EP3723352B1 (en) 2017-12-25 2018-12-25 Notification prompt method and apparatus, terminal and storage medium
AU2018393399A AU2018393399B2 (en) 2017-12-25 2018-12-25 Notification prompt method, group addition method and apparatus, terminal and storage medium
US16/885,859 US11272051B2 (en) 2017-12-25 2020-05-28 Method for notification reminder, terminal, and storage medium
US17/590,591 US20220159119A1 (en) 2017-12-25 2022-02-01 Method for notification reminder, terminal, and storage medium

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN201711418894.6A CN107864297B (zh) 2017-12-25 2017-12-25 群组添加方法、装置、终端及存储介质
CN201711418894.6 2017-12-25
CN201711419886.3A CN108156303B (zh) 2017-12-25 2017-12-25 通知提醒方法、装置、终端及存储介质
CN201711421116.2 2017-12-25
CN201711421116.2A CN108055404B (zh) 2017-12-25 2017-12-25 通知提醒方法、装置、终端及存储介质
CN201711419886.3 2017-12-25

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/885,859 Continuation US11272051B2 (en) 2017-12-25 2020-05-28 Method for notification reminder, terminal, and storage medium

Publications (1)

Publication Number Publication Date
WO2019129003A1 true WO2019129003A1 (zh) 2019-07-04

Family

ID=67066605

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123577 WO2019129003A1 (zh) 2017-12-25 2018-12-25 通知提醒方法、群组添加方法、装置、终端及存储介质

Country Status (6)

Country Link
US (2) US11272051B2 (zh)
EP (1) EP3723352B1 (zh)
JP (1) JP7043604B2 (zh)
KR (1) KR102322542B1 (zh)
AU (1) AU2018393399B2 (zh)
WO (1) WO2019129003A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115022273A (zh) * 2021-12-14 2022-09-06 北京字跳网络技术有限公司 消息免打扰设置方法、装置、系统及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112328132A (zh) * 2020-11-03 2021-02-05 珠海格力电器股份有限公司 一种通知信息的处理方法以及装置
CN114567695B (zh) * 2020-11-27 2023-08-22 成都鼎桥通信技术有限公司 消息提醒方法、装置、设备、存储介质及计算机程序产品
CN113419873A (zh) * 2021-06-21 2021-09-21 远光软件股份有限公司 聊天消息的提醒方法、装置、存储介质及终端设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859491A (zh) * 2006-01-26 2006-11-08 华为技术有限公司 一种免打扰方法
CN102957781A (zh) * 2012-11-16 2013-03-06 广东欧珀移动通信有限公司 一种移动终端的免打扰控制方法
CN103458120A (zh) * 2013-08-27 2013-12-18 小米科技有限责任公司 事件处理方法、装置和移动终端
CN106911556A (zh) * 2015-12-23 2017-06-30 北京奇虎科技有限公司 一种消息提醒管理方法及终端
CN107864297A (zh) * 2017-12-25 2018-03-30 广东欧珀移动通信有限公司 群组添加方法、装置、终端及存储介质
CN108055404A (zh) * 2017-12-25 2018-05-18 广东欧珀移动通信有限公司 通知提醒方法、装置、终端及存储介质

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004312105A (ja) 2003-04-02 2004-11-04 Nec Corp 携帯電話端末の着信制御方式
JP2004072713A (ja) 2003-04-16 2004-03-04 Helios:Kk 通信端末装置、通信システム、着信情報表示方法及びプログラム
US7117445B2 (en) 2003-06-30 2006-10-03 Danger, Inc. Multi-mode communication apparatus and interface for contacting a user
US20060240877A1 (en) * 2005-04-22 2006-10-26 Viktor Filiba System and method for providing in-coming call alerts
CN101202780A (zh) 2006-12-14 2008-06-18 英业达股份有限公司 情景模式的管理系统及方法
CN101552835A (zh) 2009-05-13 2009-10-07 北京中星微电子有限公司 一种进行手机信息提示的方法及手机
CN101951426A (zh) 2010-09-10 2011-01-19 宇龙计算机通信科技(深圳)有限公司 联系人分组方法及终端
US8559932B2 (en) * 2010-12-20 2013-10-15 Ford Global Technologies, Llc Selective alert processing
CN102082882A (zh) 2011-01-20 2011-06-01 宇龙计算机通信科技(深圳)有限公司 呼叫管理方法、装置和终端
CN102420906A (zh) 2011-12-01 2012-04-18 华为终端有限公司 提示方法和用户终端
CN103167451A (zh) 2011-12-19 2013-06-19 中兴通讯股份有限公司 一种实现免打扰的方法及移动终端
US8346881B1 (en) * 2012-05-18 2013-01-01 Google Inc. Prioritization of incoming communications
US20140057619A1 (en) * 2012-08-24 2014-02-27 Tencent Technology (Shenzhen) Company Limited System and method for adjusting operation modes of a mobile device
CN103067568A (zh) 2012-12-07 2013-04-24 东莞宇龙通信科技有限公司 一种未处理事件的提醒方法及装置
US20140177812A1 (en) * 2012-12-21 2014-06-26 Richard Barrett Urgent and emergency notification and communication system
JP2014175682A (ja) 2013-03-06 2014-09-22 Zenrin Datacom Co Ltd 携帯通信端末および携帯通信端末の動作制御方法
JP2015015665A (ja) 2013-07-08 2015-01-22 シャープ株式会社 電子機器
CN104683591A (zh) 2015-03-10 2015-06-03 苏州天鸣信息科技有限公司 基于移动终端的消息免打扰方法及其移动终端
CN105100350B (zh) 2015-05-22 2019-02-15 努比亚技术有限公司 一种根据联系频率管理联系人的方法及装置
JP2017059862A (ja) * 2015-09-14 2017-03-23 株式会社 ミックウェア 通信装置、着信出力方法、及びプログラム
US9930168B2 (en) 2015-12-14 2018-03-27 International Business Machines Corporation System and method for context aware proper name spelling
CN106303079A (zh) 2016-09-18 2017-01-04 珠海格力电器股份有限公司 一种通讯提示方法及通讯设备
CN106713674B (zh) 2017-04-05 2019-11-22 广东国利信息网络有限公司 来电处理方法和来电处理装置
CN107197096A (zh) 2017-05-26 2017-09-22 维沃移动通信有限公司 一种来电铃声的调整方法、装置和移动终端
CN106998394A (zh) 2017-06-01 2017-08-01 深圳市伊特利网络科技有限公司 特定联系人提示的设置方法及系统
CN107222629B (zh) 2017-06-20 2020-07-07 Oppo广东移动通信有限公司 来电处理方法及相关产品
CN107241481A (zh) 2017-06-30 2017-10-10 广东欧珀移动通信有限公司 通讯录管理方法、装置、存储介质及电子设备
CN108055397A (zh) 2017-12-06 2018-05-18 广东欧珀移动通信有限公司 实现免打扰功能的方法、电子设备及计算机可读存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859491A (zh) * 2006-01-26 2006-11-08 华为技术有限公司 一种免打扰方法
CN102957781A (zh) * 2012-11-16 2013-03-06 广东欧珀移动通信有限公司 一种移动终端的免打扰控制方法
CN103458120A (zh) * 2013-08-27 2013-12-18 小米科技有限责任公司 事件处理方法、装置和移动终端
CN106911556A (zh) * 2015-12-23 2017-06-30 北京奇虎科技有限公司 一种消息提醒管理方法及终端
CN107864297A (zh) * 2017-12-25 2018-03-30 广东欧珀移动通信有限公司 群组添加方法、装置、终端及存储介质
CN108055404A (zh) * 2017-12-25 2018-05-18 广东欧珀移动通信有限公司 通知提醒方法、装置、终端及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3723352A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115022273A (zh) * 2021-12-14 2022-09-06 北京字跳网络技术有限公司 消息免打扰设置方法、装置、系统及存储介质

Also Published As

Publication number Publication date
EP3723352A1 (en) 2020-10-14
AU2018393399A1 (en) 2020-07-09
AU2018393399B2 (en) 2021-07-01
KR20200090220A (ko) 2020-07-28
EP3723352B1 (en) 2023-01-25
JP2021508198A (ja) 2021-02-25
JP7043604B2 (ja) 2022-03-29
KR102322542B1 (ko) 2021-11-05
EP3723352A4 (en) 2020-11-25
US20200296207A1 (en) 2020-09-17
US11272051B2 (en) 2022-03-08
US20220159119A1 (en) 2022-05-19

Similar Documents

Publication Publication Date Title
CN107864297B (zh) 群组添加方法、装置、终端及存储介质
WO2019129003A1 (zh) 通知提醒方法、群组添加方法、装置、终端及存储介质
CN108156303B (zh) 通知提醒方法、装置、终端及存储介质
CN108055404B (zh) 通知提醒方法、装置、终端及存储介质
AU2015280093B2 (en) Location-based audio messaging
US9456082B2 (en) Determining probable topics of conversation between users of two communication devices
CN107491315A (zh) 消息提示方法、装置及终端
US10798536B2 (en) Method, system, and device for processing system call in voice call
CN109743246B (zh) 消息加急提醒方法、装置和电子设备
US20190250789A1 (en) Method and device for controlling display interface
US9906471B1 (en) System, device, and method for managing composition of electronic messages using temporary suspensions
JP2015534297A (ja) スマートディバイスの着信信号音の出力を制御するユーザインタフェース制御方法
US9571441B2 (en) Peer-based device set actions
CN107426401B (zh) 静音提醒方法、装置及终端
CN106535147B (zh) 通信信号处理方法及装置
CN106604244B (zh) 一种对通知消息进行提示的方法和装置
WO2019047127A1 (zh) 呼叫处理方法及终端
TWI622285B (zh) Multimedia communication processing method and computer program product thereof
TW202101424A (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: 18894393

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020533712

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20207018008

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018393399

Country of ref document: AU

Date of ref document: 20181225

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018894393

Country of ref document: EP

Effective date: 20200709