1 / 33

Multiple industry standards The 3GPP Approach

Multiple industry standards The 3GPP Approach. Track: Managing NGN. Date/Time: Thursday November 16 th , 3:15 - 4:15 pm. Session: Next Generation Element Management and OSS Integration. Contact: Michael Truss, E-Mail: Michael.Truss@motorola.com. Agenda.

aquene
Download Presentation

Multiple industry standards The 3GPP Approach

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multiple industry standards The 3GPP Approach Track: Managing NGN. Date/Time: Thursday November 16th, 3:15 - 4:15 pm. Session: Next Generation Element Management and OSS Integration. Contact: Michael Truss, E-Mail: Michael.Truss@motorola.com

  2. Agenda • Third Generation Partnership Project (3GPP). • Integration Reference Point (IRP) – Introduction. • IRP Components. • The Alarm IRP. • Current Status. • Co-operative Efforts.

  3. 3rd Generation Partnership Project (3GPP) 3GPP: founded in 1998, by a number of regional standard bodies: • ARIB, TTC (Japan) • ETSI (Europe) • T1 (U.S.A.) • TTA (Korea) • CWTS (China) • Goal : globally applicable Technical Specifications for a 3rd Generation Mobile System based on the evolved GSM core networks and the Universal Terrestrial Radio Access (UTRA, both FDD and TDD modes). ARIB - Association of Radio Industries and Businesses. TTC – Telecommunication Technology Committee. ETSI - European Telecommunication Standards Institute. T1 – Standards Committee T1 Telecommunications. TTA – Telecommunication Technology Association. CWTS - China Wireless Telecommunication Standard. Web Page: http://www.3gpp.org

  4. Project Co-ordination Group TSG-GERAN TSG-CN TSG-RAN TSG-SA TSG-T Service andSystem Aspects Core Network GSM-EDGE Radio Access Network Radio Access Network Terminals 3GPP Structure Technical Specification Groups (TSG’s) SA1 - Services SA2 - Architecture SA3 - Security SA4 - Codec SA5 - Telecom Management

  5. SA5 Plenary Group CH CM FM PM AR-PR CM CM TSG-T Charging & Billing Architecture & Principles Configuration Management Fault Management Performance Management SA5 (Telecom Management Group) Structure Ad-Hoc Working Groups

  6. Third Generation Partnership Project (3GPP). • IRP Components. • The Alarm IRP. • Current Status. • Co-operative Efforts. Agenda • Integration Reference Point (IRP) – Introduction.

  7. IntroductionSummary of IRP (Integration Reference Point) concept • Towards the goal of embracing multiple interface technologies (CORBA, CMIP, SNMP, WBEM……) 3GPP SA5 has developed the concept of Integration Reference Points (IRPs) - enablers for application integration. • IRPs define the point of information exchange and the communication protocol(s) used between management systems/applications and external entities using standard technologies. CORBA = Common Object Request Broker Architecture CMIP = Common Management Information Protocol SNMP = Simple Network Management Protocol WBEM = Web Based Enterprise Management

  8. The Cornerstones of the IRP concept • Top-down, process-driven modelling approach The purpose of each IRP is automation of one specific task, related to the TMF Telecom Operations MAP (TOM). This allows taking a "one step at a time" approach with a focus on the most important tasks. • Protocol-independent modellingEach IRP consists of a protocol-independent model (the IRP information model) and several protocol-dependent models (IRP solution sets). • Standard based protocol dependent modellingModels in different IRP solution sets (CORBA, CMIP, SNMP, WBEM etc.) are "hand crafted" to the specifics of the corresponding protocol environment.

  9. Performance Data IRP Notification IRP Alarm IRP Element Manager NE PSA PSA IRPs for application integration Network Manager Service Activation Configuration& Inventory Management Fault Management Performance Monitoring/Data Warehousing Configuration & Service IRP PSA = Product Specific Application NE = Network Element

  10. Agenda • Third Generation Partnership Project (3GPP). • Integration Reference Point (IRP) – Introduction. • The Alarm IRP. • Current status. • Co-operative Efforts • IRP Components.

  11. IRP Components - 1 • IRP Information Model • An IRP Information Model consists of an IRP Information Service and a ResourceModel ( see below fordefinitions of IRP Information Service and Resource Model ). • IRP Information Service: • An IRP Information Service describes the information flow andsupport objects fora certain functional area, e. g. the alarm information service in the faultmanagement area. As an example of support objects, for the Alarm IRP there isthe alarm recordandalarm list . • Resource Model: • A protocol independent model describing managed object s representing networkresources, e.g. an RNC or NodeB. • IRP Solution Set: • An IRP Solution Set is a mapping of the IRP Information Service to one of severaltechnologies ( CORBA/ IDL, SNMP/ SMI, CMIP/ GDMO, etc.). An IRP InformationService can be mapped to several different IRP Solution Sets. Differenttechnology selections may be done for different IRP’s.

  12. IRP Information Model Network Resource Model IRP Information Service SOLUTION SETS SNMP WBEM CMIP CORBA IRP Components - 2

  13. Agenda • Third Generation Partnership Project (3GPP). • Integration Reference Point (IRP) – Introduction. • IRP Components. • Current Status. • Co-operative Efforts • The Alarm IRP.

  14. Alarm IRP Overview

  15. Alarm IRP Introduction • Supports the Alarm Surveillance service component of Fault Management. • Defines four types of alarm notifications: • New alarm. • Changed alarm. • Cleared alarm. • Alarm list rebuilt. • Alarm notification attributes: • Attributes and values based on M.3100, X.733, X.736, GSM 12.11. • Mandatory attributes of X.733 alarm notification supported. • Added to X.733 alarm notification attributes: • Alarm ID, System name. • Acknowledgement and comments related values added to additional_info attribute

  16. (System) (Actor) Alarm IRP Information Service - 1 Operations and Notifications described in Unified Modeling Language ( UML)

  17. Alarm IRP Information Service – 2 Support Objects - Alarm List and Alarm Record • Alarm list: A list of alarm objects or alarm records whose alarm information is active (i.e., the severity level is not cleared). • Alarm Record : Contains the following attributes: • Alarm Id [M] • System Name [M] • Managed Object Class [M] • Managed Object Instance [M] • Event Time [M] • Event Type [M] • Probable Cause [M] • Perceived Severity [M] • Specific Problems [O] • Correlated Notifications [O] • Additional Text [O] • Additional Info [O]

  18. 0..N (c) 3GSubNetwork (a) 1 1 0..1 0..1 OR 0..N (b) 0..N ManagementNode 0..1 managedBy 0..M (b) 0..N 1 3GManagedElement (e) MEContext (d) manages 0..N IRP Resource Model Extract

  19. Alarm IRP CORBA Solution Set Extract /* This interface specifies all methods supported by System as specified in 3GPP AlarmIRP: CORBA Solution Set version 1:1. */ interface AlarmIRPOperations { CommonIRPConstDefs::Signal acknowledge_alarms ( in AlarmIRPConstDefs::AlarmInformationIdSeq alarm_information_id_list, in string ack_user_id, in string ack_system_id, out AlarmIRPConstDefs::AlarmInformationIdSeq bad_alarm_information_id_list ) raises (AcknowledgeAlarms,ParameterNotSupported,InvalidParameter);

  20. Alarm IRP CMIP Solution Set Extract 5.3.1 acknowledgeAlarms (M) acknowledgeAlarms ACTION BEHAVIOUR acknowledgeAlarmsBehaviour; MODE CONFIRMED; WITH INFORMATION SYNTAX TS32-111-AlarmAsn1TypeModule.AckOrUnackAlarms; WITH REPLY SYNTAX TS32-111-AlarmAsn1TypeModule.AckOrUnackAlarmsReply; REGISTERED AS { ts32-111AlarmAction 1}; acknowledgeAlarmsBehaviour BEHAVIOUR DEFINED AS ”This action is invoked by the Manager to indicate to the Agent that one or several alarms (previously sent by the Agent as alarm notifications) have to be acknowledged. In the action request the NM supplies the parameter ackUserId and ackSystemId. The other acknowledgement history parameters, i.e. alarm acknowledgement state (in this case acknowledged) and the acknowledgement time are set by the Agent itself………………………”

  21. Agenda • Third Generation Partnership Project (3GPP). • Integration Reference Point (IRP) – Introduction. • IRP Components. • The Alarm IRP. • Co-operative Efforts • Current Status.

  22. = Released Document (R99) = Draft Document (R99) = Planned Document (R00) 3GPP IRP Document List • Notification IRP Information Service 32.106 Part 2 • Notification IRP CORBA Solution Set 32.106 Part 3 • Notification IRP CMIP Solution Set32.106 Part 4 • Name Convention for Managed Objects: 32.106 Part 8 • Alarm IRP Information Service 32.111 Part 2 • Alarm IRP CORBA Solution Set 32.111 Part 3 • Alarm IRP CMIP Solution Set 32.111 Part 4 • Basic Configuration Management IRP Information • Model (Information Service + Resource Model) 32.106 Part 5 • Basic Configuration Management IRP CORBA • Solution Set 32.106 Part 6 • Basic Configuration Management IRP CMIP • Solution Set 32.106 Part 7

  23. Other possible IRPs and Solution Sets • Performance Management IRP. • Bulk Configurtion Management IRP. • SNMP Solution Sets for Notification, Alarm and Configuration Management. • WBEM Solution Sets for Configuration Management. • Security Management IRP.

  24. Agenda • Third Generation Partnership Project (3GPP). • Integration Reference Point (IRP) – Introduction. • IRP Components. • The Alarm IRP. • Current Status. • Co-operative Efforts

  25. A Co-operative agreement is in place between the 3GPP Telecom Management group and the 3GPP2 OAM&P group, Under this agreement 3GPP2 will reference the 3GPP IRP specifications. The 3GPP IRP specifications have been used in the development of the Common Configuration Management Catalyst Showcase at TMF, and CCM work is being used to feedback into the IRP specifications. Co-operative Efforts

  26. 3rd Generation Partnership Project 2 (3GPP2) 3GPP2: founded in 1998, by a number of regional standard bodies: • ARIB, TTC (Japan) • TIA (U.S.A.) • TTA (Korea) • CWTS (China) Goal :Global Specifications for ANSI/TIA/EIA-41 network evolution to 3G and global specifications for the RTTs supported by ANSI/TIA/EIA-41. ARIB - Association of Radio Industries and Businesses. ANSI – American National Standards Institute. TTC – Telecommunication Technology Committee. RTTs – Radio Transmission Technologies. TIA – Telecommunication Industry Association. EIA – Electronic Industries Alliance. TTA – Telecommunication Technology Association. CWTS - China Wireless Telecommunication Standard. Web Page: http://www.3gpp2.org

  27. 3GPP2 Steering Committee TSG-P TSG-A TSG-N TSG-C All-IP AdHoc TSG-S Service and System Aspects Wireless Packet Data Interworking ANSI-41 / WIN A-Interface System cdma2000 All-IP NW Requirements & Architecture 3GPP2 Structure Technical Specification Groups (TSG’s) WG1 – Features & Services Requirements WG2 – Network Reference Model & OAM&P PMT – Program Management Team

  28. Backup Slides

  29. Notification IRP

  30. Basic Configuration Managemnent IRP

  31. Alarm IRP and TOM

  32. Configuration Management IRP and TOM

More Related