3GPP SA5 Inputs for NFV Information Modelling Workshop January 13-14, 2016 Louisville, CO

3GPP SA5 Telecom Management ToR SA WG5 will specify the requirements, architecture and solutions for provisioning and management of the network (RAN, CN, IMS) and its services. The WG will define charging solutions in alignment with the related charging requirements developed by the relevant WGs, and will specify the architecture and protocols for charging of the network and its services. The WG will ensure its work is also applicable to the management and charging of converged networks, and potentially applicable to fixed networks. The WG will coordinate with other 3GPP WGs and all relevant SDOs to achieve the specification work pertinent to the provisioning, charging and management of the network and its services. http://www.3gpp.org/Specifications-groups/sa-plenary/56-sa5-telecom-management

3GPP SA5 Leadership SA5 Charging Sub-Working Group (SWG) Thomas Tovinger (Ericsson) Chair since 08/2015 Jean-Michel Cornily (Orange) VC since 08/2013 Christian Toche (Huawei) VC since 08/2015 Charging Sub-Working Group (SWG) Maryse Gardella (Alcatel-Lucent) Chair since 08/2013 David Shrader (Ericsson) VC since 08/2013 Li Li (Huawei) VC since 08/2014 OAM&P Sub-Working Group (SWG) Christian Toche (Huawei) Convenor since 10/2015

3GPP SA5 Organization Six face-to-face one-week plenary meetings per year Two Asia, two Europe, two North-America SWGs meet in parallel most of the time Average 350 documents per meeting Around 50 delegates attending meetings Conference calls between F2F meetings when needed Work is based on company contributions Need at least four supporting companies for a Work Item or Study Item Use of consensus rule for decisions SA5 outputs are approved every quarter by TSG SA plenary 3GPP specifications are grouped into Releases SA5 has about 250 specifications 32-series for FCAPS/Charging functionalities for Mobile Network 28-series for Converged Management of Fixed & Mobile Networks and NFV Release 13 closure in December 2015 Release 14 closure target in March 2017

3GPP Management Reference Model (TS 32.101) 1: Between the Network Elements (NEs) and the Element Manager (EM) of a single broadband wireless network 2: Between the Element Manager (EM) and the Network Manager (NM) of a single broadband wireless network 3: Between the Network Managers and the Enterprise Systems of a single broadband wireless network 4: Between the Network Managers (NMs) of a single broadband wireless network 4a: Between the Domain Managers (DMs) of a single broadband wireless network 5: Between Enterprise Systems & Network Managers of different broadband wireless networks 5a: Between the Domain Managers (DMs) of different broadband wireless networks 6: Between Network Elements (NEs) 7: Between the Network Management Layer Service (NMLS) and the Network Manager (NM). 3GPP Management Standards Focus

Requirements / Use Cases 3GPP SA5 IRP Concept Solution Set Definitions (CORBA, XML, SOAP) Requirements / Use Cases Information Service (UML) Solution Set Definitions (other/future) Relatively stable over long period of time Change with new/better technologies Change only with respect to functional addition and corrections Interface IRPs Notification IRP Alarm IRP Bulk CM IRP Kernel CM IRP Basic CM IRP PM IRP Etc Network Resource Model (NRM) IRPs Generic NRM IRP UTRAN NRM IRP E-UTRAN NRM IRP IMS NRM IRP EPC NRM IRP Data Definition IRPs State Management IRP

Interface IRP & NRM IRP Itf-N Network Manager (NM) Interface IRPs Defining HOW information is shared (Operations & Notifications) Network Manager (NM) User Equipment Core/IMS Network Radio Access Network DM/EM Network Resource Model (NRM) IRPs Defining WHAT can be managed (Object Models) Itf-N DM/EM

IRP Development Principles NRM IRP Extendibility NRM extensions (e.g. sub-classing) Vendor specific NRM extensions VsDataContainer Interface IRP Flexibility Use of qualifiers “mandatory”, “optional”, “visibility” for operation, notifications and parameters NRM/Technology-neutrality Not just for mobile networks

IRP Methodology Specifications TS 32.150 Integration Reference Point (IRP) Concept and definitions TS 32.151 IRP Information Service (IS) template (applicable to 32-series IRPs) TS 32.152 IRP IS Unified Modeling Language (UML) repertoire (applicable to 32-series IRPs) TS 32.153 IRP technology specific templates, rules and guidelines TS 32.154 Backward and Forward Compatibility Concept and definitions TS 32.155 Requirements template TS 32.156 Fixed Mobile Convergence (FMC) Model repertoire (applicable for FMC) TS 32.157 IRP Information Service (IS) template (applicable for FMC)

Cooperation with NGMN & TM Forum (1/6) Multi-SDO Cooperation on Converged Management of Fixed & Mobile Networks Joint Working Groups (JWG) on Model Alignment and Converged PM SA5 has created the 28-series specifications based on the JWG outputs Outputs of Multi-SDO JWG on Model alignment TS 32.107 Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) TS 28.620 Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM) TS 32.156 Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire TR 32.854 Telecommunication management; Fixed Mobile Convergence (FMC) 3GPP / TM Forum concrete model relationships and use cases TR 28.820 Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Operation Model (FNOM) Umbrella Operation Model (UOM)

Cooperation with NGMN & TM Forum (2/6) TS 32.107 Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) The Federated Network Information Model allows a number of standards and specifications generated by different organizations to function together to bring greater coherence to the management of converged networks and hence reduce operations costs. TS 28.620 Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM) The UIM is the part of the FNIM that represents the agreed model structures that 3GPP SA5 and TM Forum use (via “specific linkages” including inheritance, mappings and other derivations) for the definition of their respective Domain/Technology-specific concrete classes. The use of UIM maximizes the probability of the Domain/Technology-specific concrete classes being semantically consistent, a necessary characteristic for FMC.

Cooperation with NGMN & TM Forum (3/6) TS 32.156 Fixed Mobile Convergence (FMC) model repertoire This document defines how UML should be used to specify technology neutral Information Models (i.e. object classes, attributes, associations, association classes, stereotypes, data types) for Fixed Mobile Converged (FMC) management interfaces. ITU-T SG2 have decided to include 32.156 in their Requirements/Analysis methodology which is aligned with SA5. TR 32.854 Fixed Mobile Convergence (FMC) 3GPP / TM Forum concrete model relationships and use cases This document describes operator use cases and requirements requiring some harmonization between 3GPP and TM Forum models. Overlaps and gaps of the 3GPP and TM Forum models are highlighted. TR 28.820 Fixed Mobile Convergence (FMC) Federated Network Operation Model (FNOM) Umbrella Operation Model (UOM) The Umbrella Information Model (UIM) define the common model artifacts that will be used by the SDOs as a basis for their specific Fixed Mobile Converged (FMC) model instances. In addition to the UIM containing common “super classes” (incl. their attributes and associations), this document contains the common “interface super classes” (incl. their operations and notifications).

Cooperation with NGMN & TM Forum (4/6) Output of Multi-SDO JWG on Converged Management PM Interface definitions TR 32.863 Fixed Mobile Convergence (FMC) Metadefinitions for Measurements and KPIs This document defines the metadata for Performance Management (PM) performance measurements (KPIs and counters). The definition enforce consistency in description of all standardized performance measurements by various SDOs and organizations involved in the Management of Converged Networks. This consistency facilitates encoding and decoding of performance measurements exchanged via management protocols and/or stored in databases or files.

Umbrella Information Model Class Diagram (Extract from 3GPP TS 28.620) Cooperation with NGMN & TM Forum (5/6) Umbrella Information Model Class Diagram (Extract from 3GPP TS 28.620)

Cooperation with NGMN & TM Forum (6/6) Alarm flow through IRP Agent for NE with wireless access (Extract from 3GPP TR 32.854)

3GPP SA5 views on NFV modeling (1/3) The following diagram extracted from NFVIFA(15)0001298r4 gives the context of 3GPP views presented in the next slides Application View Outside of ETSI NFV scope Logical View

3GPP SA5 views on NFV modeling (2/3) Class relations regarding Vnf/Vnfc ManagedFunction is a kind of Function_ of 3GPP TS 28.620 (see slide 14). Vnf/Vnfc are standard terms in ETSI NFV specifications. The specifications of the bilateral relation-1 & relation-2 are subjects of investigation by the model harmonization activities. For example: The synchronization of ManagedFunction attribute(s), including identifiers (or Distinguished Names), with the corresponding attribute(s) of Vnf for Relation-1 or Vnfc for Relation-2. Dependencies of the life cycle states of ManagedFunction and Vnf/Vnfc instances.

3GPP SA5 views on NFV modeling (3/3) View on VNF VNF is composed of two main parts: An application-related part and A virtualization-related part. Use of the term ‘platform’ is under discussion.

3GPP SA5 recommendations (1/2) ETSI NFV is responsible for modeling the ETSI logical view. 3GPP SA5 is responsible for modeling the “application-specific aspects” of all 3GPP defined VNFs. 3GPP SA5 will use the current 3GPP SA5 methodology for the production and maintenance of 3GPP SA5 specifications for management of mobile networks that includes VNFs. 3GPP SA5 does not recommend to conduct model harmonization work between 3GPP SA5 defined managed function (e.g. VNF) application-specific model and all other SDO-defined application-specific models.

3GPP SA5 recommendations (2/2) 3GPP SA5 recommends to harmonize views on the following aspects among ETSI ISG NFV, 3GPP SA5 and all other related SDOs: Relation-1 (relation between ManagedFunction and Vnf) Relation-2 (relation between ManagedFunction and Vnfc) 3GPP SA5 recommends to have a clear separation of the management protocols and the information that the protocols carry (as done in 3GPP SA5 IRP methodology). 3GPP SA5 recommends SDOs to use the 3GPP-TM Forum Umbrella Information Model as the base for SDOs’ model harmonization work.

Annexes

Requirements & Architecture Specifications TS 32.101 Principles and high level requirements TS 32.102 Architecture TS 32.103 Integration Reference Point (IRP) overview and usage guide TS 32.111-1 3G Fault Management requirements TS 32.140 SuM requirements TS 32.141 SuM architecture TS 32.300 Name convention for Managed Objects TS 32.401 Performance Management concept and requirements TS 32.500 SON concepts and requirements TS 32.511 ANR management concepts and requirements TS 32.541 SON self-healing concepts and requirements TS 32.551 Energy Saving Management concepts and requirements TS 32.600 Configuration Management concept and high-level requirements

Interface IRPs Common IF IRPs Notification IRP (32.30x) Generic IRP (32.31x) CM-related IF IRPs Basic CM IRP (32.60x) Bulk CM IRP (32.61x) Kernel CM IRP (32.66x) Other IF IRPs Partial Suspension (32.38x) Delta synchronization (32.39x) FM-related IF IRPs Alarm IRP (32.111-x) AAM IRP (32.12x) Test Mgmt IRP (32.32x) SON-related IF IRPs Self-Configuration IRP (32.50x) Software Management IRP (32.53x) Supporting IF IRPs Notification Log IRP (32.33x) File Transfer IRP (32.34x) Communication Surveillance IRP (32.35x) Entry Point IRP (32.36x) PM-related IF IRPs PM IRP (32.41x) PM collection (32.43x) Trace Mgmt (32.42X, 32.44x)

Network Resource Model (NRM) IRPs FMC model Umbrella Information Model (28.620) Common NRM IRP Generic NRM IRP (28.621/2/3) Services related NRM IRPs SuM NRM IRP (28.751/2/3) 3GPP Core Network NRM IRPs Core NRM IRP (28.701/2/3) IMS NRM IRP (28.704/5/6) EPC NRM IRP (28.707/8/9) 3GPP H(e)NS NRM IRPs HNS NRM IRP (28.671/2/3) HeNS NRM IRP (28.674/5/6) 3GPP Access Network NRM IRPs Generic RAN NRM IRP (28.661/2/3) GERAN NRM IRP (28.654/5/6) UTRAN NRM IRP (28.651/2/3) E-UTRAN NRM IRP (28.657/8/9) Supporting NRM IRPs Inventory Management NRM IRP (28.631/2/3) Transport Network NRM IRP (28.731/2/3) Signalling Transport NW IF NRM IRP (28.734/5/6)

Useful Links 3GPP portal https://portal.3gpp.org/ 3GPP SA5 home page http://www.3gpp.org/Specifications-groups/sa-plenary/56-sa5-telecom-management 3GPP SA5 specifications http://www.3gpp.org/ftp/Specs/html-info/TSG-WG--S5.htm http://www.3gpp.org/ftp/Specs/archive/32_series/ http://www.3gpp.org/ftp/Specs/archive/28_series/ 3GPP SA5 meeting documents http://www.3gpp.org/ftp/tsg_sa/WG5_TM/ 3GPP SA5 email lists http://list.etsi.org/3gpp_tsg_sa_wg5.html http://list.etsi.org/3gpp_tsg_sa_wg5_oam.html http://list.etsi.org/3gpp_tsg_sa_wg5_charging.html

Thank You ! www.3gpp.org contact@3gpp.org