DETAILED ACTION
Claims 1-5, 7, 9 and 11-19 are pending in this 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 .
Allowable Subject Matter
Claims 4, 5, 13, 14, 17 and 18 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
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.
Claims 1, 3, 7, 9 and 12, 16 and 19 are rejected under 35 U.S.C. 103 as being unpatentable over Adam et al. (CN-106183821-A), [hereinafter “Adam”] in view of Hsu et al. (US PGPUB No. 2015/0121538) [hereinafter “Hsu”] in further view of Zhang et al. (US PGPUB No. 2009/0125974) [hereinafter “Zhang”].
As per claim 1, Adam teaches the method for security monitoring of a vehicle-mounted system, wherein the vehicle-mounted system comprises a plurality of levels of functions (Abstract, security system “mounted” on a vehicle with different levels related to measured security parameters), and the method comprises: receiving, by a first security monitoring module of a first level of the plurality of levels (security memory manager acts like a hypervisor for security-critical-operating system), first exception information from a second level, wherein the first level is an upper level of the second level (Page 2 para. 9, sending security parameters and variables can trigger an increase in security level); determining, by the first security monitoring module, whether the first exception information exceeds a processing range of the first security monitoring module (Page 2 para. 11, determining based on the security parameter that security requirements are higher than current level and requires more accurate measurements see Page 3 para. 1-2); and sending, by the first security monitoring module, the first exception information to a third level when the first exception information exceeds the processing range of the first security monitoring module (Page 2 para. 7, example cites four levels that can be moved increased or decreased to based on security parameters), and performing security processing on the first exception information by the third level, wherein the third level is an upper level of the first level (See id. Level C will require certain type of measurement functions for the security parameters see also Page 4 para. 1).
Adam does not explicitly teach exception information sent between security modules. Hsu teaches exception information sent between security modules ([0017], security level information is sent between security modules which jointly govern the security implementation and security levels).
At the time of filing, it would have been obvious to one of ordinary skill in the art to combine Adam with the teachings of Hsu, exception information sent between security modules, to compartmentalize the security functionalities for ease of reuse and user decision making.
The combination of Adam and Hsu does not explicitly teach monitoring, by the first security monitoring module, a running state of a function module included in the second level and a running state of the second security monitoring module. Zhang teaches monitoring, by the first security monitoring module, a running state of a function module included in the second level and a running state of the second security monitoring module ([0022], vTPM manager manages runtime data of the vTPMs and also VMs).
At the time of filing, it would have been obvious to one of ordinary skill in the art to combine Adam and Hsu with the teachings of Zhang, monitoring, by the first security monitoring module, a running state of a function module included in the second level and a running state of the second security monitoring module, to compartmentalize the security functionalities for ease of reuse and user decision making.
As per claim 3, the combination of Adam, Hsu and Zhang teaches the method for security monitoring according to claim 1, wherein the method further comprises: monitoring, by the first security monitoring module, a running state of the first level (Adam; Page 5 para. 7, monitoring for security events during the running of vehicle including things like torque).
As per claim 7, the substance of the claimed invention is identical or substantially similar to that of claim 1. Accordingly, this claim is rejected under the same rationale.
As per claim 9, the substance of the claimed invention is identical or substantially similar to that of claim 1. Accordingly, this claim is rejected under the same rationale.
As per claim 12, the substance of the claimed invention is identical or substantially similar to that of claim 3. Accordingly, this claim is rejected under the same rationale.
As per claim 16, the substance of the claimed invention is identical or substantially similar to that of claim 3. Accordingly, this claim is rejected under the same rationale.
As per claim 19, the combination of Adam, Hsu and Zhang teaches the electronic device according to claim 7, wherein the electronic device is located on a vehicle (Adam; Abstract, processing unit on a vehicle used to measure and test security parameters).
Claims 2, 11 and 15 are rejected under 35 U.S.C. 103 as being unpatentable over Adam, Hsu and Zhang in further view of Jung et al. (US PGPUB No. 2009/0259839) [hereinafter “Jung”].
As per claim 2, the combination of Adam, Hsu and Zhang teaches the method for security monitoring according to claim 1.
The combination of Adam, Hsu and Zhang does not explicitly teach performing security processing on the first exception information by the second security monitoring module when the first exception information does not exceed a processing range of the second security monitoring module; or performing security processing on the first exception information by the first security monitoring module when the first exception information does not exceed the processing range of the first security monitoring module. Jung teaches performing security processing on the first exception information by the second security monitoring module when the first exception information does not exceed a processing range of the second security monitoring module ([0051], when security level of user is the same as the second security module, the second security module is used); or performing security processing on the first exception information by the first security monitoring module when the first exception information does not exceed the processing range of the first security monitoring module ([0051], when security level of user is the same level as the first security module, the first security module is used).
At the time of filing, it would have been obvious to one of ordinary skill in the art to combine Adam, Hsu and Zhang with the teachings of Jung, performing security processing on the first exception information by the second security monitoring module when the first exception information does not exceed a processing range of the second security monitoring module; or performing security processing on the first exception information by the first security monitoring module when the first exception information does not exceed the processing range of the first security monitoring module, to route processing to the appropriate components for efficient and accurate execution of security policies.
As per claim 11, the substance of the claimed invention is identical or substantially similar to that of claim 2. Accordingly, this claim is rejected under the same rationale.
As per claim 15, the substance of the claimed invention is identical or substantially similar to that of claim 2. Accordingly, this claim is rejected under the same rationale.
Response to Arguments
Applicant’s after-final arguments with respect to the rejection of claims 1-3, 7, 9 and 11-12, 15-16 and 19 under 35 U.S.C. 103 have been considered and are convincing. Examiner has introduced a new prior art reference, Zhang, to address the discussed feature/s. This action is final in light of the previous amendments made on 7/22/2025.
To expedite prosecution, Examiner is open to conducting an after-final interview to discuss claim amendments to overcome the current rejection and/or place the application in condition for allowance.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Challener et al. (US PGPUB No. 2008/0244569), Satish et al. (US Patent No. 8,079,030), Luo et al. (CN-101425027-A), Jayarathna et al. ("Integrated Security for Services Hosted in Virtual Environments," 2016 IEEE Trustcom/BigDataSE/ISPA, Tianjin, China, 2016, pp. 82-89, doi: 10.1109/TrustCom.2016.0049), Lauer et al. ("Hypervisor-Based Attestation of Virtual Environments," 2016 Intl IEEE Conference, Toulouse, France, 2016, pp. 333-340, doi: 10.1109/UIC-ATC-ScalCom-CBDCom-IoP-SmartWorld.2016.0067) and Panda et al. ("An Efficient Virtual Machine Management Algorithm for Vehicular Clouds," 2018 Fifth International Conference on Parallel, Distributed and Grid Computing (PDGC), Solan, India, 2018, pp. 682-688, doi: 10.1109/PDGC.2018.8745987) all disclose various aspects of the claimed invention including different security levels in vehicle operations and communications.
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 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 PETER C SHAW whose telephone number is (571)270-7179. The examiner can normally be reached Max Flex.
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, Carl Colin can be reached at 571-272-3862. 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.
/PETER C SHAW/Primary Examiner, Art Unit 2493 January 12, 2026