Patent Grant
11935068
Some embodiments described herein relate generally to computer-related technologies for mobile electronic devices. In particular, some embodiments described herein relate to methods and apparatus for mobile device messaging-based communications using custom-generated deeplinks and based on the Hyper Text Transfer Protocol (HTTP).
Known methods allow a user to open a vendor's application or a vendor's website on a mobile device to select a product or service. The user can then provide payment information via the vendor's application or website to complete a transaction with the vendor. With these known methods, however, the user often pauses its previous activities (e.g., viewing a website, reading an email) on the mobile device and is redirected to the vendor's application or website to purchase the products and services via many user input (e.g., clicks, or screen taps). This time-consuming and burdensome process results in many users leaving the purchase before the transaction is completed.
Accordingly, a need exists for methods and apparatus for dynamic application deeplinking to transition from one user interface to another user interface at a mobile device for continued and improved user experience and engagement when interacting with the mobile device.
In some embodiments, a method includes, in response to an integration tag included in a webpage at a first user interface being executed at a mobile device, receiving, at a processor remote from the mobile device, (1) a mobile device identifier associated with the mobile device, and (2) a request to retrieve a purchase identifier associated with the integration tag and a set of configurable settings associated with the integration tag. The method includes in response to a loading status of the webpage including the integration tag satisfying a criteria, sending, from the processor to the mobile device and based on the mobile device identifier, a first signal causing a frame to be provided within the webpage at the first user interface of the mobile device and based on the set of configurable settings, the frame associated with the purchase identifier. The method includes in response to a first user input associated with the frame entered by a user via the mobile device, receiving, at the processor, a Hyper Text Transfer Protocol (HTTP) POST request from the mobile device. The method includes determining, at the processor and based on the HTTP POST request and the mobile device identifier, a uniform resource identifier (URI) defined to cause a second user interface at the mobile device to render at the mobile device. The URI of the second user interface is compatible with a first operating system and not a second operating system different from the first operating system. The mobile device is operable with the first operating system and not the second operating system. The second user interface is different from the first user interface. The method includes retrieving purchase information and sending a HTTP response message including the URI of the second user interface and the purchase information to deeplink to the second user interface and to cause the second user interface to be rendered at the mobile device with the purchase information pre-populated in an input field of a text message for the user to initiate a purchase via the text message. The method includes sending, from the processor to the mobile device, a second signal to initiate the purchase via the second user interface by causing the text message to be sent, upon receiving a second user input within the second user interface.
Some embodiments described herein include methods and apparatus for a technology platform for messaging-based subscriptions and payments initiated from a website viewed on a mobile device or a mobile application. By using custom-generated dynamic deeplinks, some embodiments described herein provide a method of completing mobile subscriptions, communications, and/or purchases. In these embodiments, a number of mobile interfaces can be used including, but not limited to, mobile websites, mobile applications, mobile messages, mobile advertisements, social media applications, and/or the like. In some implementations, the platform allows a user to initiate a subscription via messaging-based communications, or completes a purchase transaction for a product or service using messaging-based communications. In some implementations, custom-generated mobile deeplinks are used. In some implementations, the purchase and/or subscription process can be initiated via a rendered link on a touchscreen mobile device, and a transaction can be completed by two touch screen taps (or Two-Taps).
In some embodiments, a link can be generated in a set of mobile user interfaces including, but not limited to, a mobile website, a mobile application, a link, an email, a mobile advertisement, a text message, and/or the like. When the link is clicked, a custom-rendered deeplink is initiated, and a mobile messaging application is opened on a user's mobile device. In some embodiments, a deeplink is a type of link used in mobile applications that allows the linking of one mobile application to another mobile application. In some implementations, deep linking uses a uniform resource identifier (URI) that links to a mobile application or a specific location within a mobile application. Deeplinks can be used across a set of mobile operating systems including, for example, the Apple® iOS system and the Android™ system.
In some implementations, the content of the message and the recipient's (e.g., the vendor's) phone number can be pre-filled in the messaging application of the mobile device. This information can be communicated to the messaging application using the deeplink specific to the vendor.
In some implementations, the user can switch from, for example, a mobile website, a mobile application, a link, an email, a mobile advertisement, a text message to a subscription message or a purchase message on a mobile messaging application. In some implementations, the mobile device can receive user's selections to subscribe to and/or purchase a good or service via two touch screen taps on a touch screen mobile device. The mobile device can receive a first signal in response to the user selecting (or tapping) on the rendered link on a first mobile user interface (i.e., the first touch screen tap), and the mobile device can receive a second signal in response to the user selecting (or tapping) the “send” message button on a second mobile interface to send the message to the vendor (i.e., the second touch screen tap.) In such implementations, the mobile device receives the user's selections (touch screen tap) via the touch screen of mobile device and then produces a signal to represent the user's selections for further processing by the mobile messaging application.
In some implementations, the user can be subscribed to service to receive messaging based marketing information from the recipient when the message is sent. In some implementations, the user can initiate a process to purchase a product or service from the recipient when the message is sent.
In some embodiments, a method includes receiving a purchase identifier by a processor and in response to a signal generated by the mobile device in response to an input entered by a user at a first user interface of a mobile device. The input is associated with a frame within a page displayed at the first user interface. The method further includes receiving purchase information associated with the purchase identifier and determining a uniform resource identifier (URI) of a second user interface at the mobile device. The second user interface is different from the first user interface. The method includes sending a signal, based on the URI, to cause the second user interface to be rendered at the mobile device with the purchase information pre-populated to fulfill a purchase requested by the user.
In some embodiments, a method includes determining a state of a page load of a page at a first user interface of a mobile device. In response to the state of the page load satisfying a criteria, the method includes providing, based on a set of configurable settings, a frame within the page at the first user interface. The frame includes purchase information and deeplink information such that in response to an input associated with the frame entered by a user, a second user interface is provided at the mobile device with the purchase information pre-populated for the user to initiate a purchase.
In some embodiments, a processor-readable non-transitory medium storing code representing instructions to be executed by a processor, the code includes code to cause the processor to determine a state of a page load of a page at a first user interface of a mobile device. The code further includes code to cause the processor to, in response to the state of the page load satisfying a criteria, provide, based on a set of configurable settings, a frame within the page at the first user interface. The frame include purchase information and deeplink information. The code further includes code to cause the processor to receive a purchase identifier in response to an input entered by a user at the frame mobile device and based on the purchase information. The code includes code to cause the processor to determine, based on the deeplink information, a uniform resource identifier (URI) of a second user interface at the mobile device. The second user interface is different from the first user interface. The code includes code to cause the processor to render, based on the URI, the second user interface at the mobile device with the purchase information pre-populated to fulfill a purchase requested by the user.
As used herein, the singular forms “a,” “an” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, the term “a message” is intended to mean a single message or a combination of messages. For another example, “a purchase identifier” is intended to mean a single purchase identifier or a combination of purchase identifiers.
As used herein, data can include, for example, information such as videos, audio, text, images, games, usernames, passwords, user input, user clicks, user screen taps, user browsing history, information associated with a user, information associated with a user's mobile device, URLs, banking transaction information (e.g., credit card information, back account information, etc.), healthcare information (e.g., prescription information, healthcare records, etc.), public data, protected data, proprietary data, personal data, private data, user generated content, Internet of Things (IoT) data, autonomous vehicle data (e.g., navigation data, status data, security data, etc.), and/or any other information.
The click-to-text server 100 can be or include a computer, a cell phone, a tablet, an electronic device, a critical embedded systems, coprocessors, field-programmable gate arrays (FPGAs) and/or the like. The click-to-text server 100 can include at least one processor 101 and at least one memory 103. The at least one processor 101 and the at least one memory 103 are operatively coupled with each other. The at least one memory 103 can be, for example, non-volatile memory, volatile memory, memory local to a server or networked, virtualized memory, a random-access memory (RAM) (e.g., a dynamic RAM, a static RAM), a flash memory, a removable memory, and/or so forth. In some embodiments, the memory 103 can store, for example, message data 107 (e.g., a set of promotional messages associated with a set of entities or clients), user data 108 (e.g., user phone number, user device identifier, other information identifying the user or the user mobile device, user viewing history, user click/tap history, user status (a new user or an existing user), user cookies, page referrer URLs, impression data, user agent, and/or the like), client data 109 (e.g., user white list associated with a set of clients/entities, user black list associated with a set of clients/entities, client preferences, client business rules, and/or the like). In some implementations, the memory 103 can store, for example, a database(s), process(es), application(s), virtual machine(s), instructions, and/or other software modules (stored and/or executing in hardware) or hardware modules configured to execute an integrator process and a click-to-text process. In such implementations, instructions for executing the click-to-text process, and/or any associated methods can be stored within the memory 103 and executed at the processor 101. In some embodiments, the memory 103 can store code representing integrator instructions 105 (i.e., integration tag) to be executed by the at least one processor 101 or the user mobile device 150. The execution of the integrator instructions 105 at the user mobile device 150 can cause the user mobile device 150 to send a request to the click-to-text server 100 and receive from the click-to-text server 100 promotional messages associated with the client. In some embodiments, the memory 103 can store code representing click-to-text instructions 106 to be executed by the at least one processor 101 to cause the processor to execute the click-to-text process. In some implementations, at least a portion of the data and instructions stored at the memory 103 can be served from one of a single physical machine, multiple physical machines, a virtualized server, multiple virtualized servers, a public cloud, a private cloud, and/or a geographically distributed network of operatively coupled servers.
The at least one processor 101 can be any hardware module and/or component configured to receive and process data, and/or to execute code representing instructions. In some embodiments, the at least one processor 101 can be a general purpose processor, a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), and/or the like. The at least one processor 101 can implement a number of modules and/or server components. The at least one processor 101 can be configured to execute instructions generated by any of its modules and/or server components, and/or instructions stored in the memory 103, for example, the integrator instructions 105 and the click-to-text instructions 106. In some implementations, if the at least one processor 101 includes multiple processors, the modules and/or server components can be distributed among and/or executed by the multiple processors. The at least one memory 103 can be configured to store processor-readable instructions that are accessible and executable by the processor 101.
The client device 130 can be or include a computer, a cell phone, a tablet, an electronic device, a critical embedded systems, coprocessors, and field-programmable gate arrays (FPGAs), a smart TV, and/or another type of network-enabled machine. The client device 130 can include a processor (not shown) and a memory (not shown). In some implementations, the client device 130 is associated with a client (also referred to herein as an entity, a vendor) selling or providing a good(s) or service(s) via the internet, and/or engaging in any marketing activities via the internet. In some implementations, the client device 130 can be served from one of a single physical machine, multiple physical machines, a virtualized server, multiple virtualized servers, a public cloud, a private cloud, and/or a geographically distributed network of operatively coupled servers.
The user mobile device 150 can be any mobile electronic devices. For example, in some embodiments, the user mobile device 150 can be, but are not limited to, a mobile phone, a tablet, a smart watch, a personal computer, a personal digital assistant (PDA), a smart phone, and/or the like. The user mobile device 150 can include a processor (not shown), a memory (not shown), a network interface (not shown), and an output device (not shown). For example, in some embodiments, the output device can be any suitable display that can provide at least a portion of a user interface for a software application (e.g., a mobile application, a PC application, an internet web browser, etc.) installed on (or accessible by) the user mobile device 150. In such embodiments, the display can be, for example, a cathode ray tube (CRT) monitor, a liquid crystal display (LCD) monitor, a light emitting diode (LED) monitor, and/or the like. In other embodiments, the output device can be an audio device, a haptic device, and/or any other suitable output device. In some implementations, the output device can be configured to receive user input via taps (contact) on a touch screen by a user gesture such as a finger tap, swipe, pinch, etc. The network interface of user mobile device 150 can be, for example, a network interface card and/or the like that can include at least an Ethernet port and/or a wireless radio (e.g., a WiFi® radio, a Bluetooth® radio, etc.). The memory of user mobile device 150 can be, for example, a random access memory (RAM), a memory buffer, a hard drive, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), and/or the like. In some embodiments, the memory can include a set of software applications including, but not limited to, a messaging application, a web browser application, an email application, a book reader application, and/or any mobile applications. Each of the set of software applications can have a unique user interface. The processor can be any suitable processing device configured to run or execute a set of instructions or code. For example, the processor of user mobile device 150 can be a general purpose processor, a central processing unit (CPU), an accelerated processing unit (APU), and Application Specific Integrated Circuit (ASIC), and/or the like. The processor can be configured to run or execute a set of instructions or code stored in the memory associated with using, for example, a PC application, a mobile application, an internet web browser, a cellular and/or wireless communication (via a network), and/or the like, as described in further detail herein.
In use, a user can provide a first input (a click, a screen tap, or a selection, etc.) to a web link on a mobile website or a mobile application displayed on the user mobile device 150. This user selection can be sensed by the touch screen of the user mobile device 150 such that a signal is produced and provided to the processor of the user mobile device 150. The web link is associated with a promotional message provided by a client. The client can be an entity selling or providing a good(s) or service(s) via the internet, and/or engaging in any marketing activities via the internet. In response to receiving the signal produced by the touch screen, the processor of user mobile device 150 can produce a notification and send it to the click-to-text server 100. The click-to-text server 100 can receive a notification (e.g., a HTTP POST request) in response to the user input. The click-to-text server 100 can initiate a messaging application at the user mobile device 150 with a message pre-populated with purchase or subscription information and a recipient's phone number. The user can provide a second input (a click, a screen tap, or a selection, etc.) to send the text message to the recipient's phone number. The recipient phone number is associated with the client and the client server 130. In response to sending the text message, the user, via the user mobile device 150, can subscribe to a messaging-based marketing service, or initiate a process of purchasing a product or service, provided by the client and/or the client server 130. In some implementations, this click-to-text process can be completed in just two taps, and in compliance with the Telephone Consumer Protection Act (“TCPA”) and the regulations by trade associations representing the wireless communication industry (e.g., CTIA).
In some implementations, in response to receiving the message 213, the click-to-text server can authenticate the user based on a user identifier. In some implementations, the user identifier can be included in the signal sent to the click-to-text server in response to receiving the message 213. In other implementations, the click-to-text server can receive the user identifier prior to receiving the message 213. In such implementations, the click-to-text server can receive the user identifier in response to an execution of an integration tag (such as the integrator instructions 105 as described with regards to
In some implementations, the click-to-text server can determine, based on the user identifier, if the user is a new subscriber of the client or an existing subscriber of the client. If the user is a new subscriber, the client server and/or the click-to-text server can send a message(s) 222 via the second user interface 221 (the same second user interface shown as 211 in
In some implementations, the second user interface 211 is different from the first user interface 201. In some implementations, the second user interface 211 (e.g., a messaging application) is not a user interface provided by the client/entity/vendor from which the purchase/subscription is to be made. In some implementations, the first user interface 201 is not a user interface (e.g., a web browser) provided by the client/entity/vendor from which the purchase/subscription is to be made. In other words, a user does not need to install the vendor's mobile application to make the purchase from the vendor or subscribe to service provided by the vendor. In situations where, for example, the user is browsing a website with a promotional message 202, the user can select, tap or click the “sign-up” link 203 and a messaging application (e.g., 211) is opened with a message 213 and a phone number 214 pre-populated to complete the purchase/subscription. In such situations, the user does not need to install or open any vendor application. Stated differently, the user can initiate the purchase/subscription upon providing a single user input within the second user interface (e.g., click “send” button at the messaging application) and without further interaction with a user interface associated with a vendor from which the purchase is to be made. The click-to-text process provides dynamic application deeplinking at a mobile device such that the user's interaction with a client via a first user interface of the mobile device can continue to a second user interface of the mobile device. The dynamic application deeplinking protocol improves the user experience for shopping and interacting, via a network, with a client via the mobile device and increases customer engagement with the promotional messages/marketing efforts by the client.
In some implementations, in response to the user selecting, clicking or tapping the “sign-up” link 203 via the first user interface 201, the user mobile device can send a HTTP POST request to the client-to-text server notifying the client-to-text server of the user's select/click/tap on the “sign-up” link 203. The HTTP POST request can include, for example, a purchase identifier associated with the promotional message 202, a purchase identifier associated with the client or the entity providing the promotional message 202 (e.g., a telephone number associated with the client/entity), purchase information associated with the promotional message, a user identifier (e.g., a user phone number, a user mobile device identifier, user impression data, a user agent field collected by the web browser, and/or any information identifying the user and/or user mobile device), and/or the like. The purchase information can include, for example, a subscription to service associated with the promotional message 202, information related to the product(s) or service(s) associated with the promotional message 202, a product identifier, a subscription identifier, and/or the like. An example HTTP form that POSTs to the client-to-text server is as follows:
<form action=“/l/clicks” method=“post” target=“_top”>
<input type=“hidden” name=“i” value=“{impressionId}”></input>
<input type=“hidden” name=“id” value=“{userId}”></input>
<button type=“submit” className={‘${css.formSubmitButton} ${css.override}’}>
<svg viewBox=‘0 0 24 24’ className={‘${css.clickToTextPhoneIcon} ${css.override}’ }>
</button>
</form>
In response to receiving the HTTP request from the user mobile device, the client-to-text server can determine, based on a mobile device identifier, a uniform resource identifier (URI) (including, for example, a link syntax) of a second user interface at the user mobile device. In some implementations, the mobile device identifier can be a user agent field collected by the web browser, a platform type or an operating system type operated at the user mobile device. In some instances, the platform type is the operating system type operated at the user mobile device or information included in the user agent field collected by the web browser. The client-to-text server can determine the URI of the second user interface that is compatible with the operating system type of the user mobile device. The URI of the second user interface (e.g., a messaging application) may be the same or different for different mobile device operating systems. The client-to-text server can generate a response message including the URI of the second user interface and send the response message to the user mobile device to cause the second user interface to open with message and phone number pre-populated. The click-to-text server can receive the pre-populated message and phone number based on the purchase identifier from a database at the click-to-text server. In some implementations, the response message can be a HTTP 303 status code. In some implementations, the response message and the HTTP form that POSTs to the client-to-text server can be stored in the memory of the client-to-text server (e.g., the click-to-text 106 stored at the memory 103 of the client-to-text server 100.) In some implementations, a proper deeplinking (e.g., the HTTP POST request and the response message) can direct the user to the native text messaging application, enabling the two-tap signup. An example response message sent from the client-to-text server is as follows.
public class CreativeController {
@Path(value=“/clicks”, method=Method.POST)
}
In some implementations, in response to the user selecting, clicking or tapping the “sign-up” link 203 via the first user interface 201, the click-to-text server can dynamically request and receive, from, for example, the client database stored at the memory of the click-to-text server, the client's short code (e.g. 24321), the SMS message body (e.g. “Just send this message to join [Company Name] exclusive insiders, or Just send to purchase this red hat”). The client-to-text server can request and receive a platform specific deeplink (e.g., a URI of the second user interface) that causes the user mobile device's messaging application to be rendered at the user mobile device.
In some implementations, when the user selects/clicks/taps the “send” button via the messaging application to send the message, the message can be sent to the wireless communication provider server (e.g., AT&T, Verizon) of the user mobile device. The wireless communication provider server can then make an application programming interface (API) call to the click-to-text server. The API call can trigger a response message back to the user mobile device with a link to set user's preferences. In some instances, this user preference page can use the same client_domain. attn. tv domain specified in the site integration tag as described below.
In some implementations, the click-to-text server can send an integration tag (or site integration tag, or integrator 105 as described in
In response to the execution of the integration tag, the user mobile device can generate a unique visitor identifier and store at least a portion of the integration tag in a local storage of the user mobile device, or as a cookie at the user mobile device. The execution of the integration tag can produce, for example, a HTML, iframe that allows messages to be sent and received between the user mobile device and the click-to-text server. In some implementations, the execution of the integration tag at the user mobile device sends to the click-to-text server user data (e.g., user phone number, user device identifier, other information identifying the user or the user mobile device, user viewing history, user click/tap history, user status (a new user or an existing user), user cookies, page referrer URLs, impression data, a user agent field collected by the web browser, and/or the like). In some implementations, the integration tag can include code that manages, stores, and governs client business rules (e.g., whitelists, blacklists, timeouts, and/or the like). In some implementations, the execution of the integration tag at the user mobile device can send a request to the click-to-text server and receive, from the click-to-text server, promotional messages 202 associated with the client, the client configurable settings/preferences to display the promotional message 202 (e.g., the location of the frame relative to the page, the size of the frame relative to the page, and/or the like.) The user mobile device can then render the frame with the promotional message 202 at its output device. The frame can also include purchase information and deeplink information such that in response to an input entered by the user, the second user interface 211 can be rendered at the mobile device to initiate a purchase/subscription. An example integration tag includes code as follows:
<script>
_attentive_domain=“example.attn.tv”,function( ){window._attentive=invoked:! 1,show:function( ){this.Invoked=!0}};var
t=!1, e=function( ){if(document.readyState&&!/loaded|complete/.test(document.readyState))return=void setTimeout(e,10);if(!t)return t=!0,void setTimeout(e,50);var
n=document.createElement(“script”);n.setAttribute(“async”, “true”),n.type=“text/javascript”,n.src=“https://cdn.attn.tv/loader.js”,((document.getElementsByTagName(“head”)∥[null])[0]∥document.getElementsByTagName(“script”) [0]. parentNode).appendChild(n)};window.addEventListener?window.addEventListener(“load”,e,!1):window.attachEvent(“onload”,e)}( ),window._attentive.show( );
</script>
In some implementations, the integration tag can be customized based on client's preferences. For example, the integration tag can be executed when any webpage associated with the client's website is accessed by the user mobile device. In some instances, the integration tag can be executed only when a webpage from a set of webpages associated with the client's website is accessed by the user mobile device. The set of webpages can be selected via a specific URL slug (e.g., /p/mens_category), a specific rooting (e.g., /p/mens_category /* would cover every page with root of/p/mens_category/, including, for example, /p/mens_categorykshirts/philadephia_phillies/G72 91), a specific query parameter (e.g., clientdomain.com/utm_source=lorem&utm_medium=320b anner&utm_campaign=ipsum), all pages except a specified page (e.g., execute the integration tag on all pages except the checkout page), and/or the like. In some instances, the integration tag can be customized to be executed only by a set of devices that are on a device whitelist or blacklist (e.g., do or do not show the sign-up link 203 for devices on the whitelist or blacklist.) In some instances, the integration tag can be customized to be executed only for users from a set of countries so that the sign-up link 203 can be shown only to users from a set of countries. In some instances, the integration tag can be customized to be executed based on a referrer whitelist or blacklist (e.g., do/do not show sign-up link 203 for users from particular page referrers (e.g. Facebook, Google, etc).) In some instances, the integration tag can be customized to be executed only after a period of time since the last execution of the integration tag (e.g., a length of time until a sign-up unit is displayed again). In some instances, the integration tag can be customized to be executed only after a period of time since a certain event occurs (e.g., a length of time until a sign-up link is displayed again if the user subscribes or makes a purchase, a length of time until a sign-up link is displayed again if the user performs any measured action (close, privacy, terms, click, and/or the like.)
In some implementations, in response to a user sending a message to the client's phone number, the click-to-text server can collect data about the user. In some instances, the click-to-text server can collect transaction payment data including, but not limited to, the user's payment information (e.g. credit card information, bank account information, or other information), shipping address, and preferred shipping-related settings. The click-to-text server can use the data collected to provide a user-friendly purchase experience in subsequent transactions. In some instances, the click-to-text server can collect marketing-based data to help the client send improved marketing-related messages to the user. The marketing-based data can include, but not limited to, the type of messages the user prefers to receive, when the user prefers to receive the message, the type of website content the user has viewed, what items the user has previously purchased, and/or the like. In some instances, the click-to-text server can append additional data, directly collected or through a third party that is appended to the user's phone number as a key value. The data can be used, for example, for fraud protection or to disable a recently changed number.
As shown in
The promotional messages (302, 312, 322, 332, and 342) can be retrieved from a click-to-text server (such as the click-to-text server 100 described with regards to
The “sign-up” link (304, 314, 324, 334, or 344), when selected, clicked or tapped by the user, initiates a second user interface (not shown here) at the user mobile device. The “sign-up” link (304, 314, 324, 334, or 344) can be displayed differently based on client's preferences by the click-to-text server. In some instances, the “sign-up” link (304, 314, 324, 334, or 344) can be shown as a button having different sizes (up to a size of a full screen). In some instances, the “sign-up” link (304, 314, 324, 334, or 344) can be a standalone landing page, or a clickable link (a button, or an image) in line with the text displayed in a webpage, an email, a promotional message (302, 312, 322, 332, and 342), a mobile application, a pop-up window, and/or the like.
In some instances, the phone number 512 can be a short code cellular number or a long code cellular number. In some implementations, the message 513 and the phone number 512 are fixed and cannot be changed by the user. In other implementations, the user has an option to change the content of the pre-populated message 513 and/or the phone number 512. The user can select, click or tap the “send” button 514 to send the message 513 to the client with the phone number 512. The message 513 can be sent to a client server (such as the client server 130 described with regards to
In some implementations, in response to receiving the message 513, the click-to-text server can authenticate the user based on a user identifier. The user identifier can include, but are not limited to, a user phone number, a sender phone number, a device identifier of the user mobile device, and/or other information identifying the user or the user mobile device. In some implementations, the click-to-text server can determine if the user is on a black list or on a white list associated with the client. In some implementations, the click-to-text server can determine, based on the user identifier, if the user is a new customer of the client or an existing customer of the client. If the user is a new customer, the client server and/or the click-to-text server can send a message(s) 522 via the second user interface 521 (e.g., a messaging application) to request shipping information and payment information. The message 522 can also include a link (“checkout link”) that when clicked/tapped, opens a third user interface with a checkout page 531. The third user interface 531 can be the same as the first user interface 501 (e.g., a website browser). Upon receiving the user input on the shipping information and the payment information at the checkout page 531, the third user interface 541 can display an order confirmation page. The client server and/or the click-to-text server can send a message(s) 552 via the second user interface 551 confirming the order has been placed.
If the user is an existing customer of the client, the client server and/or the click-to-text server can send, via the second user interface, a message(s) 562 including the product information in the shopping cart, and a message 563 informing the user of the shipping information and the payment information on file associated with the user. In some implementations, the message 563 can include a link (“checkout link”) that, when selected/clicked/tapped, opens a third user interface (not shown) that shows a checkout page in which the user can change the shipping information and the payment information. In some implementations, the user can send, via the second user interface, a message 572 to confirm the purchase, the payment information and the shipping information. Upon receiving the message 572 from the client, the client server and/or the click-to-text server can send, via the second user interface, a message 582 confirming the order has been placed. In some implementations, the user's purchase history associated with the client (e.g., a new/existing customer, previous orders, previous shopping carts, user payment information, user shipping information, and/or the like) can be stored in a user database of the click-to-text server (such as the user data 108 in the memory 103 of the click-to-text server 100 described with regards to
Similar to the click-to-text subscription process described with regards to
If the user is an existing customer of the client, the client server and/or the click-to-text server can send, via the second user interface 610, a message(s) 609 including the product information in the shopping cart, the shipping information and the payment information on file associated with the user. In some implementations, the message 609 can include a link (“checkout link”) that, when clicked/tapped, opens a second user interface (not shown) that shows a checkout page in which the user can change the shipping information and the payment information. In some implementations, the user can send, via the second user interface, a message 611 to confirm the purchase, the payment information and the shipping information. Upon receiving the message 611 from the client, the client server and/or the click-to-text server can send, via the second user interface, a message 612 confirming the order has been placed. In some implementations, the user's purchase history associated with the client (e.g., a new/existing customer, previous orders, previous shopping carts, user payment information, user shipping information, and/or the like) can be stored in a user database of the click-to-text server (such as the user data 108 in the memory 103 of the click-to-text server 100 described with regards to
At 702, the method includes receiving a purchase identifier in response to an input entered by a user at a first user interface of a mobile device. The first user interface displays a promotional message within a frame of a page at the first user interface. The promotional message can be any advertising information related to a product(s) or service(s) that a client provides. The client can provide the product(s) or the service(s) for free or a fee. In some implementations, the first user interface can be a website browser, an email application, a book reader application, a messaging application, and/or any mobile application or user interfaces at the user mobile device. The location of the frame relative to the page, the size of the frame relative to the page, and/or the like can be customized based on the client's preferences. The promotional message includes a link, which can be clicked or tapped by the user.
In response to the user selecting, clicking or tapping the link via the first user interface, the client-to-text server receives a HTTP POST request notifying the client-to-text server of the user's click/tap on the link. The HTTP POST request can include, for example, a purchase identifier associated with the promotional message, a purchase identifier associated with the client providing the promotional message (e.g., a telephone number associated with the client/entity), a shopping cart identifier, purchase information associated with the promotional message, a user identifier (e.g., a user phone number, a user mobile device identifier, user impression data, a user agent field collected by the web browser, and/or any information identifying the user and/or user mobile device), and/or the like.
At step 704, the method includes receiving purchase information associated with the purchase identifier in response to receiving the HTTP POST request. The purchase identifier and the purchase information can be stored in a database at the click-to-text server. The click-to-text server can look up the purchase information based on the purchase identifier. The purchase information can include, for example, a subscription to service associated with the promotional message 202, information related to the products or service associated with the promotional message 202, a product identifier, a subscription identifier, and/or the like.
At step 706, the method includes determining a uniform resource identifier (URI) of a second user interface at the mobile device. In response to receiving the HTTP request from the user mobile device, the client-to-text server can determine, based on a mobile device identifier, a uniform resource identifier (URI) (including, for example, a link syntax) of a second user interface at the user mobile device. The second user interface can be a messaging application, and/or the like. In some implementations, the mobile device identifier can be a user agent field collected by the web browser, a platform type or an operating system type operated at the user mobile device. In some implementations, the mobile device identifier can be a user identifier (e.g., a user phone number, a user mobile device identifier, user impression data, and/or any information identifying the user and/or user mobile device). The client-to-text server can determine the URI of the second user interface that is compatible with the operating system type of the user mobile device. The URI of the second user interface (e.g., a messaging application) may be the same or different for different mobile device operating systems.
At step 708, the method includes sending a signal, based on the URI, to cause the second user interface to be rendered at the mobile device with the purchase information pre-populated to fulfill a purchase requested by the user. The client-to-text server can generate a response message including the URI of the second user interface and send the response message to the user mobile device to cause the second user interface to open with message and phone number pre-populated. The click-to-text server can receive the pre-populated message and phone number based on the purchase identifier from a database at the click-to-text server or a databased stored at the client device. In some implementations, the response message can be a HTTP 303 status code. In some implementations, the response message and the HTTP form that POSTs to the client-to-text server can be stored in the memory of the client-to-text server (e.g., the click-to-text 106 stored at the memory 103 of the client-to-text server 100.) In some implementations, a proper deeplinking (the HTTP POST request and the response message) can direct the user to the native text messaging application, enabling the two-tap subscription or purchase.
The content of the message and/or the phone number can be customized, based on client's preferences, by a click-to-text server. In some instances, the phone number can be a short code cellular number or a long code cellular number. In some instances, the content of the message can be related to, for example, join a subscription list, purchase a product or service, request customer service, or any number of other ways in which the user interacts with the client. In some implementations, the message and the phone number are fixed and cannot be changed by the user. In other implementations, the user has an option to change the content of the pre-populated message and/or the phone number. The user can click or tap the “send” button to send the message to the client associated with the phone number. The message can be sent to a client and/or the click-to-text server. In response to receiving the message, the client server can send a message(s) via the second user interface (e.g., a messaging application) to confirm the user's subscription or purchase. In some implementations, the click-to-text server can send message to confirm the user's subscription or purchase.
In some implementations, the click-to-text server can determine, based on the user identifier, if the user is a new subscriber/customer of the client or an existing subscriber/customer of the client. If the user is a new subscriber/customer, the client server and/or the click-to-text server can send a message(s) via the second user interface (e.g., a messaging application) to confirm the user's subscription, and/or direct the user to a checkout page to provide shipping information and product information for the purchase. If the user is an existing subscriber/customer, the client server and/or the click-to-text server can send a message(s) informing the user that the user are already subscribed to the client's service, or confirming the shipping information and payment information with the user. In some implementations, the user's subscription/customer status associated with the client (e.g., a new subscriber or an existing subscriber) can be stored in a user database of the click-to-text server.
In some implementations, the second user interface is different from the first user interface. In some implementations, the second user interface (e.g., a messaging application) is not a user interface provided by the client/entity/vendor from which the purchase/subscription is to be made. In some implementations, the first user interface is not a user interface (e.g., a web browser) provided by the client/entity/vendor from which the purchase/subscription is to be made. In other words, a user does not need to install the vendor's mobile application to make the purchase from the vendor or subscribe to service provided by the vendor. In situations where, for example, the user is browsing a website with a promotional message, the user can click the “sign-up” link and a messaging application is opened with a message and a phone number pre-populated to complete the purchase/subscription. In such situations, the user do not need to install or open any vendor application. Stated differently, the user can initiate the purchase/subscription upon providing a single user input the second user interface (e.g., click “send” button at the messaging application) within and without interaction with a user interface associated with a vendor from which the purchase is to be made. The click-to-text process provides dynamic application deeplinking at a mobile device such that the user's interaction with a client via a first user interface of the mobile device continues to a second user interface of the mobile device. The dynamic application deeplinking protocol improves the user experience for shopping and interacting, via a network, with a client via the mobile device and increases customer engagement with the promotional messages/marketing efforts by the client.
It is intended that the systems and methods described herein can be performed by software (stored in memory and/or executed on hardware), hardware, or a combination thereof. Hardware modules may include, for example, a general-purpose processor, a field programmable gate array (FPGA), and/or an application specific integrated circuit (ASIC). Software modules (executed on hardware) can be expressed in a variety of software languages (e.g., computer code), including Unix utilities, C, C++, Objective-C Java™, Ruby, SQL, SAS®, the R programming language/software environment, Visual Basic™, and other object-oriented, procedural, scripted, machine language or other programming language and development tools. Examples of computer code include, but are not limited to, micro-code or micro-instructions, machine instructions, such as produced by a compiler, code used to produce a web service, and files containing higher-level instructions that are executed by a computer using an interpreter. Additional examples of computer code include, but are not limited to, control signals, encrypted code, and compressed code. Each of the devices described herein can include one or more processors as described above.
Some embodiments described herein relate to devices with a non-transitory computer-readable medium (also can be referred to as a non-transitory processor-readable medium or memory) having instructions or computer code thereon for performing various computer-implemented operations. The computer-readable medium (or processor-readable medium) is non-transitory in the sense that it does not include transitory propagating signals per se (e.g., a propagating electromagnetic wave carrying information on a transmission medium such as space or a cable). The media and computer code (also can be referred to as code) may be those designed and constructed for the specific purpose or purposes. Examples of non-transitory computer-readable media include, but are not limited to: magnetic storage media such as hard disks, floppy disks, and magnetic tape; optical storage media such as Compact Disc/Digital Video Discs (CD/DVDs), Compact Disc-Read Only Memories (CD-ROMs), and holographic devices; magneto-optical storage media such as optical disks; carrier wave signal processing modules; and hardware devices that are specially configured to store and execute program code, such as Application-Specific Integrated Circuits (ASICs), Programmable Logic Devices (PLDs), Read-Only Memory (ROM) and Random-Access Memory (RAM) devices. Other embodiments described herein relate to a computer program product, which can include, for example, the instructions and/or computer code discussed herein.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Where methods and steps described above indicate certain events occurring in certain order, the ordering of certain steps may be modified. Additionally, certain of the steps may be performed concurrently in a parallel process when possible, as well as performed sequentially as described above. Although various embodiments have been described as having particular features and/or combinations of components, other embodiments are possible having any combination or sub-combination of any features and/or components from any of the embodiments described herein. Furthermore, although various embodiments are described as having a particular entity associated with a particular compute device, in other embodiments different entities can be associated with other and/or different compute devices.
The present application is a continuation of U.S. patent application Ser. No. 17/569,265, filed Jan. 5, 2022 and entitled Methods and Apparatus for Mobile Device Messaging-Based Communications Using Custom-Generated Deeplinks and Based on the Hyper Text Transfer Protocol (HTTP),” the entire contents of which are hereby incorporated by reference. U.S. patent application Ser. No. 17/569,265 is a continuation of U.S. patent application Ser. No. 17/496,590 filed Oct. 7, 2021 and entitled “Methods and Apparatus for Dynamic Application Deeplinking at a Mobile Electronic Device,” which is a continuation of U.S. patent application Ser. No. 15/986,569 filed May 22, 2018 and entitled “A Technology Platform for Messaging-Based Subscriptions and Payments Initiated From a Mobile Website,” which claims the benefit of and priority to U.S. Provisional Patent Application No. 62/511,413 filed May 26, 2017 and entitled “A Technology Platform for Messaging-Based Subscriptions and Payments Initiated From a Mobile Website.”
| Number | Name | Date | Kind |
|---|---|---|---|
| 8015615 | Agrawal | Sep 2011 | B1 |
| 9105046 | Dias et al. | Aug 2015 | B1 |
| 9195477 | Spencer | Nov 2015 | B1 |
| 9251268 | Schechter et al. | Feb 2016 | B2 |
| 9465682 | Powell et al. | Oct 2016 | B1 |
| 9594477 | Ardakani et al. | Mar 2017 | B1 |
| 9633378 | Nath | Apr 2017 | B1 |
| 9806942 | Saxena et al. | Oct 2017 | B2 |
| 9811395 | Greenwood et al. | Nov 2017 | B1 |
| 9847973 | Jakobsson et al. | Dec 2017 | B1 |
| 10042946 | Boudville | Aug 2018 | B2 |
| 10055211 | Maddern et al. | Aug 2018 | B2 |
| 10121186 | Isaacson et al. | Nov 2018 | B2 |
| 10275421 | Clark | Apr 2019 | B1 |
| 10275798 | Clark et al. | Apr 2019 | B1 |
| 10423691 | Patel et al. | Sep 2019 | B1 |
| 10521496 | Goodwin et al. | Dec 2019 | B1 |
| 10535005 | Badr et al. | Jan 2020 | B1 |
| 10659400 | Moon et al. | May 2020 | B2 |
| 10691409 | Maltsev et al. | Jun 2020 | B2 |
| 10757552 | Gross et al. | Aug 2020 | B2 |
| 10789626 | Nath et al. | Sep 2020 | B2 |
| 10810592 | Omojola et al. | Oct 2020 | B1 |
| 10817914 | Nath et al. | Oct 2020 | B1 |
| 10868711 | Chor | Dec 2020 | B2 |
| 11055744 | Conrad et al. | Jul 2021 | B2 |
| 11117380 | Tamaru et al. | Sep 2021 | B2 |
| 11151603 | Tasharofi et al. | Oct 2021 | B2 |
| 11170380 | Long et al. | Nov 2021 | B1 |
| 11211156 | Iyer et al. | Dec 2021 | B2 |
| 11336703 | Meersma et al. | May 2022 | B1 |
| 11416887 | Long et al. | Aug 2022 | B1 |
| 11416897 | Long et al. | Aug 2022 | B1 |
| 11553074 | Long et al. | Jan 2023 | B1 |
| 20020152210 | Johnson et al. | Oct 2002 | A1 |
| 20060224693 | Gaidemak et al. | Oct 2006 | A1 |
| 20080059571 | Khoo | Mar 2008 | A1 |
| 20080307517 | Grigoriev et al. | Dec 2008 | A1 |
| 20100063902 | Constantz | Mar 2010 | A1 |
| 20100099441 | Agarwal et al. | Apr 2010 | A1 |
| 20110302316 | Chou et al. | Dec 2011 | A1 |
| 20120084152 | Highbaugh, Sr. et al. | Apr 2012 | A1 |
| 20120144281 | Schechter et al. | Jun 2012 | A1 |
| 20120232985 | Lasker | Sep 2012 | A1 |
| 20130073381 | Binkley | Mar 2013 | A1 |
| 20130073400 | Heath | Mar 2013 | A1 |
| 20130117089 | Pachikov et al. | May 2013 | A1 |
| 20140108373 | Abrahami et al. | Apr 2014 | A1 |
| 20140172504 | Duva et al. | Jun 2014 | A1 |
| 20140229898 | Terwedo | Aug 2014 | A1 |
| 20140282994 | Dietrich | Sep 2014 | A1 |
| 20150052061 | Anderson et al. | Feb 2015 | A1 |
| 20150088980 | Lakes et al. | Mar 2015 | A1 |
| 20150100468 | Blackhurst et al. | Apr 2015 | A1 |
| 20150106181 | Kluth | Apr 2015 | A1 |
| 20150127554 | Steif et al. | May 2015 | A1 |
| 20150154644 | Saxena et al. | Jun 2015 | A1 |
| 20150156061 | Saxena | Jun 2015 | A1 |
| 20150178784 | Oliver et al. | Jun 2015 | A1 |
| 20150215383 | Sun et al. | Jul 2015 | A1 |
| 20150220943 | Dossick et al. | Aug 2015 | A1 |
| 20150294358 | Galadari et al. | Oct 2015 | A1 |
| 20160055133 | Look et al. | Feb 2016 | A1 |
| 20160057154 | Ferguson et al. | Feb 2016 | A1 |
| 20160142858 | Molinet et al. | May 2016 | A1 |
| 20160142859 | Molinet | May 2016 | A1 |
| 20160188721 | Glover et al. | Jun 2016 | A1 |
| 20160210334 | Prophete et al. | Jul 2016 | A1 |
| 20160234330 | Popowitz et al. | Aug 2016 | A1 |
| 20160292728 | Kang et al. | Oct 2016 | A1 |
| 20170004209 | Johl et al. | Jan 2017 | A1 |
| 20170046180 | Desineni et al. | Feb 2017 | A1 |
| 20170099228 | Hunsperger et al. | Apr 2017 | A1 |
| 20170116339 | Stein et al. | Apr 2017 | A1 |
| 20170118500 | Carroll et al. | Apr 2017 | A1 |
| 20170142214 | Nanavati et al. | May 2017 | A1 |
| 20170169473 | Boudville | Jun 2017 | A1 |
| 20170193087 | Savliwala et al. | Jul 2017 | A1 |
| 20170213464 | Emadi et al. | Jul 2017 | A1 |
| 20170222940 | O'Kelley et al. | Aug 2017 | A1 |
| 20170228797 | Nath | Aug 2017 | A1 |
| 20170236196 | Isaacson et al. | Aug 2017 | A1 |
| 20170255915 | Chandrasekaran et al. | Sep 2017 | A1 |
| 20170256003 | Isaacson et al. | Sep 2017 | A1 |
| 20170287009 | Austin | Oct 2017 | A1 |
| 20170337609 | Turemen et al. | Nov 2017 | A1 |
| 20170351693 | Boudville | Dec 2017 | A1 |
| 20180018304 | Pritchard et al. | Jan 2018 | A1 |
| 20180020038 | Penov et al. | Jan 2018 | A1 |
| 20180020039 | Loeb et al. | Jan 2018 | A1 |
| 20180052926 | Boudville | Feb 2018 | A1 |
| 20180052943 | Hui et al. | Feb 2018 | A1 |
| 20180074999 | Cogan | Mar 2018 | A1 |
| 20180095604 | Nguyen et al. | Apr 2018 | A1 |
| 20180103151 | Erm | Apr 2018 | A1 |
| 20180124148 | Boudville | May 2018 | A1 |
| 20180183618 | Jayaram et al. | Jun 2018 | A1 |
| 20180183619 | Jayaram et al. | Jun 2018 | A1 |
| 20180239576 | Fain | Aug 2018 | A1 |
| 20180260417 | Mahadevan et al. | Sep 2018 | A1 |
| 20180261861 | Jamal | Sep 2018 | A1 |
| 20180286236 | Mazzola et al. | Oct 2018 | A1 |
| 20180300754 | Narasimhan et al. | Oct 2018 | A1 |
| 20180324210 | Gadot | Nov 2018 | A1 |
| 20180324265 | MacSkassy et al. | Nov 2018 | A1 |
| 20190246238 | Crutchfield et al. | Aug 2019 | A1 |
| 20200104192 | Siddhartha | Apr 2020 | A1 |
| 20200111494 | Lau et al. | Apr 2020 | A1 |
| 20200242303 | Hwang et al. | Jul 2020 | A1 |
| 20210233097 | Doumar | Jul 2021 | A1 |
| 20210377309 | Jogand-Coulomb et al. | Dec 2021 | A1 |
| 20230017848 | Doumar et al. | Jan 2023 | A1 |
| 20230021327 | Doumar | Jan 2023 | A1 |
| 20230206267 | Doumar | Jun 2023 | A1 |
| Entry |
|---|
| User_Reachability_in_Multi-Apps_Environment (Year: 2015). |
| Send Messages & SMS from Web & Email with a URL Trick (Year: 2016). |
| Aladdin_Automating_Release_of_Android_Deep_Links_to_In-App_Content (Year: 2017). |
| Cross-Platform_Access_Control_for_Mobile_Web_Applications (Year: 2012). |
| Piecing_together-app_behavior_from_multiple_artifacts_A_case_study (Year: 2015). |
| U.S. Appl. No. 17/888,373 Amendment Under 37 CFR 1.312, filed Mar. 17, 2023, 10 pages. |
| U.S. Appl. No. 18/306,017, filed Apr. 24, 2023, 41 pages. |
| Advisory Action dated Sep. 1, 2020, for U.S. Appl. No. 15/986,569, 5 pages. |
| Android: how to pre-populate an SMS message; Nov. 20, 2014; Stack Overflow; pp. 1-3. |
| Appeal Brief filed on Nov. 23, 2020, for U.S. Appl. No. 15/986,569, 74 pages. |
| Declaration of John G. Day in Support of Motion to Dismiss, Attentive Mobile Inc. v. 317 Labs, Inc. d/b/a Emotive, C.A. No. 22-1163-CFC, Oct. 31, 2022, 37 pages. |
| Declaration of Michael J. Flynn, Attentive Mobile Inc. v. 317 Labs, Inc. d/b/a Emotive, C.A. No. 22-1163-CFC, Nov. 30, 2022, 19 pages. |
| Defendant's Opening Brief for Motion to Dismiss, Attentive Mobile Inc. v. 317 Labs, Inc. d/b/a Emotive, C.A. No. 22-1163-CFC, Oct. 31, 2022, 31 pages. |
| Final Office Action dated Aug. 8, 2019, for U.S. Appl. No. 15/986,569, 14 pages. |
| Final Office Action dated Jun. 26, 2020, for U.S. Appl. No. 15/986,569, 25 pages. |
| Final Office Action dated May 12, 2021, for U.S. Appl. No. 17/114,937, 15 pages. |
| Hoffman T; Long Code v. Short Code: Why the Difference Maters; Apr. 20, 2016; text-em-all.com; pp. 1-7. |
| Href link to send text message; May 12, 2017; Stack Overflow; pp. 1-3. |
| Non Final Office Action for U.S. Appl. No. 18/082,481 dated Mar. 23, 2023, 35 pages. |
| Non-Final Office Action for U.S. Appl. No. 18/082,498 dated Mar. 23, 2023, 31 pages. |
| Non-Final Office Action dated Mar. 17, 2022, for U.S. Appl. No. 17/569,265, 54 pages. |
| Non-Final Office Action dated Mar. 4, 2022, for U.S. Appl. No. 17/496,590, 40 pages. |
| Non-Final Office Action dated Feb. 20, 2020, for U.S. Appl. No. 15/986,569, 22 pages. |
| Non-Final Office Action dated Jul. 22, 2021, for U.S. Appl. No. 17/114,937, 13 pages. |
| Non-Final Office Action dated Mar. 21, 2019, for U.S. Appl. No. 15/986,569, 14 pages. |
| Non-Final Office Action dated Mar. 4, 2021, for U.S. Appl. No. 17/114,937, 12 pages. |
| Non-Final Office Action dated Oct. 29, 2018, for U.S. Appl. No. 15/986,569, 13 pages. |
| Notice of Allowance for U.S. Appl. No. 17/888,373, dated Feb. 21, 2023, 9 pages. |
| Plaintiff's Answering Brief for Motion to Dismiss, Attentive Mobile Inc. v. 317 Labs, Inc. d/b/a Emotive, C.A. No. 22-1163-CFC, Nov. 30, 2022, 32 pages. |
| RFC 5724: URI Scheme for Global System for Mobile Communications (GSM) Short Message Service (SMS); Jan. 2010; Internet Engineering Task Force (IETF); pp. 1-18. |
| Solano et al., “One-Time URL: A Proximity Security Mechanism between Internet of Things and Mobile Devices,” Sensors, Oct. 13, 2016, vol. 16, No. 1694, 17 pages (Year: 2016). |
| U.S. Notice of Allowance for U.S. Appl. No. 17/569,265, dated Jun. 24, 2022, 4 pages. |
| U.S. Notice of Allowance for U.S. Appl. No. 17/569,265, dated Jun. 6, 2022, 17 pages. |
| U.S. Notice of Allowance for U.S. Appl. No. 17/669,114, dated Jun. 16, 2022, 11 pages. |
| U.S. Office Action for U.S. Appl. No. 17/888,373, dated Nov. 10, 2022, 18 pages. |
| U.S. Appl. No. 18/082,481, filed Dec. 15, 2022, 71 pages total. |
| U.S. Appl. No. 18/082,498, filed Dec. 15, 2022, 71 pages total. |
| Defendant's Opening Brief for Motion to Dismiss, Attentive Mobile Inc. v. Stodge Inc. d/b/a Postscript, C.A. No. 23-87-CFC-CJB, Feb. 15, 2023, 29 pages. |
| Defendant's Reply Brief for Motion to Dismiss, Attentive Mobile Inc. v. Stodge Inc. d/b/a Postscript, C.A. No. 23-087-CJB, Mar. 29, 2023, 15 pages. |
| Motion to Dismiss, Attentive Mobile Inc. v. Stodge Inc. d/b/a Postscript, C.A. No. 23-87-CFC-CJB, Feb. 15, 2023, 3 pages. |
| Non-Final Office Action dated Jul. 25, 2022, for U.S. Appl. No. 17/496,590, 52 pages. |
| Notice of Allowance for U.S. Appl. No. 17/888,373 dated Apr. 18, 2023, 5 pages. |
| Plaintiffs Answering Brief for Motion to Dismiss, Attentive Mobile Inc. v. Stodge Inc. d/b/a Postscript, C.A. No. 23-087 (CJB), Mar. 15, 2023, 26 pages. |
| Complaint for Patent Infringement in Attentive Mobile Inc.v. Stodge Inc. d/b/a Postscript, Case No. 1-23-cv-00086 (D. Del. filed Jan. 25, 2023). |
| Cristal, “Ad Serving Technology, Understand the marketing revelation that commercialized the internet,” ISBN: 148467572 (2014), pp. 1-27, 190-193, 282-283, 584-585. |
| Declaration of Dr. Henry Houh, Attentive Mobile Inc.v. Stodge Inc. d/b/a Postscript, Inter Partes Review Exhibit 1002, Aug. 16, 2023, 103 pages. |
| Final Office Action for U.S. Appl. No. 18/082,481 dated Jul. 31, 2023, 30 pages. |
| Firtman, M., “Programming the Mobile Web, Second Edition”, O'Reilly (2013), pp. 553-595. |
| Flanagan, D. “JavaScript: The Definitive Guide, Sixth Edition”, O'Reilly Media, Inc. (2011), pp. 361-411. |
| Ha, A, “TapCommerce's founders are back with attentive, a messaging startup that's raised $13M,” available at https:techcrunch.com/2018/02/08/attentive-launch/, Feb. 8, 2018, 9 pages. |
| Levine, B., “Led by TapCommerce founders, startup Attentive launches SMS/MMS marketing platform,” available at https://martech.org/led-tapcommerce-founders-startup-attentive-launches-smsmms-marketing-platform/, Feb. 9, 2018, 5 pages. |
| Mobile Marketing Association, “US Consumer Best Practices for Messaging”, version 7.0, (2012), available at https://www.mmaglobal.com/documents/us-consumer-best-practices, 46 pages. |
| Notice of Allowance for U.S. Appl. No. 18/082,498 dated Aug. 4, 2023, 10 pages. |
| Petition for Inter Partes Review Under 35 U.S.C. §§ 311-319 and 37 C.F.R. § 42.200 et seq. for Stodge, Inc. d/b/a PostScript, petitioner, v. Attentive, Inc., Patent Holder, IPR2023-01338, U.S. Pat. No. 11,416,887, Aug. 19, 2023, 78 pages. |
| Scheiner, M., “Attentive Gets the Message Out,” available at https://crm.org/news/attentive-gets-the-message-out, Feb. 27, 2020, 12 pages. |
| U.S. Appl. No. 13/461,541 filed May 1, 2012, 48 pages. |
| U.S. Appl. No. 62/079,512 filed Nov. 13, 2014, 27 pages. |
| Defendant 317 Labs, Inc. d/b/a/ Emotive's Answer and Defenses, C.A. No. 22-1163-CJB, Oct. 4, 2023, 16 pages. |
| Defendant Stodge Inc. d/b/a Postcript's Amended Answer and Counterclaims to Plaintiff's Complaint for Patent Infringement, Aug. 25, 2023, 55 pages. |
| Joint Claim Construction Chart for U.S. Pat. Nos. 11,416,887, 11,416,897, and 11,553,074, dated Oct. 13, 2023, 14 pages. |
| Petition for Inter Partes Review Under 35 U.S.C. §§ 311-319 and 37 C.F.R. §42.200 et seq. for Stodge, Inc. d/b/a PostScript, petitioner, v. Attentive, Inc., Patent Holder, IPR2024-00129, U.S. Pat. No. 11,553,074, Oct. 31, 2023, 78 pages. |
| Plaintiff's Preliminary Identification of Terms and Phrases for Construction and Preliminary Proposed Constructions, Attentive Mobile Inc.v. Stodge Inc. d/b/a Postscripts, Case No. 1-23-cv-00087, Sep. 29, 2023, 4 pages. |
| 317 Labs, Inc. d/b/a/ Emotive's and Stodge Inc. d/b/a/ Postscript's Joint Proposed Claim Terms and Constructions, Attentive Mobile Inc.v. Stodge Inc. d/b/a Postscripts, Case No. 1-23-cv-00087, Sep. 29, 2023, 4 pages. |
| Declaration of Dr. Henry Houh, Attentive Mobile Inc.v. Stodge Inc. d/b/a Postscript, Oct. 31, 2023, 118 pages. |
| Petitioner for Inter Partes Review Under 35 U.S.C. §§ 311-319 and 37 C.F.R. § 42.200 et seq. for Stodge, Inc. d/b/a PostScript, Petitioner, v. Attentive, Inc., Patent Holder, IPR2024-00129, U.S. Pat. No. 11,416,897, Oct. 19, 2023, 80 pages. |
| Declaration of Dr. Henry Houh, Attentive Mobile Inc.v. Stodge Inc. d/b/a Postscript, for U.S. Pat. No. 11/416,897, Oct. 19, 2023, 114 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 62511413 | May 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17569265 | Jan 2022 | US |
| Child | 17888343 | US | |
| Parent | 17496590 | Oct 2021 | US |
| Child | 17569265 | US | |
| Parent | 15986569 | May 2018 | US |
| Child | 17496590 | US |
