CN111698652A - Incoming call processing method and device, host equipment and storage medium - Google Patents

Abstract

The embodiment of the application discloses a method and a device for processing an incoming call, a host device and a storage medium, wherein the method comprises the following steps: the host equipment receives an incoming call request, wherein the incoming call request carries a called number; the host equipment determines whether the called number is bound with an account corresponding to one or more sub-equipment in at least two sub-equipment; if the called number is bound with a plurality of sub-machines in at least two sub-machines, the host machine device pushes the incoming call request to each sub-machine in the plurality of sub-machines. The embodiment of the application can support the conversation requirements of a plurality of users through one mobile terminal.

Description

Incoming call processing method, device, host device and storage medium

technical field

The present application relates to the field of communication technologies, and in particular, to a method, an apparatus, a host device, and a storage medium for processing an incoming call.

Background technique

At present, mobile terminals such as mobile phones support single-card or dual-card, only one address book, and only one user.

SUMMARY OF THE INVENTION

The embodiments of the present application provide an incoming call processing method, device, host device and storage medium, which can support the call requirements of multiple users through one mobile terminal.

In a first aspect, an embodiment of the present application provides a method for processing an incoming call. The method is applied to a mobile terminal. The mobile terminal includes a host device and at least two slave devices that are communicatively connected to the host device. The method include:

The host device receives an incoming call request, and the incoming call request carries the called number;

determining, by the host device, whether the called number is bound to an account corresponding to one or more sub-devices in the at least two sub-devices;

If the called number is bound to multiple slave devices in the at least two slave devices, the host device pushes the incoming call request to each slave device in the multiple slave devices.

Optionally, before the host device pushes the incoming call request to each of the multiple slave devices, the method further includes:

If the calling number is not in the historical call records of the account corresponding to any one of the multiple slave devices, the host device determines whether the calling number is located in any of the at least two slave devices. In the blacklist or harassment flag list of the account corresponding to a slave device;

If not, the host device pushes the incoming call request to each slave device in the plurality of slave devices.

Optionally, if yes, the host device refuses to push the incoming call request.

In a second aspect, an embodiment of the present application provides an apparatus for processing an incoming call. The apparatus is applied to a host device of a mobile terminal, where the mobile terminal includes the host device and at least two sub-devices that are communicatively connected to the host device. machine equipment, the apparatus includes a processing unit and a communication unit, wherein:

the communication unit, configured to receive an incoming call request, where the incoming call request carries the called number;

the processing unit, configured to determine whether the called number is bound to an account corresponding to one or more of the at least two slave devices;

The communication unit is further configured to push the incoming call request to each of the multiple slave devices when it is determined that the called number is bound to multiple slave devices in the at least two slave devices. machine equipment.

Optionally, the processing unit is further configured to determine whether the calling number is not in the historical call records of the account corresponding to any one of the multiple slave devices. be located in the blacklist or harassment marked list of the account corresponding to any one of the at least two slave devices;

The communication unit is further configured to push the incoming call request when the calling number is not located in the blacklist or harassment marked list of the account corresponding to any one of the at least two slave devices. to each slave device in the plurality of slave devices;

Optionally, the communication unit is further configured to refuse to send the calling number to the blacklist or the harassment marked list of the account corresponding to any one of the at least two slave devices. Any one of the slave devices in at least two own devices pushes the incoming call request.

In a third aspect, an embodiment of the present application provides a host device, including a processor and a memory, where the memory is configured to store one or more programs, the one or more programs are configured to be executed by the processor, and the above The program includes instructions for performing the steps in the first aspect of the embodiments of the present application.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute the computer program as described in the first embodiment of the present application. Some or all of the steps described in an aspect.

In a fifth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute as implemented in the present application. Examples include some or all of the steps described in the first aspect. The computer program product may be a software installation package.

It can be seen that, in the method for processing an incoming call described in the embodiment of the present application, the host device receives an incoming call request, and the incoming call request carries the called number; the host device determines whether the called number is related to one of the at least two slave devices or The accounts corresponding to multiple slave devices are bound; if the called number is bound to multiple slave devices in the at least two slave devices, the host device pushes the incoming call request to each slave device in the multiple slave devices. The host device in the embodiment of the present application can push incoming call requests to at least two slave devices, at least two slave devices can correspond to at least two users, and one mobile terminal can support the call requirements of multiple users.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1a is a schematic diagram of a system architecture disclosed in an embodiment of the present application;

FIG. 1b is an example diagram of a signal interaction between a host device and a slave device disclosed in an embodiment of the present application;

FIG. 1c is another example diagram of signal interaction between a host device and a slave device disclosed in an embodiment of the present application;

FIG. 1d is another example diagram of signal interaction between a host device and a slave device disclosed in an embodiment of the present application;

FIG. 1e is another example diagram of signal interaction between a host device and a slave device disclosed in an embodiment of the present application;

1f is another example diagram of signal interaction between a host device and a slave device disclosed in an embodiment of the present application;

2 is a schematic flowchart of a method for processing an incoming call disclosed in an embodiment of the present application;

3 is a schematic flowchart of another method for processing an incoming call disclosed in an embodiment of the present application;

4 is a schematic flowchart of another method for processing an incoming call disclosed in an embodiment of the present application;

5 is a schematic flowchart of creating an address book between a slave device and a host device disclosed in an embodiment of the present application;

6 is a schematic structural diagram of an apparatus for processing an incoming call disclosed in an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a host device disclosed in an embodiment of the present application.

Detailed ways

In order to make those skilled in the art better understand the solutions of the present invention, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only These are some embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The terms "first", "second" and the like in the description and claims of the present invention and the above drawings are used to distinguish different objects, rather than to describe a specific order. Furthermore, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes unlisted steps or units, or optionally also includes For other steps or units inherent to these processes, methods, products or devices.

Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor a separate or alternative embodiment that is mutually exclusive of other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

The embodiments of the present application will be described in detail below.

Please refer to FIG. 1a. FIG. 1a is a schematic diagram of a system architecture disclosed in an embodiment of the present application. The system architecture 100 includes a host device 110 and at least two slave devices 120. The host device 110 is connected to each slave device 120 in communication. The host device 110 has cellular communication capability; the host device and the at least two slave devices can be combined into a detachable mobile terminal. The host device 110 involved in the embodiments of the present application may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless modems, and various forms of user equipment ( User Equipment (UE), mobile station (Mobile Station, MS), terminal device (terminal device) and so on. The slave device may include an audio unit and a display unit (eg, a display), responsible for presenting audio content, video content, etc. to the user, and completing functions such as user interaction. The host device is responsible for processing and control, and has remote communication capabilities. The slave device and the host device can be connected through low-power short-range wireless communication (eg, Bluetooth wireless communication, infrared wireless communication, wireless local area network communication, etc.). The following describes an example of the internal architecture of the host device and the slave device and the communication mode between them. Because the host device can communicate with two or more slave devices at the same time. For the communication mode between the host device and a plurality of slave devices, refer to the communication mode between the host device and one slave device. For ease of understanding, the following FIGS. 1 b to 1 f are all described by taking one slave device as an example.

Please refer to FIG. 1b. FIG. 1b is a diagram illustrating an example of signal interaction between a host device and a slave device disclosed in an embodiment of the present application. As shown in Figure 1b, the host device includes a wireless modem module, a host main controller, and a wireless transceiver module; the sub device includes a sub main controller, a sub microphone, a sub handset, and a wireless transceiver with the host device. The sub-machine wireless transceiver module that the module can communicate with. The host device and the slave device are detachably mechanically connected. During a voice call, when the uplink signal is sent, the audio signal from the handset's microphone is processed by the handset's main controller and sent to the host device by the handset's wireless transceiver module. The main controller transmits it to the wireless modulation and demodulation module, which is modulated by the wireless modulation and demodulation module and sent to the air. When the downlink signal is received, the signal from the air is demodulated by the wireless modulation and demodulation module, and then modulated by the wireless transceiver module of the host, and then transmitted to the slave. The audio signal demodulated by the wireless transceiver module of the slave is sent to the slave. Under the control of the main controller, it is output by the handset of the handset.

Please refer to FIG. 1c. FIG. 1c is another example diagram of signal interaction between a host device and a slave device disclosed in an embodiment of the present application. As shown in Figure 1c, the host device includes a wireless modem module, a host main controller, and a wireless transceiver module; the sub-machine device includes a sub-machine keyboard and a sub-machine display. The host device and the slave device are detachably mechanically connected. When the uplink signal is sent, the control command input from the keyboard of the slave is modulated by the wireless transceiver module of the slave, and then sent to the wireless transceiver module of the host device. sent into the air. When the downlink signal is received, the control signal from the air is modulated by the wireless transceiver module through the main controller of the host and sent to the slave.

Please refer to FIG. 1d. FIG. 1d is another example diagram of signal interaction between a host device and a slave device disclosed in an embodiment of the present application. As shown in Figure 1d, the host device includes a wireless modem module, a host main controller, and a wireless transceiver module; the sub-device includes a sub-machine main controller, a sub-machine microphone, a sub-machine earpiece, and a wireless transceiver capable of communicating with the host. The sub-machine wireless transceiver module and sub-machine audio codec for module communication. During the voice call, when the uplink signal is sent, the audio signal from the handset microphone is encoded by the handset audio codec and transmitted to the handset main controller. Under the control of the handset master controller, the handset wirelessly sends and receives After the module is sent out, it is received by the wireless transceiver module of the host device, and then sent to the wireless modulation and demodulation module under the control of the host's main controller, and then sent to the air after being modulated by the wireless modulation and demodulation module. When the downlink signal is received, the signal from the air is demodulated by the wireless modulation and demodulation module and transmitted to the host main controller. Under the control of the host main controller, it is transmitted to the wireless transceiver module of the host device. After the wireless transceiver module is modulated, it is sent to the slave device, and the audio signal demodulated by the slave wireless transceiver module is decoded by the slave audio codec under the control of the slave main controller, and then output by the slave handset.

Please refer to FIG. 1e. FIG. 1e is another example diagram of signal interaction between a host device and a slave device disclosed in an embodiment of the present application. As shown in Figure 1e, the host device includes a wireless modem module, a host main controller, and a wireless transceiver module; the sub-machine device includes a sub-machine main controller, and a sub-machine wireless transceiver module capable of communicating with the host's wireless transceiver module. ; The slave device can access the communication network through the host device.

Please refer to FIG. 1f. FIG. 1f is another example diagram of signal interaction between a host device and a slave device disclosed in an embodiment of the present application. As shown in Fig. 1f, the host device includes a host first wireless communication module, a host main controller, and a host second wireless communication module; the sub device includes a sub main controller, a sub first wireless communication module, and the sub device The first wireless communication module of the host can communicate with the first wireless communication module of the host; the second wireless communication module of the host can communicate with the base station (BaseStation).

It should be noted that the above-mentioned forms and functions of the host device and the slave device are only examples, and are not uniquely limited here.

Please refer to FIG. 2. FIG. 2 is a schematic flowchart of an incoming call processing method disclosed by an embodiment of the present application. As shown in FIG. 2, the incoming call processing method includes the following steps.

201. The host device receives an incoming call request, where the incoming call request carries the called number.

In this embodiment of the present application, when the host device is separated from the at least two slave devices, it becomes a split device, and the host device can be connected with the at least two slave devices through low-power short-range wireless communication, which is suitable for use by multiple users , which can meet the scenarios of multi-user use. For example, a scenario where multiple users use multiple slave devices to make calls and surf the Internet. Specifically, it can be used in home usage scenarios, conference usage scenarios, and the like. Of course, the host device can also be mechanically connected in a detachable manner with at least two slave devices to form an integrated mobile terminal, which is suitable for use by a user and is convenient for the user to carry.

In a scenario where multiple slave devices answer the phone, the host device is responsible for signal interaction with the base station. The slave device performs signal interaction with the base station through the host device. Each slave device can be bound to an account for one user to use. When using the slave device, the user can log in by entering the account number and password on the slave device, or by means of fingerprint unlocking, face 2D unlocking, face 3D unlocking, iris recognition unlocking, password unlocking, etc. After successful login, the user can use the handset device to make voice calls, video calls, and video content playback. Each slave device can support a single subscriber identification module (Subscriber Identification Module, SIM) SIM card or dual SIM cards. Among them, a SIM card can be bound to only one sub-device, and can also be bound to two or more sub-devices at the same time. Since one host device can communicate with multiple slave devices, when the host device receives an incoming call request, the host device determines which SIM card the incoming call request is for according to the called number carried in the incoming call request.

202. The host device determines whether the called number is bound to an account corresponding to one or more slave devices in the at least two slave devices.

203. If the called number is bound to multiple slave devices of the at least two slave devices, the host device pushes the incoming call request to each slave device of the multiple slave devices.

In the embodiment of the present application, the host device may create an address book management library, and the address book management library includes sub-machine accounts, one or two SIM card numbers bound to each sub-machine account, and each SIM card number corresponds to an address book . Specifically, as shown in Table 1, Table 1 is a schematic table of an address book management library disclosed in an embodiment of the present application.

Table 1

As shown in Table 1, Table 1 takes two slave devices as an example for description. The account Zhang San in Table 1 corresponds to the slave device 1, and the account Zhang San is bound with two SIM card numbers (150XXXXXXXX and 153XXXXXXXX). The address book corresponding to the SIM card number 150XXXXXXXX is the first and second. The address book corresponding to the SIM card number 153XXXXXXXX is the third and fourth. The account Li Si in Table 1 corresponds to the slave device 2, and the account Li Si is bound with a SIM card number (150XXXXXXXX). The address book corresponding to the SIM card number 150XXXXXXXX is the third and fifth.

If the called number is 150XXXXXXXX, since the called number is bound to both slave devices (slave device 1 and slave device 2), the host device pushes the incoming call request to slave device 1 and slave device 2.

Optionally, in an embodiment, after the slave device 1 and the slave device 2 receive the incoming call request, the display screen of the slave device 1 and the slave device 2 may display the incoming call information, and the user of the slave device 1 and the slave device 2 can display the incoming call information. The user of the slave device 2 can choose whether to connect or not. After the first connected slave device between the user of the slave device 1 and the user of the slave device 2 is connected, the other slave device will automatically hang up. This solution is suitable for one-to-one call scenarios.

Optionally, in another embodiment, after the slave device 1 and the slave device 2 receive the incoming call request, the display screen of the slave device 1 and the slave device 2 may display the incoming call information, and the user of the slave device 1 can display the incoming call information. The user of the slave device 2 and the user of the slave device 2 can choose whether to connect or not. After the user of the slave device 1 and the user of the slave device 2 are connected first, the other slave device will not hang up. After another slave device is connected, three-party or more than three-party conference calls can be conducted. This solution is suitable for three-party or more than three-party conference call scenarios.

Optionally, if the called number is not bound to the accounts corresponding to the at least two slave devices, the host device pushes the incoming call request to each of the at least two slave devices.

In the embodiment of this application, if the called number is not bound to the accounts corresponding to at least two slave devices, it may be that although a SIM card is inserted into a certain slave device, the slave device is bound with the SIM card number. The relationship is not updated to the address book management library of the host device, so the host device cannot know whether the SIM card number is bound to the slave device. Therefore, the host device pushes the incoming call request to all the slave devices. The embodiment of the present application can prevent the slave device from missing an incoming call when the data in the address book management library of the host device is not updated in time.

In a possible implementation manner, if the called number is not bound to the accounts corresponding to at least two slave devices, the host device does not perform any push. This situation may be due to the host device being crossed or the calling user dialing the wrong number.

Optionally, if the called number is bound to the third slave device in the at least two slave devices, the host device pushes the incoming call request to the third slave device, and the third slave device is one of the at least two slave devices. any one of .

In this embodiment of the present application, if the called number is bound to one of the at least two slave devices, it is directly pushed to the slave device bound to it. For example, the called number is bound to the third slave device in the at least two slave devices, and the host device pushes the incoming call request to the third slave device.

In the embodiment of this application, the host device receives an incoming call request, and the incoming call request carries the called number; the host device determines whether the called number is bound to an account corresponding to one or more of the at least two sub-devices; The calling number is bound to multiple slave devices in the at least two slave devices, and the host device pushes the incoming call request to each slave device in the multiple slave devices. The host device in the embodiment of the present application can push incoming call requests to at least two slave devices, at least two slave devices can correspond to at least two users, and one mobile terminal can support the call requirements of multiple users.

Please refer to FIG. 3. FIG. 3 is a schematic flowchart of another method for processing an incoming call disclosed in an embodiment of the present application. FIG. 3 is obtained by further optimization on the basis of FIG. 2. As shown in FIG. 3, the incoming call The processing method includes the following steps.

301. The host device receives an incoming call request, where the incoming call request carries the called number and the calling number.

302. The host device determines whether the called number is bound to an account corresponding to one or more slave devices in the at least two slave devices.

For the specific implementation of steps 301 to 302 in this embodiment of the present application, reference may be made to steps 201 to 202 shown in FIG. 2 , and details are not repeated here.

303. If the called number is bound to multiple slave devices in the at least two slave devices, the host device determines whether the calling number exists in the address book of the account corresponding to each slave device in the multiple slave devices.

304. If there is, the host device pushes the incoming call request to each of the multiple slave devices.

In the embodiment of the present application, the host device can determine whether the calling number exists in the address books of at least a plurality of slave devices bound to the called number through the address book management library. If both exist, the host device pushes the incoming call request to each of the multiple slave devices. so that each of the multiple slave devices can make a call.

Optionally, if the calling number is in the address book of the account corresponding to the first slave device among the multiple slave devices, the host device pushes the incoming call request to the first slave device, and the first slave device is a plurality of slave devices. any one of the machine equipment.

Table 1 is used as an example for description below. If the host number in the incoming call request is the number corresponding to the contact’s second child, the host device pushes the incoming call request to the slave device 1 bound to the account Zhang San and the account number. The slave device 2 bound by Li Si. If the host number in the incoming call request is the number corresponding to the old one of the contact, the host device pushes the incoming call request to the slave device 1 bound to the account Zhang San. If the host number in the incoming call request is the number corresponding to the contact number 5, the host device pushes the incoming call request to the slave device 2 bound to the account Li Si. If the host number in the incoming call request is the number corresponding to the contact number seven, it means that the number corresponding to the contact number seven is neither in the address book corresponding to the SIM card 150XXXXXXXX bound to the handset device 1, nor in the phone number corresponding to the handset device 1. 2. In the address book corresponding to the bound SIM card 150XXXXXXXX, it is assumed that the number corresponding to the contact’s old seventh is an unfamiliar number in the above two address books. In order to avoid missed calls, the host device will request the incoming call Push to the slave device 1 bound to the account Zhang San and the slave device 2 bound to the account Li Si. In this embodiment of the present application, when an unfamiliar call comes in, the unfamiliar call can be pushed to all the slave devices bound to the called number.

Optionally, the method shown in FIG. 3 may further include the following steps:

(11) If the calling number is not in the address book of the account corresponding to any one of the multiple slave devices, the host device determines whether the calling number exists in the call history corresponding to any one of the multiple slave devices. middle;

(12) if the calling number is in the historical call record of the second sub-machine device, the host device sends the incoming call request to the second sub-machine device, and the second sub-machine device is any one of the plurality of sub-machine devices;

(13) If the calling number is not in the historical call records of the account corresponding to any one of the multiple slave devices, the host device pushes the incoming call request to each of the multiple slave devices.

In the embodiment of the present application, the SIM card number bound to each slave device not only has an address book, but also has a history call record with the SIM card number, and both the address book and the history call record can be stored in the address book management library middle. Each slave device can upload the address book of the SIM card number bound to it to the host device for management. When the address book of the SIM card number bound to it in each slave device is changed, each slave device can Update the changed address book to the address book management library of the host device. When the call record of the SIM card number bound to each slave device is updated, the historical call record of the SIM card number bound to it can also be updated to the address book management library of the host device.

When the host device determines that the calling number is not in the address book of the account corresponding to any one of the multiple slave devices, it determines whether the calling number exists in the historical call records corresponding to any one of the multiple slave devices. , if the calling number is in one of the multiple slave devices, such as in the historical call record of the second slave device, it indicates that the calling number has a history call record with the second slave device , it is considered that the calling number with a larger number may be willing to talk with the second slave device. The embodiment of the present application can accurately determine the slave device that the incoming call requests to access according to the address book and the call record, thereby improving the efficiency of connecting incoming calls to the split device.

If the calling number is not in the historical call records of the account corresponding to any one of the multiple slave devices, in order to avoid missed calls, the host device pushes the incoming call request to each of the multiple slave devices. machine equipment.

Optionally, in the above (13), before the host device pushes the incoming call request to each slave device in the multiple slave devices, the following steps may also be performed:

(21) If the calling number is not in the historical call records of the account corresponding to any one of the multiple slave devices, the host device determines whether the calling number is located in any one of the above at least two slave devices corresponding to any one of the slave devices. the account's blacklist or harassment flag list;

(22) If not, the host device pushes the incoming call request to each of the multiple slave devices.

Optionally, if yes, the host device refuses to push the incoming call request.

In the embodiment of the present application, when an unfamiliar incoming call calls, if the unfamiliar incoming call neither belongs to a contact in the address book nor has a history call record, but the calling number of the unfamiliar incoming call is on the blacklist of other handset devices Or the harassment mark list, the host device can refuse to push the incoming call request, so as to avoid the harassment of the user of the slave device by the unfamiliar number. Since the host device can communicate with multiple slave devices, the host device can intercept the harassing calls according to the data in the address book management library, which can greatly improve the success rate of intercepting the harassing calls.

The host device in the embodiment of the present application can push incoming call requests to at least two slave devices, at least two slave devices can correspond to at least two users, and one mobile terminal can support the call requirements of multiple users. It can also avoid the occurrence of missed calls, and improve the success rate of nuisance call interception through the host device.

Please refer to FIG. 4. FIG. 4 is a schematic flowchart of another method for processing an incoming call disclosed in an embodiment of the present application. FIG. 4 is obtained by further optimization on the basis of FIG. 3. As shown in FIG. 4, the incoming call The processing method includes the following steps.

401. The host device receives the first address book sent by the first slave device, and binds the first address book with the user identity SIM card number of the account corresponding to the first slave device.

402. The host device receives and stores the first call record corresponding to the called number sent by the first slave device.

In the embodiment of the present application, when a new slave device is added, the slave device will report various information of itself, including the SIM card number bound to the slave device, the address book and call records corresponding to the SIM card number. , blacklist, etc. The host device can receive the first address book sent by the first slave device, bind the first address book with the SIM card number of the user identity of the account corresponding to the first slave device, and store it in the address book management library. The host device may receive the first call record corresponding to the called number sent by the first slave device, and store the first call record in the address book management library. Before performing steps 401 and 402, the host device may create an address book management library.

The execution order of step 401 and step 402 is not limited, and step 401 may be executed before step 402, or step 402 may be executed before step 401, or step 401 and step 402 may be executed simultaneously.

Optionally, after step 401 and step 402 are performed, the host device may periodically pull various information updated by each sub-device from each sub-device, including updated contacts, call records, newly added blacklists, and the like. If any slave device has information updated, it will actively upload the updated information to the host device for comprehensive management by the host device.

For example, please refer to FIG. 5 . FIG. 5 is a schematic flowchart of creating an address book between a slave device and a host device according to an embodiment of the present application. As shown in Figure 5, the host device can perform long-distance communication with the remote base station, and the host device can also perform low-power short-distance wireless communication with the slave device 1 and the slave device 2. The slave device 1 and the slave device 2 can Create a personal account, enter your personal identity information, bind your SIM card number, and create a personal address book. The slave device 1 and the slave device 2 may share data with the personal address book created by each of them and the address book management library created by the host device.

403. The host device receives an incoming call request, where the incoming call request carries the called number and the calling number.

404. The host device determines whether the called number is bound to an account corresponding to one or more slave devices in the at least two slave devices.

405. If the called number is bound to multiple slave devices in the at least two slave devices, the host device determines whether the calling number exists in the address book of the account corresponding to each slave device in the multiple slave devices.

406. If there is, the host device pushes the incoming call request to each of the multiple slave devices.

For specific embodiments of steps 403 to 406 in this embodiment of the present application, reference may be made to steps 301 to 304 shown in FIG. 3 , and details are not repeated here.

The host device in the embodiment of the present application can push incoming call requests to at least two slave devices, at least two slave devices can correspond to at least two users, and one mobile terminal can support the call requirements of multiple users. The slave device can actively upload the updated information to the host device, so that the host device can perform comprehensive management and improve the data management of the host device.

The foregoing mainly introduces the solutions of the embodiments of the present application from the perspective of the method-side execution process. It can be understood that, in order to implement the above-mentioned functions, the mobile terminal includes corresponding hardware structures and/or software modules for executing each function. Those skilled in the art should easily realize that the present invention can be implemented in hardware or a combination of hardware and computer software in conjunction with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

In this embodiment of the present application, the mobile terminal may be divided into functional units according to the foregoing method examples. For example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units. It should be noted that the division of units in the embodiments of the present application is schematic, and is only a logical function division, and other division methods may be used in actual implementation.

Please refer to FIG. 6. FIG. 6 is a schematic structural diagram of an apparatus for processing an incoming call disclosed in an embodiment of the present application. The apparatus is applied to a host device of a mobile terminal, and the mobile terminal includes a host device and at least two slave devices that are communicatively connected to the host device. For the mobile terminal, reference may be made to the system architecture shown in FIG. 1a. As shown in FIG. 6 , the apparatus 600 for processing an incoming call includes a processing unit 601 and a communication unit 602, wherein:

The communication unit 602 is configured to receive an incoming call request, where the incoming call request carries the called number;

The processing unit 601 is configured to determine whether the called number is bound to an account corresponding to one or more slave devices in the at least two slave devices;

The communication unit 602 is further configured to push the incoming call request to each of the multiple slave devices when it is determined that the called number is bound to multiple slave devices in the at least two slave devices. sub-machine equipment.

Optionally, the incoming call request also carries a calling number, and the processing unit 601 is further configured to push the incoming call request to each sub-device in the plurality of sub-devices in the communication unit 602 Before, judging whether the calling number exists in the address book of the account corresponding to each slave device in the plurality of slave devices;

The communication unit 602 is further configured to push the incoming call request to the multiple slave devices when the calling number exists in the address book of the account corresponding to each slave device in the multiple slave devices Each slave device in the device.

Optionally, the communication unit 602 is further configured to push the incoming call request when the calling number is in the address book of the account corresponding to the first slave device among the multiple slave devices. For the first sub-machine device, the first sub-machine device is any one of the plurality of sub-machine devices.

Optionally, the processing unit 601 is further configured to determine whether the calling number is not in the address book of the account corresponding to any one of the multiple slave devices. exists in the call record corresponding to any one of the multiple slave devices;

The communication unit 602 is further configured to send the incoming call request to the second slave device when the calling number is in the call record of the second slave device, and the second slave device The device is any one of the multiple sub-machine devices;

The communication unit 602 is further configured to push the incoming call request to the multiple slave devices when the calling number is not in the call record of the account corresponding to any one of the multiple slave devices. each of the slave devices.

Optionally, the communication unit 602 is further configured to push the incoming call request to the at least two slave devices when the called number is not bound to the accounts corresponding to the at least two slave devices. each of the slave devices.

Optionally, the communication unit 602 is further configured to push the incoming call request to the said at least two slave devices when the called number is bound to a third slave device in the at least two slave devices. A third sub-machine device, where the third sub-machine device is any one of the at least two sub-machine devices.

Optionally, the communication unit 602 is further configured to receive the first address book sent by the first slave device;

The processing unit 601 is further configured to bind the first address book with the user identification SIM card number of the account corresponding to the first slave device.

Optionally, the communication unit 602 is further configured to receive and store the first call record corresponding to the called number sent by the first slave device.

Optionally, the communication unit 602 is further configured to receive and store the first blacklist corresponding to the called number sent by the first slave device.

Optionally, the processing unit 601 is further configured to periodically pull various information updated by each sub-device from each sub-device, including the updated address book, the call record, and the newly added blacklist.

Optionally, the processing unit 601 is further configured to determine whether the calling number is located in at least two of the above-mentioned calling numbers under the condition that the calling number is not in the historical call records of the account corresponding to any one of the multiple slave devices. In the blacklist or harassment flag list of the account corresponding to any one of the slave devices;

The communication unit 602 is further configured to push the incoming call request to a plurality of sub-devices when the calling number is not located in the blacklist or harassment marked list of the account corresponding to any one of the above-mentioned at least two sub-devices. each slave device in the host device;

Optionally, the communication unit 602 is further configured to refuse to call any sub-device in the case that the calling number is located in the blacklist or the harassment-marked list of the account corresponding to any one of the above-mentioned at least two sub-devices. The mobile device pushes the incoming call request.

The apparatus 600 for processing an incoming call further includes a storage unit 603, the processing unit 601 may be a processor, the communication unit 602 may be a communication interface, and the storage unit 603 may be a memory.

The processing apparatus for an incoming call shown in FIG. 6 is implemented, and the apparatus for processing an incoming call can push an incoming call request to at least two sub-devices, and the at least two sub-devices can correspond to at least two users, and can support multiple devices through one mobile terminal. the calling needs of each user.

Please refer to FIG. 7 , which is a schematic structural diagram of a host device disclosed in an embodiment of the present application. As shown in FIG. 7 , the host device 700 includes a processor 701 and a memory 702, wherein the host device 700 may further include a bus 703, the processor 701 and the memory 702 may be connected to each other through the bus 703, and the bus 703 may be an interconnection of peripheral components. Connect standard (Peripheral Component Interconnect, referred to as PCI) bus or Extended Industry Standard Architecture (Extended Industry Standard Architecture, referred to as EISA) bus and so on. The bus 703 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 7, but it does not mean that there is only one bus or one type of bus. The host device 700 may further include an input/output device 704, and the input/output device 704 may include a display screen, such as a liquid crystal display screen. The memory 702 is used to store one or more programs containing instructions; the processor 701 is used to invoke the instructions stored in the memory 702 to execute some or all of the method steps in the above-mentioned FIGS. 2 to 4 .

Implement the host device shown in FIG. 7 , the host device can push incoming call requests to at least two slave devices, at least two slave devices can correspond to at least two users, and one mobile terminal can support the call requirements of multiple users.

Embodiments of the present application further provide a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program enables the computer to execute any method for processing an incoming call as described in the above method embodiments some or all of the steps.

Embodiments of the present application further provide a computer program product, the computer program product including a non-transitory computer-readable storage medium storing a computer program, the computer program being operable to cause a computer to execute any one of the method embodiments described above Some or all of the steps of a method of handling an incoming call.

It should be noted that, for the sake of simple description, the foregoing method embodiments are all expressed as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence. As in accordance with the present invention, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or Integration into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a computer-readable memory. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, Several instructions are included to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable memory, and the memory can include: a flash disk , Read-only memory (English: Read-Only Memory, referred to as: ROM), random access device (English: Random Access Memory, referred to as: RAM), magnetic disk or optical disk, etc.

The embodiments of the present application have been introduced in detail above, and specific examples are used to illustrate the principles and implementations of the present invention. The descriptions of the above embodiments are only used to help understand the methods and core ideas of the present invention; at the same time, for Persons of ordinary skill in the art, according to the idea of the present invention, will have changes in the specific embodiments and application scope. To sum up, the contents of this specification should not be construed as limiting the present invention.

Claims (11)

1. A method for processing an incoming call, wherein the method is applied to a mobile terminal, and the mobile terminal comprises a host device and at least two slave devices communicatively connected to the host device, the method comprising: The host device receives an incoming call request, and the incoming call request carries the called number; determining, by the host device, whether the called number is bound to an account corresponding to one or more sub-devices in the at least two sub-devices; If the called number is bound to multiple slave devices in the at least two slave devices, the host device pushes the incoming call request to each slave device in the multiple slave devices. 2 . The method according to claim 1 , wherein the incoming call request further carries a calling number, and the host device pushes the incoming call request to each sub-machine device in the plurality of sub-machine devices. 3 . Before, the method further includes: The host device determines whether the calling number exists in the address book of the account corresponding to each sub-machine device in the plurality of sub-machine devices; If there is, the host device performs the step of pushing the incoming call request to each of the sub-devices in the plurality of sub-devices. 3. The method according to claim 2, wherein the method further comprises: If the calling number is in the address book of the account corresponding to the first slave device among the multiple slave devices, the host device pushes the incoming call request to the first slave device, and the host device pushes the incoming call request to the first slave device. The first sub-machine device is any one of the plurality of sub-machine devices. 4. The method according to claim 2, wherein the method further comprises: If the calling number is not in the address book of the account corresponding to any one of the multiple slave devices, the host device determines whether the calling number exists in any one of the multiple slave devices In the call record corresponding to the mobile device; If the calling number is in the call record of the second slave device, the host device sends the incoming call request to the second slave device, and the second slave device is the multiple slave devices any one of the devices; If the calling number is not in the call record of the account corresponding to any one of the multiple slave devices, the host device executes the process of pushing the incoming call request to the multiple slave devices. steps for each slave device. 5. The method according to any one of claims 1 to 4, wherein the method further comprises: If the called number and the accounts corresponding to the at least two slave devices are not bound, the host device pushes the incoming call request to each slave device in the at least two slave devices. 6. The method according to any one of claims 1 to 4, wherein the method further comprises: If the called number is bound to a third slave device among the at least two slave devices, the host device pushes the incoming call request to the third slave device, and the third slave device The device is any one of the at least two sub-machine devices. 7. The method according to claim 3, wherein before the host device receives an incoming call request, the method further comprises: The host device receives the first address book sent by the first slave device, and binds the first address book with the user identity identification SIM card number of the account corresponding to the first slave device. 8. The method according to claim 3, wherein the method further comprises: The host device receives and stores the first call record corresponding to the called number sent by the first slave device. 9. An apparatus for processing incoming calls, wherein the apparatus is applied to a host device of a mobile terminal, and the mobile terminal includes the host device and at least two slave devices that are communicatively connected to the host device, and The device includes a processing unit and a communication unit, wherein: the communication unit, configured to receive an incoming call request, where the incoming call request carries the called number; the processing unit, configured to determine whether the called number is bound to an account corresponding to one or more of the at least two slave devices; The communication unit is further configured to push the incoming call request to each of the multiple slave devices when it is determined that the called number is bound to multiple slave devices in the at least two slave devices. machine equipment. 10. A host device, comprising a processor and a memory, the memory being used to store one or more programs, the one or more programs being configured to be executed by the processor, the programs comprising for carrying out the method of any one of claims 1-8. 11. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program for electronic data exchange, wherein the computer program causes a computer to execute the computer program according to any one of claims 1 to 8 method described.

Images