gprs management functional specification mfs b9 ed06.pdf

GPRS management functional specification ED 6 RELEASED

Evolium 3bk09722jaaadszza-ed6rl.doc 2006/11/06 3BK 09722 JAAA DSZZA 1/3

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

Site Vlizy

EVOLIUMTM SAS

Originator(s)

D. Escalle

GPRS MANAGEMENT

FUNCTIONAL SPECIFICATION MFS RELEASE B9

System : ALCATEL 900/BSS Sub-system : MFS Document Category : FUNCTIONAL SPECIFICATION (Step 3) ABSTRACT This document presents the MFS management functions for the GPRS application. It is dedicated to B9 release.

Approvals

Name

App.

JJ. Bellego G. Dael A. Bocl

Name

App.

A. Margineanu F. Binard



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

REVIEW Ed 06 Proposal 01 2006/11/06 Review report MRD/TD/MFS/2006-5102 HISTORY Ed. 01 Proposal 01 04/03/15 Creation, from 3BK 09722 HAAA DSZZA Ed. 6 (B8) for

B9.

Ed. 01 Proposal 02 04/05/10 Add B9 dynamic Abis impacts on cell distribution, Visibility of GPRS problems and Alarm flow reduction impacts.

Ed. 01 Released 04/06/08 Update the distribution algorithm 5.6, the cardinality of object classes, and GPMGPU report messages

Ed. 02 Proposal 01 04/11/05 Take into account CRQ 3BKA13CBR151836 Update specifications related to Alarm flow reduction and Secure single Gb features

Ed 02 Released 05/01/11 - Apply remarks on proposal 01 - Introduce B9.1/B9.2 split - renumbering of 9

Ed 03 Proposal 01 05/04/15 Apply modifications decided for secure single Gb (note ref.: 2005-4430 ed.4) plus BvcId specific constraint

Ed. 03 Released 05/04/22 ! Last updates on secure single Gb, including CR 3BKA13CBR160794

! Take into account remarks ! Titles reorganization due to doc. problem: +4 on

H1 (not tracked) Ed 04 Proposal 01 2005/06/15 Evolutions for MxMFS

Apply 3BKA55CBR156033 Ed 04 Released 2005/07/08 Last modifications:

Synchro from MxBSC (3BKA20CBR157555) Ed 05 Proposal 01 2005/09/08 Last modifications:

3BKA13FBR169285: The error 'PVC disabled has to be tested to start secured single Gb (as 'Gb failure'). 3BKA13CBR166512: Dimensioning adjustements (mainly chapter 11.4) Few updates for protected_version (chapter 10.5) for MFS EVOLUTION

Ed. 05 Released 2005/09/08 Add a few editorial precisions Ed. 06 Proposal 01 2006/10/18 Apply 3BKA13CBR197126 plus some fixes in dimensioning Ed. 06 Released 2006/11/06 Apply updates related review report MRD/TD/MFS/2006-5102

Fix some few mistakes and lacking information regarding MX



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

INTERNAL REFERENCED DOCUMENTS Not applicable FOR INTERNAL USE ONLY Not applicable

END OF DOCUMENT



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

FUNCTIONAL SPECIFICATION

TABLE OF CONTENTS

1 REFERENCED DOCUMENTS........................................................................................9 2 RELATED DOCUMENTS ................................................................................................9 3 PREFACE ........................................................................................................................10 4 OPEN POINTS ................................................................................................................10 5 SCOPE..............................................................................................................................10 6 Glossary and definitions...................................................................................................12

6.1 Glossary ...............................................................................................................................12 6.2 Definitions............................................................................................................................13

6.2.1 CMPS requests, BUL files and profile file .................................................................................... 13 6.2.2 Operating modes of the control stations ........................................................................................ 13 6.2.3 Site parameters .............................................................................................................................. 14 6.2.4 Radio configuration from the OMC............................................................................................... 14

7 General principles ............................................................................................................15 7.1 Main evolutions of management in B9..............................................................................15

7.1.1 Telecom evolutions with O&M impact ......................................................................................... 15 7.1.2 O&M specific evolutions............................................................................................................... 15

7.2 Overview of the MFS O&M processes..............................................................................20 7.3 IMT and Q3 agent...............................................................................................................23

7.3.1 Management domains.................................................................................................................... 23 7.3.2 Simultaneous launching of IMT and OMC ................................................................................... 24

7.4 Security ................................................................................................................................24 7.4.1 IMT launching ............................................................................................................................... 24 7.4.2 CMISE requests access.................................................................................................................. 25 7.4.3 PM files access .............................................................................................................................. 25 7.4.4 Radio files access........................................................................................................................... 25 7.4.5 Mib backup files access................................................................................................................. 25 7.4.6 MFS users management................................................................................................................. 26

7.5 Strategy for MFS checks on CMIS operations.................................................................26 7.6 Defense .................................................................................................................................27

7.6.1 Control station switchover............................................................................................................. 27 7.6.2 GPU switchover............................................................................................................................. 28 7.6.3 OMC-MFS communication link loss............................................................................................. 28 7.6.4 SSW switchover [MX platform only]............................................................................................ 29 7.6.5 LIU failure [MX platform only] .................................................................................................... 29

8 Data management ............................................................................................................30 8.1 Profile files ...........................................................................................................................30 8.2 BUL file or CMPS requests................................................................................................30



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

8.3 GPRS data configuration sequence...................................................................................30 8.4 Data backup and restore ....................................................................................................32 8.5 System backup and restore [Not yet relevant for MX] ......................................................32 8.6 Unix patches update [Not yet relevant for MX]..................................................................33

9 Load and Performance.....................................................................................................34 9.1 Non-MX ...............................................................................................................................34 9.2 MX........................................................................................................................................35

10 BSC multi-GPU management .....................................................................................36 10.1 Introduction.........................................................................................................................36 10.2 BSS SubSytem and sub-BSS ..............................................................................................36 10.3 Cells distribution.................................................................................................................37

10.3.1 LXPU application criteria.............................................................................................................. 37 10.3.2 Cell unmapping-mapping .............................................................................................................. 37 10.3.3 Cell unmapping ............................................................................................................................. 38 10.3.4 Cell mapping ................................................................................................................................. 38 10.3.5 Cells mapping during Control station start .................................................................................... 38 10.3.6 Reshuffling action triggered at the OMC ...................................................................................... 39

10.4 Cells distribution criteria ...................................................................................................39 10.4.1 Definitions ..................................................................................................................................... 40 10.4.2 O&M parameter change ................................................................................................................ 42 10.4.3 Reshuffling considerations ............................................................................................................ 42

10.5 Migration considerations ...................................................................................................43 10.6 Distribution algorithms ......................................................................................................44

10.6.1 Events triggering a change in the cell mapping ............................................................................. 44 10.6.2 Cell distribution algorithm............................................................................................................. 45

10.7 Inter-LXPU communication ..............................................................................................49 10.8 Principle of update of the information necessary to the multi-GPU and LCS management......................................................................................................................................50 10.9 LA/RA Main LXPU handling............................................................................................50

10.9.1 Main LXPU role ............................................................................................................................ 50 10.9.2 Election trigger of Main LXPU LA/RA ........................................................................................ 50 10.9.3 Un-election trigger of Main LXPU LA/RA................................................................................... 50 10.9.4 Main LXPU BSS ........................................................................................................................... 51 10.9.5 Paging area main table broadcast................................................................................................... 51

10.10 Cells mapping......................................................................................................................51 10.11 BSS pilot LXPU handling...................................................................................................52

10.11.1 Pilot LXPU role ........................................................................................................................ 52 10.11.2 Election trigger of BSS pilot..................................................................................................... 52 10.11.3 Un-election trigger of BSS pilot ............................................................................................... 52 10.11.4 BSS pilot broadcast................................................................................................................... 52

10.12 BSS subSystem LXPU states..............................................................................................52 10.12.1 BSS subSystem LXPU states role............................................................................................. 52 10.12.2 Trigger of apparition of BSS subSystem LXPU state............................................................... 52 10.12.3 Trigger of suppression of BSS subSystem LXPU state ............................................................ 53



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

10.12.4 Trigger of BSS subSystem LXPU state = enabled.................................................................... 53 10.12.5 Trigger of BSS subSystem LXPU state = disabled................................................................... 53 10.12.6 BSS subSystem LXPU state broadcast ..................................................................................... 53

10.13 BSS Enable/Disable LCS....................................................................................................54 10.13.1 BSS subSystem Enable/Disable LCS role ................................................................................ 54 10.13.2 Trigger of BSS subSystem LXPU EN_LCS = Enabled............................................................ 54 10.13.3 BSS subSystem LXPU enable/disable LCS broadcast ............................................................. 54

10.14 BSS subSystem LXPU IP address .....................................................................................54 10.15 Defense principles ...............................................................................................................54

10.15.1 Migration .................................................................................................................................. 54 10.15.2 Control station switchover ........................................................................................................ 55 10.15.3 Competition between operations on ater and radio domains .................................................... 55 10.15.4 Cleaning Ater and radio resources for one LxPU in Multi-GPU(GSL loss)............................. 56 10.15.5 Securing a single Gb failure at BSS level ................................................................................. 58

11 Migration .....................................................................................................................65 11.1 Different types of migration...............................................................................................65 11.2 Global migration scenario..................................................................................................66 11.3 Minor migration..................................................................................................................68 11.4 Major migration..................................................................................................................69

11.4.1 Control platform migration............................................................................................................ 69 11.4.2 GPU migration............................................................................................................................... 69

11.5 GEM software change monitoring ....................................................................................70 11.5.1 GPU software change .................................................................................................................... 71

11.6 IMT software change monitoring......................................................................................71 11.7 Data migration management .............................................................................................73

11.7.1 Industrialisation ............................................................................................................................. 73 11.7.2 Data Conversion SCIM (B8 to B9)................................................................................................ 74

12 Configuration Detailed description.............................................................................75 12.1 Object models......................................................................................................................75

12.1.1 Q3Agent object model................................................................................................................... 75 12.1.2 GOM object model ........................................................................................................................ 76 12.1.3 GEM object model......................................................................................................................... 78

12.2 Q3/MRTA/GPU ..................................................................................................................84 12.2.1 Interfaces overview........................................................................................................................ 84 12.2.2 Class mapping ............................................................................................................................... 85

12.3 Precondition on lock and delete command.......................................................................86 12.4 Dimensionning.....................................................................................................................87

12.4.1 Database & GPU Capacity ............................................................................................................ 91 12.4.2 Load & Stress ................................................................................................................................ 92

12.5 Configuration download to GPU.......................................................................................92 12.5.1 Download constraints .................................................................................................................... 92 12.5.2 InGpu attribute management automaton........................................................................................ 95

13 Alarms management....................................................................................................97 13.1 Overview..............................................................................................................................97



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

13.2 Data change from B9 on.....................................................................................................98 13.3 Alarm flow reduction..........................................................................................................99 13.4 Visibility of GPRS problems..............................................................................................99

14 Detailed scenarios......................................................................................................100 14.1 MFS software components start ......................................................................................100

14.1.1 Normal start (Site/Site, Conf/Site, Rollback) .............................................................................. 100 14.1.2 Control switchover ...................................................................................................................... 101 14.1.3 SW change................................................................................................................................... 102

14.2 GPU management .............................................................................................................105 14.2.1 Loss of CS communication with GPU......................................................................................... 105 14.2.2 GPU plug/switchover .................................................................................................................. 107 14.2.3 GPU lock ..................................................................................................................................... 115 14.2.4 GPU unlock ................................................................................................................................. 116 14.2.5 GPU goes failed.......................................................................................................................... 116 14.2.6 GPU delete................................................................................................................................... 117

14.3 Administrative state management...................................................................................119 14.3.1 Object lock with field feed-back.................................................................................................. 119 14.3.2 Object lock with no field feed-back............................................................................................. 120 14.3.3 Object unlock............................................................................................................................... 121

14.4 PCM-TTP, CNX, Fabric configuration management ...................................................122 14.4.1 Detailed object model .................................................................................................................. 122 14.4.2 PCM-TTP and PCM-port identification ...................................................................................... 123 14.4.3 PCM-TTP, CNX configuration rules........................................................................................... 123 14.4.4 PCM-TTP patterns management ................................................................................................. 125 14.4.5 PCM-TTP CRC4 management .................................................................................................... 126 14.4.6 PCM-TTP synchronisation management..................................................................................... 126 14.4.7 Q3 PCM-TTP TSUsed attribute management ............................................................................. 128 14.4.8 PCM-TTP going equipped........................................................................................................... 128 14.4.9 PCM-TTP alarm filtering modification ....................................................................................... 129 14.4.10 PCM-TTP remoteEquipment modification............................................................................. 130 14.4.11 PCM-TTP multiplexingScheme modification ........................................................................ 133 14.4.12 Connect ................................................................................................................................... 133 14.4.13 Disconnect .............................................................................................................................. 134 14.4.14 CNX modification................................................................................................................... 135 14.4.15 Defence ................................................................................................................................... 135

14.5 Gb configuration management ........................................................................................136 14.5.1 Gb detailed model........................................................................................................................ 136 14.5.2 Gb configuration rules ................................................................................................................. 137 14.5.3 Frbearer create ............................................................................................................................. 138 14.5.4 FRBearer delete ........................................................................................................................... 139 14.5.5 NSE create ................................................................................................................................... 139 14.5.6 NSE delete ................................................................................................................................... 139 14.5.7 NSE set ........................................................................................................................................ 142 14.5.8 NS-VC create............................................................................................................................... 142 14.5.9 NS-VC delete............................................................................................................................... 144 14.5.10 NS-VC lock ............................................................................................................................ 145 14.5.11 NS-VC unlock ........................................................................................................................ 145 14.5.12 LXPU NS-VC Set Loss .......................................................................................................... 145 14.5.13 Defense ................................................................................................................................... 145

14.6 Atermux configuration management ..............................................................................146



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

14.6.1 AterMux detailed model .............................................................................................................. 146 14.6.2 AterMux configuration rules ....................................................................................................... 146 14.6.3 AterMux configuration possibilities ............................................................................................ 147 14.6.4 Global scenario ............................................................................................................................ 149 14.6.5 LapDLinks creation ..................................................................................................................... 153 14.6.6 LapDLinks deletion ..................................................................................................................... 154 14.6.7 LapDlink lock.............................................................................................................................. 156 14.6.8 LapDlink unlock.......................................................................................................................... 156 14.6.9 GICs configuration ...................................................................................................................... 156 14.6.10 GPU GSL Loss (state change) ................................................................................................ 158 14.6.11 Defense ................................................................................................................................... 159

14.7 Radio configuration management ...................................................................................160 14.7.1 Radio detailed model ................................................................................................................... 160 14.7.2 Radio configuration rules ............................................................................................................ 161 14.7.3 BSS pilot change ......................................................................................................................... 163 14.7.4 LA/RA main change.................................................................................................................... 163 14.7.5 BSS reset ..................................................................................................................................... 164 14.7.6 BSS create ................................................................................................................................... 164 14.7.7 BSS delete ................................................................................................................................... 166 14.7.8 BSS lock ...................................................................................................................................... 168 14.7.9 BSS unlock .................................................................................................................................. 169 14.7.10 BSS modification.................................................................................................................... 169 14.7.11 Cell create ............................................................................................................................... 170 14.7.12 Cell delete ............................................................................................................................... 172 14.7.13 Cell create in GPU .................................................................................................................. 172 14.7.14 Cell delete in GPU .................................................................................................................. 173 14.7.15 Cell modification .................................................................................................................... 174 14.7.16 Cell lock.................................................................................................................................. 175 14.7.17 Cell unlock.............................................................................................................................. 176 14.7.18 Massive changes ..................................................................................................................... 176 14.7.19 Cell remapping........................................................................................................................ 179 14.7.20 Defense ................................................................................................................................... 179

14.8 Fault management ............................................................................................................180 14.8.1 State management on MRTA objects .......................................................................................... 180 14.8.2 Computed Alarms........................................................................................................................ 186 14.8.3 Alarm flow reduction................................................................................................................... 187 14.8.4 Visibility of GPRS problems ....................................................................................................... 188 14.8.5 Defense........................................................................................................................................ 188

14.9 Performance Management...............................................................................................189 14.9.1 GPU counters measurement ........................................................................................................ 191 14.9.2 GPU configuration data ............................................................................................................... 191 14.9.3 PM reports file management........................................................................................................ 191 14.9.4 Time synchronization .................................................................................................................. 193 14.9.5 Suspected Interval Flag (SIF) and Suspected Flag (SF) management ......................................... 193 14.9.6 GPU connection........................................................................................................................... 195 14.9.7 CTL station switch-over .............................................................................................................. 196 14.9.8 Regulation of information flow between GPM GPU............................................................ 198 14.9.9 Needs for test (not usable for the client)...................................................................................... 198

14.10 Defense ...............................................................................................................................199 14.10.1 Control platform switchover ................................................................................................... 199 14.10.2 GPU errors .............................................................................................................................. 200 14.10.3 CTL errors .............................................................................................................................. 200 14.10.4 Gb link failure......................................................................................................................... 200



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

14.11 Concurrent requests management ..................................................................................210 14.12 Concurrency on MLU, Ater (reserveGprsResource), reshuffling................................210 14.13 Error processing on the interface....................................................................................211

14.13.1 Unknown O&M reference reception....................................................................................... 211 14.13.2 Unknown Message reception.................................................................................................. 211 14.13.3 No confirmation message received (by the Control Station) .................................................. 211 14.13.4 Message error processing strategy .......................................................................................... 211 14.13.5 Reactions on negative response message ........................................................................... 212 14.13.6 Reactions on negative confirmation message..................................................................... 213

14.14 Negative create result ..................................................................................................213 14.14.1 Negative create confirmation.................................................................................................. 213 14.14.2 Negative end of configuration ................................................................................................ 216

14.15 Negative set confirmation.................................................................................................217 14.15.1 GCHGroup SET cnf................................................................................................................ 217

14.16 Negative delete confirmation ...........................................................................................218 14.16.1 GCHGroup-DELETE-cnf ....................................................................................................... 218 14.16.2 Bss-DELETE-cnf.................................................................................................................... 218 14.16.3 PVC-DELETE-cnf.................................................................................................................. 218 14.16.4 FrBc-DELETE-cnf.................................................................................................................. 218

14.17 Negative lock confirmation ..............................................................................................219 14.18 Negative unlock confirmation..........................................................................................219 14.19 Others.................................................................................................................................219



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

TABLE OF FIGURES

Figure 1: MFS configurations vs software releases............................................................... 11 Figure 2: Document dependancies overview......................................................................... 11 Figure 3 : BSC multi-releases management in B9................................................................. 17 Figure 4: Summary of GPU capacity and protection ............................................................. 19 Figure 5 : XPU board boot procedure.................................................................................... 20 Figure 6: MFS O&M agents ................................................................................................... 22 Figure 7: GPRS data configuration sequence ....................................................................... 31 Figure 8 Q3 Agent object model ............................................................................................ 75 Figure 9 GOM object model................................................................................................... 76 Figure 10 GEM model used by GPRS management............................................................. 78 Figure 11 Administrative State management......................................................................... 81 Figure 12 GPU interface object model................................................................................... 83 Figure 13 Precondition on lock and delete objects ................................................................ 86 Figure 14 : GPU download conditional flowchart................................................................... 94 Figure 15 inGPU attribute management, asynchronous deletion .......................................... 95 Figure 16: Global O&M alarm process with GOM ................................................................ 97 Figure 17: GAM data tables and attributes relationships ....................................................... 97 Figure 18: REF_ALARM operation ................................................................................... 98 Figure 19 GEM-GOM-GPM normal start ............................................................................. 100 Figure 20 GEM-GOM start after a Control platform switchover........................................... 101 Figure 21 GEM-GOM start at major software change ......................................................... 104 Figure 22 BSC migration ..................................................................................................... 105 Figure 23 LXPU loss in a multi-GPU subSystem................................................................. 107 Figure 24 BAM init ............................................................................................................... 109 Figure 25 Bcm init................................................................................................................ 110 Figure 26 NS init .................................................................................................................. 111 Figure 27 Rrm Init BSS part 1/3.......................................................................................... 112 Figure 28 Rrm init - BSS part 2/3......................................................................................... 113 Figure 29 Rrm init - cells part 3/3......................................................................................... 114 Figure 30 : initialisation of the PM........................................................................................ 115 Figure 31 GPU lock ............................................................................................................. 116 Figure 32 GPU goes failed .................................................................................................. 117 Figure 33 LXPU removal in a multi-GPU BSS subSystem .................................................. 118 Figure 34 Lock with feed-back............................................................................................. 119 Figure 35 Lock with no feed-back........................................................................................ 120 Figure 36 Unlock.................................................................................................................. 121 Figure 37 PCM-TTP, Cnx, Fabric detailed objects .............................................................. 122 Figure 38 PCM-TTP going equipped................................................................................... 129 Figure 39: Modify the alarm filtering of an equipped PCM-TTP........................................... 130 Figure 40 PCM-TTP remote equipment set to unknown ..................................................... 132 Figure 41: set the remoteEquipment of a PCM-TTP from TC to SGSN .............................. 132 Figure 42 PCM-TTP connect ............................................................................................... 134 Figure 43 GOM detailed Gb model...................................................................................... 136 Figure 44 NSE deletion........................................................................................................ 141 Figure 45 NS-VC creation.................................................................................................... 144 Figure 46 GOM detailed AterMux model ............................................................................. 146 Figure 47 AterMux configuration possibilities ...................................................................... 148



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

Figure 48 AterMux configuration.......................................................................................... 149 Figure 49 LapDLinks creation.............................................................................................. 154 Figure 50 LapDLinks deletion .............................................................................................. 155 Figure 51 Last LapDLink deletion ........................................................................................ 156 Figure 52 GICs configuration............................................................................................... 158 Figure 53 GOM detailed Radio model ................................................................................. 160 Figure 54 BSS pilot change................................................................................................. 163 Figure 55 LA/RA main LXPU change .................................................................................. 163 Figure 56 BSS creation 1/3.................................................................................................. 164 Figure 57 BSS creation 2/3................................................................................................. 165 Figure 58 BSS creation 3/3.................................................................................................. 166 Figure 59 BSS deletion........................................................................................................ 167 Figure 60 BSS lock .............................................................................................................. 168 Figure 61 BSS NMO set ...................................................................................................... 169 Figure 62 Cell creation in control station ............................................................................. 171 Figure 63 Cell creation in GPU 1/2 ..................................................................................... 172 Figure 64 Cell creation in GPU 2/2 ...................................................................................... 173 Figure 65 Cell deletion in GPU ............................................................................................ 173 Figure 66 Cell modification .................................................................................................. 175 Figure 67 Radio massive changes ...................................................................................... 177 Figure 68: PCM-TTP operational state/availability status diagram...................................... 181 Figure 69: FRBearer operational state/availability status diagram ...................................... 181 Figure 70: PVC operational state/availability status diagram .............................................. 182 Figure 71: NS-VC operational state/availability status/administrative states diagram......... 183 Figure 72: sub-BSS operational state/availability status/administrative state transition

diagram........................................................................................................................ 184 Figure 73: Cell operational state/availability status/administrative state transition diagram 185 Figure 74: LapD operational state/availability status/administrative state transition diagram

...................................................................................................................................... 186 Figure 75 Init. states re-synchronisation.............................................................................. 199 Figure 76 : Board initialisation error..................................................................................... 212



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

1 REFERENCED DOCUMENTS [1] GPRS/LCS Functional O&M Architecture

3BK 11203 0331 DSZZA [2] OMC/MFS : Ater & Gb domains

3BK 11204 0339 DSZZA [3] OMC/MFS : Radio domain

3BK 11204 0338 DSZZA [4] OMC/MFS : SW domain and backup/restore management

3BK 11204 0340 DSZZA [5] OMC/MFS : Migration to B9

3BK11204 0315 DSZZA [6] OMC/MFS : HW domain

3BK 11204 0337 DSZZA [7] MFS/OMC interface specification : GDMO Part 1 specific object identifiers

3BK 11204 0323 DSZZA [8] MFS/OMC interface specification : GDMO Part 2 implementation profile

3BK 11204 0324 DSZZA [9] MFS/OMC radio file interface specification

3BK 09647 FCAD PBZZA [10] MFS O&M Architecture

3BK 09665 HAAA EBZZA [11] MFS SFD: MFS O&M and capacity improvement

3BK 10204 0566 DTZZA [12] MFS-BSC interface BSCGP layer

3BK 11202 0371 DSZZA [13] LCS management functional specification

3BK 29225 HAAA DSZZA [14] MFS Initialisation of Telecom Part

3BK 11202 0355 DSZZA [15] SFD: Better Integration of MFS IMT at OMC-R

3BK 10204 0647 DTZZA [16] SFD: MFS Security

3BK 10204 0650 DTZZA [17] SFD: MFS O&M Supervision

3BK 10204 0645 DTZZA [30] SFD: MFS Secured Single Gb

3BK 10204 0648 DTZZA [31] SFD: MFS Alarm Flow Reduction

3BK 10204 0649 DTZZA

2 RELATED DOCUMENTS [18] GPRS NE-Platform Equipment & Alarms functional specification

3BK 09584 JAAA DSZZA [19] MFS interfaces data catalogue

3BK 09721 HAAA PQZZA [20] MFS/OMC PM file interface specification

3BK 11204 0293 DSZZA [21] Multi-GPU per BSS

3BK 10204 0517 DTZZA



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

[22] Defence scenarios for multi-GPU and BSS reset management 3BK 14393 0017 EBZZA

[23] MFS alarm dictionary 3BK 10204 0560 DTZZA

[24] MFS O&M MFS Telecom Interface Specification 3BK 09638 HAAA PBZZA

[25] MFS INSTALLATION, CONFIGURATION AND SOFTWARE CHANGE GUIDE 3BK 09679 JAAA RJZZA

[26] Backup restore management global specification 00587 CDAA DSZZA

[27] Backup restore reference manual 3CM 00496 CDAA UTZZA

[28] GOM SW Component description 3BK 09622 JAAA PEZZA

[29] Security and Supervision Functional Specification 3BK 29376 JAAA DSZZA

3 PREFACE This document describes the management of the GPRS application in the MFS NE. It is dedicated to B9 release; It covers both B9.1 and B9.2 steps.

We assume that in the following, unless specifically mentioned: BSC applies either to a BSC G2 or an MxBSC, MFS applies either to a non-MX or an MxMFS.

4 OPEN POINTS Impact of B9.1/B9.2 functional split.

5 SCOPE The detailed object models and scenarios focus on services related to the management of the GPRS telecom resources that belong to Radio, AterMux/Ater and Gb domains.

The services related to HW data, SW data and generic services for alarms management belong to MFS platform. They are also used by other applications (e. g. SGSN). They are described in document [10].

This document is dedicated to:

! O&M team, to validate consistency with OMC-R behavior

! MFS developers and test teams

A pre-requisite to the understanding of this document is to have a general knowledge of TOMAS GP3 basic mechanisms and of MFS architecture components.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

B9MFS configurations \ Releases

AS800 / Tru64 4.0f / RC23

DS10 / Tru64 4.0f / RC23

DS10 / Tru64 5.1 / RC40

MX / Linux CG3.0 / RL42

YES

B6 B7 B8

YESYES

YES YES

YES

YES

YES YES

YES

YES YES

YES

NO

NO NO Figure 1: MFS configurations vs software releases

MFS O&M Architecture(2 versions non-MX and MX)

GPRS ManagementFunctionnal Specification

GPRS NE-Platform Equipment& Alarms functional specification

(2 versions non-MX and MX)

Messages Interface +Data Catalogdocuments

Software Descriptiondocuments:

(GOM, GLM, GPM, GAM)

Software Description document:(GEM)

Figure 2: Document dependancies overview



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

6 GLOSSARY AND DEFINITIONS

6.1 Glossary BAM Board & Alarm Manager (GPU task) CMIS Common Management Interface Service CMPS Common Management Protocol Syntax CS Communication Service DM Data Manager DSI Data Set Instance EFD Event Forwarding Discriminator EGPRS Enhanced GPRS FR Frame Relay GAM Global Alarm Manager GEM Global Equipment Manager GHW Global HardWare manager (for TOMAS objects) GOM GPRS O&M GPM GPRS Performance Manager GPRS Global Packet Radio Service GPU GPRS Processing Unit GSL GPRS Signalling Link (Warning: in all documents MFS the GSL names the set

of LapDlink for a GPU/BSS, out of context MFS it is called GSL set and LapDlink is called GSL)

HMI Human Machine Interface HSDS High Speed Data Service IMT Installation and Maintenance Terminal (also called craft terminal) LA Location Area LXPU Logical XPU MFS Multi BSS Fast Packet Server MIB Managed Information Base MO Managed Object MRTA MFS Real Time Agent (GOM, GEM, GAM, GPM) MX Prefix used in the document to designate Evolution type of MFS and BSC NSE Network Service Entity NSS Network and Switching System NS-VC Network Service Virtual Connection O&M Operation and Maintenance OMC Operation and Maintenance Centre PA Paging Area PM Performance Management PVC Permanent Virtual Connection QoS Quality of Service RA Routing Area SCIM Software Component Instance Materialisation SGSN Serving GPRS Support Node SW SoftWare



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

6.2 Definitions

6.2.1 CMPS requests, BUL files and profile file

CMPS requests are CMIS like requests that are exchanged between several MFS components (Q3 agent with GOM/GEM/GAM or IMT with GOM/GEM/GAM).

A BUL file encapsulates several BUL requests. A BUL request is an ASCII command that can be translated by IMT into a CMPS request.

A BUL file is then a simple way to send configuration or get requests to the MFS GOM/GEM/GAM components. For further information, see [9].

A profile file is a particular BUL file (see 8.1), mainly used to pre-configure the MFS MIB.

6.2.2 Operating modes of the control stations

The MFS is a system based on TOMAS framework.

It contains two different MIBs:

! TOMAS MIB

! MFS MIB

Depending on the mode, the MIBs are erased or kept:

Configuration modes: The MFS application is started but it is not operational. In particular, there is no connection with the OMC nor with the GPUs: telecom functions are not operational.

These modes are used during development, in integration, by operation teams during installation and at factory premises exclusively.

In these modes, the active/standby station switch over is inhibited. Configuration operations are performed on the active station.

There are two different configuration modes:

! TOMAS configuration mode:

All previously stored data (TOMAS and MFS MIBs) are erased.

This mode is used during development exclusively.

! Factory mode:

Previously TOMAS stored data (TOMAS MIB) are kept. MFS data (MFS MIB) are erased.

This mode is used by operation teams, during installation and at factory premises exclusively.

These operations can merely be performed from the IMT.

Note: This mode is no more available on MX MFS



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

! Site mode:

The MFS application is started and launched. After initialisation phase, it becomes operational.

Active/standby mechanism is started, both control stations get synchronised.

Its configuration may be modified through CMPS requests issued by the Q3 agent or by the IMT that processes BUL file.

Switch over between modes (TOMAS configuration mode, MFS configuration mode and Site mode), requires an MFS system re-initialisation (re-boot of control stations and GPU boards). (As mentioned in the mode description, this switch over can be only triggered by Alcatel teams (in development, in integration, by operation teams during installation and at factory premises), and never by the customer, using the IMT).

6.2.3 Site parameters

Site parameters are parameters that are always present. They represent environment parameters such as timers that are mandatory for the MFS system.

The objects storing the site parameters cannot be created nor deleted in site mode.

Their modification in site mode requires the reset data of all GPU boards to take the new values into account.

They cannot be accessed by the OMC.

An IMT view offers the possibility to display and modify them, resetting automatically of the GPU boards (when GPU boards are present) afterwards.

6.2.4 Radio configuration from the OMC

In this document, the Radio configuration from the OMC is often named MLU (Massive Logical Update).



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

7 GENERAL PRINCIPLES

7.1 Main evolutions of management in B9

7.1.1 Telecom evolutions with O&M impact

7.1.1.1 Enhanced Transmission Resources Management

This is split into three sub-functions:

! Dynamic Abis ! Statistical multiplexing ! Improvement of Ater resources management

The major impact on the O&M is the modification of the reshuffling algorithm due to dynamic Abis implementation (see 10.3: Cells distribution).

7.1.1.2 Other telecom evolutions (with GPRS impact)

! Dual Transfer Mode ! Support of QoS in Packet Switched Domain ! Enhanced Packet Cell Reselection ! Extended UL TBF Mode ! Autonomous Packet Resource Allocation ! Enhanced Support of EGPRS in Uplink

7.1.2 O&M specific evolutions

7.1.2.1 Better Integration of the IMT

The goal of this function is to improve the IMT integration at OMC level by implementing the following items:

Centralized User Management User account control is centralized at OMC-R security services level: no more specific login procedure will be necessary to access the IMT.

Parallel Access Actions at GPU level will be allowed in parallel by different users, each of them operating on a different GPU.

IMT Fast Start The IMT will no more be downloaded from the MFS at opening time if there is no version change compared to the last time.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

More Navigation possibilities Ergonomy improvement at OMC-R level.

Printable IMT views idem.

For more informations, see ref.:[15]

7.1.2.2 Secured single Gb

The goal of the feature is to provide a spare Gb link to the cells of a GPU for which the Gb link is failed. This feature is provided at BSS level.

The purpose is to reroute automatically the Gb traffic of every cell of the Gb failed GPU to the Gb link of one or several other GPU(s), through re-mapping of the BVC-PTPs of the impacted cell on the other GPU

Assigning a target GPU (for each cell) and globally managing the mapping are performed at O&M level.

See document [30].

Note: This feature is the only one for B9.2 or later. Anyway, an O&M implementation prior to B9.2 is compatible with PMU software, due to the Cell create interface that will be delivered since B9.1 and a feature enabling attribute at O&M level that can be read as always disabled prior to feature delivery.

7.1.2.3 Alarm flow reduction

This is limited to the filtering of alarms (at the OMC site) related to BSS and LAPDLINK class objects when they are locked.

If alarms were already present before the object was locked, the alarm is raised again at the OMC site, when it is unlocked.

Any locking of a BSS object implies the filtering of alarms related to the attached LAPDLINK objects.

See document [31].

7.1.2.4 MFS security and supervision enhancement

This will have different implementations depending on the type of platform, as it is operating system dependant (in particular the shadow passwords feature):

7.1.2.4.1 Non-MX

Compaq delivers a set of patch (BL 22) to improve the MFS security. Some other Security and supervision functions will be made available from B9 release on: this is detailed in the documents ref.: [16], [17], and [29] The mechanism developed in B8 for BL18 patch installation will be reused in B9 for BL22 as well as some other security and supervision items.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

7.1.2.4.2 MX

To be defined.

7.1.2.5 Migration B8 => B9

The MFS will be put in B9 release before the BSCs it is connected to.

So the B9 MFS must be BSC multi-release, at least able to work with a BSC using a B8 BSCGP, or a B9 BSCGP

A GPU will be mono-release : B8 when connected to a BSC using a B8 BSCGP, B9 when connected to a BSC using a B9 BSCGP.

The B9 multiGPU cell distribution constraints are different from B8: the cells need to be remapped on the GPU serving a multiGPU BSC as soon as the BSC version changes from B8 to B9.

This is depicted in Figure 3.

Figure 3 : BSC multi-releases management in B9

Just after MFS software migration to B9, all GPUs remain in B8 (no BSC are migrated yet, see [5]).

When a B8 BSC migrates to B9, every concerned GPU warns the control station that resets all these GPU to upgrade them in B9 (see chapter 11).

Note: Only the major migration B8 => B9 and the minor migration (also called software Replacement) B9 => B9 are supported.

MFSActive Control

Station

GPU B8 GPU B9GPU B9 GPU B9

BSC B8 BSC B9

GPU B8



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

7.1.2.6 New site installation

No B8 software pre-exist on the TOMAS platform, moreover, we assume that there is no BSC in B8 release in this context. Consequently, the B9 software package does not contain the B8 GPU software.

When a MFS comes from the factory, it has a version by default, this version is zapped by a first installation in B9 from scratch. This operation can be made locally or remotely during the configuration phase by the IMT.

7.1.2.7 Up to 32 GPU in A935 MFS In B7, the MFS capacity has been limited to 22 active GPUs (24 including redundancy) With the GPRS traffic increase and after introduction of the Multi-GPU feature in B7, it was decided to use all the remaining free GPU slots. So from B8 on, The A935 MFS non-MX can manage up to 32 GPU: 30 active GPUs + 2 spare ones. However, the number of BSCs per MFS remains limited to 22 BSCs. In fact, the maximum number of GPUs and BSSs will depend on the MFS hardware configurations: Configurations which are both Non-MX and non-AS800, will accept 30 active GPUs and 22 BSSs (For example: MFS equipped with DS10 control stations) AS800 control platform configurations will be limited to 22 active GPUs and 22 BSSs (for O&M processing capacity reasons, the O&M dimensioning remains 30 GPUs) The MX type MFS is using a completely different hardware (both telecom and O&M) limiting the number of active GPs to 21 (+ one spare) and thus, the maximum number of BSSs is 21. (Although GP boards processing capacity is dramatically increased compared to GPU boards, they will play one for one the same part as the GPU boards in a non-MX MFS, for the B9 release) The objects cardinality (GDMO, MDL, and CML) has been kept to limit the size of the spdata directory (GOM MIB). The number of radio objects supported by the MFS is limited by GOM. At object creation, if a request is sent to GOM with a number of objects to create out of range, a NACK message is sent back to the Q3 agent.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

MFS configurations \ GPU Capacity

AS800 / Tru64 4.0f / RC23

DS10 / Tru64 4.0f / RC23

DS10 / Tru64 5.1 / RC40

MXMFS / Linux CG3.0 / RL42

22

GPU Spare

2

30 2

230

21 1

protection

2*(1 for 11)

2*(1 for 15)

2*(1 for 15)

1 for 21

MX rack shared / Linux CG3.0 / RL42 9 1 1 for 9

Figure 4: Summary of GPU capacity and protection

7.1.2.8 JBGPU variant AB obsolescence [Not relevant for MX] The GPU variant AC project was triggered by the obsolescence of some components in the current JBGPU and JBETI boards, of AB variant. This has led to the introduction of a new GPU board (JBGPU variant AC): ! No functional impact at all on the GPU operational behavior is implied with the

introduction of this new hardware. ! A MFS can run with a mix of GPU variant AB and AC with no limitation or impact on the

O&M nor the telecom part . The only modification brought at the MFS side is the introduction of a new GPU software file for the GPU variant AC in the /tftpboot directory. Here is the GPU download default procedure: 1. The GPU downloads LOADER via default tftp setting. 2. The LOADER sends a BNP_request to GEM. 3. The GEM MRTA finds the boot file name for the GPU according to the NEP_Profile

configuration, sends it to the LOADER as BNP_response, including either: ! BootFilename: /tftpboot/jbgpu_b8.hex, for B8 GPU software or ! BootFilename: /tftpboot/jbgpu_b9.hex, for B9 GPU software.

4. The LOADER sets up a tftp session with the control station, downloads the requested file via TFTP.

5. The GPU software starts BAM, SCA Change in the above procedure for AC variant: All the firmware in the new board will add a suffix to original file name given by GEM in order to download the dedicated software file. When a GPU variant AC board is inserted, the firmware will download and start a dedicated Loader (Loader_AC), then the new loader will also add a suffix _AC to the file name, and download either: ! jbgpu_b8_AC.hex (B8 version), or ! jbgpu_b9_AC.hex (B9 version) from the control station.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

For the same reasons, a new JBETI has been introduced (the JBETI variant AB), a suffix _AB will be added to original file name to download the right software file. The figure below details the XPU board boot procedure.

Bootp client bootpd server tftpd GEMAgent Boot Request (Eth addr)

Boot Reply(IP addr)

UDP File Request

UDP File Response

Loader software download

Firmw

areLoader

GPU

SW

UDP File Request

UDP File Response

TFTP XPU software download

Session with O&M Agent

Loader of GPU3board add thesuffix _AC toget the right file

Figure 5 : XPU board boot procedure

7.1.2.9 MFS evolution (MX) case

The information of the previous paragraph above change in the above procedure for AC variant is also relevant for the MFS evolution, except the concept of GP variant.

7.2 Overview of the MFS O&M processes Here is an overview of the processes present in the control stations and LXPU boards of the MFS that are involved in O&M management.

For more details, please refer to [9].



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

These processes are:

! An agent developed by the TOMAS team:

! GHM: TOMAS equipment manager.

It manages the equipment subset dedicated to the O&M part of the MFS (control stations and dedicated hardware environment). These equipments are completely different between MX and non-MX MFS; so there is an MX and a non-MX dedicated GHM

! Agents developed by MFS team :

# MFS SCIMs (MFS processes present on the control stations):

GEM: equipment manager.

It mainly manages the physical boards that are dedicated to telecom operation and alarms, these equipments are completely different between MX and non-MX MFS; so there will be a MX and a non-MX dedicated GEM. However the GEM/MX information model will differ as little as possible from the non-MX dedicated one. In particular the interface with GOM will remain the same.

(It offers to GOM a logical view of the GPU boards (LXPU). Its GPU correspondents are SCA, BAM)

GOM: O&M radio manager of the system. It manages GPRS telecom applications of the logical GPUs (LXPU). Its GPU correspondents are BCM, NS, RRM, all accessed via the TRM gateway. The GPRS management will not change between MX and non MX MFS.

GAM: alarm manager. It manages all the alarms related to the MFS part of the system. Its GPU correspondent is BAM. Although new alarms exist on MX MFS, due to new type of equipment, GAM is generic enough to be quite identical between MX and non MX MFS.

GPM: PM manager. Its GPU correspondent is TPM. MX: same remark as for GOM.

GLM: LCS manager. It manages LCS telecom applications of the logical GPUs (LXPU). Its GPU correspondents is SMLC, all accessed via the LRM gateway. MX: same remark as for GOM. GLM exploits the GOM MiB (It does not own any administrative object)

GPU PSOS tasks (processes running on GPU boards under PSOS operating system): e.g. BAM (Board and Alarm Manager)

Note: Throughout the rest of the document, GPU processes are not described in detail. Their names are just mentioned on the diagram for information purpose

.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

! An agent developed by TOMAS and respectively MFS teams

The Q3 agent, for LA-PF and respectively LA-MFS parts.

CONTROL STATION

CMPS INTERFACE

DM CFG MIB

SCA

XPU BOARD

GOM GEM GAM

PM

AGENT

GPM

Admin.

Real Time Real Time Real Time

Admin.

Real Time

Admin.

DM RSC MIB

MFS SCIM

PSOS TASK

CFG MIB : SEMI-PERMANENT CONFIGURATION DATA

RSC MIB : DYNAMIC RESOURCE DATA (STATES)

GHM

NECTAR SCIM

Admin

Real Time

BOARD AND

ALARM MANAGER

CS SESSION

Bearer RRM NS

TRM

CRAFT TERMINAL

OMC

LA-PF

COMET

LA-MFS

Q3 Agent

SMLC

LRM

GLM

Real Time

DM directly sends the datas to GLM(each writings triggers a message)

Figure 6: MFS O&M agents



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

7.3 IMT and Q3 agent

7.3.1 Management domains

At architectural level, both the Q3 agent and the IMT have a role of clients and share the same CMPS interface towards GEM, GOM and GAM MRTAs. (Through its HMI, IMT processes BUL files and translates them into CMPS requests).

On site, the IMT and the Q3 agent have as well separate responsibilities.

The Q3 agent operates on the following domains using Q3 information model:

! Radio (aGprsBssFunction , btsSiteManager, aGprsBts, aGprsPowerControl, aGprsAdjacentCellReselection, aGprsMasterChannel)

! Ater/Gb (fabric, crossConnection, aGprs2MbTTP, aGprsLapdLink, aGprsGicGroup, aGprsBearerChannel, aGprsPvc, aGprsNse, aGprsNsvc)

! Infra (LA-PF manages: extendedCurrentAlarmSummaryControl, eventForwardingDiscriminator, managedElement, alarmSeverityAssignmentProfile instance relative to TOMAS managed objects. LA-MFS manages aGprsManagedElementExtension and alarmSeverityAssignmentProfile instance relative to MFS managed objects. At initialisation-time, extendedCurrentAlarmSummaryControl instance is updated by LA-MFS)

! HW ( equipmentHolder, circuitPack, nectarCircuitPack : only M-GET is allowed) The IMT operates on the following domains, through dedicated views:

! O&M hardware (control stations/OMCP boards, etc...)

! Telecom hardware (reset GPU boards, GPU forced switch over/switch back, etc)

! Software

! Infra : the CONF_ALARM table, which enables to customize MFS alarms severity, can be modified, using BUL files. (TOMAS alarms severity configuration can not be modified)

Other domains such as Radio/Trans/Ater/Gb can be updated through BUL operations processing (elementary operations or BUL files). There is no HMI provided for those domains. This is reserved for MFS testing purposes.

Through BUL operation, only very basic tests can be performed, that do not require the chaining of several large BUL files sequenced followed by MRTA responses. Such a method is very simple and it does not allow to reproduce the complex behaviour at MRTA CMPS interface induced by OMC/Q3 agent exchanges (this is for pre-integration purposes).

Alarms and state changes are sent by MRTAs to both Q3 agent and IMT through the use of TOMAS getwhen event report service (there may be several IMT instances).

The IMT is in charge of modifying site parameters and to reset all the GPUs to apply these modifications (see 6.2.3).



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

7.3.2 Simultaneous launching of IMT and OMC

The IMT may be remotely launched on the OMC. In that case, alarm management must be disabled because it is already offered on the OMC, using AS Generic component.

There is no access conflict, as IMT and OMC work on separate domains.

In case (to be avoided) of concurrent accesses from several IMT, the last wins and the previous is notified of the change.

It is possible to connect to the maximum 2 IMT.

7.4 Security The access to the MFS from the OMC or from the IMT is controlled in the following ways:

! Iconbox and IMT services on the OMC-R: the access to any service is controlled both at functional and geographical level on a per SunOs user account basis by Alcatel specific security services (Centralized User Management) present on the OMC-R; no more specific logging in is required to access IMT services.

! IMT services on a Windows PC: the access remains controlled through logging in on a per MFS platform user account basis (Tru64 UNIX user accounts declared on both control stations).

The security on the MFS control platform is enhanced from B9 release on: this is detailed in a new document (see ref.:[29])

7.4.1 IMT launching

The IMT uses signed JAVA applets technology: the launching of the remote IMT screens is only allowed to machines that store the right signature file.

7.4.1.1 Local

Moreover, when launching the IMT, the local operator (Windows PC) must enter a user name and a password.

This user name and password must come from an MFS control station user account (an user account must exist on both control stations).

According to this user name, the operator will not have the same rights, and so not the same IMT views.

At least three users will be defined at MFS installation:

- root, platform : reserved for Alcatel teams, have all rights

- admin : has access to equipment and alarm management views

- omcxchg : dedicated to data exchange with the OMC (MLU files, PM files, version change delivery files).

- craft : has only access to supervision views.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

gprs management functional specification mfs b9 ed06.pdf

Documents

released evolium

review ed

3bka55cbr156033 ed

secure single gb features

jaaa dszza

functional specification

gprs application

mxbsc 3bka20cbr157555