Abstract:
A bidirectional mapping is established between network content and application programs, based on declarations at both the network content and at the application. Additionally, bidirectional mapping can provide for deep links, which can associate specific network content with a specific presentation of data in an application program. The identification format for such deep links can conform to a predetermined standard or it can be custom implemented according to a format declared either as part of the network content or the application program. The bidirectional mapping is then utilized by a lookup service to provide functionality to a third-party entity. The lookup service can identify, to the entity, application programs associated with network content specified by that entity and network content associated with application programs specified by that entity.
Abstract:
A device, system, and method are directed towards facilitating monetization of mobile devices. A click action server determines click actions that are to be sent to a client device based on one or more factors. The click actions are sent to the client device as links. An action handler receives requests indicating a selected action, and facilitates the performance of the action.
Abstract:
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.
Abstract:
A network device, system, and method are directed towards enabling a determination for page size tailoring of content based, in part, on estimating of effects of processes applicable to preparing the content for use on a specified mobile device. Before performing the processes on the content, an estimation of the effects of the configuring processes may be determined. If the estimated content size is determined to be too large for the specified mobile device's memory footprint, page tailoring techniques may be applied to the content. Such page tailoring techniques may include stretching the content across a plurality of files, discarding a portion of the content, reducing portions of the content, or the like. Various processes may then be applied to the content to configure it for use on the specified mobile device.
Abstract:
The need for upload security arises during content sharing between users in communication link with each other and a server. In one embodiment, providing the upload security involves the server identifying a mobile device that sends an upload message destined to a user. Providing the upload security further involves the server accessing opt-in parameters predetermined by the user, determining if the identity of the sending mobile device is included in the opt-in parameters, and, if so, allowing the upload to the user's account, otherwise blocking the upload. The opt-in parameters include the identity of mobile devices that are authorized by the user to upload data to the user's account. In one embodiment, the communication link includes a wireless carrier network with capability for security screening of the upload message before it reaches the server based on the identity of the wireless carrier network.
Abstract:
The invention enables one or more agents to gather information from at least one server on a network and automatically provide this information to an inbox on a server and then providing it to an inbox on a mobile device if a wireless connection to the mobile device is available. A server agent facility provides for preprocessing requests for information from the mobile device, including, collecting the information out of band, filtering the collected information, and packaging the information for delivery in a format suitable for the mobile device. A server agent within the server agent facility may actively collect the information based on a variety of factors, including but not limited to, time, event(s), user profile, mobile device profile, request(s), alert(s), and historical behavior.
Abstract:
A method and apparatus tracks and blocks content requested by a first remote device for forwarding over a network to a second remote device. For a given content item, one or more usage identities are tracked. Usage identities may include any combination of one or more of a source identity, a content identity, and/or a destination identity. One or more thresholds associated with the tracked usage identities are applied to determine whether a request to forward content should be blocked; a threshold is a limit on the number of times a content item having a particular usage identity may be forwarded within a time period. Misuse of content-forwarding messaging services by spammers and the like may thereby be discouraged. In one embodiment, the invention may be employed as part of a content clipping service for forwarding content to mobile devices by way of SMS or another mobile messaging technology.
Abstract:
Embodiments of the invention are directed to determining a universal device identifier (UDID) for a client device, based on multiple service-dependent identifiers (SDIDs) used by client applications, websites, or other services to identify the client device, SDID types are prioritized with pre-assigned weights. A received SDID causes a single database read to access all other SDIDs, and any existing UDID(s) associated with the client device. A final UDID is created or selected based on the SDID weights. The database is updated in a sequence that enables self recovery of a prior UDID in case of database error during update. First, any non-selected UDID records are updated with the final UDID. Next, lower weighted SDID records are updated. The final UDID record is updated. The highest weighted SDID record is updated last, to preserve the prior UDID as long as possible in case of update error, which aborts the remaining update.
Abstract:
A device, system, and method are directed towards employing a beacon to sniff a network metric. When a mobile device requests content from a content server, the content server obtains a beacon be a Uniform Resource Locator (URL) that encodes information about the mobile device, a network carrier, a time the beacon is generated, a connection type, or the like. The beacon may further provide a link to a small image, file, or the like. The beacon may be included with the response to the mobile device. When the mobile device receives the response, it may send a request for content using the beacon's link. A time that the request for the beacon's content is received by a server is recorded. A reverse round trip time (RRTT) may then be determined based on the encoded information and the time the beacon is received.
Abstract:
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.