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. Landi, X. Li, J. Mangues, N. Molner Barcelona, April 15, 2018

Overview • Motivation • 5G-TRANSFORMER system • Vertical service descriptions • Translation to network slices • Arbitration • Summary 15 April 2018 2

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

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

5G-TRANSFORMER system architecture Vertical Slicer Service Orchestrator Mobile Transport and Computing Platform 15 April 2018 5

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

Vertical Service Descriptions • Vertical Service Blueprint • Incomplete description of a vertical service • Required latency, throughput , … • Coverage area Missing information • VM image of vertical application provided by vertical • Created by 5G-TRANSFORMER service provider • Vertical Service Descriptor • Complete description of vertical service • Multiple instances of same vertical service possible VSD/NSD Translator, • Network Service Descriptor (ETSI NFV) Arbitrator • n:m relation to vertical service instances • Used as network slice template • Passed to 5GT-SO 15 April 2018 7

Vertical Service Blueprint Fie ield ld Descr cript ption ion Fie ield ld Descr cript ption ion Name LTE Sensor Monitoring Atomic functional vEPC_23682_indirect, 4GRAN, Description … reference architecture in 3GPP 23.682, indirect components MTC-AAA, AS mode. … application server and AAA server are involved provided by the vertical. Service sequence sapUu cpRan cpEpc cpEpcAs sapAS Version 1.0 cpAsEpc cpAs Identity Xyz4711_bp vEPC_236 Application LTE RAN 82_direct Server (AS) Parameters <cover erageA ageArea rea , Coordinates, “LTE coverage MTC-AAA area”, Service Constraints/Geographical area> cpAAAEpc cpAAA <sapLoc Locat atio ion , Coordinate, “Location of SAP”, cpEpcAAA sapAAA Connectivity service sapAS - cpAs, sapAAA - cpAAA, Service Constraints/sapAS Location> cpAsEpc – cpEpcAs, cpAAAEpc - <deviceA iceAmount mount, Int , “amount of sensors”, cpEpcAAA: L3VPN SLA/sapUu> sapUu: 4G <msgRate ate, Int , “sensor msg rate”, SLA/ sapUu> External sapAS, sapAAA, sapUu <msgSize Size , …>, < aggre regat gatedB edBw , …> interconnection <asVM VM , URL, “location of AS VM”, functional Internal n/a (no other services, except those component/as/image”> interconnection listed already are needed) <aaaVM VM , …> 15 April 2018 8

Vertical Service Blueprint Fie ield ld Descr cript ption ion SST n/a (see the field SLA instead) Service Geographical area: <<Coor ordinates dinates describi ibing ng constraints the plant nt boundary> ndary>> Fie ield ld Descr cript ption ion sapAs location: << <<Met etroAr roArea ea of this sap>> p>> Number of n/a (provided by Translator) Security: low Application servers. Images of virtual vmAS: << <<urlAS lAS>> >> Priority: medium applications. … Virtual application cpAsEpc, cpAs Mgmt and Provider managed connection end control for points tenant Lifecycle operations To be defined SLA sapUu: <<N>> devices with <<rate> te>>msg/min of Scaling rules Scale out: 80% load, <<size> ize>>B. Scale in: 60% load cpAs: << <<bwAs wAs>> >>bps cpAAA: 10Mbps latency sapUu – cpAsEpc: 50ms latency sapUu – cpAAAEpc: 50ms 15 April 2018 9

Vertical Service Descriptor Fie ield ld Descr cript ption ion Fie ield ld Descr cript ption ion Name LorryMovement_ConstructionSite_Ulm SST n/a … Description The position of lorries on a big construction site Service constraints Geographical area: city ity area area of of Ul Ulm in Ulm are monitored and surroundings and oundings Version 1.1 sapAs location: Region on_Ulm Blueprint Xyz4711_bp Security: low Identity Abc0815_vsd Priority: medium … Mgmt and control Provider managed for tenant SLA sapUu: 500 500 devices with 1msg/min of 200 200B. cpAs: 1Gbps cpAAA: 10Mbps latency sapUu – cpAsEpc: 50ms latency sapUu – cpAAAEpc: 50ms 15 April 2018 10

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

Network Service Descriptor IP-SM-GW SMS-SC Tsms GMSC/ SME IWMSC CDF/ E MTC • Even for simple vertical service, network CGF HSS AAA T4 SGd S6n Gd slice may contain many VNFs Rf/Ga S6m • No placement decisions by 5GT-VS MTC-IWF Tsp • Enhance SAP definition with location S6t Services Capability Application SCEF information Server Server T8 SCS (AS) Gi/SGi • Enhance pointToPointConnectionConstraint T6a Gi/SGi with endpoint information to express latency GGSN/ P-GW constraint along path T6b • Placement decision by 5GT-SO Um/ Uu/ LTE-Uu MSC SGs RAN MME MTC UE UE Application SGSN S-GW 15 April 2018 12

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

Arbitration (contd.) • Storage/memory • Assign according priority • Best case deployment flavour • Processing/bandwidth • VNFs deployed to same serve ver, • Focus on service vice la latenc ncy zero network ork trave vel tim ime • Processing time in VNFs • Sufficient logical cores, such that • Network travel time processing time satisfies latency requirement • Service latency depends on future placement by 5GT-SO • Worst case deployment flavour • Extend NSD with deployment • VNFs deployed to dif iffer erent ent serve vers rs, flavours for best and worst case non non-ze zero o netwo work rk trave vel tim ime • Sufficient logical cores and • At vertical service instantiation bandwidth, such that processing • Default DF: worst case plus network travel time satisfies • Optional DF: best case latency requirement 15 April 2018 14

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