# US 10,122,813 B2 · Proxied push notification based on user interaction > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,122,813 B2 - Document ID: US10122813B2 - Status: Granted - Kind: B2 - Application number: 15/707,926 - Filed: 2017-09-18 - Published: 2018-03-08 - Granted: 2018-11-06 - Earliest claimed: 2014-01-02 - Assignees: Paypal, Inc. - Applicants: PayPal, Inc. - Inventors: Max Edward Metral - Web page: https://patentgrep.com/patent/US10122813B2 ## CPC - H04L 67/55: Push-based network services - G06Q 30/0261: {based on user location} - G06Q 30/04: Billing or invoicing - H04L 67/025: for remote control or remote monitoring of applications - H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability - H04L 67/52: specially adapted for the location of the user terminal - H04W 4/02: Services making use of location information - H04W 4/12: Messaging; Mailboxes; Announcements - G06Q 30/0267: {Wireless devices} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Systems and methods are provided that allow a proprietor of a location or merchant to which a user is interacting through a third party to send a push notification to a user device associated with the user using the third party as a proxy. The provided systems and methods may assign an interaction identifier to the user and interaction when an interaction request is received by the third party that may be later used to identify the user and user device to which a notification received from the proprietor or merchant will be pushed. The user may be able to define rules and settings that limit the scope and timing of the push notifications that can be received, and the third party may determine if notifications received from the proprietor or merchant meet these rules and settings before pushing the notifications to the user device and user. ## Claims ### Claim 1 A system comprising: a non-transitory memory; and one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising: receiving an interaction request from a first client device through a network, wherein the interaction request identifies a second client device; assigning an identifier to the interaction request, wherein the identifier is configured to identify the first client device to the system, and wherein the identifier does not include information that identifies the first client device to the second client device; providing the identifier to the second client device through the network; receiving, from the second client device through the network, a communication that includes the identifier; identifying the first client device as a recipient of the communication based on the identifier; and providing the communication to the first client device through the network in response to identifying the first client device as the recipient. ### Claim 2 (depends on 1) The system of claim 1, wherein the operations further comprise: identifying the second client device as a target of the interaction request; wherein the providing the identifier to the second client device comprises providing the interaction request to the second client device; wherein the communication is received from the second client device in response to the interaction request; and wherein in response to the providing the communication to the first client device, the first client device is configured to invoke one or more applications of the first client device that include a payment application, a browser application, or a security application. ### Claim 3 (depends on 1) The system of claim 1, wherein the operations further comprise: beginning, in response to receiving the interaction request, an interaction session associated with the identifier; and determining, in response to identifying the first client device as the recipient of the communication based on the identifier, that the interaction session has not expired, and in response, providing the communication to the first client device. ### Claim 4 (depends on 1) The system of claim 1, wherein the operations further comprise: applying at least one rule to the communication, wherein the communication is provided to the first client device in response to the at least one rule allowing the communication to be provided to the first client device. ### Claim 5 (depends on 4) The system of claim 4, wherein the operations further comprise: receiving, from the first client device through the network prior to receiving the interaction request, the at least one rule that includes one of 1) a type of the communication that is allowed to be provided to the first client device, or 2) a time period that the communication is allowed to be provided to the first client device. ### Claim 6 (depends on 4) The system of claim 4, wherein the operations further comprise: retrieving from a memory, prior to receiving the interaction request, the at least one rule that includes at least one system-defined rule that defines one of 1) a type of the communication that is allowed to be provided to client devices, or 2) a content of the communication that is allowed to be provided to the client devices. ### Claim 7 (depends on 1) The system of claim 1, wherein the operations further comprise: determining a type of the interaction request, wherein the type of the interaction request includes at least one of a transaction interaction request or a check-in interaction request; and providing, to the second client device through the network, the type of the interaction request along with the identifier. ### Claim 8 A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising: receiving an interaction request from a first client device through a network, wherein the interaction request identifies a second client device; assigning an identifier to the interaction request, wherein the identifier is configured to identify the first client device to the machine, and wherein the identifier does not include information that identifies the first client device to the second client device; providing the identifier to the second client device through the network; receiving, from the second client device through the network, a communication that includes the identifier; identifying the first client device as a recipient of the communication based on the identifier; and providing the communication to the first client device through the network in response to identifying the first client device as the recipient. ### Claim 9 (depends on 8) The non-transitory machine-readable medium of claim 8, wherein the operations further comprise: identifying the second client device as a target of the interaction request; wherein the providing the identifier to the second client device comprises providing the interaction request to the second client device; wherein the communication is received from the second client device in response to the interaction request; and wherein in response to the providing the communication to the first client device, the first client device is configured to invoke one or more applications of the first client device that include a payment application, a browser application, or a security application. ### Claim 10 (depends on 8) The non-transitory machine-readable medium of claim 8, wherein the operations further comprise: beginning, in response to receiving the interaction request, an interaction session associated with the identifier; and determining, in response to identifying the first client device as the recipient of the communication based on the identifier, that the interaction session has not expired, and in response, providing the communication to the first client device. ### Claim 11 (depends on 8) The non-transitory machine-readable medium of claim 8, wherein the operations further comprise: applying at least one rule to the communication, wherein the communication is provided to the first client device in response to the at least one rule allowing the communication to be provided to the first client device. ### Claim 12 (depends on 11) The non-transitory machine-readable medium of claim 11, wherein the operations further comprise: receiving, from the first client device through the network prior to receiving the interaction request, the at least one rule that includes one of 1) a type of the communication that is allowed to be provided to the first client device, or 2) a time period that the communication is allowed to be provided to the first client device. ### Claim 13 (depends on 11) The non-transitory machine-readable medium of claim 11, wherein the operations further comprise: retrieving from a memory, prior to receiving the interaction request, the at least one rule that includes at least one system-defined rule that defines one of 1) a type of the communication that is allowed to be provided to client devices, or 2) a content of the communication that is allowed to be provided to the client devices. ### Claim 14 (depends on 8) The non-transitory machine-readable medium of claim 8, wherein the operations further comprise: determining a type of the interaction request, wherein the type of the interaction request includes at least one of a transaction interaction request or a check-in interaction request; and providing, to the second client device through the network, the type of the interaction request along with the identifier. ### Claim 15 A proxied communication method, comprising: receiving, by a proxy server system, an interaction request from a first client device through a network, wherein the interaction request identifies a second client device; assigning, by the proxy server system, an identifier to the interaction request, wherein the identifier is configured to identify the first client device to the proxy server system, and wherein the identifier does not include information that identifies the first client device to the second client device; providing, by the proxy server system and through the network, the identifier to the second client device; receiving, by the proxy server system from the second client device through the network, a communication that includes the identifier; identifying, by the proxy server system, the first client device as a recipient of the communication based on the identifier; and providing, by the proxy server system, the communication to the first client device through the network in response to identifying the first client device as the recipient. ### Claim 16 (depends on 15) The method of claim 15, further comprising: beginning, by the proxy server system in response to receiving the interaction request, an interaction session associated with the identifier; and determining, by the proxy server system in response to identifying the first client device as the recipient of the communication based on the identifier, that the interaction session has not expired, and in response, providing the communication to the first client device. ### Claim 17 (depends on 15) The method of claim 15, further comprising: applying, by the proxy server system, at least one rule to the communication, wherein the communication is provided to the first client device in response to the at least one rule allowing the communication to be provided to the first client device. ### Claim 18 (depends on 17) The method of claim 17, further comprising: receiving, by the proxy server system from the first client device through the network prior to receiving the interaction request, the at least one rule that includes one of 1) a type of the communication that is allowed to be provided to the first client device, or 2) a time period that the communication is allowed to be provided to the first client device. ### Claim 19 (depends on 17) The method of claim 17, further comprising: retrieving from a memory, by the proxy server system prior to receiving the interaction request, the at least one rule that includes at least one system-defined rule that defines one of 1) a type of the communication that is allowed to be provided to client devices, or 2) a content of the communication that is allowed to be provided to the client devices. ### Claim 20 (depends on 15) The method of claim 15, further comprising: determining, by the proxy server system, a type of the interaction request, wherein the type of the interaction request includes at least one of a transaction interaction request or a check-in interaction request; and providing, by the proxy server system to the second client device through the network, the type of the interaction request along with the identifier.