Cloud infrastructure architecture

Cloud is characterized by its short time to market and rapid innovation possibilities. Complementing this is the scalability of application and the introduction of new technologies, which are facilitated by the independent lifecycles of application components and the services they use.

This enables developers to focus on the commercial potential of their applications, along with the ability to build lightweight software modules that maximize the reuse of platform features.

Addressing key challenges

For cloud to reveal its full potential, there are many gaps to fill, including ways to troubleshoot in a highly-distributed system, test several independent services simultaneously, as well as predict latency (or maintain it within set limits).

Our future cloud infrastructure offering supports multiple routing contexts, external networks, packet-load-balancing capabilities for heavy payload applications, and latency control. Its automation and dynamicity allows the architecture to work across various cloud models: public, private, or hybrid. For instance, latency-sensitive workloads, or tasks that require security or control for proprietary data, can be deployed on premises in a private cloud – while non-sensitive workloads can be deployed in a public cloud, maximizing agility and optimizing costs.

Cloud application architecture

  • Cloud infrastructure is a set of independent services – each with different functions
  • Services are grouped into functional areas, with unique capabilities characterized by application
  • An application can be deployed into a single container execution environment, managed by a single container orchestrator entity, or can be distributed across multiple environments managed by several different orchestrator entities
  • To make cloud telco grade, availability, automation, security, and performance requirements must be met, along with other set criteria
Cloud application architecture image

IMS in the cloud

In this deployment example, we show that cloud creates the possibility for IMS core networks to serve multiple tenants simultaneously – allowing them to benefit from infrastructure-related functions, such as firewall and load balance.

By accelerating deployment speeds, simplifying complex combinations and swiftly updating software, our cloud infrastructure makes efficient use of network resources and can respond to changes in capacity demand.

This enables application scalability, as new technologies and services can be deployed as independent lifecycles. It also increases application portability to several IaaS solutions, reducing the number of cloud execution platforms that need to be supported.

IMS graphic

Subsequently, this reduces time-to-market for new services as developers can focus on the commercial viability of their applications, freeing them from the concerns associated with deployment, testing, adaptation, and rollout. This is further complemented by the fact that future applications are likely to be less complex and consume less resources than their traditionally-programmed counterparts, creating the perfect platform for new innovations, and new possibilities.

Reaching new heights

Ensuring robustness, security and interoperability, as well as an optimized performance for telco applications, the cloud infrastructure can minimize the costs induced by the transformation itself.

Additionally, the system provides a smooth transition and tailored, real-time network support for the telecoms industry – all while introducing new sets of enablers, which act as a bridge to cloud-empowered telco applications and solutions.

Discover more about cloud infrastructure:

Related architecture articles: Virtualizing network services - the telecom cloud Paving the way to telco-grade PaaS OpenStack as the API framework for NFV: the benefits, and the extensions needed Distributed cloud infrastructure – a unified approach Related Ericsson portfolio: Cloud and NFV infrastructure More reading in Future network architecture document: Cloud Infrastructure

Related Ericsson portfolio:

More reading in Future network architecture document: