Architecture evolution for automation and network programmabilityEricsson
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.
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.
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.
Dynamic Shaping Method using SDN And NFV ParadigmsIJCNCJournal
Traffic shaping controls communication traffic flow to prevent a specified communication rate from being exceeded. In conventional networks, the traffic shaping device is implemented at a predetermined location and only a communication flow passing through the device is targeted. If the traffic can be shaped dynamically on any selected communication flows at the optimal point only when necessary, it could use network bandwidths and packet relay processing capacity more efficiently and flexibly.
This paper proposes a dynamic shaping method using Software-Defined Networking (SDN) and Network Functions Virtualization (NFV) paradigms, which selects the optimal communication flows to be shaped, and the optimal shaping points dynamically. This paper also presented system configuration and functions for the proposed dynamic shaping, and the method to simplify the process of collecting the traffic data of each communication flow by SDN controller.
Architecture evolution for automation and network programmabilityEricsson
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.
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.
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.
Dynamic Shaping Method using SDN And NFV ParadigmsIJCNCJournal
Traffic shaping controls communication traffic flow to prevent a specified communication rate from being exceeded. In conventional networks, the traffic shaping device is implemented at a predetermined location and only a communication flow passing through the device is targeted. If the traffic can be shaped dynamically on any selected communication flows at the optimal point only when necessary, it could use network bandwidths and packet relay processing capacity more efficiently and flexibly.
This paper proposes a dynamic shaping method using Software-Defined Networking (SDN) and Network Functions Virtualization (NFV) paradigms, which selects the optimal communication flows to be shaped, and the optimal shaping points dynamically. This paper also presented system configuration and functions for the proposed dynamic shaping, and the method to simplify the process of collecting the traffic data of each communication flow by SDN controller.
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).
Dynamic Traffic Management Services to Provide High Performance in IntelRate ...IJMER
Abstract: Traffic is the chief puzzle problem in which every country faces to elaborate sending a
number of packets throughout the world. This paper proposes a new speculation for distributed traffic
management by availing the presumption of fuzzy logic. The routers are established by using an
IntelRate Controllers to manage the traffic congestion in the networks dynamically. Fuzzy logic is used
to previse the maximum allowable sending rate by observing the queue size of router. The network
traffic control protocol is unique to estimate the network parameter which involves link latency,
bottleneck bandwidth or packet loss rate in order to compute the allowed source sending rate. The fuzzy
logic based controller can measure queue size directly, it neglects various potential performance issues
arising due to parameter estimation as reduce consumption of computation and memory resource in
router. A network parameter, the queue size can be viewed accurately and if action should be taken to
regulate the source sending rate and it increases the resilience of the network to traffic congestion.
Using the fuzzy logic technique, QoS (Quality of Service) can achieve better performance than the
existing protocol that depends on the estimation of network parameter, to make the network more
adaptive for current traffic conditions.
Since the REST is the new arena in the SOA world, this presentation will give very good intro all such details which basically tells the choice between REST and SOAP
Talhunt is a leader in assisting and executing IEEE Engineering projects to Engineering students - run by young and dynamic IT entrepreneurs. Our primary motto is to help Engineering graduates in IT and Computer science department to implement their final year project with first-class technical and academic assistance.
Project assistance is provided by 15+ years experienced IT Professionals. Over 100+ IEEE 2015 and 200+ yester year IEEE project titles are available with us. Projects are based on Software Development Life-Cycle (SDLC) model.
Network services are services that specialize in the handling of network-related or network-resident resources. Examples of network services are data transport service, network advance reservation service, network Quality of Service (QoS) service, network information service, network monitoring service, and AAA1 service.
This informational draft describes how several network services combine and yield a rich mediation function—a resource manager—between grid applications and legacy networks. Complements of these services, the network resource is seen joining CPU and storage as a first-class, grid-managed resource (and handled, as such, by a community scheduler, or other OGSA services).
Enhancing qo s and qoe in ims enabled next generation networksgraphhoc
Managing network complexity, accommodating greater numbers of subscribers, improving coverage to support data services (e.g. email, video, and music downloads), keeping up to speed with fast-changing technology, and driving maximum value from existing networks – all while reducing CapEX and OpEX and ensuring Quality of Service (QoS) for the network and Quality of Experience (QoE) for the user. These are just some of the pressing business issues faced by mobileservice providers, summarized by the demand to “achieve more, for less.” The ultimate goal of optimization techniques at the network and application layer is to ensure End-user perceived QoS. The next generation networks (NGN), a composite environment of proven telecommunications and Internet-oriented mechanisms have become generally recognized as the telecommunications environment of the future. However, the nature of the NGN environment presents several complex issues regarding quality assurance that have not existed in the legacy environments (e.g., multi-network, multi-vendor, and multi-operator IP-based telecommunications environment, distributed intelligence, third-party provisioning, fixed-wireless and mobile access, etc.). In this Research Paper, a service aware policy-based approach to NGN quality assurance is presented, taking into account both perceptual quality of experience and technologydependant quality of service issues. The respective procedures, entities, mechanisms, and profiles are discussed. The purpose of the presented approach is in research, development, and discussion of pursuing the end-to-end controllability of the quality of the multimedia NGN-based communications in an environment that is best effort in its nature and promotes end user’s access agnosticism, service agility, and global mobility
A distributed system can be viewed as an environment in which, number of computers/nodes are connected and resources are shared among these computers/nodes. But unfortunately, distributed systems often face the problem of traffic, which can degrade the performance of the system. Traffic management is used to improve scalability and overall system throughput in distributed systems using Software Defined Network (SDN) based systems. Traffic management improves system performance by dividing the work traffic effectively among the participating computers/nodes. Many algorithms were proposed for traffic management and their performance is measured based on certain parameters such as response time, resource utilization, and fault tolerance. Traffic management algorithms are broadly classified into two categories- scheduling and machine learning traffic management. This work presents the study of performance analysis of traffic management algorithms. This analysis can further help in the design of new algorithms. However, when multiple servers are assigned to compile the mysterious code, different kinds of techniques are used. One common example is traffic management. The processes are managed based on power efficiency, networking bandwidth, Processor speed. The desired output will again send back to the developer. If multiple programs have to be compiled then appropriate technique such as scheduling algorithm is used. So the compilation process becomes faster and also the other process can get a chance to compile. SDN based clustering algorithm based on Simulated Annealing whose main goal is to increase network lifetime while maintaining adequate sensing coverage in scenarios where sensor nodes produce uniform or non-uniform data traffic.
SCALABLE AND ENERGY EFFICIENT TASK OFFLOADING SCHEMES FOR VEHICULAR CLOUD COM...IJCNCJournal
Smart vehicles of today on road are equipped with advanced computational units, multiple communication technologies, intelligent sensing platforms, and human-computer interaction devices which utilize Vehicular Edge Networks to support services offered by the remote cloud. This being named as
Opportunistic Vehicular Edge Computing recently, has the possibility to supplement the services provided by the Edge gadgets. Many Vehicular Edge Computing architectures have been proposed as of late which support task offloading. One among the premier difficulties in these networks is efficiently utilizing the resources available at the vehicular nodes. The present work uses APEATOVC, a conveyed and versatile
protocol for economical, efficient and effective task offloading in these networks which address the adaptability of vehicular clouds. The results obtained by extensive simulations are presented to assess and contrast its performance with existing protocols.
Service Level Agreements (SLAs) represent service management contracts that are processed by monitoring and measurement mechanisms for the evaluation of the signatories adherence to the agreed service levels during service execution. The paper discusses SLA data management characteristics that need to be considered in the design of data models for SLA documents. The SLA anatomy is introduced with respect to the Web Service Level Agreement (WSLA) [1] language specification. Furthermore, the paper highlights current obstacles for the integration of automated SLA management in the cloud business setting. The contributed SLA data analysis maps SLA terms to data management attributes according to their operational relevance during the SLA activity. We present an SLA digraph model for the automated SLA formulation and data handling. The SLA digraph is introduced as a programming module that sits on the application layer and communicates with backend data stores for the SLA persistence.
In the present atmosphere of tighter budgets and pressure on resources, many public sector organiza-tions, including local authorities, are outsourcing services to outer organizations under service level agreements in cloud computing. Cloud computing is an approach to convey facilitated benefits over the web. Services are available to the users relying upon cloud arrangement and the Service Level Agreement (SLA) between the service providers and the cli-ents. Service level agreements are being utilized inside associations, directing connection between various sections of the association. It requires a commitment from both parties to support and adhere to the agreement in order for the SLA to work effectively. In spite of the fact that it gives a straightforward view about the cloud condition, such as cloud services, cloud distribution, security issues, responsibilities, agreements and warranties of the services. However, there are several issues occur from incorrect SLA which can cause misunderstanding among service providers and clients. SLA checking device confirm the SLA effectively whether it deals with all administrations as per SLA. In this paper, we represent a SLA confirmation and checking process that can distinguish SLA verification in gathering the information. We consider IaaS (Infrastructure as a Service) parameters for SLA verification in Cloud.
Service Oriented Software Engineering: Services as reusable components, Service Engineering, Software Development with Services. Service-oriented architectures, RESTful services
below one was the example for SDN as per my knowledge, if useful ple.pdfannethafashion
below one was the example for SDN as per my knowledge, if useful please give reward points.
Verizon SDN-NFV Based Network:
The following are key features of the network based on SDN and NFV:
Enhancements to the Software Defined Networking (SDN) Concept :
The fundamental concept of ‘Software Defined Networking’ (SDN) changes the current network
design paradigm by introducing network programmability and abstraction. In its initial, narrow
definition, SDN is about separating the network control and data planes in L1, L2, L3, and L4
switches. This enables independent scaling of control plane resources and data plane resources,
maximizing utilization of hardware resources. In addition, control plane centralization reduces
the number of managed control plane instances, simplifies operations, and enables orchestration.
The idea of centralized network control can be generalized, resulting in the broader definition of
SDN: the introduction of standard protocols and data models that enable logically centralized
control across multivendor and multi-layer networks. Such SDN Controllers expose abstracted
topology and service data models towards northbound systems, simplifying orchestration of end-
to-end services and enabling the introduction of innovative applications that rely on network
programmability.
Platform SDN Considerations:
Network changes are initiated by the VIM to provide VNFC connectivity and establish service
chains between VNFs as instructed by EEO. The VIM and the DC SDN controller communicate
using common interfaces to implement the necessary networking changes.
Scope of Control – SDN controller vs. other NFV system elements:
The interface between End-to-End Orchestration, non-network controllers (like non-network
OpenStack services) and the network controller is important for interoperability. There are
efforts currently underway in ONF, Open Daylight, ONOS, OpenStack, IETF, and elsewhere to
implement a common Northbound Interface (NBI) to support operator critical use cases. The
primary purpose of the SDN controller is to (re)establish some clean layering between
subsystems that exclusively control their respective resources. The DC SDN controller
subsystem (VIM + SDN Controller) is responsible for controlling connectivity, QoS, path
selection, selection of VNF network placement, inter- VNFC connections, etc. In the ETSI
definition of Forwarding Graphs (FG), the FG passed to the network controller only specifies the
types/flavors of VNFs to use for specific subscriber traffic and the order in which to apply VNFs
of various types/flavors. This allows the SDN controller to have latitude in deciding how best to
satisfy the functional requirements of a given forwarding graph. In addition, this clean layering
of decision making allows for network changes and faults that would be service impacting to be
healed within the network control plane without requiring interaction and direction from the
orchestration layer. The software systems outs.
This paper is written to give basic knowledge of Network function virtualisation in network system. In this paper the work on NFV done till now has been collaborated. It describes how the challenges faced by industry lead to NFV and what is meaning of NFV and NFV architecture model. It also explains NFV Infrastructure is managed and the forwarding path on which packets traverse in NFV. A relationship of NFV with SDN and current research ongoing on NFV policies is discussed.
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).
Dynamic Traffic Management Services to Provide High Performance in IntelRate ...IJMER
Abstract: Traffic is the chief puzzle problem in which every country faces to elaborate sending a
number of packets throughout the world. This paper proposes a new speculation for distributed traffic
management by availing the presumption of fuzzy logic. The routers are established by using an
IntelRate Controllers to manage the traffic congestion in the networks dynamically. Fuzzy logic is used
to previse the maximum allowable sending rate by observing the queue size of router. The network
traffic control protocol is unique to estimate the network parameter which involves link latency,
bottleneck bandwidth or packet loss rate in order to compute the allowed source sending rate. The fuzzy
logic based controller can measure queue size directly, it neglects various potential performance issues
arising due to parameter estimation as reduce consumption of computation and memory resource in
router. A network parameter, the queue size can be viewed accurately and if action should be taken to
regulate the source sending rate and it increases the resilience of the network to traffic congestion.
Using the fuzzy logic technique, QoS (Quality of Service) can achieve better performance than the
existing protocol that depends on the estimation of network parameter, to make the network more
adaptive for current traffic conditions.
Since the REST is the new arena in the SOA world, this presentation will give very good intro all such details which basically tells the choice between REST and SOAP
Talhunt is a leader in assisting and executing IEEE Engineering projects to Engineering students - run by young and dynamic IT entrepreneurs. Our primary motto is to help Engineering graduates in IT and Computer science department to implement their final year project with first-class technical and academic assistance.
Project assistance is provided by 15+ years experienced IT Professionals. Over 100+ IEEE 2015 and 200+ yester year IEEE project titles are available with us. Projects are based on Software Development Life-Cycle (SDLC) model.
Network services are services that specialize in the handling of network-related or network-resident resources. Examples of network services are data transport service, network advance reservation service, network Quality of Service (QoS) service, network information service, network monitoring service, and AAA1 service.
This informational draft describes how several network services combine and yield a rich mediation function—a resource manager—between grid applications and legacy networks. Complements of these services, the network resource is seen joining CPU and storage as a first-class, grid-managed resource (and handled, as such, by a community scheduler, or other OGSA services).
Enhancing qo s and qoe in ims enabled next generation networksgraphhoc
Managing network complexity, accommodating greater numbers of subscribers, improving coverage to support data services (e.g. email, video, and music downloads), keeping up to speed with fast-changing technology, and driving maximum value from existing networks – all while reducing CapEX and OpEX and ensuring Quality of Service (QoS) for the network and Quality of Experience (QoE) for the user. These are just some of the pressing business issues faced by mobileservice providers, summarized by the demand to “achieve more, for less.” The ultimate goal of optimization techniques at the network and application layer is to ensure End-user perceived QoS. The next generation networks (NGN), a composite environment of proven telecommunications and Internet-oriented mechanisms have become generally recognized as the telecommunications environment of the future. However, the nature of the NGN environment presents several complex issues regarding quality assurance that have not existed in the legacy environments (e.g., multi-network, multi-vendor, and multi-operator IP-based telecommunications environment, distributed intelligence, third-party provisioning, fixed-wireless and mobile access, etc.). In this Research Paper, a service aware policy-based approach to NGN quality assurance is presented, taking into account both perceptual quality of experience and technologydependant quality of service issues. The respective procedures, entities, mechanisms, and profiles are discussed. The purpose of the presented approach is in research, development, and discussion of pursuing the end-to-end controllability of the quality of the multimedia NGN-based communications in an environment that is best effort in its nature and promotes end user’s access agnosticism, service agility, and global mobility
A distributed system can be viewed as an environment in which, number of computers/nodes are connected and resources are shared among these computers/nodes. But unfortunately, distributed systems often face the problem of traffic, which can degrade the performance of the system. Traffic management is used to improve scalability and overall system throughput in distributed systems using Software Defined Network (SDN) based systems. Traffic management improves system performance by dividing the work traffic effectively among the participating computers/nodes. Many algorithms were proposed for traffic management and their performance is measured based on certain parameters such as response time, resource utilization, and fault tolerance. Traffic management algorithms are broadly classified into two categories- scheduling and machine learning traffic management. This work presents the study of performance analysis of traffic management algorithms. This analysis can further help in the design of new algorithms. However, when multiple servers are assigned to compile the mysterious code, different kinds of techniques are used. One common example is traffic management. The processes are managed based on power efficiency, networking bandwidth, Processor speed. The desired output will again send back to the developer. If multiple programs have to be compiled then appropriate technique such as scheduling algorithm is used. So the compilation process becomes faster and also the other process can get a chance to compile. SDN based clustering algorithm based on Simulated Annealing whose main goal is to increase network lifetime while maintaining adequate sensing coverage in scenarios where sensor nodes produce uniform or non-uniform data traffic.
SCALABLE AND ENERGY EFFICIENT TASK OFFLOADING SCHEMES FOR VEHICULAR CLOUD COM...IJCNCJournal
Smart vehicles of today on road are equipped with advanced computational units, multiple communication technologies, intelligent sensing platforms, and human-computer interaction devices which utilize Vehicular Edge Networks to support services offered by the remote cloud. This being named as
Opportunistic Vehicular Edge Computing recently, has the possibility to supplement the services provided by the Edge gadgets. Many Vehicular Edge Computing architectures have been proposed as of late which support task offloading. One among the premier difficulties in these networks is efficiently utilizing the resources available at the vehicular nodes. The present work uses APEATOVC, a conveyed and versatile
protocol for economical, efficient and effective task offloading in these networks which address the adaptability of vehicular clouds. The results obtained by extensive simulations are presented to assess and contrast its performance with existing protocols.
Service Level Agreements (SLAs) represent service management contracts that are processed by monitoring and measurement mechanisms for the evaluation of the signatories adherence to the agreed service levels during service execution. The paper discusses SLA data management characteristics that need to be considered in the design of data models for SLA documents. The SLA anatomy is introduced with respect to the Web Service Level Agreement (WSLA) [1] language specification. Furthermore, the paper highlights current obstacles for the integration of automated SLA management in the cloud business setting. The contributed SLA data analysis maps SLA terms to data management attributes according to their operational relevance during the SLA activity. We present an SLA digraph model for the automated SLA formulation and data handling. The SLA digraph is introduced as a programming module that sits on the application layer and communicates with backend data stores for the SLA persistence.
In the present atmosphere of tighter budgets and pressure on resources, many public sector organiza-tions, including local authorities, are outsourcing services to outer organizations under service level agreements in cloud computing. Cloud computing is an approach to convey facilitated benefits over the web. Services are available to the users relying upon cloud arrangement and the Service Level Agreement (SLA) between the service providers and the cli-ents. Service level agreements are being utilized inside associations, directing connection between various sections of the association. It requires a commitment from both parties to support and adhere to the agreement in order for the SLA to work effectively. In spite of the fact that it gives a straightforward view about the cloud condition, such as cloud services, cloud distribution, security issues, responsibilities, agreements and warranties of the services. However, there are several issues occur from incorrect SLA which can cause misunderstanding among service providers and clients. SLA checking device confirm the SLA effectively whether it deals with all administrations as per SLA. In this paper, we represent a SLA confirmation and checking process that can distinguish SLA verification in gathering the information. We consider IaaS (Infrastructure as a Service) parameters for SLA verification in Cloud.
Service Oriented Software Engineering: Services as reusable components, Service Engineering, Software Development with Services. Service-oriented architectures, RESTful services
below one was the example for SDN as per my knowledge, if useful ple.pdfannethafashion
below one was the example for SDN as per my knowledge, if useful please give reward points.
Verizon SDN-NFV Based Network:
The following are key features of the network based on SDN and NFV:
Enhancements to the Software Defined Networking (SDN) Concept :
The fundamental concept of ‘Software Defined Networking’ (SDN) changes the current network
design paradigm by introducing network programmability and abstraction. In its initial, narrow
definition, SDN is about separating the network control and data planes in L1, L2, L3, and L4
switches. This enables independent scaling of control plane resources and data plane resources,
maximizing utilization of hardware resources. In addition, control plane centralization reduces
the number of managed control plane instances, simplifies operations, and enables orchestration.
The idea of centralized network control can be generalized, resulting in the broader definition of
SDN: the introduction of standard protocols and data models that enable logically centralized
control across multivendor and multi-layer networks. Such SDN Controllers expose abstracted
topology and service data models towards northbound systems, simplifying orchestration of end-
to-end services and enabling the introduction of innovative applications that rely on network
programmability.
Platform SDN Considerations:
Network changes are initiated by the VIM to provide VNFC connectivity and establish service
chains between VNFs as instructed by EEO. The VIM and the DC SDN controller communicate
using common interfaces to implement the necessary networking changes.
Scope of Control – SDN controller vs. other NFV system elements:
The interface between End-to-End Orchestration, non-network controllers (like non-network
OpenStack services) and the network controller is important for interoperability. There are
efforts currently underway in ONF, Open Daylight, ONOS, OpenStack, IETF, and elsewhere to
implement a common Northbound Interface (NBI) to support operator critical use cases. The
primary purpose of the SDN controller is to (re)establish some clean layering between
subsystems that exclusively control their respective resources. The DC SDN controller
subsystem (VIM + SDN Controller) is responsible for controlling connectivity, QoS, path
selection, selection of VNF network placement, inter- VNFC connections, etc. In the ETSI
definition of Forwarding Graphs (FG), the FG passed to the network controller only specifies the
types/flavors of VNFs to use for specific subscriber traffic and the order in which to apply VNFs
of various types/flavors. This allows the SDN controller to have latitude in deciding how best to
satisfy the functional requirements of a given forwarding graph. In addition, this clean layering
of decision making allows for network changes and faults that would be service impacting to be
healed within the network control plane without requiring interaction and direction from the
orchestration layer. The software systems outs.
This paper is written to give basic knowledge of Network function virtualisation in network system. In this paper the work on NFV done till now has been collaborated. It describes how the challenges faced by industry lead to NFV and what is meaning of NFV and NFV architecture model. It also explains NFV Infrastructure is managed and the forwarding path on which packets traverse in NFV. A relationship of NFV with SDN and current research ongoing on NFV policies is discussed.
SDN and NFV Value in Business Services: Innovations in Network Monetization a...Cisco Service Provider
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.
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.
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.
ENHANCING AND MEASURING THE PERFORMANCE IN SOFTWARE DEFINED NETWORKINGIJCNCJournal
Software Defined Networking (SDN) is a challenging chapter in today’s networking era. It is a network design approach that engages the framework to be controlled or 'altered' adroitly and halfway using programming applications. SDN is a serious advancement that assures to provide a better strategy than displaying the Quality of Service (QoS) approach in the present correspondence frameworks. SDN etymologically changes the lead and convenience of system instruments using the single high state program. It separates the system control and sending functions, empowering the network control to end up specifically. It provides more functionality and more flexibility than the traditional networks. A network administrator can easily shape the traffic without touching any individual switches and services which are needed in a network. The main technology for implementing SDN is a separation of data plane and control plane, network virtualization through programmability. The total amount of time in which user can respond is called response time. Throughput is known as how fast a network can send data. In this paper, we have design a network through which we have measured the Response Time and Throughput comparing with the Real-time Online Interactive Applications (ROIA), Multiple Packet Scheduler, and NOX.
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.
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
https://utilitasmathematica.com/index
Our journal Open-access journals often emphasize transparency in research, including open data practices and clear reporting. It’s Journal is now readily available to researchers, educators, policymakers, and the general public worldwide. This broader access facilitates interdisciplinary research and real-world applications of mathematical and statistical knowledge.
Similar to Conference Paper: Elastic Network Functions: opportunities and challenges (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.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
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.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
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.
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.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...
Conference Paper: Elastic Network Functions: opportunities and challenges
1. 1
Elastic Network Functions:
Opportunities and Challenges
R. Szabo1
, M. Kind2
, F.-J. Westphal2
, H. Woesner3
, D. Jocha1
and A. Csaszar1
1
Ericsson Research; 2
DT-AG; 3
BISDN
Abstract
Network Function Virtualization (NFV) and Software Defined Networking (SDN) are key technology enablers
for cost reductions and new business models in networking. The possibility to automatically and dynamically scale
network services at run time is one of the main claims of NFV. Elastic NFV could be similar to what elastic
cloud services provide for compute, with pay-per-use cost models for customers. However, control of resources
for elastic services is far from trivial. We show how current NFV and SDN architectures could support elastic
resource services for Network Functions (NFs). We reveal that the current NFV architecture does not allow recursive
resource orchestration, therefore preventing resource scaling requests from being handled by a resource orchestrator
overseeing the entire domain where an NF is executed. We introduce a logical centralization of joint compute and
network resource orchestration as a UNIFY framework, which enables direct control of elastic resources for the
NFs. We show opportunities and challenges associated to such an architecture.
I. INTRODUCTION
Socio-economic drivers, progress in information technologies, tumbling switching- and compute hard-
ware costs and availability of open source software solutions are creating the conditions for a change of
paradigm in designing and operating telecommunication networks and service infrastructures. Network
Function Virtualization (NFV) [1] by the European Telecommunications Standards Institute (ETSI) and
Software Defined Networking (SDN) [2] by the Open Networking Forum seem to be key technology
enablers in the direction of meeting requirements such as cost reductions and new business models. NFV,
on the one hand, targets at virtualizing servers and appliances that provide network functions. One of NFV’s
value propositions is cost optimization with the usage of common off the shelf hardware to reduce capital
expenditure. This, together with increased operational efficiency is expected to also reduce operational
expenditure. Operational efficiency is achieved by the automation of commission, configuration, resource
management, etc. for even an order of magnitude higher number of managed elements than before. SDN, on
the other hand, targets at breaking the vertical integration of network data and control planes to introduce
(logically centralized) control plane programmability for novel networking virtualization (abstraction),
simplified network (re)configuration and policy enforcement.
Today, all these promises are not yet realized. A typical example is the device located at the edge of
carrier networks. Here fixed network operators require Broadband Network Gateway (BNG) functionality
for customer centric processes like authentication, policing, etc. Technically, those gateways are physical
devices hosting special network services or software combining network control and data plane aspects
for fulfilling the processes, sometimes even supported by hardware acceleration. Given the fact, that the
Broadband Network Gateway is operated like an appliance, it is difficult to add and evolve the service
offering. For example, adding a parental control function or an Intrusion Detection System (IDS) for
a certain customer is rather cumbersome. Today, this would require the instantiation of a separate IDS
application, forwarding enforcement between the Network Gateway and the Intrusion Detection, and a
policy interface to configure blocking of malicious traffic. Dynamism in changing control parameters like
addresses adds additional management complexity.
The NFV framework [3] promises to remedy the problems of flexible service creation by managing and
orchestrating softwarized network functions into telecommunication data centers. However, considering
the full lifecycle of flexible network services, e.g., fulfillment, assurance and billing [4], one must look
beyond the fulfillment phase and see that flexibility is also ensured during assurance (operation) phase.
2. 2
We investigate, how network services can scale up/down or scale in/out to offer real elastic, pay as
use services. Our main contribution is the analysis of opportunities and challenges related to dynamic
service scaling with respect to i) the NFV framework; and ii) a novel and recursive resource orchestration
framework.
In Sec. II we revisit the SDN and the NFV architectures revealing their synergies and differences; intro-
duce a novel unifying architecture for joint and logically centralized compute and network orchestration.
In Sec. III we discuss elastic services in the view of the different architectures. In Sec. IV we highlight
related elasticity challenges and opportunities. Finally, we conclude in Sec. V.
II. VIRTUALIZATION: SDN, NFV AND BEYOND
Open Networking Forum works on the definition of an SDN architecture [2]. They focus on three layers:
data, control and application plane layers, but also include traditional management plane and end user
systems into their architecture. SDN applications are defined as control plane functions operating over the
forwarding abstraction offered by the SDN Controller. The applications connect to the SDN controller via
the A-CPI reference point (see Fig. 1). The control plane’s main responsibilities are i) creating the domain
wide abstraction for internal use; ii) creating application or client SDN controller specific virtualization
and policy enforcement; and iii) coordinating resources and operations for virtualization. The data plane
of this architecture constitutes of Network Elements (NEs) that deal directly with customer traffic. These
elements are connected to the controller. The right hand side of Fig. 1 shows an illustration of the SDN
components and the corresponding reference points (see details in [2]).
Fig. 1. The NFV and the SDN architectures side-by-side
3. 3
Since the architecture allows other SDN Controllers (clients) to connect to the North of an SDN
Controller the architecture is recursive. Therefore, automated network orchestration can be executed in
multi-level virtualization environments, as long as resource virtualization and client policies related to
resource use can be set. Such recursive automation enables clear separation of roles, responsibilities,
information hiding and scalability. It also provides efficient operations in multi-technology, multi-vendor,
multi-domain or multi-operator environments.
If we look into the user service aspects, then flexible service definition and creation may start by
abstracting and formalizing the service into the concept of network service. In the NFV framework [3]
the network service is formulated as a Virtualized Network Function (VNF) forwarding graph (see top
of the Fig. 1). These graphs represent the way in which service end points (e.g., customer’s access)
are interconnected with the desired VNFs, such as firewalls, load balancers, DHCP servers, etc. Service
graph representations form the input for the management and orchestration to instantiate and configure
the requested service.
The main ETSI NFV Management and Orchestration (MANO) components are the Network Func-
tion Virtualization Orchestrator (NFVO) for the lifecycle management of the services; VNF Managers
(VNFMs) for lifecycle management of individual VNFs; and Virtualized Infrastructure Managers (VIMs)
for controlling and managing compute, storage and network resources [5] (see left side of Fig. 1). VNFs
are instantiated in a NFV Infrastructure by the VIM through technology specific resource controllers like
a SDN Controller or a Compute Controller. The orchestration framework also defines major reference
points and is completed by connections to traditional management functions, which are also shown in
Fig. 1 and detailed in [5].
If we put side-by-side the SDN and the NFV architectures, we can see that the VIM talks to an SDN
Controller to orchestrate the virtualized network in the NFV Infrastructure (red arrow in Fig. 1). Logically,
however, the VIM and the NFVO will perform network resource orchestration equivalently to a network
orchestrator and coordinator within the SDN architecture (red box in the right hand side of Fig. 1).
There is, however, at least one major difference between the designs of the NFV and SDN architectures:
SDN relies on a basic forwarding abstraction which can be reused recursively for virtualization of topology
and forwarding elements, while the NFV framework offers significantly different services on the top
compared to what is consumes at the bottom. Therefore, the current MANO framework is incapable of
automated recursive orchestration for NFV.
A. Unifying compute and network virtualization (UNIFY)
Common open interfaces to programmatically control resources have been long pursued, e.g., [6],
[7], but not yet realized. We believe that the hype around NFV allows us to reconsider a combined
abstraction of compute and network resources. We propose to logically centralize all the resource or-
chestration functionalities existing distributively in the NFV MANO framework to enable automated
recursive resource orchestration and domain virtualization similar to the SDN architecture. We show
that the logical centralization of joint compute and network resource orchestration enables direct control
of elastic resources for the network functions. This embedding of resource control within a deployed
service resembles a recursive architecture.
In order to harmonize and logically centralize programmability over compute and network virtualization
a common abstraction has to be defined [8]. In the framework of the UNIFY project [9], we combined
compute and network resources to create a unified narrow waist programmability abstraction for Resource
Orchestrator (RO). The UNIFY architecture is very similar to the SDN architecture, but it operates at the
joint compute and network abstraction in each of its components. Fig. 2 shows the UNIFY architecture
with its reference points.
The role of the Controller Adapter (CA) is to create a domain wide joint abstraction for the RO
by interfacing with all possible infrastructure components. The Ca-Co reference point corresponds to
compute or network controllers for compute or network only domains; agents directly managing compute
4. 4
Fig. 2. Unifying Carrier and Cloud Resources (UNIFY)
or network resources are connected via a Co-Rm reference point, while other UNIFY domains use an
Sl-Or reference point.
The RO offers resources orchestration services at the Sl-Or reference point with isolations based
on requests and resource virtualization per client. UNIFY clients can be other UNIFY domains, the
Service Provider itself or instantiated Network Functions (NFs). The resource orchestration services
accepts Network Function Forwarding Graph (NF-FG) [9] requests, which contain abstract NF types;
SDN forwarding rules between the NFs; and deployment constraints associated to arbitrary grouping of
NFs. Additionally, the RO offers elastic control services at the Cf-Or reference point directly to NFs.
Major differences between the Cf-Or and the Sl-Or reference points are: i) Cf-Or virtualizations must
be created autonomously upon NF-FG instantiations, when detecting corresponding interface definitions at
an NF’s description (see port “C” in Fig. 3); ii) the connection between the NF and the Cf-Or interface
must autonomously be inserted into the NF-FG request; and iii) the virtualization at the Cf-Or must be
strictly scoped to the subset of the genuine NF-FG limiting the resource control to the NF’s responsibility
domain. For example, in Fig. 5 the E-IDSC can only control the IDS components but cannot control the
BNG VM.
We further assume that the infrastructure management and the service management is separated (see
purple Operation Support System (OSS) and the blue Element Management (EM) and OSS/Business
Support System (BSS)). This way the UNIFY components are assumed to be managed from a dedicated
infrastructure OSS representing the ownership of the domain wide virtualized resources.
In relation to the NFV and the SDN architectures, the RO replaces VIMs, and offers resource orchestra-
tion functions to VNFMs and the NFVO. Throughout the Sl-Or reference point, the UNIFY architecture
resembles a recursive control and orchestration framework similar to the SDN. See left (NFV) and right
(SDN) hand sides of Fig. 2.
5. 5
III. ELASTIC SERVICES
The possibility to dynamically scale network services at run-time in an automated fashion is one of
the main advantages offered by the NFV approach, providing both better resource utilization and better
service at a lower cost. Elastic NFV could be similar to what elastic cloud services provide for compute,
with pay as you use cost models for the customers.
There are multiple reasons for initiating a scaling procedure: a user could request higher capacity ahead
of time in order to deal with a known increase of demand in the future; the operations and management
system could initiate scaling to maintain service level requirements based on monitoring Key Performance
Indicators and resource use; or the deployed service components themselves could manage their resource
needs similarly to automatic multi-threading scaling of some software running on multi-core CPUs.
Scaling of VNFs can be done in many ways. Which one is appropriate in a particular case depends
heavily on the precise function provided by the VNFs, for example, the type of traffic it operates on and
at which layer in the networking stack; requirements on state synchronization; requirements on control
traffic during the scaling event; dependencies on other VNFs (service logic); ability to parallel processing
or multi-threading; etc.
We analyze the capability of network services to self-adapt to changing conditions in (quasi) real-time
in the next sub-sections.
A. Who is in charge of an elastic service?
According to the NFV MANO framework the VNFM is responsible for lifecycle management of
individual VNFs. For example, the VNFM function may monitor Key Performance Indicators of a VNF
to determine scaling operations. Scaling may include changing the configuration of virtualized resources,
like adding/removing CPUs, adding/removing Virtual Machines (VMs) and adding/removing of associated
network resources. VNFMs are assumed to be generic and exposed by an open interface for the VNFs
(see Fig. 1). However, beyond resource control, VNFM’s other functionalities are VNF instantiation and
configuration; updates, upgrades and modifications; collection of VNF related performance measurements
and event information; VNF assisted or automated healing; and coordination and adaptation between the
Element Manager and the VIM.
With the UNIFY framework, we argue that the unified compute and network programmatic interface
offered directly to VNFs at the Cf-Or reference point can enable VNF developers to autonomously
control their resources needs. This means that elastic control may indeed be VNF specific and may be
changed with VNF updates by the developers themselves. Adding this to the recursively hierarchical
structure of the UNIFY architecture resource control requests may be handled locally or closest in the
hierarchy to the actual execution unlike with a central management entity like the VNFM.
B. Monolithic vs. decomposed network functions: control and data plane split design
The SDN abstraction of the forwarding behavior enables the separation of traditional monolithic control
and data plane network function designs. Such split may allow direct control of data plane resources and
instances by the corresponding control functions. The MANO framework, however, does not address such
split NFV designs, but assumes that such control is within the VNFM or NFVO.
For example, an IDS, whose role is to identify and block malicious traffic, could be implemented in
various ways. Let’s assume that the IDS service is managed by the operator, i.e., the Service Provider
manages and operates the IDS upon the user’s subscription to the service. The user’s and the service’s
view of the IDS is shown in the left hand side of Fig. 3 including traditional management components.
The IDS functional block can be realized as a hardware based monolithic component (a); a monolithic
IDS VM (b); or as a data and control plane split design according to options (c) and (d).
6. 6
Fig. 3. IDS Decomposition Example
In option (a) one can consider only sharing of the hardware resources, in option (b) one can scale
up/down the service dynamically by requesting or releasing resources associated to the individual compo-
nents. However, scaling out/in requires adding to or removing from components and also re-configuring
the service chain.
In option (c) the IDS control logic is separated into a Control VM, a firewall component for blocking
of the malicious traffic and a traffic analyzer. The firewall may be mapped to a standard SDN network
element and the traffic analysis may be realized by some generic Deep Packet Inspection (DPI) VM.
Therefore, the Control VM must configure the generic DPI with patterns to identify malicious traffic.
In option (d), without loss of generality, we consider that the DPI processing can be parallelized by
forking additional DPI instances. In this case, the Control VM must be extended to monitor the loads
of the DPI components; to on-demand add or remove DPI instances and to re-configure traffic steering.
For example, the SDN switch will not only mirror user traffic to a single DPI instance but must also act
as a load balancer among the multiple DPI instances. Therefore, the load balancer must be dynamically
configured by the IDS Controller. Cf-Or reference point of UNIFY offers such resource service for the
IDS Control. By the means of NF-FG requests, the IDS Control can directly request adding or removing
of DPI instances and the reconfiguration of the forwarding overlay. This is achieved without the NFV
VNFM component (see Fig. 3(d)).
Note also, that the virtualization between the Cf-Or and the IDS Control can be derived based on the
VNF decomposition model presented in Fig. 3/(d). Basically, the existence of a control NF is detected
by recognizing the specific Cf-Or interface (C interface in Fig. 3) and the scope of control is given by
the components derived from the genuine service definition.
C. Example scenarios
In what follows, we analyze elastic control scenarios with the NFV (see Fig. 4) and the UNIFY (see
Fig. 5) architectures. Fig. 4 and 5 show i) the customer’s view of the service (with dashed lines), ii) the
service provider’s management view (Element Managements and the OSS), iii) virtualization managers
(NFVO, VNFM and VIM or RO) and iv) the deployed network functions systems. The customer service
is a cascade of an elastic IDS as shown in Fig. 3/(d) and a Broadband Network Gateway to connect the
user to the Internet.
7. 7
In Fig. 4 and 5 signaling messages are labeled and shown by arrow-heads for which we assume that there
is always an underlying logical network connection. Also, the arrow-heads only illustrate our discussion
of the primarily control message flow, but control messages may also pass in the reverse direction.
Fig. 4. Elastic control loop with the NFV framework
Fig. 5. Elastic control loop with the UNIFY framework
8. 8
D. Service deployment with service decomposition
In the NFV approach, the NFVO must decide between the deployment options presented in Fig. 3
during orchestration. Afterwards, the NFVO sends a fully mapped VNF Forwarding Graph to the VIMs,
who by the means of a compute (Comp C) and network (Netw C) controllers instantiate VNF VMs and
configure the forwarding overlay respectively (see Fig. 4).
In the UNIFY case shown in Fig. 5, thanks to the logically centralized orchestrator (RO), the NFVO
may send only the service provider view of the service graph to the RO. The RO, considering the VNF
decomposition model as presented in Fig. 3, can decide, which option to initiate based on the available
infrastructure resources. Furthermore, if another UNIFY domain is embedded under the RO (see repeated
orchestration layer in Fig. 2), then the decomposition may be deferred to that sub-domain. In either
cases, the services offered through different decomposition options must be equivalent; ROs shall consider
service requirements and operational policies like energy efficiency, utilization, etc. when selecting between
deployment options.
Additionally, during the UNIFY decomposition processes, ROs must detect if any VNF definition
contains a Cf-Or interface (denoted by C in Fig. 3 and 5) interface. For each such a control interface i)
a new scoped virtualization must be created at the RO with an interface ii) to which a logical connection
from the VNF’s C interface must be included into the forwarding overlay definition. In the example
given in Fig. 5, the E-IDSC control VM is connected to the IDS ctxt virtualization context at the
RO. The IDS ctxt visualization context contains only the components derived from the IDS service
decomposition according to Fig. 3, hence excludes the BNG VM.
Note that the number of external interfaces related to a service component does not change during the
decomposition process (see interfaces 1 and 2 in Fig. 3). The Cf-Or interface of a VNF is internally
resolved to a connection to the corresponding RO. If there are multiple levels of virtualization domains,
then the Cf-Or interface is resolved when first seen by an RO. The connection between such control
interfaces and the corresponding RO is only included into the NF-FG description where it happens and
does not propagate up in the hierarchy. This, thanks to the recursive orchestration framework, allows a
UNIFY domain to re-optimize or decompose a VNF implementation without affecting external operations.
Once the corresponding RO is done with the decomposition and mapping of the service to the virtualized
infrastructure resources it consults the Controller Adapter to instantiate and configure the components.
For the embedded UNIFY domain, the Controller Adapter simply pass the corresponding sub service
definition for the underlying orchestrator.
Last but not least, both in the NFV and the UNIFY cases, Element Managements and the OSS must
handle any remaining service configurations.
E. Control of elasticity
In the following, we will analyze how the NFV and the UNIFY frameworks handle a scaling request for
the example IDS service. We will refer to the control messages between the components with according
to their labels in Fig. 4 and 5.
We assume that the increased load can only be met by an additional DPI instance. In both set-ups, the
overload is learned by the E-IDSC by reports from the DPI components (message v0 in Fig. 4 and r0
in Fig. 5).
In the NFV setup, the VNFM is in charge of the scaling of the IDS service component. Therefore, the
E-IDSC must notify the VNFM (v1) about the need of extra resources. Since the VNFM is service logic
agnostic [5], it shall not know the decomposition details of the IDS service. Therefore it cannot know
what further components to deploy, but must let the NFVO know (v2) about the problem. Note here, that
even the scale up/down of a single DPI instance looks problematic, as the resources to be increased does
not directly belong to the E-IDSC. The NFVO must look-up the service specific template to get an idea
how to add more resources. Once it learns that a new DPI should be instantiated and connected into the
service, it can allocate resources and configure the overlay by sending requests to a compute VIM (VIM
9. 9
Comp) (v3/a) and to a network VIM (VIM Netw) (v3/b). VIM Comp can instantiate a new DPI via a
compute controller, e.g., OpenStack Controller (see messages v4/a, v5/a). The network overlay must be
configured similarly, via the VIM Netw and the SDN Controller (Netw C) (see messages v4/b, v5/b).
Note that the E-IDSC (VNF in general) must learn that the scaling operation was done, e.g., to be
able to update the service logic. In our example, the E-IDSC may wish to reconfigure the load balancing
rules in LB@NE2 (v6). Therefore, there must be a reverse flow of control information from the VIMs,
through the NFVO, VNFMs to the requesting VNF.
In the UNIFY setup, the E-IDSC is directly connected to the RO (see Fig. 5). Let’s assume again, that
the E-IDSC learns that DPIs are running low with resources (r0). In this case, the E-IDSC knows the
service logic inherently; it is designed and developed as part of it. It knows its instantiated VNFs, the
corresponding forwarding overlay and an abstract view of the infrastructure resources through the RO’s
dedicated virtualizer. Therefore, the E-IDSC is in the best position to initiate scale up/down or scale out/in.
The E-IDSC can issue an NF-FG request (r1), which can contain an additional DPI instance beyond the
already deployed ones. In turn, the RO verifies the associated client policies, performs orchestration for
the updated NF-FG and issues execution commands to compute and network domains (messages r2/a
and r2/b respectively). The rest of the execution is identical to the NFV case beyond the two controllers.
Note that if the IDS components are allocated in a UNIFY sub-domain, then a hierarchy of ROs may
be involved in the orchestration. However, if the decomposition happens only at the lowest level of the
hierarchy, closest to the technology specific infrastructure domain, then orchestration at higher hierarchical
levels may be left out of the process. This allows local decisions unless insufficient resources, in which
case the execution might fall back to the NFV scenario.
As a summary, we show the major signaling messages of the NFV and the UNIFY set-ups as a
comparison in Fig. 6, where components and messages labels correspond to Fig. 4 and 5. It is important
to note, that not only the fewer elements, their potential “distance” to the executed NFs matters, but also
the fact if a VNFM and NFVO can bear with service / application specific scaling details or not. In the
UNIFY approach, such knowledge is placed into the NFs themselves.
NFVO VNFM VIM
Netw
VIM
Comp
Compute
Controller
Network
Controller
Network Functions Systems
Elastic IDS
Controller NF
LB NF DPI1 NF DPI2 NF
(v0) cannot sustain user traffic(v1) need extra resources(v2) need extra DPI
instance (v3/a) instantiate new DPI VM (v4/a) instantiate
DPI
(v5/a) instantiate DPI
DPI2 NF
(v3/b) reconfigure forwarding overlay (v4/b) reconfigure forwarding (v6) update the LB
configuration
NFVcontrolloop
Resource
Orchestrator
(r0) cannot sustain user traffic
(r1) request new DPI instance connected to overlay
(r2/a) instantiate DPI (r3/a) instantiate DPI
DPI2 NF
(r2/b) reconfigure forwarding (r4) update the LB
configuration
UNIFY
controlloop
Fig. 6. Comparison of the NFV and UNIFY elastic control loops
IV. CHALLENGES AND OPPORTUNITIES
First of all, service decomposition into atomic building block looks promising from component re-
usability point of view (see, for example, DPI components in Fig. 3). Where and how decompositions
happen affects virtualization related management components. In the NFV approach such decisions happen
in the NFVO; in UNIFY we argue that decomposition and control of the corresponding sub-components
are service specific, hence best placed in the hand of the service developers and realized within the control
plane of the network functions.
10. 10
Service decomposition can also imply control and data plane split designs. In such setups the control
of data plane elasticities may rightfully be placed into the deployed control plane components instead of
the overarching virtualization managers like the NFVO or VNFMs.
For control and data plane split deployments, appropriate control network overlays must also be created
dynamically. These extra overlays should autonomously be added to the genuine service definition,
for example, see options (c) and (d) in Fig. 3. Additionally, elastic control interfaces must also be
autonomously connected (see the connection of the Cf-Or interface of the E-IDSC to the RO in Fig. 5).
Therefore, a user’s network function is connected to an infrastructure orchestrator, which, however, controls
domain wide resources. Autonomous scoping of controllability and policy enforcement is a must at such
elasticity control reference points.
How to learn about the new data plane structure after a scaling operation is another question. If
decomposition and scaling operations are handled in the NFVO or VNFMs, then it is open how a control
plane network function can learn about the revised data plane structure it oversees. If control plane network
functions are in charge of their data plane scaling operations, they inherently know the results. This also
motives our design choices behind the elasticity control services of the UNIFY framework.
Another issue is who should configure the data plane components, for example, the load balancer or
the DPIs in Fig. 4 and 5? If scaling is non-transparent to the involved network functions (e.g., stateful
processing), then a service logic must assist the operational reconfiguration of components. The question
is, can an external virtualization management component (e.g., NFVO, VNFM or RO) bear with such a
logic? We believe that such logic is best placed in control applications themselves. This is in harmony
with the end-to-end principle of Internet: application specific functions should reside in the application
(e.g., control plane network functions), rather than within the network (e.g., virtualization managers).
Regarding security issues, in the NFV setup elasticity control signaling goes through trusted elements
like Element Managements, the OSS, VNFMs, the NFVO and VIMs. Therefore, it is relatively easy to
enforce user policies related to the service contract due to the involvement of service layer management
functions. In the case of the UNIFY approach, however, resource policies related to service contracts
must be enforced in corresponding virtualizers distributed in the hierarchy of UNIFY domains. However,
UNIFY orchestrators do not have any notion of service logics but only compute, storage and network
abstractions. Therefore, configurations for virtualizers and policy enforcements must autonomously be
translated from service logics. For example, the virtualizer and the policy enforcement associated to the
E-IDSC in the RO (see Fig. 5) could limit
• the available resources (max 10 virtual CPU, max 5 Gbyte RAM, less than 100Mbps in/out rate,
maximum cost of resources, etc.),
• the capabilities as available VNF types (DPI and network elements) for the control application.
We believe, that such policy information can be extracted from genuine service requests and client policies
(e.g., maximum cost, etc.).
V. SUMMARY
The importance of control and elasticity capabilities for the Future Internet has already been pointed out,
e.g., in [10]. The recent NFV initiation with SDN may be able to provide elastic networking services similar
to elastic cloud services in compute. We have discussed the synergies and differences between the SDN and
the NFV architectures. We have shown that the ETSI NFV MANO framework does not use unified compute
and network abstractions for automated resource orchestration. This prevents recursion and automation,
which affects who could be in charge for controlling and providing elasticity of services. We have shown
that the UNIFY architecture has appropriate resource abstractions for recursive automation of resource
orchestrations, yielding for possible outplacement of elasticity control to deployed network functions
systems. Throughout the analysis of an example scenario, we discussed opportunities and challenges
related to both, the NFV and the UNIFY management and orchestration frameworks.
We conclude with some highlighted opportunities considering the UNIFY approach:
11. 11
• faster resource control loops with less involved elements;
• clearer separation of roles and responsibilities;
• logical centralization of all resource orchestration functions;
• recursion and automation of resource orchestration across multi-level virtualization domains;
• enabler for split control and data plane design;
• resource driven service decomposition;
• interfacing directly with deployed network functions for (3rd party) elastic control;
and associated challenges:
• autonomous service decomposition for control and data plane split designs;
• autonomous definition of resource virtualizations and policy enforcements for deployed control func-
tions;
• autonomous creation of management and control network overlays.
Initial proof of concept validations for the UNIFY orchestration framework had been showcased at
SIGCOMM 2014 [11] and at the European Workshop on Software Defined Networking (EWSDN) 2014
[12]. The orchestration framework is released as an open source [13]. We hope to trigger further discussions
in this hot topic area with our ideas.
ACKNOWLEDGMENT
We are grateful for the invaluable comments and suggestions to the anonymous reviewers.
This work is supported by FP7 UNIFY, a research project partially funded by the European Community
under the Seventh Framework Program (grant agreement no. 619609). The views expressed here are those
of the authors only. The European Commission is not liable for any use that may be made of the information
in this document. The authors are thankful to the UNIFY team for the inspiring discussions.
REFERENCES
[1] ETSI, “White Paper: Network Functions Virtualisation (NFV),” 2013. [Online]. Available: http://portal.etsi.org/NFV/NFV White
Paper2.pdf
[2] Open Networking Forum (ONF), “SDN architecture,” ONF, TR (Technical Reference), non-normative, type 2 SDN ARCH 1.0
06062014, Jun. 2014. [Online]. Available: https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/
TR SDN ARCH 1.0 06062014.pdf
[3] ETSI, “Architectural framework,” ETSI, Group Specification v1.1.1, Oct. 2013. [Online]. Available: http://docbox.etsi.org/ISG/NFV/
Open/Published/gs NFV002v010101p%20-%20Architectural%20Fwk.pdf
[4] TM Forum, “Business Process Framework (eTOM),” online, Feb. 2015. [Online]. Available: http://www.tmforum.org/
BusinessProcessFramework
[5] Jrgen Quittek et al., “Network function virtualization (NFV) management and orchestration,” ETSI, GROUP SPECIFICATION GS
NFV-MAN 001 V1.1.1, Nov. 2014. [Online]. Available: http://www.etsi.org/deliver/etsi gs/NFV-MAN/001 099/001/01.01.01 60/gs
NFV-MAN001v010101p.pdf
[6] A. Palo, L. Zuccaro, A. Simeoni et al., “A common open interface to programmatically control and supervise open networks in the
future internet,” in Future Network and Mobile Summit (FutureNetworkSummit), 2013, Jul. 2013, pp. 1–9.
[7] M. Castrucci, M. Cecchi, F. Delli Priscoli et al., “Key concepts for the future internet architecture,” in Future Network Mobile Summit
(FutureNetw), 2011, Jun. 2011, pp. 1–10.
[8] P. Skoldstrom, B. Sonkoly, A. Gulyas et al., “Towards unified programmability of cloud and carrier infrastructure,” in 2014 Third
European Workshop on Software-Defined Networks (EWSDN), http://ewsdn.eu, 2014.
[9] R. Szabo, B. Sonkoly, M. Kind et al., “D2.2: Final Architecture,” UNIFY Project, Deliverable 2.2, Nov. 2014. [Online]. Available:
http://fp7-unify.eu/files/fp7-unify-eu-docs/Results/Deliverables/UNIFY%20Deliverable%202.2%20Final%20Architecture.pdf
[10] A. Galis, H. Abramowicz, M. Brunner et al., “Management and service-aware networking architectures (MANA) for future internet;
position paper: System functions, capabilities and requirements,” in Fourth International Conference on Communications and Networking
in China, 2009. ChinaCOM 2009, Aug. 2009, pp. 1–13.
[11] A. Csoma, B. Sonkoly, L. Csikor et al., “ESCAPE: Extensible Service ChAin Prototyping Environment using Mininet, Click, NETCONF
and POX. Demonstation.” in ACM SIGCOMM 2014, 2014.
[12] ——, “Multi-layered service orchestration in a multi-domain network environment. Demonstation.” in 2014 Third European Workshop
on Software-Defined Networks (EWSDN), http://ewsdn.eu, 2014.
[13] UNIFY Project, “Extensible Service ChAin Prototyping Environment using Mininet, Click, NETCONF and POX,” open source, Sep.
2014. [Online]. Available: https://github.com/nemethf/escape