DETAILED ACTION
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 4 December 2025 has been entered.
Status of Claims
This action is in reply to the response and amendments filed on 4 December 2025. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claims 1, 4-5, 9, 11, 14-15, and 19 have been amended.
Claims 3, 6, 13, 16 are cancelled.
Claims 2, 7-8, 10, 12, 17-18, and 20 are original / previously presented.
Claims 1-2, 4-5, 7-12, 14-15, and 17-20 are currently pending and have been examined.
Response to Arguments
Regarding the Applicant’s arguments filed regarding the previous 35 USC 101 rejection of claims 1-2, 4-5, 7-12, 14-15, and 17-20; the arguments have been considered but they are not persuasive.
Applicant argues the claims are eligible in Step 2A because “while the claims may involve abstract concepts such as receiving logistics requests and generating quotes, amended independent claims 1 and 11 are not directed solely to an abstract idea because they include concrete improvements in the way rate sources are selected and activated in real time, providing a technical solution to a long-standing problem in logistics automation” (Remarks pg. 12). Examiner disagrees. First, claims 1 and 11 are directed to an abstract idea in Step 2A Prong One. The claims as a whole recite certain methods of organizing human activities (e.g. the subcategories of fundamental economic principles or practices, commercial interactions, marketing or sales activities or behaviors, managing personal behavior or relationships or interactions between people, following rules or instructions). Whether or not the claims provide a technical solution to a technical problem is evaluated in Step 2A Prong Two and Step 2B. Second, the claim limitations regarding rate source selection and activation in real time (e.g. “wherein the processor enables real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected”) represents the identified judicial exception (certain methods of organizing human activities: managing personal behavior, following rules or instructions) ‘applied’ by a generic / general purpose computer (processor). Based on MPEP 2106.05(f), this is not indicative of a practical application or significantly more because it is no more than implementing a judicial exception on a computer or using a computer as a tool to perform an abstract idea. Hence, since applying a judicial exception on a computer is not a technical solution that represents an improvement to a technical field. Third, the longstanding problems addressed in the background / related art of the Applicant’s specification (e.g. Applicant Specification ¶[0002] handling shipping requests manually, overwhelmed workers providing rate quotes, tedious / repetitive tasks) are business / economic problems tied to a judicial exception (certain methods of organizing human activities) and not technical problems. Also, using a computer to perform functions / tasks faster or more efficient (e.g. wherein the processor enables real-time activation of one or more rate sources based…) is not a practical application or significantly more because this is an inherent benefit of a computer implementation. See MPEP 2106.05(f) citing Intellectual Ventures I LLC v. Capital One Bank (USA), 792 F.3d 1363, 1367, 115 USPQ2d 1636, 1639 (Fed. Cir 2015) stating “claiming the improved speed or efficiency inherent with applying the abstract idea on a computer” does not integrate a judicial exception into a practical application or provide an inventive concept”. Thus, the claims still recite a judicial exception / abstract idea in Step 2A Prong One; and the claimed way ‘rate sources are selected and activated in real time’ does not address a technical solution to a technical problem that would represent an improvement to a technical field or technology that is a practical application or significantly more in Step 2A Prong Two / Step 2B. This argument is not persuasive.
Applicant argues the claims are eligible in Step 2A Prong Two because “Regardless of whether or not independent claims 1 and 11 may somehow be construed as including limitations that fall within one of the enumerated groupings of abstract ideas under Step 2A: Prong One, Applicant respectfully asserts that amended independent claims 1 and 11 integrate the alleged abstract ideas into a practical application under Step 2A: Prong Two. In particular, amended claims 1 and 11 recite functionality enabling real-time activation of individual rate sources based on dynamic conditions or user-defined parameters. This is not merely a generic application of quoting logic, but instead provides a non-conventional technical improvement to logistics platforms by allowing runtime control of external systems, i.e., rate sources such as, rate engines, market intelligence feeds, etc., which eliminates the need for pre-configuration or provider intervention. This is a marked departure from traditional systems, which rely on static configurations or pre-integrated APIs.” (Remarks pg. 12). Examiner disagrees. First, using a computer to perform functions / tasks faster or more efficient (e.g. ‘wherein the processor enables real-time activation of one or more rate sources based on the one or more user defined parameters’) is not a practical application or significantly more because this is an inherent benefit of a computer implementation. See MPEP 2106.05(f) citing Intellectual Ventures I LLC v. Capital One Bank (USA), 792 F.3d 1363, 1367, 115 USPQ2d 1636, 1639 (Fed. Cir 2015) stating “claiming the improved speed or efficiency inherent with applying the abstract idea on a computer” does not integrate a judicial exception into a practical application or provide an inventive concept”. Second, this is not an improvement that is representative of a practical application because at best this is a business / entrepreneurial improvement of the judicial exeption (e.g. activation of a rate source based on user defined parameters represents certain methods of organizing human activities: following rules or instructions), and the additional element is only ‘applying’ the judicial exception by a computer and which is not practical application, per MPEP 2106.05(f). Third, the rate engines in the claims only provide high-level extra-solution data gathering for the subsequent judicial exception steps of processing of the rate request and calculating a final rate, without any technical details regarding accessing the rate engines provided in the claims. As claimed, the rate engines represent using a computer in its ordinary capacity as a tool (i.e. to receive data), and without any technical, particular steps they do not provide a practical application, per MPEP 2106.05(f) and MPEP 2106.05(g). Fourth, the claims do not include the argued market intelligence feeds. Although the claims are interpreted in light of the specification, limitations from the specification are not read into the claims. See In re Van Geuns, 988 F.2d 1181, 26 USPQ2d 1057 (Fed. Cir. 1993). Fifth, providing user level access instead of requiring API connections to interact with other platforms or websites does not provide a technical advantage, since providing logistics quotes for requests is not limited to Internet technologies since logistics rate quoting has long existed outside of technology. See Wikipedia “History of United States postage rates” (<http://web.archive.org/web/20191108141030/https://en.wikipedia.org/wiki/History_of_United_States_postage_rates> captured on 8 November 2019 Using Wayback Machine) detailing published rates quoted for shipping letters / packages dating back to 1863, i.e. before Internet / API technology. Hence, the departure from API is long established in logistics rate quoting and not a technological improvement. These features do not provide a technical improvement or an improvement to technology that is a practical application. This argument is not persuasive.
Applicant argues the claims are eligible in Step 2B because “Applicant respectfully submits that amended limitation claim 1 adds a specific limitation that: 1) improves the functioning of the computing system itself in the logistics and transportation industry; and 2) adds meaningful limitations that amount to more than generally linking the use of the abstract idea to a particular technological environment of the logistics and transportation industry. Applicant respectfully asserts that all of these features, especially when viewed in combination, amount to significantly more than the judicial exception” (Remarks pg. 12-13). Examiner disagrees. Examiner disagrees. Regarding (1), the Applicant’s invention is more representative of implementing a judicial exception (certain methods of organizing human activities: fundamental economic principles or practices, commercial interactions, marketing or sales activities or behaviors, managing personal behavior or relationships or interactions between people, following rules or instructions) in a computer environment and using computers as a tool than improving computer systems themselves outside of a judicial exception. Regarding (2) the technical elements in the claims are all recited at a high level of detail and either represent (a) generic computers or general computer components implementing the judicial exception: a processor, logistics request receiver (e.g. email / website / electronic document), at least one GUIs includes an automated quoting validator function (e.g. general computer component with program instructions), computing device, graphical user interface, one or more rate engines (e.g. computer hardware), one or more GUIs includes a text analysis function (e.g. general computer component with program instructions), one or more bots (e.g. software code); (b) generally linking the use of the judicial exception to a technological environment: the logistics receiver as email / website / electronic document (i.e. Internet, computers) noting that mere instructions to apply a judicial exception using computers and the Internet does not provide a practical application or significantly more, and using natural language processing (NLP) / artificial intelligence (AI) noting that there are no claimed details about the technical steps or details about the NLP or AI algorithms; or (c) extra-solution use of computers in their ordinary capacity (e.g. to receive, store, transmit data): performing keystroke input (the one or more bots and screen are receiving data), selecting user defined parameter options (the processor, graphical display, drop-down menus are receiving data), recording (the processor is storing data), accessing rate engines / obtaining rate related information (the rate engines and processor are retrieving data). Since all of the additional elements either represent (a) adding the words ‘apply it’ with the judicial exception or mere instructions to implement an abstract idea on a computer per MPEP 2106.05(f), (b) generally link the use of the judicial exception to a particular technology or field of use per MPEP 2106.05(h), or (c) add insignificant extra-solution activity to the judicial exception per MPEP 2106.05(g) and use computers a tool per MPEP 2106.05(f), none of these additional elements provide a practical application or significantly more. Also, when viewed in combination, there is nothing that changes what is otherwise present when viewing these additional elements individually. Hence, none of these limitations apply the judicial exception in some meaningful way to provide significantly more. This argument is not persuasive.
Applicant argues the claims are eligible because “Please consider paragraph [0073] of the Subject Application, reproduced below: [0073] Embodiments of automated quoting process 10 provide numerous advantages over existing approaches. Some of these may include, but are not limited to, providing access through user level, which doesn't require API connections to interact with other platforms or websites, the user does not have to enter the load information or lane manually, the automation takes it from the request, parameters at tenderer email address level, customizable parameter lists, lane and location volume exception handling, not just all or nothing, preset calendar for additional margin, mileage tiered margin per customer per equipment type or per tenderer per equipment type, copy parameter sets from another built set to save time, saved parameter sets for ease of re-use, not a rate engine, performs the same process a human should do using rate sources, human intervention not required every task, process can be completed with no human interaction, provides the ability to turn on and off rate sources in real time, not preset and provider determines where rates come from or have to ask provider to make changes when needed, option of margin by % or $ amount, location exception by shipper or receiver, not just city, st, provides the ability to select rate index option, automation moves to next index if no results returned, hours of the day options at load pickup level or quote request level, connects the shipper rate request with carrier truck rates from any rate engine used by the third party logistics, doesn't require shipper input or carrier input into the system, audit option with the validator if the user wants a stop point or if information needs confirmed prior to submitting, etc… As disclosed in paragraph [0073], the system ‘provides the ability to turn on and off rate sources in real time… not preset and provider determines where rates come from or have to ask provider to make changes when needed.’ This demonstrates a concrete technological improvement: users and systems can respond to real-time conditions (e.g., platform availability, market volatility, performance) without halting operations or reconfiguring backend infrastructure” (Remarks pg. 13). Examiner disagrees. The advantages provided in ¶[0070] (as filed) do not provide technological advantages. First, the ability to turn on and off rate sources without having to ask a provider to make changes represents a judicial exception (certain methods of organizing human activity: managing personal behavior or interactions between people, following rules or instructions), and at best this is only a business or entrepreneurial improvement of the judicial exception (i.e. having one individual turning on/off a rate source instead of having another), instead of a technological improvement. Second, providing user level access instead of requiring API connections to interact with other platforms or websites does not provide a technical advantage, since providing logistics quotes for requests is not limited to Internet technologies since logistics rate quoting has long existed outside of technology. See Wikipedia “History of United States postage rates” (<http://web.archive.org/web/20191108141030/https://en.wikipedia.org/wiki/History_of_United_States_postage_rates> captured on 8 November 2019 Using Wayback Machine) detailing published rates quoted for shipping letters / packages dating back to 1863, i.e. before Internet / API technology. Next, the advantages achieved based on automation and improved speed or efficiency are inherent to a computer implementation and also do not integrate a judicial exception into a practical application or inventive concept. See MPEP 2106.05(f). Next, the remaining business and customization advantages listed (e.g. setting option margins / rate index, rate default rules, connecting shipper / carrier / third parties, audit options) are each certain methods of organizing human activities (e.g. managing personal behavior, following rules or instructions) that (1) are not claimed and (2) are representative of a judicial exception rather than a technological process and problem. Hence, the claims and specification ¶[0070] (as filed) do not support an improvement to the functioning of a computer or improvement to a technology or technical field. This argument is not persuasive.
Applicant argues the claims are eligible in view of BASCOM because “independent claims 1 and 11 also improve prior systems by introducing a flexible, runtime-configurable quoting engine. This is not well-understood, routine, or conventional, as traditional quoting systems cannot dynamically change their data source behavior without developer intervention or system updates” (Remarks pg. 15). Examiner disagrees. First, note that the claims in BASCOM were eligible because they presented a non-generic arrangement of elements that amounts to significantly more than an abstract idea in an ordered combination. This is in contrast to the Applicant's claimed invention which only uses a generic computers / general computer components (i.e. a processor, logistics request receiver (e.g. email / website / electronic document), at least one GUIs includes an automated quoting validator function, computing device, graphical user interface, one or more rate engines, one or more GUIs includes a text analysis function, (claim 11) one or more bots) to implement the invention. Also see Applicant specification ¶[0012] reciting that the invention may take the form of entirely hardware / entirely software / or a combination of software and hardware without detailing any particular arrangement. There is no particular arrangement provided in the claims regarding the positioning of the components, further demonstrating that the arrangement is generic. This is no more than using the words “apply it” with the judicial exception or presenting mere instructions to implement an abstract idea on a general computer, and does not present a particular ordered combination of elements. The combination of limitations and claim elements add nothing that is not already present when the steps are considered separately, simply reciting implementation as performed by using generic computers / general computer components, generally linking high-level use of particular technologies, and does not provide a non-conventional and non-generic arrangement of various computer components to achieve a technical improvement. Thus, the claims do not present the same criteria as the eligible claims in BASCOM Global v. AT&T Mobility LLC. Second, whether activities are well-understood, routine, conventional activities are evaluated for the additional elements or combination of elements in Step 2B. The activity of changing the source behavior (e.g. real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use to generate the at least one quote) is part of the judicial exception in Step 2A Prong One. This argument is not persuasive.
Information Disclosure Statement
The Information Disclosure Statement (IDS) filed on 1 February 2024 has been acknowledged by the Office.
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
(A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function.
Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function.
Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action.
The term ‘function’ in the limitations “a text analysis function” and “an automated quoting validator function” is being interpreted by the Office as “a computer subroutine”, using the Merriam-Webster online definition of a ‘function’ <https://www.merriam-webster.com/dictionary/function>, and in view the Applicant’s response on 4 December 2025 pg. 9 acknowledging that “neither the ‘automated quoting validator function’ or the ‘text analysis function’ are structural components in their own right”.
Claim Rejections - 35 USC § 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.
Claims 1-2, 4-5, 7-12, 14-15, and 17-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
Claims 1-2, 4-5, 7-12, 14-15, and 17-20:
Step 1:
Claims 1-2, 4-5, 7-10 recite a method; and claims 11-12, 14-15, and 17-20 recite a system. Since the claims recite either a process, machine, manufacture, or composition of matter, the claims satisfy Step 1 of the Subject Matter Eligibility Framework in MPEP 2106 and the 2019 Patent Examination Guidelines (PEG). Analysis proceeds to Step 2A Prong One.
Step 2A – Prong One:
Claims 1-2, 4-5, 7-12, 14-15, and 17-20 recite an abstract idea. Independent claims 1 recites identifying, a logistics request…, to extract and process information; access the logistics request at the user level without using application programing interface (API) connections; in response to identifying, extracting the information from the logistics request; comparing and validating, the extracted information; to read raw text from the logistics request and to understand where data was extracted incorrectly, associate raw text read from the logistics request with one or more data categories including at least one of a pick up location, a delivery location, a commodity, a weight, or physical dimensions; providing, the extracted information to generate at least one quote…; to publish a list of one or more requests extracted from the body of a predefined [source]; generating, the at least one quote for the logistics request… based upon, at least in part, one or more user defined parameters, real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use… to generate the at least one quote, wherein at least one of the one or more user defined parameters is configured to define a percentage margin outside of which quotes are discarded, wherein at least one of the one or more user defined parameters is configured to define an afterhours window and to charge an additional fee for shipments that are required to be picked up during this predefined period of time, wherein at least one of the one or more user defined parameters is configured to define a minimum rate and profit based on different distance tiers; in response to the logistics request, processing, the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; and once the information is extracted and validated… processing at least one rate request; calculating a final rate; and publishing the final rate, …do not require input from a shipper or carrier. Independent claim 11 recites to identify a logistics request…, to extract and process information; to access the logistics request at the user level without using application programing interface (API) connections; to mimic human interaction; in response to identifying, to extract the information from the logistics request; to compare and validate, the extracted information; to read raw text from the logistics request and to understand where data was extracted incorrectly; to associate raw text read from the logistics request with one or more data categories including at least one of a pick up location, a delivery location, a commodity, a weight, or physical dimensions; to provide the extracted information to generate at least one quote…; to publish a list of one or more requests extracted from the body of a predefined [source]; to generate, the at least one quote for the logistics request based upon, at least in part, one or more user defined parameters, wherein at least one of the one or more user defined parameters is configured to define a percentage margin outside of which quotes are discarded, wherein at least one of the one or more user defined parameters is configured to define an afterhours window and to charge an additional fee for shipments that are required to be picked up during this predefined period of time, wherein at least one of the one or more user defined parameters is configured to define a minimum rate and profit based on different distance tiers; real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use… to generate the at least one quote, in response to the logistics request, to process the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; and once the information is extracted and validated… process at least one rate request; calculate a final rate; and publish the final rate, …do not require input from a shipper or carrier.
The claims as a whole recite certain methods of organizing human activities; and individual limitations in the claims also recite mental processes and a mathematical concept.
First, the limitations of (claim 1) identifying, a logistics request…, to extract and process information; access the logistics request at the user level without using application programing interface (API) connections; in response to identifying, extracting the information from the logistics request; comparing and validating, the extracted information; to read raw text from the logistics request and to understand where data was extracted incorrectly, associate raw text read from the logistics request with one or more data categories including at least one of a pick up location, a delivery location, a commodity, a weight, or physical dimensions; providing, the extracted information to generate at least one quote…; to publish a list of one or more requests extracted from the body of a predefined [source]; generating, the at least one quote for the logistics request based upon, at least in part, one or more user defined parameters, real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use… to generate the at least one quote, wherein at least one of the one or more user defined parameters is configured to define a percentage margin outside of which quotes are discarded, wherein at least one of the one or more user defined parameters is configured to define an afterhours window and to charge an additional fee for shipments that are required to be picked up during this predefined period of time, wherein at least one of the one or more user defined parameters is configured to define a minimum rate and profit based on different distance tiers; in response to the logistics request, processing, the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; and once the information is extracted and validated… processing at least one rate request; calculating a final rate; and publishing the final rate, …do not require input from a shipper or carrier; and (claim 11) to identify a logistics request…, to extract and process information; to access the logistics request at the user level without using application programing interface (API) connections; to mimic human interaction; in response to identifying, to extract the information from the logistics request; to compare and validate, the extracted information; to read raw text from the logistics request and to understand where data was extracted incorrectly; to associate raw text read from the logistics request with one or more data categories including at least one of a pick up location, a delivery location, a commodity, a weight, or physical dimensions; to provide the extracted information to generate at least one quote…; to publish a list of one or more requests extracted from the body of a predefined [source]; to generate, the at least one quote for the logistics request based upon, at least in part, one or more user defined parameters, wherein at least one of the one or more user defined parameters is configured to define a percentage margin outside of which quotes are discarded, wherein at least one of the one or more user defined parameters is configured to define an afterhours window and to charge an additional fee for shipments that are required to be picked up during this predefined period of time, wherein at least one of the one or more user defined parameters is configured to define a minimum rate and profit based on different distance tiers; real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use… to generate the at least one quote, in response to the logistics request, to process the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; and once the information is extracted and validated… process at least one rate request; calculate a final rate; and publish the final rate, …do not require input from a shipper or carrier are certain methods of organizing human activities. For instance, these limitations represent the sub-groupings of fundamental economic principles or practices, commercial interactions, marketing or sales activities or behaviors, managing personal behavior or relationships or interactions between people, and following rules or instructions. For example, fundamental economic principles or practices includes identifying a logistics request…, accessing the logistics request at the user level…, activat[ing] one or more rate sources…, dynamically select[ing] rate sources for use…, generating at least one quote…, calculating a final rate…, and publishing the final rate; commercial interactions includes identifying a logistics request…, generating at least one quote…, calculating a final rate…, and publishing the final rate; marketing or sales activities or behaviors includes identifying a logistics request…, accessing the logistics request at the user level…, extracting and processing information…, extracting information from the logistics request…, comparing and validating the extracted information…, associate raw text read from the logistics request with one or more data categories…, providing the extracted information…, generating at least one quote…, processing at least one rate request…, calculating a final rate…, and publishing the final rate; managing personal behavior or relationships or interactions between people includes identifying a logistics request…, accessing the logistics request at the user level…, extracting and processing information…, mimicking human interaction…, extracting information from the logistics request…, comparing and validating the extracted information…, reading raw text…, understanding where data was extracted incorrectly…, associate raw text read from the logistics request with one or more data categories…, providing the extracted information…, generating at least one quote…, publishing a list of one or more requests extracted from the body…, activat[ing] one or more rate sources…, dynamically select[ing] rate sources for use…, processing at least one rate request…, calculating a final rate…, and publishing the final rate, do not require input from a shipper or carrier; and following rules or instructions includes accessing the logistics request at the user level…, extracting and processing information…, extracting information from the logistics request…, comparing and validating the extracted information…, reading raw text…, understanding where data was extracted incorrectly…, associate raw text read from the logistics request with one or more data categories…, providing the extracted information…, generating at least one quote…, publishing a list of one or more requests extracted from the body…, activat[ing] one or more rate sources…, dynamically select[ing] rate sources for use…, processing at least one rate request…, calculating a final rate…, and publishing the final rate, do not require input from a shipper or carrier. The presence of generic and general computer components such as a processor, logistics request receiver (e.g. email / website / electronic document), at least one GUIs includes an automated quoting validator function (e.g. general computer component and program instructions, see Application specification ¶[0018-20]; and also note that ‘quoting’ and ‘validat[ing]’ at this high level are certain methods of organizing human activities: managing personal behavior), computing device, graphical user interface, one or more rate engines (e.g. computer hardware, see Applicant specification ¶[0012]), one or more GUIs includes a text analysis function (e.g. general computer component and program instructions, see Application specification ¶[0018-20]; and also note that ‘text analysis’ at this high level is certain method of organizing human activities: managing personal behavior), (claim 11) one or more bots (e.g. software code, see Applicant specification ¶[0036], computer), and performing steps ‘automatically’ or ‘with no human interaction’ does not preclude the steps from reciting certain methods of organizing human activities, since the number of people involved in the activities is not dispositive as to whether a claim limitation falls within this grouping and instead it is based on whether an activity itself falls within one of the sub-groupings. If a claim limitation, under its broadest reasonable interpretation, covers certain methods of organizing human activity (e.g. fundamental economic principles or practices, commercial interactions, marketing or sales activities or behaviors, managing personal behavior or relationships or interactions between people, following rules or instructions) regardless of the recitation of generic computer components, then it falls within the ‘Certain Methods of Organizing Human Activity’ grouping of abstract ideas.
Second, the limitations of identifying, a logistics request…, to extract and process information; in response to identifying, extracting the information from the logistics request; comparing and validating, the extracted information; reading raw text…, understanding where data was extracted incorrectly…, to associate raw text read from the logistics request with one or more data categories…, to generate at least one quote…; extracting from the body…; generating, the at least one quote for the logistics request based upon, at least in part, one or more user defined parameters; activat[ing] one or more rate sources…, dynamically select[ing] rate sources for use…; in response to the logistics request, processing, the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; and once the information is extracted and validated… processing at least one rate request; and calculating a final rate as drafted are processes that, under its/their broadest reasonable interpretation, covers performance of the limitation in the mind (i.e. mental processes) but for the recitation of generic / general computer components. That is, other than reciting a processor, logistics request receiver (e.g. email / website / electronic document), at least one GUIs includes an automated quoting validator function (e.g. general computer component and program instructions, see Application specification ¶[0018-20]; and also note that ‘quoting’ and ‘validat[ing]’ at this high level are also mental processes: judgment), computing device, graphical user interfaces, one or more rate engines (e.g. computer hardware, see Applicant specification ¶[0012]), one or more GUIs include a text analysis function (e.g. general computer component and program instructions, see Application specification ¶[0018-20]; and also note that ‘text analysis’ at this high level is a mental process: evaluation), and performing steps ‘automatically’ or ‘with no human interaction’, nothing in the claim elements preclude these steps from practically being performed in the mind, or in the mind with the assistance of pen and paper. For example, but for the generic / general purpose computer language, identifying in the context of this claim encompasses a user manually observing a logistics request in a document; extracting and processing in the context of this claim encompasses a user manually evaluating and judging information within a request / body of a source; comparing and validating in the context of this claim encompasses a user evaluating extracted information; reading in the context of this claim encompasses a user manually observing raw text; understanding in the context of this claim encompasses a user manually evaluating and judging incorrect data extracted information; associating in the context of this claim encompasses a user manually evaluating raw text and judging data categories; generating in the context of this claim encompasses a user manually judging a quote by evaluating parameters; activating in the context of this claim encompasses a user manually evaluating user defined parameters and then judging to use a rate source; selecting rate sources in the context of this claim encompasses a user manually judging to use a rate source; processing in the context of this claim encompasses a user manually evaluating and judging a quote using scored parameters and an algorithm; calculating in the context of this claim encompasses a user manually judging a final rate. If a claim limitation, under its broadest reasonable interpretation, covers performance of the limitation in the mind (e.g. an observation, evaluation, judgment) but for the recitation of generic computer components, then it falls within the ‘Mental Processes’ grouping of abstract ideas.
Third, the limitations regarding generating at least one quote and calculating a final rate recite mathematical concepts. Note that in this claim, the generating steps are determined to recite a mathematical concept because broadest reasonable interpretation includes a mathematical relationship between a quote and parameters (and this interpretation is also supported in Applicant’s specification ¶[0047]). The calculating step is determined to recite a mathematical calculation because it explicitly states it is a calculation. Thus, the claim recites a mathematical concept. If a claim limitation, under its broadest reasonable interpretation, covers mathematical concepts (e.g. mathematical relationships, mathematical calculations) but for the recitation of generic computer components, then it falls within the ‘Mathematical Concepts’ grouping of abstract ideas.
Accordingly, the claims recite an abstract idea. Analysis proceeds to Step 2A Prong Two.
Step 2A – Prong Two:
This judicial exception is not integrated into a practical application. First, claims 1-2, 4-5, 7-12, 14-15, and 17-20 as a whole merely describes how to generally ‘apply’ the concept of organizing human activities in a computer environment. The claimed computer components (i.e. a processor, logistics request receiver (e.g. email / website / electronic document), automated quoting validator function, computing device, graphical user interfaces (GUIs), one or more rate engines, text analysis function, (claim 11) one or more bots, computer) are recited at a high-level of generality and are merely invoked as tools to perform otherwise manual processes. Simply implementing the abstract idea on a generic / general purpose computer is not a practical application of the abstract idea. See MPEP 2106.04(d) and 2016.05(f). Also, (claim 11) using one or more bots in the ‘mimicking’ limitation does no more than generally link the use of the judicial exception to a particular technological environment (i.e. robotic process automation (RPA)), and as such does not provide integration into a practical application. Accordingly, these additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea.
Next, the additional element of the logistics request receiver as email / website / electronic documents (e.g. wherein the logistics request receiver is selected from a group consisting of an email, a website, or one or more electronic documents; and …a list of one or more requests extracted from the body of a predefined email address) in the limitations does no more than generally link the use of the judicial exception to a particular technological environment or field of use (i.e. Internet, computers), and as such does not provide integration into a practical application. See MPEP 2106.04(d) and 2106.05(h). Also, the courts have found that using additional elements that amount to mere instructions to apply a judicial exception using computers and the Internet does not provide a practical application. See MPEP 2106.05(f) citing Ultramercial Inc v. Hulu (Fed. Cir. 2014). Also, the element of API in the limitation wherein the logistics request receiver is configured to access the logistics request at the user level without using application programing interface (API) connections at this high level of detail is only a general linkage of the judicial exception to a technological environment / field of use which is not a practical application. Note that broadest reasonable interpretation of this limitation would include any means of logistics request receiver access of the logistics request at the user level without using API connection (e.g. manually accessing, visibly accessing) therefore this is not a linkage to a particular technical environment. Hence, this additional element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
Next, the additional element of (claim 11) performing keystroke input / point / click and its steps of wherein one or more bots are configured to… perform one or more of a keystroke input, a point, and a click on the screen are recited at a high level of generality (i.e. as a general means of gathering data for the mimicking human interactions), and amounts to mere data gathering, which is a form of insignificant extra-solution activity and not a practical application. See MPEP 2106.04(d) and 2106.05(g). Furthermore, the one or more bots, and screen (general computer components) are only being used as a tool to perform keystroke inputs / points / clicks, which is also not indicative of integration into a practical application. See MPEP 2106.04(d) and 2106.05(f). This limitation also represents using a computer in its ordinary capacity for other tasks (e.g. to receive data), and adding computer components after the fact to an abstract idea, which is not a practical application. See MPEP 2106.05(f) citing Affinity Labs v. DirecTV, 838 F.3d 1253, 1262, 120 USPQ2d 1201, 1207 (Fed. Cir 2016). Next, using one or more bots in the limitation does no more than generally link the use of the judicial exception to a particular technological environment (i.e. robotic process automation (RPA)), and as such does not provide integration into a practical application. See MPEP 2106.04(d) and 2106.05(h). Note that there are no particular technical steps regarding these inputting a keystroke, pointing / clicking on a screen more than using computers as a tool to perform an otherwise manual process (obtaining inputs / selections). Accordingly, this additional element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
Also, while identified above as an organizing human activity in Step 2A Prong One, note that the step of extracting (e.g. using an artificial intelligence to extract and process information; extracting information from the logistics request; a list of one or more requests extracted from the body of a predefined email address) is recited at a high level of generality (i.e. as a general means of gathering data for subsequent providing / generating), and also amounts to mere data gathering, which is a form of insignificant extra-solution activity and not a practical application. See MPEP 2106.04(d) and 2106.05(g). Furthermore, the processor (generic computer) / computer, is only being used as a tool in the extracting, which is also not indicative of integration into a practical application. See MPEP 2106.04(d) and 2106.05(f). Next, using artificial intelligence in the limitations does no more than generally link the use of the judicial exception to a particular technological environment (i.e. machine learning, AI), and as such does not provide integration into a practical application. See MPEP 2106.04(d) and 2106.05(h). Without any particular, technical steps regarding artificial intelligence in the claims, this general association is no more than programming a computer to perform the extracting and processing. With no particular technical steps regarding extracting (and processing) and only a general association to a computer technology, this is no more than using computers as a tool to perform an otherwise manual process (obtaining information). Accordingly, this element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
Also, while identified above as an organizing human activity in Step 2A Prong One, note that the step of reading (e.g. wherein the one or more GUIs include a text analysis function configured to read raw text from the logistics request) is recited at a high level of generality (i.e. as a general means of gathering data for subsequent understanding), and also amounts to mere data gathering, which is a form of insignificant extra-solution activity and not a practical application. See MPEP 2106.04(d) and 2106.05(g). Furthermore, the one or more GUIs include a text analysis function (general computer component and program instructions, see Application specification ¶[0018-20]), is only being used as a tool in the reading, which is also not indicative of integration into a practical application. See MPEP 2106.04(d) and 2106.05(f). With no particular technical steps regarding how the reading is accomplished, this is no more than using computers as a tool to perform an otherwise manual process (obtaining information). Accordingly, this element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
Also, while identified above as an organizing human activity in Step 2A Prong One, note that the step of providing (e.g. providing, using the processor and with no human interaction, the extracted information to at least one graphical user interface (GUI), wherein the at least one GUI includes an automated quoting validator function) is recited at a high level of generality (i.e. as a general means of gathering data for subsequent generating), and also amounts to mere transmitting data, which is a form of insignificant extra-solution activity and not a practical application. See MPEP 2106.04(d) and 2106.05(g). Furthermore, the processor, at least one GUI that includes an automated quoting validator function (generic computer; general computer component and program instructions, see Application specification ¶[0018-20]) are only being used as a tool in the providing, which is also not indicative of integration into a practical application. See MPEP 2106.04(d) and 2106.05(f). Note that there are no particular technical steps regarding providing more than using computers as a tool to perform an otherwise manual process (communicating information). Accordingly, this element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
Next, the additional element of natural language processing in the limitation automatically generate at least one quote based upon, at least in part, natural language processing does no more than generally link the use of the judicial exception to a particular technological environment or field of use (i.e. NLP), and as such does not provide integration into a practical application. See MPEP 2106.04(d) and 2106.05(h). Note that there are no particular technical steps regarding the natural language processing more than generally linking the use of the abstract idea with NLP technology. Hence, this additional element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
Next, the additional element of selecting and its steps of wherein the one or more user defined parameters are presented in at least one graphical display as one or more selectable options in a plurality of dropdown menus, wherein each dropdown menu is affiliated with an industry specific cost driver are recited at a high level of generality (i.e. as a general means of gathering data for the generating at least one quote), and amounts to mere data gathering, which is a form of insignificant extra-solution activity and not a practical application. See MPEP 2106.04(d) and 2106.05(g). Furthermore, the processor, graphical display, dropdown menus (generic computer, general computer components) are only being used as a tool to perform in a computer’s ordinary capacity (i.e. to receive data), which is also not indicative of integration into a practical application. See MPEP 2106.04(d) and 2106.05(f). Note that there are no particular technical steps regarding selecting dropdown menus more than using computers as a tool to perform an otherwise manual process (obtaining inputs / selections). Accordingly, this additional element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
Next, the additional element of recording and its step of automatically recording, using the processor, a plurality of quotes to have historical records is recited at a high level of generality (i.e. as a general means of recording / storing data from the generating), and amount to mere electronic record keeping / storing data, which is a form of insignificant extra-solution activity and not a practical application. See MPEP 2106.04(d) and 2106.05(g). Furthermore, the processor (general computer) is only being used as a tool in the recording, which is also not indicative of integration into a practical application. See MPEP 2106.04(d) and 2106.05(f). Note that there are no particular technical steps regarding recording more than using computers as a tool to perform an otherwise manual process (maintain records). Accordingly, these additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea.
Next, the additional element of obtaining / accessing and its steps of accessing one or more rate engines, using the processor and with no human interaction, for: obtaining a plurality of rate related information for each logistics request; wherein the one or more rate engines do not require input from a shipper or a carrier; are recited at a high level of generality (i.e. as a general means of gathering data for subsequent calculating), and amounts to mere data gathering, which is a form of insignificant extra-solution activity and not a practical application. See MPEP 2106.04(d) and 2106.05(g). Furthermore, the rate engines, processor (generic computer / general computer component) is only being used as a tool in the obtaining, which is also not indicative of integration into a practical application. See MPEP 2106.04(d) and 2106.05(f). Note that there are no particular technical steps regarding obtaining more than using computers as a tool to perform an otherwise manual process (retrieving information). Accordingly, this additional element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
Also, while identified above as an organizing human activity in Step 2A Prong One, note that the step of publishing (e.g. wherein the automated quoting validator function is further configured to publish a list of one or more requests…; publishing the final rate in the at least one graphical user interface) is recited at a high level of generality (i.e. as a general means of transmitting / outputting results of the extracting, as a general means of transmitting / outputting results of the calculating), and also amounts to mere transmitting / outputting data, which is a form of insignificant extra-solution activity and not a practical application. See MPEP 2106.04(d) and 2106.05(g). Furthermore, the processor, at least one graphical user interface, automated quoting validator function (generic computer, general computer components, computer component with program instructions) are only being used as a tool in the publishing, which is also not indicative of integration into a practical application. See MPEP 2106.04(d) and 2106.05(f). Note that there are no particular technical steps regarding publishing more than using computers as a tool to perform an otherwise manual process (communicating information). Accordingly, this element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
The combination of these additional elements is no more than mere instructions to apply the exception using generic computers / general computer components (computing device, processor, logistics request receiver, at least one GUI that includes an automated quoting validator function, rate engines, at least one graphical user interface, one or more GUIs include a text analysis function, (claim 11) one or more bots); and adding high-level extra-solution activities (data gathering, transmitting data, storing data, outputting data), and generally linking the judicial exception with a technology or field of use (e.g. Internet, AI, NLP, RPA, without API). Accordingly, even in combination, these additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limitations on practicing the abstract idea. Hence, the claim is directed to an abstract idea. Analysis proceeds to Step 2B.
Step 2B:
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the additional element of using a computing device, processor, logistics request receiver, at least one GUI that includes an automated quoting validator function, rate engines, at least one graphical user interface, one or more GUIs include a text analysis function, (claim 11) one or more bots, to perform automatically / ‘with no human interaction’ identifying a logistics request…, accessing the logistics request at the user level…, extracting and processing information…, mimicking human interaction…, extracting information from the logistics request…, comparing and validating the extracted information…, reading raw text…, understanding where data was extracted incorrectly…, associate raw text read from the logistics request with one or more data categories…, providing the extracted information…, generating at least one quote…, publishing a list of one or more requests extracted from the body…, activat[ing] one or more rate sources…, dynamically select[ing] rate sources for use…, processing at least one rate request…, calculating a final rate…, and publishing the final rate, do not require input from a shipper or carrier to no more than mere instructions to ‘apply’ the exception using generic computers. The same analysis applies here in Step 2B, i.e. mere instructions to apply an exception on a generic computer cannot integrate a judicial exception into a practical application at Step 2A or provide an inventive concept in Step 2B. See MPEP 2106.05(f). Also, (claim 11) using one or more bots in the ‘mimicking’ limitation does no more than generally link the use of the judicial exception to a particular technological environment (i.e. RPA), and as such does not provide integration into a practical application or provide an inventive concept. Regarding the logistics request receiver, note the Applicant specification ¶[0001], ¶[0003] (and the claim language) states that the logistics request receiver may be an electronic document (i.e. general computer component). Regarding the automated quoting validator function, the specification does not explicitly state an automated quoting validator ‘function’, however Applicant specification Figure 2, ¶[0018-20], ¶[0025], ¶[0027] states that the blocks in the flowcharts are implemented by computer program instructions provided to a processor of a general purpose computer; and the automated quoting process as a whole may reside on a server computer or client device / personal computer (i.e. general purpose computer, or a general computer component). Regarding the text analysis function, note that Applicant specification ¶[0044] details reading text and understanding failures at a high level of detail and without explicitly reciting a text analysis ‘function’, however Applicant specification ¶[0012], ¶[0018-20] details that the disclosure may take the form of entirely hardware / entirely software or combining software and hardware (i.e. a general purpose computer, or general computer component) and the blocks in the flowcharts are implemented by computer program instructions. Regarding the (claim 11) one or more bots, note that Applicant specification ¶[0036] details these are software code performing human tasks in a computer. Also see the Wikipedia ‘Robotic process automation’ entry <https://en.wikipedia.org/wiki/Robotic_process_automation> (<http://web.archive.org/web/20200512073119/https://en.wikipedia.org/wiki/Robotic_process_automatio> captured using Wayback Machine on 12 May 2020) discussing the nature of using one or more bots as routine / well-known / conventional (Wikipedia ‘robotic process automation’ Historic Evolution section ¶2 details the concept has been around for a long time, RPA actual deployment section details its use in Customer Care Automation and OCR Application). Hence, these features do not provide an inventive concept / significantly more.
As discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the additional element regarding the logistics request receiver as email / website / electronic documents (e.g. wherein the logistics request receiver is selected from a group consisting of an email, a website, or one or more electronic documents; and …a list of one or more requests extracted from the body of a predefined email address) does no more than generally link the use of the judicial exception to a particular technological environment or field of use (i.e. Internet, computers). The same analysis applies here in Step 2B, i.e. generally linking the use of the judicial exception to a particular technological environment or field of use does not provide integration into a practical application in Step 2A or provide an inventive concept in Step 2B. See MPEP 2106.05(h). Also, the courts have found that using additional elements that amount to mere instructions to apply a judicial exception using computers and the Internet does not provide a practical application or significantly more. See MPEP 2106.05(f) citing Ultramercial Inc v. Hulu (Fed. Cir. 2014). Also, the element of API in the limitation wherein the logistics request receiver is configured to access the logistics request at the user level without using application programing interface (API) connections at this high level of detail is only a general linkage of the judicial exception to a technological environment / field of use which is not significantly more. Note that broadest reasonable interpretation of this limitation would include any means of logistics request receiver access of the logistics request at the user level without using API connection (e.g. manually accessing, visibly accessing) therefore this is not a linkage to a particular technical environment. Furthermore, see the Applicant’s specification ¶[0035], ¶[0040-41], ¶[0044] describing the additional element of using an email for identifying a logistics request at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). See the Applicant’s specification ¶[0045], ¶[0050] describing the additional element of using a website / portal for identifying a logistics request at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). See the Applicant’s specification ¶[0035], ¶[0040] describing the additional element of using a PDF / electronic document for identifying a logistics request at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). See the Applicant’s specification ¶[0048], ¶[0051], ¶[0070] describing the additional element of using RPA or ‘any other suitable approach’ in place of API, and providing access through user level which doesn’t require API connections at such a high level that indicates this element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). Hence, these features do not provide an inventive concept / significantly more.
As discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the additional elements regarding the (claim 11) performing keystroke input / point / click are recited at a high level of generality (i.e. as a general means of gathering data for the mimicking human interactions), and amounts to mere data gathering, which is a form of insignificant extra-solution activity. The same analysis applies here in Step 2B, i.e. adding insignificant extra-solution activity to the judicial exception does not provide integration into a practical application in Step 2A or provide an inventive concept in Step 2B. See MPEP 2106.05(g). The use of the computer (i.e. the one or more bots, and screen) in these steps merely represents using a generic / general purpose computer as a tool, and is not indicative of an inventive concept. See MPEP 2106.05(f). Using one or more bots in the limitation does no more than generally link the use of the judicial exception to a particular technological environment (i.e. RPA), and as such does not provide significantly more. See MPEP 2106.05(h). This limitation also represents using a computer in its ordinary capacity for other tasks (e.g. to receive data), and adding computer components after the fact to an abstract idea, which is not significantly more. See MPEP 2106.05(f) citing Affinity Labs v. DirecTV, 838 F.3d 1253, 1262, 120 USPQ2d 1201, 1207 (Fed. Cir 2016). Note that using a computer to perform functions / tasks faster or more efficient is not a practical application or significantly more. See MPEP 2106.05(f) citing Intellectual Ventures I LLC v. Capital One Bank (USA), 792 F.3d 1363, 1367, 115 USPQ2d 1636, 1639 (Fed. Cir 2015) stating “claiming the improved speed or efficiency inherent with applying the abstract idea on a computer” does not integrate a judicial exception into a practical application or provide an inventive concept”. Furthermore, these input steps are also claimed at a high level of generality, and/or as insignificant extra-solution activities (e.g. data gathering) representing computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular receiving or transmitting data over a network (Symantec), recording a customer’s order (Apple). Hence, these features do not provide an inventive concept / significantly more. See the Applicant’s specification ¶[0036] describing the additional element of a bot performing a keystroke input, a point, and a click on the screen to mimic the human interaction with a computer at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). See the Wikipedia ‘Robotic process automation’ entry <https://en.wikipedia.org/wiki/Robotic_process_automation> (<http://web.archive.org/web/20200512073119/https://en.wikipedia.org/wiki/Robotic_process_automatio> captured using Wayback Machine on 12 May 2020) discussing the nature of using one or more bots as routine / well-known / conventional (Wikipedia ‘robotic process automation’ Historic Evolution section ¶2 details the concept has been around for a long time, RPA actual deployment section details its use in Customer Care Automation and OCR Application). Hence, these limitations do not provide an inventive concept.
Also, as discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the Step 2A Prong One organizing human activity elements regarding the extracting are recited at a high level of generality (i.e. as a general means of gathering data for subsequent providing / generating), and also amounts to the extra-solution activity of data gathering, which is not a practical application or an inventive concept. See MPEP 2106.05(g). The use of the computer (i.e. processor / computer) in these steps merely represents using a generic / general purpose computer as a tool; and the use of artificial intelligence at this high level of detail does no more than generally link the use of the judicial exception to a technological environment (i.e. machine learning, AI), neither of which are indicative of an inventive concept. See MPEP 2106.05(f) and MPEP 2106.05(h). Furthermore, this extracting step is also claimed at a high level of generality, and/or as an insignificant extra-solution activity (e.g. data gathering) representing computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular electronically scanning or extracting data from a physical document (Content Extraction); recording a customer’s order (Apple). See the Applicant’s specification ¶[0035], ¶[0040], ¶[0043] describing the additional element of using optical character recognition / artificial intelligence / natural language processing to process rate quoting requests in the quoting process at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). Hence, these limitations do not provide an inventive concept.
Also, as discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the Step 2A Prong One organizing human activity elements regarding the reading are recited at a high level of generality (i.e. as a general means of gathering data for subsequent understanding), and also amounts to the extra-solution activity of data gathering, which is not a practical application or an inventive concept. See MPEP 2106.05(g). The use of the computers (i.e. one or more GUIs includes a text analysis function) in these steps merely represents using a general purpose computer / general computer component as a tool, and is not indicative of an inventive concept. See MPEP 2106.05(f). Furthermore, this reading step is also claimed at a high level of generality, and/or as an insignificant extra-solution activity (e.g. data gathering) representing computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular electronically scanning or extracting data from a physical document (Content Extraction); recording a customer’s order (Apple). Hence, these limitations do not provide an inventive concept.
Also, as discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the Step 2A Prong One organizing human activity elements regarding the providing are recited at a high level of generality (i.e. as a general means of sending data for subsequent generating), and also amounts to the extra-solution activity of transmitting data, which is not a practical application or an inventive concept. See MPEP 2106.05(g). The use of the computers (i.e. processor, at least one graphical user interface, automated quoting validator) in these steps merely represents using generic / general purpose computers as a tool, and is not indicative of an inventive concept. See MPEP 2106.05(f). Furthermore, this providing step is also claimed at a high level of generality, and/or as an insignificant extra-solution activity (e.g. transmitting data) representing computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular receiving or transmitting data over a network (Symantec), sending messages over a network (OIP Techs), a computer receives and sends information over a network (buySAFE). Hence, these limitations do not provide an inventive concept.
As discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the additional element regarding natural language processing does no more than generally link the use of the judicial exception to a particular technological environment or field of use (i.e. NLP). The same analysis applies here in Step 2B, i.e. generally linking the use of the judicial exception to a particular technological environment or field of use does not provide integration into a practical application in Step 2A or provide an inventive concept in Step 2B. See MPEP 2106.05(h). See the Applicant’s specification ¶[0035], ¶[0040-43] describing the additional element of using optical character recognition / artificial intelligence / natural language processing to process rate quoting requests in the quoting process at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). See ’10 Examples of Natural Language Processing in Action‘ (captured on Wayback Machine 2 November 2021 <http://web.archive.org/web/20211102170747/https://monkeylearn.com/blog/natural-language-processing-examples/>) to Roldos detailing common examples of natural language processing include smart assistants (responding to queries), customer service automation, email filtering, text analytics, (Roldos Section 3. Smart Assistants ¶2 beginning “These smart assistants such as Siri or Alexa, use voice recognition…”; Section 4. Customer Service Automation ¶3-4 beginning “NLP can be used to detect sentiment and keywords in emails…”; Section 5. Email Filters ¶3 beginning “Behind all of these filters NLP is at work. As your emails come into your inbox…”; Section 9. Text Analytics ¶2 beginning “NLP is special in that it has the capability to make sense of these reams of unstructured information…”; before ‘The Wrap Up’ ¶ beginning “These are the most common natural language processing examples that you are likely to encounter…”). Also, the recitation of the at least one GUI includes an automated quoting validator function is a computer component recited at a high level of generality and amounts to ‘applying’ the abstract idea on a generic computer. Hence, these limitations do not provide an inventive concept.
As discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the additional elements regarding the selecting are recited at a high level of generality (i.e. as a general means of gathering data for the generating at least one quote), and amounts to mere data gathering, which is a form of insignificant extra-solution activity. The same analysis applies here in Step 2B, i.e. adding insignificant extra-solution activity to the judicial exception does not provide integration into a practical application in Step 2A or provide an inventive concept in Step 2B. See MPEP 2106.05(g). The use of the computer (i.e. processor, graphical display, dropdown menus ) in these steps merely represents using a generic / general purpose computer as a tool, and is not indicative of an inventive concept. See MPEP 2106.05(f). Furthermore, these input steps are also claimed at a high level of generality, and/or as insignificant extra-solution activities (e.g. data gathering) representing computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular receiving or transmitting data over a network (Symantec), recording a customer’s order (Apple). Hence, these features do not provide an inventive concept / significantly more. See the Applicant’s specification ¶[0053] describing the additional element of selectable drop-down menus at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). Hence, these features do not provide an inventive concept / significantly more.
As discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the additional elements regarding the recording are recited at a high level of generality (i.e. as a general means of recording / storing data from the generating), and amount to mere electronic record keeping / storing data, which is a form of insignificant extra-solution activity. The same analysis applies here in Step 2B, i.e. adding insignificant extra-solution activity to the judicial exception does not provide integration into a practical application in Step 2A or provide an inventive concept in Step 2B. See MPEP 2106.05(g). The use of the computer (i.e. processor) in these steps merely represents using a generic / general purpose computer as a tool, and is not indicative of an inventive concept. See MPEP 2106.05(f). Furthermore, these recording steps are also claimed at a high level of generality, and/or as insignificant extra-solution activities (e.g. data storage) representing computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular electronic record keeping (Alice), storing and retrieving information in memory (Versata; OIP Techs). Hence, these features do not provide an inventive concept / significantly more.
As discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the additional elements regarding the obtaining / accessing are recited at a high level of generality (i.e. as a general means of gathering data for subsequent calculating), and amounts to mere data gathering, which is a form of insignificant extra-solution activity. The same analysis applies here in Step 2B, i.e. adding insignificant extra-solution activity to the judicial exception does not provide integration into a practical application in Step 2A or provide an inventive concept in Step 2B. See MPEP 2106.05(g). The use of the computer (i.e. the rate engines, processor) in these steps merely represents using a generic / general purpose computer as a tool, and is not indicative of an inventive concept. See MPEP 2106.05(f). Furthermore, these obtaining steps are also claimed at a high level of generality, and/or as insignificant extra-solution activities (e.g. data gathering) representing computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular receiving or transmitting data over a network (Symantec), sending messages over a network (OIP Techs), a computer receives and sends information over a network (buySAFE), storing and retrieving information in memory (Versata; OIP Techs).Hence, these features do not provide an inventive concept / significantly more.
Also, as discussed above in Step 2A Prong Two with respect to integration of the abstract idea into a practical application, the Step 2A Prong One organizing human activity elements regarding the publishing are recited at a high level of generality (i.e. as a general means of transmitting / outputting results of the calculating), and also amounts to the extra-solution activity of transmitting data / outputting data, which is not a practical application or an inventive concept. See MPEP 2106.05(g). The use of the computer (i.e. processor, rate engines, at least one graphical user interface) in these steps merely represents using a generic / general purpose computer as a tool, and is not indicative of an inventive concept. See MPEP 2106.05(f). Furthermore, these publishing steps are also claimed at a high level of generality, and/or as insignificant extra-solution activities (e.g. outputting data) representing computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular transmitting data over a network (Symantec), sending messages over a network (OIP Techs), a computer receives and sends information over a network (buySAFE), presenting offers (OIP Techs). Hence, these features do not provide an inventive concept / significantly more.
The claims do not improve another technology or technical field. Instead the claims represent a generic implementation of organizing human activities ‘applied’ by generic / general purpose computers, generally ‘applied’ to technologies and field of use, and using general computer components in extra-solution capacities such as data gathering / transmitting data / storing data. The claims do not provide meaningful limitations beyond generally linking the user of an abstract idea to a particular technological environment. At best, the claims are more directed towards solving a business / economic / entrepreneurial problem (i.e. generating quotes from a logistics request source), that is tangentially associated with technology elements (e.g. computers, Internet, AI, NLP, RPA, not API), rather than solving a technology based problem. See MPEP 2106.05(a). The claims do not improve the functioning of a computer itself. The claims are more directed towards improving a business / economic / entrepreneurial process rather than improving a computer outside of a business use, i.e. using computers a tool. The claims do not apply the judicial exception with or by use of a particular machine. The claims do not effect a transformation or reduction to a particular article to a different state or thing. The claims do not add a specific limitation other than what is well understood, routine, and conventional in a way that confines the claim to a particular useful application.
Viewing the claim limitations as an ordered combination does not add anything further than looking at each of the claim limitations individually, both with respect to the independent claims 1 and 11, and further considering the addition of dependent claims 2, 4-5, 7-10, 12, 14-15, and 17-20. Note that the combination of limitations and claim elements add nothing that is not already present when the steps are considered separately, simply reciting implementation as performed by using generic computers / general computer components, see Alice (2014), and does not provide a non-conventional and non-generic arrangement of various computer components to achieve a technical improvement, see BASCOM Global Internet v. AT&T Mobility LLC (2016). Hence, the ordered combination of elements does not provide significantly more. With respect to the dependent claims:
Dependent claims 2 and 12: The limitation displaying the at least one quote at the at least one graphical user interface is further directed to a method of organizing human activity (fundamental economic principles or practices, commercial interactions, marketing or sales activities or behaviors, managing personal behavior or relationships or interactions between people, and following rules or instructions) as described in the independent claims. The recitation of the graphical user interface is another computer component recited at a high level of generality and amounts to ‘applying’ the abstract idea on a generic computer. Similar to the independent claims, this recitation does not meaningfully integrate the abstract idea in a practical application, and is not significantly more than the abstract idea.
Dependent claims 4 and 14: The limitation wherein the automated quoting validator function automatically generates the at least one quote based upon, at least in part, optical character recognition or artificial intelligence represents an additional element (general linkage to technology) that is not indicative of a practical application or significantly more. Note that there are no particular technical steps regarding the optical character recognition or artificial intelligence more than generally linking the use of the abstract idea with a technology (OCR, AI). Furthermore, optical character recognition is claimed at a high level of detail, and represents computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular electronically scanning or extracting data from a physical document (Content Extraction). See the Applicant’s specification ¶[0035], ¶[0040] describing the additional element of using optical character recognition / OCR at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). See the Applicant’s specification ¶[0035], ¶[0041], ¶[0045], ¶[0053] describing the additional element of using artificial intelligence at such a high level that indicates this additional element is sufficiently well-known that the specification does not need to describe the particulars to satisfy 35 USC 112(a). Also, the recitation of the automated quoting validator function is a computer component recited at a high level of generality and amounts to ‘applying’ the abstract idea on a generic computer / general computer component (noting the independent claims recite “wherein the at least one GUI includes an automated quoting validator function”). . Similar to the independent claims, this recitation does not meaningfully integrate the abstract idea in a practical application, and is not significantly more than the abstract idea.
Dependent claims 5 and 15: The limitation wherein the automated quoting validator function automatically generates the at least one quote at one or more predefined intervals merely narrows the previously recited abstract idea limitations. The recitation of the automated quoting validator function is a computer component recited at a high level of generality and amounts to ‘applying’ the abstract idea on a generic computer / general computer component (noting the independent claims recite “wherein the at least one GUI includes an automated quoting validator function”). For the reasons described above with respect to the independent claims, these judicial exceptions are not meaningfully integrated into a practical application, or significantly more than an abstract idea
Dependent claims 7 and 17: The limitation automatically providing the at least one quote back to the logistics request receiver is further directed to a method of organizing human activity (fundamental economic principles or practices, commercial interactions, marketing or sales activities or behaviors, managing personal behavior or relationships or interactions between people) as described in the independent claim. The recitation of logistics request receiver is a computer component recited at a high level of generality and amounts to ‘applying’ the abstract idea on computers. Similar to the independent claims, this recitation does not meaningfully integrate the abstract idea in a practical application, and is not significantly more than the abstract idea. Also note that providing here is claimed at such a high level of detail that it represents the extra-solution activity of transmitting data (i.e. a general means of transmitting the results of the generating), which is not a practical application or significantly more; and represents computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular receiving or transmitting data over a network (Symantec), sending messages over a network (OIP Techs), a computer receives and sends information over a network (buySAFE). Similar to the independent claims and the claims above, this recitation does not meaningfully integrate the abstract idea in a practical application, and is not significantly more than the abstract idea.
Dependent claims 8 and 18: The limitation storing the at least one quote at a database represents an additional element (the extra-solution activity of data storage / electronic record keeping) that is not indicative of a practical application or significantly more. The recitation of the database is another computer component recited at a high level of generality and amounts to using a computer component as a tool in its ordinary capacity. Furthermore, the storing step here is claimed at a high level of detail, and represents computer functions that the courts have recognized as well-understood, routine, and conventional functions that do not present an inventive concept. See MPEP 2106.05(d)(II) in particular electronic record keeping (Alice), storing and retrieving information in memory (Versata; OIP Techs). For the reasons described above with respect to the independent claims, this judicial exception is not meaningfully integrated into a practical application, and is not significantly more than the abstract idea.
Dependent claims 9 and 19: The limitation displaying, using the automated quoting validator function, the logistics request and the extracted information simultaneously at the at least one graphical user interface is further directed to a method of organizing human activity (managing personal behavior or relationships or interactions between people, and following rules or instructions) as described in the independent claim. The recitation of the automated quoting validator function and graphical user interface are computer components recited at a high level of generality and amounts to ‘applying’ the abstract idea on a generic computer / general computer component. Similar to the independent claims and the claims above, this recitation does not meaningfully integrate the abstract idea in a practical application, and is not significantly more than the abstract idea.
Dependent claims 10 and 20: The limitation wherein displaying includes the plurality of rate related information for each logistics request merely narrows the previously recited abstract idea limitations. For the reasons described above with respect to the independent claims and the claims above, these judicial exceptions are not meaningfully integrated into a practical application, or significantly more than an abstract idea.
Therefore claims 1, 11, and the dependent claims 2, 4-5, 7-10, 12, 14-15, and 17-20 and all limitations taken both individually and as an ordered combination, do not integrate the judicial exception into a practical application, nor do they include additional elements that are sufficient to amount to significantly more than the judicial exception. Accordingly, claims 1-2, 4-5, 7-12, 14-15, and 17-20 are ineligible.
Novelty / Non-Obviousness
Claims 1-2, 4-5, 7-12, 14-15, 17-20 are not rejected under 35 USC 102 or 35 USC 103.
Claims 1-2, 4-5, and 7-10:
The Examiner knows of no art which teaches or suggests the following combination of limitations together as recited in claim 1 (and similarly recited in dependent claims 2, 4-5, 7-10).
automatically identifying, using a processor and with no human interaction, a logistics request from a logistics request receiver, wherein the logistics request receiver is selected from a group consisting of an email, a website, or one or more electronic documents using an artificial intelligence to extract and process information, wherein the logistics request receiver is configured to access the logistics request at the user level without using application programing interface (API) connections;
in response to automatically identifying, extracting the information from the logistics request;
comparing and validating, using the processor and with no human interaction, the extracted information using one or more graphical user interfaces (GUIs),
wherein the one or more GUIs include a text analysis function configured to read raw text from the logistics request and to understand where data was extracted incorrectly, wherein the text analysis function is configured to automatically associate raw text read from the logistics request with one or more data categories including at least one of a pick up location, a delivery location, a commodity, a weight, or physical dimensions;
providing, using the processor and with no human interaction, the extracted information to at least one graphical user interface (GUI), wherein the at least one GUI includes an automated quoting validator function configured to automatically generate at least one quote based upon, at least in part, natural language processing,
wherein the automated quoting validator function is further configured to publish a list of one or more requests extracted from the body of a predefined email address;
automatically generating, using the processor and with no human interaction, the at least one quote for the logistics request at the automated quoting validator function based upon, at least in part, one or more user defined parameters,
wherein the processor enables real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use by the automated quoting validator function to generate the at least one quote,
wherein the one or more user defined parameters are presented in at least one graphical display as one or more selectable options in a plurality of dropdown menus, wherein each dropdown menu is affiliated with an industry specific cost driver,
wherein at least one of the one or more user defined parameters is configured to define a percentage margin outside of which quotes are discarded,
wherein at least one of the one or more user defined parameters is configured to define an afterhours window and to charge an additional fee for shipments that are required to be picked up during this predefined period of time,
wherein at least one of the one or more user defined parameters is configured to define a minimum rate and profit based on different distance tiers;
automatically recording, using the processor and with no human interaction, a plurality of quotes to have historical records;
in response to the logistics request, processing, using the processor and with no human interaction, the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; and
once the information is extracted and validated, accessing one or more rate engines, using the processor and with no human interaction, for:
obtaining a plurality of rate related information for each logistics request;
processing at least one rate request;
calculating a final rate; and
publishing the final rate in the at least one graphical user interface,
wherein the one or more rate engines do not require input from a shipper or carrier.
The closest prior art of He (US 2020/0211077 A1) details automatically identifying, using a processor, a logistics request from a logistics request receiver; wherein the logistics request is selected from a group consisting of an email, a website, or one or more electronic documents using an artificial intelligence to extract and process information; using an API or querying a database to match on keywords and return results; in response to automatically identifying, extracting the information from the logistics request; comparing and validating, using the processor, the extracted information; reading raw text from the logistics request, associating raw text with products / item weights / dimensions / logistical information; providing using the processor the extracted information to an automated quoting validator configured to automatically generate at least one quote based upon at least in part natural language processing; requests are extracted from the body of an email; automatically generating, using the processor, the at least one quote for the logistics request at the automated quoting validator based upon, at least in part, one or more user defined parameters; in response to the logistics request, processing, using the processor, the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; once the information is extracted and validated, accessing one or more rate engines; using the processor for: obtaining a plurality of rate related information for each logistics request; processing at least one rate request; calculating a final rate; and publishing the final rate in the at least one graphical user interface, the rate engine generates shipping fees but does not require input from a shipper / carrier (He Fig 3-4, ¶[0006], ¶[0022], ¶[0029], ¶[0037], ¶[0041], ¶[0055-56], ¶[0087], ¶[0090-93], ¶[0097-102], ¶[0197], claim 1, claim 17). However, He does not explicitly state a text analysis function to understand where data was extracted incorrectly; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; publishing a list of one or more requests extracted from the body of a predefined email address; and automatically recording using the processor a plurality of quotes to have historical records; real-time activation of one or more rate sources dynamically selected based on user defined parameters
The prior art of Lee (US 2010/0107190 A1) details comparing and validating, using the processor, the extracted information using one or more graphical user interfaces (displaying the original request) (Lee Fig 4-5, ¶[0012-14], ¶[0037], ¶[0072-73]). However, Lee does not explicitly state processing logistics requests with extraction including extraction from email / email address; a text analysis function to understand where data was extracted incorrectly; publishing a list of one or more requests extracted from the body of a predefined email address; automatically recording using the processor a plurality of quotes to have historical records; real-time activation of one or more rate sources dynamically selected based on user defined parameters
Next, the prior art of Middendorf (US 2019/0332662 A1) details extracting information by optical character recognition from electronic documents / email; viewing the data extracted in tables through a user interface; users providing corrections to the extracted data if incorrect; and correcting the local machine learning model to learn from the corrections (Middendorf ¶[0005], ¶[0009-10], ¶[0027]). However, Middendorf does not explicitly state processing logistics requests with extraction and quoting; publishing a list of one or more requests extracted from the body of a predefined email address; automatically recording using the processor a plurality of quotes to have historical records; and real-time activation of one or more rate sources dynamically selected based on user defined parameters
Next, the prior art of Lutnick (US 2008/0161945 A1) details responding to requests by a user; filtering reports data stored in the system associated with an email address, and reports involve potential delivery service and product delivery (Lutnick ¶[0536-538], claim 19). However, Lutnick does not explicitly state processing logistics requests with extraction including extraction and quoting; a text analysis function to understand where data was extracted incorrectly; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; automatically recording using the processor a plurality of quotes to have historical records; and real-time activation of one or more rate sources dynamically selected based on user defined parameters
Next, the prior art of Morimoto (US 2002/0169710 A1) automatically recording, using the processor, a plurality of quotes to have historical records when storing shipping quotes (Morimoto ¶[0047], ¶[0010], claim 16). However, Morimoto does not explicitly state processing logistics requests with extraction; a text analysis function to understand where data was extracted incorrectly; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; publishing a list of one or more requests extracted from the body of a predefined email address; real-time activation of one or more rate sources dynamically selected based on user defined parameters.
Next, the prior art of Cahill et al. (US 2012/0036158 A1) details a travel booking method and system that receives inputs from a user, provides access to one or more sources of data by applying a business logic layer in a predetermined manner based on the rules, preferences, and search criteria with simultaneous search to the applicable sources of data to identify potentially suitable travel products, and presenting the travel products on the interface; searching and providing prices and quotes for air flight reservations (Cahill Abstract, ¶[0014], ¶[0042], ¶[0058]). However, Cahill does not explicitly state: processing logistics requests with extraction; a text analysis function to understand where data was extracted incorrectly; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; publishing a list of one or more requests extracted from the body of a predefined email address; and automatically recording using the processor a plurality of quotes to have historical records.
Next, the prior art of Lukis et al. (US 7,840,443 B2) details an automated quoting system that involves changing menu-driven parameters that impact cost to achieve the desired quotation that the operator desires (Lukis col 25 ln 6-15).
Next, the prior art of Benchaya (WO 2019/145960) details a transportation system that will provide a more competitive offer with opportunities according to total profit with more than one delivery, and reject delivery requests which are less profitable (Benchaya pg. 5 ¶ beginning “The present invention discloses a method for selecting…”).
Next, the prior art of Lam (US 2023/0143975 A1) details a dynamic pricing system that adjusts and adapts billable rates for service scenarios such as after-hours services based on rules and changes to routine services (Lam ¶[0003], ¶[0027]).
Net, the prior art of James (US 2014/0067490 A1) details a dynamic fare system that identifies a priced transportation option based on zone travel and distance, including transportation across multiple zones where the fare calculations are made according to the distance traveled within the relevant zones / jurisdictions, and zones are pre-defined (James Fig 5F-5G, ¶[0121], ¶[0140], ¶[0147], ¶[0154]).
The collective references of He, Lee, Middendorf, Lutnick, Morimoto, Cahill, Lukis, Benchaya, Lam, and James teach the features of claim 1 individually, however it would not have been obvious to one or ordinary skill in the art before the effective filing data of the claimed invention to combine each of these teachings together to reproduce the invention of claim 1. Thus, the art on record fails to collectively teach “automatically identifying, using a processor and with no human interaction, a logistics request from a logistics request receiver, wherein the logistics request receiver is selected from a group consisting of an email, a website, or one or more electronic documents using an artificial intelligence to extract and process information, wherein the logistics request receiver is configured to access the logistics request at the user level without using application programing interface (API) connections; in response to automatically identifying, extracting the information from the logistics request; comparing and validating, using the processor and with no human interaction, the extracted information using one or more graphical user interfaces (GUIs), wherein the one or more GUIs include a text analysis function configured to read raw text from the logistics request and to understand where data was extracted incorrectly, wherein the text analysis function is configured to automatically associate raw text read from the logistics request with one or more data categories including at least one of a pick up location, a delivery location, a commodity, a weight, or physical dimensions; providing, using the processor and with no human interaction, the extracted information to at least one graphical user interface (GUI), wherein the at least one GUI includes an automated quoting validator function configured to automatically generate at least one quote based upon, at least in part, natural language processing, wherein the automated quoting validator function is further configured to publish a list of one or more requests extracted from the body of a predefined email address; automatically generating, using the processor and with no human interaction, the at least one quote for the logistics request at the automated quoting validator function based upon, at least in part, one or more user defined parameters, wherein the processor enables real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use by the automated quoting validator function to generate the at least one quote, wherein the one or more user defined parameters are presented in at least one graphical display as one or more selectable options in a plurality of dropdown menus, wherein each dropdown menu is affiliated with an industry specific cost driver, wherein at least one of the one or more user defined parameters is configured to define a percentage margin outside of which quotes are discarded, wherein at least one of the one or more user defined parameters is configured to define an afterhours window and to charge an additional fee for shipments that are required to be picked up during this predefined period of time, wherein at least one of the one or more user defined parameters is configured to define a minimum rate and profit based on different distance tiers; automatically recording, using the processor and with no human interaction, a plurality of quotes to have historical records; in response to the logistics request, processing, using the processor and with no human interaction, the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; and once the information is extracted and validated, accessing one or more rate engines, using the processor and with no human interaction, for: obtaining a plurality of rate related information for each logistics request; processing at least one rate request; calculating a final rate; and publishing the final rate in the at least one graphical user interface, wherein the one or more rate engines do not require input from a shipper or carrier” as substantially required by independent claim 1.
Claims 11-12, 14-15, and 17-20:
The Examiner knows of no art which teaches or suggests the following combination of limitations together as recited in claim 11 (and similarly recited in dependent claims 12, 14-15, 17-20).
a computing device having at least one processor configured to automatically identify a logistics request from a logistics request receiver with no human interaction, wherein the logistics request receiver is selected from a group consisting of an email, a website, or one or more electronic documents using an artificial intelligence to extract and process information, wherein the logistics request receiver is configured to access the logistics request at the user level without using application programing interface (API) connections, wherein one or more bots are configured to mimic human interaction with a computer and to perform one or more of a keystroke input, a point, and a click on the screen, wherein in response to automatically identifying, the at least one processor is configured to extract the information from the logistics request with no human interaction, wherein the at least one processor is configured to compare and validate the extracted information using one or more graphical user interfaces (GUIs) with no human interaction, wherein the one or more GUIs include a text analysis function configured to read raw text from the logistics request and to understand where data was extracted incorrectly, wherein the text analysis function is configured to automatically associate raw text read from the logistics request with one or more data categories including at least one of a pick up location, a delivery location, a commodity, a weight, or physical dimensions, wherein the at least one processor is configured to provide the extracted information to a graphical user interface (GUI), wherein the GUI includes an automated quoting validator function configured to automatically generate at least one quote based upon, at least in part, natural language processing with no human interaction, wherein the automated quoting validator function is further configured to publish a list of one or more requests extracted from the body of a predefined email address, wherein the at least one processor is configured to automatically generate the at least one quote for the logistics request at the automated quoting validator function based upon, at least in part, one or more user defined parameters with no human interaction, wherein the one or more user defined parameters are presented in at least one graphical display as one or more selectable options in a plurality of dropdown menus, wherein each dropdown menu is affiliated with an industry specific cost driver, wherein at least one of the one or more user defined parameters is configured to define a percentage margin outside of which quotes are discarded, wherein at least one of the one or more user defined parameters is configured to define an afterhours window and to charge an additional fee for shipments that are required to be picked up during this predefined period of time, wherein at least one of the one or more user defined parameters is configured to define a minimum rate and profit based on different distance tiers, wherein the at least one processor is configured to automatically record a plurality of quotes to have historical records with no human interaction, wherein the at least one processor is configured to enable real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use by the automated quoting validator function to generate the at least one quote, wherein in response to the logistics request the at least one processor is configured to process the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting logic parameters with no human interaction, and wherein once the information is extracted and validated, the at least one processor is configured to access one or more rate engines with no human interaction to: obtain a plurality of rate related information for each logistics request, process at least one rate request, calculate a final rate, and publish the final rate in the at least one graphical user interface, wherein the one or more rate engines do not require input from a shipper or a carrier.
The closest prior art of He (US 2020/0211077 A1) details automatically identifying, using a processor, a logistics request from a logistics request receiver; wherein the logistics request is selected from a group consisting of an email, a website, or one or more electronic documents using an artificial intelligence to extract and process information; using an API or querying a database to match on keywords and return results; in response to automatically identifying, extracting the information from the logistics request; comparing and validating, using the processor, the extracted information; reading raw text from the logistics request, associating raw text with products / item weights / dimensions / logistical information; providing using the processor the extracted information to an automated quoting validator configured to automatically generate at least one quote based upon at least in part natural language processing; requests are extracted from the body of an email; automatically generating, using the processor, the at least one quote for the logistics request at the automated quoting validator based upon, at least in part, one or more user defined parameters; in response to the logistics request, processing, using the processor, the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting parameters; once the information is extracted and validated, accessing one or more rate engines; using the processor for: obtaining a plurality of rate related information for each logistics request; processing at least one rate request; calculating a final rate; and publishing the final rate in the at least one graphical user interface, the rate engine generates shipping fees but does not require input from a shipper / carrier (He Fig 3-4, ¶[0006], ¶[0022], ¶[0029], ¶[0037], ¶[0041], ¶[0055-56], ¶[0087], ¶[0090-93], ¶[0097-102], ¶[0197], claim 17). However, He does not explicitly state using bots to mimic human interaction with a computer and perform keystroke input / point / click functions; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; publishing a list of one or more requests extracted from the body of a predefined email address; automatically recording using the processor a plurality of quotes to have historical records; real-time activation of one or more rate sources dynamically selected based on user defined parameters.
The prior art of Lee (US 2010/0107190 A1) details comparing and validating, using the processor, the extracted information using one or more graphical user interfaces (displaying the original request beside the (Lee Fig 4-5, ¶[0012-14], ¶[0037], ¶[0072-73]). However, Lee does not explicitly state processing logistics requests with extraction including extraction from email / email address; using bots to mimic human interaction with a computer and perform keystroke input / point / click functions; publishing a list of one or more requests extracted from the body of a predefined email address; automatically recording using the processor a plurality of quotes to have historical records; real-time activation of one or more rate sources dynamically selected based on user defined parameters.
Next, the prior art of Monakova (US 2022/0083330 A1) details using RPA bots to generate electronic documentation, and the bots are configured to mimic human interactions with a computer including on-screen clicks (Monakova ¶[0011-12]). However, Monakova does not explicitly state processing logistics requests with extraction and quoting; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; publishing a list of one or more requests extracted from the body of a predefined email address; automatically recording using the processor a plurality of quotes to have historical records; real-time activation of one or more rate sources dynamically selected based on user defined parameters.
Next, the prior art of Lutnick (US 2008/0161945 A1) details responding to requests by a user; filtering reports data stored in the system associated with an email address, and reports involve potential delivery service and product delivery (Lutnick ¶[0536-538], claim 19). However, Lutnick does not explicitly state processing logistics requests with extraction including extraction and quoting; using bots to mimic human interaction with a computer and perform keystroke input / point / click functions; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; automatically recording using the processor a plurality of quotes to have historical records; real-time activation of one or more rate sources dynamically selected based on user defined parameters.
Next, the prior art of Morimoto (US 2002/0169710 A1) automatically recording, using the processor, a plurality of quotes to have historical records when storing shipping quotes (Morimoto ¶[0047], ¶[0010], claim 16). However, Morimoto does not explicitly state processing logistics requests with extraction; using bots to mimic human interaction with a computer and perform keystroke input / point / click functions; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; publishing a list of one or more requests extracted from the body of a predefined email address; real-time activation of one or more rate sources dynamically selected based on user defined parameters.
Next, the prior art of Cahill et al. (US 2012/0036158 A1) details a travel booking method and system that receives inputs from a user, provides access to one or more sources of data by applying a business logic layer in a predetermined manner based on the rules, preferences, and search criteria with simultaneous search to the applicable sources of data to identify potentially suitable travel products, and presenting the travel products on the interface; searching and providing prices and quotes for air flight reservations (Cahill Abstract, ¶[0014], ¶[0042], ¶[0058]). However, Cahill does not explicitly state: processing logistics requests with extraction; using bots to mimic human interaction with a computer and perform keystroke input / point / click functions; comparing and validating extracted information using a graphical interface, providing extracted information to a graphical user interface; publishing a list of one or more requests extracted from the body of a predefined email address; and automatically recording using the processor a plurality of quotes to have historical records.
Next, the prior art of Lukis et al. (US 7,840,443 B2) details an automated quoting system that involves changing menu-driven parameters that impact cost to achieve the desired quotation that the operator desires (Lukis col 25 ln 6-15).
Next, the prior art of Benchaya (WO 2019/145960) details a transportation system that will provide a more competitive offer with opportunities according to total profit with more than one delivery, and reject delivery requests which are less profitable (Benchaya pg. 5 ¶ beginning “The present invention discloses a method for selecting…”).
Next, the prior art of Lam (US 2023/0143975 A1) details a dynamic pricing system that adjusts and adapts billable rates for service scenarios such as after-hours services based on rules and changes to routine services (Lam ¶[0003], ¶[0027]).
Net, the prior art of James (US 2014/0067490 A1) details a dynamic fare system that identifies a priced transportation option based on zone travel and distance, including transportation across multiple zones where the fare calculations are made according to the distance traveled within the relevant zones / jurisdictions, and zones are pre-defined (James Fig 5F-5G, ¶[0121], ¶[0140], ¶[0147], ¶[0154]).
The collective references of He, Lee, Monakova, Lutnick, Morimoto, Lukis, Cahill, Benchaya, Lam, and James teach the features of claim 11 individually, however it would not have been obvious to one or ordinary skill in the art before the effective filing data of the claimed invention to combine each of these teachings together to reproduce the invention of claim 11. Thus, the art on record fails to collectively teach “a computing device having at least one processor configured to automatically identify a logistics request from a logistics request receiver with no human interaction, wherein the logistics request receiver is selected from a group consisting of an email, a website, or one or more electronic documents using an artificial intelligence to extract and process information, wherein the logistics request receiver is configured to access the logistics request at the user level without using application programing interface (API) connections, wherein one or more bots are configured to mimic human interaction with a computer and to perform one or more of a keystroke input, a point, and a click on the screen, wherein in response to automatically identifying, the at least one processor is configured to extract the information from the logistics request with no human interaction, wherein the at least one processor is configured to compare and validate the extracted information using one or more graphical user interfaces (GUIs) with no human interaction, wherein the one or more GUIs include a text analysis function configured to read raw text from the logistics request and to understand where data was extracted incorrectly, wherein the text analysis function is configured to automatically associate raw text read from the logistics request with one or more data categories including at least one of a pick up location, a delivery location, a commodity, a weight, or physical dimensions, wherein the at least one processor is configured to provide the extracted information to a graphical user interface (GUI), wherein the GUI includes an automated quoting validator function configured to automatically generate at least one quote based upon, at least in part, natural language processing with no human interaction, wherein the automated quoting validator function is further configured to publish a list of one or more requests extracted from the body of a predefined email address, wherein the at least one processor is configured to automatically generate the at least one quote for the logistics request at the automated quoting validator function based upon, at least in part, one or more user defined parameters with no human interaction, wherein the one or more user defined parameters are presented in at least one graphical display as one or more selectable options in a plurality of dropdown menus, wherein each dropdown menu is affiliated with an industry specific cost driver, wherein at least one of the one or more user defined parameters is configured to define a percentage margin outside of which quotes are discarded, wherein at least one of the one or more user defined parameters is configured to define an afterhours window and to charge an additional fee for shipments that are required to be picked up during this predefined period of time, wherein at least one of the one or more user defined parameters is configured to define a minimum rate and profit based on different distance tiers, wherein the at least one processor is configured to automatically record a plurality of quotes to have historical records with no human interaction, wherein the at least one processor is configured to enable real-time activation of one or more rate sources based on the one or more user defined parameters, wherein the activated rate sources are dynamically selected for use by the automated quoting validator function to generate the at least one quote, wherein in response to the logistics request the at least one processor is configured to process the at least one quote based off scored parameters including a quoting algorithm and a plurality of quoting logic parameters with no human interaction, and wherein once the information is extracted and validated, the at least one processor is configured to access one or more rate engines with no human interaction to: obtain a plurality of rate related information for each logistics request, process at least one rate request, calculate a final rate, and publish the final rate in the at least one graphical user interface, wherein the one or more rate engines do not require input from a shipper or a carrier” as substantially required by independent claim 11.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to BRIAN TALLMAN whose telephone number is (571)272-3198. The examiner can normally be reached Monday-Friday 9-5.
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, Jeffrey Zimmerman can be reached at (571) 272-4602. 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.
BRIAN TALLMAN
Examiner
Art Unit 3628
/BRIAN A TALLMAN/Examiner, Art Unit 3628
/MICHAEL P HARRINGTON/Primary Examiner, Art Unit 3628
Prosecution Insights