18576787. STATEFUL ENDPOINT MOBILITY IN A FEDERATED CLOUD COMPUTING SYSTEM simplified abstract (Telefonaktiebolaget LM Ericsson (publ))

From WikiPatents
Revision as of 11:24, 19 September 2024 by Wikipatents (talk | contribs) (Creating a new page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

STATEFUL ENDPOINT MOBILITY IN A FEDERATED CLOUD COMPUTING SYSTEM

Organization Name

Telefonaktiebolaget LM Ericsson (publ)

Inventor(s)

Miika Komu of HELSINKI (FI)

Tero Kauppinen of ESPOO (FI)

Jemal Tahir of Espoo (FI)

[[:Category:Jimmy Kj�llman of ESPOO (FI)|Jimmy Kj�llman of ESPOO (FI)]][[Category:Jimmy Kj�llman of ESPOO (FI)]]

STATEFUL ENDPOINT MOBILITY IN A FEDERATED CLOUD COMPUTING SYSTEM - A simplified explanation of the abstract

This abstract first appeared for US patent application 18576787 titled 'STATEFUL ENDPOINT MOBILITY IN A FEDERATED CLOUD COMPUTING SYSTEM

The abstract describes a method in a federated cloud computing system to move an endpoint between clusters. This involves deploying a replica of the endpoint and database in a new cluster, synchronizing the databases, and redirecting clients to the new endpoint.

  • Method to move an endpoint between clusters in a federated cloud computing system
  • Deploying a replica of the endpoint and database in a new cluster
  • Synchronizing the databases to ensure data consistency
  • Redirecting clients to the new endpoint for continued service
  • Efficiently managing the migration of endpoints in a distributed system

Potential Applications: - Cloud computing services - Data center management - Load balancing in distributed systems

Problems Solved: - Seamless migration of endpoints between clusters - Ensuring data consistency during the migration process - Efficient resource utilization in a federated cloud environment

Benefits: - Improved scalability and flexibility in cloud computing systems - Enhanced fault tolerance and reliability - Simplified management of distributed endpoints

Commercial Applications: Title: "Efficient Endpoint Migration in Federated Cloud Computing Systems" This technology can be utilized by cloud service providers to optimize resource allocation, improve service availability, and enhance overall system performance. It can also benefit companies with large-scale distributed systems looking to streamline endpoint management and ensure data consistency across clusters.

Prior Art: Further research can be conducted in the field of federated cloud computing systems, endpoint migration strategies, and database synchronization techniques to identify any existing technologies or methods related to the described innovation.

Frequently Updated Research: Stay updated on advancements in federated cloud computing, distributed systems management, and database replication technologies to enhance the efficiency and effectiveness of endpoint migration processes.

Questions about Endpoint Migration in Federated Cloud Computing Systems: 1. How does the method ensure data consistency between the original and replica databases during the migration process? 2. What are the key factors to consider when deciding to move an endpoint between clusters in a federated cloud computing system?


Original Abstract Submitted

A method by a master orchestrator in a federated cloud computing system to move an endpoint between clusters. The method includes receiving a request to move a first endpoint implemented in a first cluster to another cluster, wherein the first endpoint provides a service and uses a first database to store state associated with the service, responsive to receiving the request, causing a second endpoint and a second database to be deployed in a second cluster, wherein the second endpoint is a replica of the first endpoint, the second database is a replica of the first database, and the second endpoint is to use the second database to store state, causing synchronization between the first database and the second database to begin, causing the first endpoint to use the second database instead of the first database, and causing clients to use the second endpoint instead of the first endpoint.