Prosecution Insights
Last updated: November 04, 2026
Application No. 18/527,883

INTERFACE SCHEDULING METHOD AND DEVICE, AND COMPUTING DEVICE

Final Rejection §103
Filed
Dec 04, 2023
Priority
Dec 15, 2022 — CN 202211618693.1
Examiner
WU, QING YUAN
Art Unit
2199
Tech Center
2100 — Computer Architecture & Software
Assignee
Faurecia Clarion Electronics (Xiamen) Co. Ltd.
OA Round
3 (Final)
91%
Grant Probability
Favorable
4-5
OA Rounds
0m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 91% — above average
91%
Career Allowance Rate
711 granted / 782 resolved
+35.9% vs TC avg
Moderate +11% lift
Without
With
+10.8%
Interview Lift
resolved cases with interview
Typical timeline
2y 10m
Avg Prosecution
18 currently pending
Career history
803
Total Applications
across all art units

Statute-Specific Performance

§101
18.8%
-21.2% vs TC avg
§103
24.8%
-15.2% vs TC avg
§102
19.5%
-20.5% vs TC avg
§112
26.1%
-13.9% vs TC avg
Black line = Tech Center average estimate • Based on career data from 782 resolved cases

Office Action

§103
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 . DETAILED ACTION Claims 1-20 are pending in the application. Continued Examination Under 37 CFR 1.114 A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set for3th in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 9/30/26 has been entered. 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: “module used to” recited in claims 5-8 which are treated as computer hardware and/or hardware executed software/firmware [paragraph 116]. 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 § 103 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 (i.e., changing from AIA to pre-AIA ) 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. 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. Claim(s) 1-20 is/are rejected under 35 U.S.C. 103 as being unpatentable over US PG Pub. 2023/0300240 to Fan, and further in view of US PG Pub. 2022/0303385 to Hsieh et al. (hereafter Hsieh). Fan was cited in the previous office action. As to claim 1, Fan teaches the invention as claimed including an interface scheduling method, performed by a computing device, comprising: obtaining a first request message of an application and an identifier of a second interface, wherein the first request message is used to request a display of a first interface of the application, the request message is an interface display request message, the first request message includes an identifier of the first interface, and the second interface is a currently displayed interface [triggering condition by means of user input or detected changes in an application or request by an application including/included in various rules that triggers the switch from currently displayed lock screen 1 to displaying lock screen 2, paragraphs 13, 53, 87, 137, 144-146 and 149; Lock screen change request being application requested, paragraphs 11, 38-39, 146; application identifiers or lock screen application identifier that identifies corresponding lock screen of an application, paragraphs 37, 112, 176, 182]; determining a scheduling result according to a preset scheduling strategy, the identifier of the first interface and the identifier of the second interface, wherein the preset scheduling strategy includes priorities of a plurality of identifiers, and the plurality of identifiers include the identifier of the first interface and the identifier of the second interface [preset or predetermined sequence level associated with respective lock screens determines the lock screen to be displayed or schedule next for display over current lock screen based on priorities of application(s) and respective lock screens, paragraphs 7, 10, 13 and 149; application identifiers or lock screen application identifier that identifies corresponding lock screen of an application, paragraphs 37, 112, 176, 182]; and performing an interface scheduling on the first interface and the second interface according to the scheduling result to display the first interface or the second interface [triggering of preset/predetermined condition determines the next lock screen to display such as change from lock screen 1 to lock screen 2, paragraphs 13, 87, 137, 144-146 and 149]; wherein determining the scheduling result according to the preset scheduling strategy, the identifier of the first interface and the identifier of the second interface, includes: determining a priority corresponding to the identifier of the first interface and a priority corresponding to the identifier of the second interface according to the priorities of the plurality of identifiers in the preset scheduling strategy; and determining the target scheduling result according to a comparison of the priority corresponding to the identifier of the first interface and the priority corresponding to the identifier of the second interface [preset sequence of lock screens are based on priorities of applications of corresponding screens such that screen of higher priority has higher sequence level and preferentially displayed on the screen of the device, paragraph 7; presence of lock screens are identifiable by a lock screen application identifiers that are ordered/sequenced in a preset manner with respect to each other based on priorities of the applications, paragraphs 176 and 179; S401-s404, Fig. 4(a); determination of current lock screen or next/ target screen to display (i.e. scheduling) are based on priority-based preset sequence as well as preset rules/conditions that rely on the priority-based preset sequence to display the next lock screen, paragraphs 137, 141-142 and 145], wherein the scheduling result is to display the first interface and to not display the second interface [when content displayed on a lock screen changes, second lock screen is display in place of current lock screen, paragraphs 14, 17 and 144], or the scheduling result is to not display the first interface and to display the second interface [current screen not replaced when rule 3 is violated, more specifically over a request threshold, by a requesting application, paragraph 146]. Fan does not specifically teach applying interface scheduling to an in-vehicle infotainment system. However, Hsieh teaches prioritized display of operation interface such as that of Android Auto as well as Apple Carplay allowing display screen of automobile entertainment device to display content of the driver’s smartphone [abstract; paragraph 2]. It would have been obvious before the effective filing date of the claimed invention to have apply Fan’s Android-based [paragraphs 102,104 and 118] prioritized lock screen display [paragraphs 7, 10, 13 and 149] in Hsieh’s in-vehicle infotainment system to extend the applicability of Fan’s method to different platforms. As to claim 2, Fan teaches the invention as claimed including wherein determining the scheduling result according to the preset scheduling strategy, the identifier of the first interface and the identifier of the second interface includes: determining a first priority of the identifier of the first interface in the preset scheduling strategy; determining a second priority of the identifier of the second interface in the preset scheduling strategy [preset sequence of ranked/prioritize lock screens to be display such that an exercise lock screen can be switch out to a music lock screen or a system lock screen, etc., based on various preset condition satisfying rule(s), paragraphs 7, 31, 149 and 143-146]; and in a case where the first priority is lower than the second priority, determining that the scheduling result is to not display the first interface and to display the second interface [application lock screen of a same application over a request threshold within a predetermined time is prevented from using its lock screen as the target lock screen, paragraph 146, lines 9-19]. As to claim 3, Fan as modified teaches the invention substantially as claimed including wherein determining the scheduling result according to the preset scheduling strategy, the identifier of the first interface and the identifier of the second interface includes: determining a first priority of the identifier of the first interface in the preset scheduling strategy; determining a second priority of the identifier of the second interface in the preset scheduling strategy [preset sequence of ranked/prioritize lock screens to be display such that an exercise lock screen can be switch out to a music lock screen or a system lock screen, etc., based on various preset condition satisfying rule(s), paragraphs 7, 31, 149 and 143-146]; and in a case where the first priority is higher than the second priority, determining that the scheduling result is to display the first interface and to not display the second interface [cyclically switch and display lock screens based on preset sequence, paragraph 149]. As to claim 4, Fan as modified teaches the invention substantially as claimed including further comprising: obtaining a second request message of the application, wherein the second request message is used to request that the first interface not be displayed, and the second request message includes the identifier of the first interface; and removing the first priority of the identifier of the first interface in the preset scheduling strategy to obtain a first scheduling strategy such that the first interface is not displayed and the second interface is displayed [timeout of lock screen 2 and recovers original display sequence of the lock screens of the applications based on the preset sequence, paragraphs 152 and 171-172]. As to claims 5-8, Fan and Hsieh teach an interface scheduling method as claimed in claims 1-4, therefore Fan and Hsieh teach the device for implementing the method. As to claims 9-12, these claims are rejected for the same reason as claims 5-8 above. As to claims 13-16, Fan and Hsieh teach an interface scheduling method as claimed in claims 1-4, therefore Fan and Hsieh teach the non-transitory computer-readable storage medium has stored thereon computer programs or instructions, wherein the computer programs or the instructions, when run on a computer, cause the computer to perform the method. As to claims 17-20, these claims are rejected for the same reason as claims 13-16 above. Response to Arguments Applicant's arguments filed 9/30/26 have been fully considered but they are not persuasive. In the remarks, Applicant argued in substance that: Neither Hsieh or Fan alone or in combination teaches a request message sent by applications. As described by Fan in paragraph [0145], Fan states that the lock screen interface cycles in response to physical user actions rather than triggered by “app requests message” that rely on interface priority comparisons to determine interface scheduling. Prioritization in Hsieh is triggered by physical device connection or manual user selection. As described by Fan in paragraph [0145], there is no scenario in which “the next interface is not displayed”. The basis for determining a display a target lock screen interface is the triggering of a preset condition rather than the determination and comparison of priorities of two specific interface. Examiner respectfully traversed Applicant's remarks: As to point (a), the examiner respectfully disagrees and submits that Fan additionally teaches lock screen change request being application requested to subsequently display the lock screen on the screen of the device [paragraphs 11, 38-39 and 146], such that the lock screens are arranged in predetermined sequence based on priorities [paragraphs 13, 31 and 41] and application identifiers or lock screen application identifier that identifies corresponding lock screen of an application [paragraphs 37, 112, 176 and 182]. Therefore, applicant’s argument is not persuasive. As to point (b), the examiner respectfully disagrees and submits that Fan clearly teaches that a current screen is not replaced under rule 3, more specifically request to use lock screen of an application as target lock screen for display over a requesting frequency threshold by a requesting application is not allow (i.e. allowed if less than a threshold) [paragraph 146]. As to point (c), the examiner respectfully disagrees and submits that “priority” as disclosed by Fan corresponds to the preferential display of a lock screen over other lock screens on the screen of an electronic device, whether the priority/order is predetermined/preset sequence (i.e. before triggering predetermined/preset rules/conditions) and/or subsequently triggered by preset conditions [paragraphs 7, 31 and 41; abstract], such that the determination of a target lock screen (i.e. top priority) to be preferentially display requires the comparing or determining of other lock screens having a lower priority in comparison. All claims are identical to or patentably indistinct from, or have unity of invention with claims in the application prior to the entry of the submission under 37 CFR 1.114 (that is, restriction (including a lack of unity of invention) would not be proper) and all claims could have been finally rejected on the grounds and art of record in the next Office action if they had been entered in the application prior to entry under 37 CFR 1.114. Accordingly, THIS ACTION IS MADE FINAL even though it is a first action after the filing of a request for continued examination and the submission under 37 CFR 1.114. See MPEP § 706.07(b). 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 nonprovisional extension fee (37 CFR 1.17(a)) 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 mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to QING YUAN WU whose telephone number is (571)272-3776. The examiner can normally be reached M-F 9AM-6PM EST. 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, Lewis Bullock can be reached on 571-272-3759. 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. /QING YUAN WU/Primary Examiner, Art Unit 2199
Read full office action

Prosecution Timeline

Dec 04, 2023
Application Filed
Mar 16, 2026
Non-Final Rejection mailed — §103
Jun 05, 2026
Response Filed
Jul 02, 2026
Final Rejection mailed — §103
Sep 30, 2026
Request for Continued Examination
Oct 07, 2026
Response after Non-Final Action
Oct 30, 2026
Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12783303
POWER NEURAL NETWORK-BASED WORKLOAD DISTRIBUTION IN DISTRIBUTED COMPUTING SYSTEMS
3y 4m to grant Granted Nov 03, 2026
Patent 12775529
DATA PROCESSORS
3y 5m to grant Granted Oct 27, 2026
Patent 12775489
MULTI-CORE PROCESSOR TASK SCHEDULING METHOD, AND DEVICE AND STORAGE MEDIUM
3y 2m to grant Granted Oct 27, 2026
Patent 12769571
CONTROLLER VIRTUALIZATION DEVICE AND CONTROL SYSTEM
3y 8m to grant Granted Oct 20, 2026
Patent 12769587
WORKLOAD-INTENT-BASED LCS RESOURCE CAPABILITY CONFIGURATION SYSTEM
2y 10m to grant Granted Oct 20, 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

4-5
Expected OA Rounds
91%
Grant Probability
99%
With Interview (+10.8%)
2y 10m (~0m remaining)
Median Time to Grant
High
PTA Risk
Based on 782 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