CN102710842B - Method and device for processing incoming calls of Android platform mobile terminal - Google Patents
Method and device for processing incoming calls of Android platform mobile terminal Download PDFInfo
- Publication number
- CN102710842B CN102710842B CN201210169262.1A CN201210169262A CN102710842B CN 102710842 B CN102710842 B CN 102710842B CN 201210169262 A CN201210169262 A CN 201210169262A CN 102710842 B CN102710842 B CN 102710842B
- Authority
- CN
- China
- Prior art keywords
- incoming call
- caller
- access request
- layer
- processing unit
- 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.)
- Active
Links
Landscapes
- Telephone Function (AREA)
Abstract
The invention discloses a method and a device for processing incoming calls of an Android platform mobile terminal, which are used for avoiding misjudgments or erroneous judgments caused by directly rejecting answering or answering an incoming call after the number of the incoming call fails to be acquired for the first time and improving the accuracy and the success rate of rejecting answering the incoming call. The method comprises the following steps: triggering start to acquire the incoming call number by a Framework layer of an Android platform according to an incoming call state change event acquired from an RIL (recombinant inbred line) layer, wherein the incoming call state change event is generated after an access request of the incoming call is received by the RIL layer; after the Framework layer fails to acquire the incoming call number for the first time, at least starting to acquire the incoming call number for a second time by the Framework layer; and operating the access request of the incoming call by an application layer according to an acquisition result.
Description
Technical field
The present invention relates to communication technical field, particularly relate to a kind of Android platform mobile terminal call processing method and device.
Background technology
Along with developing rapidly of intelligent mobile terminal, Android platform is one of Mainstream Platform becoming intelligent mobile terminal, and firewall for received calls is one of function becoming intelligent mobile terminal indispensability gradually also.
In prior art, when realizing firewall for received calls function, being generally arrange based on user, namely pre-setting by user the caller ID that the caller ID that allows to answer and refusal answer.After mobile terminal bottom receives the incoming call access request of portable phone number, report to firewall for received calls, in this firewall for received calls, obtain the telephone number carried in incoming call access request, this telephone number is mated with the refusing incoming call list of numbers that user pre-sets, judge in the refusing incoming call list of numbers that user pre-sets, whether to there is the telephone number carried in incoming call access request, when there is the telephone number carried in incoming call access request in the refusing incoming call list of numbers determining to pre-set, this incoming call access request of rejection.
But, under cdma network, due to network reason, time network first time reports incoming message, the telephone number carried in the incoming message reported is for empty, now, adopt the mobile terminal of Android platform effectively to judge, can only process according to default setting, namely when default setting is the incoming call of answering non-portable phone number in reporting message, answer this incoming call, and when default setting is the incoming call of non-portable phone number in rejection reporting message, this incoming call of rejection.
This just may cause erroneous judgement or misjudgement, to needing the incoming call of answering to carry out rejection, and to needing the incoming call of rejection to answer, thus reducing success rate and the accuracy rate of refusing incoming call, reducing efficiency, also reducing Consumer's Experience.
Summary of the invention
The invention provides a kind of Android platform mobile terminal call processing method and device, in order to avoid after once obtaining caller ID failure directly rejection or to answer the erroneous judgement or misjudgement that this incoming call causes, improve accuracy rate and the success rate of refusing incoming call.
The concrete technical scheme that the embodiment of the present invention provides is as follows:
A kind of Android platform mobile terminal call processing method, comprising:
The framework Framework layer of Android platform changes event and triggers to start according to the electricity condition that comes obtained from wireless access RIL layer and obtain caller ID, described come electricity condition to change event be that described RIL layer generates after the described incoming call access request of reception;
Described Framework layer, after first time obtains the failure of described caller ID, at least again starts and obtains described caller ID;
Application layer operates described incoming call access request according to acquisition result.
A kind of incoming call handling device, is arranged in Android platform mobile terminal, comprises:
First processing unit, for changing event and trigger to start according to the electricity condition that comes obtained from wireless access RIL layer and obtain caller ID, described come electricity condition to change event be described RIL layer generates after the described incoming call access request of reception;
Second processing unit, after obtaining the failure of described caller ID in first time, at least again starts and obtains described caller ID;
3rd processing unit, for operating described incoming call access request according to acquisition result.
Based on technique scheme, in the embodiment of the present invention, adopt in the mobile terminal of Android platform, the ccf layer of Android platform changes event triggering startup acquisition caller ID according to the electricity condition that comes obtained from radio access layer, this carrys out electricity condition change event is that RIL layer generates after reception incoming call access request, ccf layer is after first time obtains caller ID failure, at least again start and obtain caller ID, after repeatedly obtaining the process of caller ID, incoming call access request is operated according to acquisition result by application layer again, namely this incoming call access request of rejection is determined whether according to acquisition result, thus effectively prevent and obtain the acquisition result of caller ID by single and determine whether the erroneous judgement that this incoming call of rejection causes or misjudgement, improve the success rate obtaining caller ID, and then improve accuracy rate and the success rate of refusing incoming call.
Accompanying drawing explanation
Fig. 1 is incoming call handling method flow diagram under Android platform in the embodiment of the present invention;
Fig. 2 is the complete procedure schematic diagram of incoming call handling under Android platform in the embodiment of the present invention;
Fig. 3 is incoming call handling apparatus structure schematic diagram in the embodiment of the present invention.
Embodiment
In order to avoid directly rejection or answer the erroneous judgement or misjudgement that this incoming call causes after once obtaining caller ID failure, improve accuracy rate and the success rate of refusing incoming call, embodiments provide a kind of Android platform mobile terminal call processing method and device.
Below in conjunction with accompanying drawing, the preferred embodiment of the present invention is described in detail.
As shown in Figure 1, in the embodiment of the present invention, the concrete grammar flow process based on the mobile terminal incoming call handling of Android platform is as follows:
Framework (Framework) layer of step 101:Android platform is according to from wireless access (RadioInterface Layer, RIL) electricity condition that comes of layer acquisition changes event triggering startup acquisition caller ID, and this carrys out electricity condition change event is that RIL layer generates after access request is sent a telegram here in reception.
Wherein, RIL layer is that encapsulate in Android platform, relevant to wireless traffic level of abstraction.
Such as, in Android platform, RIL layer after receiving incoming call access request message, to Framework(framework) layer reports EVENT_CALL_STATE_CHANGE, EVENT_CALL_STATE_CHANGE is used to indicate electricity condition and changes, and triggers Framework layer and obtains caller ID.
Particularly, the Framework layer of Android platform obtains caller ID from the modulator-demodulator (modem) of mobile terminal bottom.
Such as, in Android platform, Framework layer passes through the modem inquiry incoming call specifying information of instruction CLCC to bottom of standard.
Step 102:Framework layer, after first time obtains caller ID failure, at least again starts and obtains caller ID.
Preferably, Framework layer, after first time obtains caller ID failure, again starts the number of times obtaining caller ID and is no more than setting threshold.Such as, Framework layer is after first time obtains caller ID failure, and the number of times again obtaining caller ID is no more than 3 times.
Preferably, adjacent twice startup of Framework layer obtains the time interval of caller ID for setting duration.
Such as, Framework layer is after this obtains caller ID failure, and 500 milliseconds, interval starts acquisition caller ID again.
Particularly, Framework layer, after first time obtains caller ID failure, inquires about incoming call specifying information again every setting duration, until determine get caller ID or until determine that obtaining number of times reaches setting threshold.If Framework layer, when inquiry times reaches setting threshold, does not also obtain caller ID, then determined to answer this incoming call access request or this incoming call access request of rejection according to default setting by application layer.
Such as, after the failure of Framework layer first time acquisition caller ID, 500 milliseconds, interval afterwards second time obtains caller ID; If determine, second time gets caller ID, then judged whether to need this incoming call access request of rejection according to this caller ID by application layer; Otherwise when determining that the number of times of repeated obtain does not reach the threshold value 2 of setting, third time obtains caller ID afterwards at 500 milliseconds, interval; If third time gets caller ID, then judged whether to need this incoming call access request of rejection according to this caller ID by application layer; Otherwise, determine that the number of times of repeated obtain reaches the threshold value 2 of setting, then answered the incoming call access request of unknown incoming call number by application layer according to default setting, or according to the incoming call access request of default setting rejection unknown incoming call number.
Wherein, the empirical value that scheduled duration and setting threshold can experimentally be determined, not with above-mentioned 500 milliseconds, 2 times for restrictive condition.
Particularly, Framework layer is determining that incoming call physical connection has been set up and after being in electricity condition, judged whether to get caller ID.
Step 103: application layer operates incoming call access request according to acquisition result.
Particularly, when application layer is determined to get caller ID according to acquisition result, when determining that this caller ID does not belong in the scope of answering according to the number filtering condition preset, this incoming call access request of rejection, otherwise, answer this incoming call access request; When determining not get caller ID according to acquisition result, according to default setting rejection or the incoming call access request of answering unknown incoming call number.
Particularly, the number filtering condition of user's setting can be determine this incoming call access request of rejection when caller ID belongs to default refusing incoming call list (as blacklist), also can be determine this incoming call access request of rejection when caller ID does not belong to default incoming call list (as white list), also can be determine this incoming call access request of rejection when the value of assigned address belongs to setting range in caller ID.Such as, if rear four then these incoming call access requests of rejection in [1100,1199] scope of caller ID.Be only citing herein, in practical application, number filter condition is not limited in above several, can be applied to number filtering condition setting mode of the present invention the present invention also included for other.
Such as, in Android platform, application layer obtains caller ID from the electrical connection event of newly arriving (EVENT_NEW_RINGING_CONNECTION) that Framework layer reports, this caller ID is compared one by one with the refusing incoming call number comprised in the blacklist preset, if caller ID is present in this blacklist, then this incoming call access request of rejection.
Be illustrated below in conjunction with the whole process of accompanying drawing 2 to the mobile terminal refusing incoming call adopting Android platform:
The electricity condition that comes that step 201:RIL layer reception bottom reports changes event EVENT_CALL_STATE_CHANGE;
According to EVENT_CALL_STATE_CHANGE, step 202:Framework layer determines that carrying out electricity condition changes;
Step 203:Framework layer obtains caller ID from the modem of bottom;
Step 204:Framework layer judges whether the physical connection of sending a telegram here has been set up and be in electricity condition, if not, perform step 205, otherwise, perform step 206;
Step 205: the processing procedure performing other talking state (as activated or hold mode);
Step 206:Framework layer judges whether to get caller ID, if so, performs step 208, otherwise, perform step 207;
Whether the number of times that step 207:Framework layer obtains caller ID is greater than 2, if not, turn and go to perform step 203, otherwise perform step 213;
Step 208:Framework layer reports EVENT_NEW_RINGING_CONNECTION to application layer, wherein carries caller ID;
Step 209: application layer obtains caller ID from EVENT_NEW_RINGING_CONNECTION.
Step 210: application layer according to the number filtering condition judgment preset whether this incoming call access request of rejection, if perform step 211, otherwise, perform step 212;
Step 211: this incoming call access request of application layer rejection;
Step 212: application layer answers this incoming call access request;
Step 213: application layer is according to the incoming call access request of default setting rejection unknown incoming call number.
Based on above-mentioned principle, as shown in Figure 3, a kind of incoming call handling device is additionally provided in the embodiment of the present invention, be arranged in the mobile terminal adopting Android platform, it is similar to said method that it realizes principle, something in common see the description in said method, can repeat no more herein, and this device mainly comprises following processing unit:
First processing unit 301, for obtaining caller ID according to the electricity condition change event triggering startup that comes from the acquisition of RIL layer, this carrys out electricity condition change event is that RIL layer generates after receiving access request of sending a telegram here;
Second processing unit 302, after obtaining caller ID failure in first time, at least again starts and obtains caller ID;
3rd processing unit 303, for really operating incoming call access request according to acquisition result.
Wherein, when the 3rd processing unit 303 is specifically for determining to get caller ID according to acquisition result, when not belonging in the scope of answering according to the number filtering condition determination caller ID preset, this incoming call access request of rejection, otherwise, answer this incoming call access request;
When determining not get caller ID according to acquisition result, according to default setting rejection or the incoming call access request of answering unknown incoming call number.
Wherein, the second processing unit 302, specifically for after the failure of acquisition caller ID, again starts the number of times obtaining caller ID and is no more than setting threshold.
Wherein, the second processing unit 302 obtains the time interval of caller ID for setting duration specifically for adjacent twice startup.
Wherein, the first processing unit 301 or the second processing unit 302 are specifically for obtaining caller ID when obtaining caller ID from the modulator-demodulator of mobile terminal bottom.
Based on technique scheme, in the embodiment of the present invention, adopt in the mobile terminal of Android platform, the ccf layer of Android platform changes event triggering startup acquisition caller ID according to the electricity condition that comes obtained from radio access layer, this carrys out electricity condition change event is that RIL layer generates after reception incoming call access request, ccf layer is after first time obtains caller ID failure, at least again start and obtain caller ID, after repeatedly obtaining the process of caller ID, incoming call access request is operated according to acquisition result by application layer again, namely this incoming call access request of rejection is determined whether according to acquisition result, thus effectively prevent and obtain the acquisition result of caller ID by single and determine whether the erroneous judgement that this incoming call of rejection causes or misjudgement, improve the success rate obtaining caller ID, and then improve accuracy rate and the success rate of refusing incoming call.
Obviously, those skilled in the art can carry out various change and modification to the present invention and not depart from the spirit and scope of the present invention.Like this, if these amendments of the present invention and modification belong within the scope of the claims in the present invention and equivalent technologies thereof, then the present invention is also intended to comprise these change and modification.
Claims (10)
1. an Android platform mobile terminal call processing method, is characterized in that, comprising:
The framework Framework layer of Android platform changes event and triggers to start according to the electricity condition that comes obtained from wireless access RIL layer and obtain caller ID, described come electricity condition to change event be that described RIL layer generates after the described incoming call access request of reception;
Described Framework layer, after first time obtains the failure of described caller ID, at least again starts and obtains described caller ID;
Application layer operates described incoming call access request according to acquisition result.
2. the method for claim 1, is characterized in that, described application layer operates described incoming call access request according to acquisition result, comprising:
When described application layer is determined to get described caller ID according to described acquisition result, when determining that described caller ID does not belong in the scope of answering according to the number filtering condition preset, access request of sending a telegram here described in rejection, otherwise, answer described incoming call access request;
When described application layer is determined not get described caller ID according to described acquisition result, according to default setting rejection or the incoming call access request of answering unknown incoming call number.
3. method as claimed in claim 1 or 2, is characterized in that, after described Framework layer obtains the failure of described caller ID, again starts the number of times obtaining described caller ID and is no more than setting threshold.
4. method as claimed in claim 3, is characterized in that, the time interval of the described caller ID of adjacent twice acquisition is setting duration.
5. method as claimed in claim 1 or 2, is characterized in that, obtain described caller ID and be specially:
The described Framework layer of Android platform obtains described caller ID from the modulator-demodulator of mobile terminal bottom.
6. an incoming call handling device, is arranged in Android platform mobile terminal, it is characterized in that, comprising:
First processing unit, for changing event and trigger to start according to the electricity condition that comes obtained from wireless access RIL layer and obtain caller ID, described come electricity condition to change event be described RIL layer generates after the described incoming call access request of reception;
Second processing unit, after obtaining the failure of described caller ID in first time, at least again starts and obtains described caller ID;
3rd processing unit, for operating described incoming call access request according to acquisition result.
7. device as claimed in claim 6, it is characterized in that, when described 3rd processing unit is specifically for determining to get described caller ID according to described acquisition result, when determining that described caller ID does not belong in the scope of answering according to the number filtering condition preset, to send a telegram here described in rejection access request, otherwise, answer described incoming call access request;
When determining not get described caller ID according to described acquisition result, according to default setting rejection or the incoming call access request of answering unknown incoming call number.
8. device as claimed in claims 6 or 7, is characterized in that, described second processing unit, specifically for after obtaining the failure of described caller ID, again starts the number of times obtaining described caller ID and is no more than setting threshold.
9. device as claimed in claim 8, is characterized in that, described second processing unit is setting duration specifically for the time interval of the described caller ID of adjacent twice acquisition.
10. device as claimed in claims 6 or 7, is characterized in that, described first processing unit or described second processing unit are specifically for obtaining described caller ID when obtaining caller ID from the modulator-demodulator of mobile terminal bottom.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210169262.1A CN102710842B (en) | 2012-05-28 | 2012-05-28 | Method and device for processing incoming calls of Android platform mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210169262.1A CN102710842B (en) | 2012-05-28 | 2012-05-28 | Method and device for processing incoming calls of Android platform mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102710842A CN102710842A (en) | 2012-10-03 |
| CN102710842B true CN102710842B (en) | 2015-02-18 |
Family
ID=46903385
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210169262.1A Active CN102710842B (en) | 2012-05-28 | 2012-05-28 | Method and device for processing incoming calls of Android platform mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102710842B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103002446B (en) * | 2012-11-15 | 2016-02-17 | 广东欧珀移动通信有限公司 | A kind of method and apparatus of call interceptor |
| CN106067919B (en) * | 2016-06-13 | 2019-03-01 | 珠海市魅族科技有限公司 | A kind of method and device intercepting incoming call |
| CN107172265A (en) * | 2017-05-12 | 2017-09-15 | 北京安云世纪科技有限公司 | A kind of call blocking method, device and mobile terminal |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101026645A (en) * | 2006-02-18 | 2007-08-29 | 三星电子株式会社 | Device and method for detecting telephone number information from digital multimedia broadcasting |
| CN101257669A (en) * | 2007-03-02 | 2008-09-03 | 英华达（南京）科技有限公司 | Method for managing incoming call of communicating terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3613822B2 (en) * | 1994-11-17 | 2005-01-26 | ブラザー工業株式会社 | Telephone equipment |
-
2012
- 2012-05-28 CN CN201210169262.1A patent/CN102710842B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101026645A (en) * | 2006-02-18 | 2007-08-29 | 三星电子株式会社 | Device and method for detecting telephone number information from digital multimedia broadcasting |
| CN101257669A (en) * | 2007-03-02 | 2008-09-03 | 英华达（南京）科技有限公司 | Method for managing incoming call of communicating terminal |
Non-Patent Citations (1)
| Title |
|---|
| Android平台手机来电及短信防火墙关键技术研究;孟小华等;《2010 The 3rd International Conference on Power Electronics and Intelligent Transportation System (PEITS 2010)》;20101231;3.2节、图2、图3、图4 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102710842A (en) | 2012-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101072441B (en) | Calling information processing method and device based on dual-card dual-standby service | |
| CN104767893A (en) | Crank call interception method and system | |
| CN104080065A (en) | Method and device of automatic redial of call | |
| CN101227511A (en) | Terminal and method for recognizing and controlling nuisance call | |
| RU2429589C2 (en) | Method of detecting fraud during roaming connections in mobile communication networks | |
| CN103647871B (en) | A kind of automatic prompting processing method based on mobile terminal and system | |
| CN103167451A (en) | Method and mobile terminal capable of achieving no disturbing | |
| CN102843661B (en) | Emergency contact method and communication terminal | |
| CN105101071A (en) | Terminal positioning method and device, and terminal | |
| CN102710842B (en) | Method and device for processing incoming calls of Android platform mobile terminal | |
| CN104717378B (en) | Call transferring method and device | |
| US20080214141A1 (en) | System and method for allowing callback on an emergency call | |
| CN103491501A (en) | One-key rescuing service system and method | |
| CN110113791A (en) | Mobile terminal and its method for falling cell after rise | |
| US20100144390A1 (en) | Dialing device for mobile phone and method for using the same | |
| CN104602361A (en) | Method for expanding wireless network service of mobile phone by WiFi (wireless fidelity) network | |
| CN101848447B (en) | Call processing method and device in communication process | |
| CN102652437B (en) | Method and device for controlling called call of mobile terminal | |
| CN104602214A (en) | Expansion method of wireless voice and short message service of mobile phone | |
| CN105991837A (en) | Prompting method and device and terminal | |
| WO2010104887A3 (en) | Who-called system for detecting and reporting slamdown calls in a mobile network | |
| CN102421076A (en) | Malicious incoming call processing method, device and terminal | |
| CN101572890A (en) | Method for detecting illegal group calling party and device thereof | |
| CN101621776B (en) | Method for realizing cross-network starting reminding service | |
| CN105227780B (en) | Processing incoming call and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |