Centralized service for distributed service deployments

• US 9,350,819 B2
• Filed: 12/14/2011
• Issued: 05/24/2016
• Est. Priority Date: 07/21/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Bhagavatula, Girija, Downes, Aidan, Eydelman, Vadim, Garg, Neeraj, Lakshminarayanan, Anand, Mehta, Bimal K., Rao, Deepak, Thatte, Rahul
• Primary Examiner(s): Tolentino, Roderick
• Application Number:
  US13/325,995
• Publication Number:
  US 20130024690A1
• Time in Patent Office: 1,623 Days
• Field of Search: 726 26- 30
• US Class Current: 1/1
• CPC Class Codes: H04L 2209/76 Proxy, i.e. using intermediary entity to perform cryptographic operations network architectures or network communication protocols using hop-by-hop encryption H04L63/0464
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 9/3268 using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]

Abstract

A centralized service communicatively links an application provider to a plurality of different message forwarding services. The centralized service receives a request and authenticates the application provider associated with the request. Further, the centralized service delivers a message embodied by the request to a first message forwarding service with a first protocol and/or to a second message forwarding service with a second protocol different than the first protocol.

Claims

1. A centralized service for communicatively linking a plurality of application providers to different device-specific versions of a plurality of provider-specific applications via a plurality of different message forwarding services, the central service comprising:

a logic subsystem including one or more processor devices; and

a data-holding subsystem including one or more storage devices holding a plurality of digital certificates and associated cryptographic keys for authenticating requests, and the one or more storage devices holding instructions executable by the logic subsystem, the instructions including;

instructions to receive a request from a particular application provider of the plurality of application providers to communicate with a plurality of different device-specific versions of a particular provider-specific application provided by the particular application provider executing on different types of client computing devices via the plurality of different message forwarding services;

instructions to authenticate the request by matching the provider identifier to a digital certificate and a cryptographic key associated with its digital certificate;

instructions to authenticate the request by matching the application identifier to a digital certificate and a cryptographic key associated with its digital certificate;

and instructions to deliver, responsive to the request being authenticated, a message embodied by the request to one or more of the plurality of different device-specific versions of the particular provider-specific application via one or more different message forwarding services identified by the request, wherein the message is delivered to a first of the plurality of different message forwarding services arranged to deliver the message to a first device-specific version of the particular provider-specific application executing on a first type of computing device using a first protocol and to a second of the plurality of different message forwarding services arranged to deliver the message to a second device-specific version of the particular provider-specific application executing on a second type of computing device using a second protocol that is different than the first protocol.

2. The centralized service of claim 1, wherein each application provider of the plurality of application providers is configured to identify the first or second of the plurality of different message forwarding services as an intended message forwarding service.

3. The centralized service of claim 2, wherein a service identifier embodied by the request identifies the intended message forwarding service.

4. The centralized service of claim 1, wherein the plurality of different message forwarding services are remote services, and wherein the remote services forward the message to a particular mobile computing device.

5. The centralized service of claim 1, wherein the plurality of different message forwarding services are local services, and wherein the local services forward the message to a particular mobile computing device.

6. The centralized service of claim 1, wherein the message is a push notification message.

7. A method for a computing device to process a push notification, the method comprising:

receiving a request from an application provider to push a push notification to a plurality of different device-specific versions of a provider-specific application executing on different types of computing devices, the application provider being one of a plurality of different application providers for which the computing device is configured to receive the request, each of the plurality of different application providers associated with a provider identifier and a corresponding digital certificate;

authenticating the request by matching the provider identifier to a digital certificate and a cryptographic key associated with its digital certificate and by matching an application identifier to a digital certificate and a cryptographic key associated with its digital certificate;

processing an authenticated request to create a formatted push notification; and

sending the formatted push notification to a corresponding device-specific version of the provider-specific application via a corresponding message forwarding service, the corresponding message forwarding service being one of a plurality of different message forwarding services, one or more of the plurality of different message forwarding services being configured to push the formatted push notification using a different format or a different transport protocol than another of the plurality of different message forwarding services.

8. The method of claim 7, wherein the request includes a provider identifier, a service identifier, an application identifier, and a payload, and wherein the formatted push notification includes the payload unmodified from the request.

9. The method of claim 8, wherein authenticating the request includes matching the provider identifier associated with the request to a digital certificate, wherein the provider identifier identifies the application provider that sent the request.

10. The method of claim 9, wherein authenticating the request includes matching the application identifier associated with the request to a digital certificate, wherein the application identifier identifies a particular application associated with the request.

11. The method of claim 10, wherein the request is further authenticated via a cryptographic key that is associated with the digital certificate.

12. The method of claim 7, wherein processing the authenticated request includes retrieving a task corresponding to an authenticated request from a task pool, the task pool including a plurality of tasks stored within a data-holding subsystem of the computing device.

13. The method of claim 12, wherein each of the plurality of tasks further includes a connection object.

14. The method of claim 13, wherein the connection object includes data pertinent to establishing a communicative connection with the corresponding message forwarding service, the pertinent data including one or more of a digital certificate, a server identifier, a port identifier, and a uniform resource locator.

15. The method of claim 7, wherein processing the authenticated request further includes matching a service identifier of the request to the corresponding message forwarding service, wherein the service identifier indicates a particular format for the formatted push notification, the particular format compatible with the corresponding message forwarding service.

16. The method of claim 15, wherein the formatted push notification is sent to the corresponding message forwarding service using a particular transport protocol identified by the service identifier, the particular transport protocol compatible with the corresponding message forwarding service.

17. The method of claim 7, further comprising sending a response message to the application provider indicating a status of the request.

18. A system for authenticating a request for forwarding a push notification, the system comprising:

a logic subsystem including one or more processor devices; and

a data-holding subsystem including one or more storage devices holding instructions executable by the logic subsystem, the instructions including;

instructions to receive the request from an application provider to push a push notification to a plurality of different device-specific versions of a provider-specific application executing on different types of client computing devices, the request including a provider identifier, an application identifier, a service identifier, and a payload, the application provider being one of a plurality of different application providers for which the system is configured to receive the request;

instructions to authenticate the request by matching the provider identifier to a digital certificate and a cryptographic key associated with the digital certificate;

instructions to authenticate the request by matching the application identifier to a digital certificate and a cryptographic key associated with the digital certificate;

instructions to retrieve a task corresponding to the authenticated request from a task pool, wherein the task includes connection data that establishes a communicative connection with a message forwarding service;

instructions to add the task to a task queue;

instructions to process the task to create a push notification with a particular format identified by the service identifier; and

instructions to send the formatted push notification to a corresponding device-specific version of the provider-specific application via a corresponding message forwarding service using a particular transport protocol identified by the service identifier, wherein the formatted push notification includes the payload of the request, the corresponding message forwarding service being one of a plurality of different message forwarding services, one or more of the different message forwarding services being configured to push the formatted push notification using a different format or a different transport protocol than another of the plurality of different message forwarding services.