Prosecution Insights
Last updated: August 06, 2026
Application No. 18/726,220

Methods, Systems and Computer Program Products for Optimizing Identification of Communication Device Based Spamming

Final Rejection §103§112
Filed
Jul 02, 2024
Priority
Jan 03, 2022 — IN 202211000188 +1 more
Examiner
MCBETH, WILLIAM C
Art Unit
2449
Tech Center
2400 — Computer Networks
Assignee
Truecaller International LLP
OA Round
2 (Final)
67%
Grant Probability
Favorable
3-4
OA Rounds
6m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 67% — above average
67%
Career Allowance Rate
197 granted / 294 resolved
+9.0% vs TC avg
Strong +57% interview lift
Without
With
+57.1%
Interview Lift
resolved cases with interview
Typical timeline
2y 8m
Avg Prosecution
21 currently pending
Career history
315
Total Applications
across all art units

Statute-Specific Performance

§101
9.2%
-30.8% vs TC avg
§103
49.7%
+9.7% vs TC avg
§102
5.7%
-34.3% vs TC avg
§112
30.7%
-9.3% vs TC avg
Black line = Tech Center average estimate • Based on career data from 294 resolved cases

Office Action

§103 §112
DETAILED ACTION The amendment to Application Ser. No. 18/726,220 filed on April 6, 2025, has been entered. Claims 1-4, 6, 7, 9-12, 14, 15 and 17 are currently amended. Claims 1-17 are pending and are examined. Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. Examiner’s Note While Claim 16 is indicated in the remarks as being amended, Claim 16 is provided with the status identifier “Original” and no markups indicating changes to the claim text are shown. As the text in line 1 has changed from “as claimed in claim 1” to “as claimed in claim 9”, Claim 16 is treated as “Currently Amended”. Response to Arguments The amendment to Claims 3 and 11 has overcome the objection to the claims for minor informalities set forth in the Non-Final Office Action mailed November 4, 2025. The objection to the claims for minor informalities is hereby withdrawn. The amendment to Claims 2, 3, 6, 7, 10, 11 and 14-16 has overcome the rejection of Claims 2, 3, 6, 7, 10, 11 and 14-16 under 35 U.S.C. 112(b) as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or joint inventor regards as the invention set forth in the Non-Final Office Action mailed November 4, 2025. The rejection of Claims 2, 3, 6, 7, 10, 11 and 14-16 under 35 U.S.C. 112(b) is hereby withdrawn. However, the rejection of Claims 4 and 12 under 35 U.S.C. 112(b) is maintained for the reasons set forth below in this Office Action. The amendment to Claims 1, 9, and 17 has overcome the rejection of Claims 1-17 under 35 U.S.C. 103 set forth in the Non-Final Office Action mailed November 4, 2025. New grounds of rejection under 35 U.S.C. 103, necessitated by the amendment, are set forth in this Office Action. Claim Rejections - 35 USC § 112(b) The following is a quotation of 35 U.S.C. 112(b): (b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention. Claims 4 and 12 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention. Claim 4 recites the limitation “the second telephony device is a communication device having one or both of voice calling based communication capability, text message based communication capability, as well as data network based communication capability” in lines 5-7. It is unclear which of “voice calling based communication capability, text message based communication capability, and data network based communication capability” the word “both” is referencing, rendering the claim indefinite. For examination purposes, the clause “one or both of voice calling based communication capability, text message based communication capability, as well as data network based communication capability (emphasis added)” is interpreted as “one or both of voice calling based communication capability and text message based communication capability, as well as data network based communication capability”. Insofar as it recites similar claim elements, Claim 12 is rejected for substantially the same reasons presented above with respect to Claim 4. Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 1-6, 8-14, 16 and 17 are rejected under 35 U.S.C. 103 as being unpatentable over Trivi et al., Pub. No. US 2011/0294478 A1, hereby “Trivi”, in view of Dutkevic et al., Pub. No. US 2018/0288221 A1, hereby “Dutkevic” and in further view of Murynets et al., Pub. No. US 2014/0004892 A1, hereby “Murynets”. Regarding Claim 1, Trivi discloses “A communication origination categorization server configured for generating communication origination categorization decisions corresponding to one or more telephony devices (Trivi fig. 11 and paragraphs 1 and 124: spam-classification server system 1108 for performing telephone caller classification), the server comprising: a memory (Trivi fig. 12 and paragraphs 136-139: memory 1204, storage device 1206); a network transceiver (Trivi fig. 12 and paragraph 140: low-speed expansion port 1214, which may be a wired or wireless network adapter); and a processor (Trivi fig. 12 and paragraphs 136-139: processor 1202) configured to implement the steps of: identifying a number for a communication origination categorization decision, wherein the identified number is associated with a first telephony device that has initiated a communication with a second telephony device (Trivi figs. 5 and 11 and paragraphs 78-79 and 124-126: server system 1108 receives a request to determine whether the telephone number of telephone 1110 is a spam telephone number from mobile telephone 1112); identifying application user feedback information associated with the identified number (Trivi figs. 5, 7, 8 and 11 and paragraphs 73-76, 80, 95, 100-101 and 126: the telephone number of telephone 1110 is referenced against telephone numbers that have been identified as sources of spam by subscribers 1104 to the spam identification service);” and “generating a communication origination categorization decision... (Trivi figs. 5, 7, 8 and 11 and paragraphs 80, 95, 100, 111-112 and 126-127: telephone spam determination unit 1118 of server system 1108 makes a determination that the telephone number of the calling device is a source of spam); and transmitting to the second telephony device, the communication origination categorization decision (Trivi figs. 5 and 11 and paragraphs 81 and 127: server system 1108 transmits an indication that the telephone number is a source of spam to mobile telephone 1112).” However, while Trivi discloses making a determination that the telephone number of the calling device is a source of spam based on feedback received from the community of mobile telephone users (Trivi paragraphs 80, 95, 100, 111-112 and 126-127), Trivi does not explicitly disclose “identifying at least one of calling behavior information associated with the identified number and messaging behavior information associated with the identified number; generating a communication origination categorization decision based on at least one or both of the identified calling behavior information and the identified messaging behavior information (emphasis added)”. In the same field of endeavor, Dutkevic discloses “identifying application user feedback information associated with the identified number (Dutkevic figs. 1-3 and paragraphs 22 and 26: classifier 204 of analytic engine obtains feedback information associated with the phone number from end users); identifying at least one of calling behavior information associated with the identified number and messaging behavior information associated with the identified number (Dutkevic figs. 1-3 and paragraphs 21-22 and 27: classifier 204 of analytic engine determines caller behavior using aggregated call data associated with the phone number obtained from call log collector 202); generating a communication origination categorization decision based on at least one or both of the identified calling behavior information and the identified messaging behavior information (Dutkevic figs. 1-3 and paragraphs 22 and 26-30: classifier 204 identifies the phone number as being associated with a spam caller based on the feedback information and the determined caller behavior)”. It would have been obvious to one of ordinary skill in the art at the time of the effective filing to modify the server of Trivi to make the determination that the phone number is a source of spam based on caller behavior as taught by Dutkevic. One of ordinary skill in the art would have been motivated to combine making the determination that the phone number is a source of spam based on caller behavior to improve detection of a newly rising spammer telephone number (Dutkevic paragraph 32). However, while Trivi discloses that an incoming telephone number may be classified as a source of spam based on feedback from a set of users from a community that subscribe to the spam identification service and have downloaded a particular application (Trivi paragraphs 100-101), the combination of Trivi and Dutkevic does not explicitly disclose “wherein: the identified calling behavior information comprises a number of incoming calls to the first telephony device, from communication devices that implement instances of a software application configured to communicate with the communication origination categorization server; and the identified messaging behavior information comprises a number of incoming message based communications received at the first telephony device, from communication devices that implement instances of a software application configured to communicate with the communication origination categorization server.” In the same field of endeavor, Murynets discloses classifying a particular device or account associated with an identifier, e.g., an IP address, IMEI or MEID, as a source of spam based in part on the number of incoming messages (Murynets figs. 3 and 4 and paragraphs 41-42, 55-57 and 62: “The average number of incoming SMS messages of node 7, in conjunction with the information on the average number of SMS messages sent per day in node 1 is indicative of whether or not a source is a potential SMS spammer.”). It would have been obvious to one of ordinary skill in the art at the time of the effective filing to modify the server of Trivi, as modified by Dutkevic, to make the determination that the phone number is a source of spam based on caller behavior including a number of incoming calls or messages to the phone number as taught by Murynets because doing so constitutes applying a known technique (classifying a device or account as a source of spam based in part on a number of incoming messages) to known devices and/or methods (a spam-classification server system) ready for improvement to yield predictable and desirable results (making the determination that the telephone number is a source of spam based in part on the number of incoming messages). See KSR International Co. v. Teleflex Inc., 82 USPQ2d 1385 (U.S. 2007). Regarding Claim 2, the combination of Trivi, Dutkevic and Murynets discloses all of the limitations of Claim 1. Additionally, Trivi discloses “wherein generating the communication origination categorization decision is also based on the identified application user feedback information (Trivi figs. 5, 8 and 11 and paragraphs 72, 80, 100, 111-112 and 126-127: telephone spam determination unit 1118 makes the determination that the telephone number is a source of spam based on classification of the telephone number as being associated with spam by subscribers 1104 to the spam identification service).” Regarding Claim 3, the combination of Trivi, Dutkevic and Murynets discloses all of the limitations of Claim 1. Additionally, Trivi discloses “wherein generating the communication origination categorization decision comprises:” and “generating the communication origination categorization decision based on the generated communication organization categorization prediction and one or more whitelists or blacklists (Trivi fig. 7 and paragraphs 91-95: the telephone number is flagged as spam based on the determination made based on the crowd-sourced classification and on a white list defined by the user of mobile telephone 1112).” However, while Trivi discloses flagging the telephone number as spam based on a determination made based on classification of the telephone number as being associated with spam by the community of mobile telephone users and a white list defined by the user of the mobile telephone (Trivi paragraphs 91-95), Trivi does not explicitly disclose “generating a communication origination categorization decision based on at least one or both of the identified calling behavior information and the identified messaging behavior information”. In the same field of endeavor, Dutkevic discloses “generating a communication origination categorization prediction based on at least one or both of the identified calling behavior information and the identified messaging behavior information (Dutkevic figs. 1-3 and paragraphs 22 and 26-30: classifier 204 identifies the phone number as being associated with a spam caller based on the feedback information and the determined caller behavior).” It would have been obvious to one of ordinary skill in the art at the time of the effective filing to modify the server of Trivi to make the determination that the phone number is a source of spam based on caller behavior as taught by Dutkevic for the reasons set forth in the rejection of Claim 1. Regarding Claim 4, the combination of Trivi, Dutkevic and Murynets discloses all of the limitations of Claim 1. Additionally, Trivi discloses wherein “the first telephony device is a communication device having one or both of voice calling based communication capability and text message based communication capability (Trivi fig. 11 and paragraphs 124-125: calling device 1110 may be a computerized bulk dialing device capable of initiating telephone calls); and the second telephony device is a communication device having one or both of voice calling based communication capability, text message based communication capability, as well as data network based communication capability, wherein said second telephony device is configured for data network based communication with the communication origination categorization server (Trivi fig. 11 and paragraphs 124-127: mobile telephone 1112 is capable of receiving telephone calls and communicating with server system 1108).” Regarding Claim 5, the combination of Trivi, Dutkevic and Murynets discloses all of the limitations of Claim 1. Additionally, Trivi discloses “wherein the application user feedback information is retrieved from a database communicably coupled with the communication origination categorization server (Trivi figs. 5, 8 and 11 and paragraphs 36, 72-76, 90, 100-101 and 130: the telephone number of calling device is referenced against telephone numbers that have been identified as sources of spam by subscribers 1104 to spam identification service stored in repository 1132 which is accessible to server system 1108), and the application user feedback information comprises information corresponding to one or more of: a number of requests that have been received over a defined period for blocking the first telephony device or for blocking a number associated with the first telephony device, wherein said requests have been received from communication devices that implement instances of a software application configured to communicate with the communication origination categorization server (Trivi figs. 5, 6, 8 and 11 and paragraphs 36-38, 55, 72-76, 88-90 and 100-101: the spam identification service maintains a statistical dataset that includes the number of times each telephone number was classified as spam by subscribers to the spam identification service, said classification as spam resulting in blocking of telephone calls received from the telephone number [see Fig. 6 steps 608 and 610], wherein subscribers have downloaded and installed an application that enables communication with the spam identification service – while not explicitly stated, it is inferred that the statistical dataset comprises the number of times each telephone number was classified as spam since the creation of the dataset, which constitutes “a defined period” in accordance with paragraph [0054] of the specification)”. Regarding Claim 6, the combination of Trivi, Dutkevic and Murynets discloses all of the limitations of Claim 1. Additionally, Dutkevic discloses “wherein the communication origination categorization server is configured to retrieve calling behavior information from a database communicably coupled with the communication origination categorization server (Dutkevic fig. 2 and paragraphs 20-22: classifier 204 obtains the aggregated call data associated with the phone number from call log collector 202), and wherein the retrieved calling behavior information comprises information corresponding to one or more of: call duration information for outgoing calls from the first telephony device (Dutkevic paragraph 21: aggregated call data associated with the phone number includes call duration of calls made by the phone number)”. It would have been obvious to one of ordinary skill in the art at the time of the effective filing to modify the server of Trivi to make the determination that the phone number is a source of spam based on caller behavior as taught by Dutkevic for the reasons set forth in the rejection of Claim 1. Regarding Claim 8, the combination of Trivi, Dutkevic and Murynets discloses all of the limitations of Claim 1. Claim 1 is directed towards a communication origination categorization server. The combination of Trivi, Dutkevic and Murynets anticipates the limitations of Claim 8 as functions “the second telephony device is configured for” are outside the scope of “the communication origination categorization server” of Claim 1. Insofar as it recites similar claim elements, Claim 9 is rejected for substantially the same reasons presented above with respect to Claim 1. Additionally, Trivi discloses “A method for generating communication origination categorization decisions corresponding to one or more telephony devices, comprising implementing at a communication origination categorization server... (Trivi figs. 5 and 11 and paragraphs 1, 72 and 124: a method for performing telephone caller classification implemented by spam-classification server system 1108)”. Insofar as it recites similar claim elements, Claim 10 is rejected for substantially the same reasons presented above with respect to Claim 2. Insofar as it recites similar claim elements, Claim 11 is rejected for substantially the same reasons presented above with respect to Claim 3. Insofar as it recites similar claim elements, Claim 12 is rejected for substantially the same reasons presented above with respect to Claim 4. Insofar as it recites similar claim elements, Claim 13 is rejected for substantially the same reasons presented above with respect to Claim 5. Insofar as it recites similar claim elements, Claim 14 is rejected for substantially the same reasons presented above with respect to Claim 6. Regarding Claim 16, the combination of Trivi, Dutkevic and Murynets discloses all of the limitations of Claim 9. Claim 9 is directed towards a method for generating communication origination categorization decisions implemented at a communication origination categorization server. The combination of Trivi, Dutkevic and Murynets anticipates the limitations of Claim 16 as functions “the second telephony device is configured for” are outside the scope of the method implemented by “a communication origination categorization server” of Claim 9. Insofar as it recites similar claim elements, Claim 17 is rejected for substantially the same reasons presented above with respect to Claim 1. Additionally, Trivi discloses “A computer program product for generating communication origination categorization decisions corresponding to one or more telephony devices, the computer program product comprising a non-transitory computer readable medium having a computer readable program code embodied therein, wherein the computer readable program code comprises instructions for implementing within a processor based computing system... (Trivi fig. 5 and paragraphs 1, 72, 136 and 139: a computer program product comprising a machine-readable medium storing instructions for performing telephone caller classification)”. Claims 7 and 15 are rejected under 35 U.S.C. 103 as being unpatentable over the combination of Trivi, Dutkevic and Murynets in view of Bobotek, Pub. No. US 2012/0030293 A1. Regarding Claim 7, the combination of Trivi, Dutkevic and Murynets discloses all of the limitations of Claim 1. However, while Trivi suggests that the spam-classification server system may be applied to classification of sources of text message spamming (Trivi paragraph 132), and Dutkevic discloses obtaining aggregated call data associated with the phone number from a call log collector (Dutkevic paragraphs 20-22), the combination of Trivi and Dutkevic does not explicitly disclose “wherein the communication origination categorization server is configured to retrieve the messaging behavior information from a database communicably coupled with the communication origination categorization server, and wherein the messaging behavior information comprises information corresponding to one or more of...”. In the same field of endeavor, Bobotek discloses “wherein the communication origination categorization server is configured to retrieve the messaging behavior information from a database communicably coupled with the communication origination categorization server (Bobotek fig. 2 and paragraphs 108, 117 and 167: message abuse detector component (MADC) 206 accesses information related to mobile messaging associated with an originating address, i.e., messaging behavior information, from repository 226), wherein the messaging behavior information comprises information corresponding to one or more of: whether the identified number associated with the first telephony device is a short code based number... (Bobotek fig. 2 and paragraphs 108, 113, 131 and 167: information related to mobile messaging associated with an originating address can identify whether the originating address is a short code address, i.e., a 5-number originating address)”. It would have been obvious to one of ordinary skill in the art at the time of the effective filing to modify the server of Trivi, as modified by Dutkevic and Murynets, to retrieve information related to mobile messaging associated with the telephone number from a database as taught by Bobotek because doing so constitutes applying a known technique (retrieving mobile messaging information associated with an originating address) to known devices and/or methods (a spam-classification server system) ready for improvement to yield predictable and desirable results (making the determination that the telephone number is a source of spam based in part on the mobile messaging information associated with the telephone number). See KSR International Co. v. Teleflex Inc., 82 USPQ2d 1385 (U.S. 2007). Insofar as it recites similar claim elements, Claim 15 is rejected for substantially the same reasons presented above with respect to Claim 7. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure: Quilici et al., Pub. No. US 2016/0309024 A1, discloses a method and system for identifying an unwanted caller wherein a calling party is classified as source of unwanted calls based in part on call patterns derived from call information received from application-enabled mobile phones; Wang et al., the paper titled “Voice spam detecting technique based on user behavior pattern model”, discloses a method for detecting unsolicited communication callers based on call behavior patterns that include the ratio of outgoing calls made by a user and the number of calls received by the user; Warshaw, Pub. No. US 2020/0374251 A1, discloses a technique for processing intra and inter-messaging platform communications wherein a risk rating indicating the likelihood a particular message device identifier is a source of spam is assigned based in part on the number of sent messages vs number of received messages; and Zaki et al., Pub. No. US 2022/0053092 A1, discloses a system and method for telephone call regulation wherein a predictive model executing on a server classifies a phone number received from an application running on user device as spam based in part on spam factors that include frequency of calls for each telephone number during a certain period of time. Applicant's amendment necessitated the new ground(s) of rejection presented in this Office Action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to WILLIAM C MCBETH whose telephone number is (571)270-0495. The examiner can normally be reached on Monday - Friday, 8:00AM - 4:30PM ET. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Vivek Srivastava can be reached on 571-272-7304. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /WILLIAM C MCBETH/Examiner, Art Unit 2449 /VIVEK SRIVASTAVA/Supervisory Patent Examiner, Art Unit 2449
Read full office action

Prosecution Timeline

Jul 02, 2024
Application Filed
Nov 04, 2025
Non-Final Rejection mailed — §103, §112
Apr 06, 2026
Response Filed
Jul 01, 2026
Final Rejection mailed — §103, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12689683
CONTENT MANAGEMENT AND DELIVERY FOR A COMMUNICATION CHANNEL
2y 11m to grant Granted Jul 21, 2026
Patent 12676769
METHOD AND APPARATUS FOR ESTABLISHING CONNECTION, STORAGE MEDIUM AND SERVER
2y 8m to grant Granted Jul 07, 2026
Patent 12665821
SYSTEM AND METHOD TO DETERMINE CRITICALITY AND PRIORITIZE LIVE EVENTS TO IMPROVE PROACTIVE CUSTOMER SERVICE
3y 0m to grant Granted Jun 23, 2026
Patent 12659290
DOMAIN NAME SYSTEM QUERY HANDLING FOR AN EDGE APPLICATION SERVICE
2y 9m to grant Granted Jun 16, 2026
Patent 12652265
Application-Agnostic Puncturing of Network Address Translation (NAT) Services
2y 1m to grant Granted Jun 09, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
67%
Grant Probability
99%
With Interview (+57.1%)
2y 8m (~6m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 294 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month