Abstract: Managing data collection for one or more scheduled alert messages. A primary or backup poller manager coordinates any number of poller services to access content and generate the alert messages. At a predefined period the poller manager is informed that an existing or new poller service is available for work. The poller manager provides a query to the poller service to access content in which one or more users have expressed an interest. Querying for a large number of users can be subdivided among the poller services. The poller service can also automatically expand the query if it yields insufficient content. The poller service generates the alert messages for the interested users and informs the poller manager when done. A change in content can be used to generate or update alert messages before their scheduled delivery. The poller manager prioritizes processing with a quality of service level.

Abstract: Enabling a user of a device, such as a wired or wireless device, that is associated with a telephone number to communicate text messages with another user of another device that is not associated with a telephone number (or the telephone number is unknown to the sender). Although the other user's telephone number is not known or does not exist, the other user is associated with a user identifier for a user community that is assigned a Common Short Code (CSC). The text message includes a source telephone number (sender/user's device telephone number) and a destination number (the CSC for the other user/recipient's user community). The content of the text message includes a user identifier, where the identifier indicates the particular other user within the user community. A server employs the CSC to determine the user community and the identifier to determine the particular user in the determined community that is the intended recipient of the text message.

Abstract: An architecture for providing an alert message based on content that may be received as an event based feed or a time based feed in one or more formats. The architecture includes a data collection processing module for normalizing the content into a predefined data structure, and indexing the content for processing large amounts of content according to selected characteristics. A matching engine employs user queries to associate the event based content with one or more users who have indicated an interest in receiving alert messages associated with selected content. The matching engine also generates the corresponding alert messages. A poller fetches content on behalf or users at a predefined period and generates a corresponding alert message. A delivery interface determines which alert messages are to be sent immediately and which alert messages are to be scheduled for later delivery. The architecture is mirrored for scalability and backup.