Abstract:
The claimed subject matter provides a method for securing a partner-enabled web service. The method includes receiving a request to access the partner-enabled web service. The request is received from a browser client for a partner application. The browser client is associated with a user. Additionally, the method includes determining that the user is authorized to access the partner application. The method further includes generating a token that associates the user with the partner application. Also, the method includes sending the token to the browser client.
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.
Abstract:
An application feature store may be integrated with an application. The feature store may be accessed by a user through a feature storefront hosted within the application. The user may search the feature store for additional desired features available for the augmentation of the productivity application.
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:
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:
In one example embodiment, a code segment may be embedded in a web page by a web page publisher, and the code segment may be executed at least in part by a user computing platform. Information related to one or more web applications may be provided to the user computing platform at least in part in response to the user computing platform executing the code segment.
Abstract:
A platform for customized rendering of markup language (ML) documents into a document in a device specific language that is subsequently provided for display by a target remote device. A rendering context for the target remote device and an ML document is received by the platform, which performs processes that can paginate and fully render pages that are subsequently delivered for display by the target remote device. A post-rendering process may also be provided to perform additional processing of media items for the device specific language document. This additional processing may include including links to or embedding media items in pages of the device specific language document. The remote device can be arranged as a client device that provides for wired and/or wireless communication over a network.
Abstract:
Among other things, one or more techniques and/or systems are provided for facilitating the completion of a user task. That is, user intent (e.g., intentions of a user to perform a user task) may be identified. The user intent may comprise an entity (e.g., a movie entity) and/or an action (e.g., an order movie tickets action) that the user wants to perform on the entity. A provider list may be created based upon one or more providers capable of performing the action on the entity (e.g., a movie application may be capable of performing the order movie tickets action on the movie entity). Providers may be dynamically selected for inclusion within the provider list at run-time. For example, an open market of providers may be maintained (e.g., providers may be added, removed, and/or updated over time), such that providers may be selected from the open market to complete user tasks.
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.