Prosecution Insights
Last updated: July 17, 2026
Application No. 18/254,388

MOBILE DEVICE, GUARD UNIT, AND METHOD FOR ENSURING THE PERFORMANCE OF A SAFETY ACTIVITY FOR AN ELEVATOR

Non-Final OA §101§102§112
Filed
May 25, 2023
Priority
Dec 02, 2020 — EU 20211282.7 +1 more
Examiner
DUDA, RINA I
Art Unit
2846
Tech Center
2800 — Semiconductors & Electrical Systems
Assignee
Inventio AG
OA Round
1 (Non-Final)
80%
Grant Probability
Favorable
1-2
OA Rounds
0m
Est. Remaining
90%
With Interview

Examiner Intelligence

Grants 80% — above average
80%
Career Allowance Rate
814 granted / 1011 resolved
+12.5% vs TC avg
Moderate +10% lift
Without
With
+10.0%
Interview Lift
resolved cases with interview
Typical timeline
2y 5m
Avg Prosecution
32 currently pending
Career history
1035
Total Applications
across all art units

Statute-Specific Performance

§101
1.9%
-38.1% vs TC avg
§103
53.5%
+13.5% vs TC avg
§102
26.4%
-13.6% vs TC avg
§112
13.3%
-26.7% vs TC avg
Black line = Tech Center average estimate • Based on career data from 1011 resolved cases

Office Action

§101 §102 §112
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 Claims 21-24 are withdrawn from further consideration pursuant to 37 CFR 1.142(b) as being drawn to a nonelected invention, there being no allowable generic or linking claim. Election was made without traverse in the reply filed on 6/2/26. Claim Rejections - 35 USC § 101 35 U.S.C. 101 reads as follows: Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title. Claims 16-20 and 25-31 are rejected under 35 U.S.C. 101 because the claimed invention is directed to the abstract idea of managing a safety checklist which would fall under methods for organizing human activity or mental processes without significantly more (Step 2A, prong 1). The claim(s) recite(s) requesting a user to perform a safety check, receiving confirmation that the safety check has been performed, and checking the correctness of the answers to safety check questions as well as the time taken by the user to answer said questions. Validating a safety checklist answers can be performed in the human mind or via pen/paper. Step 2A, prong 2: Is the abstract idea integrated into a practical application? This judicial exception is not integrated into a practical application because even though the claims recite hardware elements such as a processor, communication unit, and mobile device, they do it in a way that is highly general. They act as general tools to execute the abstract idea rather than improving the each of the recited structural components. The recited invention does not solve any technical problem with any novel technical solution. Step 2B: Does the claims recite an inventive concept? The claim(s) lack an inventive concept. The recited structural elements such as the processor and a mobile device which communicates with an elevator controller via a communication unit perform nothing more than well-understood and conventional functions in the art. The method claims 25-31 do not add any other limitation directed to a patent eligible subject matter. The claims are ejected for the same reasons as apparatus claims 16-20. Claim Interpretation The following is a quotation of 35 U.S.C. 112(f): (f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph: An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked. As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph: (A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function; (B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and (C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function. Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function. Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function. Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “questioning unit” in claims 16-20. Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof. If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. Claim Rejections - 35 USC § 112 The following is a quotation of the first paragraph of 35 U.S.C. 112(a): (a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention. The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112: The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention. 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. The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph: The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention. Claims 16-20 and 25-31 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the enablement requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to enable one skilled in the art to which it pertains, or with which it is most nearly connected, to make and/or use the invention. The specification fails to include an algorithm or step-by-step process describing how the recited functional checks are automated. The disclosure does not include the technical implementation of the recited method of operation. How is the processor programmed to determine correctness of the answers provided by the user or the time taken by the user to answer any questions? Claims 16-20 and 25-31 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. In reference to the limitation directed to the “questioning unit”, the recited functional language is implemented via computer instructions on a mobile device. It is unclear how the ”questioning unit” generates the request to perform the safety check. The originally filed disclosure does not provide the necessary algorithm for performing the recited functions. Claim Rejections - 35 USC § 102 The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention. Claim(s) 16-20 and 25-31 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Cortona et al (US Patent 10676318). The pending claims have been rejected under 35 USC 112(a) and (b). It is unclear how the recited functions could be performed. The examiner will apply prior art to the invention as best understood by her. Claims 16 and 25, Cortona et al teaches a mobile device for performing a safety check before operating an elevator, wherein the mobile device comprises a user interface 3 that includes an inherent “questioning unit” for sending a request 6 to an elevator control system 2, wherein the control system comprises a processor 11 and a receiving unit 10 for receiving the request 6 from the user interface 3. The control system 2 sends permission to an elevator maintenance technician via interface 3 to access the elevator system after it has performed at least two authentication checks of the user using interface 3. Claims 17 and 26, Cortona et al teaches, for example col. 4 lines 7-19, that the communication unit in the user interface 3 communicates with elevator system 2 to control the elevator in the context of a maintenance issue (ending of a normal operation of the elevator). Claims 18 and 27, Cortona et al describes in fig. 2 and corresponding description that the control system 2 would confirm the right of a user 5 to communicate with the control system 2 via interface 3. If the control system cannot verify that the user has an authorization to access the elevator system, then the control system will let the user know that access has been denied in various ways (message 7). Claims 19 and 28, Cortona et al teaches a control system including a processor 11 and a memory unit 9. The specific data stored in the memory unit is considered a design choice and it is not given any patentable weight. Claims 20 and 29, Cortona et al teaches the safety check performed by the user interface 3 and the elevator control system 2 is predetermined and save in memory 9. Claim 30, Cortona et al teaches an elevator system comprising a controller 2 and a mobile device as described in the rejection of claim 25 above. Claim 31, Cortona et al teaches an elevator system comprising a guard unit 8 (which can verify the authorization of the maintenance technician to access the elevator) and a mobile device as described in the rejection of claim 25 above. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. The documents cited in the attached PTO-892 describe other elevators systems that include a user interface and a controller, wherein the controller monitors access to the elevator by a technician. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Rina I Duda whose telephone number is (571)272-2062. The examiner can normally be reached M-F 8-4 PM. 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, Eduardo Colon Santana can be reached at (571) 272-2060. 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. /RINA I DUDA/Primary Examiner, Art Unit 2837
Read full office action

Prosecution Timeline

May 25, 2023
Application Filed
Jun 29, 2026
Non-Final Rejection mailed — §101, §102, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12679698
METHOD AND APPARATUS FOR DETECTING ELEVATOR SAFETY CHAIN
3y 9m to grant Granted Jul 14, 2026
Patent 12676566
CONTROLLER CIRCUIT OF MOTOR AND CONTROL METHOD
2y 3m to grant Granted Jul 07, 2026
Patent 12671243
MOTOR TERMINAL SNUBBING CIRCUIT
2y 10m to grant Granted Jun 30, 2026
Patent 12662350
VOICE ACTIVATED ELEVATOR PASSENGER INTERFACE CONFIGURATION DEVICE
5y 6m to grant Granted Jun 23, 2026
Patent 12662352
ELEVATOR OPERATING DEVICE HAVING TWO CALL INPUT DEVICES DISPOSED SEPARATE FROM EACH OTHER WITH RESPECT TO PASSENGERS
3y 9m to grant Granted Jun 23, 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
80%
Grant Probability
90%
With Interview (+10.0%)
2y 5m (~0m remaining)
Median Time to Grant
Low
PTA Risk
Based on 1011 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