http://www.ericsson.com/review
Automation and network programmability are key concepts in the evolution of telecom networks. Architecture designed with high degrees of automation and network programmability can rapidly adapt to emerging requirements, and as such improve operational efficiency and time to market for new services.
Software Defined Networking (SDN) is an emerging trend in the networking and communication industry and promises to deliver enormous benefits, from reduced costs to more efficient network operations. It is a new approach that gives network operators and owners more control of the infrastructure, allowing optimization, customization and virtualization that enable the creation of new types of network services. This is done by decoupling the management and control planes that make decisions about where traffic is sent from (the control plane) the underlying hardware that forwards data traffic to the selected destination (the data plane).
CONTAINERIZED SERVICES ORCHESTRATION FOR EDGE COMPUTING IN SOFTWARE-DEFINED W...IJCNCJournal
As SD-WAN disrupts legacy WAN technologies and becomes the preferred WAN technology adopted by corporations, and Kubernetes becomes the de-facto container orchestration tool, the opportunities for deploying edge-computing containerized applications running over SD-WAN are vast. Service orchestration in SD-WAN has not been provided with enough attention, resulting in the lack of research focused on service discovery in these scenarios. In this article, an in-house service discovery solution that works alongside Kubernetes’ master node for allowing improved traffic handling and better user experience when running micro-services is developed. The service discovery solution was conceived following a design science research approach. Our research includes the implementation of a proof-ofconcept SD-WAN topology alongside a Kubernetes cluster that allows us to deploy custom services and delimit the necessary characteristics of our in-house solution. Also, the implementation's performance is tested based on the required times for updating the discovery solution according to service updates. Finally, some conclusions and modifications are pointed out based on the results, while also discussing possible enhancements.
Applications Drive Secure Lightpath Creation Across Heterogeneous DomainsTal Lavian Ph.D.
We realize an open, programmable paradigm for application-driven network control by way of a novel network plane — the “service plane” — layered above legacy networks. The service plane bridges domains, establishes trust, and exposes control to credited users/applications while preventing unauthorized access and resource theft. The Authentication, Authorization, Accounting subsystem and the Dynamic Resource Allocation Controller are the two defining building blocks of our service plane. In concert, they act upon an interconnection request or a restoration request according to application requirements, security credentials, and domain-resident policy. We have experimented with such service
plane in an optical, large-scale testbed featuring two hubs (NetherLight in Amsterdam, StarLight in Chicago) and attached network clouds, each representing an independent domain. The dynamic interconnection of the heterogeneous domains occurred at Layer 1. The interconnections ultimately resulted in an optical end-to-end path (lightpath) for use by the
requesting Grid application.
Software Defined Networking (SDN) is an emerging trend in the networking and communication industry and promises to deliver enormous benefits, from reduced costs to more efficient network operations. It is a new approach that gives network operators and owners more control of the infrastructure, allowing optimization, customization and virtualization that enable the creation of new types of network services. This is done by decoupling the management and control planes that make decisions about where traffic is sent from (the control plane) the underlying hardware that forwards data traffic to the selected destination (the data plane).
CONTAINERIZED SERVICES ORCHESTRATION FOR EDGE COMPUTING IN SOFTWARE-DEFINED W...IJCNCJournal
As SD-WAN disrupts legacy WAN technologies and becomes the preferred WAN technology adopted by corporations, and Kubernetes becomes the de-facto container orchestration tool, the opportunities for deploying edge-computing containerized applications running over SD-WAN are vast. Service orchestration in SD-WAN has not been provided with enough attention, resulting in the lack of research focused on service discovery in these scenarios. In this article, an in-house service discovery solution that works alongside Kubernetes’ master node for allowing improved traffic handling and better user experience when running micro-services is developed. The service discovery solution was conceived following a design science research approach. Our research includes the implementation of a proof-ofconcept SD-WAN topology alongside a Kubernetes cluster that allows us to deploy custom services and delimit the necessary characteristics of our in-house solution. Also, the implementation's performance is tested based on the required times for updating the discovery solution according to service updates. Finally, some conclusions and modifications are pointed out based on the results, while also discussing possible enhancements.
Applications Drive Secure Lightpath Creation Across Heterogeneous DomainsTal Lavian Ph.D.
We realize an open, programmable paradigm for application-driven network control by way of a novel network plane — the “service plane” — layered above legacy networks. The service plane bridges domains, establishes trust, and exposes control to credited users/applications while preventing unauthorized access and resource theft. The Authentication, Authorization, Accounting subsystem and the Dynamic Resource Allocation Controller are the two defining building blocks of our service plane. In concert, they act upon an interconnection request or a restoration request according to application requirements, security credentials, and domain-resident policy. We have experimented with such service
plane in an optical, large-scale testbed featuring two hubs (NetherLight in Amsterdam, StarLight in Chicago) and attached network clouds, each representing an independent domain. The dynamic interconnection of the heterogeneous domains occurred at Layer 1. The interconnections ultimately resulted in an optical end-to-end path (lightpath) for use by the
requesting Grid application.
Cloud-computing applications are characterized by stateful access, with differentiated service levels, charged to the end user using the pay-per-use pricing model. Implicit in this model is the assumption that a cloud application is always on. Scaling the cloud delivery model to an Internet scale (millions of users) is a challenge that next-generation Layer 4–7 infrastructure needs to overcome.
When two large companies merge, it often takes a while – years in some cases – before processes get redesigned to span all departments, and the new organization settles into a lean and profitable machine. And the same is true of OSS/BSS. These systems have been designed for two different purposes: to keep the network operational and to keep it profitable. But today’s demanding networks need the functions of both of these systems to work together, and to work across the varying lifecycles of products and services.
This volume of the Open Datacenter Interoperable Network (ODIN) describes software defined networking (SDN) and OpenFlow. SDN is used to simplify network control and management, automate network virtualization services, and provide a platform from which to build agile ....
This paper focuses on the evolutionary stages for cloudification then covers the key software building blocks that will be needed to enable NFV, and ultimately ICT transformation to 5G. It describes how Intel® Open Networking Platform (Intel® ONP) Server running on innovative new networking platforms based on Intel® silicon can help reduce the cost and effort required for service providers and vendors alike to adopt and deploy SDN and NFV architectures.
aCelera WAN optimization controllers accelerate applications,
speed data transfers and reduce bandwidth costs using a
combination of application, network and protocol optimization.
Secure & fault tolerance handoff in vanet using special mobile agentcsandit
Vehicular Traffic poses an emerging issue nowadays. The critical factors for the data
communication are speed and time tradeoffs. For data communication, gathering and retrieving
information many cost-effective and tested techniques are required in VANET. Client server
architectures being coercive are commonly used in spite of having drawbacks of fault and time
in-effectiveness. This paper elaborates a proposed method in VANET for fault tolerance
information retrieval based on theory of bandwidth and timestamp. Mobile Agents, with the
feature of autonomy, social ability, learning, and most importantly mobility, regarded as an
appropriate technology to build applications for instance information retrieval system in mobile
computing environment.
SDN and NFV Value in Business Services: Innovations in Network Monetization a...Alan Sardella
White paper submitted to the Society of Cable Telecommunications Engineers (SCTE) by Mazen Khaddem of Cox Communications and Dr. Loukas Paraschis of Cisco Systems. Paper covers technical reference design in SDN including the role of open source, orchestration and control, and the importance of a hybrid control plane for legacy, multivendor networks.
Cloud-computing applications are characterized by stateful access, with differentiated service levels, charged to the end user using the pay-per-use pricing model. Implicit in this model is the assumption that a cloud application is always on. Scaling the cloud delivery model to an Internet scale (millions of users) is a challenge that next-generation Layer 4–7 infrastructure needs to overcome.
When two large companies merge, it often takes a while – years in some cases – before processes get redesigned to span all departments, and the new organization settles into a lean and profitable machine. And the same is true of OSS/BSS. These systems have been designed for two different purposes: to keep the network operational and to keep it profitable. But today’s demanding networks need the functions of both of these systems to work together, and to work across the varying lifecycles of products and services.
This volume of the Open Datacenter Interoperable Network (ODIN) describes software defined networking (SDN) and OpenFlow. SDN is used to simplify network control and management, automate network virtualization services, and provide a platform from which to build agile ....
This paper focuses on the evolutionary stages for cloudification then covers the key software building blocks that will be needed to enable NFV, and ultimately ICT transformation to 5G. It describes how Intel® Open Networking Platform (Intel® ONP) Server running on innovative new networking platforms based on Intel® silicon can help reduce the cost and effort required for service providers and vendors alike to adopt and deploy SDN and NFV architectures.
aCelera WAN optimization controllers accelerate applications,
speed data transfers and reduce bandwidth costs using a
combination of application, network and protocol optimization.
Secure & fault tolerance handoff in vanet using special mobile agentcsandit
Vehicular Traffic poses an emerging issue nowadays. The critical factors for the data
communication are speed and time tradeoffs. For data communication, gathering and retrieving
information many cost-effective and tested techniques are required in VANET. Client server
architectures being coercive are commonly used in spite of having drawbacks of fault and time
in-effectiveness. This paper elaborates a proposed method in VANET for fault tolerance
information retrieval based on theory of bandwidth and timestamp. Mobile Agents, with the
feature of autonomy, social ability, learning, and most importantly mobility, regarded as an
appropriate technology to build applications for instance information retrieval system in mobile
computing environment.
SDN and NFV Value in Business Services: Innovations in Network Monetization a...Alan Sardella
White paper submitted to the Society of Cable Telecommunications Engineers (SCTE) by Mazen Khaddem of Cox Communications and Dr. Loukas Paraschis of Cisco Systems. Paper covers technical reference design in SDN including the role of open source, orchestration and control, and the importance of a hybrid control plane for legacy, multivendor networks.
Presentation on 1G/2G/3G/4G/5G/Cellular & Wireless TechnologiesKaushal Kaith
This Presentation is explaining all about the Generations of Mobile or Cellular Technology (1G/2G/2.5/ 3G/4g/5G). This explain the invented details ,features,drawbacks,look of wireless models and comparison and evolution of technology from 1G to 5G and also explaining about wireless application and their services.
Ericsson Review: Software-Defined-NetworkingEricsson
An architecture based on software-defined networking (SDN) techniques gives operators greater freedom to balance operational and business parameters, such as network resilience, service performance and QoE against opex and capex. With its beginnings in data-center technology, software-defined networking (SDN) technology has developed to the point where it can offer significant opportunities to service providers.
The traditional way of describing network architecture and how a network behaves is through the fixed designs and behaviors of its various elements. The concept of software-defined networking (SDN) describes networks and how they behave in a more flexible way – through software tools that describe network elements in terms of programmable network states.
To maximize the potential benefits and deliver superior user experience, software-defined networking (SDN) needs to be implemented outside the sphere of the data center across the entire network. This can be achieved through enabling network programmability based on open APIs. Service Provider SDN will help operators to scale networks and take advantage of new revenue-generating possibilities.
For more from Ericsson Review visit: http://www.ericsson.com/thinkingahead/technology_insights
Joint RTI/Cisco response to the SDN RFI (see http://www.omg.org/cgi-bin/doc?mars/13-09-16.zip).
Summary:
SDN programming relies on the ability to query network state, define forwarding policies and update policies in a consistent way. Another important aspect is the management and configuration interfaces across heterogeneous devices.
Current northbound API’s still force developers to think in terms of match-action rules and not in higher level abstractions with proper compositional semantics.
Part of the problem lies in the various protocols being adopted for SDN including OpenFlow, OF-CONFIG, PCEP, I2RS, OVSDB, IF-MAP, OnePK, etc. Vendors must either build adapters for each or rely on a mediation server such as OpenDaylight Controller Service Abstraction Layer to provide the mediation between protocols.
Each of these protocols expands the feature space with sometimes conflicting behaviors and representations making it difficult to design a high-level interface which addresses the developers need to build applications out of multiple independent and reusable network policies that must act on the same traffic.
With this in mind, the first step towards developing and/or standardizing a Northbound protocol and/or API should be the standardization of the information model that represents the observable and controllable state of the SDN network elements.
Model Driven Architectures are fundamental to building platform and computation independent services. SDN adopts some of these principals leveraging schema driven approaches and data driven models but there are no efforts to converge onto a well-understood model that can be used to define the protocol and API interaction.
In this respect our motivation is to leverage existing middleware technologies and architectures such as DDS, XMPP, AMQP and REST to provide an extensible and adaptable protocol, which will promote unification and simplify access to the goals of querying state, notification of changes, forwarding policy, security and performance policies.
For instance leveraging middleware platforms which can automatically define the network data representations, network protocols, discovery mechanism, and the means to scale in a fault tolerant way would allow more concentration on the higher level abstractions, composition and segmentation of controller logic. In addition these middleware platforms provide standard APIs in different programming languages, so the API also comes “for free” once the mapping is done.
A Centralized Network Management Application for Academia and Small Business ...ITIIIndustries
Software-defined networking (SDN) is reshaping the networking paradigm. Previous research shows that SDN has advantages over traditional networks because it separates the control and data plane, leading to greater flexibility through network automation and programmability. Small business and academia networks require flexibility, like service provider networks, to scale, deploy, and self-heal network infrastructure that comprises of cloud operating systems, virtual machines, containers, vendor networking equipment, and virtual network functions (VNFs); however, as SDN evolves in industry, there has been limited research to develop an SDN architecture to fulfil the requirements of small business and academia networks. This research proposes a network architecture that can abstract, orchestrate, and scale configurations based on academia and small business network requirements. Our results show that the proposed architecture provides enhanced network management and operations when combined with the network orchestration application (NetO-App) developed in this research. The NetO-App orchestrates network policies, automates configuration changes, secures container infrastructure, and manages internal and external communication between the campus networking infrastructure.
Softwarization has been transforming industries like data center and communications businesses. The established hardware-based architectures are being replaced by fundamentally new approaches - software-based systems which are essentially more flexible, dynamic and powerful. In this paper we analyse the evolution in data centers and communications networks towards virtualized platforms and study how a similar type of evolution could impact and benefit power distribution. Following the softwarization process in other industry sectors, we consider that next a Software Defined Grid (SDG) will emerge.
The NECOS project addresses the limitations of current cloud computing infrastructures to respond to the demand of new services, as presented in two use-cases, that will drive the whole execution of the project.
The NECOS platform will be based on state of the art open software platforms, which will be carefully selected, rather than start from scratch. This baseline platform will be enhanced with the management and orchestration algorithms and the APIs that will constitute the research activity of the project. Finally, the NECOS platform will be validated, in the context of the two proposed use cases, using the 5TONIC and FIBRE testing frameworks.
everis joins Telefonica to collaborate in the Internet para Todos Peru initiative, a wholesale telecommunications infrastructures operator that aims to expand the internet connectivity in rural areas of Latin America.
Resulting from this collaboration, everis will be in charge of the deployment and maintenance of the Operation Support Systems (OSS) that enable the creation and sustainment of a reliable and quality network.
The solutions already deployed by everis are based on open models and include advanced network analytics systems, AI and machine learning applications.
Container ecosystem based PaaS solution for Telco Cloud Analysis and ProposalKrishna-Kumar
In our lab setup, we have derived a cluster
container orchestration mechanism to handle the
Telco specific (NFV) capabilities on top of the
traditional containers.
Original document @ http://dl6.globalstf.org/index.php/joc/article/view/1641/1667
IT teams face unprecedented challenges to support dynamic application requirements on top of a rigid legacy infrastructure. A vendor-agnostic orchestration helps deliver rapid network
services for multi-vendor infrastructure. Anuta NCX platform with it’s layered, YANG model-driven and abstraction approach helps in delivering vendor neutral, extensible and maintainable
services for multiple domains such as Branch/CPE, Data Center, Cloud, and Carrier Core networks. The NCX platform enables customers and partners to develop their own Service and Device models for complete customization within few days. Many large enterprises and service providers have deployed NCX to orchestrate their brownfield and greenfield networks.
Our journal is official publication of the Utilitas mathematical journal original research articles and aspect of both the pure and applied mathematics. UMJ coverage extends to Operations Research, Mathematical Economics, Mathematics Biology and Computer Science. our Journal has became fully open access Journal.
our journal publishes original research and review articles on all aspects of both pure and applied mathematics. It's publish Algebra,Analysis,Geometry,Topology,Number Theory,Differential Equations etc. UMJ coverage extends to Operations Research, Mathematical Economics, Mathematics Biology and Computer Science.
Utilitas Mathematica Journal has a original research in all areas of pure and applied mathematics.UMJ coverage extends to Operations Research, Mathematical Economics, Mathematics Biology and Computer Science.It enjoys good reputation and popularity at international level in terms of research papers and distribution worldwide.
Utilitas Mathematica Journal the journal publishes original research in all areas of pure and applied mathematics, statistics Algebra,Topology,Differential Equations,Mathematical Physics Utilitas Mathematica international level in terms of research provides worldwide.
https://utilitasmathematica.com/index.php/Index
Similar to Architecture evolution for automation and network programmability (20)
Ericsson Technology Review: Versatile Video Coding explained – the future of ...Ericsson
Continuous innovation in 5G networks is creating new opportunities for video-enabled services for both consumers and industries, particularly in areas such as the Internet of Things and the automotive sector. These new services are expected to rely on continued video evolution toward 8K resolutions and beyond, and on new strict requirements such as low end-to-end latency for video delivery.
The latest Ericsson Technology Review article explores recent developments in video compression technology and introduces Versatile Video Coding (VVC) – a significant improvement on existing video codecs that we think deserves to be widely deployed in the market. VVC has the potential both to enhance the user experience for existing video services and offer an appropriate performance level for new media services over 5G networks.
BRIDGING THE GAP BETWEEN PHYSICAL AND DIGITAL REALITIES
The key role that connectivity plays in our personal and professional lives has never been more obvious than it is today. Thankfully, despite the sudden, dramatic changes in our behavior earlier this year, networks all around the world have proven to be highly resilient. At Ericsson, we’re committed to ensuring that the network platform continues to improve its ability to meet the full range of societal needs as well as supporting enterprises to stay competitive in the long term. We know that greater agility and speed will be essential.
This issue of our magazine includes several articles that explain Ericsson’s approach to future network development, including my annual technology trends article. The seven trends on this year’s list serve as a critical cornerstone in the development of a common Ericsson vision of what future networks will provide, and what sort of technology evolution will be required to get there.
ERIK EKUDDEN
Senior Vice President, Chief Technology Officer and Head of Group Function Technology
Ericsson Technology Review: Integrated access and backhaul – a new type of wi...Ericsson
Today millimeter wave (mmWave) spectrum is valued mainly because it can be used to achieve high speeds and capacities when combined with spectrum assets below 6GHz. But it can provide other benefits as well. For example, mmWave spectrum makes it possible to use a promising new wireless backhaul solution for 5G New Radio – integrated access and backhaul (IAB) – to densify networks with multi-band radio sites at street level.
This Ericsson Technology Review article explains the IAB concept at a high level, presenting its architecture and key characteristics, as well as examining its advantages and disadvantages compared with other backhaul technologies. It concludes with a presentation of the promising results of several simulations that tested IAB as a backhaul option for street sites in both urban and suburban areas.
Ericsson Technology Review: Critical IoT connectivity: Ideal for time-critica...Ericsson
Critical Internet of Things (IoT) connectivity is an emerging concept in IoT development that enables more efficient and innovative services across a wide range of industries by reliably meeting time-critical communication needs. Mobile network operators (MNOs) are in the perfect position to enable these types of time-critical services due to their ability to leverage advanced 5G networks in a systematic and cost-effective way.
This Ericsson Technology Review article explores the benefits of Critical IoT connectivity in areas such as industrial control, mobility automation, remote control and real-time media. It also provides an overview of key network technologies and architectures. It concludes with several case studies based on two deployment scenarios – wide area and local area – that illustrate how well suited 5G spectrum assets are for Critical IoT use cases.
5G New Radio has already evolved in important ways since the 3GPP standardized Release 15 in late 2018. The significant enhancements in Releases 16 and 17 are certain to play a critical role in expanding both the availability and the applicability of 5G NR in both industry and public services in the near future.
This Ericsson Technology Review article summarizes the most notable new developments in releases 16 and 17, grouped into two categories: enhancements to existing features and features that address new verticals and deployment scenarios. This analysis and our insights about the future beyond Release 17 is an important component of our work to help mobile network operators and other stakeholders better understand and plan for the many new 5G NR opportunities that are on the horizon.
Ericsson Technology Review: The future of cloud computing: Highly distributed...Ericsson
The growing interest in cloud computing scenarios that incorporate both distributed computing capabilities and heterogeneous hardware presents a significant opportunity for network operators. With a vast distributed system (the telco network) already in place, the telecom industry has a significant advantage in the transition toward distributed cloud computing.
This Ericsson Technology Review article explores the future of cloud computing from the perspective of network operators, examining how they can best manage the complexity of future cloud deployments and overcome the technical challenges. Redefining cloud to expose and optimize the use of heterogeneous resources is not straightforward, but we are confident that our use cases and proof points validate our approach and will gain traction both in the telecommunications community and beyond.
Ericsson Technology Review: Optimizing UICC modules for IoT applicationsEricsson
Commonly referred to as SIM cards, the universal integrated circuit cards (UICCs) used in all cellular devices today are in fact complex and powerful minicomputers capable of much more than most Internet of Things (IoT) applications require. Until a simpler and less costly alternative becomes available, action must be taken to ensure that the relatively high price of UICC modules does not hamper IoT growth.
This Ericsson Technology Review article presents two mid-term approaches. The first is to make use of techniques that reduce the complexity of using UICCs in IoT applications, while the second is to use the UICCs’ excess capacity for additional value generation. Those who wish to exploit the potential of the UICCs to better support IoT applications have the opportunity to use them as cryptographic storage, to run higher-layer protocol stacks and/or as supervisory entities, for example.
Mobile data traffic volumes are expected to increase by a factor of four by 2025, and 45 percent of that traffic will be carried by 5G networks. To deliver on customer expectations in this rapidly changing environment, communication service providers must overcome challenges in three key areas: building sufficient capacity, resolving operational inefficiencies through automation and artificial intelligence, and improving service differentiation. This issue of ETR magazine provides insights about how to tackle all three.
Ericsson Technology Review: 5G BSS: Evolving BSS to fit the 5G economyEricsson
The 5G network evolution has opened up an abundance of new business opportunities for communication service providers (CSPs) in verticals such as industrial automation, security, health care and automotive. In order to successfully capitalize on them, CSPs must have business support systems (BSS) that are evolved to manage complex value chains and support new business models. Optimized information models and a high degree of automation are required to handle huge numbers of devices through open interfaces.
This Ericsson Technology Review article explains how 5G-evolved BSS can help CSPs transform themselves from traditional network developers to service enablers for 5G and the Internet of Things, and ultimately to service creators with the ability to collaborate beyond telecoms and establish lucrative digital value systems.
Ericsson Technology Review: 5G migration strategy from EPS to 5G systemEricsson
For many operators, the introduction of the 5G System (5GS) to provide wide-area services in existing Evolved Packet System (EPS) deployments is a necessary step toward creating a full-service, future-proof 5GS in the longer term. The creation of a combined 4G-5G network requires careful planning and a holistic strategy, as the introduction of 5GS has significant impacts across all network domains, including the RAN, packet core, user data and policies, and services, as well as affecting devices and backend systems.
This Ericsson Technology Review article provides an overview of all the aspects that operators need to consider when putting together a robust EPS-to-5GS migration strategy and provides guidance about how they can adapt the transition to address their particular needs per domain.
Ericsson Technology Review: Creating the next-generation edge-cloud ecosystemEricsson
The surge in data volume that will come from the massive number of devices enabled by 5G has made edge computing more important than ever before. Beyond its abilities to reduce network traffic and improve user experience, edge computing will also play a critical role in enabling use cases for ultra-reliable low-latency communication in industrial manufacturing and a variety of other sectors.
This Ericsson Technology Review article explores the topic of how to deliver distributed edge computing solutions that can host different kinds of platforms and applications and provide a high level of flexibility for application developers. Rather than building a new application ecosystem and platform, we strongly recommend reusing industrialized and proven capabilities, utilizing the momentum created with Cloud Native Computing Foundation, and ensuring backward compatibility.
The rise of the innovation platform
Society and industry are transforming at an unprecedented rate. At the same time, the network platform is emerging as an innovation platform with the potential to offer all the connectivity, processing, storage and security needed by current and future applications. In my 2019 trends article, featured in this issue of Ericsson Technology Review, I share my view of the future network platform in relation to six key technology trends.
This issue of the magazine also addresses critical topics such as trust enablement, the extension of computing resources all the way to the edge of the mobile network, the growing impact of the cloud in the telco domain, overcoming latency and battery consumption challenges, and the need for end-to-end connectivity. I hope it provides you with valuable insights about how to overcome the challenges ahead and take full advantage of new opportunities.
Ericsson Technology Review: Spotlight on the Internet of ThingsEricsson
The Internet of Things (IoT) has emerged as a fundamental cornerstone in the digitalization of both industry and society as a whole. It represents a huge opportunity not only in economic terms, but also from a global challenges perspective – making it easier for governments, non-governmental organizations and the private sector to address pressing food, energy, water and climate related issues.
5G and the IoT are closely intertwined. One of the biggest innovations within 5G is support for the IoT in all its forms, both by addressing mission criticality as well as making it possible to connect low-cost, long-battery-life sensors.
With this in mind, we decided to create a special issue of Ericsson Technology Review solely focused on IoT opportunities and challenges. I hope it provides you with valuable insights about the IoT-related opportunities available to your organization, along with ideas about how we can overcome the challenges ahead.
Ericsson Technology Review: Driving transformation in the automotive and road...Ericsson
A variety of automotive and transport services that require cellular connectivity are already in commercial operation today, and many more are yet to come. Among other things, these services will improve road safety and traffic efficiency, saving lives and helping to reduce the emissions that contribute to climate change. At Ericsson, we believe that the best way to address the growing connectivity needs of this industry sector is through a common network solution, as opposed to taking a single-segment silo approach.
The latest Ericsson Technology Review article explains how the ongoing rollout of 5G provides a cost-efficient and feature-rich foundation for a horizontal multiservice network that can meet the connectivity needs of the automotive and transport ecosystem. It also outlines the key challenges and presents potential solutions.
This presentation explains the importance of SD-WAN technology as part of the Enterprise digital transformation strategy. It goes over the first wave of SD-WAN in a single vendor deployment, with Do-it-yourself (DIY) as the preferred model. Then continues with the importance of orchestration in the second wave of SD-WAN deployments in a multi-vendor ecosystem, turning to SD-WAN Managed Services as the preferred model. It ends up with some examples of use cases and the Verizon customer case. More information on Ericsson Dynamic orchestration - http://m.eric.sn/6rsZ30psKLu
Ericsson Technology Review: 5G-TSN integration meets networking requirements ...Ericsson
Time-Sensitive Networking (TSN) is becoming the standard Ethernet-based technology for converged networks of Industry 4.0. Understanding the importance and relevance of TSN features, as well as the capabilities that allow 5G to achieve wireless deterministic and time-sensitive communication, is essential to industrial automation in the future.
The latest Ericsson Technology Review article explains how TSN is an enabler of Industry 4.0, and that together with 5G URLLC capabilities, the two key technologies can be combined and integrated to provide deterministic connectivity end to end. It also discusses TSN standards and the value of the TSN toolbox for next generation industrial automation networks.
Ericsson Technology Review: Meeting 5G latency requirements with inactive stateEricsson
Low latency communication and minimal battery consumption are key requirements of many 5G and IoT use cases, including smart transport and critical control of remote devices. Thanks to Ericsson’s 4G/5G research activities and lessons learned from legacy networks, we have identified solutions that address both of these requirements by reducing the amount of signaling required during state transitions, and shared our discoveries with the 3GPP.
This Ericsson Technology Review article explains the why and how behind the new Radio Resource Control (RRC) state model in the standalone version of the 5G New Radio standard, which features a new, Ericsson-developed state called inactive. On top of overcoming latency and battery consumption challenges, the new state also increases overall system capacity by decreasing the processing effort in the network.
Ericsson Technology Review: Cloud-native application design in the telecom do...Ericsson
Cloud-native application design is set to become standard practice in the telecom industry in the near future due to the major efficiency gains it can provide, particularly in terms of speeding up software upgrades and releases. At Ericsson, we have been actively exploring the potential of cloud-native computing in the telecom industry since we joined the Cloud Native Computing Foundation (CNCF) a few years ago.
This Ericsson Technology Review article explains the opportunities that CNCF technology has enabled, as well as unveiling key aspects of our application development framework, which is designed to help navigate the transition to a cloud-native approach. It also discusses the challenges that the large-scale reuse of open-source technology can raise, along with key strategies for how to mitigate them.
Ericsson Technology Review: Service exposure: a critical capability in a 5G w...Ericsson
To meet the requirements of use cases in areas such as the Internet of Things, AR/VR, Industry 4.0 and the automotive sector, operators need to be able to provide computing resources across the whole telco domain – all the way to the edge of the mobile network. Service exposure and APIs will play a key role in creating solutions that are both effective and cost efficient.
The latest Ericsson Technology Review article explores recent advances in the service exposure area that have resulted from the move toward 5G and the adoption of cloud-native principles, as well as the combination of Service-based Architecture, microservices and container technologies. It includes examples that illustrate how service exposure can be deployed in a multitude of locations, each with a different set of requirements that drive modularity and configurability needs.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
Architecture evolution for automation and network programmability
1. The communications technology journal since 1924 2014 • 11
Architecture evolution for automation
and network programmability
November 28, 2014
2. Architecture evolution for
automation and network
programmability
The target architecture of future telecom networks will be designed using sets of aggregated
capabilities. Each domain will have its own set of resources that are abstracted and exposed to other
domains, supporting multi-tenancy and tenant isolation. The result is a fully programmable network,
that has the ability to evolve and adapt to the emerging requirements of the Networked Society.
interfaces and abstractions are critical
to facilitate a split of responsibilities,
support trust relationships and enable
opex efficiency.
This article aims to describe the big
picture of the target ecosystem, pre-senting
an architecture description that
focuses on the inter-domain interfaces,
separation of concerns as well as net-work
programmability.
The ecosystem
The target network architecture will
be built using a set of critical techni-cal
interfaces that support business
relations – which we call inter-domain
interfaces. These interfaces mark the
boundaries between the different layers
or domains of a network; they support
the separation of concerns, interop-erability,
and enable Service Level
Agreements (SLAs). Administrative
domains, as defined by NFV1, are suit-able
for being managed as one entity
from a competence and administrative
responsibility point of view. As Figure 1
illustrates, there are four typical admin-istrative
domains:
transport;
infrastructure and platform services ;
access and network functions; and
business and cross-domain operations.
The target architecture – and in partic-ular
the inter-domain interfaces – serve
as enablers for a multitude of domain
combinations. Many other domain
structures are possible, depending on
the strategy and operational structure
of the operator.
Administrative domains are quite
physical in nature. Traditionally, they
as-a-service models with rapid scalabil-ity
capabilities and greater levels of auto-mation,
the need to focus on the basic
principles will become more significant.
Full programmability of a network
and its services needs to take all the
building blocks of a network into con-sideration:
how each piece will evolve;
how they will interface; and how they
support the structure and business pro-cesses
of an operator.
SDN technologies, for example, are
key enabling tools for network program-mability,
but to provide value they must
be integrated with the end-to-end pro-cess
view of the operator. Cloud orches-tration
technologies are also important
enablers, but without proper interfaces
to business management functions in
place, the result would be a technically
functional but commercially dysfunc-tional
system. Well-defined technical
GÖRAN RUNE, ERIK WESTERBERG, TORBJÖRN CAGENIUS,
IGNACIO MAS, BALÁZS VARGA, HENRIK BASILIER, AND LARS ANGELIN
BOX A Terms and abbreviations
AAA authentication, authorization and
accounting
API application programming interface
APN Access Point Name
BSS business support systems
COMPA control, orchestration, management,
policy and analytics
DC data center
EPC Evolved Packet Core
IGP Internet Gateway Protocol
IPS infrastructure and platform services
MPLS multi-protocol label switching
MTC machine-type communication
MVNO mobile virtual network operator
NFV network functions virtualization
OSS operations support systems
opex operational expenditure
OVF Open Virtualization Format
PaaS platform as a service
POD performance-optimized data centers
R&S routing and switching
SDN software-defined networking
SLA Service Level Agreement
TTM time to market
TTC time to customer
VM virtual machine
vDC virtual data center
VIM Virtualized Infrastructure Manager
Enabled by emerging
technologies like virtualization,
software-defined networking
(SDN) and cloud capabilities,
the architecture of telecom
networks is undergoing a
massive transformation. This is
being driven by several factors,
including the need for less
complex and lower-cost network
operations, shorter time to
customer (TTC) and time to
market (TTM) for new services,
and new business opportunities
built on the anything as a service
(XaaS) model.
The principles of the target architecture
are based on separation of concerns,
multi-tenancy and network program-mability.
As networks progress toward
the target architecture supporting
2
E R I C S S O N R E V I E W • N OVEMBER 28, 2014
Programmable networks
3. tend to consist of physical nodes with
pre-integrated hardware and software
functions. This, however, is changing.
Together, NFV and the separation of
software and hardware have brought
about a new administrative domain:
the infrastructure and platform ser-vices
(IPS) domain. Some administrative
domains – notably transport, access net-work
and the new IPS domain – main-tain
responsibility for hardware and
platforms, while most other network
function domains – such as the Evolved
Packet Core (EPC) – manage only soft-ware
functions.
Even though current network archi-tecture
already includes several inter-domain
interfaces, the evolution to the
target architecture aims to improve
multi-tenancy capabilities, as well as
intra-domain and inter-domain pro-grammability.
This evolution will hap-pen
gradually and to varying degrees
for each domain depending on need –
in terms of value – as well as additional
considerations like legacy equipment
and operational processes.
Key principles of the target
architecture
Developing network architecture so
that it is both highly automated and
programmable requires functionality
to be coordinated across administrative
domains. This can be achieved through
a set of tools to operate each admin-istrative
domain, which have opera-tional
responsibility for the resources
within the domain, as well as the abil-ity
to expose services based on these
resources. In this article we refer to the
combination of these operational tools
as COMPA: control, orchestration, man-agement,
policies and analytics. Each
term has a wider meaning than its leg-acy
definition; all are tightly interlinked
within each administrative domain, as
well as having inter-domain relations.
The COMPA functional groupings are
illustrated in the target architecture
shown in Figure 2.
The main principles of the target
architecture are:
separation of concerns;
abstraction and exposure of capabilities;
multi-tenancy;
intra-domain programmability; and
inter-domain programmability.
Control, orchestration and management
Management and control functions
within each domain will do much the
same job as they do today, but with a
higher degree of automation and real-time
capabilities. Orchestration enables
automation across different types of
resources and uses defined workflows
to provide the desired network behav-ior
– all aligned with and enabled by a
policy framework that is supported by
analytics insights. Creating infrastruc-ture
services is one example of where
orchestration is heavily used in the IPS
domain, in which processing, storage
and networking resources are assigned
in a coordinated manner.
Services from other domains can also
be viewed as resources orchestrated in a
synchronized manner with a domain’s
own resources to provide services in a
hierarchical way. A strict framework
with a common information model is
required to maintain consistency across
domains – illustrated by the vertical-arrow
flow in Figure 2.
Access and network functions
Access Core Services
Control
Orchestration
Management
Policies
Analytics
Transport
Infrastructure and platform
Business
and cross-domain
operations
FIGURE 1 Target architecture with example administrative domains
Control
Orchestration
Management
Policies
Analytics
Control
Orchestration
Management
Policies
Analytics
Control
Orchestration
Management
Policies
Analytics
Control
Orchestration
Management
Policies
Analytics
Transport
Infrastructure
and platform
Access and network
functions
Business and
cross-domain
operations
FIGURE 2 Grouping of COMPA functions in the target architecture
3
E R I C S S O N R E V I E W • N OVEMBER 28, 2014
4. and for real-time stream processing. Domain competence is usually needed to understand prediction, but insights exposed from other domains or external sources could also be used as input.
Exposing analytics insights on a domain basis, and then aggregating multiple domains through a cross-domain analytics application, enables the entire network state to be analyzed; which in turn supports the definition of network- wide KPIs.
A policy engine can use network analytics to check performance-related KPIs, triggering network state updates when needed. Such requests could then be applied to the relevant network domains by the control-orchestration- management functions – possibly with some form of manual intervention.
A closed feedback loop from the control- orchestration-management functionality back to the policy engine would enable policies to learn and adapt automatically as the network environment changes.
Applying the concepts
Transport
In telco networks, the transport domain delivers connectivity services between remote sites and equipment, maintaining topology awareness and services for multiple customers – multi-tenancy. In reality, a transport network consists of a set of interworking administrative domains defined by technology, geography and ownership. The main technologies powering the delivery of connectivity services will be based on IP/MPLS, Ethernet and optical transport; in the access domain, microwave transport may also play a significant role, and IPv6 will be the dominant protocol (as IPv4 becomes more associated with legacy infrastructure). Transport network topology will become flatter with fewer packet hops, as the use of converged IP and optical transport technologies becomes more widespread2.
Traditional connectivity services like residential broadband, mobile backhaul, and enterprise VPNs will coexist with newer services that will provide connectivity for cloud solutions, such as DC-to-DC or user-to-DC. These new generation services and the increased number of connections will drive the need
To offer services that draw resources from more than one domain, a cross-domain OSS/BSS function is needed. This second main flow of orchestration relates to external business offerings and how to leverage services from multiple domains. For example, an enterprise customer may require a service that combines an infrastructure service from the IPS domain with a business VPN from the transport domain – this is shown conceptually by the horizontal arrows in Figure 2.
To support service exposure, each domain needs appropriate logging tools. For example, an IPS domain will need to create and maintain data records related to usage for the infrastructure services it provides – regardless of whether it delivers these services to an external tenant or to an internal tenant (to other domains within the same operator). Many of these functions will be automated and simplified in their interfaces among staff, OSS/BSS, and resource control functions.
The policy framework
Policies are sets of rules that govern the behavior of a system. A policy comprises conditions and actions; events trigger conditions to be evaluated and actions are taken if the conditions are met. Policies are used to define a framework and set the bounds for the control- orchestration-management functions, derived from the overall business goals of the operator.
Some policies, like those that control how specific resources are used, are strictly defined and applied within an administrative domain. Other policies apply to the inter-domain interfaces, and define for example how one domain can use services from another. Such policies can be partly defined by the administrative domain delivering the service, but may also be defined by the administrative domain for business and cross-domain operations. Figure 3 shows how policies originate from the overall business objectives of the operator and how they relate to different levels within the operator structure.
The relationship between business and network operations policies is defined by a set of meaningful operational KPIs. For example, a business policy governing the parameters of a gold subscriber service can be interpreted into specific settings for, say, QoS in the network. By factoring in the insights supplied by analytics, these operational KPIs enable a greater degree of network automation, and allow policies to govern operational decisions.
Network analytics
Analytics is therefore a key tool for increasing automation of operations. To provide insights, predictions, as well as supporting automation in other ways, analytics can be applied within an administrative domain or work in conjunction with the other COMPA functions – both in offline processing of data
System level policies peradministrative domainStrategic, tactical and commercial policies: Business and cross-domain operationsDetailed policies: Network functions levelOperator levelPolicy administrative domainsNetwork functions (NF groups)
FIGURE 3 Policy framework
4
ERICSSON REVIEW • NOVEMBER 28, 2014Programmable networks
5. for more flexible and dynamic ways to operate the transport domain.
A number of key components are needed to support evolved architectural principles and facilitate both intra-domain and inter-domain programmability. These components include SDN and network virtualization technologies3, which allow connectivity services to be deployed and controlled in a flexible way.
Programmability in the transport domain will ensure a suitable level of resource abstraction, exposure and control so that other administrative domains can request transport services according to established SLAs. Programmability can be achieved by using northbound SDN-based interfaces, for example, and can be further increased by leveraging the benefits of data/control plane separation.
As shown in Figure 4, several scenarios regarding what parts of a transport node can be SDN controlled. These scenarios lead to multiple possible paths and intermediate steps to transform a traditional transport network into a network that is fully SDN-controlled – in which only a limited set of functions are local to the transport node. Using SDN controllers will not only result in the introduction of new functions and services into transport nodes, but existing control functionalities will be moved to the SDN controller – replacing current local- node implementations.
Migrating an existing transport network to an SDN-based architecture requires hybrid operational modes that apply SDN-based control capabilities onto the existing (protocol-driven local node) transport infrastructure. The capabilities that are included depend on the level of centralization versus distribution of functions that the operator chooses for its transport domain.
The resulting transport domain – in the context of packet-optical integration – combines increased programmability (enabled by SDN technologies) with the simpler, more cost-efficient IP and optical components, and is detailed in a previous Ericsson Review article2. The evolved transport domain enables faster service deployment and reduces operational complexity.
Infrastructure and platform services
As networks evolve, telecom solutions and systems will increasingly be built using on-demand elastic infrastructure and platform services rather than dedicated and managed infrastructure and software. To leverage the benefits of this model, a split in responsibility between the provider of such services and the users (tenants) is necessary. The provider role is taken by what we refer to in this article as the IPS domain, which is a new domain type that provides infrastructure and platform services using owned or leased resources.
One of the key services offered by the IPS domain is a structured collection of virtual computational processing, storage and networking resources, within what is referred to as virtual data center (vDC). The vDC interface separates logical telecom nodes from the actual physical infrastructure, using concepts like virtual machines, virtual network overlays, baremetal, and storage services.
Networking capabilities exposed to tenants will be rich enough to support a wide set of telco functions, including L2 and L3 VPN interworking and SDN- controlled service chaining4. The IPS domain can also take the administrative responsibility for common network functions (such as DNS, firewalling, DHCP, and load balancing) and offer these as services, orderable as products deployable in a vDC.
In addition, the IPS domain can also supply services to applications, providing an execution framework (PaaS) and network APIs that expose underlying network capabilities. For example, common network functions can be exposed and made programmable by applications. Inter-domain programmability and abstraction increases application development productivity and reduces lead times. In addition, the IPS domain will support migration by providing interconnectivity with non-virtualized networks as well as mixed
PortTransportfunctionPortTransportfunctionOpticalTransportfunctionOpticalServicefunctionTransportfunctionSDNcontrollerHybrid SDNlegacy mode(packet) IGPIGPHybrid SDNlegacy mode(IP+optical) Full SDN mode(packet) Full SDN mode(IP+optical) SDNcontrollerSDNcontrollerSDNcontrollerServicefunctionServicefunctionServicefunctionOpticalTransportServiceOpticalServiceTransportServiceService
FIGURE 4 Scenarios for control plane and data plane separation for packet,
and IP/optical transport networks 5
ERICSSON REVIEW • NOVEMBER 28, 2014
6. deployments of non-virtualized, virtualized and PaaS-based applications.
All the capabilities of the vDC and application services are orderable by tenants through policy-controlled inter-domain interfaces, and all of the capabilities can be requested, monitored and maintained/scaled through these interfaces. The interfaces will rely heavily on modeling of the (sometimes complex) sets of capabilities, using OVF descriptors, for example, and forwarding descriptors for service chaining.
Within the IPS domain, overall functions in the COMPA category will act across a wide set of resources in the underlying infrastructure.
Using orchestration technologies, for example, suitable abstractions can be provided to tenants using a heterogeneous set of resources – which allows tenants to manage and program resources without requiring any lower level implementation details. Policies and analytics may then be used to ensure that resources are used efficiently, while respecting SLAs and business requirements.
The physical resources that expose virtual resources to tenants may be organized into infrastructure resource zones, each with their own functions (VIM in ETSI NFV terminology) acting within the zone – such as OpenStack and SDN controllers. Some or all such zones may be external to the IPS domain. Another option is to use similar services from another IPS domain or service provider, where orchestration capabilities deliver a consolidated service. The transport domain may be used for inter-connectivity of infrastructure resource zones at different data center sites or to connect infrastructure resource zones to external networks. In both cases, the IPS domain interacts with the transport domain, based on frame agreements, to request or dynamically adapt WAN connections.
As shown in Figure 5, the IPS domain relies on several arbitrarily distributed DC sites, which contain a number of PODs – blocks of computational, storage and networking resources. Typically, a POD corresponds to an infrastructure resource zone. To deliver consolidated and distributed vDCs, the overall orchestrator can request resources across the PODs through their VIM functions.
The IPS domain offers abstracted services (the vDCs and application services), multi-tenancy with isolation of resources, security and SLAs associated with these services. It allows for intra- domain programmability and automation via the VIM (OpenStack), SDN for the connectivity resources and the COMPA functions for resource and service orchestration across infrastructure resource zones and to external providers. It also offers inter-domain programmability where tenants have access to interfaces for controlling – within frame agreements – their instances of the vDC and application services, supporting for example scaling, tenant SDN control or access to telco network capabilities. The interface between the IPS domain and its tenants needs to be open and, where applicable, standardized to support a full business ecosystem between IPS-domain service providers and its tenants, with a minimum amount of system integration between the two. Indeed, this appears to be one of the main tasks of the NFV forum.
Network functions
Most network functions of the logical telecom architecture shown in Figure 6 benefit from using services from the IPS domain. The separation of network functions from platforms can result in significant operational gain – primarily through automated routines for backup and restore, capacity planning, hardware handling and a general reduction in the number of platforms to be managed. This has a direct impact on TTM for new services, which can be reduced from up to a year down to a few months as the introduction process no longer depends on platform introduction. Auto scaling of the infrastructure and platform services and programmability of the network functions removes much of the manual work associated with fulfillment, which greatly reduces the TTC.
The original design of mobile network architecture in 3GPP supports a certain
ExternalinfrastructureserviceproviderTransportAppframeworkPODPODPODPODDCinterconnectDCinterconnectPlatformresourcesVIMHW/OS(v) switchVirtual- izationCOMPATenant domainOverall IPSfunctionsInfrastructure resourcezone or providerData site center 1Data site center 2
FIGURE 5 Infrastructure and platform services domain
6
ERICSSON REVIEW • NOVEMBER 28, 2014Programmable networks
7. level of programmability, abstraction and multi-tenancy. Standardized interfaces between the RAN, EPC and IMS domains support automation in bearer service handling and a set of MVNO solutions at various levels. The Rx interface enables rudimentary inter-domain programming to the PCRF from outside the EPC domain, while the APN structure provides a foundation for multi-tenancy. However this is not sufficient, network functions architecture is evolving to increase support for COMPA functions. Introducing the infrastructure and platform services are a significant step in this direction, but additional architectural changes and interface improvements are also part of the wider picture.
Separating network functions from the platforms allows the capacity of a given network function system – such as an EPC system – to scale up or down by simply adjusting the capacity of the vDC to achieve the wanted capacity of the EPC system. The multi-tenancy of the vDC service also means that multiple EPC systems can be instantiated in parallel in separate vDCs.
Figure 7 illustrates how deploying a multitude of EPCs in different vDCs provides full isolation of the EPC instances, inherited from the tenant isolation built into the vDC service from the IPS domain. Isolation makes both service exposure and inter-domain programmability to EPC instances safer – opening up programmability to one instance does not impact others, and exposure of data from the EPC system to a customer or partner is limited to that of the associated EPC system instance. Implementing isolation in this way minimizes risk and reduces the cost for troubleshooting faulty services.
For operations in multiple markets, one EPC system can be instantiated per market, with a central responsibility for the EPC domain, but with selected programmability suitable for the demands of the given market. This is a cost-efficient approach with consolidated competence and responsibility, while still allowing different operational entities to control selected features of the EPC system – such as rules for charging or subscription.
Instantiating a VoLTE system5, for example, can enable an operator to offer communication services to enterprises, emergency services or any other industry with full isolation and varying degrees of programmability. To support this use case, network architecture needs to evolve to the target architecture. In particular, additional inter-domain interfaces (to enable programmability and automated orchestration) are needed to instantiate the relevant subsystems and combine them into service solutions.
The evolution of the network functions integrates well with 5G radio evolution6. Next generation networks will support legacy services as well as new services like enhanced mobile broadband, massive machine-type communication (MTC), as well as mission-critical MTC. Future networks will need to support a vast number and a much more diverse set of use cases. Consequently, service creation that is platform-independent and flexible, based on programmability and automation is key. A massive range of industries will depend on 5G networks – all with different requirements for characteristics, security, analytics and cost. Meeting all of these needs is a strong driver for multi- tenancy, isolation, and instantiation of services and resources.
Extending instantiation capabilities to work across multiple domains may enable novel business offerings to be created. If, for example, an instance of an EPC system is integrated with a VoLTE system instance, the two are then connected to an IP VPN, and finally
ePDGGWTDFSCCFAAAHSS/ HLRUDRDomainmgmt. OSSBSSExposeUser data managementOSS/BSSServiceenablementPacket coreMME/ SGSNS/PDNGWeMBMSGWPCRFMedia servicesMediadeliveryMobilebroadcastIMStelephonyIMSmessageCommunication servicesMobileCSIMScoreOther servicesServerServer
FIGURE 6 Logical telecom architecture
7
ERICSSON REVIEW • NOVEMBER 28, 2014
8. all three are associated with an isolated and SLA controlled radio-access service; the result is an isolated, and SLA-controlled logical instance of the complete network. Such logical network instances can be offered to an industry, to an MVNO or an enterprise. As each network instance is isolated, it is safe to open up interfaces to each instance to enable each customer or partner to program selected properties of the logical network instance, and to do this in real time.
To reach the point where a network can be offered as a programmable service requires a cost-efficient way to connect services – and eventually resources – from the various domains into logical network instances. As described at the beginning of this article, to connect services in such a cost-efficient way requires inter-domain programmability and more generally a network- wide architecture for cross-domain orchestration and management, while maintaining per-domain responsibility and accountability.
Conclusions
Increased levels of automation and programmability are transforming network architecture. This transformation is being driven by expected gains in operational efficiency and reduced TTM for new services, reduced TTC, and new business, as well as by the fact that enabling technologies such as virtualization and SDN are gaining maturity.
The target architecture is built on interfaces that support the principles of service and resource abstraction, multi- tenancy and programmability. Inter- domain interfaces also support business relations, as they include security and SLAs, as well as separation of responsibility and accountability.
As a first important transformation step toward the target architecture, many network functions will be managed in similar way as any other virtualized software: following virtualization management principles in line with ETSI NFV specifications. Initially virtualized network functions will be operated in parallel with legacy nodes, and DC operations as well as maintenance will be automated to a much larger degree than it is today.
In the longer term, the architecture should be able to provide the desired level of automation and network programmability. Full programmability of the network and its services requires the inter-domain interfaces as well as the domains to evolve. To achieve the full gain of the network architecture transformation, the related internal operator processes (like workflow, operation, and maintenance processes) will need to be adjusted. Technologies like SDN and cloud orchestration are crucial enablers and tools for automation
Business agreementinterfaces, ratherstatic, not automatedIsolated per-tenantEPC instancesBusiness frame agreementinterfaces, non-real time, not automatedAPIs within frameagreement, real-timeand programmableCurrent architectureTarget architectureBusiness managementBusiness and cross-domainoperationsManagementconfigurationinterfaceEPCEPCEPCCOMPAR&SProcessStoreBSSExposeExposeCOMPAX-domCOMPA
FIGURE 7 Architecture evolution
8
ERICSSON REVIEW • NOVEMBER 28, 2014Programmable networks
9. 1.
ETSI, 2014, Draft Group Specification, Security and Trust Guidance, NFV ISG Spec, available at: http://docbox. etsi.org/isg/nfv/open/Latest_Drafts/nfv-sec003v111 security and trust guidance.pdf
2.
Ericsson Review, May 2014, IP-optical convergence: a complete solution,available at: http://www.ericsson.com/ news/140528-er-ip-optical-convergence_244099437_c
3.
Ericsson Review, February 2013, Software-defined networking: the service provider perspective, available at: http://www.ericsson.com/news/130221- software-defined-networking-the-service-provider- perspective_244129229_c
4.
Ericsson Review, March 2014, Virtualizing network services – the telecom cloud, available at: http://www. ericsson.com/news/140328-virtualizing-network- services-the-telecom-cloud_244099438_c
5.
Ericsson Review, July 2014, Communications as a cloud service: a new take on telecoms, available at: http://www. ericsson.com/news/140722-communications-as-a- cloud-service-a-new-take-on-telecoms_244099436_c
6.
Ericsson Review, June 2014, 5G Radio Access, available at: http://www.ericsson.com/ news/140618-5g-radio-access_244099437_c
References
network programmability, but network operations and services also need to be controlled through operational policies linked to business policies.
Due to the impact on operator processes and potentially even the business ecosystem it is likely that the transformation will take place in a stepwise manner over a significant period of time – with different parts of the network evolving at different rates. In addition, the resulting network architecture will support 5G radio evolution and the associated use cases and requirements.
BOX B Main principles of the target architecture
Separation of concerns
Each domain has full responsibility over the resources and operations performed inside the domain.
Exposure and abstraction of capabilities
The abstraction of functions into APIs that are exposed as services supports domain inter-operability, which enables automation and programmability.
Multi-tenancy
Each domain offers full isolation of how the different users (tenants) use domain resources.
Intra-domain programmability
This is achieved by leveraging automation and programmability within an administrative domain through its COMPA functions.
Inter-domain programmability
Each domain exposes capabilities and services using well- defined APIs to achieve an end-to-end service offering, orchestrated by the cross-domain COMPA functionality.
9
ERICSSON REVIEW • NOVEMBER 28, 2014
10. Torbjörn Cagenius is an expert in distributed network architecture at Business Unit Cloud and IP. He joined Ericsson in 1990 and has worked in a variety of technology areas such as FTTH, main-remote RBS, FMC, IPTV, network architecture evolution, SDN and NFV. In his current role, he focuses on cloud impact on network architecture evolution. He holds an M.Sc. from KTH Royal Institute of Technology, Stockholm, Sweden.
Göran Rune is a principal researcher at Ericsson Research. His current focus is the functional and deployment architecture of future networks, primarily 5G. Before joining Ericsson Research, he held a position as an expert in mobile systems architecture at Business Unit Networks focusing on the end-to-end aspects of LTE/EPC, as well as various systems and network architecture topics. He joined Ericsson in 1989 and has held various systems management positions, working on most digital cellular standards, including GSM, PDC, WCDMA, HSPA, and LTE. From 1996 to 1999, he was a product manager at Ericsson in Japan, first for PDC and later for WCDMA. He was a key member of the ETSI SMG2 UTRAN Architecture Expert group and later 3GPP TSG RAN WG3 from 1998 to 2001, standardizing the WCDMA RAN architecture. He studied at the Institute of Technology at Linköping University, Sweden, where he received an M. Sc. in applied physics and electrical engineering and a Lic. Eng. in solid state physics.
Erik Westerberg joined Ericsson from MIT, Massachusetts, the US, in 1996 and currently holds the senior expert position in system and network architecture. In his first 10 years at Ericsson, he worked with the development of mobile broadband systems before broadening his scope to include the full network architecture, serving as chief network architect until 2014. He holds a Ph.D. in quantum physics from Stockholm University, Sweden.
Ignacio Mas is a system architect at Group Function Technology and an expert in network architecture. He holds a Ph.D. in telecommunications from KTH Royal Institute of Technology, Stockholm, and an M.Sc. from both KTH and the Technical University of Madrid (UPM). He joined Ericsson in 2005 and has worked in IETF standardization, IPTV and messaging architectures, as well as media-related activities for Ericsson Research. He is a member of the Ericsson System Architect Program (ESAP) and has research interests in QoS, multimedia transport, signaling and network security, IPTV and, most recently in cloud computing.
Balázs Varga joined Ericsson in 2010 and he is an expert in multiservice networks at Ericsson Research. His focus is on packet evolution studies to integrate IP, Ethernet and MPLS technologies for converged mobile and fixed network architectures. Prior to Ericsson, he worked for Magyar Telekom on the enhancement of broadband services portfolio and introduction of new broadband technologies. He has many years of experience in fixed and mobile telecommunication and also represents Ericsson in standardization. He holds a Ph.D. in telecommunication from the Budapest University of Technology and Economics, Hungary.
Henrik Basilier is an expert at Business Unit Cloud and IP. He has worked for Ericsson since 1991 in a wide range of areas and roles. He is currently engaged in internal R&D studies and customer cooperation in the areas of cloud, virtualization and SDN. He holds an M.Sc. in computer science and technology from the Institute of Technology at Linköping University, Sweden.
Lars Angelin is an expert in the multimedia management technology area at Business Unit Support Solutions. He has more than 28 years of experience in the areas of concept development, architecture and strategies within telecom and education. He joined Ericsson in 1996 as a research engineer, and in 2003 he moved to the position of concept developer for telco-near applications, initiating and driving activities mostly related to M2M and OSS/BSS. He holds an M.Sc. in engineering physics and a Tech. Licentiate in tele-traffic theory from Lund Institute.
Acknowledgements
The authors gratefully acknowledge their colleagues who have contributed to
this article: Jaume Rius i Riu and Ulf Olsson.
10
ERICSSON REVIEW • NOVEMBER 28, 2014
Programmable networks