WO2019153687A1

WO2019153687A1 - Call record management method and terminal

Info

Publication number: WO2019153687A1
Application number: PCT/CN2018/100177
Authority: WO
Inventors: 易婕
Original assignee: 华为技术有限公司
Priority date: 2018-02-08
Filing date: 2018-08-13
Publication date: 2019-08-15
Also published as: CN110138954B; CN110138954A

Abstract

The embodiments of the present invention provide a call record management method and a terminal, relating to the field of communications and capable of improving the efficiency of management of call records. Said method comprises: a terminal detecting a first call event, and generating a first call record comprising a first phone number and a first label corresponding to the first phone number; the terminal detecting a second call event, and generating a second call record comprising a second phone number and a second label corresponding to the second phone number; the terminal detecting a third call event, and generating a third call record comprising a third phone number and the first label; if the call duration of the first call event is less than a first preset value, the terminal automatically deleting the first call record after a first time elapses; if the call duration of the second call event is less than a second preset value, the terminal automatically deleting the second call record after a second time elapses; and if the call duration of the third call event is greater than a third preset value, and the third call event is an outgoing call event, the terminal keeping the third call record.

Description

Call record management method and terminal

This application claims priority to Chinese Patent Application No. 201101129210.9, entitled "Management Method and Terminal for Call Recording", filed on February 8, 2018, the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present invention relates to the field of communications, and in particular, to a method and a terminal for managing call records.

Background technique

With the rapid development of communication technology, mobile terminals and other communication terminals are also convenient for users' lives, and users are often plagued by harassing calls such as real estate agents, fraud, sales, insurance, or ringing. The call records of these harassing calls are usually Together with the call history of the normal phone, it is displayed in chronological order in the recent call list of the call application.

Although there are many terminals that can identify the specific types of strange calls by online identification, such as scam calls, sales calls, etc., the call records of these harassing calls are mixed in the user's normal call records, which will undoubtedly manage these call records for the user. The inconvenience is caused, and the management efficiency of the call record is lowered.

Summary of the invention

Embodiments of the present invention provide a method and a terminal for managing call records, which can automatically clear unnecessary call records for a user, and improve management efficiency of call records.

In order to achieve the above object, embodiments of the present invention adopt the following technical solutions:

In a first aspect, an embodiment of the present invention provides a method for managing a call record, including: after detecting a first call event, the terminal generates a first call record and saves, where the first call record includes the first number and the first a first label corresponding to the first number; after detecting the second call event, the terminal generates a second call record and saves the second call record, where the second call record includes a second number and a second label corresponding to the second number; After the third call event, the third call record is generated and saved, and the third call record includes the third number and the first label (ie, the label of the third number is the same as the label of the first number); then, when the terminal determines When the duration of the call of the call event is less than the first preset value, the terminal may automatically delete the first call record after the first time according to the first clear setting preset for the first label; when the terminal determines the second call event When the duration of the call is less than the second preset value, the terminal may automatically delete the second call after the second time according to the second clear setting preset for the second label. When the terminal determines that the call duration of the third call event is greater than a third preset value (the third preset value is greater than or equal to the first preset value), and the third call event is an outgoing call event, the terminal may reserve the third call record. .

In this way, for a call record containing different tags, the terminal can automatically clear the corresponding call record for different time periods according to the call setting (Clean Setting); and for different call records containing the same tag, the terminal can according to the call duration. And the information related to the call event such as the call type determines which call records are reserved, which call records are deleted, and intelligently helps the user to automatically clear unnecessary call records, improve the management efficiency of the call record, and save the storage space of the terminal.

In a possible design method, the first call event is an incoming call event, an outgoing call event, or a missed event; and the second call event is an incoming call event, an outgoing call event, or a missed event.

Exemplarily, the above label may be: real estate agent phone, fraud phone, sales phone, insurance bank phone, courier phone or meal delivery phone.

Exemplarily, the above tag may be stored in the CACHED_NUMBER_LABEL field or the MARK_CONTENT field of calls.db.

In a second aspect, an embodiment of the present invention provides a method for managing a call record, including: detecting, by a terminal, a first call event, generating a first call record, and saving, where the first call record includes the first number and the first number Corresponding first label; the terminal detects the second call event, generates a second call record and saves, the second call record includes a second number and a second label corresponding to the second number; when the terminal determines that the first label is pre- When the first garbage label is set, the terminal automatically deletes the first call record after the first time passes; when the terminal determines that the second label is the preset second garbage label, the terminal automatically deletes the second call after the second time passes. Recording; wherein the first garbage label has a higher priority than the second garbage label, and the first time is less than the second time.

That is to say, the terminal can divide the priority of the garbage label based on the degree of interference of different garbage labels on the user life, and can set a shorter cleaning period for the garbage label with higher priority, thereby minimizing the interference to the user life, and A lower-level junk tag can set a relatively long clean-up cycle, automatically clearing the call history of the different junk tags for the user.

In a possible design method, the method further includes: the terminal detects the third call event, generates a third call record and saves, the third call record includes a third number, and the label of the third number is empty; During the preset time period, the monitoring terminal generates a new call record with the third number; if no new call record is generated, the terminal automatically deletes the third call record.

In a possible design method, the terminal automatically deletes the first call record, which specifically includes: when the call duration of the first call event is less than a preset value, the terminal automatically deletes the first call record, or when the first call event is When the incoming call event occurs, the terminal automatically deletes the first call record, or when the first number is the preset number, the terminal automatically deletes the first call record, or when the number of calls between the terminal and the first number is greater than the threshold, the terminal automatically The first call record is deleted, or when the number of call records stored in the terminal reaches a preset upper limit, the terminal automatically deletes the first call record.

That is to say, the terminal can intelligently determine the call record that the user does not need according to the specific call behavior of the user (such as the duration of the call, the number of calls, the call number or the type of the call, etc.), and automatically delete the unnecessary call records for the user. Improve the management efficiency of call records in the terminal.

In a possible design method, the preset garbage label includes at least one of a real estate agent phone, a fraud phone, a sales phone, an insurance money phone, a courier phone, and a meal phone; wherein the priority of the fraud phone Above the priority of the sales call, the promotion phone has a higher priority than the priority of the insurance phone, the priority of the insurance phone is higher than the priority of the agent phone, and the priority of the agent phone is high The priority of the courier and meal delivery calls.

In a third aspect, an embodiment of the present application provides a terminal, including: a detecting unit, configured to: detect a first call event, a second call event, and a third call event; and a generating unit, configured to: generate a first call record, The first call record includes a first number and a first label corresponding to the first number; generating a second call record, the second call record includes a second number and a second label corresponding to the second number; and generating a third a call record, the third call record includes a third number and a first label corresponding to the third number; the management unit is configured to: when the terminal determines that the call duration of the first call event is less than the first preset value, The first clear setting of the preset label automatically deletes the first call record after the first time passes; when the terminal determines that the call duration of the second call event is less than the second preset value, the preset according to the second label The second clearing setting automatically deletes the second call record after the second time; when the terminal determines that the call duration of the third call event is greater than the third preset value, and the third pass Event is an outgoing call event, to retain the third call record, the third predetermined value is greater than or equal the first preset value.

In one possible design method, the tag is: real estate agent phone, fraud phone, sales phone, insurance phone, courier phone or room phone.

In one possible design approach, the tag is stored in the CACHED_NUMBER_LABEL field or the MARK_CONTENT field of calls.db in the Android operating system.

In a fourth aspect, an embodiment of the present application provides a terminal, including: a touch screen, wherein the touch screen includes a touch-sensitive surface and a display; one or more processors; a memory for storing a plurality of applications, and one or more a computer program; wherein the one or more computer programs include instructions that, when executed by the terminal, cause the terminal to perform the following steps:

Displaying a first GUI in the touch screen; the first GUI includes a first call record and a second call record; wherein the first call record includes a first number and a first tag corresponding to the first number, and the second call record The second number includes a second label corresponding to the second number, and the label of the first number is a garbage label; the first GUI further includes a first control, where the first control is used to hide or display the call record including the garbage label The terminal detects a first input event for the first control in the first GUI; in response to the first input event, displays a second GUI in the touch screen, the second GUI includes the first control and the second call record, but does not include The first call record, avoiding the call record containing the junk tag from interfering with the normal operation of the user in the call list; the terminal detecting the second input event for the first control in the second GUI; displaying the touch screen in response to the second input event The first GUI.

In a possible design method, the first GUI further includes a second control, where the second control is used to edit the call record displayed in the first GUI; wherein, after displaying the first GUI in the touch screen, the method further includes: Detecting a third input event for the second control in the first GUI; displaying a third GUI in the touch screen in response to the third input event, the third GUI including a first call record that is topped and automatically selected, It is convenient for users to quickly clear all call records including garbage labels, and improve the efficiency of manual management of call records.

In a possible design method, after displaying the third GUI in the touch screen, the method further includes: displaying the first GUI in the touch screen if the input operation of the third GUI by the user is not received within the preset time.

In one possible design method, in the first GUI, the call record of the junk tag is displayed topped.

In a fifth aspect, an embodiment of the present application provides a terminal, including: a touch screen, wherein the touch screen includes a touch-sensitive surface and a display; one or more processors; a memory for storing a plurality of applications, and one or more a computer program; wherein the one or more computer programs include instructions that, when executed by the terminal, cause the terminal to perform the following steps:

Displaying a first GUI in the touch screen; the first GUI includes a first call record and a second call record; wherein the first call record includes a first number and a first tag corresponding to the first number, and the second call record The second number includes a second label corresponding to the second number, and the label of the first number is a garbage label; the first GUI further includes a first control and a second control, where the first control is used to hide the garbage label a call record, the second control is used to display all the call records including the garbage tag; then, after detecting the first input event for the first control in the first GUI, the terminal may display the second GUI in the touch screen, and second The second call record is included in the GUI, but does not include the first call record; and further, if the terminal detects the second input event for the second control in the second GUI, the first call record may be redisplayed in the touch screen. And the first GUI of the second call record.

In a sixth aspect, an embodiment of the present application provides a terminal, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the terminal is running The processor executes the computer-executed instructions stored in the memory to cause the terminal to perform the management method of any of the above call records.

In a seventh aspect, the embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores an instruction, when the instruction is run on any one of the terminals, causing the terminal to perform any of the above-mentioned calls. The management method of the record.

In an eighth aspect, an embodiment of the present application provides a computer program product, including an instruction, when the terminal runs on any of the foregoing terminals, causing the terminal to perform the management method of any one of the foregoing call records.

In the embodiment of the present application, the names of the components in the terminal are not limited to the device itself, and in actual implementation, the components may appear under other names. As long as the functions of the various components are similar to the embodiments of the present application, they are within the scope of the claims and their equivalents.

In addition, the technical effects brought by the design method of any one of the second aspect to the eighth aspect can be referred to the technical effects brought by different design methods in the above first aspect, and details are not described herein again.

DRAWINGS

FIG. 1 is a schematic structural diagram 1 of a terminal according to an embodiment of the present disclosure;

FIG. 2 is a schematic structural diagram of a programming module in a terminal according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a call scenario according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram 1 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram 2 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram 3 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram 4 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram 5 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram 6 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 10 is a schematic diagram 7 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 11 is a schematic diagram 8 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 12 is a schematic diagram 9 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 13 is a schematic diagram of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 14 is a schematic diagram 11 of an application scenario for managing call records according to an embodiment of the present disclosure;

FIG. 15 is a schematic flowchart 1 of a method for managing call records according to an embodiment of the present disclosure;

FIG. 16 is a second schematic flowchart of a method for managing call records according to an embodiment of the present disclosure;

FIG. 17 is a schematic structural diagram 2 of a terminal according to an embodiment of the present disclosure;

FIG. 18 is a schematic structural diagram 3 of a terminal according to an embodiment of the present application.

Detailed ways

In the following, the terms "first" and "second" are used for descriptive purposes only, and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, features defining "first" and "second" may include one or more of the features either explicitly or implicitly. In the description of the embodiments of the present application, "multiple" means two or more unless otherwise stated.

A call record management method provided by an embodiment of the present application can be applied to a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an augmented reality (AR), a virtual reality (VR) device, a notebook computer, The embodiment of the present application does not impose any limitation on any terminal having a call function, such as an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA).

As shown in FIG. 1 , the terminal in the embodiment of the present application may be the mobile phone 100. The embodiment will be specifically described below by taking the mobile phone 100 as an example. It should be understood that the illustrated mobile phone 100 is only one example of the above terminal, and the mobile phone 100 may have more or fewer components than those shown in FIG. 1, and two or more components may be combined, or Can have different component configurations.

Referring to FIG. 1, the handset 100 can communicate with other

electronic devices

102 and 104, other than the handset 100, and the server 106. The handset 100 can include a bus 110, a processor 120, a memory 130, a user input module 150, a display module 160, a communication interface 170, and other similar and/or suitable components.

Bus 110 may be circuitry that interconnects the above elements and communicates (e.g., control messages) between the elements.

The processor 120 can receive commands from the other components (such as the memory 130, the user input module 150, the display module 160, the communication interface 170, the communication configuration control module 170, etc.) through the bus 110, can interpret the received commands, and can Interpret commands to perform calculations or data processing.

Memory 130 may store commands or data received from processor 120 or other components (e.g., user input module 150, display module 160, communication interface 170, etc.) or commands or data generated by processor 120 or other components.

The memory 130 may include programming modules such as a kernel 131, a middleware 132, an application programming interface (API) 133, an application 134, and the like. Each of the above programming modules may be implemented in software, firmware, hardware, or a combination of two or more thereof, as described in detail in the related description of FIG.

The kernel 131 may control or manage system resources (e.g., bus 110, processor 120, memory 130, etc.) for performing operations or functions implemented by other programming modules (e.g., middleware 132, API 133, and applications 134). Additionally, the kernel 131 can provide an interface that can access and control or manage the various elements of the handset 100 by using the middleware 132, the API 133, or the application 134.

The middleware 132 can be used to operate between the API 133 or the application 134 and the kernel 131 in communication with the kernel 131 with the API 133 or the application 134 and exchange data therewith. For example, the middleware 132 can be configured as an intermediary for communication between the API 133 or the application 134 and the kernel 131. Additionally, for example, regarding a work request received from one or more applications 134 and/or middleware 132, a priority may be assigned to at least one of the one or more applications 134 (where the priority may be Load balancing of work requests is performed using methods of system resources (e.g., bus 110, processor 120, memory 130, etc.) of handset 100.

The API 133 is an interface by which the application 134 can control functions provided by the kernel 131 or the middleware 132, and can include, for example, at least one interface or function for file control, window control, image processing, character control, and the like.

Applications 134 may include, for example, a home page application, a dialer application, a short message service/multimedia message service application, an instant messaging application, a browser application, a camera application, an alarm clock application, a contact application, a voice dialing application, an email (e-mail). Apps, calendar apps, media player apps, photo album apps, clock apps, and any other suitable and/or similar applications.

The user input module 150 can receive commands or data input from a user via input-output means (eg, sensors, keyboards, touch screens, etc.) and can transmit the received commands or data to the processor 120 or memory 130 via the bus 110. Display module 160 can display video, images, data, and the like to the user.

The display module 160 can display various information (eg, multimedia data, text data) received from the above components.

Communication interface 170 can control a short range communication connection with another electronic device 102. When the mobile phone 100 is paired with another electronic device, the communication interface 170 may stop a scanning operation of waiting for receiving a signal from a neighboring electronic device or stopping a broadcast operation of a broadcast signal. For example, in response to the handset 100 being paired with another electronic device 102, the communication interface 170 stops waiting for a scan operation to receive a signal from a neighboring electronic device or a broadcast operation to stop the broadcast signal. When the handset 100 is paired with another electronic device, the communication interface 170 can control the period of the scanning or broadcast operation.

In accordance with various embodiments disclosed herein, handset 100 can communicate with another electronic device using communication interface 170. For example, communication interface 170 can communicate with another electronic device 104, server 106, and the like. Communication interface 170 can communicate with other electronic devices 104, servers 106, etc., either directly or through network 162. For example, communication interface 170 can operate to connect handset 100 to network 162.

2 shows a block diagram of a configuration of a programming module disclosed in accordance with an embodiment of the present application.

Referring to FIG. 2, programming module 310 can be included (or stored) in handset 100 (e.g., memory 130) shown in FIG. At least a portion of programming module 310 can be implemented as software, firmware, hardware, or a combination of two or more of them. Programming module 310 can be implemented as hardware (eg, hardware 201) and can include an OS that controls resources associated with an electronic device (eg, cell phone 100) and/or various applications (eg, applications 370) that are executed in the OS. For example, the OS can be Android, iOS, Windows, Symbian, Tizen, Bada, and the like.

Referring to FIG. 2, programming module 310 can include kernel 320, middleware 330, API 360, and/or application 370.

Kernel 320 (e.g., kernel 131) may include system resource manager 321 and/or device driver 323. The system resource manager 321 can include a process manager (not shown), a memory manager (not shown), and a file system manager (not shown). The system resource manager 321 can perform control, allocation, recovery, and the like of system resources. The device driver 323 may include, for example, a display driver (not shown), a camera driver (not shown), a Bluetooth driver (not shown), a shared memory driver (not shown), a USB driver (not shown) And a keypad driver (not shown), a Wi-Fi driver (not shown), and/or an audio driver (not shown). Moreover, in accordance with embodiments disclosed herein, device driver 323 can include an interprocess communication (IPC) driver (not shown).

The middleware 330 may include a plurality of modules that are implemented in advance to provide functions shared by the application 370. In addition, middleware 330 can provide functionality to application 370 via API 360 to enable application 370 to efficiently utilize limited system resources within the electronic device. For example, as shown in FIG. 2, the middleware 330 (eg, the middleware 132) may include at least one of the following: a runtime library 335, an application manager 341, a window manager 342, a multimedia manager 343, a resource manager 344, and a power supply. Manager 345, database manager 346, package manager 347, connection manager 348, notification manager 349, location manager 350, graphics manager 351, security manager 352, and any other suitable and/or similar manager.

The runtime library 335 can include library modules, such as used by a compiler, to add new functionality by using a programming language during execution of the application 370. According to an embodiment disclosed herein, the runtime 335 can perform functions related to input and output, management of memory, arithmetic functions, and the like.

The application manager 341 can manage, for example, the lifecycle of at least one application 370. Window manager 342 can manage the graphical user interface (GUI) resources used on the screen. The multimedia manager 343 can detect a format for reproducing various media files, and can encode or decode the media file by using a codec suitable for the relevant format. The resource manager 344 can manage resources of at least one application 370, such as source code, memory, storage space, and the like.

The power manager 345 can operate with a basic input output system (BIOS), can manage a battery or a power source, and can provide power information for operation and the like. Database manager 346 can manage the database in a manner that enables generation, searching, and/or changing of a database to be used by at least one application 370. The package manager 347 can manage the installation and/or update of applications distributed in the form of package files.

Connection manager 348 can manage wireless connections such as Wi-Fi and BT. The notification manager 349 can display or report events such as arrival messages, appointments, proximity alerts, etc. to the user in a manner that does not bother the user. The location manager 350 can manage location information of the electronic device. The graphics manager 351 can manage graphics effects to be provided to the user and/or UIs related to the graphics effects. Security manager 352 can provide various security functions for system security, user authentication, and the like. According to an embodiment of the present disclosure, when an electronic device (eg, mobile phone 100) has a phone function, the middleware 330 may further include a phone manager (not shown) for managing voice phone call functions of the electronic device and/or Video call function.

The middleware 330 can generate and use a new middleware module through various functional combinations of the internal component modules described above. The middleware 330 can provide modules that are specialized according to the type of OS to provide differentiated functionality. The middleware 330 can also dynamically delete some of the existing components, or can add new components. Accordingly, the middleware 330 may omit some of the elements described in the various embodiments disclosed herein, and may include other elements, or some of these elements may be replaced with elements that perform similar functions and have different names.

API 360 (eg API 133) is a collection of API programming functions and can have different configurations depending on the OS. In the case of, for example, Android or iOS, one API set can be provided to each platform. In the case of, for example, Tizen, two or more API sets can be provided to each platform.

Application 370 (eg, application 134 in FIG. 1) may include, for example, a preloaded application and/or a third party application. The application 370 (eg, the application 134) may include, for example, a home page application 371, a memo application 372, a short messaging service (SMS)/multimedia messaging service (MMS) application 373, an instant messaging (IM) application 374, browsing. Application 375, camera application 376, alarm application 377, contact application 378, voice dialing application 379, email application 380, calendar application 381, media player application 382, album application 383, clock application 384, and any other suitable and/or Or a similar application.

Illustratively, the user can make a call to the contact using the voice dialing application 379, or can receive a call from a strange number or a stored contact via the voice dialing application 379.

In some embodiments of the present application, when the mobile phone 100 receives the call made by the strange number, as shown in FIG. 3, the mobile phone 100 may also obtain the label of the strange number from the server in the network, the label is used to indicate the The type to which the strange number belongs, for example, the tag may specifically be a fraud phone, an insurance bank phone, an intermediary phone, a courier phone, or a meal phone. The server may be a provider that provides a phone number yellow page service for the mobile phone 100, and the mobile phone 100 may call the interface of the server to display various yellow pages on the touch screen.

In other embodiments of the present application, the mobile phone 100 may further acquire a label of the strange number from the server when generating a call record with the strange number, or when the mobile phone 100 detects that the user views the details of the call record, The server obtains the label of the strange number, and the embodiment of the present application does not impose any limitation on this.

After the server identifies the tag of the strange number (for example, the scam phone 301), the tag can be sent to the mobile phone 100 through the wireless network, and the mobile phone 100 displays the caller ID interface, the call list interface, and the call details interface of the strange number. This tag helps users identify the type of tag for unfamiliar calls.

In some embodiments of the present application, tags obtained from a server on the network side or tags manually tagged by the user may be stored in the call log of the mobile phone 100. Illustratively, if the mobile phone 100 is an Android operating system, a tag corresponding to the phone number in the call log may be stored in the CACHED_NUMBER_LABEL field of the database of calls.db.

In other embodiments of the present application, in order to store the label in more detail, a plurality of fields may be added to record information related to the label: for example, MARK_TYPE, MARK_CONTENT, MARK_COUNT, IS_CLOUD_MARK related to the telephone number in the call record may be added. Fields, these fields can also be stored in the database calls.db.

The MARK_TYPE field indicates the type of the label, for example, the label type may be user-defined or may be default; the MARK_CONTENT field indicates specific information of the label, such as a fraud phone, an intermediary phone, a courier phone, or a meal delivery phone, and the MARK_COUNT field indicates The number of times the telephone number is marked, for example, a telephone number can display information such as "the number is marked as a fraudulent telephone by 108 people" in the call record; the IS_CLOUD_MARK field indicates whether the label of the telephone number is marked by the server on the network side.

Taking the Android operating system as an example, the API 360 of the Android operating system is generally provided with a contact provider API, and the voice dialing application 379 can read the basic information of each call record by calling the interface to obtain the call. The label of the phone number in the record that is being called with this machine. The basic information of these call records may be stored in a database (for example, calls.db) in a form or in other forms, which is not limited in this embodiment of the present application.

As shown in FIG. 4, each call record in the call list interface 401 corresponds to a call record table 402. The basic information of the call record is recorded in different fields of the call record table 402, for example, the ID of the call record (the value of the ID may increase in accordance with the number of call records), the phone number of the call, this time The incoming and outgoing call type of the call (1 is incoming call, 2 is outgoing call), the start time of the call, and the call duration of the call.

In the embodiment of the present application, as shown in FIG. 4, the call record table 402 is further provided with a field 403 for storing the specific type of the label (which may be referred to as a label field in the embodiment of the present application, for example, the above-mentioned CACHED_NUMBER_LABEL field), The tag of the strange number obtained from the above server is stored, for example, 01 is a fraudulent phone, 02 is an intermediary phone, 03 is a courier phone, and the like. In this way, the voice dialing application 379 can obtain the target tag 404 of the strange number recognized by the server by reading the tag field 403, and then display the target tag 404 in the call record of the call list interface 401.

In some other embodiments of the present application, for the phone number 100 where the mobile phone 100 has stored the contact name, the mobile phone 100 may also obtain the label of the phone number from the server, or the mobile phone 100 may also set the user for the phone number. The label is uploaded to the server, and the embodiment of the present application does not impose any limitation on this.

In some other embodiments of the present application, the mobile phone 100 may also store an offline tag identification library for identifying a tag to which the phone number belongs. For example, the offline tag identification library may be downloaded from the server by the mobile phone 100. The mobile phone 100 can also periodically obtain the updated phone number and the correspondence between the tags from the server to update the offline tag identification library.

Then, when receiving the call made by the strange number, the mobile phone 100 may also identify the tag of the strange number from the offline tag identification library, and write the identified tag into the tag field 403 of the call record table 402. The embodiment does not impose any restrictions on this.

In other embodiments of the present application, when the mobile phone 100 (for example, the voice dialing application 379 in the mobile phone 100 described above) detects that the tag recorded in the tag field 403 in a certain call record is a junk tag (for example, a fraudulent phone), the terminal may be in the The call list interface 401 automatically deletes the call record, and automatically helps the user to clear unnecessary call records, thereby improving the management efficiency of the call record and further saving the storage space of the terminal.

The garbage label may specifically be a real estate intermediary telephone, a fraud telephone, a sales call, an insurance financial call, a courier call or a meal delivery call. The garbage label may be obtained by the terminal from the server, or may be preset in the terminal when the terminal is shipped from the factory, or may be manually set by the user during the process of using the terminal, or may be based on the history of the user during the running of the terminal. The data and the like are automatically generated, and the embodiment of the present application does not impose any limitation on this.

Exemplarily, for different types of garbage tags, the terminal can set different cleaning cycles to automatically clear the call records including the garbage tags. For example, for a garbage tag with a high degree of interference such as a fraudulent phone, the terminal can automatically delete the call record immediately after receiving such a call; for a junk tag such as a sales call and an insurance financial call, the degree of interference is lower than that of the fraudulent call. The terminal can automatically delete the call record on the day of receiving such a call; for the garbage tag, such as express delivery and real estate agent, the terminal can automatically delete the call record after receiving the call for 7 days.

In addition, if the label of a certain telephone number is not recorded in the server, when the terminal requests the server to obtain the label of the telephone number in the call record, the result returned by the server to the terminal may be empty. At this time, the call record of the telephone number is The label field is also empty, indicating that the phone number is a strange number. Then, the terminal can detect whether the user generates a new call record with the strange number within a preset time period (for example, 15 days) of receiving the strange number call, if there is no new call record, or the new call record number is less than the threshold. , indicating that the user has a low call requirement with the strange number, so the terminal can automatically delete the call record of the strange number after the expiration of 15 days.

Exemplarily, each time the terminal generates a new call record, the terminal can identify whether the tag of the call record is a junk tag by reading a tag field in the call record. As shown in (a) of FIG. 5, the call list displayed by the terminal includes a call record 1 - a call record 5, which are displayed in accordance with the time sequence in which the call record is generated.

The call record 1 is an incoming call event just received by the terminal, and the tag included in the call record 1 is a sales call 501, and the tag 501 can be displayed below the phone number. Then, when the terminal detects that the tag included in the call record 1 is the sales call 501, the call duration in the call record 1 can be further checked. If the duration of the call is less than a first preset value (for example, 10 s) set for the tag of the sales call, the terminal may start a timer 1 of one day according to the first cleanup setting stored in advance for the tag 501.

Similarly, the call record 4 is an incoming call event received by the terminal at 8:46 on the day, and the tag included in the call record 4 is the express call 502. Then, when the terminal detects that the tag included in the call record 4 is a courier call After 502, the call duration in the call record 4 can be further checked. If the duration of the call is less than a second preset value (eg, 20 s) set for the label of the courier phone, the terminal may start a timer 2 of 7 days according to the second cleanup setting stored in advance for the tag 502.

Similarly, the call record 5 is an outgoing call event that the terminal calls out at 8:09 on the day, and the tag included in the call record 5 is also the express call 502. Then, when the terminal detects that the tag included in the call record 5 is the express call 502, You can also check the duration of the call in call log 5. If the duration of the call is greater than a third preset value set for the label of the courier phone (for example, 1 minute, the third preset value is greater than or equal to the first preset value), it indicates that the call is intentionally called by the user. Therefore, the terminal does not need to delete the call record 5.

Then, when the timer 1 times out after 1 day, the terminal can automatically delete the call record 1 including the label 501 of the sales call. At this time, as shown in (b) of FIG. 5, when the user opens the interface of the call list. When the call record 1 is no longer displayed in the call list, the remaining call records 2 - call record 5 can also be retained in the call interface. Of course, the basic information such as the call time displayed in the call record 2 - call record 5 can also be adjusted accordingly. Still as shown in (b) of FIG. 5, the talk time in the call record 3 is changed from 17:19 shown in (a) of FIG. 5 to 1 day as shown in (b) of FIG. before.

Correspondingly, when the timer 2 expires after 7 days, as shown in (c) of FIG. 5, the terminal automatically deletes the call including the label 502 of the courier phone on the basis of (b) in FIG. Record 4. The call record 5 includes the same tag as the call record 4, but since the call duration of the call record 5 is greater than the third preset value, and the call event is an outgoing call event that the user actively calls, the terminal deletes the call record. The call record 5 can be reserved at 4 o'clock. At this time, as shown in (c) of FIG. 5, when the user opens the interface of the call list, the call record 1 and the call record 4 are no longer displayed in the call list, and the remaining call records can be retained in the call interface. , call log 3 and call log 5.

Of course, during the operation of the timer 1 or the timer 2, the terminal may also generate a new one or more call records. If the newly generated call record includes a garbage tag, the terminal may continue to start a new timer. These call records are deleted periodically, and the embodiment of the present application does not impose any restrictions on this.

In some other embodiments of the present application, the terminal may also periodically detect the label field of each call record in the call list. For example, as shown in FIG. 6, the terminal can read the label field of each call record in all current call records every night at 22:00, and when detecting that the label in the call record 1 is the garbage label of the sales call 501, the terminal It can be determined according to the talk time in the call record 1 whether or not the call record 1 is deleted at this time. If the call time in the call record 1 has exceeded the preset cleaning period (for example, 1 day), the terminal can automatically delete the call record 1. Otherwise, the terminal can retain the call record 1 until 22:00 the next day to determine whether to delete. The call record is 1.

In some other embodiments of the present application, the terminal may also detect a label field of each call record in the call list every time the user opens the call list or edit the call list, and then the call record including the garbage label is It is automatically deleted from the call list.

In still other embodiments of the present application, the terminal may also automatically clear the call record based on the number of call records including the junk tag. For example, whenever the terminal detects a call record including the garbage label of the meal delivery phone, the preset counter in the terminal may be triggered to increase by one. When the counter is accumulated to 10, that is, when the call record including the garbage label of the meal list reaches 10, the terminal can be triggered to automatically delete the 10 call records.

In other embodiments of the present application, the terminal may also automatically clear the call record according to the label in the call record and the duration of the call. For example, when the terminal detects the call record 2 including the garbage tag of the harassing phone, the terminal may further check the call duration of the call record 2. If the call duration is greater than the first preset time (for example, 5 minutes), the user and the user The caller in the call record 2 has a call request, so the terminal does not need to delete the call record 2. Correspondingly, if the duration of the call in the call record 2 is less than the second preset time (for example, 10 seconds), it indicates that the caller in the call record 2 has almost no call demand, so the terminal can automatically delete the call record 2. The first preset time and the second preset time may be the same or different, and the embodiment of the present application does not impose any limitation on this.

It should be noted that, in addition to automatically clearing the call record for the user according to the label included in the call record, the terminal can automatically clear the call record for the user according to the content recorded in other fields in the call record. Any restrictions.

For example, the terminal may also record the number of call events that the user rejects the garbage tag, for example, after the user accumulates the call event of the label of the promotion call 5 times, the terminal may automatically delete the corresponding five call events. The call record enables the terminal to intelligently determine the call record that the user does not need according to the specific call behavior (such as the number of rejections, the duration of the call, the number of calls, etc.), and automatically delete the unnecessary call records and improve the terminal. The management efficiency of the internal call record.

Exemplarily, when the terminal detects that the call number in the call record is a terminal preset or a specified phone number set by the user (for example, “10086”), the terminal may be triggered to automatically delete the call record; for example, when the terminal detects the call. When the contact name in the record is a terminal preset or a specified contact set by the user (for example, "Mike"), the terminal may be triggered to automatically delete the call record; for example, when the terminal detects that the call duration in the call record is less than the preset When the value (for example, 5 seconds), the terminal can be triggered to automatically delete the call record.

Illustratively, as shown in (a) of FIG. 7, the user can manually set which call records are automatically deleted in the setting interface 701 of the voice dialing application 379.

In (a) of FIG. 7, the control 702 is configured to set an automatic deletion of the call record of the designated contact. For example, after the terminal detects a touch operation for the control 702, in response to the touch operation, the terminal may display a plurality of contacts stored in the address book for selection by the user in the setting interface 701. After detecting that the user selects one or more contacts in the multiple contacts, the terminal may save the identifiers of the contacts, and when the subsequent detection of a call record includes the identifier of the contact selected by the user, the terminal may automatically Delete the call history.

In (a) of FIG. 7, the control 703 is for setting the automatic deletion of the call record of the specified telephone number. For example, after the terminal detects a touch operation for the control 703, in response to the touch operation, the terminal may display a plurality of phone numbers stored in the address book for selection by the user in the setting interface 701. After detecting that the user selects one or more phone numbers in the plurality of phone numbers, the terminal may save the phone numbers, and when subsequently detecting that a certain call record includes the phone number selected by the user, the terminal may automatically delete the call record. .

In (a) of FIG. 7, the control 704 is configured to automatically delete the call record of the specified call duration. For example, after the terminal detects a touch operation for the control 704, in response to the touch operation, the terminal may display a candidate interval of a plurality of call durations in the setting interface 701, for example, 0-20s, 1 minute-5 minutes, and 10 minutes. Multiple candidate intervals above. After detecting that the user selects an interval in the candidate interval of the multiple call durations, the terminal may save the specific value of the interval, and when the subsequent detection of the call duration in a certain call record falls within the selected interval of the user, the terminal may The call history is automatically deleted.

In (a) of FIG. 7, the control 700 is configured to automatically delete a call record containing the specified tag. For example, when the terminal detects a touch operation for the control 700, the terminal may display a setting interface as shown in (b) of FIG. 7 in response to the touch operation. Specifically, in the setting interface shown in (b) of FIG. 7, the user can further set the automatic cleaning of the call record including which label or labels, for example, the user can set the automatic cleaning including the fraudulent call by clicking the control 710. A call record of a tag, the user can set the call record of the tag including the advertisement and the promotion phone automatically by clicking the control 720, and the user can set the call record of the label including the courier and the meal delivery phone automatically by clicking the control 730.

Exemplarily, when the user clicks the control 710 to enable the cleaning function of the call record of the tag of the fraudulent phone, the user can further set the cleaning time for clearing the call record in the setting interface shown in (b) of FIG. 7 . Cleanup strategy such as 710a and cleanup cycle 710b. For example, after the user sets the cleanup time 710a to "22:00 every day", the terminal can query the call record carrying the label of the fraudulent telephone in the current call list at 22:00 every day, and automatically delete the call record. For another example, after the user sets the cleanup time 710b to “clean up immediately”, whenever the terminal generates a new call record, if the tag included in the call record is a fraudulent call, the terminal can automatically delete the call record immediately.

In addition, as shown in (a) of FIG. 7, a control 705 of "recover deleted records" may also be provided in the setting interface 701 of the voice dialing application 379. Then, after the terminal detects the touch operation for the control 705, in response to the touch operation, the terminal may display an interface as shown in FIG. 8, where the call record automatically deleted by the terminal in the last 7 days is displayed, that is, the terminal may Call records that are automatically deleted in the last 7 days are cached in memory. Then, the user can select one or more of the deleted call records to be restored for recovery. Subsequently, when the terminal detects that the user clicks the "Resume" button 706, the terminal can redisplay the deleted call record selected by the user in the call list. If the terminal does not detect the user's operation to resume the call record within 7 days of deleting a certain call record, the terminal may permanently delete the call record from its memory. The embodiment of the present application does not impose any limitation on the time when the deleted call record is cached in the terminal memory.

Of course, as shown in (a) of FIG. 9, the user can also modify the label that has been set for the contact or phone number in the contact details interface 801, or add a user customization in the contact details interface 801. s Mark. For example, the user adds a custom tag to the call number "13032920112" as "Customer" 802. Then, the user can also select the "Add Cleanup Policy" option 740 in the interface shown in (b) of FIG. 7, and the user can also "in the interface shown in (b) of FIG. 9 as " The customer "802" is a custom label setting corresponding to the cleaning policy of the call record. For example, the cleaning policy is "If the call record is not deleted within 10 days, the call record is automatically deleted."

In addition, the terminal generally has a limit on the number of stored call records, for example, allowing the terminal to save up to 200 call records. Then, when the call record generated by the terminal is greater than 200, the call record including the garbage tag in the call record can be automatically deleted, so that the retained call record has higher use value to the user.

In the foregoing embodiment, the terminal automatically deletes the call record including the garbage label as an example. It can be understood that the terminal can automatically clear the call record for the user, and can automatically hide the basic information according to the label in the call record. The call history in the call list.

For example, when the label in the label field in the call record generated by the terminal is a garbage label, the terminal may mark the call record (for example, add a preset identifier to a certain field in the call record), and subsequently, when the user is detected. When the call list is opened, the terminal can not display the marked call record. The call list displayed at this time does not include the call record containing the junk tag, which can prevent the call record containing the junk tag from interfering with the user in finding or managing the call list. The normal call history, which improves the management efficiency of the call record.

Alternatively, the terminal may further determine whether to hide the call record according to the information related to the call event, such as the duration of the call or the type of the call in the call record. For example, if the tag in the call record is a junk tag and the call type is an incoming call event, and the call duration is less than a preset value (for example, 10 seconds), the call is likely to be an invalid call that interferes with the user's life. Then, the terminal can automatically hide the call record when detecting that the user opens the call list; correspondingly, if the label in the call record is a garbage label, but the call type is an outgoing call event, and the call duration is greater than a preset value (for example, 3) Minutes), this means that the call is intentionally executed by the user, so the terminal does not need to hide the call record when displaying the call list.

Of course, the user can also cancel the hidden function of one or more call records through specific controls or gestures. Since the terminal does not actually delete the fields in the call record when the terminal hides the call records, the terminal responds to the user input. The previously hidden call history can be restored in the call list.

In the foregoing embodiment, the terminal automatically deletes or hides the call record including the garbage tag as an example. It can be understood that, in the management method of the call record provided by the present application, the user can manually manage the call record in the call list. .

Exemplarily, as shown in FIG. 10, an edit button 902 is disposed in the call list 901. When it is detected that the user clicks the edit button 902 to manually manage the call record, the terminal may display the call record 903 including the junk tag on the call list. In 901, it is convenient for the user to quickly locate and clean these unimportant call records in the call list 901.

Optionally, as shown in FIG. 10, the terminal not only displays the call record 903 including the junk tag in the call list 901, but also automatically selects the call record 903, so that the user only needs to click the clear button 904. The key clears all call records 903 including the garbage tag, improving the efficiency of manually managing the call record.

Alternatively, as shown in (a) of FIG. 11, the terminal can automatically hide the call record 903 including the junk tag when the call list 901 is displayed, so that the call record 903 including the junk tag is mixed in the call list 901 to interfere with the user pair. The management of normal call records further improves the interaction between the terminal and the user. When it is detected that the user clicks the button 1001 that is unhidden on the call list 901, as shown in (b) of FIG. 11, the terminal can display all the call records of the call record 903 including the above-mentioned junk tag.

After the terminal displays all the call records of the call record 903 including the above-mentioned junk tag, as shown in (b) of FIG. 11, the button 1001 can be converted from the function of unhiding to the function of hiding the call record including the junk tag. . Then, if the terminal detects that the user clicks the button 1001 at this time, the terminal can hide the call record 903 including the above-mentioned junk tag, and display the call list 901 as shown in (a) of FIG.

Of course, the terminal may also set two buttons (such as a first button and a second button) in the interface of the call list, the first button is used to hide the call record including the garbage tag in the call list, and the second button is used to display the call list. All call records in . In this way, when the terminal detects that the user clicks the first button, the call record 903 including the garbage tag may be hidden in the call list; when the terminal detects that the user clicks the second button, the call record 903 including the garbage tag may be displayed. call records.

In some other embodiments of the present application, the terminal may also determine whether it is necessary to automatically hide or automatically delete the call record with the junk tag by using a specific gesture. Exemplarily, the terminal detects a gesture made by the user in the call list interface, and in response to the gesture, the terminal can determine whether the gesture is the same as the predetermined gesture. When the terminal determines that the detected gesture is the same as the predetermined gesture, the terminal may hide the call record 903 including the junk tag in the call list. Illustratively, the predetermined gesture may be a pull-down gesture or the like in the call list interface, and the embodiment of the present application does not impose any limitation on this.

Optionally, as shown in FIG. 12, when detecting that the user clicks the button 1001 that is unhidden on the call list 901, the terminal may display the call record 903 including the junk tag on the call list 901 to facilitate the user in the call list. Quickly locate and clean up these unimportant call records in the 901. If the user does not detect that the call record 903 is clicked within a preset time (for example, 3 seconds), the user does not need to clear the call records at this time, so the terminal may display the included garbage in a default order (for example, chronological order). The complete call record of the tag's call log 903.

In some other embodiments of the present application, the terminal may also require the user to input identity verification information such as a fingerprint or a password when displaying the call list. After the authentication information input by the user is verified by the terminal, the terminal can automatically delete or automatically hide the call record containing the garbage tag.

For example, as shown in (a) of FIG. 13, the fingerprint collection device is integrated in the home screen button 1211, and then when the user is detected to open the call list, the terminal may prompt the user to enter the fingerprint. After the terminal collects the fingerprint of the user, the terminal verifies the fingerprint according to the fingerprint of the legal user stored in advance, and the verification is passed when the fingerprint input by the user is the fingerprint of the legal user. At this time, as shown in (b) of FIG. 13, the terminal can automatically hide the call record 903 including the junk tag when the call list 901 is displayed, so that the call record 903 including the junk tag is mixed in the call list to interfere with the user pair. Management of normal call records.

Further, as shown in (c) of FIG. 13 , when the terminal does not detect the fingerprint input by the user on the home screen button 1211 (ie, the user's finger is raised) within the preset time (for example, 1 s), the terminal may Displays a complete call record containing the call history including the junk tag in the default order (for example, chronological order).

Alternatively, as shown in FIG. 14, the terminal may also collect all the detected call records 903 including the garbage tags under the directory 1201 of "junk phones". When it is detected that the user clicks on the "garbage phone" directory 1201, the terminal displays all the call records 903 including the garbage tags under the directory 1201, so that the user can uniformly manage the call records of the garbage phones.

With reference to the application scenario shown in FIG. 3 and FIG. 14 and the foregoing embodiment, in a possible implementation manner, as shown in FIG. 15 , a method for managing a call record provided by the embodiment of the present application may be, for example, The method is implemented on the terminal in FIG. 1 and FIG. 2, and the method may specifically include:

S1501: The terminal detects the first call event, where the first call event may be an incoming call event, an outgoing call event, or a missed event.

S1502: The terminal generates a first call record according to the first call event, and saves, where the first call record includes a label of the first number and the first number.

In the steps S1501-S1502, the first call event is an example of an incoming call event. As shown in FIG. 3, when the first number (ie, 13032920112) calls the terminal, if the first number is not stored in the terminal, the terminal may The server obtains the label of the first number. For example, the label may be a fraudulent telephone, an insurance financial telephone, an intermediary telephone, a courier telephone, or a meal delivery telephone.

Further, as shown in FIG. 4, the terminal may store information such as the first number, the type of the call event, the duration of the call, and the obtained label of the first number in the call record table 402, and generate a call record of the first call event. (ie the first call record). At this time, as shown in FIG. 4, if the terminal detects that the user opens the interface of the call list, the terminal may display the newly generated first call record on the top of the call list, where the first call record includes obtaining from the server. The first number to the tag: Scam Phone 404.

Then, in the embodiment of the present application, the terminal may perform intelligent management on the first call record based on the label of the first number. For example, when the label of the first number is a garbage label (for example, a fraudulent telephone), the terminal can automatically delete the first call record, thereby improving the management efficiency of the call record and further saving the storage space of the terminal.

The garbage label may specifically include an intermediary phone, a fraud phone, a sales phone, an insurance phone, a courier phone, or a meal phone. The garbage label may be obtained from the cloud at the terminal, may be set by the manufacturer by default when the terminal is shipped from the factory, or may be manually set by the user during the process of using the terminal, or may be based on the history of the user during the running of the terminal. The data and the like are automatically generated, and the embodiment of the present application does not impose any limitation on this.

In other embodiments of the present application, the terminal may further divide the garbage label into garbage labels of different priorities according to the degree of interference of the different garbage labels on the user's life. When the priority is higher, the garbage label is included. The greater the interference of the call event on the user's life, the correspondingly, the lower the priority, the less the interference of the call event containing the junk tag on the user's life.

For example, the terminal can set the priority of the fraud phone to be higher than the priority of the promotion call, the priority of the promotion call is higher than the priority of the insurance call, the priority of the insurance call is higher than the priority of the real estate call, and the real estate agent calls The priority is higher than the priority of the courier and meal delivery phones.

S1503. When the terminal determines that the label of the first number is the first garbage label, the terminal automatically deletes the first call record after the first time passes.

In step S1503, if the terminal detects that the label included in the first call record is the first garbage label with higher priority, the terminal may perform the first time according to the first cleaning setting set for the first garbage label. Afterwards, all the fields corresponding to the first call record are automatically deleted from the memory of the terminal, for example, the call record table 402 shown in FIG. 4 is deleted. At this time, the first call record is not displayed in the call list interface.

Taking the first garbage tag as a fraudulent phone, the first cleanup setting set by the user for the first garbage tag is: automatically deleted after 24 hours. Then, when the label in the first call record is a fraudulent call, the terminal may automatically delete the call record table of the first call record 24 hours after the first call record is generated.

Exemplarily, as shown in FIG. 5, when the terminal detects that the label of the first number in the call record 1 is a sales call, the terminal may start a first timer with a duration of 24 hours; when the first timer expires, The terminal can automatically delete the call record table of the call record 1.

S1504. When the terminal determines that the label of the first number is the second garbage label (the priority of the second garbage label is lower than the first garbage label), the terminal automatically after the second time (the second time is greater than the first time) Delete the first call record above.

In step S1504, if the terminal detects that the label included in the first call record is the second garbage label with lower priority, the terminal may perform the second time according to the second cleaning setting set for the second garbage label. The call record table of the first call record described above is automatically deleted.

For example, the second garbage label is a courier phone, and the first cleaning setting set by the user for the second garbage tag is: automatically deleted after 7 days. Then, when the label in the first call record is a courier call, the terminal may automatically delete the call record table of the first call record 7 days after the first call record is generated.

Exemplarily, as shown in FIG. 5, when the terminal detects that the label of the first number in the call record 4 is a courier call, the terminal may start a second timer with a duration of 7 days; when the second timer expires The terminal can automatically delete the call record table of the call record 4.

S1505a: When the label of the first number is empty, the terminal monitors whether a new call record is generated with the first number in the preset time period.

S1505b. If no new call record is generated, the terminal automatically deletes the first call record.

In parallel with the above steps S1503 and S1504, in the steps S1505a-S1505b, when the terminal detects that the label field in the first call record is also empty, that is, the label of the first number is empty, the number is a strange number. .

Then, the terminal can monitor whether the user generates a new call record with the strange number within a preset time period (for example, 15 days) of receiving the incoming call of the strange number. If there is no new call record, or the number of new call records is less than the threshold, the user's call demand with the strange number is low, so the terminal can automatically delete the call record table of the first call record after the expiration of 15 days.

In addition, when the terminal automatically deletes the first call record in the foregoing steps S1503, S1504, and S1505b, the terminal may further determine conditions based on the call duration of the first call event, the call type of the first call event, and the number of calls with the first number. Further determining whether to delete the first call record described above.

For example, when the duration of the call of the first call event is less than a preset value (for example, 10 s), it indicates that the user has almost no call requirement with the party in the call record, and therefore, the terminal can automatically delete the first call record including the garbage tag. .

For another example, when the call type of the first call event is an incoming call event, it indicates that the user does not intentionally make an active call to the first number in the first call event, and therefore, the terminal may automatically delete the first call record that includes the garbage tag. .

For another example, when the first number in the first call event is a preset number set by the terminal or set by the user (for example, “10086”), the user intentionally deletes the call record of the number, and therefore, the terminal may automatically delete the garbage included. The first call record of the tag.

For another example, when the number of calls between the terminal and the first number in the first call event is greater than a threshold (for example, 50 times), or the terminal detects that the number of times the user rejects the first number is greater than a threshold (for example, 5 times), the terminal It can also automatically delete the first call record containing the garbage tag, saving the storage space of the terminal.

With reference to the application scenario shown in FIG. 3 and FIG. 14 and the foregoing embodiment, in another possible implementation manner, as shown in FIG. 16 , a method for managing a call record provided by the embodiment of the present application may be As shown in FIG. 1 and FIG. 2, the method may specifically include:

S1601: After detecting the first call event, the terminal generates a first call record and saves the first call record, where the first call record includes a first number and a first label corresponding to the first number.

S1602: After detecting the second call event, the terminal generates a second call record and saves the second call record, where the second call record includes a second number and a second label corresponding to the second number.

S1603: After detecting the third call event, the terminal generates a third call record and saves, where the third call record includes the third number and the first label corresponding to the third number (ie, the label and the first number of the third number) The same label).

By performing steps S1601-S1603, the terminal can generate three call records, that is, a first call record, a second call record, and a third call record in the call list. For example, the first tag in the first call record is a fraudulent phone, and the second tag in the second call record is a courier phone. The tag in the third call record is the same as the first tag in the first call record, and is also a fraud. phone.

The method for the terminal to generate the first call record, the second call record, and the third call record is the same as the method in the steps S1501-S1502 of the foregoing embodiment, and therefore is not described herein again.

Exemplarily, as shown in (a) of FIG. 5, the call record 1 is an incoming call event just received by the terminal, and the tag included in the call record 1 is the sales call 501; the call record 4 is the terminal at 8 o'clock on the day. The incoming call event received in 46 minutes, the tag included in the call record 4 is the express call 502; the call record 5 is the outgoing call event that the terminal calls out at 8:09 on the day, and the tag included in the call record 5 is also the express call. 502. In addition, as shown in (a) of FIG. 5, the call list further includes a call record 2 and a call record 3 with the stored contacts.

S1604: When the duration of the call of the first call event is less than the first preset value, the terminal automatically deletes the first call record after the first time according to the first clear setting preset for the first label.

The first call event may be an incoming call event, an outgoing call event, or a missed event.

The call record 4 in Fig. 5 is taken as an example of the first call record, and the tag of the first number in the call record 4 is the courier phone 502 (i.e., the first tag). If the user sets the first cleanup setting for the express call in advance, when the call duration is less than the first preset value (for example, 15s), the call record including the label of the express call is automatically deleted after 7 days. Then, in step S1604, after the terminal generates the call record 4, the terminal may query whether the first label is a courier phone in the tag field of the call record 4 according to the first cleaning setting, and indicate the duration of the call in the call record 4. In the field, it is queried whether the length of the call of the first call event is less than the first preset value.

When the first label is a courier phone, and the duration of the call of the first call event is less than the first preset value, the terminal may start a timer with a duration of 7 days. When the timer expires, the terminal can automatically delete all the fields in the call record 4, and the call record 4 is not displayed in the call list as shown in (c) of FIG.

S1605: When the duration of the call of the second call event is less than the second preset value, the terminal automatically deletes the second call record after the second time according to the second clear setting preset for the second label.

The second call event may be an incoming call event, an outgoing call event, or a missed event.

Taking the call record 1 in FIG. 5 as an example of the second call record, the tag of the second number in the call record 1 is the sales call 501 (ie, the second tag). If the second cleaning setting set by the user for the sales call is set to: when the call duration is less than the second preset value (for example, 10s), the call record including the tag of the sales call is automatically deleted after one day. Then, in step S1605, after the terminal generates the call record 1, the terminal can query whether the second label is a sales call in the label field of the call record 1 according to the second cleaning setting, and the call record 1 is used to indicate the duration of the call. In the field, it is queried whether the length of the call of the second call event is less than the second preset value.

When the second tag is a sales call, and the call duration of the second call event is less than the second preset value, the terminal may start a timer with a duration of one day. When the timer expires, the terminal can automatically delete all the fields in the call record 1 at this time, and the call record 1 is not displayed in the call list as shown in (b) of FIG. 5 .

S1606: When the duration of the call of the third call event is greater than the third preset value, and the third call event is an outgoing call event, the terminal reserves the third call record, where the third preset value is greater than or equal to the first preset value.

In step S1606, since the label of the third number in the third call event and the label of the first number in the first call event are both the first label (for example, the above-mentioned express call), when the third call record does not satisfy the foregoing When a cleaning setting is performed (for example, the call duration of the third call record is greater than the first preset value of 15 s), the terminal may retain the third call record without automatically deleting the third call record.

Alternatively, the user may further set a reservation setting for retaining the call record for the first tag in advance, for example, the retention setting is: when the call duration is greater than a third preset value (eg, 3 minutes), and the third call event When an event is called, the call history of the tag including the courier call in the call list is retained.

This is because, when the call duration of the third call event is greater than the third preset value, and the third call event is an outgoing call event, it indicates that the call event is likely to be an outgoing call event that the user intentionally performs, and therefore, for the convenience of the user. The third call record of the third call event, the terminal may reserve the third call record.

Taking the call record 5 in FIG. 5 as an example of the third call record, the label of the third number in the call record 5 is also the express call 502, although the labels in the call record 5 and the call record 4 are both the express call 502, but The call duration in the call record 5 is greater than a third preset value (for example, 3 minutes), and the call record 5 is an outgoing call event that the user actively calls. Therefore, the terminal does not need to automatically delete the call record 5, then, as shown in FIG. 5 ( c), 7 days after the terminal generates the call record 5, the call record 5 remains in the call list.

Of course, in addition to automatically clearing the call record for the user according to the label included in the call record, the terminal may also manage the call record in the call list according to other fields in the call record or an edit operation manually input by the user. Referring to the related descriptions of FIG. 1 to FIG. 14 in the above embodiment, details are not described herein again.

It can be understood that, in order to implement the above functions, the above terminal and the like include hardware structures and/or software modules corresponding to each function. Those skilled in the art will readily appreciate that the embodiments of the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

The embodiment of the present application may perform the division of the function modules on the terminal or the like according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.

FIG. 17 is a schematic diagram showing a possible structure of the terminal involved in the foregoing embodiment, which is used to implement the method described in the foregoing method embodiments. Exemplarily, the terminal includes: a detecting unit 1701, a generating unit 1702, and a managing unit 1703.

The detecting unit 1701 is configured to support the terminal to perform the process 1501 in FIG. 15 and the processes 1601-1603 in FIG. 16; the generating unit 1702 is configured to support the terminal to execute the process 1502 in FIG. 15, and the processes 1601-1603 in FIG. 16; The management unit 1703 is for supporting the terminal to execute the processes 1503-1505 (including 1505a and 1505b) in FIG. 15, and the processes 1604-1606 in FIG. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

In the case of employing an integrated unit, the above-described detecting unit 1701, generating unit 1702, and management unit 1703 may be integrated as a processing module. Of course, the terminal may further include a storage module, a communication module, an input and output module, and the like.

At this time, as shown in FIG. 18, a possible schematic structural view of the terminal involved in the above embodiment is shown. The processing module 1801 is configured to control and manage the action of the terminal. The communication module 1802 is configured to support communication between the terminal and other network entities. The input/output module 1803 is for receiving information input by a user or outputting information provided to the user and various menus of the terminal. The storage module 1804 is configured to save program codes and data of the terminal.

Exemplarily, the processing module 1801 may be a processor or a controller, for example, may be a central processing unit (CPU), a GPU, a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit. (Application-Specific Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.

The communication module 1802 can be a transceiver, a transceiver circuit, an input/output device, a communication interface, or the like. For example, the communication module 2002 may specifically be a Bluetooth device, a Wi-Fi device, a peripheral interface, or the like.

The memory module 1804 can be a memory, which can include high speed random access memory (RAM), and can also include non-volatile memory, such as magnetic disk storage devices, flash memory devices, or other volatile solid state storage devices.

The input/output module 1803 can be an input/output device such as a touch screen, a keyboard, a microphone, and a display. The display may specifically be configured in the form of a liquid crystal display, an organic light emitting diode or the like. In addition, a touch panel can be integrated on the display for collecting touch events on or near the display, and transmitting the collected touch information to other devices (such as a processor, etc.).

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it may appear in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present application should be covered by the scope of the present application. . Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A method for managing a call record, the method being implemented in a terminal having a touch screen, comprising:

The terminal detects the first call event, generates a first call record, and saves the first call record, where the first call record includes a first number and a first label corresponding to the first number;

The terminal detects the second call event, generates a second call record, and saves the second call record, where the second call record includes a second number and a second label corresponding to the second number;

The terminal detects a third call event, generates a third call record, and saves the third call record, where the third call record includes a third number and the first label corresponding to the third number;

When the terminal determines that the duration of the call of the first call event is less than the first preset value, the terminal automatically deletes the first time after the first time according to the first clear setting preset for the first label. First call record;

When the terminal determines that the duration of the call of the second call event is less than the second preset value, the terminal automatically deletes the second time after the second time according to the second clear setting preset for the second label. Second call record;

When the terminal determines that the call duration of the third call event is greater than a third preset value, and the third call event is an outgoing call event, the terminal reserves the third call record, the third preset The value is greater than or equal to the first preset value.
The method of claim 1 wherein

The first call event is an incoming call event, an outgoing call event, or a missed event;

The second call event is an incoming call event, an outgoing call event, or a missed event.
The method according to claim 1 or 2, wherein the tag is: a real estate intermediary phone, a fraud phone, a sales phone, an insurance bank phone, a courier phone or a meal phone.
The method according to any one of claims 1 to 3, wherein the tag is stored in a CACHED_NUMBER_LABEL field or a MARK_CONTENT field of calls.db in the Android operating system.
A terminal, wherein the terminal comprises:

a touch screen, wherein the touch screen includes a touch sensitive surface and a display;

One or more processors;

a memory for storing a plurality of applications, and one or more computer programs; wherein the one or more computer programs include instructions that, when executed by the terminal, cause the terminal to perform the following steps:

Displaying a first graphical user interface GUI in the touch screen; the first GUI includes a first call record and a second call record; wherein the first call record includes a first number and the first number Corresponding first label, the second call record includes a second number and a second label corresponding to the second number, where the label of the first number is a garbage label; a control, the first control is used to hide or display a call record including the garbage tag;

The terminal detects a first input event for the first control in the first GUI;

Displaying, in the touch screen, a second GUI, where the second GUI includes the first control and the second call record, but not including the first call record, in response to the first input event;

The terminal detects a second input event for the first control in the second GUI;

The first GUI is displayed in the touch screen in response to the second input event.
The terminal according to claim 5, wherein the first GUI further comprises a second control, wherein the second control is used to edit a call record displayed in the first GUI;

After the first GUI is displayed on the touch screen, the method further includes:

The terminal detects a third input event for the second control in the first GUI;

In response to the third input event, a third GUI is displayed in the touch screen, the third GUI including the first call record that is topped displayed and automatically selected.
The terminal according to claim 6, wherein after displaying the third GUI in the touch screen, the method further comprises:

If the input operation of the third GUI by the user is not received within the preset time, the first GUI is displayed in the touch screen.
The terminal according to any one of claims 5-7, wherein in the first GUI, a call record of the junk tag is displayed topped.
A method for managing a call record, the method being implemented in a terminal having a touch screen, comprising:

The terminal detects the first call event, generates a first call record, and saves the first call record, where the first call record includes a first number and a first label corresponding to the first number;

The terminal detects the second call event, generates a second call record, and saves the second call record, where the second call record includes a second number and a second label corresponding to the second number;

When the terminal determines that the first label is a preset first garbage label, the terminal automatically deletes the first call record after the first time passes;

When the terminal determines that the second label is a preset second garbage label, the terminal automatically deletes the second call record after the second time passes;

The first garbage label has a higher priority than the second garbage label, and the first time is less than the second time.
The method of claim 9 wherein the method further comprises:

The terminal detects a third call event, generates a third call record, and saves, where the third call record includes a third number, and the label of the third number is empty;

The terminal monitors whether the terminal generates a new call record with the third number within a preset time period;

If no new call record is generated, the terminal automatically deletes the third call record.
The method according to claim 9 or 10, wherein the terminal automatically deleting the first call record comprises:

When the duration of the call of the first call event is less than a preset value, the terminal automatically deletes the first call record, or

When the first call event is an incoming call event, the terminal automatically deletes the first call record, or

When the first number is a preset number, the terminal automatically deletes the first call record, or

When the number of calls between the terminal and the first number is greater than a threshold, the terminal automatically deletes the first call record, or

When the number of call records stored in the terminal reaches a preset upper limit, the terminal automatically deletes the first call record.
The method according to any one of claims 9-11, wherein the preset garbage label comprises at least one of a real estate intermediary telephone, a fraud telephone, a sales call, an insurance financial call, a courier call, and a meal call. item;

Wherein the priority of the fraudulent telephone is higher than the priority of the promotional telephone, the priority of the promotional telephone is higher than the priority of the insurance financial telephone, and the priority of the insurance telephone is higher than the real estate. The priority of the intermediary phone, the priority of the real estate agent phone is higher than the priority of the courier phone and the meal delivery phone.
A terminal, comprising:

a detecting unit, configured to: detect a first call event, a second call event, and a third call event;

a generating unit, configured to: generate a first call record, where the first call record includes a first number and a first label corresponding to the first number; and generate a second call record, where the second call record includes a second number and a second label corresponding to the second number; and a third call record, where the third call record includes a third number and the first label corresponding to the third number;

a management unit, configured to: when the terminal determines that the duration of the call of the first call event is less than the first preset value, according to the first clear setting preset for the first label, after the first time Deleting the first call record; when the terminal determines that the call duration of the second call event is less than a second preset value, according to the second clear setting preset for the second label, after the second time Automatically deleting the second call record; and when the terminal determines that the call duration of the third call event is greater than a third preset value, and the third call event is an outgoing call event, retaining the third call record The third preset value is greater than or equal to the first preset value.
The terminal of claim 13 wherein:

The first call event is an incoming call event, an outgoing call event, or a missed event;

The second call event is an incoming call event, an outgoing call event, or a missed event.
The terminal according to claim 13 or 14, wherein the tag is: a real estate intermediary phone, a fraud phone, a sales phone, an insurance money phone, a courier phone or a meal phone.
The terminal according to any one of claims 13-15, wherein the tag is stored in a CACHED_NUMBER_LABEL field or a MARK_CONTENT field of calls.db in the Android operating system.
A terminal, comprising:

a touch screen, wherein the touch screen includes a touch sensitive surface and a display;

One or more processors;

a memory for storing a plurality of applications, and one or more computer programs; wherein the one or more computer programs include instructions that, when executed by the terminal, cause the terminal to perform the following steps:

The terminal detects the first call event, generates a first call record, and saves the first call record, where the first call record includes a first number and a first label corresponding to the first number;

The terminal detects the second call event, generates a second call record, and saves the second call record, where the second call record includes a second number and a second label corresponding to the second number;

The terminal detects a third call event, generates a third call record, and saves the third call record, where the third call record includes a third number and the first label corresponding to the third number;

When the terminal determines that the duration of the call of the first call event is less than the first preset value, the terminal automatically deletes the first time after the first time according to the first clear setting preset for the first label. First call record;

When the terminal determines that the duration of the call of the second call event is less than the second preset value, the terminal automatically deletes the second time after the second time according to the second clear setting preset for the second label. Second call record;

When the terminal determines that the call duration of the third call event is greater than a third preset value, and the third call event is an outgoing call event, the terminal reserves the third call record, the third preset The value is greater than or equal to the first preset value.
The terminal according to claim 17, wherein the first call event is an incoming call event, an outgoing call event or a missed event; and the second call event is an incoming call event, an outgoing call event or a missed event.
The terminal according to claim 17 or 18, wherein the tag is: a real estate intermediary phone, a fraud phone, a sales phone, an insurance money phone, a courier phone or a meal phone.
The terminal according to any one of claims 17 to 19, wherein the tag is stored in a CACHED_NUMBER_LABEL field or a MARK_CONTENT field of calls.db in the Android operating system.
A computer readable storage medium having stored therein instructions, wherein when the instructions are run on a terminal, causing the terminal to perform as in claims 1-4 or 9-12 A method of managing call records as described in any one of the preceding claims.
A computer program product comprising instructions, wherein when said computer program product is run on a terminal, said terminal is caused to perform a call record according to any one of claims 1-4 or 9-12 Management method.