DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Status of Claims
This office action on the merits in response to the application filed on 10/10/2025.
Claims 21-40 are currently pending and have been examined.
Response to Arguments
Applicant's arguments filed 10/10/2025 with respect to the rejection of claim(s) 21-40 have been fully considered and are persuasive. Therefore, the rejection has been withdrawn. However, upon further consideration, a new ground(s) of rejection is made.
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 21-40 are rejected under 35 U.S.C. 101 because the claimed invention is directed to a judicial exception (i.e., a law of nature, a natural phenomenon, or an abstract idea) without significantly more.
Subject Matter Eligibility Criteria – Step 1:
Claims 21-27 are directed to a method, claims 28-34 are directed to an article of manufacture, and claims 35-40 is directed to an system. Therefore, these claims fall within the four statutory categories of invention.
Subject Matter Eligibility Criteria – Step 2A – Prong One:
Regarding Prong One of Step 2A of the Alice/Mayo test, the claim limitations are to be analyzed to determine whether, under their broadest reasonable interpretation, they “recite” a judicial exception or in other words whether a judicial exception is “set forth” or “described” in the claims. MPEP 2106.04(II)(A)(1). An “abstract idea” judicial exception is subject matter that falls within at least one of the following groups: a) certain methods of organizing human activity, b) mental processes, and/or c) mathematical concepts. MPEP 2106.04(a).
Representative independents claims 21, 28, and 35 include limitations that recite at least one abstract idea.
Claims 21, 28, and 35 are directed to the abstract idea of “receiving, by a processor, a new incoming message event from an electronic message repository; retrieving, by the processor, an incoming message from the electronic message repository, the incoming message relating to a previously-received transaction request associated with a point of sale (POS) terminal and a personal identification number (PIN) pad; determining, by the processor, whether a message type of the retrieved incoming message matches a current step in a transaction request process flow of the previously- received transaction request associated with the POS terminal and the PIN pad; upon determining that the message type of the retrieved incoming message does not match the current step in the transaction request process flow of the previously- received transaction request associated with the POS terminal and the PIN pad, retaining, by the processor, the retrieved incoming message in the electronic message repository until the current step in the transaction request process flow matches the message type of the previously-received transaction request; transmitting, by the processor, the previously-received transaction request to the PIN pad for processing based on the current step in the transaction request process flow of the previously-received transaction request matching the message type of the retrieved incoming message; and purging, by the processor, the electronic message repository of remaining messages based on the transaction request being completed.” Under its broadest reasonable interpretation, this claim is managing a transaction approval workflow based on message types, and hence falls under organizing human activity (i.e., as fundamental economic practices).
Dependent Claims:
Claims 22, 29, and 36 recites: sending, by the processor, the received transaction request message to the PIN pad by way of the electronic message repository; and sending, by the processor, a subscription request to the electronic message repository for messages generated by the PIN pad; further describes the abstract idea of organizing human activity (i.e., as fundamental economic practices).
Claims 23, 30, and 37 recites: receiving, by the processor, a transaction status message from the cloud-based application; and updating, by the processor, the current step in the transaction request process flow of the received transaction request according to the received transaction status message; further describes the abstract idea of organizing human activity (i.e., as fundamental economic practices).
Claims 24, 31, and 38 recites: receiving, by the processor, a transaction complete message from the PIN pad; and sending, by the processor, a mailbox flush notification to the electronic message repository; further describes the abstract idea of organizing human activity (i.e., as fundamental economic practices).
Claims 25, 32, and 39 recites: wherein the cloud-based application is a POS application; further describes the abstract idea of organizing human activity (i.e., as fundamental economic practices).
Claims 26, 33, and 40 recites: wherein the current step in the transaction request process flow of the received transaction request is associated with one or more message types of messages sent to or from the PIN pad; further describes the abstract idea of organizing human activity (i.e., as fundamental economic practices).
Claims 27 and 34, recites: receiving, by the processor, a notification from the electronic message repository of past unretrieved messages stored in the electronic message repository; further describes the abstract idea of organizing human activity (i.e., as fundamental economic practices).
Subject Matter Eligibility Criteria – Step 2A – Prong Two:
Claim 21, 28, and 35 recites to a generic computer as additional elements to the judicial exception in the preamble. Viewed individually and in combination, this additional element to the identified judicial exception of Step 2A.1, amounts to no more than mere instructions for managing a transaction approval workflow based on message types on a generic computer. Therefore, at Step 2A.2, these additional elements do not act in combination to integrate the abstract idea into a practical application. The additional elements of claims 21, 28, and 35 considered both individually and as an ordered combination, do not amount to significantly more than the judicial exception because the additional element of a generic computer does no more than “[s]imply appending well-understood, routine, conventional activities previously known to the industry, specified at a high level of generality, to the judicial exception, e.g., a claim to an abstract idea requiring no more than a generic computer to perform generic computer functions that are well-understood, routine and conventional activities previously known to the industry.” See MPEP 2106.05 (citing to Alice Corp. Pty. Ltd. v. CLS Bank Int'l, 573 U.S. 208, 225 (2014)).
Therefore claims 21, 28, and 35 is found ineligible under 35 U.S.C. 101.
Step 2B:
Viewed as a whole, instructions/method claims recite the concept of “organizing human activity” (i.e., as fundamental economic practices) in managing a transaction approval workflow based on message types are performed by a generic computer. The method claims do not, for example, purport to improve the functioning of the computer itself. Nor do they effect an improvement in any other technology or technical field. Instead, the claims at issue amount to nothing significantly more than an instruction to apply the abstract idea using some unspecified, generic computer. See Alice Corp. Pty. Ltd., 573 U.S. 208. Mere instructions to apply the exception using a generic computer component and limitations to a particular field of use or technological environment cannot integrate a judicial exception into a practical application at Step 2A or provide an inventive concept in Step 2B. The use of a computer server is to merely automate and/or implement the abstract idea cannot provide significantly more than the abstract idea itself (MPEP 2106.05(I)(A)(f) & (h)). Therefore, the claim is not patent eligible.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
5. Claim 21, 23, 25-28, 30, 32-35, 37, and 39-40, are rejected under 35 U.S.C. 103 as being unpatentable over Nukala et al. (US 20170126591 A1), and in view of Davis et al. (US 10783513 B2), in view of Banks et al. (US 20230410109 A1), and further in view of Zhang et al. (US 20040205770 A1).
6. Regarding claims 21, 28, and 35, Nukala discloses a computer-implemented method (a non-transitory machine-readable medium storing instructions and a system, (Para. 0038)) for cloud-based asynchronous communication, the method comprising:
receiving, by a processor, a new incoming message event from an electronic message repository, (Para. 0030, With reference now to the figures, and beginning with FIG. 1, there is depicted a block diagram representation of an example data processing system (DPS) 100, within which one or more of the described features of the various embodiments of the disclosure can be implemented. Data processing system 100 includes at least one central processing unit (CPU) or processor 104 coupled to system memory 110 via system interconnect 102; and Para. 0032, In one embodiment DPS 100 may be a server or cloud device that executes AARU 117 for performing the various method and functions described herein. In an alternate embodiment DPS 100 can be a personal device such as a desktop computer, notebook computer, mobile phone, tablet, or any other electronic device that supports local messaging functionality; Abstract, The method includes receiving an incoming message in an inbox of a respondent that has an autoreply message activated and identifying, from content of at least one of the incoming message and the autoreply message; and Para. 0027, As utilized herein, an inbox refers to an incoming message repository associated with a messaging account that is assigned to a person or party for a messaging service. The messaging service may be, for example, but not limited to, an email service, short-messaging service, instant messaging service, or any suitable combination of the foregoing. The person or party assigned to the account receiving the incoming message is referred to as the respondent, and the person or party that generated the incoming message is referred to as the sender.)
Nukala does not explicitly disclose retrieving, by the processor, an incoming message from the electronic message repository, the incoming message, relating to a previously-received transaction request associated with a point of sale (POS) terminal and a personal identification number (PIN) pad.
However, Davis teaches retrieving, by the processor, an incoming message from the electronic message repository, the incoming message, relating to a previously-received transaction request associated with a point of sale (POS) terminal and a personal identification number (PIN) pad, (Column 16/line 8, the client device 104a can include a data manager 218, as illustrated in FIG. 2. The data manager 218 can maintain message data representative of data used in connection with composing, sending, and receiving messages between a user and one or more other users. For example, message data can include message logs, contact lists, content, past communications, and other similar types of data that the communication application 202 can use in connection with providing the ability for users to communicate using the communication application 202.; and Column 17/line 31, The message database 234 may maintain status data representative of the information mentioned above that the status manager 232 tracks. The message database 234 can thus provide an archive of messaging threads, which the network application 204 can provide to a user on demand or once a user logs into the client application 202 using a new computing device. The payment manager 236 of FIG. 2 can integrate the sending and receiving of payment messages and initiate payment transactions, and may employ one or more application programming interfaces (APIs). For example, upon the communication manager 230 can receiving a payment message, the communication manager 230 can send any payment details to the payment manager 236. The payment manager 236 can then user the payment details retrieved from the payment message to initiate a payment transaction using the payment network 115.; and Column 62/line 55, the processor 1802 may retrieve (or fetch) the instructions from an internal register, an internal cache, the memory 1804, or the storage device 1806 and decode and execute them.)
One of ordinary skill in the art would have recognized that applying the known technique of Davis to the known invention of Nukala would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include retrieving, by the processor, an incoming message from the electronic message repository, the incoming message, relating to a previously-received transaction request associated with a point of sale (POS) terminal and a personal identification number (PIN) pad results in an improved invention because applying said technique ensures that the transaction request flow is remaining updated with the messages only pertaining to transactions, improving the overall performance of the invention.
Nukala does not explicitly disclose determining, by the processor, whether a message type of the retrieved incoming message matches a current step in a transaction request process flow of the previously-received transaction request associated with the POS terminal and the PIN pad,
However, Davis teaches determining, by the processor, whether a message type of the retrieved incoming message matches a current step in a transaction request process flow of the previously-received transaction request associated with the POS terminal and the PIN pad, (Column 14/line 53, the client application 202 can further include a message analyzer 212. The message analyzer 212 can analyze messages sent from and received by the client application 202 for potential payment events. In one or more embodiments, the message analyzer 212 can infer the payment events from the electronic messages exchanged between users based on contextual content in the exchanged messages. Specifically, the message analyzer 212 can identify certain phrases or character strings that indicate an opportunity for a payment. For example, the character strings can include predetermined character strings from electronic messages in a conversation between two or more users.; and Column 52/line 7, The method 1100 includes an act 1104 of inferring a payment event. In particular, act involves inferring a payment event based on the analysis of the one or more electronic messages exchanged between the user and the one or more co-users… the method 1100 can include identifying a predetermined character string in the one or more electronic messages, and performing an operation associated with the payment transaction based on the predetermined character string.).
One of ordinary skill in the art would have recognized that applying the known technique of Davis to the known invention of Nukala would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include determining, by the processor, whether a message type of the retrieved incoming message matches a current step in a transaction request process flow of the previously-received transaction request associated with the POS terminal and the PIN pad results in an improved invention because applying said technique ensures that the transaction request flow is remaining updated with the messages only pertaining to transactions, improving the overall performance of the invention.
Nukala does not explicitly disclose upon determining that the message type of the retrieved incoming message does not match the current step in the transaction request process flow of the previously- received transaction request associated with the POS terminal and the PIN pad.
However, Davis teaches upon determining that the message type of the retrieved incoming message does not match the current step in the transaction request process flow of the previously- received transaction request associated with the POS terminal and the PIN pad, (Column 23/line 5, In the event that the network application 204 does not validate the sender or the payment credential, the network application 204 can send a communication to the sender client device 104a to cause the client application 202 to present an error message to the sender that indicates the payment could not be authorized. In one or more embodiments, the error message can include a prompt for the sender to provide additional authorization information, agree to terms and conditions, or otherwise verify their identify. After which the sender client device 104a can send a revised payment request to the network application 204. The network application 204 can then attempt to validate the sender/payment credential. If the network application 204 cannot validate the sender/payment credential, then the network application 204 may terminate the payment transaction based on the payment message 302.).
One of ordinary skill in the art would have recognized that applying the known technique of Davis to the known invention of Nukala would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include determining that the message type of the retrieved incoming message does not match the current step in the transaction request process flow of the previously- received transaction request associated with the POS terminal and the PIN pad, results in an improved invention because applying said technique ensures that the transaction request flow is remaining updated with the messages only pertaining to transactions and able to determine if there is an error in the process flow, improving the overall performance of the invention.
Nukala does not explicitly disclose retaining, by the processor, the retrieved incoming message in the electronic message repository. until the current step in the transaction request process flow matches the message type of the previously-received transaction request.
However, Davis teaches retaining, by the processor, the retrieved incoming message in the electronic message repository. until the current step in the transaction request process flow matches the message type of the previously-received transaction request. (Column 17/line 27, The network application 204 may also include a message database 234. The message database 234 can maintain message data representative of content of messages from electronic messaging sessions among a plurality of participants. The message database 234 may maintain status data representative of the information mentioned above that the status manager 232 tracks. The message database 234 can thus provide an archive of messaging threads, which the network application 204 can provide to a user on demand or once a user logs into the client application 202 using a new computing device.; and Column 17/line 38, The payment manager 236 of FIG. 2 can integrate the sending and receiving of payment messages and initiate payment transactions, and may employ one or more application programming interfaces (APIs). For example, upon the communication manager 230 can receiving a payment message, the communication manager 230 can send any payment details to the payment manager 236.; and Column 13/line 22, For example, the message handler 210 can interact with the user interface manager 206 and the user input detector 208 to coordinate the sending and receiving of messages using the communication application 202. The message handler 210 may direct the sending and receiving of messages to and from the network application 204 over the course of an electronic messaging session among a plurality of participants. The message handler 210 may organize incoming and outgoing messages and direct the user interface manager 206 to display messages.) Examiner interprets the term retaining is analogous for the terms archive and storing in the cited prior art.
One of ordinary skill in the art would have recognized that applying the known technique of Davis to the known invention of Nukala would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such message repository features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include retaining, by the processor, the retrieved incoming message in the electronic message repository. until the current step in the transaction request process flow matches the message type of the previously-received transaction request ensures that users can access and retrieve messages from the electric message repository at any time, thus improving the overall user accessibility of the invention.
Nukala does not explicitly disclose transmitting, by the processor, the previously-received transaction request to the PIN pad for processing based on the current step in the transaction request process flow of the previously-received transaction request matching the message type of the retrieved incoming message.
However, Banks teaches transmitting, by the processor, the previously-received transaction request to the PIN pad for processing based on the current step in the transaction request process flow of the previously-received transaction request matching the message type of the retrieved incoming message, (Para. 0024, As shown in FIG. 1, an infrastructure 100 for processing electronic payment requests may include one or more point of sale (POS) devices 102, which may be in communication with a POS engine 106, and one or more personal identification number (PIN) pad terminals 128, which may be in communication with a socket gateway 124. POS devices 102 may communicate a sale request message over computer network 104 to POS engine 106. POS engine 106 may be embodied, for example, as middleware that may transmit commands to control a PIN pad 128, such as by sending a payment request to PIN pad transaction generator 110 over computer network 118. PIN pad transaction generator 110 may generate one or more PIN pad commands 114 for processing by a transaction generator 112. Transaction generator 112 may take in a transaction request from the POS engine 106 and PIN pad specific commands 114 for the transaction. Transaction generator 112 may further take in expected responses from PIN pad 128. Transaction generator 112 may manage the entire transaction using, for example, a state machine for the specific transaction.; and Para. 0028] Turning to FIG. 2, PIN pad transaction generator 110 may receive a transaction request 210 from, for example, a backend service or application, or from a client device such as point of sale device 102. Transaction generator 110 may then determine whether a transaction generator actor 112 is available to service the transaction request. If no transaction generator actor 112 is available to service the transaction request, then PIN pad transaction generator 110 may create a new transaction generator actor 112. Transaction generator actor 112 may then create a transaction command generator 114 to generate commands to be transmitted to a PIN pad for the transaction request. Alternatively, transaction generator actor 112 may select an available transaction command generator 114 from a pool of idle transaction command generators 114. Transaction command generator 114 may generate PIN pad commands to be transmitted to a client device, such as PIN pad 128, according to the contents of transaction request 210 including, for example, the transaction type and expected responses from the client device. A new transaction request including the generated PIN pad commands may be transmitted to PIN pad 128 as transaction request 230. A transaction response 240 may be received from PIN pad 128 and further processed by PIN pad transaction generator 110 before being transmitted to POS device 102 as transaction response 220.
One of ordinary skill in the art would have recognized that applying the known technique of Nukala as modified to the known invention of Banks would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate message repository features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include transmitting, by the processor, the previously-received transaction request to the PIN pad for processing based on the current step in the transaction request process flow of the previously-received transaction request matching the message type of the retrieved incoming message results in an improved invention because applying said technique ensures that each step in the transaction process matches each pin pad command, thus improving the overall performance of the invention.
Nukala as modified does not explicitly disclose purging, by the processor, the electronic message repository of remaining messages based on the transaction request being completed.
However, Zhang teaches purging, by the processor, the electronic message repository of remaining messages based on the transaction request being completed, (Para. 0027-0028, In Step 3a, as shown in block 403, the MTA 306 will access the Monitor Queue 310 to retrieve the unique message id from the last successfully delivered message. It will then compare that message id with the message id of the message 108 it retrieved from the Message Store 102. If the message ids are identical, as determined in block 404, this means that this current message is a duplicate and should not be delivered to the Destination Queue 110. Accordingly, the MTA 306 will skip Steps 3b, 3c, and 3d, thus causing the transaction to roll back in block 420 and go right to Step 4 in block 430 and send an acknowledgement to the Message Store 102 that this message has already been successfully delivered. This action will cause the Message Store 102 to remove the message 108 from its queue or otherwise tag the message so that it is not served again. If, however, the message ids do not match in Step 3a, then the MTA 306 will go on to Step 3b, shown in block 405, and send the message id of this message 108 to the Monitor Queue 310. Processing will continue to Step 3c., and Para. 0031, Step 4, shown as block 430, remains the same as in FIG. 2. The MTA 306 sends an acknowledgement (ACK) to the Message Store 102 confirming the successful delivery of the message 108. The Message Store 102, upon receipt of this ACK, will remove the message 108 from its queue. This will prevent the message 108 from being resent.)
One of ordinary skill in the art would have recognized that applying the known technique of Nukala as modified to the known invention of Zhang would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate purging features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include purging, by the processor, the electronic message repository of remaining messages based on the transaction request being completed results in an improved invention because applying said technique ensures that messages are removed after the transaction is completed to prevent duplicate transactions, thus improving the overall performance of the invention.
7. Regarding claims 23, 30, and 37, Nukala does not explicitly disclose the method further comprising: receiving, by the processor, a transaction status message from the cloud-based application; and u)dating, by the processor, the current step in the transaction request process flow of the received transaction request according to the received transaction status message.
However, Davis teaches the method further comprising: receiving, by the processor, a transaction status message from the cloud-based application; and u)dating, by the processor, the current step in the transaction request process flow of the received transaction request according to the received transaction status message, (Column 17/line 8, The status manager 232 can track the status of users of the client applications 202 and/or the client devices 104a, 104b. For example the status manager 232 can identify when a user is logged into the client application 202, when a user is active on the client application 202, when a client device 104a, 104b associated with a user or user account is online or active. The status manager 232 can send indications (such as push notifications) to the client application 202 to notify the client application 202 of the status of users, device, messages, or payments. The user interface manager 206 can add, modify, or otherwise change or update status notifications based on indications received from the status manager 232. For example, the status manager 232 can send an indication to the client application 202 indicating that another user has accessed a message, received a payment, sent a payment, is active, a device or device type a co-user is active on (e.g., mobile vs. web), etc. The user interface manager 206 in turn an update a user interface to notify a user of the status.; and Column 17/line 27, The network application 204 may also include a message database 234. The message database 234 can maintain message data representative of content of messages from electronic messaging sessions among a plurality of participants. The message database 234 may maintain status data representative of the information mentioned above that the status manager 232 tracks. The message database 234 can thus provide an archive of messaging threads, which the network application 204 can provide to a user on demand or once a user logs into the client application 202 using a new computing device.)
One of ordinary skill in the art would have recognized that applying the known technique of Davis to the known invention of Nukala would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying method to include receiving, by the processor, a transaction status message from the cloud-based application; and updating, by the processor, the current step in the transaction request process flow of the received transaction request according to the received transaction status message results in an improved invention because applying said technique ensures that the transaction request flow is remaining updated with the messages only pertaining to transactions, improving the overall efficiency of the invention.
8. Regarding claims 25, 32, and 39, Nukala does not explicitly disclose wherein the cloud- based application is a (POS) application.
However, Davis teaches wherein the cloud- based application is a (POS) application, (Column 62/line 11, Embodiments of the present disclosure can also be implemented in cloud computing environments. In this description, “cloud computing” is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources. For example, cloud computing can be employed in the marketplace to offer ubiquitous and convenient on-demand access to the shared pool of configurable computing resources. The shared pool of configurable computing resources can be rapidly provisioned via virtualization and released with low management effort or service provider interaction, and then scaled accordingly… In this description and in the claims, a “cloud-computing environment” is an environment in which cloud computing is employed.)
One of ordinary skill in the art would have recognized that applying the known technique of Davis to the known invention of Nukala would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale system features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include the cloud-based application being a (POS) application results in an improved invention because applying said technique ensures that the consumer may enter payment and/or personal information in order to complete payment processing requests for purchases thus, improving the overall efficiency of the invention.
9. Regarding claims 26, 33, and 40, Nukala does not explicitly disclose wherein the current step in the transaction request process flow of the received transaction request is associated with one or more message types of messages sent to or from the PIN pad.
However, Davis teaches wherein the current step in the transaction request process flow of the received transaction request is associated with one or more message types of messages sent to or from the PIN pad, (Column 17/line 8, The status manager 232 can track the status of users of the client applications 202 and/or the client devices 104a, 104b. For example the status manager 232 can identify when a user is logged into the client application 202, when a user is active on the client application 202, when a client device 104a, 104b associated with a user or user account is online or active. The status manager 232 can send indications (such as push notifications) to the client application 202 to notify the client application 202 of the status of users, device, messages, or payments. The user interface manager 206 can add, modify, or otherwise change or update status notifications based on indications received from the status manager 232. For example, the status manager 232 can send an indication to the client application 202 indicating that another user has accessed a message, received a payment, sent a payment, is active, a device or device type a co-user is active on (e.g., mobile vs. web), etc. The user interface manager 206 in turn an update a user interface to notify a user of the status.)
One of ordinary skill in the art would have recognized that applying the known technique of Davis to the known invention of Nukala would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include wherein the current step in the transaction request process flow of the received transaction request is associated with one or more message types of messages sent to or from the PIN pad in an improved invention because applying said technique ensures that the transaction request flow is remaining updated with the status of the transaction thus, improving the overall efficiency of the invention.
10. Regarding claim 27 and 34, Nukala does not explicitly disclose receiving, by the processor, a notification from the electronic repository of past unretrieved messages stored in the electronic repository.
However, Davis teaches receiving, by the processor, a notification from the electronic repository of past unretrieved messages stored in the electronic repository, (Column 48/line 55, Upon selecting the notification control 840, the user interface manager 206 can provide a notification interface 844. The notification interface 844 can display a plurality of notifications received for the user client device 400c. In one instance, the notification interface 844 presents the payment request notification 846 at the top of a list of notifications for the user, as shown in FIG. 8D. The payment request notification 846 can include a selectable element 848 or the entire payment request notification 846 can be a selectable element. The system can also provide an option to allow the sender to apply social pressure by reminding the recipient of the payment transaction. For example, by selecting a reminder option (similar to the reminder option 504 describe above) can cause the system 100 to send a message to the recipient to complete the payment transaction by entering the credentials for the payment transaction. In some instances, the message to the recipient can cause a message or notification to appear at the sender client device 104a and/or within the messaging interface 412 at the sender client device 104a.
One of ordinary skill in the art would have recognized that applying the known technique of Hayhow to the known invention of Nukala would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include receiving, by the processor, a notification from the electronic repository of past unretrieved messages stored in the electronic repository results in an improved invention because applying said technique ensures that the consumer may enter payment and/or personal information in order to complete payment processing requests for purchases thus, improving the overall efficiency of the invention.
11. Claims 22, 24, 29, 31, 36 and 38 are rejected under 35 U.S.C. 103 as being unpatentable over Nukala et al. (US 20170126591 A1), in view of Davis et al. (US 10783513 B2), in view of Banks et al. (US 20230410109 A1), in view of Zhang et al. (US 20040205770 A1), and further in view of in view of Hayhow et al. (US 20150242854 A1).
12. Regarding claims 22, 29, and 36, Nukala as modified discloses sending, by the processor, the received transaction request message to a PIN pad by way of the electronic message repository; and sending, by the processor, the subscription request to the electronic message repository for messages generated by the PIN pad, (0007-0008, In accordance with the first aspect of the disclosure, there is also provided a network gateway that includes a network interface, a transactions database, and a processor. The network interface is configured for communication with at least one pin-pad terminal and a merchant acquirer server. Each pin-pad terminal has a memory storing particulars of at least one authorized transaction authorized using said pin-pad terminal. The processor is coupled to the network interface and the transactions database and is configured to receive from the merchant acquirer server an authorization code for one of the authorized transactions, and to save in the database the particulars of the one authorized transaction. The processor is also configured to receive a request to close out all the saved transactions, and to receive from one of the pin-pad terminals an authorization request message requesting authorization for an additional transaction.).
Nukala as modified does not explicitly disclose a subscription request to the electronic message repository for messages generated by the PIN pad.
However, Hayhow teaches a subscription request to the electronic message repository for messages generated by the PIN pad, (Para. 0057, The network gateway then receives a request to close out all the saved transactions, and receives from one of the pin-pad terminals 300 an authorization request message requesting authorization for an additional transaction. In response, the network gateway (i) in the transactions database 414, closes all the saved transactions authorized using the one pin-pad terminal 300, an (ii) responds to the authorization request message by providing the one pin-pad terminal 300 with a remote synchronization command commanding the one pin-pad terminal 300 to clear the running total from the memory.
One of ordinary skill in the art would have recognized that applying the known technique of Hayhow to the known invention of Nukala as modified would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying processor in Nukala to include a subscription request to the electronic message repository for messages generated by the PIN pad results in an improved invention because applying said technique ensures that the user has access to the message repository, improving the overall user convenience of the invention.
13. Regarding claims 24, 31, and 38, Nukala as modified does not explicitly disclose receiving, by the processor, a transaction complete message from the PIN pad; and sending, by the processor, a mailbox flush notification to the electronic message repository.
However, Hayhow teaches receiving, by the processor, a transaction complete message from the PIN pad; and sending, by the processor, a mailbox flush notification to the electronic message repository, (Para. 0083, At step S608, the transaction tracking processor 416 responds to the pin-pad terminal 300 with a remote synchronization command that includes the tab number of each of the located "closed" tabs, and commanding the pin-pad terminal 300 to clear the running total amount for the current business day. In response, the pin-pad terminal 300 associates each specified tab in its memory with a "closed" status identifier, and clears the running total in the memory for the current business day.; Para. 0076-0077, Depending upon the functionality implemented by the payment card, the payment card processor may request that the payment card confirm that the issuer server 500 authorized the transaction. If the merchant authorization code indicates that the electronic payment was authorized (and optionally the payment card confirmed that the issuer server 500 authorized the transaction), the payment card processor saves in the memory of the pin-pad terminal 300 particulars (e.g. tab number, monetary amount paid, merchant authorization code) of the transaction, and adds the monetary amount paid to the running monetary total amount of all payment transactions authorized using the pin-pad terminal 300 in the current business day. The transaction processor then transmits to the electronic cash register 200, at step S512, a close tab command that includes the tab number and requests that the electronic cash register 200 mark the specified tab as "closed" in the pending transaction database 250). Examiner interprets the term mailbox flush notification is analogous for the term remote synchronization command commanding the one pin-pad terminal to clear in the cited prior art.
One of ordinary skill in the art would have recognized that applying the known technique of Hayhow to the known invention of Nukala as modified would have yielded predictable results and resulted in an improved invention. It would have been recognized that the application of the technique would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such point-of-sale features into a similar invention. Further, it would have been recognized by those of ordinary skill in the art that modifying the method to include receiving, by the processor, a transaction complete message from the PIN pad; and sending, by the processor, a mailbox flush notification to the electronic message repository results in an improved invention because applying said technique makes it easier for the user to enter transaction data via the pin pad thus, improving the overall user convenience of the invention.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Audio Broadcast System with Cloud Communications Platform and Related Methods (US 11146689 B1) teaches an audio broadcast system may include communications devices, a cloud communications platform in communication with the communications devices, and an event-driven serverless cloud computing platform in communication with the communications devices and the cloud communications platform. The event-driven serverless cloud computing platform may be configured to provision resources from the cloud communications platform to initiate telephone calls respectively for the communications devices, and simultaneously broadcast an audio stream to the communications devices respectively via the telephone calls.
In addition to the foregoing, other aspects are described in the claims, drawings, and text. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Davida L. King whose telephone number is (571) 272-4724. The examiner can normally be reached M-F 8am-5pm.
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, Neha Patel can be reached on (571) 270-1492. 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.
/D.L.K./Examiner, Art Unit 3699
/NEHA PATEL/Supervisory Patent Examiner, Art Unit 3699