Prosecution Insights
Last updated: October 04, 2026
Application No. 18/508,374

SYSTEM AND METHOD FOR A CONNECTOR APPLICATION TO CAUSE AN ACTION TO BE EXECUTED BY A PUBLIC SAFETY DEVICE

Non-Final OA §103
Filed
Nov 14, 2023
Examiner
TORRES, MARCOS L
Art Unit
2647
Tech Center
2600 — Communications
Assignee
Motorola Solutions Inc.
OA Round
1 (Non-Final)
68%
Grant Probability
Favorable
1-2
OA Rounds
6m
Est. Remaining
78%
With Interview

Examiner Intelligence

Grants 68% — above average
68%
Career Allowance Rate
479 granted / 709 resolved
+5.6% vs TC avg
Moderate +11% lift
Without
With
+10.7%
Interview Lift
resolved cases with interview
Typical timeline
3y 4m
Avg Prosecution
46 currently pending
Career history
756
Total Applications
across all art units

Statute-Specific Performance

§101
5.4%
-34.6% vs TC avg
§103
55.2%
+15.2% vs TC avg
§102
15.8%
-24.2% vs TC avg
§112
20.1%
-19.9% vs TC avg
Black line = Tech Center average estimate • Based on career data from 709 resolved cases

Office Action

§103
DETAILED ACTION 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 . Election/Restrictions Applicant's election with traverse of group II, claims 9-20 in the reply filed on 5-27-2026 is acknowledged. The traversal is on the ground(s) that would not be a serious burden. This is not found persuasive because as disclosed in the restriction the subcombination has a separate utility such as identifying safety device, protecting private information, etc. thereby, requiring a different search than from the system. The requirement is still deemed proper and is therefore made FINAL. 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. The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows: 1. Determining the scope and contents of the prior art. 2. Ascertaining the differences between the prior art and the claims at issue. 3. Resolving the level of ordinary skill in the pertinent art. 4. Considering objective evidence present in the application indicating obviousness or nonobviousness. This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention. Claim(s) 9-20 are rejected under 35 U.S.C. 103 as being unpatentable over OOI 20230189396. As to claim 9, OOI discloses a method performed by a connector application comprising: receiving, from a workflow server, a trigger, the trigger including an action ID (par. [0033]: the workflow server is configured to send triggers to request a public-safety network to perform actions associated with the trigger; par. [0059]: the public-safety network comprises a core network and a gateway which has the role of connector application between workflow server and core network, thus, sending the trigger to the public-safety network by the workflow server implies sending the trigger to the public-safety CN; the trigger comprises a CAD ID, a incident ID, par. [0105], identifying the action); identifying a public safety device from a plurality of public safety devices, (par. [0077]: the workflow server sends to public-safety officers, e.g. policemen, fire fighters, an alarm indicating a triggering event, instructions by sending an "action" to devices worn or carried by officers), based on agency private information, to perform an action in response to the trigger, wherein agency private information may be shared or not with the workflow server (par. [0062]: the officer may determine a device that will accompany the officer on their shift; the information may or may not shared with the workflow server, par. [0068, 0105]); sending an indication to the identified public safety device to execute the action (par. [0077]). OOI does not explicitly recite no agency private information is shared with the workflow server, but since sharing private information is optional it would be obvious to one of the ordinary skills in the art to only provide the required information. Therefore. it would have been obvious to one of the ordinary skills in the art before the effective filing date of the present invention to only provide the required information and withholding private information for the simple purpose of protecting private information and avoiding scams. As to claim 10, OOI discloses the method of claim 9 further comprising: creating an action ID; sending the action ID to the workflow server, wherein the action ID is incorporated into workflows generated by the workflow server, wherein no agency private information is included in the workflows (par. [0033]: the workflow server is configured to send triggers to request a public-safety network to perform actions associated with the trigger; par. [0059]: the public-safety network comprises a core network and a gateway which has the role of connector application between workflow server and core network, thus, sending the trigger to the public-safety network by the workflow server implies sending the trigger to the public-safety CN; the trigger comprises a CAD ID, a incident ID, other details related to the incident may be sent par. [0105], identifying the action). OOI does not explicitly recite no agency private information is shared with the workflow server, but since sharing private information is optional it would be obvious to one of the ordinary skills in the art to only provide the required information. Therefore. it would have been obvious to one of the ordinary skills in the art before the effective filing date of the present invention to only provide the required information and withholding private information for the simple purpose of protecting private information and avoiding scams. As to claim 11, OOI discloses the method of claim 9 further comprising: receiving, from the workflow server, additional information associated with the trigger; wherein the action to be performed by the public safety device is determined based on the action ID and the additional information (see par. 0058-0060, 0077, 0108). As to claims 12-14, OOI discloses the method of claim 9 wherein agency information includes public safety device geographic location (see par. 0106, 0141); public safety device roll assignment information (see par. 0062); public safety device availability status [drone, cameras, etc.] (see par. 0113-0114, 0127). Ooi does not disclose that the information is private, but it is within the knowledge of one of the ordinary skills in the art to determine what information is private or not. Therefore. it would have been obvious to one of the ordinary skills in the art before the effective filing date of the present invention to only provide the required information and withholding private information for the simple purpose of protecting private information and avoiding scams. As to claims 15, OOI discloses the method of claim 9 further comprising: querying a plurality of public safety networks to identify if integration with the connector application is supported; and sending action IDs to those public safety networks that support the integration (see par. 0063, 0105). As to claims 16, OOI discloses the method of claim 9 wherein the public safety device is a public safety radio (see par. 0059). Regarding claims 17-20 they are the corresponding non-transitory processor readable medium claims of method claims 9-11 and 15. Therefore, claims 17-20 are rejected for the same reasons as shown above. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to MARCOS L TORRES whose telephone number is (571)272-7926. The examiner can normally be reached 10:00 AM - 6:00 PM M-F. 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, Alison Slater can be reached at (571)270-0375. 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. MARCOS L. TORRES Primary Examiner Art Unit 2647 /MARCOS L TORRES/Primary Examiner, Art Unit 2647
Read full office action

Prosecution Timeline

Nov 14, 2023
Application Filed
Aug 11, 2026
Non-Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12750779
ENERGY-SAVING INDICATION METHOD AND APPARATUS THEREOF
4y 7m to grant Granted Sep 29, 2026
Patent 12744842
Terminal Device
3y 0m to grant Granted Sep 22, 2026
Patent 12739789
METHOD AND APPARATUS FOR POWER SAVING ENHANCEMENTS OF PAGING PROCEDURES IN CELLULAR SYSTEMS
3y 1m to grant Granted Sep 15, 2026
Patent 12739752
WAKEUP METHOD AND APPARATUS, AND ELECTRONIC DEVICE
2y 9m to grant Granted Sep 15, 2026
Patent 12713342
REPORTING TRANSMISSION FOR DISCONTINUOUS RECEPTION
3y 1m to grant Granted Aug 18, 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

1-2
Expected OA Rounds
68%
Grant Probability
78%
With Interview (+10.7%)
3y 4m (~6m remaining)
Median Time to Grant
Low
PTA Risk
Based on 709 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