1 / 40

IMT2000 의 망관리 규격 표준화 동향

IMT2000 의 망관리 규격 표준화 동향. 삼성전자 안일수. 목차. Overview Architecture Configuration Management Fault Management Performance Management Charging and Billing References. 3GPP. Third Generation Partnership Project ETSI, ARIB, TTA, TTC, T1 and CWTS

freya
Download Presentation

IMT2000 의 망관리 규격 표준화 동향

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. IMT2000의 망관리 규격표준화 동향 삼성전자 안일수

  2. 목차 • Overview • Architecture • Configuration Management • Fault Management • Performance Management • Charging and Billing • References

  3. 3GPP • Third Generation Partnership Project • ETSI, ARIB, TTA, TTC, T1 and CWTS • 5 Technical Specification Groups (TSG) : CN, RAN, GERAN, T, SA • TSG SA : Services and System Aspects • 5 Working Groups : Services, Architecture, Security, Codec … • SA WG5 : Telecom Management • 5 Rapporteur Groups AR-PR, CM, FM, PM, CB • ftp://www.3gpp.org/TSG_SA/WG5_TM/

  4. SA WG5 • AR-PR • TS 32.102 : 3G Telecom Management Architecture • TS 32.101 : 3G Telecom Management: Principles and high level requirements • CM (Configuration Management) : TS 32.106-x • FM (Fault Management) : TS 32.111-x • PM (Performance Management) : TS 32.104 • CB (Charging & Billing) : TS 32.005 & 015

  5. ITU-T, GSM TMF Architectural Objectives Multi-Vendors Heterogeneous Flexible & rapid configurations Scalable Extensible Re-use relevant standards Utilize IT & datacom technologies Architecture Methodology Open Cost-effective Inter-operable Top-Down Approach TOM MCCM

  6. Functional Architecture Physical Architecture Information Architecture Architectural Relationships Business needs Cost Performance Legacy Preferences

  7. Functional Architecture • UMTS Management Processes • Based on TMF TOM (Telecom Operations Map) • Customer Care, Service Development & Operations, Network & Systems Management Processes • Management Functions • FCAPS, roaming, customer profile, service deployment • fraud management, software management • mapping management functions to management processes

  8. Telecom Operations Map (TOM) • Service based Vertical Development • Standardization • è Information & Scenario • FAB • (Fulfillment èAssurance • èBilling) • Component based Integration • & Automation • Top-Down Development Customer Fulfillment Assurance Billing Customer Interface Management Process Customer Order Invoicing/ Problem Sales QoS Handling Collection Handling Management Customer Care Processes Information Service Service Service Service Rating and Systems Planning/ Quality Problem Configuration Discounting Management Development Management Resolution Processes Service/Product Development and Operations Processes Network Network Network Network Data Network Planning/ Inventory Maintenance Management Provisioning Development Management & Restoration Network and Systems Management Processes Physical Network and Information Technology

  9. Physical Architecture • Inter-operability • focus change from element management to information management • Open architecture : reuse widely used standards & technologies • Interfaces • Ift-N : between the NE/EM and the NM OSF, standardized • Ift-T : between a terminal and the OSF, for further study (Rel. 5) • Management Application Protocol : CMIP, CORBA, SNMP • Application Protocol for bulk transfer : FTAM, FTP, TFTP • Network protocol : IP, X.25

  10. Integration Levels • Screen Integration • Unified screen : not to be standardized now • Application Integration • High-level generic interfaces • Between generic & product-specific applications • Define Network Infrastructure IRPs : top-down, open • Detailed (product-specific) interfaces • Between product-specific applications and NEs • Traditional TMN approach to EM : need not be open

  11. Information Architecture • IRP (Integration Reference Point) Specification • IRP Information Model : protocol independent • IRP Information Service • Network Resource Model • IRP Solution Sets : protocol dependent, CORBA & CMIP • Notification IRP • Basic Configuration Management IRP • Alarm IRP • Log IRP

  12. NE NE Integration Reference Points (IRPs) • IRPs for application integration Performance Monitoring / Data Warehouse Service Activation Inventory Management Fault Management Configuration Service IRPs (Including Notification IRP) Alarm IRP Performance Data IRP (?) IRP (alternative 1) IRP (alternative 2) EM/SNM EM/SNM PSA PSA Don’t care

  13. Configuration Management • TS 32.106-x (Rel. 99) • -1: 3G Configuration Management: Concept and Requirements • -2: Notification IRP: Information Service • -3: Notification IRP: CORBA Solution Set • -4: Notification IRP: CMIP Solution Set • -5: Basic Configuration Management IRP Information Model (inc. NRM) • -6: Basic Configuration Management IRP CORBA Solution Set • -7: Basic Configuration Management IRP CMIP Solution Set • -8: Name Convention for Managed Objects

  14. <<Interface>> NotificationIRPOperation • subscriber() • unsubscriber() • getNotificationIRPVersion() • getSubscriptionStatus() • getSubscriptionIds() • changeSubscription() • suspendSubscription() • resumeSubscription() • getNotificationCategories() implement use IRP Agent implement use Notification IRP : Information Services • TS 32.106-2 IRP Manager <<Interface>> NotificationIRPNotifications • notify()

  15. Operations & Notifications • Operations : invoked by IRPManager • subscribe : establish subscription to receive events via notifications • Input Parameters : managerReference, timeTick, notificationCategories, filter • Output Parameters : subscriptionId, status • unsubscribe: cancel subscription • Input Parameters : managerReference, subscriptionId • Output Parameter :status • Notificationnotify • IRPagent notifies the subscribed IRPManager that an event occurred • Notification header :managedObjectClass, managedObjectInstance, notificationId, eventTime, systemDN, eventType, extendedEventType

  16. IS Operations SS Methods subscribe attach_push, attach_push_b, attach_pull unsubscribe detach get Notification IRPVersion get_notification_IRP_version get Subscription Status get_subscription_status getSubscriptionIds get_subscription_ids Notification IRP : CORBA Solution Set • TS 32.106-3 : CORBA/IDL • CORBA Event Service : event routing & distribution • CORBA Notification Service : event filtering & support for QoS • Mapping IS Operations to SS Methods

  17. Common attributes defined in Notification IRP Attributes defined by OMG Structured Event eventType type_name extended EventType event_name managed Object Class, managed Object Instance One NV (name-value) pair of filterable_ body_fields notificationId One NV pair of filterable_ body_fields eventTime One NV pair of filterable_ body_fields systemDN One NV pair of filterable_ body_fields Notification IRP : CORBA Solution Set … • StructuredEvent : for OMG Notifications Service • Push_structured_events : pack multiple notifications • Mapping Notification attributes to OMG equivalents

  18. Operations of Information Services of the Notification IRP Equivalent GDMO Actions of the CMIP solution set subscribe subscribe unsubscribe unsubscribe suspendSubscription suspendSubscription resumeSubscription resumeSubscription changeSubscriptionFilter changeSubscriptionFilter getNotificationCategories getNotificationCategories Notification IRP : CMIP Solution Set • TS 32.106-4 : CMIP/GDMO • Operations mapped to CMIP Actions • Notifications sent by M_EVENT_REPORT • NotificationControl MOC : mapping between operations for subscription identifier and the local EFD

  19. IRP Agent Basic Configuration Management IRP : Information Model • TS 32.106-5 : IRP Information Service <<Interface>> BasicCmIRPOperations use • getMoAttributes() • getContainment() • getBasicCmIRPVersion() implement IRP Manager <<Interface>> BasicCMIRPNotifications use implement • notifyObjectCreation() • notifyObjectDeletion() • notifyAttributeValueChange()

  20. Operations & Notifications • Operations : invoked by IRPManager • getMoAttributes : retrieve name/value pairs for MO attributes • Input Parameters : baseObjectInstance, scope, filter, attributeListIn • Output Parameters : managedObjectClass, managedObjectInstance, attributeListOut, status • getContainment : retrive a list of all MO instances contained in a base object • Input Parameters : baseObjectInstance, scope • Output Parameter : containment, status • Notifications : with a Notification header • notifyObjectCreation : when a new MO has been created • notifyObjectDeletion : when a new MO has been deleted • notifyAttributeValueChange : one or several attributes of a MO has changed

  21. Generic Network Resource Model

  22. MOC definitions • MOC G3SubNetwork • Attributes : g3SubNetworkId, dnPrefix, userLabel • Notifications : notifyObjectCreation, notifyObjectDeletion, notifyAttributeValueChange, notifyAckStateChanged, notifyNewAlarm, notifyChangedAlarm, notifyClearedAlarm • MOC g3ManagedElement • Attributes : g3ManagedElementId, dnPrefix, userLabel, managedElementType, vendorName, userDefinedState, locationName, managedBy • Notifications : notifyObjectCreation, notifyObjectDeletion, notifyAttributeValueChange, notifyAckStateChanged, notifyNewAlarm, notifyChangedAlarm, notifyClearedAlarm

  23. UMTS NRM : UTRAN view

  24. UMTS NRM : CN view

  25. Basic Configuration Mgmt IRP : CORBA Solution Set • TS 32.106-6 : Map IS to IDL Equivalents • Map IS MOC to IDL interface • Map IS Operations to IDL Equivalents getMoAttributes BasicCmIrpOperations::find_managed_objects Iterator::get_next_elements Iterator::destroy getContainment BasicCmIrpOperations::find_managed_objects Iterator::get_next_elements Iterator::destroy getBasicCmIRPVersion get_basicCm_IRP_version

  26. Operations of Information Services of the Basic CM IRP Equivalent operation of the CMIP solution set of the Basic CM IRP getMoAttributes M-GET (CMISE Service) getContainment M-GET (CMISE Service) getBasicCmIRPVersion M-ACTIONgetBasicCmIRPVersion (Action of MOC bcmControl) Basic Configuration Mgmt IRP : CMIP Solution Set • TS 32.106-7 : CMIP/GDMO • Map IS MOC to CMIP MANAGED OBJECT CLASS • Map IS Operations & Notification to CMIP equivalents

  27. New CM Numbering (R4) • 32.600 : Configuration Management: Concept and Main Requirements • 32.300 : Name convention for Managed Objects (or Information Objects?) • 32.301-1 : Notification IRP: Requirements • 32.301-2 : Notification IRP: Information Service • 32.301-3 : Notification IRP: CORBA SS • 32.301-4 : Notification IRP: CMIP SS • 32.601-1 : Basic CM IRP: Requirements • 32.602-1 : Bulk CM IRP: Requirements • 32.620-1 : Generic Network Resources IRP: Requirements • 32.621-1 : Core Network Resources IRP: Requirements • 32.622-1 : UTRAN Network Resources IRP: Requirements • 32.623-1 : GERAN Network Resources IRP: Requirements

  28. Fault Management • TS 32.111-x • -1: 3G FaultManagement: Requirements • -2: Alarm IRP: Information Service • -3: Alarm IRP: CORBA Solution Set • -4: Alarm IRP: CMIP Solution Set • Concepts and Requirements • Fault detection, generation/clearing of alarms • Alarm forwarding & filtering, storage, fault recovery

  29. <<Interface>> AlarmIRPOperations <<Interface>> AlarmIRPNotifications • acknowledgeAlarms() • unacknowledgeAlarms() • getAlarmList() • getAlarmIRPVersion() • getAlarmCount() • notifyNewAlarm() • notifyChangedAlarm • notifyAlarmListRebuilt() • notifyAckStateChanged() • notifyClearedAlarm() IRP Agent IRP Manager Alarm IRP : Information Service • TS 32.111-2 : Operations & Notifications implement use implement use

  30. Operations & Notifications • Operations : invoked by IRPManager • getAlarmList: invoked by RPManager to get a list of alarms in Alarm List • Input Parameters :alarmAckState, filter • Output Parameters :alarmInformationList, status • acknowledgeAlarms: invoked by RPManager to acknowledge alarms • Input Parameters :alarmInformationReferenceList, AckUserId, ackSystemId • Output Parameter :badAlarmInformationReferenceList, status • Notifications • notifyNewAlarm: when a new alarm has been added into the Alarm List • Input Parameters :notificationHeader, alarmInformationBody • notifyChangedAlarm: when perceived severity level in Alarm Information changes • Input Parameters :notificationHeader, alarmInformationBody

  31. Alarm Behavior • Behavior • Alarm List • Network Resource Name • Alarm Information Identification • Alarm loss detection and recovery • Alarm List loss • Alarm Information • Alarm States

  32. IS Operation / Notification SS Method getAlarmList get_alarm_list getAlarmCount get_alarm_count acknowledgeAlarms acknowledge_alarms notifyNewAlarm push_structured_events notifyChangedAlarm push_structured_events notifyClearedAlarm push_structured_events Alarm IRP : CORBA Solution Set • TS 32.111-3 : CORBA/IDL • Mapping IS Operations to SS Methods • CORBA Event Service : event routing & distribution • CORBA Notification Service : event filtering & support for QoS

  33. Operations & Notifications of IS CMIP SS Actions & Notifications getAlarmCount getAlarmCount getAlarmList getAlarmList acknowledgeAlarms acknowledgeAlarms notifyNewAlarm notifyChangedAlarm ... notifyAckStateChanged environmentalAlarm equipmentAlarm ... communicationAlarm notifyAlarmListRebuilt alarmListRebuilt Alarm IRP : CMIP Solution Set • TS 32.111-4 : CMIP/GDMO • Operations mapped to CMIP Actions • Notifications sent by M_EVENT_REPORT • alarmControl MOC : with ACTIONS and NOTIFICATIONS

  34. Performance Management • Concept & Requirements • Measurement data • traffic measurements Network configuration evaluation • Resource access Quality of Service • Resource Availability • Measurement Schedule : start and stop time • The granularity period : 5 minutes, 15 minutes, 30 minutes, 1 hour • Measurement reporting : scheduled measurement reports • Measurement job state and status attributes • Measurement job administration • Create, Modify, Display, Delete, Suspend, Resume

  35. Performance Data • Measurement Report File : Naming <Type><Startdate>.<Starttime>-<Enddate>.]<Endtime>_<UniqueId>[:<RC>] • Measurement Report File : Format • measFileHeader, measData, measFileFooter • ASN.1 Specification • XML Specification: using DTD • Measurement Definition Template DescriptionCollection Method Condition Measurement Result Measurement TypeMeasurement Object InstanceSwitching Technology • Only measurement types specific to 3G networks are defined • Measurements for RNC, NodeB, MSC, HLR, VLR, EIR … • May re-use GSM measurements

  36. Charging and Billing • Circuit Switched Domain (Circuit Service) : TS 32.005 (Rel. 99) • Define management services (tariff administration, data collection) • Tariff administration • Tariff class management • Tariff period management • Day class management • Tariff management • Tariff system management • Data collection : Data generation control, Data transfer control • Bulk transfer : FTAM

  37. Charging and Billing • Packet Switched Domain (Packet Service) : TS 32.015 (Rel. 99) • Transfer charging information from the SGSN and GGSN nodes to the network operator’s chosen Billing Systems(BS) through Charging Gateway Functionality(CGF) • Charging Data Collection Types • S-CDR : GPRS charging data in SGSN • G-CDR : GPRS charging data in GGSN • M-CDR : GPRS MS mobility management data in SGSN • S-SMO-CDR : GPRS MO SMS data in SGSN • S-SMT-CDR : GPRS MT SMS data in SGSN • Charging Protocol : GTP (Optional) • Information format of CDRs : ASN.1

  38. Current Activities • Rel. 4 : June, 2001 • Rel. 5 : March, 2002 • New numbering for Charging/Billing : TS 32.200 • TS 32.205 CS implementor's guide (<- 32.005) • TS 32.215 PS implementor's guide (<- 32.015) • New work items • Subscription Management • User Equipment (Terminal) Management • Use of CORBA in the TMN (Liaison with ITU-T SG4) • tML : XML for telecommunications applications (by T1M1 & ITU-T)

  39. References (Rel. 99) Title Type Number Frozen Ver. Location Telecommunications Management; Charging and billing; 3G call and event data for the Circuit Switched (CS) domain TS 32.005 Sep 00 V3.2.0 R1999/32_series/32 Telecommunications Management; Charging and billing; 3G call and event data for the Packet Switched (PS) domain TS 32.015 Sep 00 V3.3.0 R1999/32_series/32 3G Telecom Management: Principles and high level requirements TS 32.101 Dec 00 V3.3.0 R1999/32_series/32 3G Telecom Management Architecture TS 32.102 Jul 00 V3.2.0 R1999/32_series/32 3G Performance Management TS 32.104 Dec 00 V3.4.0 R1999/32_series/32 TS 32.105 3G Charging and Billing; Stage 2 description Oct 00 V0.0.4 R1999/32_series/32 Telecommunications Management; Configuration Management; Concept and Requirements TS 32.106-1 Jul 00 V3.1.0 R1999/32_series/32 Telecommunications Management; Part 2: Notification Integration Reference Point: Information Service version 1 TS 32.106-2 Dec 00 V3.2.0 R1999/32_series/32 Telecommunications Management; Configuration Management; Part 3: Notification Integration Reference Point: CORBA solution set version 1:1 TS 32.106-3 Dec 00 V3.2.0 R1999/32_series/32 Telecommunications Management; Configuration Management; Part 4: Notification Integration Reference Point: CMIP solution set version 1:1 TS 32.106-4 Jul 00 V3.1.0 R1999/32_series/32

  40. References … Title Type Number Frozen Ver. Location Telecommunications Management; Configuration Management; Part 5: Basic Configuration Management IRP: Information Model version 1 TS 32.106-5 Dec 00 V3.0.0 R1999/32_series/32 Telecommunications Management; Configuration Management; Part 6: Basic Configuration Management IRP: CORBA Solution Set Version 1:1 TS 32.106-6 Dec 00 V3.0.0 R1999/32_series/32 Telecommunications Management; Configuration Management; Part 7: Basic Configuration Management IRP: CMIP Solution Set Version 1:1 TS 32.106-7 Dec 00 V3.0.0 R1999/32_series/32 Telecommunications Management; Configuration Management; Part 8: Name convention for Managed Objects TS 32.106-8 Jul 00 V3.1.0 R1999/32_series/32 Telecommunications Management; Fault Management; Part 1: 3G fault management requirements 32.111-1 Sep 00 V3.2.0 R1999/32_series/32 TS Telecommunications Management; Fault Management; Part 2: Alarm Integration Reference Point: Information Service Version 1 TS 32.111-2 Dec 00 V3.0.0 R1999/32_series/32 Telecommunications Management; Fault Management; Part 3: Alarm Integration Reference Point: CORBA solution set version 1 32.111-3 Dec 00 V3.3.0 R1999/32_series/32 TS Telecommunications Management; Fault Management; Part 4: Alarm Integration Reference Point: CMIP solution set Version 1 TS 32.111-4 Sep 00 V3.1.1 R1999/32_series/32

More Related