SDN Architecture

SDN Layers
 Key Elements of SDN
• Centralized Network Controller
– With decoupled control and data planes and a centralized network
controller, the network administrators can rapidly configure the network.
• Programmable Open APIs
– SDN architecture supports programmable open APIs for interface
between the SDN application and control layers (Northbound interface).
• Standard Communication Interface (OpenFlow)
– SDN architecture uses a standard communication interface between the
control and infrastructure layers (Southbound interface).
– OpenFlow, which is defined by the Open Networking Foundation (ONF),
is the broadly accepted SDN protocol for the Southbound interface.
Open Flow switch
Open Flow Table

Match Action Counter Priority Time-out

When to delete the entry

What order to process the rule

# of Packet/Bytes processed by the rule
1. Forward packet to zero or more ports
2. Encapsulate and forward to controller
3. Send to normal processing pipeline
4. Modify Fields
Switch VLAN VLAN MAC MAC Eth IP IP IP IP L4 L4
Port ID pcp src dst type Src Dst ToS Prot sport dport
 Network Function Virtualization

• Network Function
Virtualization (NFV) is a
technology that leverages
virtualization to consolidate
the heterogeneous network
devices onto industry-
standard high-volume
servers, switches and
storage.
• NFV is complementary to
SDN as NFV can provide the
infrastructure on which SDN
can run.

Book website: http://www.internet-of- Bahga & Madisetti, ©

 Key Elements of NFV
• Virtualized Network Function (VNF)
– VNF is a software implementation of a network function which
is capable of running over the NFV Infrastructure (NFVI).
• NFV Infrastructure (NFVI)
– NFVI includes computer, network and storage resources that are
virtualized.
• NFV Management and Orchestration
– NFV Management and Orchestration focuses on all
virtualization-specific management tasks and covers the
orchestration and life-cycle management of physical and/or
software resources that support infrastructure virtualization and
the life-cycle management of VNFs.

Book website: http://www.internet-of- Bahga & Madisetti, ©

Conventional Home Automation System
Network Function Virtualization
IOT PLATFORMS DESIGN METHODOLOGY
Purpose and Requirements Specification

First step is to define the purpose and requirements of the

system.
In this step, the system purpose, behavior and requirements
are captured. Requirements can be:
• Data collection requirements
• Data analysis requirements
• System management requirements
• Security requirements
• User interface requirements
For home automation system the purpose and requirements
specification is as follows:
Process Specification
The use cases of the IoT system are formally described
based on or derived from the purpose and requirements
specifications.
The process specification for home automation system is as
shown below.
Domain Model Specification
The domain model describes the main concepts, entities and
objects in the domain of the IoT system to be designed.

Domain model defines the attributes of the objects and

relationships between objects.

The domain model is independent of any specific technology

or platform.

Using domain model, system designers can get an

understanding of the IoT domain for which the system is to
be designed.
The entities, objects and concepts defined in the domain
model of home automation system include the following:
Information Model Specification
Service Specifications
The service specification defines the following:
• Services in the system
• Service types
• Service inputs/output
• Service endpoints
• Service schedules
• Service preconditions
• Service effects
Controller Service:
Mode Service:
State Service:
IoT Level Specification
 Functional View Specification
The functional view defines the functions of the
IoT systems grouped into various functional
groups.

Each functional group provides functionalities for

interacting with concepts in the domain model and
information related to the concepts.
The functional groups in a functional view include:
Device, Communication, Services, Management, Security,
Application.
Mapping deployment level to functional groups for
home automation IOT system
OPERATIONAL VIEW SPECIFICATIONS
In this step, various options pertaining to the IoT system
deployment and operation are defined.

• Service Hosting Options,

•Storage Options,
• Device Options,
•Application Hosting Options, Etc
Operational view specifications for the home automation
example are
Devices:
Computing Device , Raspberry PI, Light dependent resistor (sensor),
really switch (actuator)
Communication APIs :REST APIs
Communication Protocols: Link Layer-802.11, Network
Layer-IPv4/IPv6, Transport Layer –TCP, Application Layer- HTTP
Services:
i)Controller Service- Hosted on device, Implemented Python and
run as a native service.
ii)Mode Service-REST-ful web service, hosted on device,
implemented with DJango – REST frame work.
iii) State Service- REST-ful web service, hosted on device,
implemented with Django –REST frame work.
Application:
i) Web Application- Django web application ,
ii)Application Server- Django App server
iii) Database Server-MySQL

Security:
i) Authentication- Web App, Database
ii) Authorization- Web App, Database

Management:
i) Application Management-Django App Management
ii) Database Management- My SQL, DB Management
iii)Device Management- Raspberry Pi Device
Management.
DEVICE & COMPONENT INTEGRATION
APPLICATION DEVELOPMENT