A method for providing a roaming service to a first client may be provided. The first client may be associated to at least one application service running on an associated virtual machine as a Cloud service via a primary route between the first client and the at least one application service. The method may comprise providing a first agent on the first client, and providing an alternative route to the primary route between the first client and the at least one application service utilizing a second agent running on a second client. Thereby, the alternative route is based on a set of preferences submitted by the first client.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for providing a roaming service to a first client, the first client being associated to at least one application service running on an associated virtual machine as a Cloud service via a primary route between the first client and the at least one application service, the method comprising: providing a first agent on the first client; and providing an alternative route to the primary route between the first client and the at least one application service utilizing a second agent running on a second client, wherein the alternative route is based on a set of preferences submitted by the first client, wherein a first server running the associated virtual machine executing the application service also runs a roaming daemon, the roaming daemon using a profile comprising at least one of a trusted vendor list, a reserved computation volume, an engagement type, a billing threshold, and a security level, and wherein different servers may be selected, according to the profile, to establish the alternative route.
A roaming service for cloud applications allows a client device to maintain connectivity even when the primary network route is poor. It works by setting up an alternative route through a second client device acting as a proxy. The first client has an agent installed. The service uses a roaming daemon on the server hosting the application. This daemon selects the alternative route based on preferences (service level constraints) defined by the first client. The profile includes factors like trusted vendors, reserved compute resources, engagement type, billing limits, and security level. Different servers can be chosen to establish the alternate route based on the profile.
2. The method according to claim 1 , wherein the alternative route is used if the primary route does not comply with the set of preferences which are service level constraints.
The roaming service from the previous description will only switch to the alternative network route (through the second client device) if the primary network route doesn't meet the quality of service requirements defined in the first client's preferences. These preferences are service level constraints that the primary route must comply with. If the primary route's performance degrades below acceptable levels, the system automatically activates the alternative route.
3. The method according to claim 1 , wherein providing the alternative route comprises using a second server as a roaming device not running the at least one application service and the associated virtual machine on a first server.
The roaming service from the initial description uses a second server as a dedicated "roaming device." This second server doesn't host the application itself; instead, it purely provides routing services for the alternative route. The application and associated virtual machine runs on a first server, while a separate server provides the alternate routing path when needed.
4. The method according to claim 3 , wherein the first server and the second server each deploy a counter for counting routing services provided for alternative routes.
In the roaming service using two servers (one hosting the application and one as a dedicated roaming device), both servers track the number of times they provide routing services for alternative routes. Each server deploys a counter to keep track of how often they are used for the routing. This counting allows for monitoring and potentially billing or resource allocation adjustments based on the usage of alternative routes.
5. The method according to claim 1 , wherein the set of preferences comprises rules for quality of service for a communication between the first client and the associated application service.
In the roaming service from the initial description, the client preferences used to determine the alternative route include rules related to the quality of service (QoS) of the communication between the first client and the application. These QoS rules can specify requirements for latency, bandwidth, packet loss, or other network performance metrics. The alternative route is selected to satisfy these quality of service requirements.
6. The method according to claim 1 , wherein the second client is adapted to operate as a proxy for a route between the first client and the at least one application service.
In the roaming service, the second client device acts as a proxy for the connection between the first client and the application. The second client is adapted to relay traffic between them, effectively creating an alternative network path when the primary route is insufficient. This proxy functionality allows the first client to continue accessing the application even when the direct connection is problematic.
7. The method according to claim 1 , wherein a second server, in communication with the first server, also runs a roaming daemon.
The roaming service includes a second server that communicates with the first server (hosting the application). Both servers run a roaming daemon. This allows the second server to assist in making routing decisions and potentially provide the alternative route directly, rather than relying solely on the second client device as a proxy. The two roaming daemons work together to manage roaming functionality.
8. A roaming system for providing comprising: a memory; a processor executing instructions stored in the memory to provide: a roaming service to a first client, wherein the first client is associated to at least one application service running on an associated virtual machine as a Cloud service via a primary route between the first client and the at least one application service; a second client, both the first and second client running an agent; a routing module adapted for providing an alternative route to the primary route between the first client and the at least one application service utilizing the second agent running in the second client, wherein the alternative route is based on a set of preferences submitted by the first client, wherein a first server running the associated virtual machine executing the application service also runs a roaming daemon, the roaming daemon using a profile comprising at least one of a trusted vendor list, a reserved computation volume, an engagement type, a billing threshold, and a security level, and wherein different servers may be selected, according to the profile, to establish the alternative route.
A roaming system provides seamless connectivity for cloud applications. The system comprises a processor, memory, and software to implement a roaming service. A first client accesses an application running on a virtual machine via a primary route. A second client, running an agent, helps create an alternative route. The system chooses this alternative route based on the first client's preferences. The application server runs a roaming daemon. This daemon uses a profile including trusted vendors, compute resources, engagement type, billing threshold and security level to choose different servers for the alternative route. Both the first and second clients run agents to facilitate routing.
9. A computer program product comprising instructions embodied on a non-transitory computer usable medium and configured, when executed by a computer, to provide a roaming service to a first client, the first client being associated to at least one application service running on an associated virtual machine as a Cloud service via a primary route between the first client and the at least one application service, by performing steps of: providing a first agent on the first client; and providing an alternative route to the primary route between the first client and the at least one application service utilizing a second agent running on a second client, wherein the alternative route is based on a set of preferences submitted by the first client, wherein a first server running the associated virtual machine executing the application service also runs a roaming daemon, the roaming daemon using a profile comprising at least one of a trusted vendor list, a reserved computation volume, an engagement type, a billing threshold, and a security level, and wherein different servers may be selected, according to the profile, to establish the alternative route.
A software program, stored on a computer-readable medium, implements a roaming service for cloud applications. When executed, the program allows a client device to maintain connectivity by using an alternate route via a second client. The first client has an agent installed. The roaming daemon on the server selects the alternative route based on the first client's preferences, like trusted vendors, compute resources, engagement type, billing limits and security level. These factors determine which servers provide the alternative route. It sets up an alternative route through a second client device acting as a proxy when the main connection is poor.
10. The method according to claim 1 , wherein the roaming daemon uses a profile comprising a trusted vendor list and a reserved computation volume.
The roaming service's daemon uses a profile containing a list of trusted vendors and the amount of reserved computing resources. These are two factors considered when selecting a server for the alternative route. The trusted vendor list prioritizes servers from preferred providers, while the reserved compute volume ensures sufficient resources are available for the application's roaming needs.
11. The method according to claim 1 , wherein the roaming daemon uses a profile comprising a reserved computation volume and an engagement type.
The roaming service's daemon profile includes a reserved compute volume and an engagement type. These parameters influence the selection of an alternative routing server. The reserved compute volume ensures enough resources, and the engagement type (e.g., trial, paid) may affect the priority or type of resources allocated to the roaming service.
12. The method according to claim 1 , wherein the roaming daemon uses a profile comprising an engagement type and a billing threshold.
The roaming service's daemon profile uses engagement type and billing threshold information. These factors influence the server chosen for the alternative route. The engagement type (e.g., premium, basic) may determine resource allocation, while the billing threshold helps avoid exceeding budget limits when using roaming services.
13. The method according to claim 1 , wherein the roaming daemon uses a profile comprising a billing threshold and a security level.
The roaming service's daemon profile includes a billing threshold and a security level. These parameters determine which servers can provide the alternative route. The billing threshold prevents excessive costs during roaming, while the security level ensures the chosen server meets the required security standards for data transmission and application access.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
June 25, 2015
May 16, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.