Client cloud synchronizer

• US 10,528,625 B2
• Filed: 06/21/2017
• Issued: 01/07/2020
• Est. Priority Date: 06/21/2017
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Fink, David William, Davis, Miles Colin John, Kataria, Lalit, Locquet, Fabien, Zaharia, Meidad, Yanai, Omer, Nimrod, Reuven
• Primary Examiner(s): Dennison, Jerry B
• Application Number:
  US15/628,777
• Publication Number:
  US 20180373811A1
• Time in Patent Office: 930 Days
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: H04L 45/507 Label distribution
• CPC Class Codes: H04W 56/0015 one node acting as a reference for the others

Abstract

Client and cloud synchronization may be provided. First, a request may be received. Then the request may be labeled with a package metadata tag yielding a labeled request. The package metadata tag may identify a package assigned to a client device corresponding to the request. Next, the labeled request may be routed to a version of a first cloud service component based on the package metadata tag. The labeled request may then be routed from the version of the first cloud service component to a version of a second cloud service component based on the package metadata tag.

Claims

1. A method comprising:

receiving a request;

labeling the request with a package metadata tag yielding a labeled request, wherein the package metadata tag identifies a package assigned to a client device corresponding to the request, wherein labeling the request with the package metadata tag comprises;

performing a look up in a client database for identification information identifying the client device, the identification information being received in the request, the client database comprising a plurality of packages, each of the plurality of packages comprising a combination of client software components and a combination of cloud software components corresponding to the combination of client software components, and rules for assigning the plurality of packages, and

identifying the package assigned to the client device from the client database;

routing the labeled request to a version of a first cloud service component based on the package metadata tag; and

routing the labeled request from the version of the first cloud service component to a version of a second cloud service component based on the package metadata tag.

2. The method of claim 1, wherein receiving the request comprises receiving the request from the client device.

3. The method of claim 1, wherein the package comprises at least one artifact for the client device, the first cloud service component, and the second cloud service component.

4. The method of claim 1, wherein routing the labeled request to the version of the first cloud service component comprises routing the labeled request to the version of the first cloud service component by a first routing system.

5. The method of claim 1, wherein routing the labeled request to the version of the first cloud service component based on the package metadata tag comprises:

querying a rules engine based on the package metadata tag; and

receiving from the rules engine an identifier of the version of the first cloud service component.

6. The method of claim 1, wherein routing the labeled request from the version of the first cloud service component to the version of the second cloud service component comprises routing the labeled request from the version of the first cloud service component to the version of the second cloud service component by a second routing system.

7. The method of claim 1, wherein routing the labeled request from the version of the first cloud service component to the version of the second cloud service component comprises:

querying a rules engine based on the package metadata tag; and

receiving from the rules engine an identifier of the version of the second cloud service component.

8. The method of claim 1, further comprising provisioning the client device with at least one artifact based on the package assigned to the client device.

9. The method of claim 8, wherein provisioning the client device with the at least one artifact comprises provisioning the client device with the at least one artifact comprising a client device application.

10. The method of claim 8, wherein provisioning the client device with the at least one artifact comprises provisioning the client device with the at least one artifact comprising a client device component.

11. The method of claim 1, further comprising assigning the package assigned to the client device based on a hardware type corresponding to the client device.

12. The method of claim 1, further comprising assigning the package assigned to the client device based on a community corresponding to the client device.

13. A system comprising:

a memory storage; and

a processing unit coupled to the memory storage, wherein the processing unit is operative to;

receive a request;

label the request with a package metadata tag yielding a labeled request, wherein the package metadata tag identifies a package assigned to a client device corresponding to the request, wherein the processing unit being operative to label the request with the package metadata tag comprises the processing unit being operative to;

perform a look up in a client database for identification information identifying the client device, the identification information being received in the request, the client database comprising a plurality of packages, each of the plurality of packages comprising a combination of client software components and a combination of cloud software components corresponding to the combination of client software components, and rules for assigning the plurality of packages; and

identify the package assigned to the client device from the client database; and

route the labeled request to a version of a first cloud service component based on the package metadata tag.

14. The system of claim 13, wherein the processing unit being operative to receive the request comprises the processing unit being operative to receive the request from the client device.

15. The system of claim 13, wherein the package comprises at least one artifact for the client device, the first cloud service component, and the second cloud service component.

16. The system of claim 13, wherein the processing unit being operative to route the labeled request to the version of the first cloud service component based on the package metadata tag comprises the processing unit being operative to:

query a rules engine based on the package metadata tag; and

receive from the rules engine an identifier of the version of the first cloud service component.

17. A non-transitory computer-readable medium that stores a set of instructions which when executed perform a method comprising:

receiving a request;

labeling the request with a package metadata tag yielding a labeled request, wherein the package metadata tag identifies a package assigned to a client device corresponding to the request, wherein labeling the request with the package metadata tag comprises;

performing a look up in a client database for identification information identifying the client device, the identification information being received in the request, the client database comprising a plurality of packages, each of the plurality of packages comprising a combination of client software components and a combination of cloud software components corresponding to the combination of client software components, and rules for assigning the plurality of packages; and

identifying the package assigned to the client device from the client database; and

routing the request to a version of a first cloud service component based on the package metadata tag.

18. The non-transitory computer-readable medium of claim 17, wherein receiving the request comprises receiving the request from the client device.

19. The non-transitory computer-readable medium of claim 17, wherein labeling the request with the package metadata tag comprises labeling the request with the package metadata tag wherein the package comprises at least one artifact for the client device, the first cloud service component, and the second cloud service component.

20. The non-transitory computer-readable medium of claim 17, wherein routing the labeled request to the version of the first cloud service component based on the package metadata tag comprises:

querying a rules engine based on the package metadata tag; and

receiving from the rules engine an identifier of the version of the first cloud service component.