chap14. gsm operations, administration, and maintenance 네트워크 컴퓨팅 연구실 서 돈 철...

Chap14. GSM Operations, Administration, and Maintenance

네트워크 컴퓨팅 연구실서 돈 철

2003. 4. 29

Kwangwoon Univ.http://netcom.kw.ac.kr

Wireless and Mobile Network Architectures

To manage the network GSM requires OA&M functions Follow the standard Telecommunication Management Network (TMN) con

cept

The TMN Component Operations System (OS)

With the operations system function (OSF), the OS is responsible for the overall TMN management

billing, accounting, management of mobile equipment, HLR measurement

Reside in an operation and maintenance center (OMC) Network Element (NE)

NEs in GSM are HLR, VLR, MSC, AuC, BSC, BTS, EIR monitored or controlled by the OS Network Element Functions (NEFs) represent the telecommunications a

nd support functions to be managed by the OS

Chap14. GSM Operations, Administration, and Maintenance



Data Communication Network (DCN) The OSs, NEs, and other TMN elements communicate through DCN by usin

g data communication function (DCF) The DCN technology can be WAN, LAN, or others The GSM OMC typically connects to MSCs and BSCs by X.25

Mediation Device (MD) The MD adapts the OS to the specific NEs Uses the mediation function (MF) to route or pass information between stand

ardized interface Q-Adapter (QA)

Use the Q-adaptor function (QAF) to connect the non-TMN entities Workstation (WS)

Interacts the operation/maintenance personnel with the OS through the workstation functions (WSFs)

With WSFs, staff access the status of the network and monitor the system parameters



TMN architecture

To anotherTMN

Workstation Functions(WSFs)

Workstations(WS)

Operations SystemFunctions (OSF)

Operations System(OS)

Mediation Functions(MFs)

Mediation Device(MD)

Q-Adaptor Functions(QAFs)

Q-Adaptor(QA)

Network Element Functions(NEFs)

Network Element(NE)

(f)

(x)

(q3)

(q3)

(qx)

(g)

Data Communications Function (DCF)Data Communications Function (DCF)

Data Communications Function (DCF)


To operating staff

To anotherTMN

Workstation Functions(WSFs)

Workstations(WS)

Operations SystemFunctions (OSF)

Operations System(OS)

Mediation Functions(MFs)

Mediation Device(MD)

Q-Adaptor Functions(QAFs)

Q-Adaptor(QA)

Network Element Functions(NEFs)

Network Element(NE)

Data CommunicationsNetwork(DCN)

(f)

(x)

(q3)

(q3)

(qx)

(g)


Data Communications Function (DCF)




14.2 TMN connection for the base station system

OSF

OS BSC BTS

MF

NEF

NEF(q3)

(qx)

The relationship between components of TMN functions are defined by using the reference points q3 : connects an OSF to an MF or an NEF qx : connects an MF to an NEF or a QAF x : connects an OSF to another OSF , OSF-like functionality in a different TMN f : connects an OSF to a WSF g : connects an WSF to the operating staff



Common Management Function for GSM

Three categories Forwarding of event notifications

Emit event notifications to the OS following Event Report Systems Management Function

The object class Event Forwarding Discriminator (EFD) in the NE manages forwarding of event notifications

Information logging Information generated by NE may be stored in a record filestore in the NE Information can be retrieved by NE or OS Allows the OS to control the logging of selective event notifications

Bulk data transfer between the OS and the NE Use Common Management Information Service Element (CMISE) control of F

ile Transfer Access and Management (FTAM) The data transfer is controlled by the OS



Figure 14.3 GSM-managed object class containment

Network

plmnNetwork

managedElement

aucFunction

mscFunction

wlrFunction

hlrFunction

bssFunction

Other Object Classes

CommonManagedObegects

Sms_G_JW_Function

elrFunction

callRecording Function(a)

(b)

(c)

(d) (i)

(h)

(g)

(f)

(e)



14.1 Call-Recording Functions

The billing of the mobile subscribers, statistics of service usage, and roaming traffic must be monitored by the OS

This information is provided by the NEs Managed by the tariff and charging administration Administration includes the following services

Service Provision : introduce new or modified services to the GSM Billing : determines the charge for the services Accounting

Inter-PLMN: ○ Required for roaming traffic management, which is settled by means of

the transfer account procedure (TAP)○ TAP records are regularly exchanged between GSM network○ For visitor from another GSM network

• The mobile-originated call charges are calculated and converted to an agreed accounting currency



Fixed-network : manage call traffic between MS and the fixed network

signaling traffic for functions such as location updates

Customer Administration : handles customer queries such as billing com

plaints



Tariff and charing administration

OSFService

Provision

OSFBilling

OSFAccounting

CustomerAdministration

TariffAdministra

-tion

DataCollection

TariffAdministra

-tion

OnlineTariff(AoC)

DataGeneration

Control

TariffData

Real-timeEvent

Collection

Call-RecordingFunction

RecordClass

Event-ForwardingDiscriminat

-or

DataTransferControl

Log

RecordFilestore

OSFTariff andCharging

Administration

Telecommunication Events

Log control

Event reporting

Internal event

Recordgeneration

controlEventreport

Logrecord

File transfer

Recordgeneration

control

Event report

a b c d

e f

g

h

i

j

l

n

k

m

o

AoC parameter (sent to MS)



14.1.1 Tariff Administration Tariff administration function provides the tariff administration information to the

NEs

The OSF uses the tariff class management functions to assign a tariff class with service, distance, and time-based tariff-dependent charging parameters

These dependencies are elaborated next: The service charging dependencies are defined based on the customized AoC The AoC (advice of charge) service definition may consist of one or more

Service types Radio channel types Connection type

The distance dependencies are defined based on the origins, destinations, and charging zone



14.1.2 Data Collection Data collection functions provide the specifications of the collected data to the NEs th

rough the data generation control in the NEF (record generation, event reporting, and log control)

The OSF data collection functions collect the data from these NEs through the data transfer control

Call-recording function generates potential call and event records based on the internal telecommunication events in the NE

The record generation control determines where the records are sent: The records may be forwarded to the record filestore The records may be saved in a log file The records may also be passed to the EFDs controlled by the event-reporting fu

nction



14.2Performance Measurement and Management

Performance of GSM network Evaluate based on the data provided by NEs

data : user/signaling traffic levels, quality of service

network configuration verification, resource access measurements

Measurement job is created, modified, displayed, suspended, resumed, deleted in the OS

○ is implemented as a simpleScanner object is scheduled in a period to accumulate measurement data for inspection instruct measurement function objects in the NEs to collect the data

hlrFunction

simpleScanner hlrMeasurementFuction

(measurement job)

HLR measurement object class containment



Fig 5. Measurement attribute modifications in location update

(a) Modifymeasurement attributeattLocationUpdate

(b) Modifymeasurement attributesuccLocationUpdate

Location updateoperation in HLR

HLR VLR

MAP_UPDATE_LOCATION

MAP_UPDATE_LOCATION_ack



simpleScanner object Measurement types

○ attLocationUpdate : number of the attempted location updates○ succlocationUpdate : number of the successful location updates

Measured network resources : The network resource is HLR Measurement function : The simpleScanner specifies one or more measurem

ent functions in the NEs to collect the desired data Measurement schedule :

○ specify start time & stop time of the active measurement period○ should be started within 90 days after measurement job is created

Granularity period :○ specify periodic interval of sending measured data from HLR to OS

Scan report○ is sent from NE to OS at the end of every granularity period○ include timestamp to indicate when it is sent to OS



14.3 Subscriber and Service Data Management

Subscriber and Service Data Management Define management for NEs … AuC, HLR, VLR, and EIR Managed data in different NEFs may depend on each other example :

To create a subscriber profile in the HLR, subscriber data should already exist in the AuC

If it does not, creation in the HLR fails MSISDNs and IMSIs are managed in HLR An MSISDN can associate with several basic service

Established between the msisdnHlr object and the basicServiceInHlr objects Some supplementary services are specified with parameters When a subscriber is deleted from the HLR, the corresponding subscribe

rInHlr object and all its contained objects are removed



subscriberInHlr msisdnHlr

hlrFunction

basicServiceInHlr basicServiceGroupInHlr

ssInHlrCFNRc ssInHlrBarring ssInHlrCW ssInHlrCUG

ssInHlrCFNRy ssInHlrCFU ssInHlrSimple ssInHlrClir

ssInHlrParmCFNRcssInHlrParmBarr

ingssInHlrParmSimple

ssInHlrParmCUG

ssInHlrParmCFNRy ssInHlrParmCFB ssInHlrParmCFU

ssInHlrCUGSubscription

ssInHlrCFB

Subsclasses of sslnHlrParameter

b a d c

e

f

g

Subsclasses of supplementary ServiceInHlr

HLR subscriber administration object class containment

chap14. gsm operations, administration, and maintenance 네트워크 컴퓨팅 연구실 서 돈 철...

Documents