Improved push notification delivery
The system addresses inefficiencies in push messaging by using unique phone numbers tied to contextual data for targeted delivery, improving relevance and reducing bandwidth usage and latency.
Patent Information
- Application Number
- DE112016005265
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2015-11-17
- Filing Date
- 2016-10-11
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2036-10-11
AI Technical Summary
Existing push messaging systems lack the ability to efficiently target and deliver content to relevant users based on contextual data, leading to unnecessary bandwidth usage and delayed delivery.
A system that assigns a unique push messaging phone number to users based on their contextual data, allowing for targeted delivery of messages when the user is in the most advantageous position to receive them, using geographical location, time of day, and user interaction with electronic documents.
Enhances content delivery by reducing bandwidth usage and latency while ensuring timely and relevant message delivery to users, allowing users to subscribe to services that align with their interests and preferences.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
BACKGROUND
[0001] This specification concerns the processing of data and the distribution of content via push notification.
[0002] The internet and networking capabilities facilitate the exchange of information and transactions between users worldwide. This exchange of information enables the distribution of content to a large number of users. In some situations, information may be contained in push notifications delivered to users who have registered on a subscription service's subscriber list.
[0003] German patents DE 10 2007 025 020 A1 and US 2015 / 0 163 675 A1 concern procedures for push data transmission in connection with a registration process. Specifically, German patent DE 10 2007 025 020 A1 discloses the allocation of "info-push" telephone numbers. SUMMARY
[0004] In general, an innovative aspect of the subject matter described in this specification can be implemented in methods that include receiving, from a user device, a request to subscribe to a push notification service, and selecting, by one or more servers, a specific telephone number uniquely assigned to the user based on the received request, where the specific telephone number is different from the user's telephone number. Furthermore, the methods can include sending, to a user device and in response to receiving the request, an initial message that presents visual information on the user device and includes the specific telephone number, and receiving, from the user device and by one or more servers, a second message addressed to the specific telephone number.Furthermore, the methods may involve selecting, by one or more servers, an additional message that presents additional visual information on the user device, at least partially based on the message received by the user device and one or more from a geographic location of the mobile device or a time of day, and sending the additional message to the user device.
[0005] Receiving a request to subscribe to a push notification service may further include receiving a data packet containing data representing a user interaction with a subscription user interface element presented in an online search results page, as well as contextual data of the user's device.
[0006] Receiving a data packet containing context data may include receiving a data packet that specifies a search query used to generate the electronic document prior to user interaction with the subscription user interface element.
[0007] Receiving a second message addressed to the specified phone number may include receiving a second message confirming the request to subscribe to the push notification service, the second message containing a phone number of the user's device.
[0008] The process may further include: obtaining distribution criteria that specify the conditions that must be met for one or more push messages to be distributed to user devices, the distribution criteria including one or more geographic location data of the user devices, a time of day, or user interaction with electronic documents associated with a subscriber list; determining, based on context data of the user device, that the distribution criteria are met; and distributing, using the user device's phone number, the additional message to the user device, based on the determination that the distribution criteria are met.
[0009] The procedure may further include: requesting third-party content from a third-party content distribution system for inclusion in the additional message; and receiving the third-party content from the third-party content distribution system for inclusion in the additional message.
[0010] The procedure may further include determining that the user device will receive the additional message, the determination being based on user control information which includes at least one of limiting the number of additional messages sent to the user device or the times at which the user device allows messages to be sent to the user device by the one or more servers.
[0011] The procedure may also include indexing contextual data related to the user with the specified telephone number, including indexing at least one piece of information from a mobile phone number of the user's device, a search query submitted by the user, a time of day at which the search query was submitted, or a geographic location of the mobile device according to the specified telephone number.
[0012] Further embodiments of this aspect include appropriate systems, devices and computer programs configured to perform the actions of the procedure encoded on computer storage devices.
[0013] Certain embodiments of the subject matter described in this specification can be implemented to realize one or more of the following advantages. The subject matter described in this application enables push notifications to be distributed based on contextual distribution information for the content of the user associated with the user's device. This targeted content delivery allows content to be delivered only to a subset of relevant devices and provides improved content delivery, which can reduce bandwidth usage while still delivering content to relevant users.For example, the device can enable information such as a warning to be distributed to users at a specific location associated with the information, while simultaneously avoiding the need to distribute this information to users outside the relevant location.
[0014] Implementations of the subject matter of this application allow a push message to be delivered to a user device when the user device is in the most advantageous position to positively receive the third-party content of the push message and to act upon its content. Additionally, the subject matter of this application allows users to subscribe to push messaging services of interest and to receive the push messages directly on their user device when the contextual distribution and user control information indicates that the push message will be most useful to the user.
[0015] The device described in this document also reduces the time required by a data processing device to select and deliver push notifications to the user based on the interaction of the push notification delivery system with a third-party content distribution system. This interaction results in lower latency in selecting and delivering the push notification to the user in a timely manner.
[0016] The feature described in this document enhances a push notification system, for example, by enabling the system to collect data about a specific user and uniquely associate that data with that user. For instance, in some implementations, each user is automatically assigned a unique push notification phone number, and this unique phone number is linked to the data collected about that user. When distribution criteria for a specific push message are met by the data collected from that user, the push notification phone number associated with that user is then used to deliver the push message to that user (e.g., as a message delivered to the user's mobile phone).
[0017] The details of one or more embodiments of the item described in this specification are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages of the item will become apparent from the description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS Fig. Figure 1 shows a block diagram of an exemplary environment in which content is distributed. Fig. Figure 2 shows an exemplary screenshot of a subscription process presented on a user device, along with a system diagram of the interaction between the user device and the push notification system. The Fig. 3A, Fig. 3B, and Fig. 3C shows sample account interfaces. Fig. Figure 4 shows an example user subscription manager interface. Fig. Figure 5 shows a flowchart of an exemplary push notification delivery process.
[0018] Identical reference numbers and designations in the different drawings refer to similar elements. DETAILED DESCRIPTION
[0019] This document discloses methods, systems, devices and a computer-readable medium that facilitate and improve the delivery of push notifications to users. Fig. Figure 1 shows a block diagram of an exemplary environment 100 in which push notification services are initiated and delivered to users. The exemplary environment 100 includes a network 102, such as a local area network (LAN), a wide area network (WAN), the Internet, or a combination thereof. The network 102 connects an electronic document server 104, user devices 106, a search system 108, and a push notification system 120, which communicates with a third-party content distribution system 130.
[0020] A user device 106 is an electronic device capable of requesting and receiving resources and content over the network 102. Exemplary user devices 106 can include personal computers, mobile communication devices including mobile phones or smartphones, and other devices capable of sending and receiving data over the network 102. A user device 106 typically includes a user application, such as a web browser, to facilitate sending and receiving data over the network 102; however, native applications running on the client device 106 can also facilitate sending and receiving data over the network 102.
[0021] An electronic document is data that presents a set of content on a user device. Examples of electronic documents include web pages, word processing documents, Portable Document Format (PDF) documents, images, videos, search results pages, and feed sources. Native applications (e.g., "apps"), such as applications installed on mobile, tablet, or desktop computer devices, are also examples of electronic documents. Electronic documents can be delivered to user devices by electronic document servers. For example, electronic document servers may include servers that host publisher websites.In this example, the user device 106 can initiate a request for a specific publisher web page, and the electronic server 104, which hosts the specific publisher web page, can respond to the request by sending machine-executable commands that initiate the presentation of the specific web page on the user device 106.
[0022] In another example, the electronic document servers can include application servers from which user devices can download applications. In this example, the user device can download the files required to install an application on the user device and then run the downloaded application locally.
[0023] Electronic documents can contain a variety of content. For example, an electronic document may contain static content (such as text or other specified information) that is present in the document and / or does not change over time. Electronic documents may also contain dynamic content that can change over time or depending on specific requirements. For example, the publisher of a particular document may manage a data source that is used to populate portions of the electronic document. In this example, the particular electronic document may contain a tag or script that instructs the user device 106 to request content from the data source when the particular electronic document is processed (such as rendered or executed) by the user device 106.The user device 106 integrates the content received from the data source into the specified document to create a composite electronic document that includes the content received from the data source.
[0024] To facilitate the retrieval of these electronic documents, the search system 110 identifies the electronic documents by crawling the electronic documents server 104 (e.g., crawling the publisher websites and indexing the resources provided by the publisher websites). The electronic documents are indexed by the index processor 112, and the information is stored in the index data 114. Although the index processor 112 and the index data 114 are represented as a single entity, this entity can contain multiple parts and different indexes. The user device 106 can send search queries to the search system 110. The search queries are sent in the form of a search request, which includes the search query and, optionally, a unique identifier that identifies the user device 106 sending the request.The unique identifier can be data from a cookie stored on the user's device, or the identifier of a user account if the user has an account with the search system 110, or another identifier that identifies the user's device 106 or the user using the user's device.
[0025] In response to the search request, the search system 110 uses the index processor 112 to identify electronic documents relevant to the queries. The search system 110 identifies the electronic documents, including search results, answers, and information cards, and delivers data describing the responsive information to the user devices 106 in a search results page, which is graphically presented on a display of the user device.
[0026] A search result is data generated by the search system 110 that identifies one or more electronic documents or provides information that satisfies a specific search query. A search query is a command input on the user device 106 for the search system 110. Other information, such as answers and information cards, may include facts derived from the electronic documents and, optionally, links to the electronic documents from which the facts were derived. The search results can be ranked based on scores for the resources identified by the search results. The user devices 106 receive the search results pages and render the search results page (e.g., execute machine-readable commands that define the search results page) for presentation to users according to their ranking.
[0027] The queries submitted during search operations can be stored in index data 114. Specifically, index data 114 stores queries following search operations by a group or subset of users. Index data 114 also includes data that describes an input context for each query input. An input context of a query input differs from the content described by the query input in that an input context describes the context surrounding the query input. The contexts of each search query are independent of the actual content described by the query input. For example, the context of a search query might include the time of day the query was submitted, a browser and / or device used to submit the query, a geographic location of the user device from which the query was submitted, and other contextual information (e.g.,This includes weather conditions at the geographic location of the user device, events taking place near the geographic location of the user device, and / or other contextual information.
[0028] The push notification system 120 provides push notifications to user devices 106 when users subscribe to receive push notifications related to specific topics, products, or services. The push notification system 120 includes one or more push notification servers 122 and data stores 124. The push notification servers 122 can interact with electronic documents to include a subscription user interface element (such as a button or other call to action) within the electronic document. For example, in an electronic document containing a set of search results, a subscription user interface element can be presented along with the search results in the form of a button, as described in more detail in Fig. 2 described.
[0029] Once a user selects the subscription user interface element presented in an electronic document, the push messaging servers 122 receive contextual data from the user, which can be sent from the user device 106 to the push messaging servers 122 in the form of a data packet. For example, the data packet may have a header (or other section) indicating that the destination of the data packet is the push messaging servers, and may have a payload (or other section) containing the contextual data.
[0030] The contextual data may include the search query used prior to user interaction with the subscriber user interface element to generate the electronic document (e.g., search results page), the geographic location of the user device and the time of day at which the search query was provided, one or more subscriber lists associated with the search query, the specific electronic document, or the location within the specific electronic element where the subscriber user interface element was selected.
[0031] The push notification server 122 contains a list of one or more telephone numbers, each corresponding to a user for a specific subscriber list. A subscriber list can correspond to specific topics, products, or services. For example, if the user has selected the subscription user interface element presented in an electronic document related to televisions (e.g., a search results page for the query "televisions"), a consumer electronics subscriber list can be identified. The push notification server 122 can then use the data store 124 to select a telephone number from the list of telephone numbers for delivery to the user, thus assigning the user to that specific subscriber list.This selected phone number is then associated with the contextual data obtained based on the user's interaction with the subscription user interface element and serves as a unique identifier for the contextual data corresponding to the subscription request. If the user is logged into a search service account, additional contextual data can also be obtained and associated with the uniquely selected user phone number, allowing the push notification system 120 to access this additional contextual information and initiate push notifications using it.
[0032] The push notification server 122 can provide a phone number to the user device 106, which selected the subscription user interface element, to confirm the user's assignment to a specific subscriber list. A message containing the specific phone number can be provided to the user device 106 in the same electronic element where the user selected the subscription user interface element, or in a different electronic element or electronic message (e.g., Short Message Service (SMS) or Multimedia Messaging Service (MMS)). The push notification server 122 can then receive a notification that the user device 106 has communicated confirmation of the user's assignment to the specific subscriber list using the phone number provided to the user device 106.Communication from user device 106 can be a message and can take place over the network, for example, in the form of SMS or MMS. In some implementations, the message provided to user device 106 can request that a specific term or string be included in the communication from user device 106 to the provided telephone number (e.g., requesting that the term "JOIN").
[0033] After the push notification server 122 receives the requested communication with the provided phone number from the user device 106, the push notification server 122 can map the phone number of the user device 106 to the phone number used to confirm the user's assignment to the specific subscriber list. This mapping of the phone number of the user device 106 to the phone number used to confirm the user's assignment to the specific subscriber list establishes a connection between the phone number of the user device 106 and the contextual data corresponding to the initial subscription request.
[0034] The push notification system 120 communicates with the third-party content distribution system 130 to identify specific push messages for delivery to users in one or more subscriber lists. Although a specific user device 106 can be assigned to a subscriber list for which a push message has been identified, the push notification system 120 additionally determines whether the user control information associated with the specific user device 106 (e.g., limiting the number of messages sent to the user device, times when the user allows or blocks messages, etc.), as described in more detail in Fig. As described in section 2, this enables the presentation of the push notification. Furthermore, the user can adjust or change the user control information.
[0035] In some implementations, the push notification system 120 can monitor contextual data for each user's device 106 associated with one or more subscriber lists to determine if and / or when the contextual data meets distribution criteria that must be met for a specific portion of third-party content to be distributed to users. Contextual data for each user can be continuously or periodically received from, or requested by, the push notification system 120, and it can include data such as the geographic location of the user's device 106 in a specific subscriber list (e.g., proximity to a store associated with a subscriber list), user interaction with electronic documents (e.g., a user searching for electronic documents in a search result), and other data.
[0036] A third party providing push notifications, which are distributed by the push notification system 120, can provide distribution criteria. If the distribution criteria are met by certain contextual data of one or more users in a specific subscriber list, the push notification system 120 initiates the distribution of a push notification to those users whose contextual data meets the distribution criteria. The distribution criteria can include, for example, the geographic location of the user's device (e.g., near a specific store), a time of day (which can also include a specific hour or a range of hours, days, weeks, months, etc.), user interactions with electronic documents (e.g.,a user who enters a search query for electronic documents related to the provided search query (where the user has selected the subscription user interface element). The entity can be any suitable entity that distributes third-party content. For example, the entity can be one that distributes emergency or warning information, and the push notifications can distribute this information to users at a specific location associated with that information. In some embodiments, the third party can be an advertiser.
[0037] For example, a third party can specify distribution criteria based on one or more keywords, the use of which is a condition for delivering specific third-party push content to users entering a virtual geographic zone. In this example, a user who physically enters the virtual geographic zone with their mobile device and has contextual data indicating that they previously submitted a search query matching one or more keywords can receive a push notification whose distribution is determined by the keyword. Similarly, the third party can assign different distribution criteria to different parts of the push content, so that different users with different contextual data receive different parts of the push content.This allows third parties to control the distribution of push notifications individually for users from a specific list and to use contextual data beyond geographic location and / or time.
[0038] In some implementations, the push notification system 120 provides a request 126 to the third-party content delivery system 130 to identify and deliver third-party content that will be presented as a push message to one or more of the user's devices. In some implementations, the third-party content is selected in less than one second (or within another specified timeframe) to avoid errors that could be caused by a delayed selection of the third-party content. In some implementations, the selection of the third-party content occurs within a timeframe that ensures the third-party content is delivered within a time window during which the third-party content is relevant to the user. For example, if the push notification system 120 receives data indicating that the user is traveling toward a particular restaurant (e.g.,(at high speed), a push notification informing the user that the restaurant is nearby (or another message) should generally be delivered before the user passes the restaurant to prevent the user from having to turn around to reach the restaurant.
[0039] In some implementations, the third-party content distribution system 130 includes a set of multiple computer devices 132 used to identify and select third-party content. This set of computer devices 132 works together to identify, from a corpus of millions of available third-party content items, a set of third-party content suitable for presentation as a push message or inclusion within the content of a push message. The millions of available third-party content items can be indexed, for example, in a third-party corpus database 134. Each third-party content index input can reference the corresponding third-party content and / or include distribution parameters that define the conditions for distributing the corresponding third-party content. The third-party content distribution system 130 can also specify a bid and / or budget for selecting the specific third-party content.
[0040] Identifying the appropriate third-party content can be divided into several tasks, which are then assigned to different computer devices from the set of multiple computer devices 132. For example, different computer devices in the set 132 can each analyze a different part of the third-party corpus database 134 to identify different third-party content with distribution parameters that match information contained in or provided by the push notification system 120. In some implementations, each particular computer device in the set 132 can analyze a different data dimension (or set of dimensions) and send the results 136 of the analysis back to the third-party content distribution system 130.For example, the results provided by each of the computer devices in the set can identify a subset of third-party content suitable for distribution as a push message and / or a subset of third-party content that has certain distribution parameters or properties.
[0041] The third-party content distribution system 130 aggregates the results 136 received by the set of multiple computer devices 132 and uses the information associated with the aggregated results to select one or more third-party content items to be provided as a response 138 to the push notification system 120. As explained in more detail below, the third-party content distribution system 130 can, for example, select a set of qualifying third-party content based on the result of one or more content selection processes.
[0042] Fig. Figure 2 shows an exemplary screenshot of a subscription process presented on the user device, along with a system diagram of the interaction between a user device 106 and the push notification system 120. A user device 106 can include a display area 202 where electronic documents and other content can be displayed to the user. As explained previously, a search results page can be an electronic document provided to the user to facilitate the search for electronic documents. For example, a user can provide the search query "televisions" in query input 204, and search results 208, 210, and 212 can be provided, which can be electronic documents deemed relevant to the search query, as described previously.In addition to search results 208, 210, and 212, a subscriber user interface element 206 can be provided in the electronic document. However, as previously described, a subscriber user interface element 206 can also be provided in other types of electronic documents (e.g., on a home webpage for a specific product). The push notification system 120 can interact with the electronic documents to provide the subscriber user interface element 206, or the subscriber user interface element 206 can be embedded in the electronic document by its creator.
[0043] Once a user selects the subscriber user interface element 206, the user device can send 214 (e.g., send a data packet) contextual data 216 over the network 102 to the push message delivery servers 122. The contextual data 216 can include the search query used to generate the electronic document (e.g., search results page) prior to the user's interaction with the subscriber user interface element, the geographic location of the user device 106 and the time of day at which the search query was submitted, one or more subscriber lists associated with the search query, the specific electronic document, or the location within the specific electronic element where the subscriber user interface element was selected.
[0044] The push notification server 122 contains a list of one or more telephone numbers, where each telephone number can correspond to a user for a specific subscriber list. The subscriber list can correspond to specific topics, products, or services. For example, if the user has selected the subscription user interface element presented in an electronic document related to "televisions" (e.g., a search results page for the query "televisions"), a subscriber list for consumer electronics can be identified.
[0045] The push notification servers 122 can then send the phone number 226 corresponding to the user for the specific subscriber list, so that it is presented in the subscription message 228 on the user's device 106. In some implementations, the push notification servers 122 can interact with the electronic document presented on the user's device 106 to incorporate the subscription message 228 into the electronic document. For example, after the user selects the subscription user interface element 206, the subscription message 228 can be made available in the display area 202 along with the same search results page. However, it is not necessary for the subscription message 228 to be shown in the same electronic document in which the subscription user interface element 206 was presented, and it can be presented in other or different electronic documents.
[0046] The user of device 106 can then send a message 230 to the provided phone number to confirm their inclusion in the specific subscriber list for receiving push notifications. Communication from device 106 can be a message and can occur over the network, for example, via Short Message Service (SMS) or Multimedia Messaging Service (MMS). In some implementations, the message provided to device 106 may require a specific term or string to be included in the communication from device 106 to the provided phone number.The push notification server 122 can then receive the message 230 from the user device 106 and store the user's telephone number, along with the user's user ID (which may be the individual telephone number provided to the user in the subscription message 228), and assign the user ID and telephone number to the specific subscriber list.
[0047] The push notification system 120 can monitor changing contextual data for each user of the user devices 106 assigned to one or more subscriber lists in order to determine if and / or when the contextual data meets the distribution criteria. Exemplary distribution criteria 232 are in Fig. 2. The distribution criteria for initiating a push notification for a subscriber list can be based on one or more distinct distribution criteria. For example, the distribution criteria for initiating a push notification to a user on the subscriber list might require that the user has selected the subscription user interface element from a search results page provided in response to a search query that matches a keyword in the distribution criteria. A different set of distribution criteria for initiating a push notification to a user on the subscriber list might specify that the time is between 3:00 PM and 5:00 PM and that the user is within a defined area of a particular store (e.g., a store that sells consumer electronics if the subscriber list pertains to consumer electronics).A variety of distribution criteria can be provided by an entity for each subscriber list to which they are assigned. The distribution criteria 232 can be sent to the push notification delivery system 120 234 and stored in the data store 124.
[0048] As previously explained, the push notification system 120 communicates with the third-party content distribution system 130 to identify and deliver third-party content, which is presented as a push notification. The push notification is delivered to the phone numbers corresponding to the user devices 106 in the specific subscriber list. The push notification system 120 can provide the third-party content distribution system 130 with specific user information (e.g., in request 126) that displays the contextual data for each user in a subscriber list.For example, if User A registered in the consumer electronics subscriber list using a subscription element provided when User A submitted a search query for "TVs," and User B registered in the consumer electronics subscriber list using a subscription element provided when User B submitted a search query for "stereo systems," this information can be provided to the third-party content distribution system 130 to select push notification content relevant to the provided search query. This process can also be performed for a subset of users in the subscriber list (e.g., a subset of users in the subscriber list provided the search query "TVs" when they registered in the consumer electronics subscriber list).Based on the previous example, the third-party content distribution system 130 can provide content related to "TV sets" for inclusion in the push notification for user A and content related to "stereo systems" for inclusion in the push notification for user B. More generally, all contextual data for each user in a subscriber list can be provided to the third-party content distribution system 130 to select content for that user's push notification. Using the contextual data to create the push notification allows the push notification delivery system 120 to selectively deliver user-specific push notifications to users in the subscriber list.
[0049] Additionally, a user subscription manager can be provided to the user to manage their subscriptions. For example, a user can choose to activate or deactivate a specific subscription (e.g., indefinitely or for a certain period), set a maximum number of push notifications to receive per period and per subscription (or a total number of push notifications to receive per period), set a time of day to receive push notifications, choose to enable or disable the sending of geographic information from the user's device, and set location parameters for when push notifications should be received. An example user subscription manager is described in Fig. 2 is provided and includes various management options for the user for both List 1 and List 2. Once the user of user device 106 interacts with the user subscription manager, user device 106 sends updated or modified information from the user subscription manager to the push messaging servers 122. If the push messaging servers 122 determine that the contextual distribution information is satisfied, they then determine whether the user control information permits the distribution of the push message. In some cases, the push message may be delayed or canceled if the user control information does not permit distribution.
[0050] For push notifications delivered to users, the push notification delivery servers 122 can collect push notification outcome data for each individual push notification or group of push notifications and store the data in the data store 124. The push notification outcome data is displayed in the sample dataset 224. In some implementations, the push notification delivery servers 122 can determine whether the push notification reached the user device 106 (e.g., whether the phone number associated with user device 106 is reachable), whether the push notification was opened on user device 106, and whether any action was taken in response to the push notification. For example, a push notification for the subscriber list associated with "Skincare Products" might provide a discount on a specific type of soap.If the user of the user device 106, which receives the push message, takes action, for example by interacting with the push message to buy the soap, the push message delivery servers 122 would determine that action has been taken for this particular push message.
[0051] Fig. 3A, Fig. 3B, and Fig. 3C provides sample account interfaces. Different entities can interact with the Push Notification System 120 and provide content to the Third-Party Content Distribution System 130. The Push Notification System 120 can handle entities, as shown in the Fig. 3A and Fig. 3B., provide information relating to the entity's account to show the performance impact of specific push notifications and push notification campaigns. In Fig. For example, interface 300A provides result data from push messages for different push messages, Message 1 and Message 2. As described previously, the result data from push messages can indicate whether the push message reached the user device, whether the push message was opened on user device 106, and whether any action was taken in response to the push message. For example, to determine that the push message reached the user device, a signal can be sent from user device 106 back to the push message delivery system 120 to indicate receipt. In some implementations, to determine that the push message was opened on user device 106, a flag can be set when the push message is opened, and a signal indicating that the push message has been opened can be provided from user device 106 to the push message delivery system 120.Additionally, the user device 106 can send a signal to the push notification system 120 when an item or other content in the push message is selected on the user device 106 (e.g., when the user has selected a discount link provided in the push message). Fig. 3B also includes interface 300B, which provides results data from campaign push notifications, allowing different push notifications to be subdivided into campaigns. For example, Campaign 1 can contain both Message 1 and Message 2. Entities can use the account information to evaluate the performance of different push notifications.
[0052] Additionally, as in Fig. As provided in Surface 300C, entities can select different distribution options for each push message. The options selected by the entity can be communicated to the Push Message Delivery System 120 and the Third-Party Content Distribution System 130 to determine which push messages should be delivered to the various user devices 106 when the contextual distribution criteria are met. As shown in Surface 300C, distribution options can include the geographic range of user devices 106 (e.g., the area code associated with the phone number of the user device 106), requests made on the user devices 106, a time of day at which the push message should be delivered, and a location of the user device 106. A larger or smaller number of distribution options can be included.
[0053] Fig. Section 4 provides a sample user subscription manager interface. As described previously, a user subscription manager can be provided to the user to manage their subscriptions. A sample user subscription manager interface, Section 400, is presented in Fig. 4. User control information is provided, allowing a user to specify user control information for List 1, List 2, and List 3. This information includes selecting whether to activate or deactivate a specific subscription (e.g., indefinitely or for a specific period), setting a maximum number of push notifications to receive per period and per subscription, setting a time of day to receive push notifications, selecting whether to enable or disable the sending of geographic information from the user's device (106), and setting location parameters for when to receive push notifications. A greater or lesser number of subscription management options for user control information can be included. An "advanced" option can also be provided, allowing for additional details regarding user control information.When the push messaging servers 122 determine that the contextual distribution information is satisfied, they then determine whether the user control information permits the distribution of the push message. In some cases, the push message may be delayed or canceled if the user control information does not permit distribution. In some embodiments, the user control information may be applied before or after the selection of the specific push message from the third-party content distribution system 130.
[0054] Fig. Figure 5 shows a flowchart of an exemplary push messaging process 500. Process 500 can be implemented, for example, by the push messaging system 120. In some implementations, the operations of exemplary process 500 can be implemented as instructions stored on a non-volatile, computer-readable medium, where the instructions cause a data processing device to perform the operations of exemplary process 300.
[0055] A request to subscribe to a push notification service is received from a user of a user device 106 (502). As previously described, the user can provide this request by interacting with or selecting a subscribe user interface element presented in an electronic document. For example, the electronic document may be a search results page, and a subscribe user interface element may be presented along with the search results. The subscribe request may be presented, for example, in a data packet that includes data representing a user interaction with a subscribe user interface element presented in an online search results page, as well as contextual data of the user device.The contextual data can be presented in a data package that specifies a search query used prior to user interaction with the subscription user interface element to generate the electronic document.
[0056] Once a user selects the subscriber user interface element, the user's device can send (e.g., send a data packet) contextual data over the network to the push notification servers 122. The contextual data can include the search query used to generate the electronic document (e.g., search results page) prior to the user's interaction with the subscriber user interface element, the geographic location of the user's device 106 and the time of day the search query was submitted, one or more subscriber lists associated with the search query, the specific electronic document, or the location within the specific electronic element where the subscriber user interface element was selected.
[0057] The push notification system 120 selects a specific phone number uniquely assigned to the user based on the received request (504). As previously described, the push notification server 122 can contain a list of one or more phone numbers, each corresponding to a user for a specific subscriber list. A subscriber list can correspond to specific topics, products, or services. For example, if the user selected the subscription user interface element presented in an electronic document related to "televisions" (e.g., a search results page for the query "televisions"), a consumer electronics subscriber list can be identified.The push notification server 122 can then use the data store 124 to select a phone number from the list of phone numbers for provision to the user, in order to assign the user to this specific subscriber list.
[0058] The push notification system 120 sends an initial message presenting visual information on the user device 106 and including the specified phone number (506). The push notification system can send the phone number corresponding to the user for the specific subscriber list to the user device 106, so that it appears in a subscription message (as represented by element 228 in Fig. 2) is presented. In some implementations, the push message delivery servers 122 can interact with the electronic document presented on the user device 106 to incorporate the subscription message into the electronic document. As in Fig. As shown in Figure 2, for example, after the user selects the subscription user interface element 206, the subscription message 228 can be provided in the display area 202 along with the same search results page. However, it is not necessary for the subscription message 228 to be shown in the same electronic document in which the subscription user interface element 206 was presented, and it can be presented in other or different electronic documents.
[0059] A message addressed to the specified telephone number is received (508). The user of the user device 106 can communicate the message to the provided telephone number to acknowledge the user's request to subscribe to the push notification service and to complete the user's inclusion in this specific subscriber list for receiving push notifications. The communication from the user device 106 can be a message and can be made over the network and, for example, in the form of Short Message Service (SMS) or Multimedia Messaging Service (MMS). In some implementations, the message provided to the user device 106 can request that a specific term or string be included in the communication from the user device 106 to the provided telephone number.The push notification server 122 can then receive the message 230 from the user device 106 and store the user's telephone number, along with the user's user ID (which may be the individual telephone number provided to the user in the subscription message 228), and assign the user ID and telephone number to the specific subscriber list.
[0060] An additional message, presenting further visual information, can be selected based on the received message and one or more geographic locations of the user device 106 or a time of day (510). The push notification system 120 can, as previously described, monitor contextual data for each user of the user devices 106 associated with one or more subscriber lists to determine if and / or when the contextual data meets the distribution criteria. The user device 106's contextual data can include a geographic location or a time of day, but other contextual data may also be included. The contextual data can be indexed by the push notification servers 122 and stored in the data store 124.Indexing may involve indexing at least one of the following: a mobile phone number of the user's device, a search query submitted by the user, a time of day the search query was submitted, or a geographic location of the mobile device according to the specified phone number.
[0061] The additional message can be a push notification that is initiated. Once the push notification system 120 determines to deliver a push notification to one or more user devices 106, the push notification system 120 communicates with the third-party content distribution system 130 to identify and deliver the third-party content that will be presented as the push notification. The third-party content includes visual information as part of the push notification. The push notification system 120 can provide the third-party content distribution system 130 with specific user information (e.g., in request 126) that displays the contextual data for each user in a subscriber list. More generally, all contextual data for each user in a subscriber list can be provided to the third-party content distribution system 130 to select content for that user's push notification.Using contextual data to create the push message enables the push notification system 120 to selectively provide user-specific push messages to users in the subscriber list.
[0062] In some implementations, the push notification system 120 can receive distribution criteria from the entity. These criteria define the conditions that must be met for one or more push messages to be distributed to user devices. The distribution criteria may include one or more factors such as the geographic location of the user devices, the time of day, or user interaction with electronic documents associated with a subscriber list. The push notification system 120 can then determine, based on the user device's contextual data, that the distribution criteria have been met. Following this determination, the push notification system 120 can request third-party content from a third-party content distribution system for inclusion in the additional message.After receiving the third-party content from a third-party content distribution system for inclusion in the additional message, the push notification system 120 can distribute the additional message to the user device using the user device's phone number, based on the determination that the distribution criteria are met.
[0063] The additional message is sent to the user device (512). The push message can be delivered to the phone numbers corresponding to the user devices (106) in the specific subscriber list. In some implementations, a user can provide user control information for management when receiving push messages. When the push message delivery servers (122) determine that the contextual distribution information is satisfied based on the user device's context data, the push message delivery system (120) then determines whether the user control information permits distribution of the push message. In some cases, the push message may be delayed or canceled if the user control information does not permit distribution.As previously described, the user control information may include at least one of the following: limiting the number of additional messages sent to the user device or the times at which the user device allows messages to be sent to the user device by one or more servers.
[0064] Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuit arrangements or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or combinations thereof. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., as one or more modules containing computer program instructions encoded on a computer storage medium for execution by a data processing device or for controlling its operation.Alternatively or additionally, program instructions can be encoded on an artificially generated propagating signal, such as a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information for transmission to a suitable receiving device, which is then executed by a data processing device. A computer storage medium can be or contain a computer-readable storage device, a computer-readable storage substrate, a freely addressable or serial access memory array or device, or a combination thereof. Furthermore, a computer storage medium, although not itself a propagated signal, can be a source or destination of computer program instructions programmed into an artificially generated propagated signal.The computer storage medium can also be one or more different physical components or media (e.g., multiple CDs, floppy disks, or other storage devices), or the storage medium can be contained within it.
[0065] The operations described in this specification can be implemented as operations performed by a data processing device on data stored on one or more computer-readable storage devices or received from other sources.
[0066] The term "data processing device" encompasses all types of devices, equipment, and machines for processing data, including, for example, a programmable processor, a computer, a system on one or more chips, or combinations thereof. The device may include special-purpose logic circuits, such as an FPGA (field-programmable general-purpose circuit) or an ASIC (application-specific integrated circuit). In addition to hardware, the device may also include code that creates an execution environment for the corresponding computer program, such as code representing processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination thereof. The device and the execution environment may include various computer model infrastructures, such as...Implement web services, as well as distributed computing and spatially distributed computing infrastructures.
[0067] A computer program (which may also be called a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and can be provided in any form, such as a standalone executable program or as a module, component, subroutine, object, or any other unit suitable for use in a computer environment. A computer program may, but need not, correspond to a file in a file system. A program may be stored in a portion of a file containing other programs or data (such as one or more scripts stored in a markup language document), in a single file dedicated to the program itself, or in multiple coordinated files (such as files containing one or more modules, subprograms, or code snippets).A computer program can be deployed and run on one computer or on multiple computers located at one or more sites and connected to each other via a communication network.
[0068] The processes and logical sequences described in this specification can be executed by one or more programmable processors, which run one or more computer programs to perform actions by processing input data and generating output data. Alternatively, the processes and logic sequences can be executed by a specialized logic circuit, such as an FPGA (Functional Processing Assembly Device) or an ASIC (Application-Specific Integrated Circuit), and the device can be implemented accordingly.
[0069] Processors suitable for executing a computer program include, for example, both general-purpose and specialized microprocessors, as well as all types of single or multiple processors found in any type of digital computer. Generally, a processor receives instructions and data from read-only memory or main memory, or both. The essential components of a computer are a processor for performing actions in accordance with instructions, and one or more storage devices for storing instructions and data. Typically, a computer includes one or more mass storage devices for storing data, such as magnetic, magneto-optical, or optical hard drives, or is operationally coupled to receive data from or transfer data to them. However, it is not essential for a computer to have these devices. Furthermore, a computer may also include, among other things...It can be integrated into another device, such as a mobile phone, personal digital assistant (PDA), portable audio or video player, game console, GPS receiver, or portable storage device (e.g., USB flash drive). Media suitable for storing computer program instructions and data include all types of solid-state storage, media, and storage devices, including semiconductor memory elements such as EPROM, EEPROM, and flash memory devices; magnetic hard disks, such as internal or removable disks; magneto-optical hard disks; and CD-ROM and DVD-ROM drives. The processor and memory can be supplemented by or integrated into a special logic circuit.
[0070] To enable user interaction, embodiments of the item described in this specification can be implemented on a computer with a display device, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, which displays information to the user, as well as a keyboard and a pointing device, such as a mouse or trackball, with which the user can input information into the computer. Furthermore, other devices can be used to enable user interaction; for example, feedback to the user can be any type of sensory feedback, such as visual, auditory, or tactile feedback; likewise, user input can be received in any form, including, but not limited to, auditory, verbal, or tactile.Furthermore, a computer can interact with a user by sending documents to a device and receiving documents from a device used by the user, for example by sending web pages to a web browser on the user's client device in response to requests received from the web browser.
[0071] The embodiments of the subject matter described in this specification can be implemented in a computer system that includes a backend component, such as a data server, or a middleware component, such as an application server, or a frontend component, such as a client computer with a graphical user interface, or any combination of one or more of said backend, middleware, or frontend components, or a web browser, through which a user can interact with an implementation of the subject matter described in this specification. The components of the system can be interconnected by any form or medium of digital data communication, such as a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g.,ad hoc peer-to-peer networks).
[0072] The computing system can include a client and a server. A client and server are generally located remotely and typically interact via a communication network. The client-server relationship arises from computer programs running on the respective computers, which establish a client-server relationship. In some implementations, a server transmits data (e.g., an HTML page) to a client device (e.g., to display data to and receive user input from a user interacting with the client device). Data generated on the client device (e.g., a result of user interaction) can be received by the user device on the server.
[0073] Although this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of inventions or claims, but rather as descriptions of specific features of particular embodiments of particular inventions. Certain features described in this specification in the context of the different embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented in several embodiments or in any suitable combination thereof.Furthermore, in some cases one or more features of a claimed combination can be extracted from the combination, even if the features are described above as functioning in certain combinations or are even claimed as a combination; in addition, the claimed combination can be referred to a partial combination or a variation of a partial combination.
[0074] Similarly, while the processes in the drawings are depicted in a specific sequence, this should not be interpreted as a requirement that such processes must be performed in the specific sequence shown, or in a sequential order, or that all depicted processes must be performed to achieve desired results. Multitasking and parallel processing can be advantageous under certain circumstances. Furthermore, the separation of different system components in the embodiments described above should not be considered necessary in all embodiments. It is also understood that the described program components and systems can generally be integrated into a single software product or combined into several software products.
[0075] Consequently, certain embodiments of the subject matter have been described. Further embodiments are within the scope of the following claims. Thus, in some cases, the actions specified in the claims can be performed in a different sequence and still achieve the desired results. Additionally, for example, the processes illustrated in the accompanying figures do not necessarily require the specific sequence or sequential order shown to achieve the desired results. In certain implementations, multitasking and parallel processing may be advantageous.
[0076] In situations where the systems described here may collect personal information about users or use personal data, users may be given the option to configure whether programs or functions collect user information (e.g., information about a user's social network data, social actions or activities, occupation, user preferences, or current location), or whether and / or how content may be received from the content server that may be more relevant to the user. Additionally, certain data may be processed in one or more ways before being stored or used, so that personally identifiable information is removed.For example, a user's identity can be handled in such a way that no personally identifiable information can be determined for the user, or a user's geographic location can be generalized by retrieving location information (such as a city, postal code, or state) so that a specific location of a user cannot be determined. This allows the user to control how information about them is collected and used by a content server.
Claims
[1] Method of delivering push notifications, comprising: Receiving, from a user device, a request to subscribe to a push messaging service; selecting, by one or more servers, a particular telephone number uniquely associated with the user based on the received request, wherein the particular telephone number is different from a telephone number of the user; Sending, to a user device and in response to receiving the request, a first message presenting visual information on the user device and including the particular telephone number; Receiving, from the user device and by the one or more servers, a second message directed to the particular telephone number; selecting, by the one or more servers, an additional message presenting additional visual information on the user device based at least in part on the message received by the user device and one or more of a geographic location of the mobile device or a time of day; and Sending the additional message to the user device. [2] The method of claim 1, wherein receiving a request to subscribe to a push messaging service comprises receiving a data packet including data representing a user interaction with a subscription user interface element presented in an online search results page and user device context data. [3] The method of claim 2, wherein receiving a data packet containing context data includes receiving a data packet specifying a search query used to generate the online search results page prior to user interaction with the subscription user interface element. [4] A method according to any one of the preceding claims, wherein receiving a second message directed to the particular telephone number comprises receiving a second message confirming the request to subscribe to the push messaging service, the second message including a telephone number of the user device. [5] A method according to any one of the preceding claims, further comprising: Obtaining distribution criteria that specify conditions that must be met for one or more push messages to be distributed to user devices, wherein the distribution criteria include one or more of geographic location data of the user devices, a time of day, or user interaction with electronic documents associated with a subscriber list; Determine, based on context data of the user device, that the distribution criteria are met; and Distributing, using the user device's telephone number, the additional message to the user device based on determining that the distribution criteria are met. [6] The method of claim 5, further comprising: Requesting third-party content from a third-party content distribution system for inclusion in the additional message; and Receiving the third-party content from the third-party content distribution system for inclusion in the additional message. [7] A method according to any one of claims 5 or 6, further comprising: Determining that the user device will receive the additional message, wherein the determination is made based on user control information including at least one of limiting the number of additional messages sent to the user device or the times at which the user device allows messages to be sent to the user device by the one or more servers. [8] The method of any preceding claim, further comprising indexing context data associated with the user having the particular telephone number, including indexing at least one of a mobile phone number of the user device, a search query submission by the user, a time of day at which the search query was submitted, or a geographic location of the mobile device according to the particular telephone number. [9] A computer storage medium encoded with a computer program, the program comprising instructions which, when executed by a data processing device, cause the data processing device to perform operations comprising a method according to any one of claims 1 to 8. [10] System comprising: a processor; and a computer-readable medium coupled to the processor and having stored thereon instructions that, when executed by the processor, cause the processor to perform operations comprising a method according to any one of claims 1 to 8.
Citation Information
Patent Citations
Method and device for the automatic transmission of information
DE102007025020A1
Provisioning subscriptions to user devices
US20150163675A1
