Network Slices for Vertical Industries The First Workshop on - - PowerPoint PPT Presentation

network slices for
SMART_READER_LITE
LIVE PREVIEW

Network Slices for Vertical Industries The First Workshop on - - PowerPoint PPT Presentation

Network Slices for Vertical Industries The First Workshop on Control and C. Casetti, C. F. Chiasserini, Management of Vertical Slicing Including the Thomas omas Dei i, P. A. Frangoudis, Edge and Fog Systems (COMPASS) A. Ksentini, G.


slide-1
SLIDE 1

Network Slices for Vertical Industries

The First Workshop on Control and Management of Vertical Slicing Including the Edge and Fog Systems (COMPASS) Barcelona, April 15, 2018

  • C. Casetti, C. F. Chiasserini,

Thomas

  • mas Deiß

iß, P. A. Frangoudis,

  • A. Ksentini, G. Landi, X. Li,
  • J. Mangues, N. Molner
slide-2
SLIDE 2

Overview

  • Motivation
  • 5G-TRANSFORMER system
  • Vertical service descriptions
  • Translation to network slices
  • Arbitration
  • Summary

15 April 2018 2

slide-3
SLIDE 3

Motivation

  • 5G networks provide different service types
  • eMBB

enhanced mobile broadBand

  • mIoT

massive IoT

  • URLLC

ultra-reliable low-latency communication

  • Different service types require different deployments
  • Create several logical networks on common physical infrastructure
  •  network slices
  • (eMBB), mIoT, and URLLC enable the creation of new services
  • Provided by vertical industries (automotive, eHealth, smart city, …)
  • Hundreds, thousands, … of service instances
  • Communication service extended with applications provided by verticals
  •  vertical service

15 April 2018 3

slide-4
SLIDE 4

Motivation (contd.)

  • Verticals are experts in their application domain
  • Assumption: less knowledgeable in creating and orchestrating network

slice for their specific service

  • Intersection collision avoidance (automotive), onsite live experience

(entertainment), emergency response in case of heart attack (eHealth), control of production plant (eIndustry), …

  • Create a platform that allows verticals to focus on the service to

be provided

  • Creation and orchestration of network slices handled by the platform

15 April 2018 4

slide-5
SLIDE 5

5G-TRANSFORMER system architecture

15 April 2018 5

Vertical Slicer Service Orchestrator Mobile Transport and Computing Platform

slide-6
SLIDE 6

5G-TRANSFORMER Components

  • Vertical Slicer
  • Common entry for all verticals
  • Definition of vertical services and SLAs
  • Mapping to network slices,
  • Arbitration
  • Service Orchestrator
  • End-to-end orchestration of network slices
  • Federation
  • Mobile Transport and Computing Platform
  • Orchestration of resources
  • Manages network, compute, storage infrastructure
  • Infrastructures: cloud/MEC datacenter, 5G AN/CN, …
  • Provides different abstractions

15 April 2018 6

slide-7
SLIDE 7

Vertical Service Descriptions

  • Vertical Service Blueprint
  • Incomplete description of a vertical service
  • Required latency, throughput, …
  • Coverage area
  • VM image of vertical application
  • Created by 5G-TRANSFORMER service provider
  • Vertical Service Descriptor
  • Complete description of vertical service
  • Multiple instances of same vertical service possible
  • Network Service Descriptor (ETSI NFV)
  • n:m relation to vertical service instances
  • Used as network slice template
  • Passed to 5GT-SO

15 April 2018 7

Missing information provided by vertical VSD/NSD Translator, Arbitrator

slide-8
SLIDE 8

Vertical Service Blueprint

15 April 2018 8

Fie ield ld Descr cript ption ion

Atomic functional components involved vEPC_23682_indirect, 4GRAN, MTC-AAA, AS Service sequence Connectivity service sapAS - cpAs, sapAAA - cpAAA, cpAsEpc – cpEpcAs, cpAAAEpc - cpEpcAAA: L3VPN sapUu: 4G External interconnection sapAS, sapAAA, sapUu Internal interconnection n/a (no other services, except those listed already are needed)

Fie ield ld Descr cript ption ion

Name LTE Sensor Monitoring Description … reference architecture in 3GPP 23.682, indirect

  • mode. … application server and AAA server are

provided by the vertical. Version 1.0 Identity Xyz4711_bp Parameters <cover erageA ageArea rea, Coordinates, “LTE coverage area”, Service Constraints/Geographical area> <sapLoc Locat atio ion, Coordinate, “Location of SAP”, Service Constraints/sapAS Location> <deviceA iceAmount mount, Int, “amount of sensors”, SLA/sapUu> <msgRate ate, Int, “sensor msg rate”, SLA/sapUu> <msgSize Size, …>, <aggre regat gatedB edBw, …> <asVM VM, URL, “location of AS VM”, functional component/as/image”> <aaaVM VM, …>

Application Server (AS) sapUu MTC-AAA vEPC_236 82_direct LTE RAN cpRan cpEpc cpEpcAs cpEpcAAA sapAAA sapAS cpAsEpc cpAAAEpc cpAAA cpAs

slide-9
SLIDE 9

Vertical Service Blueprint

15 April 2018 9

Fie ield ld Descr cript ption ion

Number of Application servers. n/a (provided by Translator) Images of virtual applications. vmAS: << <<urlAS lAS>> >> Virtual application connection end points cpAsEpc, cpAs Lifecycle operations To be defined Scaling rules Scale out: 80% load, Scale in: 60% load

Fie ield ld Descr cript ption ion

SST n/a (see the field SLA instead) Service constraints Geographical area: <<Coor

  • rdinates

dinates describi ibing ng the plant nt boundary> ndary>> sapAs location: << <<Met etroAr roArea ea of this sap>> p>> Security: low Priority: medium … Mgmt and control for tenant Provider managed SLA sapUu: <<N>> devices with <<rate> te>>msg/min of <<size> ize>>B. cpAs: << <<bwAs wAs>> >>bps cpAAA: 10Mbps latency sapUu – cpAsEpc: 50ms latency sapUu – cpAAAEpc: 50ms

slide-10
SLIDE 10

Vertical Service Descriptor

15 April 2018 10

Fie ield ld Descr cript ption ion

SST n/a … Service constraints Geographical area: city ity area area of

  • f Ul

Ulm and and surroundings

  • undings

sapAs location: Region

  • n_Ulm

Security: low Priority: medium … Mgmt and control for tenant Provider managed SLA sapUu: 500 500 devices with 1msg/min

  • f 200

200B. cpAs: 1Gbps cpAAA: 10Mbps latency sapUu – cpAsEpc: 50ms latency sapUu – cpAAAEpc: 50ms

Fie ield ld Descr cript ption ion

Name LorryMovement_ConstructionSite_Ulm Description The position of lorries on a big construction site in Ulm are monitored Version 1.1 Blueprint Xyz4711_bp Identity Abc0815_vsd

slide-11
SLIDE 11

Translator/Arbitrator

  • Map vertical service to network slice
  • NFV NSD used as network slice template
  • Structural information in VSD is similar to NSDs
  • Cardinalities, availability, …
  • Additional decisions to take (Arbitrator)
  • Map to existing network slice or create new one?
  • Isolation requirement
  • Sensor monitoring example: security: low
  • several instances in same NSI, even of different verticals
  • Map (composed) vertical service to one or to several network slices?
  • Same or different lifecycle of parent/child VSDs?
  • Isolation requirements
  • Describe connectivity among network slice instances

15 April 2018 11

slide-12
SLIDE 12

Network Service Descriptor

  • Even for simple vertical service, network

slice may contain many VNFs

  • No placement decisions by 5GT-VS
  • Enhance SAP definition with location

information

  • Enhance pointToPointConnectionConstraint

with endpoint information to express latency constraint along path

  • Placement decision by 5GT-SO

15 April 2018 12

GGSN/ P-GW SMS-SC GMSC/ IWMSC

T4 S6m Rf/Ga Um/ Uu/ LTE-Uu MTC UE Application

MME

Gi/SGi

SGSN S-GW

UE

MSC

RAN

T6a T6b

HSS

Tsms

Application Server (AS)

IP-SM-GW CDF/ CGF SME MTC-IWF MTC AAA

S6n E SGd Gd

SCEF

S6t SGs

Services Capability Server SCS

T8 Tsp Gi/SGi

slide-13
SLIDE 13

Arbitration

  • Resources are limited
  • Bandwidth, storage, processing capacity, …
  • Some vertical services might not get all the resources they need
  • Provide resources to high-priority vertical services, accept KPI degradation for low-

priority ones

  • Vertical and provider agree on resource budget
  • Assign priorities to vertical service instances
  • Assign resources to high-priority services of the vertical
  • Arbitrator encodes this assignment in deployment flavours of NSDs
  • Arbitrator may modify NSD computed by Translator
  • Reassignment when vertical services are instantiated or terminated
  • 5GT-SO scales vertical services within the limits of deployment flavours
  • Unaware of priorities

15 April 2018 13

slide-14
SLIDE 14

Arbitration (contd.)

  • Storage/memory
  • Assign according priority
  • Processing/bandwidth
  • Focus on service

vice la latenc ncy

  • Processing time in VNFs
  • Network travel time
  • Service latency depends on future

placement by 5GT-SO

  • Extend NSD with deployment

flavours for best and worst case

  • At vertical service instantiation
  • Default DF: worst case
  • Optional DF: best case
  • Best case deployment flavour
  • VNFs deployed to same serve

ver, zero network

  • rk trave

vel tim ime

  • Sufficient logical cores, such that

processing time satisfies latency requirement

  • Worst case deployment flavour
  • VNFs deployed to dif

iffer erent ent serve vers rs, non non-ze zero

  • netwo

work rk trave vel tim ime

  • Sufficient logical cores and

bandwidth, such that processing plus network travel time satisfies latency requirement

15 April 2018 14

slide-15
SLIDE 15

Summary and Outlook

  • Different descriptions and main components of the 5GT-VS

have been presented

  • Vertical service blueprints and descriptors, network service descriptors
  • Translator, Arbitrator
  • PoC implementation about to start
  • Evaluate algorithms
  • Complement catalogue of blueprints with possibility to compose

vertical services from building blocks

15 April 2018 15