Patent application number | Description | Published |
20080275864 | ENABLING CLUSTERED SEARCH PROCESSING VIA TEXT MESSAGING - Methods and apparatus for searching data, grouping search results into categories that are ordered according to search relevance, and reviewing the search results via text messaging. In one embodiment, a search term is submitted via a search request text message to a short code for a search service. The search service searches for content based on the search term and context data, such as location of a submitting client device. The search results are clustered into categories and ranked by relevance to the search term and context within each category. The categories are also ranked relative to each other. The most relevant search result from the most relevant category is transmitted in an initial result text message, which also includes instructions to access additional results via subsequent text messages. Each result text message also includes a link to a web page of categorized search results for display in a browser. | 11-06-2008 |
20090052359 | Mobile carrier capability - A network device and method are directed towards determining whether a carrier gateway is likely to be associated with a mobile carrier service. Content/service providers receive request for content along with a network address of a gateway device providing the request. If the network address is unknown, the content/service provider may be provided to a new gateway identifier that is configured to determine a likelihood that the gateway device is configured to provide services to mobile devices. Based, in part, on the determined likelihood, a gateway device's capability may also be determined, such that the content/service provider may then select to provide a response, degrade a response, or reject a request for the content, service, or the like. | 02-26-2009 |
20090055398 | RETRIEVING MOBILE USER CONTEXT INFORMATION USING TOKENIZED VIRTUAL DICTIONARIES - A network device, system, and method are directed towards providing user context information to improve relevancy of a search result, or other content, provided to a user. A context service may provide a common retrieval interface (CRI) that reflects the capabilities available to a content service application (CSA). The CSA may provide limited information about the user to the context service and may specify user context information being sought. The context service provides at least some of the known user information to various context analysis services to request the user context information, and receives back user context information along with a confidence level indicating a percentage of confidence the context analysis service may have for the results. The context service then selects user context information based on weighted confidence levels, and provides the results to the CSA, to improve the relevancy of information provided to the user. | 02-26-2009 |
20090069037 | SMS SHORTCODE ALLOCATION - A system, apparatus, and method are directed towards managing short code allocation policies across a plurality of different carriers for multiple applications. Each carrier provides to a centralized routing service a short code policy that includes an extension allocation policy. The extension allocation policy may specify whether the extensions are allocated based on a dynamical recycle allocation, a range recycle allocation, a pass-through allocation, or a re-usekey based allocation policy, or other mechanism. When a message is sent from an application, a carrier is determined to send the message to a destination mobile device. The carrier's short code policy, including the extension allocation policy, is then used to select how to allocate and/or re-allocate a short code and extension for use with the message. The message may then be modified to include the selected short code and extension, and is then sent using the determined network carrier. | 03-12-2009 |
20090082042 | SMS SPAM CONTROL - A system, apparatus, and method are directed towards managing abuse of text messages through controls on messages sent by an application to a mobile device (e.g., MT text messages). MT text messages sent from a defined application are intercepted by a Text Message SPAM Control Service (TMSCS). Various controls are determined for the sending application based on the application, level of user control on contents of the message, the user requesting the message to be sent (if any), and/or a destination address for the message. These controls may then be used in various combinations and/or various levels of constraint to determine whether to block transmission of the message to a destination mobile device. By monitoring messages from the application, abuse of the application may be minimized. | 03-26-2009 |
20090106770 | SMS SESSIONING - A system, apparatus, and method are directed towards managing communications with global applications through message handlers. The message is received by a first message handler that is local to the client device. The first message handler determines if the message is to be forwarded to a global application, and if so, forwards the message to a second message handler, which is configured to be local to the global application. The second message handler forwards the message and receives a response from the global application. The second message handler may then generate a session identifier that is useable to manage its session data for the message/response. The session identifier is sent to the first message handler in lieu of sending the session data, such that the two message handlers manage separately their own session data for the session. The session identifier is useable to relate the separately managed session data sets. | 04-23-2009 |
20090109978 | Application interface for global mobile message delivery - A device, system, and method are directed towards communicating mobile information over a network. A mobile message (MM) is generated by an Internet Protocol (IP) enabled application interface. The MM may include advertising information. The MM is received at a routing server and comprises a destination phone number and/or advertising information. If the MM is determined to be locally processed, the routing server selectively routes the MM to a destination carrier associated with the destination phone number. If the MM is determined to be remotely processed, the MM is recursively forwarded until the MM reaches another routing server associated with the destination phone number. The other routing server is configured to selectively route the MM to the destination carrier. A response MM may be received at a boundary routing server. The response MM may be sent to the API if at least a portion of the response MM matches information associated with the MM. | 04-30-2009 |
20090138563 | DYNAMICAL ROUTING FOR TEXT MESSAGING - Routing text messages. A mobile message (MM) is received from an application program or other message source, and includes a destination identifier, such as a phone number. Based on the destination identifier, a routing server determines whether the MM is to be locally routed to a destination carrier, or forwarded to a remote server that provides access to the destination carrier. For local routing, the routing server determines a channel to the carrier based on predefined carrier information, the destination user information, and the carrier gateway dynamic information. The predefined carrier information indicates predicted availability or reliability of each of a plurality of channels to the carrier. The destination user information indicates availability of the destination user to receive messages, and includes a destination user criterion for determining one of the channels. The carrier gateway dynamic information indicates current and statistical traffic information for each of the channels. | 05-28-2009 |
20120184308 | APPLICATION INTERFACE FOR GLOBAL MESSAGE DELIVERY - A device, system, and method are directed towards communicating mobile information over a network. A mobile message (MM) is generated by an Internet Protocol (IP) enabled application interface. The MM may include advertising information. The MM is received at a routing server and comprises a destination phone number and/or advertising information. If the MM is determined to be locally processed, the routing server selectively routes the MM to a destination carrier associated with the destination phone number. If the MM is determined to be remotely processed, the MM is recursively forwarded until the MM reaches another routing server associated with the destination phone number. The other routing server is configured to selectively route the MM to the destination carrier. A response MM may be received at a boundary routing server. | 07-19-2012 |