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 . In communications filed on 11/26/2024. Claims 1-8 are pending in this examination.
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 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. This examination is in response to US Patent Application No. 18/960,836.
Claim Rejections - 35 USC § 112
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 1-6 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 pre-AIA the applicant regards as the invention.
The claim 1 recites in the first line, “a digital key that is registered” and also recites on line 4, “a digital key registered”, the two instances would raise an issue since both refer to “a digital key” which imposes ambiguity whether the claim is referring the same key or a different key.
Claims 2-6 do not cure the deficiency of claim 1 and are rejected under 35 USC 112, 2nd paragraph, for their dependency upon claim 1.
The claim 1 recites “A management device configured to manage a digital key that is registered in a mobile information terminal…” .This device is configured to “manage a digital key”, that is a function of such device. While the claim later states that the device comprises a processor configured to…issuing a password, the claim does not provide a discernable boundary to what perform the function of “manage a digital key”. The claim does not provide a discernable boundary on what performs the function e.g. processor.
Claims 2-6 do not cure the deficiency of claim 1 and are rejected under 35 USC 112, 2nd paragraph, for their dependency upon claim 1.
Specification
The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed.
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 of this title, 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 set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied 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.
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 of this title, 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.
Frist set of rejections:
Claims 1-3 , 5, and 7-8 are rejected under 35 U.S.C. 103 as being unpatentable over US Patent No. 2014/0232520 issued to Kawamura, and in view of US Patent Application No. (2023/0288924) issued to IKEDA ( filed in IDS 11/29/2024) .
Regarding claim 1, Kawamura discloses a management device configured to manage a digital key that is registered in a mobile information terminal to operate a vehicle, the management device comprising a processor configured to execute a process for
[0034-0037] The management center 17 includes a vehicle database 24, an ECU database 25, a key database 26, and an operator database 27. Although not illustrated, the management center 17 includes a computer or processor, for example, a server, that controls the processing performed in the management center 17. The vehicle ID, the ECU ID, the electronic key ID, and the operator ID are stored in the vehicle database 24 associated with one another. The ECU ID and the ECU code are stored in the ECU database 25 associated with each other. The electronic key ID and the encryption code are stored in the key database 26 associated with each other. An operator ID, which is unique to the operator, and a password are stored in the operator database 27 associated with each other. The management center 17 also stores an encryption algorithm 28, which is the same as that stored in the verification ECU 4… The management center 17 further includes an operator verification unit 32 that verifies the operator during key registration, a registration control unit 33 that controls key registration, and a data update unit 34 that reflects a key registration result to the databases 24 to 27 after key registration is completed. The operator verification unit 32 refers to the operator database 27 to verify the operator using the operator ID input during key registration.
[0039-0048] (I) Factory Registration (Initial Registration) , Referring to FIG. 4, an electronic key 2a is initially registered to the vehicle (verification ECU 4) using the registration tool 16, which is provided in, for example, a vehicle factory 35. Prior to the factory registration (initial registration), an electronic key ID "ID-1", a SEED code "SEED-1f", and an encryption code "K-1" are written beforehand to the memory 12a of the electronic key 2a…. In step S105, the ECU registration unit 29 transmits a SEED code delete request to the electronic key 2a through LF band bidirectional near-field wireless communication. When the key registration unit 31a receives the SEED code delete request from the verification ECU 4, the key registration unit 31a deletes the SEED code "SEED-1f" from the SEED code storage region of the memory 12a… Optionally, in step S106, when the ECU registration unit 29 receives a request for deleting a factory registering function from the registration tool 16…The data update unit 34 writes the vehicle ID ".alpha.", the ECU ID "ID-A", the electronic key ID "ID-1", and the operator ID "factory" (factory registration) to the vehicle database 24 in association with the registration information acquired from the registration tool 16].
[0086-0092] (IV-2) Online Key Reregistration, Referring to FIG. 9, when network communication is available, electronic keys may be reregistered online to the verification ECU 4s, which has replaced the old verification ECU 4, in the vehicle 1 using the registration tool 16, which is provided in, for example, the vehicle dealer 37. The reregistration of the electronic key 2a will now be described. In step S601, the operator inputs a command to the registration tool 16 to start key reregistration. In this case, the operator inputs an operator ID "ID-U1", a password "PW-1", and a vehicle ID ".alpha.", which is marked on the vehicle body, to the registration tool 16. In step S602, the registration tool 16 transmits the operator ID "ID-U1", the password "PW-1", and the vehicle ID ".alpha.", which are marked to the vehicle body, to the registration tool 16 through network communication. The operator verification unit 32 verifies the operator when the operator ID "ID-U1" and the password "PW-1" acquired from the registration tool 16 are associated with each other in the operator database 27. Then, when the operator verification unit 32 verifies the operator, the operator verification unit 32 transmits an operator verification accomplishment notification to the registration tool 16 through network communication. In step S603, the registration tool 16 transmits a key reregistration command to the verification ECU 4 through wire-connected communication in response to the operator verification accomplishment notification. In step S604, the ECU registration unit 29s reads the electronic key ID from the electronic key 2a through LF band bidirectional near-field wireless communication. More specifically, the ECU registration unit 29s transmits a key information acquisition request to the electronic key 2a. When the key registration unit 31a receives the key information acquisition request from the verification ECU 4s, the key registration unit 31a reads the electronic key ID "ID-1" from the memory 12a. Then, the key registration unit 31a sends the electronic key ID "ID-1" to the vehicle 1. The ECU registration unit 29s writes the electronic key ID "ID-1" acquired from the electronic key 2a to a storage region of the memory 9s. In this case, the electronic key ID "ID-1" may be written to any one of a factory registration storage region and an additional registration storage region. In step S605, the ECU registration unit 29s transmits the electronic key ID "ID-1" from the registration tool 16 to the management center 17 through network communication together with the ECU ID "ID-C", which has already been stored in the memory 9s, and the vehicle ID ".alpha.", which has been input to the registration tool 16 in step S601.
While Kawamura discloses the limitation issuing a password on a condition
as: [0039-0048] (I) Factory Registration (Initial Registration) , Referring to FIG. 4, an electronic key 2a is initially registered to the vehicle (verification ECU 4) using the registration tool 16, which is provided in, for example, a vehicle factory 35. Prior to the factory registration (initial registration), an electronic key ID "ID-1", a SEED code "SEED-1f", and an encryption code "K-1" are written beforehand to the memory 12a of the electronic key 2a…. In step S105, the ECU registration unit 29 transmits a SEED code delete request to the electronic key 2a through LF band bidirectional near-field wireless communication. When the key registration unit 31a receives the SEED code delete request from the verification ECU 4, the key registration unit 31a deletes the SEED code "SEED-1f" from the SEED code storage region of the memory 12a… Optionally, in step S106, when the ECU registration unit 29 receives a request for deleting a factory registering function from the registration tool 16…The data update unit 34 writes the vehicle ID ".alpha.", the ECU ID "ID-A", the electronic key ID "ID-1", and the operator ID "factory" (factory registration) to the vehicle database 24 in association with the registration information acquired from the registration tool 16].
However, does not explicitly disclose, and IKEDA discloses issuing a password on a condition
as :
[0037-0039] FIG. 3 is a block diagram illustrating an example of a functional configuration of the management server 20. The management server 20 includes, as a functional configuration, a digital key generating section 211, a transmission/reception control section 212, and an information management section 213. These are implemented by the CPU 21A reading and executing a program stored in the ROM 21B.The digital key generating section 211 generates a digital key used by a user when using a vehicle of the system 10. The digital key generating section 211 is capable of setting an expiration date for the generated digital key. The transmission/reception control section 212 controls the wireless communication I/F 21E. The wireless communication I/F 21E, which is controlled by the transmission/reception control section 212, is capable of recording data, received from an outside, in the ROM 21B and the storage 21D. Moreover, the wireless communication I/F 21E, which is controlled by the transmission/reception control section 212, is capable of wirelessly transmitting a digital key generated by the digital key generating section 211 to a vehicle of the system 10 and a portable device of a user, and of wirelessly transmitting data recorded in the ROM 21B and the storage 21D to an outside.
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the teaching of Kawamura by incorporating “management server which includes a digital key generating section capable of setting expiration date ”, as taught by IKEDA. One could have been motivated to do so in order to generates a digital key used by a user when using a vehicle of the system , where the CPU of ECU processes the confirmation of whether the digital key recorded every time a predetermined period of time elapses. [ IKEDA, 0094-0101].
Regarding claim 2, Kawamura discloses, wherein the processor is configured to execute a process for transmitting the issued password to a digital key application that the mobile information terminal of the vehicle owner has.
While Kawamura discloses this limitation as: [0034] The management center 17 includes a vehicle database 24, an ECU database 25, a key database 26, and an operator database 27. Although not illustrated, the management center 17 includes a computer or processor, for example, a server, that controls the processing performed in the management center 17. The vehicle ID, the ECU ID, the electronic key ID, and the operator ID are stored in the vehicle database 24 associated with one another. The ECU ID and the ECU code are stored in the ECU database 25 associated with each other. The electronic key ID and the encryption code are stored in the key database 26 associated with each other. An operator ID, which is unique to the operator, and a password are stored in the operator database 27 associated with each other. The management center 17 also stores an encryption algorithm 28, which is the same as that stored in the verification ECU 4.
[0052] In step S201, the operator inputs a command to the registration tool 16 to start additional registration. In this case, the operator inputs an operator ID "ID-U1", a password "PW-1", and the vehicle ID ".alpha.", which is marked on the vehicle body, to the registration tool 16.
[0053] In step S202, the registration tool 16 transmits the operator ID "ID-U1" and the password "PW-1" to the management center 17 through network communication. The operator verification unit 32 verifies the operator when the operator ID "ID-U1" and the password "PW-1" acquired from the registration tool 16 are associated with each other in the operator database 27. Then, when the operator verification unit 32 verifies the operator, the operator verification unit 32 transmits an operator verification accomplishment notification to the registration tool 16 by performing network communication.
Furthermore, IKEDA discloses this limitation as:[ 0039] The transmission/reception control section 212 controls the wireless communication I/F 21E. The wireless communication I/F 21E, which is controlled by the transmission/reception control section 212, is capable of recording data, received from an outside, in the ROM 21B and the storage 21D. Moreover, the wireless communication I/F 21E, which is controlled by the transmission/reception control section 212, is capable of wirelessly transmitting a digital key generated by the digital key generating section 211 to a vehicle of the system 10 and a portable device of a user, and of wirelessly transmitting data recorded in the ROM 21B and the storage 21D to an outside.
Regarding claim 3, Kawamura discloses, wherein the digital key application includes a first application and a second application, the processor is configured to transmit the issued password to the first application, and the issued password is automatically input from the first application into the second application.
[see FIGS 2A-2C and corresponding text for more details,[ 0030] FIGS. 2A to 2C illustrate the electronic key registration system 15 that registers the electronic key 2 to the vehicle 1. In the present example, the electronic key registration system 15 includes the vehicle 1 (verification ECU 4), the electronic key 2, a registration tool 16, and a management center 17. The registration process of the electronic key 2 (hereafter also referred to as key registration) is classified into factory registration serving as area-limited registration (refer to FIG. 2A), online registration (refer to FIG. 2B), and offline registration (refer to FIG. 2C). Factory registration is performed when initially registering the electronic key 2 to the vehicle 1 in a factory. Online registration is performed when registering the electronic key 2 to the vehicle 1 by accessing a network. Offline registration is performed when registering the electronic key 2 to the vehicle 1 without accessing a network.
Regarding claim 5, Kawamura discloses, wherein the digital key application includes a first application and a second application, the processor is configured to transmit the issued password to the first application, in response to receipt of data from the mobile information terminal to which the address has been transmitted, and the issued password is automatically input from the first application into the second application.
[see FIGS 2A-2C and corresponding text for more details,[ 0030] FIGS. 2A to 2C illustrate the electronic key registration system 15 that registers the electronic key 2 to the vehicle 1. In the present example, the electronic key registration system 15 includes the vehicle 1 (verification ECU 4), the electronic key 2, a registration tool 16, and a management center 17. The registration process of the electronic key 2 (hereafter also referred to as key registration) is classified into factory registration serving as area-limited registration (refer to FIG. 2A), online registration (refer to FIG. 2B), and offline registration (refer to FIG. 2C). Factory registration is performed when initially registering the electronic key 2 to the vehicle 1 in a factory. Online registration is performed when registering the electronic key 2 to the vehicle 1 by accessing a network. Offline registration is performed when registering the electronic key 2 to the vehicle 1 without accessing a network.
Regarding claims 7, and 8, these claims are interpreted and rejected for the same rational set forth in claim 1.
Claims 4, and 6 are rejected under 35 U.S.C. 103 as being unpatentable over US Patent No. 2014/0232520 issued to Kawamura, ( US) in view of US Patent Application No. (2023/0288924) issued to IKEDA ( filed in IDS filed on 11/26/2024) , and further in view of Krishnan ( US2018/0065598).
Regarding claim 4, IKEDA does not explicitly disclose wherein the processor is configured to execute a process for transmitting an address of a home page to a mail account of the vehicle owner, and the home page is for automatically inputting the issued password into a digital key application that the mobile information terminal of the vehicle owner has.
While Kawamura discloses: [0034-0037]… An operator ID, which is unique to the operator, and a password are stored in the operator database 27 associated with each other. …[, and [0086-0092]… In this case, the operator inputs an operator ID "ID-U1", a password "PW-1", and a vehicle ID ".alpha.", which is marked on the vehicle body, to the registration tool 16. In step S602, the registration tool 16 transmits the operator ID "ID-U1", the password "PW-1", and the vehicle ID ".alpha.", which are marked to the vehicle body, to the registration tool 16 through network communication. The operator verification unit 32 verifies the operator when the operator ID "ID-U1" and the password "PW-1" acquired from the registration tool 16 are associated with each other in the operator database 27…
Furthermore, Krishnan discloses: [0021-0022] As shown at step 24, if the customer accepts the form provided by the rental company, the rental company verifies the acceptance and transmits a digital key for the selected keyless vehicle to the user by sending an email to the user's smartphone 15 as shown at step 26. The digital key may be attached to the email. Alternatively, as shown at step 28, the email may configure to download and install the program or app on user's smartphone 15 whereby the user's smartphone 15 is configured to accept a digital key corresponding to the keyless rental vehicle selected by the user 5 at step 18. As shown at step 30, the customer 5 accepts the email and downloads the digital key for the selected keyless vehicle 2 onto the user's smartphone 15…, the rental car company may provide a website that permits entry of credit card information, driver's license information, information concerning available vehicles, etc., and the website, may permit user selection of a vehicle whereby a website causes and email including the digital key for a selected keyless vehicle to be emailed to the user's smartphone 15.
[Abstract, A method of operating/renting keyless motor vehicles includes configuring a user's smartphone to wirelessly communicate with the security systems of at least a selected keyless vehicle, whereby the user's smartphone can transmit a digital key to the security system of a keyless vehicle to permit operation thereof. A digital key for a selected keyless vehicle is transmitted to the user's smartphone, and the user is provided with an authorization code that can be used to gain entry into the selected vehicle. The user enters the authorization code using the user input device of the selected keyless vehicle, and the user's smartphone then transmits the digital key to the security system of the selected keyless vehicle. The user can enter and operate the selected vehicle without receiving a conventional key and/or key fob.
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the teaching of Kawamura, and IKEDA by incorporating “company’s website and digital key attached to email”, as taught by Krishnan. One could have been motivated to do so in order to whereby a website causes and email including the digital key for a selected keyless vehicle to be emailed to the user's smartphone . Where the email may be configured to download and install the program or app on user's smartphone whereby the user's smartphone is configured to accept a digital key corresponding to the keyless rental vehicle selected by the user [ Krishnan, [0021-22]].
Regarding claim 6, IKEDA does not explicitly disclose, wherein the processor is configured to execute a process for transmitting the issued password to a mail account of the vehicle owner.
While Kawamura discloses: [0034-0037]… An operator ID, which is unique to the operator, and a password are stored in the operator database 27 associated with each other. …[, and [0086-0092]… In this case, the operator inputs an operator ID "ID-U1", a password "PW-1", and a vehicle ID ".alpha.", which is marked on the vehicle body, to the registration tool 16. In step S602, the registration tool 16 transmits the operator ID "ID-U1", the password "PW-1", and the vehicle ID ".alpha.", which are marked to the vehicle body, to the registration tool 16 through network communication. The operator verification unit 32 verifies the operator when the operator ID "ID-U1" and the password "PW-1" acquired from the registration tool 16 are associated with each other in the operator database 27…
Furthermore, Krishnan discloses: [0021-0022] As shown at step 24, if the customer accepts the form provided by the rental company, the rental company verifies the acceptance and transmits a digital key for the selected keyless vehicle to the user by sending an email to the user's smartphone 15 as shown at step 26. The digital key may be attached to the email. Alternatively, as shown at step 28, the email may configure to download and install the program or app on user's smartphone 15 whereby the user's smartphone 15 is configured to accept a digital key corresponding to the keyless rental vehicle selected by the user 5 at step 18. As shown at step 30, the customer 5 accepts the email and downloads the digital key for the selected keyless vehicle 2 onto the user's smartphone 15…, the rental car company may provide a website that permits entry of credit card information, driver's license information, information concerning available vehicles, etc., and the website, may permit user selection of a vehicle whereby a website causes and email including the digital key for a selected keyless vehicle to be emailed to the user's smartphone 15.
[Abstract, A method of operating/renting keyless motor vehicles includes configuring a user's smartphone to wirelessly communicate with the security systems of at least a selected keyless vehicle, whereby the user's smartphone can transmit a digital key to the security system of a keyless vehicle to permit operation thereof. A digital key for a selected keyless vehicle is transmitted to the user's smartphone, and the user is provided with an authorization code that can be used to gain entry into the selected vehicle. The user enters the authorization code using the user input device of the selected keyless vehicle, and the user's smartphone then transmits the digital key to the security system of the selected keyless vehicle. The user can enter and operate the selected vehicle without receiving a conventional key and/or key fob.
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the teaching of Kawamura, and IKEDA by incorporating “company’s website and digital key attached to email”, as taught by Krishnan. One could have been motivated to do so in order to whereby a website causes and email including the digital key for a selected keyless vehicle to be emailed to the user's smartphone . Where the email may be configured to download and install the program or app on user's smartphone whereby the user's smartphone is configured to accept a digital key corresponding to the keyless rental vehicle selected by the user [ Krishnan, [0021-22]].
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.
Claims 1, and 7-8 are rejected under 35 U.S.C. 102(a) (1) as being anticipated by MATSUSHITA Suguru (WO2023054298) which corresponds. US 20240227733 A1. The claim is mapped with WO2023054298 application.
Second set of rejections:
Regarding claim 1, MATSUSHITA discloses “A management device (processor) managing a digital key registered in a mobile information terminal to operate a vehicle”
Matsushita discloses a Digital Key Server (DKS 3) that generates service keys (owner/guest), distributes them to mobile terminals, and manages key-related data and operations using a data processing unit/server processor (see ¶[0028-29]; description of DKS, FIG.5; data processing unit 30 and server processor 301 ¶¶[0077]–[0079]; functional units G1–G6 ¶[0087]).
Matsushita discloses that owner and guest service keys are stored in mobile terminals and managed by DKS (owner key and guest key definitions ¶[0037]–[0040]; issuance and storage in terminal memory ¶¶[0118]–[0125], FIGs.12–14).
“Issuing a password on a condition that an owner key that is a digital key registered in the mobile information terminal of an owner is deleted from the mobile information terminal”
Matsushita teaches deletion flows initiated by an owner via the owner terminal and processed by the DKS: owner key deletion request → DKS transmits vehicle owner deletion package and deletion commands to related terminals and initiates deletion (see owner deletion sequence ¶¶[0200]–[0212]; Fig.29 steps T11–T18; Fig.30 steps T21–T24). These passages show DKS-initiated message generation and transmission in response to owner-initiated deletion, i.e., the DKS issues data/commands upon the deletion event.
Matsushita further teaches that the DKS issues registration/unlock codes and registration packages used in owner-registration operations (terminal registration package, vehicle registration package, vehicle check codes, terminal check codes) (see ¶¶[0118]–[0126], FIG.13 S14–S17, FIG.14 S28). In particular, the DKS (or associated tools) issues a “security unlock signal/code” that switches the authentication ECU into an owner-registration enable mode on request (¶¶[0128]–[0132], Fig.14 S21–S22).
Under a broad reading of “issues a password on a condition that the owner key is deleted” and the later teachings of Matsushita’s disclosure of (a) DKS-generated/deletion-related packages and (b) DKS issuance of registration/unlock codes supports the mapping that the DKS (management device) issues a code/password in the context of a delete-then-reregister sequence (¶¶[0202]–[0212]; ¶¶[0156]–[0166]).
“The issued password is needed to reregister the owner key”
Matsushita discloses that the authentication ECU will not accept owner registration unless it has been placed in owner-registration enable mode (owner registration prohibition/enable modes; ECU shifts to owner registration mode based on security unlock signal/code) (¶¶[0122]–[0132]; FIG.14 S21–S22). The security unlock code is required to enable owner registration into the vehicle.
Matsushita also discloses that the DKS issues vehicle registration packages and/or vehicle registration data which are transferred via mobile terminal to the authentication ECU to complete registration (¶¶[0122]–[0126], FIG.13 S16–S17, FIG.14 S28). Thus, the reference teaches that certain codes/signals issued by the system are prerequisites for owner registration (i.e., required to allow owner-key registration to proceed), which maps to the claimed requirement that the issued password be needed to reregister the owner key.
Regarding claims 7, and 8, these claims are interpreted and rejected for the same rational set forth in claim 1.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
See 892 for more relevant references.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SHAHRIAR ZARRINEH whose telephone number is (571)272-1207. The examiner can normally be reached Monday-Friday, 8:30am-5:30pm.
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, Jorge Ortiz-Criado can be reached at 571-272-7624. 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.
/SHAHRIAR ZARRINEH/Primary Examiner, Art Unit 2496
Prosecution Insights