CTNF 18/795,045 CTNF 76267 DETAILED ACTION Claims 1-3 are presented for examination. Notice of Pre-AIA or AIA Status 07-03-aia AIA 15-10-aia The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA. 07-30-03-h AIA Claim Interpretation 07-30-03 AIA 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. 07-30-05 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: “package generation section” [to generate a package] in claim 1 “package distribution section” [to distribute the package] in claim 1 “logic management registration section” [that registers logic generating the package] in claim 1 “logic identification (ID) management registration section” [that registers an ID assigned to the logic and a version of software] in claim 1 “package generation section” [that identifies an ID corresponding to the master device…, acquires logic corresponding to the ID…, and generates a package…] in claim 1 “package generation section” [to generate a package] in claim 2 “package distribution section” [to distribute the package] in claim 2 “logic management registration section” [that manages logic generating the package] in claim 2 “logic identification (ID) management registration section” [that manages a version of software of a master device and an ID assigned to the logic for the version of the software] in claim 2 “package generation section” [that identifies an ID corresponding to the master device…, acquires logic corresponding to the ID…, and generates a package…] in claim 2 ** Support for corresponding hardware is found in ¶ 43 of Applicant’s Specification: “The control unit and the method thereof of the present disclosure may be implemented by a dedicated computer provided by configuring a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the control unit and the technique according to the present disclosure may be achieved by a dedicated computer provided by constituting a processor with one or more dedicated hardware logic circuits. Alternatively, the control unit and the technique according to the present disclosure may be achieved using one or more dedicated computers constituted by a combination of the processor and the memory programmed to execute one or more functions and the processor with one or more hardware logic circuits. The computer program may also be stored on a computer-readable and non-transitory tangible storage medium as an instruction executed by a computer.” 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 § 102 07-07-aia AIA 07-07 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 – 07-12-aia AIA (a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. 07-15-03-aia AIA Claim s 1-3 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Kim et al. (US 2025/0010750) . [Claim 1] Kim discloses a center device that manages data to be written to a plurality of electronic control devices installed in a vehicle (¶ 52 – “The vehicle controller 110 communicates with the plurality of part controllers 130 provided inside the vehicle 100 through a communication unit 112 to receive and store version information of the firmware of each of the part controllers 130 .”; ¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.), the center device comprising: a package generation section that is configured to generate a package including update data to be distributed to the vehicle (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 52, 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.); and a package distribution section that is configured to distribute the package to the vehicle (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 52, 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.), wherein the package generation section includes a logic management registration section that registers logic generating the package when the logic is generated according to a specification change of a master device that receives a package distributed from the center device and transfers update data to the electronic control device (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 52, 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.), and a logic identification (ID) management registration section that registers an ID assigned to the logic and a version of software of the master device corresponding to the logic when the ID and the version are notified (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶ 2 – “Electric vehicles include controllers that control various types of parts, and the firmware of each controller can be updated (reprogrammed) to the latest version through CAN communication. There is a possibility that serious software defects may be found in vehicles after production and updates may be needed to correct such defects, and controllers may also improve various functions through updates.” In other words, the firmware includes software.; ¶ 16 – “In addition, when the battery pack is mounted in the slot, the battery management system may compare the version information of the firmware of each of the part controllers being stored with the version information of the firmware stored in the server.” In other words, version information is correlated to each respective part controller.), and when an input of information on a master device to which a package is to be distributed is received from the package distribution section, the package generation section identifies an ID corresponding to the master device with reference to the logic ID management registration section on a basis of the information, acquires logic corresponding to the ID from the logic management registration section, and generates a package on a basis of the logic (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶ 2 – “Electric vehicles include controllers that control various types of parts, and the firmware of each controller can be updated (reprogrammed) to the latest version through CAN communication. There is a possibility that serious software defects may be found in vehicles after production and updates may be needed to correct such defects, and controllers may also improve various functions through updates.” In other words, the firmware includes software.; ¶ 16 – “In addition, when the battery pack is mounted in the slot, the battery management system may compare the version information of the firmware of each of the part controllers being stored with the version information of the firmware stored in the server.” In other words, version information is correlated to each respective part controller.). [Claim 2] Kim discloses a center device that manages data to be written to a plurality of electronic control devices installed in a vehicle (¶ 52 – “The vehicle controller 110 communicates with the plurality of part controllers 130 provided inside the vehicle 100 through a communication unit 112 to receive and store version information of the firmware of each of the part controllers 130 .”; ¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.), the center device comprising: a package generation section that is configured to generate a package including update data to be distributed to the vehicle (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 52, 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.); and a package distribution section that is configured to distribute the package to the vehicle (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 52, 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.), wherein the package generation section includes a logic management registration section that manages logic generating the package and an ID assigned to the logic (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 52, 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.), and a logic ID management registration section that manages a version of software of a master device and an ID assigned to the logic for the version of the software (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶ 2 – “Electric vehicles include controllers that control various types of parts, and the firmware of each controller can be updated (reprogrammed) to the latest version through CAN communication. There is a possibility that serious software defects may be found in vehicles after production and updates may be needed to correct such defects, and controllers may also improve various functions through updates.” In other words, the firmware includes software.; ¶ 16 – “In addition, when the battery pack is mounted in the slot, the battery management system may compare the version information of the firmware of each of the part controllers being stored with the version information of the firmware stored in the server.” In other words, version information is correlated to each respective part controller.), and when an input of a version of software of a master device to which a package is to be distributed is received as information from the package distribution section, the package generation section identifies an ID corresponding to the master device with reference to the logic ID management registration section on a basis of the information, acquires logic corresponding to the ID from the logic management registration section, and generates a package on a basis of the logic (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶ 2 – “Electric vehicles include controllers that control various types of parts, and the firmware of each controller can be updated (reprogrammed) to the latest version through CAN communication. There is a possibility that serious software defects may be found in vehicles after production and updates may be needed to correct such defects, and controllers may also improve various functions through updates.” In other words, the firmware includes software.; ¶ 16 – “In addition, when the battery pack is mounted in the slot, the battery management system may compare the version information of the firmware of each of the part controllers being stored with the version information of the firmware stored in the server.” In other words, version information is correlated to each respective part controller.). [Claim 3] A method for generating a distribution package, in which a package including update data to be distributed to a vehicle is generated to write data to a plurality of electronic control devices installed in the vehicle (¶ 52 – “The vehicle controller 110 communicates with the plurality of part controllers 130 provided inside the vehicle 100 through a communication unit 112 to receive and store version information of the firmware of each of the part controllers 130 .”; ¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.), the method comprising: registering logic for generating the package in a logic management registration section when the logic is generated according to a specification change of a master device that receives a package distributed from a center device and transfers update data to the electronic control device (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶¶ 52, 89-90 – Updates are downloaded to the vehicle ( e.g., from a server that distributes firmware) for part controllers that need a new version of the respective firmware.); registering an ID assigned to the logic and a version of software of the master device corresponding to the logic in a logic ID management registration section when the ID and the version are notified (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶ 2 – “Electric vehicles include controllers that control various types of parts, and the firmware of each controller can be updated (reprogrammed) to the latest version through CAN communication. There is a possibility that serious software defects may be found in vehicles after production and updates may be needed to correct such defects, and controllers may also improve various functions through updates.” In other words, the firmware includes software.; ¶ 16 – “In addition, when the battery pack is mounted in the slot, the battery management system may compare the version information of the firmware of each of the part controllers being stored with the version information of the firmware stored in the server.” In other words, version information is correlated to each respective part controller.); and identifying, when an input of information on a master device to which a package is to be distributed is received, an ID corresponding to the master device with reference to the logic ID management registration section on a basis of the information, acquiring logic corresponding to the ID from the logic management registration section, and generating a package on a basis of the logic (¶ 87 – “For example, if the firmware version information of the motor controller stored in the BMS 122 is 1.1 and the firmware version information of the motor controller stored in the server 300 is 1.2, since the firmware version information of the motor controller stored in the server 300 is a more recent version, the BMS 122 may download the firmware of the motor controller from the server 300 . Once the download is complete, the BMS 122 may update the firmware version information of the motor controller it stores to version 1.2.”; ¶ 2 – “Electric vehicles include controllers that control various types of parts, and the firmware of each controller can be updated (reprogrammed) to the latest version through CAN communication. There is a possibility that serious software defects may be found in vehicles after production and updates may be needed to correct such defects, and controllers may also improve various functions through updates.” In other words, the firmware includes software.; ¶ 16 – “In addition, when the battery pack is mounted in the slot, the battery management system may compare the version information of the firmware of each of the part controllers being stored with the version information of the firmware stored in the server.” In other words, version information is correlated to each respective part controller.) . Conclusion 07-96 AIA The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Moran et al. (US 2009/0300595) – Updates software for a vehicle. Any inquiry concerning this communication or earlier communications from the examiner should be directed to SUSANNA M DIAZ whose telephone number is (571)272-6733. The examiner can normally be reached M-F, 8 am-4:30 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, Brian Epstein can be reached at (571) 270-5389. 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. /SUSANNA M. DIAZ/ Primary Examiner Art Unit 3625A Application/Control Number: 18/795,045 Page 2 Art Unit: 3625 Application/Control Number: 18/795,045 Page 3 Art Unit: 3625 Application/Control Number: 18/795,045 Page 4 Art Unit: 3625 Application/Control Number: 18/795,045 Page 5 Art Unit: 3625 Application/Control Number: 18/795,045 Page 6 Art Unit: 3625 Application/Control Number: 18/795,045 Page 7 Art Unit: 3625 Application/Control Number: 18/795,045 Page 8 Art Unit: 3625 Application/Control Number: 18/795,045 Page 9 Art Unit: 3625 Application/Control Number: 18/795,045 Page 10 Art Unit: 3625 Application/Control Number: 18/795,045 Page 11 Art Unit: 3625 Application/Control Number: 18/795,045 Page 12 Art Unit: 3625 Application/Control Number: 18/795,045 Page 13 Art Unit: 3625 Application/Control Number: 18/795,045 Page 14 Art Unit: 3625 Application/Control Number: 18/795,045 Page 15 Art Unit: 3625 Application/Control Number: 18/795,045 Page 16 Art Unit: 3625 Application/Control Number: 18/795,045 Page 17 Art Unit: 3625 Application/Control Number: 18/795,045 Page 18 Art Unit: 3625
Prosecution Insights