Towards the scalability of a Service-oriented PCE architecture

for IoT scenarios

Vitor Barbosa C. Souza

Xavi Masip Bruin

Eva Marin Tordera

CRAAX - Technical University of Catalonia (UPC)

PACE Workshop

May 2015

2

Scenario

IoT, Smart City, Vehicular Networks Improved capabilities of mobile devices Distinct sensors and actuators

Characteristics Mobility Heterogeneity Large number of Network Elements (NE)

Can we take advantage of this large number of mobile and heterogeneous NEs?

3

What are the benefits?

Diminish the cost of sensors deployment Community effect Distributed maintenance tasks Mobility

New services New connectivity paradigm

Anywhere Anyhow Anytime

4

What are the difficulties?

Addressing IPv4 scalability limitations Address depletion increased by the IPv4 double

functionality Network layer = locator (LOC) Service layer = identifier (ID)

The host-oriented model also introduces frequent communication interruptions

5

What are the difficulties?

Routing NEs positioning NEs availability Selection of the best devices Computation of optimal path

Control overhead to handle new services Service orchestration based on network layer

and service layer constraints

6

State-of-the-art technologies

Addressing problem: ID/LOC separation ID/LOC Split Architecture (ILSA)

7

State-of-the-art technologies

Routing problem Decouple control and data plane: PCE

Can it address mobility? Can it enable service orchestration?

Host-oriented PCE vs. Service-oriented PCE (SPCE) What are the advantages of SPCE? Service provider as a PCC

PCC is not requesting just for a path PCC requests a service

8

SPCE with ILSA scheme overviewILSA

LOC: B

LOC: C

SPCE

3

2

LOC: D

LOC: A

Access Domain 1

Access Domain 4

1

Access Domain 3

Access Domain 2

User

Optical aggregation node

Mobile Devices

Wireless Access Points

PCC

Webserver

4

NSI

9

ILSA extension

The PCC does not know what hosts it should connect

The service is used as the main parameter for PCReq message

The proposed ILSA scheme adopts different IDs for services and hosts

10

Three-tier ILSA paradigm

SID

SPCE Architecture with ILSA

HID 1 HID 2 HID 3

LOC 1a

LOC 2a LOC 3

LOC 1b LOC 1c

LOC 2b

ILSA

11

SPCE architecture PCC sends a service request using a extension of the PCEP to the PCEP Module (PCEPM)The request is

transmitted to the Service Orchetration Module (SOM)

The SOM communicates with the Device-Context Database (DCDB) to get information about the available NEs, and choose the HIDs to be used

The DCDB uses information available in the ILSA scheme

SOM sends the bests NEs selected to the Path Computation Module (PCM) which uses network constraints for path computation

PCM communicates with ILSA to map each HID to LOC

The PCM communicates with the Traffic Engineering Database (TED) to get updated NSI and compute the paths.

The computed paths are sent back to the SOM

SOM sends to the Decision Module (DM) a list of destinations’ HID, a set of paths to the respective LOC, and network and service layer constraints

The DM selects the best combination of paths according to PCReq to the PCEPM

The PCEPM sends the PCRep to the PCC

12

Next steps

Definition of the attributes to be stored in the DCDB and strategies for managing it

Define algorithms and attributes to be used in order to map SID to HID

Propose PCEP extension to support new messages and parameters.

Questions?

Suggestions?