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 .
Response to Amendment
2. This is in response to the amendments filed on 05/11/2026. Claims 1-21 are currently pending and have been considered below.
Double Patenting rejection to the claim 1 has been reconsidered and withdrawn.
Response to Arguments
3. Applicant’s arguments filed on 05/11/2026 have been fully considered but they are not persuasive. On the Remarks, Applicant argues that;
the activation code of Doyon comes from the server, which is remote to the security device 105, as claim 1 clearly recites that the secret code is stored on the camera itself, the approaches are different.
the stated motivation to combine Doyon with Ramesh is improper.
The examiner respectfully disagrees.
First, in response to applicant's argument that the activation code of Doyon comes from the server, which is remote to the security device 105, as claim 1 clearly recites that the secret code is stored on the camera itself, the approaches are different, it is noted that, DOYON at FIG. 3A/Para.0069 discloses, “The security device 105…. is an IP camera …. which comprise…. The storage 315…. comprise memory for storing …. an activation code” which the examiner interpreted as being the claimed “secret information stored by the camera”. From FIG.3A of DOYON, it is clearly indicated that storage 315 resides within security device 105/an IP camera. Also, DOYON at Abstract discloses, “for registering … security devices such as IP cameras to a security server ….. server is provided … to request and receive an activation code for the security device… The Security device authenticates itself based on the activation code”, which the examiner interpreted as being the claimed “the secret information used for enrolling the camera with the VMS". Thus, from these two citations, it is clear that the claimed ‘the secret information’ is equivalent to ‘the activation code’ of DOYON. The activation code of DOYON is stored within storage 315 which resides within the security device 105/an IP camera.
Second, in response to applicant's argument that the stated motivation to combine Doyon with Ramesh is improper, first, it is noted that, DOYON at Para.0023, Abstract discloses “establish a first network connection over the network …. with a …. computing device”, “registering …. security devices such as IP cameras …. over a ….. network ….. using a computing device ….” which the examiner interpreted as being the claimed “establishing a first browser-based connection over the network to the camera". Also, DOYON at Para.0405, Para.0387, Para.0388, Para.0162, Para.0120 discloses; “the Enrolment Service to register the device…. URL …. found in the configuration.xml file”, “the configuration file template can be …. Configuration.xml”, “….the configurations needed by the CBVSS ….to establish the communication …..”, “A set of HTML pages ….. used …. to activate the camera in the CBVSS”, “video surveillance system (CBVSS)…. record and playback IP devices over the Internet” which the examiner interpreted as being the claimed “accessing, over the browser-based connection, a configuration page hosted by the camera". Also, DOYON discloses the claimed “…. secret information stored by the camera, the secret information used for enrolling the camera with the VMS;” [disclosed in the above citations]. In addition, DOYON at Para.0023 discloses; “establish a second network connection over the network … with the security device”, which the examiner interpreted as being the claimed “launching, ….. a second browser-based connection …… ".
Finally, it is noted that, Ramesh at Para.0014, Para.0099 discloses; “The server is programmed or configured ….. associated with a payment device of a user….to generate a unique uniform resource locator (URL) associated with the payment device…...”, “user …. access payment device data of a payment device …. through a …. communication channel …. (e.g., by opening a browser …. of the ….URL)”, which the examiner interpreted as being the claimed “…. using the link, a ….browser-based connection to the configuration site". Also, Ramesh at Para.0014 discloses; ‘”The server is … configured to generate a unique uniform resource locator (URL) associated with the payment device….. the …URL accessible by a …. user. The server is …. configured to…. verify an identity of the user ….”, which the examiner interpreted as being the claimed “authenticating the ….. browser-based connection to the configuration site", as the server is configured to generate a unique uniform resource locator (URL) associated with the payment device and the URL accessible by a user, when the identity of the user is verified, it is equivalent to the claimed ‘authenticating the browser-based connection to the configuration site’. In addition, Ramesh at Para.0078, Para.0088, Para.0083 discloses; “a client device” ….. used by a user…a client device …. configured to communicate with …. networks and initiate communications”, “Client device ….. communicate ….. through a ….. communication channel”, “user …. enroll themselves ….. in a communication channel (e.g., …. Email…. etc.) ….”, which the examiner interpreted as being the claimed “…. an enrollment ……obtained from the configuration site over the …..browser-based connection….. ".
It is clearly indicated that DOYON and Ramesh disclose all the limitations in claim 1 and a proper primafacie case of obviousness has been established by combining the references of DOYON and Ramesh. Therefore, the rejection of such is sustained below.
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.
4. Claims 1-3,5-21 are rejected under AIA 35 U.S.C. 103 as being unpatentable over DOYON et al (US 20210111895 A1) in view of Ramesh et al. (US 20230085031 A1)
Regarding Claim 1:
DOYON discloses:
a. A method for enrolling a camera into a video management system (VMS), (Claim 62, Abstract, Para.0120; “A method for enrolling a … security device”, “registering …. security devices such as IP cameras”, “video surveillance system …. record and playback IP devices over the Internet”) the camera and the VMS being connected to a common network, (Para.0120, Para.0055; “video surveillance system (CBVSS) ….record and playback IP devices over the Internet”, video surveillance system (CBVSS) is construed as video management system (VMS), “the security device 105 is a security camera that comprises a video sensor …. is configured to communicate over a network … the security device is an IP camera”) the method comprising:
b. establishing a first browser-based connection over the network to the camera; (Para.0023, Abstract; “establish a first network connection over the network …. with a …. computing device”, “registering …. security devices such as IP cameras …. over a ….. network ….. using a computing device ….”)
accessing, over the browser-based connection, a configuration page hosted by the camera; (Para.0405, Para.0387, Para.0388, Para.0162, Para.0120; “the Enrolment Service to register the device…. URL …. found in the configuration.xml file”, “the configuration file template can be …. Configuration.xml”, “….the configurations needed by the CBVSS ….to establish the communication …..”, “A set of HTML pages ….. used …. to activate the camera in the CBVSS”, “video surveillance system (CBVSS)…. record and playback IP devices over the Internet”)
displaying a graphical-user interface (GUI) of the configuration page, (Para.0138, Para.0130, Abstract, Para.0131; “Device connects to the CBVSS and …. configure …. settings in the CBVSS web interface”, “to add a camera in the CBVSS”, “registering …. security devices such as IP cameras”, “configures IP Settings …. through the device web interface or an installation wizard tool”) the GUI comprising at least one interactive GUI element; (Para.0073, Para.0133; “the enrollment web page …. displayed at the computing device … the web page includes a “get activation code” button, clicking on which results in a ….”, “clicks on “Get an activation code” and a new tab opens with the CBVSS enrollment pages”)
detecting user interaction with an enrollment GUI element of the configuration page; (Para.0392, Para.0277, Para.0397; “Click on “Get an activation code for …. camera”, “The CBVSS activation web pages is … HTML pages …. to … enrollment of a device in the CBVSS”, “The Enrolment ….URL ….. found in the configuration.xml file”)
c. accessing, responsive to the detecting, secret information stored by the camera, the secret information used for enrolling the camera with the VMS; (Para.0074, Para.0069, Abstract; “based on the detection of a click on the “get activation code” button, the security device 105, establishes communication …. by accessing ….an activation web page URL …..”, “The security device …. is an IP camera …. which comprise…. The storage …. for storing …. an activation code”, ‘for registering ….. security devices such as IP cameras ….. receive an activation code ….. The Security device authenticates itself based on the activation code” the claimed ‘the secret information’ is equivalent to ‘the activation code’ of DOYON. The activation code of DOYON is stored within storage 315 which resides within the security device 105/an IP camera)
obtaining, from the configuration page in response to the user interaction, …..associated with the VMS, ….comprising at least part of the secret information; (Para.0394, Para.0397; “Click on “Enroll” to launch the enrollment progress and to get an activation code”, “The Enrolment ….URL ….. found in the configuration.xml file”)
d. launching, ….. a second browser-based connection …… (Para.0023; “establish a second network connection over the network … with the security device”)
…. the second browser-based connection (disclosed above) …..
e. ….. authenticating, providing, ….. the at least part of the secret information to the VMS (Claim.62, Para.0079, Para.0022; “enrolling a ….security device with an enrollment server…. receiving, at the enrollment server, the activation code from the security device…..”, “Upon successful authentication of the connection…/user…. the enrollment server ….. knows that …. the connection…. has been authenticated….”, “establishing network communication between the security device and the …. server using the surveillance connection …..”surveillance connection between security device and server is within the VMS/ video surveillance system which record and playback IP devices over the Internet) …..
causing the VMS to enroll the camera using the at least part of the secret information ….. (Claim.62; “enrolling the security device with the enrollment server ….. that the security device has been authenticated when the activation code received …..”) and
displaying an enrollment confirmation obtained ….. over the second ….. connection in response to the camera being enrolled with the VMS. (Para.0095, Para.0094, Claim.62; “Once the security device 105 is ….registered …. establish communication ….and transmit ….a confirmation that the security device 120 …. registered, e.g. to be displayed …. at the computer …..”, “the security device with ….secondary…. connection …. for connecting to the ….. server”, ‘enrolling the security device …. by creating a …. indication that the security device has been authenticated”)
however, DOYON does not explicitly disclose:
c. … a link to a configuration site…. [DOYON discloses ‘obtaining, from the configuration page in response to the user interaction, …..associated with the VMS, ….. comprising at least part of the secret information;’, but DOYON does not disclose …a link to a configuration site…..]
d. …. using the link, a ….browser-based connection to the configuration site;
authenticating the …..browser-based connection to the configuration site; [DOYON discloses ‘launching, ….. a second browser-based connection …. ‘, but DOYON does not disclose ‘……using the link, a ….browser-based connection to the configuration site; authenticating the …..browser-based connection to the configuration site…..’]
e. after the ….. providing, by the link, the at least part of the …. information to the …. via the …..browser-based connection;
….. using the at least part of the …..information comprised in the link;
…. an enrollment ……obtained from the configuration site over the …..browser-based connection…..[DOYON discloses ‘…. authenticating, providing, ….. the at least part of the secret information to the VMS…. causing the VMS to enroll the camera using the at least part of the secret information…… displaying an enrollment confirmation obtained ….. over the second ….. connection in response to the camera being enrolled with the VMS ‘, but DOYON does not disclose ‘after the …. providing, by the link, the at least part of the …. information to the …. via the …..browser-based connection; ….. using the at least part of the …..information comprised in the link;…. an enrollment ……obtained from the configuration site over the …..browser-based connection…..’]
In an analogous reference Ramesh discloses:
c. … a link to a configuration site….(Para.0014, Para.0099; “The server is programmed or configured ….. associated with a payment device of a user….to generate a unique uniform resource locator (URL) associated with the payment device…...”, “user …. access payment device data of a payment device …. through a …. communication channel …. (e.g., by opening a browser …. of the ….URL)”)
d. …. using the link, a ….browser-based connection to the configuration site; (Para.0014, Para.0099; “The server is programmed or configured ….. associated with a payment device of a user….to generate a unique uniform resource locator (URL) associated with the payment device…...”, “user …. access payment device data of a payment device …. through a …. communication channel …. (e.g., by opening a browser …. of the ….URL)”)
authenticating the ….. browser-based connection to the configuration site; (Para.0014; ‘”The server is … configured to generate a unique uniform resource locator (URL) associated with the payment device….. the …URL accessible by a …. user. The server is …. configured to…. verify an identity of the user ….” as the server is configured to generate a unique uniform resource locator (URL) associated with the payment device and the URL accessible by a user, when the identity of the user is verified, it is construed as authenticating the browser-based connection to the configuration site)
e. after the …., providing, by the link, the at least part of the …. information to the …. via the …..browser-based connection; (Para.0121, Para.0008; “after generating the unique user token….. may transmit the unique user token to the client device ….. through the …. communication channel”, “…. a unique user token associated with the user”)
…..using the at least part of the ….. information comprised in the link; (Para.0121; “…. transmit the unique user token to the client device ….. through the …. communication channel”)
…. an enrollment ……obtained from the configuration site over the …..browser-based connection….. (Para.0078, Para.0088, Para.0083; “a “client device” ….. used by a user…a client device …. configured to communicate with …. networks and initiate communications”, “Client device ….. communicate ….. through a ….. communication channel”, “user …. enroll themselves ….. in a communication channel (e.g., …. Email…. etc.) ….”)
Before the effective filing date of the claimed invention, it would have been obvious to one with ordinary skill in the art to modify DOYON’s method for establishing a secure connection between a network-enabled security device and a security server by enhancing DOYON’s method to include Ramesh’s method of verifying an identity of the user.
The motivation: when a server is configured to generate a uniform resource locator (URL) associated with a client device and a user, the identity of the user is verified as well as the URL accessible by a client device of the user.
With respect to independent claim 15, a corresponding reasoning was given earlier in this section with respect to claim 1; therefore, claim 15 rejected, for similar reasons, under the grounds as set forth for claim 1.
Regarding Claim 2:
DOYON in view of Ramesh discloses:
The method of claim 1, wherein said establishing of the first browser-based connection comprises connecting to the camera via an IP address associated therewith. (DOYON, Para.0021, Para.0074; “for establishing a …. connection between a …... security device and a … server ….. over a first network connection …...”, “…. using a web browser…. e.g. including an IP address or URL…... the security device …. establishes communication with the …..server by accessing ….. web page URL”)
Regarding Claim 3:
DOYON in view of Ramesh discloses:
The method of claim 1, comprising …. the first browser-based connection to the camera …... (DOYON, Para.0023, Abstract; “establish a first network connection over the network …. with a …. computing device”, “registering …. security devices such as IP cameras …. over a ….. network ….. using a computing device ….”)
authenticating the ….browser-based connection …. by supplying access credentials to the ……(Ramesh, Para.0014, Para.0100; ‘”The server is … configured to generate a unique uniform resource locator (URL) associated with the payment device….. the …URL accessible by a …. user. The server is …. configured to…. verify an identity of the user ….”, “verify the identity of the user …..executing a step-up authentication ….. include a one-time password…..The one-time password ….. verified at ……”)
Regarding Claim 5:
DOYON in view of Ramesh discloses:
The method of claim 3, wherein said …. the second browser-based connection to the …… VMS. (DOYON, Para.0023, Para.0120; ‘establish a second network connection over the network … with the security device”, “video surveillance system (CBVSS) that can record and playback IP devices over the Internet”)
….. authenticating of the …. browser-based connection to the configuration site comprises supplying the access credentials to the configuration site …… (Ramesh, Para.0014, Para.0100; ‘”The server is … configured to generate a unique uniform resource locator (URL) associated with the payment device….. the …URL accessible by a …. user. The server is …. configured to…. verify an identity of the user ….”, “verify the identity of the user …..executing a step-up authentication ….. include a one-time password…..The one-time password ….. verified at ……”)
Regarding Claim 6:
DOYON in view of Ramesh discloses:
The method of claim 1, wherein said launching of the second browser-based connection to the VMS comprises launching the second browser-based connection over the Internet. (DOYON, Para.0023; “establish a second network connection over the network …. with the security device……the data received from the security device”)
Regarding Claim 7:
DOYON in view of Ramesh discloses:
The method of claim 1, wherein said authenticating of the second browser-based connection to the VMS comprises authenticating a user via a single sign-on (SSO) process. (DOYON, Para.0032, Abstract, Para.0088; “log on screen provided by the security device via which a user may be authenticated…. for ….. registering a security device”, “The Security device authenticates itself based on the activation code”, “the activation code …. is a single-use activation code…. for activating a single security device only once”)
Regarding Claim 8:
DOYON in view of Ramesh discloses:
The method of claim 1, wherein launching the second browser-based connection comprises selecting, on the configuration site associated with the VMS, one of a plurality of surveillance systems. (DOYON, Para.0054, Para.0022; “plurality of …. servers”, “surveillance communication between a …..security device and a …. server”)
Regarding Claim 9:
DOYON in view of Ramesh discloses:
The method of claim 1, comprising, after the authenticating, providing additional information for use in at least one of enrollment of the camera …… to the VMS (DOYON, Para.0084, Claim.62; “the security device transmits to the ….. server the activation code ….as wells as device data ….(e.g. MAC address, serial number, public key) is exchanged that allows, once the security device ….. is authenticated”, “for enrolling a …. security device with an …..server”) ……
….. configuration of the …. subsequent to enrollment thereof to the ….. (Ramesh, Para.0134, Para.0144; “User …. initiate issuance of a new payment device that will be subsequently enrolled …..”, “The payment device …… configured”) via the configuration site.(Para.0014; “The server is …. configured …. a payment device of a user. The server is …. configured to generate a unique uniform resource locator (URL) associated with the payment device”)
With respect to dependent claim 16, a corresponding reasoning was given earlier in this section with respect to claim 9; therefore, claim 16 rejected, for similar reasons, under the grounds as set forth for claim 9.
Regarding Claim 10:
DOYON in view of Ramesh discloses:
The method of claim 9, wherein said providing of the additional information for the camera to the VMS comprises detecting further user interaction ……and providing, based on the further user interaction, the additional information. (DOYON, Para.0010; “the …. server provides the user with an activation code…. valid only for a certain period of time. The user may also provide details of the security device, e.g. a serial number or MAC address”)
….user interaction with the configuration site (Ramesh, Para.0014; “The server is …. configured to receive a data access request from the client device via the ….URL through a …… communication channel”)
With respect to dependent claim 17, a corresponding reasoning was given earlier in this section with respect to claim 10; therefore, claim 17 rejected, for similar reasons, under the grounds as set forth for claim 10.
Regarding Claim 11:
DOYON in view of Ramesh discloses:
The method of claim 9, wherein said accessing, responsive to the detecting, comprises accessing the additional information stored by the camera. (DOYON, Claim.76, Abstract; “the unique device identifier is a serial number of the security device, a MAC address of the security device, or an IP address of the security device.”, “security devices such as IP cameras”)
With respect to dependent claim 18, a corresponding reasoning was given earlier in this section with respect to claim 11; therefore, claim 18 rejected, for similar reasons, under the grounds as set forth for claim 11.
Regarding Claim 12:
DOYON in view of Ramesh discloses:
The method of claim 11, wherein said providing of the additional information for the camera to the VMS comprises providing, by the link, the additional information. (DOYON, Para.0080; “the serial number…. IP address, and/or MAC address are provided, ….by the security device ….when requesting the activation web page ….using REST API”)
With respect to dependent claim 19, a corresponding reasoning was given earlier in this section with respect to claim 12; therefore, claim 19 rejected, for similar reasons, under the grounds as set forth for claim 12.
Regarding Claim 13:
DOYON in view of Ramesh discloses:
The method of claim 1, wherein said providing, by the link, of the at least part of the secret information to the VMS comprises providing the secret information in a trailing portion of the link used to launch the browser-based connection. (DOYON, Para.0084, Para.0208, Para.0118; “the security device transmits to the …. server the activation code ….as wells as device data, such as …..MAC address, serial number, public key…..”, “…. a link (in a browser such as Internet Explorer) that a person can click on the Device Activation Page”, “Device activation page…..to initiate the enrollment of a device in the CBVSS”)
With respect to dependent claim 20, a corresponding reasoning was given earlier in this section with respect to claim 13; therefore, claim 20 rejected, for similar reasons, under the grounds as set forth for claim 13.
Regarding Claim 14:
DOYON in view of Ramesh discloses:
The method of claim 1, wherein enrollment of the camera is effected based on the user interaction with the enrollment GUI element without any additional user input. (DOYON, Para.0073, Para.0392, Para.0277, Para.0397; “the enrollment web page ….provided by the security device …. includes a “get activation code” button, clicking on which results in a corresponding message being transmitted …..”, “Click on “Get an activation code for …. camera”, “The CBVSS activation web pages is … HTML pages …. to … enrollment of a device in the CBVSS”, “The Enrolment ….URL ….. found in the configuration.xml file”)
Regarding Claim 21:
DOYON in view of Ramesh discloses:
A method for enrolling a security device into a surveillance system, comprising: (disclosed in claim 1)
obtaining secret information stored by the security device; (DOYON, Abstract, Para.0069; “The activation code is …. provided to the security device…..”, “The security device …. is an IP camera …. which comprise…. The storage …. for storing …. an activation code”)
instantiating, via the security device, a browser-based connection to the surveillance system; (DOYON, Para.0077, Para.0011, Para.0120; “a user at the computing device …..authentication data … over the network connection …. to the ….server”, “…. security devices ….. communicate with a computing device….. to communicate with the ….server”, “video surveillance system …. record and playback IP devices over the Internet”)
authenticating the browser-based connection to the surveillance system; (disclosed in claim 1)
after the authenticating, providing the secret information to the surveillance system via the browser-based connection; (disclosed in claim 1) and
causing the surveillance system to enroll the security device. (disclosed in claim 1)
Claim 4 is rejected under AIA 35 U.S.C. 103 as being unpatentable over DOYON et al (US 20210111895 A1) in view of Ramesh et al. (US 20230085031 A1) and further in view of Ernst et al. (US 20050124320 A1)
Regarding Claim 4:
DOYON in view of Ramesh discloses:
The method of claim 3, wherein said ….. the first browser-based connection to the camera (DOYON, Para.0021, Abstract; “for establishing a secure connection between a …. security device and …. server …. over a first network connection”, “for registering ….. security devices such as IP cameras to a …. server over a …. network”) comprises supplying default access credentials, (Para.0009; “the security device, e.g. IP camera…. a user may communicate with the …..server and provide credentials, e.g. security account credentials”) the method comprising modifying the camera (Para.0123, Para.0009; “….modified each time a new functionality is added to a device.”, “the security device, e.g. IP camera”)
…...authenticating of the ……browser-based connection (Ramesh, disclosed in claim 1)
…..updated access credentials, different from the default access credentials. (Ramesh, Para.0066; “the term “account identifier” may include one or more primary account numbers (PANs) …. associated with a customer account. The term “token” may refer to an identifier that is used as a substitute or replacement identifier for an original account identifier, such as a PAN…...”)
however, DOYON in view of Ramesh does not explicitly disclose:
….. modifying the …. to accept a future browser-based connection using …..access credentials……
In an analogous reference Ernst discloses:
….. modifying the …. to accept a future browser-based connection using …..access credentials…… (Para.0278, Para.0269; “modify ….. file …. that future login requests by …. website ….. may succeed…..”, “enters the URI of the …. displayed login page of …. website”)
Before the effective filing date of the claimed invention, it would have been obvious to one with ordinary skill in the art to modify DOYON in view of Ramesh’s method for establishing a secure connection between a network-enabled security device and a security server by enhancing DOYON in view of Ramesh’s method to include Ernst’s method for managing and making available electronically a plurality of evolving identity.
The motivation: modifying an authorization file by adding the information that future login requests by any website can be successful is important without human intervention.
Conclusion
THIS ACTION IS MADE FINAL. 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 extension fee 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.
Contact Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SAYEDA SALMA NAHAR whose telephone number is (703)756-4609. The examiner can normally be reached M-F 12:00 PM to 6:00 PM 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, Amir Mehrmanesh can be reached on (571) 270-3351. 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.
/SAYEDA SALMA NAHAR/Examiner, Art Unit 2435
/BEEMNET W DADA/Primary Examiner, Art Unit 2435
Prosecution Insights