Mobile Network Management (IMT-2000 Management)ain.knu.ac.kr/professor/apnoms99-tut5.pdf · Mobile Network Management (IMT-2000 Management) Mobile Network Management (IMT-2000 Management)

1999. 9 Jong-Tae Park

Kyungpook National UniversityE-mail : [email protected]

Tel. : +82-53-950-5543Fax. : +82-53-950-5505

Mobile Network Management(IMT-2000 Management)

Mobile Network Management(IMT-2000 Management)

APNOM `99

1

APNOMS `99

Kyungpook National University AIN Lab.

OUTLINE

IMT-2000 Standardization

IMT-2000 Management Framework

IMT-2000 Network Management

IMT-2000 Service Management

Management System Architecture and Supporting Technologies

Implementation of IMT-2000 Management Service

2

APNOMS `99


IMT-2000 STANDARDIZATION

3

APNOMS `99


IMT-2000 OBJECTIVE

Global Service and Global Roaming Available in Year 2000s

Flexible and Seamless Service Provision Independent of Location

Wider Range of Services and Terminals

Support of High Speed Access

Support of Packet Mode Services (e.g., Internet)

Fixed/Mobile and Public/Private

Improved Operational Efficiencies

Evolution from 2nd Generation

4

APNOMS `99


IMT-2000 STANDARDIZATION GROUPS

ITU-T SG11 WG3(Signaling requirements for mobility service)

ITU-T SG2(Network and service operation)

ITU-T SG4(TMN and network maintenance)

ITU-T SG7(Data networks and

open system communication)

ITU-T SG13(General network aspect)

ITU-T SG15(Transport networks, systems]

and equipment)

ITU-T SG16(Multimedia service and systems)

T1 CommitteeT1P1/T1S1/T1M1

TTC/ARIB

ATM ForumITU-R SG8 TG8/1

(Mobile, radiodetermination,amateur andrelated satellite service)

SWP-1(IMT-2000 Architecture and Information Flows)

SWP-2(IMT-2000 Access Signaling Requirements)

SWP-3(IMT-2000 Network Signaling Requirements)

SWP-4(Signaling for UPT)

CDMAONE

TTA

ETSI SMG

3GPP1 3GPP2

TIA TR 45/46

5

APNOMS `99


IMT-2000 FUNCTION MODEL

UIM MT RAN CN

CN

Functional Model

FamilyMember

A

FamilyMember

B

FamilyMember

CIMT-2000Family

IMT-2000 Family

UIM= User Identity ModuleMT= Mobile TerminalRAN= Radio Access NetworkCN= Core Network

6

APNOMS `99


IMT-2000 SYSTEM ARCHITECTURE

Functional communications

UIM MT RAN CN

UIM-MT MT - RAN RAN - CN CN - CN

Core networks of otherIMT-2000 Family members

MT - CN

CN

UIM - CN (visited)

UIM - CN (home)

UIM MT RAN CN

UIM- MTInterface

RAN - CNInterface

NNI

IC ore ne tworks of othe r

MT-2000 F a m ily m e m be rs

MT - RANInterface

CN

Functional Model and Interfaces

7

APNOMS `99


IMT-2000 NETWORK REFERENCE MODEL

AC - Authentication CenterBS - Base StationDMSC - Drift MSCGLR - Gateway Location RegisterGMSC - Gateway MSCHLR - Home Location RegisterIP - Intelligent PeripheralMSC - Mobile Switching CenterMT - Mobile TerminalRNC - Radio Network ControllerPDSN - Packet Data Serving NodePDGN - Packet Data Gateway NodeSCP - Service Control PointSDP - Service Data PointTx - Transit ExchangeUIM - User Identification ModuleVLR - Visited Location RegisterPDSN

DMSC

MSC GMSC

VLR/GLR

AC

MT

UIM

R ACAF

CCAF

MRTR

MCF

UIMF

BS

RFTR

SIBF

LM F v

AMF v

AMF h

IP

SRF

SDP

SDF

SCP

SCF

SDF

SACF

UIM

MT

UIM-MT Interface

PS CAF

MT-RAN InterfaceRAN

ARF

ARF

PSCF

PDGN

PSGCF

LM F h

HLR

LM F h

CN

RAN -CN Interface

NNI

SDP SCP

MSC/GMSC SCP

PDSN HLR

PDGN HLR

CCF?SSFCCF?SSF

Tx MSC HLR SCP IP

Tx GMSC HLR IP SCP

RNC

RACFARF

RNCFGPF

RNC

RACFARF

RNCFGPF

MGPF

GPCF

GPCF

VLR/GLR SCP* MSC/GMSC PDSN/ PDGN

SDP SCP HLR* VLR/GLR* IP MSC/GMSC

HLR VLR/GLR SCP*

8

APNOMS `99


IMT-2000 PROTOCOLS

Interface Japan Europe U.S.AUIM-MT In process In process In process

MT-RANL1: Asynchronous W-CDMA implement

-> based on GSM

L1: W-CDMA orATDMA

L2,3: GSM CAI

L1: SynchronousW-CDMA

L2,3: IS-95 (L2)+GSM-like (L3)

RAN-CNITU-T standardizationorPDC MAP

GSM MAP IS-634

CN PDC MAP GSM MAP IS-41C

IN INAP CS2 CAMEL WIN(IS41 format)

CN-CNBased on GSMandITU-T standardization

Based on GSMand standardization

Global roamingVHE concept standardizationNew protocol

VHE : Virtual Home Environment (to support service portability between networks)

9

APNOMS `99


IMT-2000 PROTOCOL STRUCTURE

UIM

Home

MT RAN CN CN/PN

Service Application - Home

Service Application - Visited

ITU-T SG11

ITU-T SG11

L3Call ControlMobility ManagementService ControlBearer Control

ITU-T SG11

L3 - RRMITU-T SG11

Visited

L2 - LAC

ITU-T TG8/1

ITU-T TG8/1L2 MAC

L1

ITU-T SG11L3

ITU-T SG11L2

L3

L3ControlMobility ManagementService ControlBearer Control

ITU-T SG11

Data PacketsIP/ATM

Mobility Management

ITU-T SG7, SG16 or IETF

10

APNOMS `99


IMT-2000 PROTOCOL STACK - USER PLANE

AP

L2

L1

Voice Data Video

Internal interface

R-MAC(MUX)

PHY(W-CDMA)

R-LACd(only for data)

Control-plane

R-MAC

PHY(W-CDMA)

R-LACd

ATM

ATM-PHY

AAL-1/5

ATM

ATM-PHY

ATM

ATM-PHY

AAL-1/5

Internal interface

(Terminal Equipment)RAN

(Radio Access Network)CN

(Core Network)

RAN InterfaceRadio Interface

MT BSS MSC

ALL type(f.s):ALL-1(CBR:voice, video), ALL-5(VBR:signaling&data), AAL-2(VBR:voice, video):f.s under optics

Internal interface

AAL-1/5

11

APNOMS `99


IMT-2000 Dominated by Data Services

Data Communication Between Devices

Internet and Multimedia

High Quality Voice

Flexible Mixed/Multi-Service Provision Based on Compliance to

ITU IMT-2000 Recommendations

Global Roaming Service

IMT-2000 SERVICES

12

APNOMS `99


IMT-2000 MANAGEMENT

13

APNOMS `99


MAMAGING IMT-2000

Scope: – Address the roles, relationship and objectives of working teams

establishing standards and services for managing mobile / wireless networks to implement UMTS, and IMT-2000 3G wireless / mobile network

Outcomes:– TR45.7 (North America), TMN5 (Europe), TTC (Asia/Japan) and ITU-T

SG4 (IMT-2000) are collaborating effectively for Configuration, Performance, Fault Management, and Object Models.

– Service Management Challenges, QOS Management, and Service Portability are much different for Mobile Services.

14

APNOMS `99


IMT-2000 MANAGEMENT STANDARDIZATION

ITUITU--T SG 4T SG 4IMTIMT--2000 Management 2000 Management

StandardsStandards

ETSI TMN5 & SMG6ETSI TMN5 & SMG63GPP1 TSG3GPP1 TSG--SA/WG5SA/WG5

TTC/ARIB/TTATTC/ARIB/TTA

T1/TIA TRT1/TIA TR--45.745.73GPP2 TSG3GPP2 TSG--SS

TMForumTMForum Mobile TeamMobile Team

15

APNOMS `99


IMT-2000 NM STANDARDIZATION

ITU-T SG4 : IMT-2000 Network Management StandardizationTIA TR45.7 & T1M1.5 :

– Lucent Technology (USA) : IMT-2000 TMN Management Functional Requirements Contribution on Configuration : Service Provisioning.

– Motorola (USA) : IMT-2000 TMN Management Framework Contribution on Security: Audits-Counts of Fraudulent Use.

ETSI SMG5– UMTS 21.06, version 3.0.0 : Universal Mobile Telecommunications System (UMTS) ; Network

and Service Management Requirements for UMTS.– ETSI 201 385 v1.1.1 : Telecommunications Management Network (TMN); Universal Mobile

Telecommunications System (UMTS); Management architecture framework; Overview, processes and principles.

TTA/ARIB– Document Vol. 1 (Spec. No. 5) : Requirements and Objectives for a 3G Mobile Services and

System.3GPP1 (Third Generation Partnership Project) TSG-SA/WG5, 1998 Dec

– Developing the overall network management (NM) concept of the 3G system.– Specifying the NM high level framework.– Coordinating all other TSGs to have the actual detailed specification work of OA&M for the 3G

system based on GSM core network.– ARIB, ETSI, T1, TTA and TTC partnership.

3GPP2 (Third Generation Partnership Project) TSG-S (Systems and Services Aspects)– Definition of high level requirements for OAM&P across all 3GPP2 TSGs.– ANSI, TIA,TTA, TTC and ARIB partnership

16

APNOMS `99


TMForum MOBILE TEAM

• Promote Mobile and Wireless in the TMForum.

• Philosophy♦ Recognize special needs of Mobile / Wireless.

♦ Utilize and apply TMForum’s expertise ( e.g. TelOpsMap) to the Mobile Industry.♦ Contribute Mobile perspective to TMForum programs.

♦ Avoid overlap, and work in co-operation with other standards organizations.

• Maintain liaisons to ETSI TMN5 and TR45.

• Build a relationship to ITU-T SG4 and IMT-2000.

• Complete initial IMT-2000 Project.

• Mobile Team is in TMForum program #4 - Service Assurance.

17

APNOMS `99


IMT-2000 NETWORK OPERATION & MANAGEMENTRELATED ITU RECOMMENDATIONS

Study Group Recommandation Subject

ITU-R SG8 1079 speech and voiceband data Performance Requirements

ITU-R SG8 1168 Framework of IMT-2000 management

ITU-T SG2 - Numbering, Addressing and identifiacation for IMT-2000

ITU-T SG2 E.750Introduction to the E.750-series of Recommandation on Traffic engineering aspwcts of networks supporting mobile and UPT

Services

ITU-T SG2 E.751 Reference Connections for Traffic engineering on land mobile networks

ITU-T SG2 E.752 Reference Connections for Traffic engineering of maritime of aeronautical systems

ITU-T SG2 E.760 Terminal mobility Traffic modeling

ITU-T SG2 E.770 Land mobile and fixed network interconnection GOS concept

ITU-T SG2 E.771 Network GOS parameters and target values for circuit-sw itdhed public land mobile services

ITU-T SG2 E.773 Maritime and aeronautical mobile grade of service concept

ITU-T SG2 E.774 Network GOS parameters and target values for maritime and aeronautical mobile services

ITU-T SG2 E.780 Traffic engineering methods for land mobile systems

ITU-T SG4 M.3200 Prose description on IMT-2000 as a managed area

ITU-T SG4 M.32xx TMN Management Service for IMT-2000

ITU-T SG4 M.3400 TMN Management Function Sets(IMT-2000 related)

ITU-T SG4 M.31xx IMT-2000 Management Information

ITU-T SG7 X.115 Address Translation Service definition

ITU-T SG7 X.116 Address Translation Registration Protocal

ITU-T SG12 G.174 Transmission Performance Objectives for Terrestrial Digital Wireless Systems Using Portable Terminals to Access the PSTN

ITU-T SG13 I.37w Network Architecture and Capabilities got IMT-2000

ITU-T SG13 I.580 Interworking B-ISDN/64K

ITU-T SG13 I.581 Interworking Requirements B-ISDN

ITU-T SG13 I.35z Framework for Mobile Performance

ITU-T SG13 I.5xw Network Interworking between IMT-2000 and other types of Networks

ITU-T SG13 TBD Network related synchronization

ITU-T SG13 I.5xz UPT/Mobile Interaction

ITU-T SG13 I.140 Attribute technique for the characterisation of ISDN services and network capabilities(for IMT-2000)

ITU-T SG13 I.340 ISDN Connection Types(For IMT-2000)

18

APNOMS `99


IMT-2000 FAMILY MANAGEMENT INTERFACEX

OS OSA B

INTERFACE

CN NNI CNFAMILY FAMILY

NETWORK NETWORKSYSTEM A SIGNALING INTERFACE SYSTEM B

RAN A OTASP RAN BRTT RTT

INTERFACES

MT A MT A(ROAMING)

UIM A UIM A(ROAMING)

Three potential interfaces– The “X” interface between two OSs,– The NNI interface as signaling

information,– The air (OTASP) interface to either a

MT or to a UIM.This function set is defined as:

– This set supports requests that the specified service and/or features be activated, changed, or deactivated as a result of the negotiated customer solution.

X interface common generic forms:– Send <data> : manager role OS sends

<data> to agent role OS– Retrieve <data> : manager role OS

retrieves all or part of <data> from agent role OS

– Change <data> : manager role OS changes part of <data> stored in agent role OS

– Delete <data> : manager role OS requests agent role OS to delete <data>

OS = Operations System, CN = Core Network, NNI = Network-to-Network,RAN = Radio Access Network, RTT = Radio Transmission TechnologyMT = Mobile Terminal, OTASP = Over The Air Service Provisioning,UIM = User Identity Module

19

APNOMS `99


OS LAYERING

XRS RS

FUNCTION FUNCTIONSET INTERFACE SET

OS Q3 SML Q3 OSA B

INTERFACE NML INTERFACE

NSFA NSFAFUNCTION FUNCTION

SET SET

TO TOLOWER LOWER

TMN LAYERS TMN LAYERS

Legend:

RS = Request for Service (function set)SML = Service Management Layer

NML = Network Management Layer

NSFA = Network Service Feature Administration (function set)

The X interface communication be peer-to-peer within the TMN service management layer.The received provisioning data must proceed downward of the TMN layers to eventually effect the network elementsThe internal OS “Q3” interfaces will transport the dataA new function set, for the “Provisioning” function set group, is defined to transfer data over the “Q3”interface between the SML and the NMLNetwork Service Feature Administration : This set supports the transfer of service provisioning data between the SML and NML that arrives/goes over the “X”interface

20

APNOMS `99


IMT-2000 MANAGEMENT SERVICES (M.1168)

IMT-2000 specific network management servicesdescribed in the framework of IMT-2000 management

1) Radio resource related management service2) MS mobility related management service3) Charging and accounting management service4) User/user terminal equipment management service5) Security management service

Management services extendedfor IMT-2000 on the basis of fixednetwork management services

• Switching management• Security management• QoS/GOS management• IN management

etc.

Newly definedmanagementservices

• BS management• MS managementetc.

Management servicescommonly used in fixedand IMT-2000 network

• TMN management• TMN security

management• Staff work scheduling

management• Transport network

management• Commonly channel

signaling systemmanagement

etc.

IMT-2000 Management Services

21

APNOMS `99


RADIO RESOURCE RELATEDMANAGEMENT SERVICE

MSC managementFixed/transportable/mobile BS managementHome/roaming MS managementSatellite radio resource managementManagement of radio channel quality between MS and BSManagement of traffic load in each cellManagement of point to multi-point connections in radio common control channelInter-operator information exchange regarding radio resource related management

22

APNOMS `99


MS MOBILITY RELATED MANAGEMENT SERVICES

Handover performance management

Location/paging area management

Mobility pattern measurement

MSC management with regard to MS mobility

Fixed/transportable/mobile BS management with regard to MS mobility

Home/roaming MS management with regard to MS mobility

Inter-operator information exchange regarding MS mobility related management

23

APNOMS `99


CHARGING & ACCOUNTINGMANAGEMENT SERVICES

Charging for mobile public pay telephones

Charging based on diversified accounting parameters

Inter-administration accounting

Charging notification

Inter-operator information exchange regarding charging and

accounting management

24

APNOMS `99


USER & USER TERMINAL EQUIPMENT MANAGEMENT SERVICES

Management of user identity

Management of subscriber and its subscription

Management of user terminal equipment attached to mobile termination

Management of complaints from both home and roaming users

Inter-operator information exchange regarding user and user terminal equipment management

25

APNOMS `99


SECURITY MANAGEMENT SERVICES

Management of FPLMTS-specific security mechanism

Key management

Encryption management

Authentication management

Access control management

Service barring list management

Security audit management

Management of subscriber related credential information

Information exchange regarding security management

26

APNOMS `99


IMT-2000 NETWORK MANAGEMENT

27

APNOMS `99


REQUIREMENTS FOR NETWORK MANAGEMENT

Minimization of complexityManageability of heterogeneous equipmentProvision of communication via standardized interfacesMinimization of cost for managementSupporting Flexible configuration capabilityAllowing remote controlAllowing interoperability between Network Operator/Service providers for the exchange of management and charging informationScalability for management of increasing network resourcesRe-using of existing relevant standardsAssurance of system performance

28

APNOMS `99


TMN BASED IMT-2000 MANAGEMENT

WSF

EM-OSF

N-OSF

S-OSF

SCEF

NEF(MS)

CCAF

MCF MPCF

RACAF MRTR

NEF(BS/MSC)

SCF(M)

RACF SRF

ARF SIBF

SDF(M)

RFTR

MF

QAF

TMN

q3

q3

q3q3

q3

qXqX

X

mTo non-TMNNetworkElements

q3f

MF

INAP/SS7

CMIS/P, FTAM

AMF

LMF

29

APNOMS `99


IMT-2000 SERVICE MANAGEMENT

30

APNOMS `99


REQUIREMENTS FOR SERVICE MANAGEMENT

Minimizing operation costs of IMT-2000

Supporting introduction and removal of services

Control of access to IMT-2000 services

Allowing management of services over shared infrastructure

Allowing interoperability between Network Operator/Service providers for the exchange of management and charging information

Providing Quality of Service management

Standardization of service management should not prevent competition between manufacturers nor between operators

31

APNOMS `99


INTEROPERABILITY OF SERVICE MANAGEMENT

Interoperable with other networks as well as other IMT-2000 networks and service providers

Support co-operative management capabilities

Supporting function over interworking interface for interoperability– retrieval of supported management functions

– configuration of Service Level Agreements (SLA)

– request for supported management functions within a SLA

– transparency whether the request comes from a human operator or another management system

32

APNOMS `99


SERVICE MANAGEMENT LIFE CYCLE

Usage MonitoringStatistical information shall be gathered and maintained concerning the usage of services

Performance MonitoringStatistical information shall be gathered and maintained concerning system performance throughout the service life cycle

Status MonitoringUMTS services are expected to implemented through the inter-operation of sub-services from multiple operators. In order to present status information for subscriber-facing interaction, status information relating to these sub-services needs to be exchanged

ControlDelivery of a reliable user-configurable service depends on the exchange, across operator boundaries, of service control functions. Such functions would control and manage service invocation, service usage, deal with testability, resilience and load control mechanisms

CREATION

PROVISION

INVOCATION

DELETION/EVOLUTION

SERVICEMANAGEMENT

LIFE CYCLEService Management Functional Requirements

33

APNOMS `99


SERVICE PROVISIONING

Get customer onto Network– Customer profile: Service data

Billing/Charging Support– Common billing records across CNIs (since customer may roam)

Security– Audits: Counts of fraudulent use

Performance Management– Quality of service, Network performance monitoring– Network congestion control, Access blockage– IN congestion

Fault Management– Connectivity failures– Trouble tickets

34

APNOMS `99


SERVICE PROVISIONING FUNCTIONALITY

PROVISIONING

XADMINISTRATIVE

INTRAFAMILYSERVICE

PROVISIONING

INTRAFAMILYSERVICE

INTRAFAMILYSERVICE

PROVISIONINGDATA DATA DATAQ3 IN A

Q3 IN B

Service Provisioning Data Sets

“Q3A” and “Q3B”– Represent the service provisioning data pertaining to OS “A” and OS “B”.

“X ADMINISTRATIVE”– Represents that information which is needed to allow for communication over

the “X” interface

35

APNOMS `99


SERVICE PROVISIONING REQUIREMENTS

Customer data– To identify an end customer

Customer correlated data – That identifies the customer’s authorised mobile terminal

Static Data– Provisions the customer contracted services

Dynamic Data – Effecting multiple calls (not per call data) that permit customer/system

modification

Service classification– Defines the provisioning parameters for each service type– Contains proprietary, regional, and future service types

36

APNOMS `99


SERVICE PROVISIONING INFORMATION SPECIFICATIONS

Three major categories– Customer Subscription provisioning :

Information specifications for service provisioning

• Static Data• Dynamic Data

– Terminal Subscription provisioning : Common pointers are needed to correlate a customer to the subscribed terminals

• Static Data• Dynamic Data

– Terminal Services provisioning : Common pointers are needed to correlate Terminal services with a customer subscription and the subscribed terminals

• Universal Services• Other Services

Customer Profile

Customer Subscription

Static Data Dynamic Data

Terminal Subscription

Static Data Dynamic Data

Terminal Services

Universal Other

Static Data Static Data

Dynamic Data Dynamic Data

37

APNOMS `99


SERVICE PROVISIONING RESULTS

Initial work on the service provisioning aspect of the IMT-2000 management functional requirementsIdentification of key informational requirements needed to achieve service provisioningAn association between the key informational requirements and M.3400 functional sets were determinedMajor remaining effort:– Associate M.3400 functional sets with parameters– Determine new functional sets, if needed,– Associate the new functional sets with parameters– Determine parameters which apply to the “X” interface– Complete the parameter list for “universal” services and “other” services

38

APNOMS `99


CONSIDERATION FOR GLOBAL ROAMING

Consideration of defining the roles and responsibility of the X Interface for IMT-2000– Roaming between two different service providers within a single family member– Roaming between two different service providers between different family

members

Accounting Management– Exchange of accounting management information

Configuration Management– Management information exchange for the establishment and update of roaming

agreements– Management information exchange to facilitate subscriber roaming

Fault Management– Management information exchange to facilitate the rapid detection and correction

of subscriber roaming anomalies

39

APNOMS `99


MANAGEMENT OF SERVICE WITH MOBILITY

Airtime Service Provider

Network Operator

Platform-Provider

Media Service Provider

Bank

User

Content FlowCommercial Relation

Content Provider

40

APNOMS `99


MANAGEMENT SYSTEM ARCHITECTURE AND SUPPORTING

TECHNOLOGIES FOR UMTS

41

APNOMS `99


MANAGEMENT APPROACH FOR UMTS

New approach to standardise an O&M interface – Rapid specification of a standard framework which demonstrates the

conceptual principles– Different levels of abstraction to reduce complexity– Use of common and proven methods and tools to specify the standard for easy

implementation– Choosing an approach that gives the network element supplier the opportunity

for bespoke design but allows the operator open access to all data

The object oriented approach incorporated in CORBA is one of themost modern and powerful methods to describe and implement distributed systems.

42

APNOMS `99


THE FRAMEWORK UMTS MANAGEMENT (1/2)

Using the object oriented method (UML)– Pro :

• Object oriented modelling is a state of the art modelling technique

• UML is a frequently used syntax to describe object oriented models

• Tools available

• Compiler from UML into program skeletons for C++ or Java are part of software engineering environments

• UML has been submitted to the OMG for standardisation in January 1997

– Contra :• No implicit mechanism for notification handling by comparison with GDMO

• May be extra time required for UML specifications

43

APNOMS `99


THE FRAMEWORK UMTS MANAGEMENT (2/2)

Using CORBA for object distribution and communication • Standardised in OMG• Many implementations available• Wide utilisation in different domains• Many components specified or implemented• Service component for notifications under standardisation

Strict delineation between service components and applications– Pro :

• Open interface (API) for the Service Component “O&M Functionality” in a standardised environment

• No constraints on realising the management model except the use of UML and IDL• Open access to all data

– Contra :• Possible mediation between an operator specific view and the vendors object model

has to be initiated by the operator• The vendor has to follow constraints of the design pattern

44

APNOMS `99


PRINCIPLES OF THE REQUIRED ARCH. OF A NEW O&M INTERFACE FOR UMTS

Corba

Facility ComponentO&M Functionality(class library)

Application Component"Vendor specific GUI"(optional) TMN-System

inter-ORBCommunication

Corba

Operation and Control entity

The operator- has full access to all management information- probably has to map the OMC-model onto

it's own model

The vendor- must deliver an open API (class library)- has no restriction in the modelling of its

own system architecture

model description: UMLinterface description: IDL

UML: unified modelling languageIDL: inteface definition language

45

APNOMS `99


USE OF JAVA TO IMPLEMENT A DEDIATION DEVICE

In most cases the vendor specific model would not match the operator’s view of the NetworkThe operator has to model and implement such a mediation device as a facility component of the CORBA bus.Security requirements from the provider of the operation and control system.Each operation and control system is required to support a JVM and the necessary API’s

46

APNOMS `99


USE OF JAVA TO IMPLEMENT A DEDIATION DEVICE

CorbaFacility ComponentO&M Functionality

GUI(optional)

Operation and Control system

Java VirtualMachine

IDLUMLStubAPI's

TMN-System

operator dependentmodel

Java

Developmentenvironment

Java binariesof the

facility component

facilitycomponent

download

The operator gets the IDLCORBA Stub to access the service component “O&M Functionality”The operator knows his own internal model and requirement of the O&M-Functionality

UMTS management system can communicate with the facility component, after downloading the Operation and Control System, Proper definitions will need to be made relating to resource and performance requirements to ensure the facility component and core functions of the NE operate satisfactorily

47

APNOMS `99


USE OF JAVA TO REALISE A FLEXIBLE DISTRIBUTION OF MANAGEMENT CAPABILITY

All the management functionality must be distributed to the network elements themselves by using CORBAIf some of the management functions are more management applications it could be valuable to download them onto the UMTS management system

Core network

RNC Typ A

SiteCtrl

BTS

RNS Typ A/B RNCTyp B

SiteCtrl

BTS

RNS Typ B/C

logical connection : CORBA

Imageof thereal Network

, : Management Components,

IuIu

Iub Iub

SiteCtrl

BTS

Node BTyp A

Node BTyp B

Node BTyp C

The network element supplier will probably support the operator only with raw data excess components.This approach will allow the realisation of a “tool box”.

48

APNOMS `99


USE OF JAVA TO REALISE A FLEXIBLE DISTRIBUTION OF MANAGEMENT CAPABILITY

Core network

RNC Typ A

SiteCtrl

BTS

RNS Typ A/BRNC Typ B

SiteCtrl

BTS

RNS Typ B/C

logical connection CORBA over TCP/IP:

Imageof thereal Network

, : Management Components,

IuIu

Iub Iub

XML Browser

XML-DOC XML-DOC

XML-DOC

XML-DOC

XML-DOC

finds managementcomponents

SiteCtrl

BTS

XML-DOC

Node BTyp C

Node BTyp A

Node BTyp B

49

APNOMS `99


REQUIREMENTS ON THE Iu AND Iub INTERFACES FROM A MANAGEMENT PERSPECTIVE

SiteCtrl BTSRNCManager

Abs

tract

ion

Communicatingobjects

ORBlogi

cal s

truct

ure

system

transport

syst

em a

rchi

tect

ure CORBA 1

System ACORBA 2

System BCORBA 3

System C

method invocation

method invocation

IIOPTCPIP??

IIOPTCPIP??

IIOPTCPIP??

Iub interface

50

APNOMS `99


Iub FACILITY COMPONENTS

The O&M facility components must be defined to allow the architecture of the UTRAN to be determined.High level functional model for the facility components– Signalling Link Management, Timing and Synchronisation– Cell Configuration, Dedicated Resource Management– Common Channel Management, Radio System Management– Software Management, Node B Initialisation– Node B Hardware Configuration, Performance Monitoring– Site Maintenance, Security and Access Control– External Interface Management

When establishing a suitable architecture an appreciation should be given to the functions described above and their dependency and impact on each other.

51

APNOMS `99


REQUIREMENTS FOR UTRAN MANAGEMENT ARCHITECTURE

High level architectural requirements– The chosen management architecture must ensure the RNC performs an

integral role in O&M procedures– The architecture must support multiple vendor implementations which support

a multi-vendor Node B environment– The chosen architecture must provide a robust and distributed management

system– The hardware platform requirements of the management system must be

minimised

Many O&M processes will have a direct impact on the traffic handling ability of the Node B radio siteThe management architecture must also be capable of supporting multiple vendor implementations

52

APNOMS `99


REQUIREMENTS FOR UTRAN MANAGEMENT ARCHITECTURE

The third architectural requirement above indicates the need to maximise the integrity of the UTRAN O&M management system

RNC Vendor A

Node BO&M

TrafficHandling

RNC

O&M

Iu

Cell

Internal Node B O&M

Cell Cell Cell

Internal Node B O&M

Cell Cell

Vendor Specific O&M

Cell

Internal Node B O&M

Cell Cell

Node B Vendor A Node B Vendor B Node B Vendor C

Iub Iub Iub

TMN-System

Iur

53

APNOMS `99


IMPLEMENTATION OF IMT-2000 MANAGEMENT SERVICE

54

APNOMS `99


SOFTWARE FRAMEWORK

Java/CORBA Software BusProcess Flow

EnginePersistence Publish &Subscribe

ManagementProtocol

CORBAServices

Ordering Provisioning ILECInterface

ApplicationServer B

Web / BrowserJava HTML Perl CGI

IIOPRMI

Database NetworkElement

SNMPASCIISQL

...

Web-based M

gmt. Tech

CO

RB

A-based M

gmt. TechLegacy M

anagement Tech.

55

APNOMS `99


A HIGH-LEVEL VIEW OF TECHNOLOGY SELECTION

Item System Role Technology

1 Customer/Operational Staff access Web browser / JAVA

2 Business process interaction/ backbone distribution CORBA (+ Workflow?)

3 Business process controlof network resources

CMIP/GDMOSNMP/MIBs

4 Business process access tooperational data (not discussed)

SQL, SQL-Net, ODBC,Data Distribution?

56

APNOMS `99


WEB-BASED MANAGEMENT TECHNOLOGY

WBEM

JMAPI

Network Product Vendor

Laboratory

Web-based Network Management

JavaHTTP

ScriptCGI

HTMLXML

CORBA

Web Technologies

57

APNOMS `99


CORBA-BASED MANAGEMENT TECHNOLOGY

OMG CORBA Telcom

Developing Procedure

UMLModeling

Met

a-O

bjec

t Fac

ility

IDL Interface, Mapping, & ORB

CORBADomains

CORBA Services

CORBA Facilities

CORBADomains

CORBADomains S

ecurity

58

APNOMS `99


TECHNOLOGIES INTEGRATION

CORBA/IDL ↔ CMIP/GDMO– JIDM Specification Translation developed by the Joint Inter-Domain Management (JIDM) team

consisting of members from TM Forum and Open Group (previous X-Open representatives)CORBA Services ↔ CMIP Services

– JIDM Interaction TranslationCORBA Objects ↔ HTTP/HTML based Browser Services

– No defined specification as such, but some individual product implementations (e.g. via IIOP/HTTP tunneling)

Java Objects ↔ CORBA Objects– Use of Java as a Programming Language binding to CORBA

– Use of Internet Inter-Orb Protocol (IIOP) to provide object linkage between Java objects and CORBA objects

– Ability to download CORBA components written as Java applets into client environment using the principles of code

TMN Manager/Agent Programming Interface– TM Forum TMN C++ APIs– Developed for: Overall Architecture, GDMO ( Architecture, Class References, Specific Aspects – CMIS ASN.1 ( Base Classes and Specific Interface, Generic Interface )

59

APNOMS `99


CONCLUSION

IMT-2000 Standardization

IMT-2000 Network Management Using TMN

IMT-2000 Service Management

UMTS Management

Technologies and Integration for the Implementation of IMT-2000 Management Service

Documents

Mobile Network Management (IMT-2000 Management)ain.knu.ac.kr/professor/apnoms99-tut5.pdf · Mobile Network Management (IMT-2000 Management) Mobile Network Management (IMT-2000 Management)