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 .
Status of Claims
This action is a Final Action on the merits in response to the communications filed on 05/08/2026.
Applicant has amended claims 1, 5 – 6, 8 – 11, 13, and 15.
Claims 1 – 20 are pending in this application.
Response to Remarks
Examiner’s Response to the Remarks.
Rejections of Claims Under 35 U.S.C. § 101.
Examiner’s response to Rejections of Claims under 35 U.S.C. § 101.
Applicant argues amended independent claims recite practical application in accordance with Step 2A Prong Two as articulated in Ex Parte Hannun (Appeal 2018-003323) “Hannun”.
Examiner respectfully disagrees. In Hannun, the claims are directed to speech transcription; in the instant Applicant’s case, the claims are directed to managing demand requests for ride-sharing purposes. In Hannun, the claims recite steps of normalizing an input file, generating a jitter set of audio files, generating a set of spectrogram frames, obtaining predicted character probabilities using a trained neural network, and decoding a transcription of the input audio using the predicted character probability outputs. In Applicant’s case, claim 1 recites the steps of in response to a requestor device for a requestor launching a requestor application for transportation matching, identifying, utilizing real-time GPS signals of the requestor device, a pickup location associated with the requestor device for the requestor; generating a pool of provider devices by adding unassigned provider devices waiting for requestor transportation assignments and adding assigned provider devices en route to pickup locations of assigned requestor devices, wherein the unassigned provider devices and the assigned provider devices are associated with vehicles comprising dynamic GPS locations; prior to matching a provider device with the requestor device, determining, utilizing a computational model that samples from the generated pool of provider devices comprising the assigned provider devices and the unassigned provider devices and utilizing real-time GPS locations of the generated pool of the assigned provider devices and the unassigned provider devices, candidate provider devices associated with candidate transportation vehicles for prioritized transport of the requestor; selecting utilizing the computational model, from the candidate provider devices comprising the assigned provider devices and the unassigned provider devices, a ghost match comprising the provider device to surface via a graphical user interface of the requestor device as a prioritized transportation option for the prioritized transport of the requestor based on an estimated time to arrival (ETA) at the pickup location of a transportation vehicle associated with the provider device and based on real-time GPS data of the candidate provider devices and the real-time GPS signals of the requestor device; based on selecting the ghost match comprising the provider device for the prioritized transport of the requestor by utilizing the computational model and prior to matching the provider device with the requestor device, providing, for display on the graphical user interface of the requestor device, a selectable element option in the graphical user interface for prioritized transport of the requestor by the transportation vehicle associated with the provider device, wherein the selectable element option for the prioritized transport of the requestor indicates the ghost match as a matching option for the requestor device that includes a faster pickup that reduces a waiting time prior to pick up, relative to a standard transportation option or a shared transportation option, and the matching option is selected using the computational model, and the matching option indicates a price differential relative to the standard transportation option or the shared transportation option; in response to receiving a selection of the selectable element option for prioritized transport in the graphical user interface via the requestor of the requestor device, updating the graphical user interface to visually indicate a selection of the prioritized transport and matching the provider device associated with the prioritized transport with the requestor device; and based on receiving the selection of the selectable element option for prioritized transport, iteratively comparing real-time GPS locations of the candidate provider devices with the provider device and updating parameters of the computational model, wherein the parameters indicate a dynamic conversion metric of prioritized transportation of requestor devices and influences whether additional requests for transportation from additional requestor devices are provided an option of prioritized transport; and based on updating the parameters of the computational model and in response to an additional requestor device for an additional requestor launching an additional requestor application for transportation matching, excluding from providing, for display on a graphical user interface of the additional requestor device, the prioritized transportation option for the prioritized transport of the additional requestor, and recites certain methods of organizing human activity that are managing interactions between a human and a computer, where there is a response to a requestor device for a requestor launching a requestor application for transportation request. Hannun does not recite certain methods of organizing human activity, as the claims do not include fundamental economic principles or practices, commercial or legal interactions, managing personal behavior or relationships or interactions between people. Applicant’s claim recites mathematical concepts, where the claim limitations recite mathematical calculations and mathematical relationships performing mathematical operations such as an act of computing or calculating, and comparing using mathematical methods to determine a recommendation of a variable and mathematical relationships of variables that represent some modeled characteristic. Hannun is directed to a specific implementation. Claim 1 does not recite additional elements that integrate the judicial exception into a practical application. Applicant recites the additional elements a requestor device, a requestor application, utilizing real-time GPS signals of the requestor device, provider device(s), vehicles, at least one processor, at least one non-transitory computer-readable storage medium, a computing device, a system, dynamic GPS locations, a computational model, ghost match, a selectable element option in the graphical user interface, wherein determining the candidate provider devices comprises: calculating, from real-time GPS locations of the pool of provider devices and the pickup location associated with the requestor device, an estimated time of arrival (ETA) at the pickup location for each provider device in the generated pool, and iteratively comparing real-time GPS locations; these additional elements are merely using the computer as a tool to collect and analyze data. Applicant argues claim 1 is similar to SiRF Tech., 601 F.3d at 1331-33, 94 USPQ2d at 1616-17, "calculating an absolute position of a GPS receiver," and "an absolute time of reception of satellite signals," where the claimed GPS receiver calculated pseudo ranges estimating the distance from the GPS receiver to satellites. However, in SiRF, the calculations and claim cannot be performed in the human mind, whereas in Applicant’s claim 1, the mathematical calculations can be performed with the human mind, pen, and paper; as the claim merely observes the driver location and the pickup location of the requestor and calculates and estimated time of arrival (ETA) at the pickup location; and is much like hailing a taxi cab and calculating an ETA. Furthermore, in Applicant’s claim 1, there is no “providing an estimate of the time at which a GPS receiver receives a plurality of satellite signals, and computing the position "of the GPS receiver." Id. Thus Applicant’s claim 1 calculating from GPS locations is contrastingly different than calculating an absolute position of a GPS receiver and an absolute time of reception of satellite signals of SiRF and are not tied to a particular machine or apparatus. Accordingly, claims 1 – 20, are rejected under 35 U.S.C. § 101.
Claim Rejections: 35 U.S.C. § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Applicant’s claims 1 – 20, are rejected under 35 U.S.C. § 101 because the claimed invention is directed to judicial exception (i.e., an abstract idea) without reciting significantly more.
Claims 1, 8, and 15 recite:
A method comprising: in response to a requestor device for a requestor launching a requestor application for transportation matching, identifying, utilizing real-time GPS signals of the requestor device, a pickup location associated with the requestor device for the requestor;
generating a pool of provider devices by adding unassigned provider devices waiting for requestor transportation assignments and adding assigned provider devices en route to pickup locations of assigned requestor devices, wherein the unassigned provider devices and the assigned provider devices are associated with vehicles comprising dynamic GPS locations;
prior to matching a provider device with the requestor device, determining, utilizing a computational model that samples from the generated pool of provider devices comprising the assigned provider devices and the unassigned provider devices and utilizing real-time GPS locations of the generated pool of the assigned provider devices and the unassigned provider devices, candidate provider devices associated with candidate transportation vehicles for prioritized transport of the requestor;
and identifying provider devices having ETAs within a threshold ETA or within a threshold distance to the pickup location;
selecting utilizing the computational model, from the candidate provider devices comprising the assigned provider devices and the unassigned provider devices, a ghost match comprising the provider device to surface via a graphical user interface of the requestor device as a prioritized transportation option for the prioritized transport of the requestor based on a comparison of the calculated ETAs to select the provider device having an earlier ETA at the pickup location relative to other candidate provider devices;
based on selecting the ghost match comprising the provider device for the prioritized transport of the requestor by utilizing the computational model and prior to matching the provider device with the requestor device, providing, for display on the graphical user interface of the requestor device, a selectable element option in the graphical user interface for prioritized transport of the requestor by a transportation vehicle associated with the provider device, wherein the selectable element option for the prioritized transport of the requestor indicates the ghost match as a matching option for the requestor device that includes a faster pickup that reduces a waiting time prior to pick up, relative to a standard transportation option or a shared transportation option, and the matching option is selected using the computational model, and the matching option indicates a price differential relative to the standard transportation option or the shared transportation option;
in response to receiving a selection of the selectable element option for prioritized transport in the graphical user interface via the requestor of the requestor device, updating the graphical user interface to visually indicate a selection of the prioritized transport and matching the provider device associated with the prioritized transport with the requestor device;
and based on receiving the selection of the selectable element option for prioritized transport, iteratively comparing real-time GPS locations of the candidate provider devices with the provider device and updating parameters of the computational model, wherein the parameters indicate a dynamic conversion metric of prioritized transportation of requestor devices and influences whether additional requests for transportation from additional requestor devices are provided an option of prioritized transport;
and based on updating the parameters of the computational model and in response to an additional requestor device for an additional requestor launching an additional requestor application for transportation matching, excluding from providing, for display on a graphical user interface of the additional requestor device, the prioritized transportation option for the prioritized transport of the additional requestor.
The limitations of claim 1, under its broadest reasonable interpretation recite certain methods of organizing human activity. The claim particularly recites managing interactions where there are management of interactions between a human and a computer, as we have in response to a requestor device for a requestor launching a requestor application for transportation matching, identifying, utilizing real-time GPS signals of the requestor device, a pickup location associated with the requestor device for the requestor; generating a pool of provider devices by adding unassigned provider devices waiting for requestor transportation assignments and adding assigned provider devices en route to pickup locations of assigned requestor devices, wherein the unassigned provider devices and the assigned provider devices are associated with vehicles comprising dynamic GPS locations; prior to matching a provider device with the requestor device, determining, utilizing a computational model that samples from the generated pool of provider devices comprising the assigned provider devices and the unassigned provider devices and utilizing real-time GPS locations of the generated pool of the assigned provider devices and the unassigned provider devices, candidate provider devices associated with candidate transportation vehicles for prioritized transport of the requestor; selecting utilizing the computational model, from the candidate provider devices comprising the assigned provider devices and the unassigned provider devices, a ghost match comprising the provider device to surface via a graphical user interface of the requestor device as a prioritized transportation option for the prioritized transport of the requestor based on a comparison of the calculated ETAs to select the provider device having an earlier ETA at the pickup location relative to other candidate provider devices; based on selecting the ghost match comprising the provider device for the prioritized transport of the requestor by utilizing the computational model and prior to matching the provider device with the requestor device, providing, for display on the graphical user interface of the requestor device, a selectable element option in the graphical user interface for prioritized transport of the requestor by a transportation vehicle associated with the provider device, wherein the selectable element option for the prioritized transport of the requestor indicates the ghost match as a matching option for the requestor device that includes a faster pickup that reduces a waiting time prior to pick up, relative to a standard transportation option or a shared transportation option, and the matching option is selected using the computational model, and the matching option indicates a price differential relative to the standard transportation option or the shared transportation option; in response to receiving a selection of the selectable element option for prioritized transport in the graphical user interface via the requestor of the requestor device, updating the graphical user interface to visually indicate a selection of the prioritized transport and matching the provider device associated with the prioritized transport with the requestor device; and based on receiving the selection of the selectable element option for prioritized transport, iteratively comparing real-time GPS locations of the candidate provider devices with the provider device and updating parameters of the computational model, wherein the parameters indicate a dynamic conversion metric of prioritized transportation of requestor devices and influences whether additional requests for transportation from additional requestor devices are provided an option of prioritized transport; and based on updating the parameters of the computational model and in response to an additional requestor device for an additional requestor launching an additional requestor application for transportation matching, excluding from providing, for display on a graphical user interface of the additional requestor device, the prioritized transportation option for the prioritized transport of the additional requestor. Certain methods of organizing human activity are particularly recited as commercial interactions in the form of business relations where there a standard costs and premium costs for prioritized transportation of the requestor. Accordingly, claim 1 recites certain methods of organizing human activity.
The limitations of claim 1 under its broadest reasonable interpretation recites mathematical concepts. For example, claim 1 recites prior to matching a provider device with the requestor device, determining, utilizing a computational model that samples from the generated pool of provider devices comprising the assigned provider devices and the unassigned provider devices and utilizing real-time GPS locations of the generated pool of the assigned provider devices and the unassigned provider devices, candidate provider devices associated with candidate transportation vehicles for prioritized transport of the requestor; selecting utilizing the computational model, from the candidate provider devices comprising the assigned provider devices and the unassigned provider devices, a ghost match comprising the provider device to surface via a graphical user interface of the requestor device as a prioritized transportation option for the prioritized transport of the requestor based on a comparison of the calculated ETAs to select the provider device having an earlier ETA at the pickup location relative to other candidate provider devices; based on selecting the ghost match comprising the provider device for the prioritized transport of the requestor by utilizing the computational model and prior to matching the provider device with the requestor device, providing, for display on the graphical user interface of the requestor device, a selectable element option in the graphical user interface for prioritized transport of the requestor by the transportation vehicle associated with the provider device, wherein the selectable element option for the prioritized transport of the requestor indicates the ghost match as a matching option for the requestor device that includes a faster pickup that reduces a waiting time prior to pick up, relative to a standard transportation option or a shared transportation option, and the matching option is selected using the computational model, and the matching option indicates a price differential relative to the standard transportation option or the shared transportation option; and based on receiving the selection of the selectable element option for prioritized transport, iteratively comparing real-time GPS locations of the candidate provider devices with the provider device and updating parameters of the computational model, wherein the parameters indicate a dynamic conversion metric of prioritized transportation of requestor devices and influences whether additional requests for transportation from additional requestor devices are provided an option of prioritized transport; and based on updating the parameters of the computational model and in response to an additional requestor device for an additional requestor launching an additional requestor application for transportation matching, excluding from providing, for display on a graphical user interface of the additional requestor device, the prioritized transportation option for the prioritized transport of the additional requestor; where the claim limitations recite mathematical calculations and mathematical relationships performing mathematical operations such as an act of computing or calculating using mathematical methods to determine a recommendation of a variable and mathematical relationships of variables that represent some modeled characteristic. Accordingly, claim 1 recites mathematical concepts.
Claims 8 and 15 are substantially similar to claim 1 and recite the same abstract ideas identified above.
The dependent claims encompass the same abstract ideas as well. For instance, claim 2 is directed towards observing the selectable element option for prioritized transportation a provider indicator or a graphical representation, claim 3 is directed towards evaluating wherein selecting the ghost match comprising the provider device further comprises: iteratively searching from the generated pool of provider devices comprising the assigned provider devices and the unassigned provider devices to determine closer provider devices from the generated pool relative to the provider device associated with the prioritized transport; and based on the iterative search, further providing, for display in the graphical user interface via the requestor of the requestor device, an additional notification indicating that the provider device is still en route to the pickup location associated with the requestor device; claim 4 is directed towards observing selection of the wherein selecting the ghost match comprising provider device for the prioritized transport further comprises: iteratively searching from the generated pool of provider devices comprising the assigned provider devices and the unassigned provider devices to determine closer provider devices from the generated pool relative to the provider device associated with the prioritized transport; and based on the iterative search, further providing, for display in the graphical user interface via the requestor of the requestor device, an additional notification indicating an additional provider device is en route to the pickup location associated with the requestor device instead of the provider device, wherein the iterative search indicates that the additional provider device has an ETA closer than the ETA of the provider device at the pickup location; claim 5 is directed towards in response to the requestor device for the requestor launching the requestor application for transportation matching, evaluating requestor profile data by generating, utilizing a machine learning model and based on the requestor profile data, a predicted conversion probability of the requestor device selecting the selectable element option for prioritized transport; claim 6 is directed towards evaluating, utilizing the machine learning model to analyze historical travel activity, training conversion probabilities; comparing the training conversion probabilities with ground truth conversions to determine a measure of loss; and modifying parameters of the machine learning model based on the measure of loss reflecting differences between the training conversion probabilities and the ground truth conversions; claim 19 is directed towards evaluating the provider device for the prioritized transport of the requestor is not assigned to a particular requestor and evaluating the ETA at the pickup location of the transportation vehicle associated with the provider device is both later than an alternative ETA at an alternative pickup location of the transportation vehicle for an alternative requestor and earlier than other ETAs at the pickup location of other candidate transportation vehicles associated with other candidate provider devices, and based on determining that the ETA at the pickup location of the transportation vehicle is earlier than the other ETAs at the pickup location of the other candidate transportation vehicles selecting the provider device for the prioritized transport of the requestor; claims 7 and 18 are directed towards observing an indication of a selection of the selectable element option for prioritized transportation from the requestor device, identifying an unassigned provider device corresponding to an unassigned transportation vehicle having an earlier ETA at the pickup location than the ETA at the pickup location of the transportation vehicle associated with the provider device initially selected for the prioritized transport of the requestor, and based on identifying the unassigned provider device corresponding to an unassigned transportation vehicle having an earlier ETA sending a matched transportation assignment to the unassigned provider device for the unassigned transportation vehicle to pick up the requestor at the pickup location and sending a notification to the provider device initially selected for the prioritized transport of the requestor to not pick up the requestor; claim 9 is directed towards evaluating generate a plurality of potential transportation plans corresponding to a plurality of requestors and a plurality of provider devices; generate a plurality of preliminary matching scores for the plurality of potential transportation plans, wherein a higher preliminary matching score corresponds with a lower ETA; and apply penalization factors to one or more of the plurality of preliminary matching scores based on one or more requestors or providers experiencing multiple swaps; claim 10 is directed towards observing a transportation plan from the plurality of potential transportation plans; and based on the comparison of the calculated ETAs to select the provider device having the earlier ETA at the pickup location relative to other candidate provider devices and the transportation plan, select the ghost match as the prioritized transportation option; claim 16 are directed towards evaluating the provider device is assigned to pick up an initial requestor at an initial pickup location; after selecting the provider device for the prioritized transport of the requestor, generate one or more matching scores for the initial requestor based on a prioritization factor that increases a priority of matching the initial requestor relative to other requestors, and select an alternative provider device for transport of the initial requestor at the initial pickup location based on the one or more matching scores; claim 11 is directed towards based on receiving the selection of the selectable element option for prioritized transport, analyzing additional ETAs for additional requestor devices to determine an ETA degradation; and spreading out the ETA degradation utilizing chain bumping for the additional requestor devices; claim 12 is directed towards evaluating an alternative provider device associated with an alternative transportation vehicle for the prioritized transport of the requestor rather than the provider device initially selected for the prioritized transport of the requestor, based on the alternative transportation vehicle having an earlier ETA at the pickup location, and determine a time or distance traveled toward the pickup location by the transportation vehicle associated with the provider device initially selected for the prioritized transport of the requestor, and providing to the provider device initially selected for the prioritized transport of the requestor, a compensation value based on the determined time or the determined distance; Claim 13 is directed towards observing ETAs at the pickup location of the candidate transportation vehicles associated with the candidate provider devices, wherein the ETAs at the pickup location of the candidate transportation vehicles is determined from the real-time GPS locations of the candidate provider devices; and selecting the provider device based on the ETA at the pickup location of the transportation vehicle being less than other ETAs at the pickup location of other candidate transportation vehicles from the candidate transportation vehicles; claims 14 and 20 are directed toward observing the provider device is assigned to pick up an initial requestor at an initial pickup location, and receiving an indication of a selection of the selectable element option for prioritized transportation from the requestor device, and modifying utilizing the computational model a transportation assignment for the provider device to pick up the requestor; and claim 17 is directed towards evaluating the candidate provider devices associated with the candidate transportation vehicles are unavailable for the prioritized transport of the requestor and remove, for display on the GUI of the requestor device, the selectable element option for prioritized transportation based on determining the candidate provider devices are unavailable for the prioritized transport of the requestor. Thus, the dependent claims further limit the abstract ideas.
These judicial exceptions are not integrated into a practical application. The additional elements of a requestor device, a requestor application, utilizing real-time GPS signals of the requestor device, provider device(s), vehicles, at least one processor, at least one non-transitory computer-readable storage medium, a computing device, a system, dynamic GPS locations, a computational model, ghost match, a selectable element option in the graphical user interface, wherein determining the candidate provider devices comprises: calculating, from real-time GPS locations of the pool of provider devices and the pickup location associated with the requestor device, an estimated time of arrival (ETA) at the pickup location for each provider device in the generated pool, and iteratively comparing real-time GPS locations are considered generic computer components as per Applicant’s Specification shown below:
“[0043] As suggested above, each of the provider devices 110a-110n and the requestor devices 116a-116n may comprise a mobile device, such as a laptop, smartphone, or tablet associated with a requestor or a provider. The provider devices 110a-110n and the requestor devices 116a-116n may be any type of computing device as further explained below with reference to FIG. 12. In some embodiments, one or more of the provider devices 110a-110n are not associated with human providers, but are attached to (or integrated within) the transportation vehicles 108a-108n, respectively.
[0044] As further indicated by FIG. 1, the provider devices 110a-110n include provider applications 112a-112n, respectively. Similarly, the requestor devices 116a-116n include requestor applications 118a-118n, respectively. In some embodiments, the provider applications 112a-112n (or the requestor applications 118a-118n) comprise web browsers, applets, or other software applications (e.g., native applications) respectively available to the provider devices 110a-110n or the requestor devices 116a-116n. Additionally, in some instances, the dynamic transportation matching system 104 provides data including instructions that, when executed by the provider devices 110a-110n or by the requestor devices 116a-116n, respectively create or otherwise integrate one of the provider applications 112a-112n or the requestor applications 118a-118n with an application or webpage.”
and thus are not practically integrated nor significantly more.
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As stated above, the additional elements of a requestor device, a requestor application, utilizing real-time GPS signals of the requestor device, provider device(s), vehicles, at least one processor, at least one non-transitory computer-readable storage medium, a computing device, a system, dynamic GPS locations, a computational model, ghost match, a selectable element option in the graphical user interface, and iteratively comparing real-time GPS locations are considered generic computer components, and the claims amount to no more than mere instructions using generic computer components to implement the judicial exception. Each of the additional limitations are no more than mere instructions to apply the exception using a generic computer component (e.g., a processor). The combination of these additional elements are no more than mere instructions to apply the exception using generic computer components (e.g., processor). Mere instructions to apply an exception using generic computer components cannot provide an inventive concept.
Dependent claims 2 – 7, 9 – 14, and 16 – 20, when analyzed both individually and in combination are also held to be ineligible for the same reason above and the additional recited limitations fail to establish that the claims are not directed to an abstract idea. The additional limitations of the dependent claims when considered individually and as an ordered combination do not amount to significantly more than the abstract ideas.
Looking at these limitations as an ordered combination and individually add nothing additional that is sufficient to amount to significantly more than the recited abstract idea because they simply provide instructions using generic computer components, to “apply” the recited abstract idea. Thus, the elements of the claims, considered both individually and as an ordered combination, are not sufficient to ensure that the claim as a whole amount to significantly more than the abstract idea itself. Therefore, claims 1 – 20, are not patent eligible.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the Examiner should be directed to Frank Alston whose telephone number is 703-756-4510. The Examiner can normally be reached 9:00 AM – 5:00 PM Monday - Friday. Examiner can be reached via Fax at 571-483-7338. 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 Beth Boswell can be reached at (571) 272-6737.
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.
/FRANK MAURICE ALSTON/
Examiner, Art Unit 3625
07/10/2026
/ROBERT D RINES/Primary Examiner, Art Unit 3625
Prosecution Insights