CN110933222A - Call control method, device, equipment and computer readable medium - Google Patents

Call control method, device, equipment and computer readable medium Download PDF

Info

Publication number
CN110933222A
CN110933222A CN201811100224.4A CN201811100224A CN110933222A CN 110933222 A CN110933222 A CN 110933222A CN 201811100224 A CN201811100224 A CN 201811100224A CN 110933222 A CN110933222 A CN 110933222A
Authority
CN
China
Prior art keywords
call
hang
duration
command
current
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201811100224.4A
Other languages
Chinese (zh)
Other versions
CN110933222B (en
Inventor
张亮中
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201811100224.4A priority Critical patent/CN110933222B/en
Publication of CN110933222A publication Critical patent/CN110933222A/en
Application granted granted Critical
Publication of CN110933222B publication Critical patent/CN110933222B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72451User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to schedules, e.g. using calendar applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72484User interfaces specially adapted for cordless or mobile telephones wherein functions are triggered by incoming communication events

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)

Abstract

The embodiment of the invention discloses a call control method, a device, equipment and a computer readable medium, which relate to the field of terminals, wherein the method comprises the following steps: the terminal determines a delay hang-up duration for preventing the call from being hung up by mistake according to the type of the contact of the current call; determining whether the detected hang-up command of the current call is an invalid hang-up command triggered by mistake within the time delay hang-up duration; and if the hang-up command is determined to be the false-triggered invalid hang-up command, restoring the conversation state of the current conversation.

Description

Call control method, device, equipment and computer readable medium
Technical Field
The embodiments of the present invention relate to the field of terminals, and in particular, to a method, an apparatus, a device, and a computer readable medium for controlling a call.
Background
The call function is one of the most important and frequently used functions in a terminal (such as a mobile phone), and users use the call function to make mutual contact. The call is represented not only by making a call by using the call application of the terminal system, but also by performing a network call by using a third party application (for example, WeChat). The call can be in the form of voice call, video call, conference call, and the like. No matter which kind of conversation is, the user must hang up the conversation when the conversation is finished so as to avoid wasting resources. However, in some cases, a false touch may occur during a call, resulting in a call being dropped.
Disclosure of Invention
The embodiment of the invention provides a call control method, a call control device, call control equipment and a computer readable medium, and solves the problem of call miss hang-up.
The embodiment of the invention provides a call control method, which comprises the following steps:
the terminal determines a delay hang-up duration for preventing the call from being hung up by mistake according to the type of the contact of the current call;
determining whether the detected hang-up command of the current call is an invalid hang-up command triggered by mistake within the time delay hang-up duration;
and if the hang-up command is determined to be the false-triggered invalid hang-up command, restoring the conversation state of the current conversation.
An embodiment of the present invention provides a call control device, where the device includes:
the time length determining module is used for determining the time delay hang-up time length used for preventing the call from being hung up by mistake according to the contact person category of the current call;
the command determining module is used for determining whether the detected hanging-up command of the current call is a false-triggered invalid hanging-up command within the time delay hanging-up duration;
and the call recovery module is used for recovering the call state of the current call if the hang-up command is determined to be the false-triggered invalid hang-up command.
The embodiment of the invention provides a call control device, which comprises a processor and a memory; the memory stores a call control program which can run on the processor, and the call control program realizes the steps of the call control method when being executed by the processor.
An embodiment of the present invention provides a computer-readable medium, on which a call control program is stored, where the call control program, when executed by a processor, implements the steps of the call control method described above.
According to the embodiment of the invention, the contacts of different types (or classifications) are delayed for different time according to the contact types (or classifications), so that the purpose of preventing mistaken touch is achieved, the mistaken hanging-up of the call is avoided, and the call control of system level and cross-application is realized.
Drawings
Fig. 1 is a first flowchart of a call control method according to an embodiment of the present invention;
fig. 2 is a second flowchart of a call control method according to an embodiment of the present invention;
fig. 3 is a schematic block diagram of a call control system according to an embodiment of the present invention;
FIG. 4 is a detailed flow diagram of call control of the system of FIG. 3;
FIG. 5 is a detailed flowchart of step S303 in FIG. 4;
FIG. 6 is a detailed flowchart of step S404 in FIG. 5;
FIG. 7 is a schematic diagram of a false touch detection prevention application setting interface according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of a false touch prevention confirmation interface according to an embodiment of the present invention;
fig. 9 is a schematic block diagram of a call control device according to an embodiment of the present invention;
fig. 10 is a schematic structural block diagram of a call control device according to an embodiment of the present invention.
Detailed Description
The embodiments of the present invention will be described in detail below with reference to the accompanying drawings, and it should be understood that the embodiments described below are only for illustrating and explaining the present invention and are not intended to limit the present invention.
The embodiment of the invention carries out time delay of different degrees according to the classification of the contact persons so as to achieve the aim of preventing mistaken touch and hang up. Contacts can be divided into at least the following categories: 1. collecting the contact persons; 2. a common contact; 3. contact list contacts of other than the two categories; 4. a strange number; 5. numbers identified by third parties, networks as advertisements, promotions, harassments, etc. The method can set a default value (or default time length or default time delay) aiming at different contact person classifications, can also provide a user interaction entrance for setting time delay in the system setting application, and through the entrance, a user can carry out self-defined setting on the basis of the default time delay, and can also dynamically set the time delay (or the time delay hang-up time length) through the monitored call time (or the call time length). The embodiment of the invention can be applied to various terminals with a communication function, such as mobile phones, tablet computers and the like.
Fig. 1 is a first flowchart of a call control method according to an embodiment of the present invention, and as shown in fig. 1, the method may include:
step S101: and the terminal determines the time length of the delayed hanging-up for preventing the call from being hung up by mistake according to the type of the contact of the current call.
In one embodiment, the terminal obtains the contact information (e.g., a mobile phone number) of the current call, determines a contact type to which the contact information of the current call belongs, and searches and determines a time length of the delay hang-up corresponding to the contact type.
In this embodiment, the contact categories include, but are not limited to, favorite contacts, common contacts, contacts in the address list other than the favorite contacts and the common contacts, and user-defined categories of mobile phone numbers of different contacts performed by the user.
In this embodiment, the terminal may pre-establish a corresponding relationship table between the contact classification and the delay duration, for example, if the contact belongs to the collected contact, the delay is 2s, so that the delay hang-up duration (or the default duration) corresponding to the contact classification may be found by looking up the table.
In another embodiment, the terminal may dynamically adjust the default duration based on the above embodiments. Firstly, acquiring the contact information of the current call, determining the contact type to which the contact information of the current call belongs, searching the delay hang-up time corresponding to the contact type, then counting the call frequency of the contact, acquiring the call time of the current call after detecting the hang-up command of the current call, and finally dynamically adjusting the default time according to at least one of the call frequency and the call time to obtain the adjusted delay hang-up time.
In this embodiment, the terminal may dynamically adjust the default duration according to the call frequency to obtain the adjusted delay hang-up duration. That is, the terminal may extend the default duration appropriately as the frequency of calls increases. For example, every 5 times of call times increase in 30 days, the default duration is extended by the step length of 0.5s until the delay hang-up duration reaches 5 s.
In this embodiment, the terminal may dynamically adjust the default duration according to the call duration to obtain the adjusted delay hang-up duration. That is, the terminal may extend the default duration appropriately as the call duration increases. For example, every 5 minutes of the call duration, the default duration is extended by the step length of 0.5s until the delayed hang-up duration reaches 5 s.
In this embodiment, the terminal may dynamically adjust the default duration according to the call frequency and the call duration to obtain an adjusted delay hang-up duration. That is, the terminal may appropriately extend the default duration as the call frequency and the call duration increase. For example, if the number of calls in 30 days is 6, and the call duration of the current call is 12 minutes, the default duration (e.g., 2s) found in the above embodiment is extended by 1.5s (i.e., 0.5s +1s), and at this time, the adjusted delay hang-up duration is 3.5 s.
It should be noted that the above-mentioned time delay hang-up time may be customized by the user according to the contact category.
Step S102: and determining whether the detected hang-up command of the current call is an invalid hang-up command triggered by mistake within the time delay hang-up duration.
In one embodiment, a false touch prevention confirmation interface is displayed, if a call return command is received through the false touch prevention confirmation interface within the delay hang-up duration, it is determined that the detected call hang-up command of the current call is a false-triggered invalid hang-up command, and if a call return command is not received or a call still received through the false touch prevention confirmation interface within the delay hang-up duration, it is determined that the detected call hang-up command of the current call is a valid hang-up command, and the current call can be hung up.
The embodiment distinguishes different contacts aiming at the current situation that most applications do not provide a call false touch prevention function or the false touch prevention function of part of applications only carries out unified time delay when a hang-up command is received, sets different time delays for the different contacts, provides a false touch prevention confirmation interface for a user, and the user can return to the state before clicking a hang-up button through operation on the false touch prevention confirmation interface so as to prevent false hang-up.
Step S103: and if the hang-up command is determined to be the false-triggered invalid hang-up command, restoring the conversation state of the current conversation, namely not hanging up the current conversation.
Fig. 2 is a second flow chart of a call control method according to an embodiment of the present invention, and as shown in fig. 2, the method may include:
step S100: after detecting the hang-up command of the current call, the terminal determines whether to carry out the delayed hang-up processing on the current call, namely, the direct hang-up processing or the delayed hang-up processing is carried out.
In one embodiment, the terminal determines to perform direct hang-up processing or delayed hang-up processing on the current call according to the contact information.
In this embodiment, the terminal obtains contact information (e.g., a mobile phone number) of the current call, and if it is determined that the current call is a nuisance call according to the contact information, it determines to perform direct hang-up processing on the current call, otherwise, it determines to perform delay hang-up processing on the current call, so as to execute the following steps S101 to S103. For example, the contact of the current call is marked as 'harassment' by a third party, which indicates that the current call is a harassment call, and at this time, the current call can be directly hung up according to a hang-up command. For another example, if the contact is an address list contact, and the current call is not a harassing call, determining to perform delayed hanging-up processing on the current call.
In another embodiment, the terminal determines to perform direct hang-up processing or delayed hang-up processing on the current call according to the call duration.
In this embodiment, the terminal acquires the call duration of the current call after detecting the hang-up command of the current call, determines to directly hang up the current call if the call duration is less than a preset call duration, and otherwise determines to perform delayed hang-up processing on the current call to execute steps S101 to S103. For example, assuming that the preset call duration is 10s, when the call duration of the current call is less than 10s, determining to perform direct hang-up processing on the current call, otherwise, determining to perform delay hang-up processing on the current call.
In another embodiment, the terminal determines to perform direct hang-up processing or delayed hang-up processing on the current call according to the contact information and the call duration.
In this embodiment, the terminal obtains contact information (e.g., a mobile phone number) of the current call, obtains a call duration of the current call after detecting a hang-up command of the current call, determines that the current call is a nuisance call and the call duration is less than a preset call duration according to the contact information, determines to directly hang up the current call, and otherwise determines to perform a delayed hang-up process on the current call so as to execute steps S101 to S103. For example, if the contact is an address list contact and the call duration is greater than 10s, determining to perform delayed hanging-up processing on the current call.
Steps S101 to S103 of the embodiment of fig. 2 are the same as those of fig. 1, and are not repeated herein.
In the embodiments of fig. 1 and fig. 2, the current call may be a call of a false touch prevention application, and the method further includes: and displaying a false touch prevention application setting interface, and acquiring the user-defined false touch prevention application from the false touch prevention application setting interface. Based on this, the terminal may acquire the application to which the current call belongs before performing step S101 in fig. 1 or before performing step S100 in fig. 2, and determine whether the application is a user-defined false touch prevention application, and if the application is the false touch prevention application, may continue the subsequent processing steps.
It should be noted that all the call applications in the system of the communication terminal can be hung up with different durations according to the contact classification when the call applications are hung up.
It should be noted that the contact may be an address book contact of a terminal system call application, or an address book contact of a third party application supporting a call function.
There are currently many applications that support telephony functions. Such applications are installed and run on various terminal operating systems. The connection and disconnection of the call functions of these applications requires support from the system framework. Fig. 3 is a schematic structural block diagram of a call control system according to an embodiment of the present invention, as shown in fig. 3, including a decision system at a framework layer, a call application at an application layer, and a false touch prevention setting application.
The call application of the embodiment of the invention can be various applications which run on an operating system and support audio and video calls, and the applications are sourced from different developers. The existing partial call application does not provide the function of preventing the false hang-up completely, and the partial call application only provides the simple function of preventing the false hang-up. Aiming at the difference, the embodiment of the invention provides a system-level method for preventing mistaken hang-up for various applications supporting conversation on an operating system.
The embodiment of the invention provides an interaction entrance for the user to perform delay setting according to different contact classifications, namely the false touch prevention setting application shown in fig. 3, and the interaction entrance is mainly used for the user to select the application for performing false touch prevention detection (namely, a false touch prevention application setting interface is provided for the user to select the false touch prevention application). The interactive portal may be a separate application or may be integrated into a setup application of the operating system.
The decision system of the embodiment of the invention judges the number of the current call to be hung up when a user selects to start the anti-false touch application and receives a hang-up command, determines the classification and the contact frequency of the contact person where the number is located, acquires the current call duration, combines the setting value of the delay setting application, determines the delay hang-up time (or the delay hang-up duration) by a certain method, and then informs the call application of delay hang-up. The call application and the delay setting application are both implemented in the application layer.
Fig. 4 is a detailed flow chart of call control of the system shown in fig. 3, and as shown in fig. 4, the steps may include:
step S301: an application is set to be suspended for delay to prevent false touches.
In this step, the application to be delay hung up is set in the delay setting application by the user. The application list lists all applications supporting the call in the terminal operating system, and the delayed hang-up is performed only when the selected application calls.
Step S302: it is detected whether the application marked in step S301 has a command to hang up the phone (i.e., a hang up command). The following steps are only performed if a hang-up command is detected for the marking application.
Step S303: when the framework layer receives a hang-up command, the decision system can decide whether to carry out delayed hang-up or not according to the information of the contact person of the current call and the call duration, determine the delayed duration according to the classification priority of the contact person, and delay the duration to carry out hang-up so that a user can return to the state before the mistaken touch.
Step S304: during the time delay hang-up, if the user clicks a button for returning to the state before the false touch, the user returns to the conversation state before the false touch, and whether a hang-up command exists is monitored again.
Fig. 5 is a detailed flowchart of step S303 in fig. 4, and as shown in fig. 5, the step of determining (or deciding) whether to delay by the decision system may include:
step S401: and when a hang-up command is received, the decision system acquires the contact information of the current call. The contact information includes whether the contact is a frequent contact, whether it is already collected and/or set-top (i.e., whether it is already collected or set-top or both), whether it is tagged as harassing/intermediating by a third party (i.e., harassing or intermediating), etc., whether it is a strange number, etc.
Step S402: the decision-making system obtains the call duration.
Step S403: and judging the call duration, and if the current call duration is less than the preset call duration (for example, 10 seconds), determining that the call is not mistakenly hung up, and directly hanging up normally without delaying.
Step S404: and if the call number does not meet the condition of the step S403, the decision system acquires whether the call number is marked as harassment, intermediary or the like by a third party through the contact information, and if the call number is marked, the call number is directly hung up without delay.
Step S405: on the premise that the conditions of the step S403 and the step S404 are not satisfied, the delay time duration (or the delay hang-up time duration) is determined according to the contact classification.
Step S406: and after the delay time length is determined in the step S405, a delay hang-up is performed for the user to return to the interface before the error touch.
Step S407: if the button in step S403 or step S404 is satisfied or if the user does not operate the button to return to the state before the false touch, normal hang-up is performed.
Fig. 6 is a detailed flowchart of step S404 in fig. 5, and as shown in fig. 6, delays of 2S, 1.5S, 1S, and 0.5S are respectively performed according to the contact classification priority. The priority of the contact classification is from high to low: the collection/top contact (namely the collection contact or the top contact), the common contact and the contact stored in the address list. The step of the decision system determining the delay time length according to the contact classification may comprise:
step S501 to step S502: if the contact of the current call is a favorite/set-top contact (i.e. favorite contact or set-top contact), delaying for 2S after detecting the hang-up command of the current call, otherwise executing the steps S503 to S504.
Step S503 to step S504: if the contact of the current call is a frequently-used contact, delaying for 1.5S after detecting the hang-up command of the current call, otherwise executing the steps S505 to S506.
Step S505 to step S506: if the contact of the current call is a collection/top contact (namely a collection contact or a top contact), delaying for 1s after detecting the hang-up command of the current call, otherwise delaying for 0.5 s.
Fig. 7 is a schematic diagram of a setting interface of a false touch detection preventing application according to an embodiment of the present invention, where a user selects an application to be subjected to false touch hang-up detection in the false touch prevention setting application, a selection interface (or a false touch prevention application setting interface) is as shown in fig. 7, 601 denotes the selected application, 602 denotes the unselected application, and after the selection is completed, if a determination button is clicked 603, the current selection is saved, otherwise, if a cancel button is clicked 604, the current interface is exited, and no option is saved. The embodiment of the invention provides the interactive entrance for the user, so that the user can set different applications, and the user-defined effect is achieved.
Fig. 8 is a schematic diagram of a false touch prevention confirmation interface according to an embodiment of the present invention, where when a call that may be hung up by a false touch is detected, the decision system determines that the current call is to be hung up with a delay, and at this time, the system pops up the confirmation interface (or the false touch prevention confirmation interface) shown in fig. 8, so that the user returns to the call interface before the false touch. The countdown is displayed in the area 701, the specific time is determined by a decision system, and if the user has no operation within the time of ending the countdown (or the operation of returning to the call is not received within the time delay hang-up duration), the current call is considered to be normally hung up. In the delayed confirmation stage, if the user clicks the call return button of 702, the pop-up frame (or confirmation interface) disappears, and returns to the normal call interface; if the user clicks the hang-up button of 703, the current call is not mistakenly touched and hung up, and the current call is immediately hung up.
Fig. 9 is a schematic structural block diagram of a call control device according to an embodiment of the present invention, and as shown in fig. 9, the device may include: the duration determination module 81, the command determination module 82, and the call resumption module 83 may implement the functions of the decision making system shown in fig. 3.
The duration determining module 81 is configured to determine a delay hang-up duration for preventing a call from being hung up by mistake according to the type of the contact of the current call.
In one embodiment, the duration determining module 81 obtains the contact information (for example, a mobile phone number) of the current call, determines a contact type to which the contact information of the current call belongs, and searches and determines a delay hang-up duration corresponding to the contact type. The contact person category includes but is not limited to favorite contact persons, common contact persons, contact persons in other address lists except for the favorite contact persons and the common contact persons, and user-defined categories of mobile phone numbers of different contact persons by a user.
In another embodiment, the duration determining module 81 may dynamically adjust the default duration based on the above embodiments. Namely, the duration determining module 81 first obtains the contact information of the current call, determines the contact type to which the contact information of the current call belongs, searches for the delay hang-up duration corresponding to the contact type, then counts the call frequency of the contact, obtains the call duration of the current call after detecting the hang-up command of the current call, and finally dynamically adjusts the default duration according to at least one of the call frequency and the call duration (i.e., the call frequency, or the call duration, or the call frequency and the call duration) to obtain the adjusted delay hang-up duration.
The command determining module 82 is configured to determine whether the detected hang-up command of the current call is an invalid hang-up command triggered by a mistake within the delay hang-up duration.
In one embodiment, the command determining module 82 displays a false touch prevention confirmation interface, determines that the detected hang-up command of the current call is a false triggered invalid hang-up command if a call return command is received through the false touch prevention confirmation interface within the delay hang-up duration, and determines that the detected hang-up command of the current call is a valid hang-up command if a call return command is not received or a received call still is a hang-up command within the delay hang-up duration, so as to hang up the current call.
The call resuming module 83 is configured to resume the call state of the current call if it is determined that the hangup command is an invalid hangup command triggered by a false trigger, that is, the current call is not hung up.
Based on any of the above embodiments, the duration determining module 81 may be further configured to determine whether to perform a delay hang-up process on the current call after detecting a hang-up command of the current call, that is, perform a direct hang-up process or perform a delay hang-up process, so as to determine a delay hang-up duration for preventing a call from being hung up by mistake when determining to perform the delay hang-up process on the current call. Specifically, the duration determining module 81 may determine to perform direct hang-up processing or delay hang-up processing on the current call according to at least one of the contact information and the call duration.
In one embodiment, the duration determining module 81 may obtain contact information (for example, a mobile phone number) of the current call, and determine to directly hang up the current call if it is determined that the current call is a nuisance call according to the contact information, or determine to perform delay hang up processing on the current call if not.
In another embodiment, the duration determining module 81 may obtain the call duration of the current call after detecting the hang-up command of the current call, determine to directly hang up the current call if the call duration is less than a preset call duration, and otherwise determine to perform delayed hang-up processing on the current call.
In another embodiment, the duration determining module 81 may obtain contact information (e.g., a mobile phone number) of the current call, and obtain a call duration of the current call after detecting a hang-up command of the current call, and if it is determined that the current call is a nuisance call and the call duration is less than a preset call duration according to the contact information, determine to directly hang up the current call, otherwise determine to perform a delayed hang-up process on the current call.
Based on any one of the above embodiments, the current call may be a call of a false touch prevention application, and the duration determination module 81 may further display a false touch prevention application setting interface, and obtain the user-defined false touch prevention application from the false touch prevention application setting interface. Based on this, the duration determining module 81 may obtain the application to which the current call belongs, and determine whether the application is the user-defined false touch prevention application, and if the application is the false touch prevention application, may continue to determine to perform subsequent processing on the current call.
Fig. 10 is a schematic block diagram of a call control device according to an embodiment of the present invention, where the call control device may include a processor and a memory, as shown in fig. 10; the memory stores a call control program which can run on the processor, and the call control program realizes the steps of the call control method when being executed by the processor.
An embodiment of the present invention further provides a computer readable medium, on which a call control program is stored, where the call control program, when executed by a processor, implements the steps of the call control method described above.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
According to the embodiment of the invention, different hang-up delays are set for different classified contacts, so that the problem of hang-up behavior caused by mistaken touch in the conversation process is solved, and the user experience is improved.
Although the embodiments of the present invention have been described in detail above, the embodiments of the present invention are not limited thereto, and those skilled in the art can make various modifications according to the principles of the embodiments of the present invention. Therefore, any modifications made to the principles of the embodiments of the present invention should be understood to fall within the scope of the present invention.

Claims (10)

1. A call control method, comprising:
the terminal determines a delay hang-up duration for preventing the call from being hung up by mistake according to the type of the contact of the current call;
determining whether the detected hang-up command of the current call is an invalid hang-up command triggered by mistake within the time delay hang-up duration;
and if the hang-up command is determined to be the false-triggered invalid hang-up command, restoring the conversation state of the current conversation.
2. The method of claim 1, wherein before the terminal determines the delay hang-up duration for preventing the call from being hung up by mistake according to the contact category of the current call, the method further comprises:
acquiring the call duration of the current call after the hang-up command of the current call is detected;
and determining to carry out direct hanging-up processing or delayed hanging-up processing on the current call according to at least one of the contact information and the call duration.
3. The method of claim 2, wherein determining whether to directly hang up or delay hang up the current call according to at least one of the contact information and the call duration comprises:
if the current call is determined to be a harassing call according to the contact information, determining to perform direct hang-up processing on the current call, and otherwise determining to perform delay hang-up processing on the current call;
or, if the call duration is less than a preset call duration, determining to perform direct hang-up processing on the current call, otherwise, determining to perform delay hang-up processing on the current call;
or if the current call is determined to be a harassing call according to the contact information, and the call duration is less than the preset call duration, determining to perform direct hang-up processing on the current call, otherwise determining to perform delayed hang-up processing on the current call.
4. The method according to any one of claims 1-3, wherein the determining, by the terminal, the delayed hang-up duration for preventing the call from being hung up by mistake according to the contact category of the current call comprises:
acquiring the contact information of the current call;
determining the contact type to which the contact information of the current call belongs;
and searching and determining the time length of the delayed hanging-up corresponding to the contact person type.
5. The method according to claim 2 or 3, wherein the terminal determines the time delay hang-up duration for preventing the call from being hung up by mistake according to the contact type of the current call, and the method comprises the following steps:
acquiring the contact information of the current call;
determining the contact type to which the contact information of the current call belongs;
searching the time length of the delayed hangup corresponding to the contact person;
counting the call frequency of the contact persons;
and dynamically adjusting the searched time delay hang-up time according to at least one of the call frequency and the call time to obtain the adjusted time delay hang-up time.
6. The method of claim 1, wherein the current call is a call for a false touch prevention application, the method further comprising:
displaying an application setting interface for preventing false touch;
and acquiring the user-defined false touch prevention application from the false touch prevention application setting interface.
7. The method of claim 1, wherein the determining whether the detected hang-up command for the current call is a false-triggered invalid hang-up command within the delayed hang-up duration comprises:
displaying a false touch prevention confirmation interface;
and if a call return command is received through the false touch prevention confirmation interface within the delay hang-up duration, determining that the detected hang-up command of the current call is a false-triggered invalid hang-up command.
8. A call control apparatus, comprising:
the time length determining module is used for determining the time delay hang-up time length used for preventing the call from being hung up by mistake according to the contact person category of the current call;
the command determining module is used for determining whether the detected hanging-up command of the current call is a false-triggered invalid hanging-up command within the time delay hanging-up duration;
and the call recovery module is used for recovering the call state of the current call if the hang-up command is determined to be the false-triggered invalid hang-up command.
9. A call control device, the device comprising a processor and a memory; characterized in that the memory has stored thereon a call control program executable on the processor, the call control program, when executed by the processor, implementing the steps of the call control method according to any one of claims 1 to 7.
10. A computer-readable medium, on which a call control program is stored, which when executed by a processor implements the steps of the call control method according to any one of claims 1 to 7.
CN201811100224.4A 2018-09-20 2018-09-20 Call control method, device, equipment and computer readable medium Active CN110933222B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811100224.4A CN110933222B (en) 2018-09-20 2018-09-20 Call control method, device, equipment and computer readable medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811100224.4A CN110933222B (en) 2018-09-20 2018-09-20 Call control method, device, equipment and computer readable medium

Publications (2)

Publication Number Publication Date
CN110933222A true CN110933222A (en) 2020-03-27
CN110933222B CN110933222B (en) 2022-05-10

Family

ID=69856285

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811100224.4A Active CN110933222B (en) 2018-09-20 2018-09-20 Call control method, device, equipment and computer readable medium

Country Status (1)

Country Link
CN (1) CN110933222B (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030010213A (en) * 2001-07-26 2003-02-05 삼성전자주식회사 Method for controlling volume of wireless headset in portable phone onboard bluetooth
US20080056243A1 (en) * 2003-02-11 2008-03-06 Roy Radhika R Access independent common architecture for real-time communications services for networking environments
CN101924811A (en) * 2010-06-25 2010-12-22 康佳集团股份有限公司 Mobile phone with auto-answer function and auto-answer method for mobile phone
CN103391372A (en) * 2013-07-31 2013-11-13 广东欧珀移动通信有限公司 Intelligent conversation time reminding method and intelligent conversation time reminding device
CN104038648A (en) * 2014-06-06 2014-09-10 陈伟 Method and device for recognizing crank calls
US9497304B1 (en) * 2007-06-07 2016-11-15 West Corporation Method and apparatus for voice recognition unit simulation
CN106791231A (en) * 2016-11-30 2017-05-31 宇龙计算机通信科技(深圳)有限公司 A kind of harassing call treating method and apparatus
CN107343088A (en) * 2017-06-21 2017-11-10 深圳传音通讯有限公司 The information protecting method and mobile terminal of mobile terminal
CN108551530A (en) * 2018-07-05 2018-09-18 奇酷互联网络科技(深圳)有限公司 Call processing method, device, readable storage medium storing program for executing and mobile terminal

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030010213A (en) * 2001-07-26 2003-02-05 삼성전자주식회사 Method for controlling volume of wireless headset in portable phone onboard bluetooth
US20080056243A1 (en) * 2003-02-11 2008-03-06 Roy Radhika R Access independent common architecture for real-time communications services for networking environments
US9497304B1 (en) * 2007-06-07 2016-11-15 West Corporation Method and apparatus for voice recognition unit simulation
CN101924811A (en) * 2010-06-25 2010-12-22 康佳集团股份有限公司 Mobile phone with auto-answer function and auto-answer method for mobile phone
CN103391372A (en) * 2013-07-31 2013-11-13 广东欧珀移动通信有限公司 Intelligent conversation time reminding method and intelligent conversation time reminding device
CN104038648A (en) * 2014-06-06 2014-09-10 陈伟 Method and device for recognizing crank calls
CN106791231A (en) * 2016-11-30 2017-05-31 宇龙计算机通信科技(深圳)有限公司 A kind of harassing call treating method and apparatus
CN107343088A (en) * 2017-06-21 2017-11-10 深圳传音通讯有限公司 The information protecting method and mobile terminal of mobile terminal
CN108551530A (en) * 2018-07-05 2018-09-18 奇酷互联网络科技(深圳)有限公司 Call processing method, device, readable storage medium storing program for executing and mobile terminal

Also Published As

Publication number Publication date
CN110933222B (en) 2022-05-10

Similar Documents

Publication Publication Date Title
CN111399709B (en) Message reminding method and device, electronic equipment and storage medium
US11444895B2 (en) Session message sticking method and device
US9799080B2 (en) Method and apparatus for providing a contact address
US9594496B2 (en) Method and apparatus for playing IM message
CN106055246B (en) A kind of mobile terminal and its operating method
KR101706359B1 (en) Method and device for controlling background application
CN107911798B (en) Message pushing method and device and terminal
CN107390997B (en) Application program switching method and device
CN109245997B (en) Voice message playing method and device
US20180352398A1 (en) Method, Device And User Equipment For Pushing Service Information
US20140378104A1 (en) Method and device for processing short messages
CN106792892B (en) Access control method and device for application program
CN110945467B (en) Disturbance-free method and terminal
US9906471B1 (en) System, device, and method for managing composition of electronic messages using temporary suspensions
CN112445832B (en) Data anomaly detection method and device, electronic equipment and storage medium
CN111787152A (en) Address list calling method of mobile terminal and mobile terminal thereof
CN112866022B (en) Method, device and medium for reducing system breakdown times of modem
CN113934331B (en) Information processing method, device and storage medium
CN110933222B (en) Call control method, device, equipment and computer readable medium
CN109586951B (en) Method, device, electronic equipment and readable storage medium for implementing fault transfer
CN112788691B (en) Method, device and storage medium for controlling network connection
CN111757040B (en) Communication method and device
CN112083841B (en) Information input method, device and storage medium
CN107889062B (en) Offline positioning data learning method and device
CN112073308A (en) Information pushing method, device, equipment and computer readable storage medium

Legal Events

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