mfs gom sw component description b9 ed02.pdf

ED 02 RELEASED

Evolium 3bk09622jaaapezza-ed2rl.doc 02-08-27

3BK 09622 JAAA PEZZA Y 1/2

Site

VELIZY EVOLIUM SAS

Originators

O&M Team

MFS

GOM SW COMPONENT DESCRIPTION

RELEASE B9

Domain : ALCATEL 900/BSS Division : PRODUCT DEFINITION Rubric : MFS Type : DETAILED SPECIFICATION AND DESIGN Distribution Codes Internal : External :

ABSTRACT

This document describes the software design of the GPRS Operation & Maintenance (GOM) Agent in the MFS B9 MR3. It applies to BSS release B9.

Approvals

Name App.

D.ALBONICO L.RAPHALEN

Name App.

ED 02 RELEASED

Evolium 3bk09622jaaapezza-ed2rl.doc 02-08-27

3BK 09622 JAAA PEZZA Y 2/2

REVIEW

Ed. 01 04/112004 Approved with review report GOM SW COMPONENT DESCRIPTION EVOLIUM/MRD/CNS/2004-4178

HISTORY

Ed. 01 Proposal 01 14/10/2004

Creation issued from 3BKA09622JAAAPEZZA

Ed. 01 RELEASED 04/11/2004 Remarks EVOLIUM/MRD/MFS/2004-4178

Ed. 02 Proposal 02 12/05/2005 Creation issued from 3BKA09622JAAAPEZZA

Ed. 02 RELEASED 13/09/2005 Remarks EVOLIUM/MRD/MFS/2005-4694

INTERNAL REFERENCED DOCUMENTS

Not applicable.

FOR INTERNAL USE ONLY

Not applicable.

END OF DOCUMENT

ED 02 RELEASED

Evolium

3bk09622jaaapezza-ed2rl.doc

04/11/2004 3BK 09622 JAAA PEZZA 1/380

DETAILED SPECIFICATION AND DESIGN

TABLE OF CONTENTS

SCOPE................................................................................................................................................. 16 1 MAIN FEATURES........................................................................................................................... 17 2 DATA MODEL ................................................................................................................................ 19

2.1 CMPS data model............................................................................................................... 19 2.2 Alarms................................................................................................................................. 19

3 EXTERNAL INTERFACES............................................................................................................. 20 3.1 GEM Interface..................................................................................................................... 20

3.1.1 Interface with subscription ................................................................................................... 20 3.1.2 Interface without subscription .............................................................................................. 21

3.2 LXPU Interface ................................................................................................................... 21 3.3 GAM interface..................................................................................................................... 21 3.4 GPM interface..................................................................................................................... 22 3.5 Administrative interface.................................................................................................... 22

4 ARCHITECTURE............................................................................................................................ 23 4.1 Overview ............................................................................................................................. 23

4.1.1 Communications flows and constraints ............................................................................... 24 4.1.2 GOM internal Architecture ................................................................................................... 24

4.2 Administrative Server........................................................................................................ 25 4.2.1 Managed Objects................................................................................................................. 26 4.2.2 Operations ........................................................................................................................... 27

4.3 Object Control Server........................................................................................................ 27 4.3.1 Reception Thread Role........................................................................................................ 28 4.3.2 LXPUn Threads Role........................................................................................................... 28

4.3.2.1 LXPU discovery ........................................................................................................... 29 4.3.2.2 Global LXPU configuration .......................................................................................... 29 4.3.2.3 Radio massive configuration change .......................................................................... 29 4.3.2.4 Resource supervision .................................................................................................. 29 4.3.2.5 On-line LXPU configuration ......................................................................................... 30 4.3.2.6 Synchronisation after a control station switchover ...................................................... 30 4.3.2.7 Initialisation of the LXPUn thread ................................................................................ 30

4.3.3 Alarm thread Role ................................................................................................................ 30 4.4 GOM Interactions ............................................................................................................... 31

4.4.1 Overview .............................................................................................................................. 31 4.4.1.1 Interactions in configuration mode............................................................................... 31 4.4.1.2 Interactions in site mode.............................................................................................. 31

4.4.2 Internal/External interaction scenario .................................................................................. 34 4.4.2.1 Interactions with LXPU ................................................................................................ 34 4.4.2.2 Interaction between GOM and GEM ........................................................................... 36 4.4.2.3 Interaction with GAM ................................................................................................... 38 4.4.2.4 Interaction with GPM ................................................................................................... 39

4.4.3 Interactions between Admin thread and LXPUn threads .................................................... 39 4.4.4 Interactions between Reception thread and LXPUn threads .............................................. 41 4.4.5 Interaction between LXPUn Threads and Alarm Thread..................................................... 41 4.4.6 Interactions between Admin thread and Equipment thread ................................................ 41

4.5 Internal tables..................................................................................................................... 41

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 2/380

4.5.1 LXPU Logical Number mapping .......................................................................................... 41 4.5.2 LXPUn thread allocation ...................................................................................................... 42 4.5.3 BssRef / OamRef Table....................................................................................................... 42 4.5.4 Paging Area structures ........................................................................................................ 42

4.5.4.1 Structure for main of a Bss and for Pilot...................................................................... 43 4.5.4.2 Structure for Main of a La ............................................................................................ 43 4.5.4.3 Structure for Main of a Ra............................................................................................ 44

4.6 Thread priority.................................................................................................................... 44 4.6.1 Initialisation of the main thread (Admin thread) ................................................................... 45 4.6.2 Initialisation of an lxpu thread .............................................................................................. 46 4.6.3 Initialisation of Alarm thread ................................................................................................ 46

5 SOFTWARE DESIGN..................................................................................................................... 47 5.1 Software architecture ........................................................................................................ 47

5.1.1 O&M model .......................................................................................................................... 48 5.1.2 LXPU model......................................................................................................................... 48 5.1.3 Software layers .................................................................................................................... 49 5.1.4 Object identifier .................................................................................................................... 49

5.2 Packages ............................................................................................................................ 50 5.2.1 Class diagram...................................................................................................................... 52

5.2.1.1 Rebuild the MIB ........................................................................................................... 56 5.2.1.2 Process CMPS requests ............................................................................................. 57 5.2.1.3 Manage LXPU connections ......................................................................................... 57 5.2.1.4 Send LXPU messages................................................................................................. 57 5.2.1.5 Receive LXPU messages............................................................................................ 57 5.2.1.6 Send LXPU global configuration.................................................................................. 58 5.2.1.7 Radio Massive Configuration Change......................................................................... 58 5.2.1.8 Synchronise on LXPU resource states........................................................................ 58 5.2.1.9 Equipment change notifications................................................................................... 58 5.2.1.10 Alarm registration ................................................................................................ 58 5.2.1.11 Fault Report sending ........................................................................................... 58 5.2.1.12 MultiGpu management ........................................................................................ 58 5.2.1.13 Cells mapping handling ....................................................................................... 59 5.2.1.14 Multi-Interface/Multi version management .......................................................... 60

5.2.2 OAM package ...................................................................................................................... 60 5.2.2.1 OamDmCore and OamCorePersistent........................................................................ 62 5.2.2.2 OamConstructor .......................................................................................................... 62 5.2.2.3 OamManager class...................................................................................................... 62 5.2.2.4 OamCore class ............................................................................................................ 63 5.2.2.5 OamCmpsConfig class................................................................................................ 65 5.2.2.6 OamCmpsAttribute class............................................................................................. 65 5.2.2.7 OamCmpsTranslatorSet.............................................................................................. 66 5.2.2.8 OamCmpsTranslatorDeclaratorTmpl .......................................................................... 66 5.2.2.9 OamConfirmCtx class.................................................................................................. 66 5.2.2.10 Inter Thread indication......................................................................................... 67 5.2.2.11 Admin thread encapsulation................................................................................ 68

5.2.3 CML package....................................................................................................................... 69 5.2.3.1 Model ........................................................................................................................... 69 5.2.3.2 BssRef / OamRef Table............................................................................................. 109 5.2.3.3 Use examples ............................................................................................................ 115

5.2.4 Main package..................................................................................................................... 120 5.2.4.1 Gom class.................................................................................................................. 120 5.2.4.2 Mode, ConfMode and Site classes............................................................................ 121 5.2.4.3 ModeBuilder and ModeBuilderTmpl classes ............................................................. 122 5.2.4.4 GomInitControler class .............................................................................................. 123

5.2.5 Common packages............................................................................................................ 124 5.2.5.1 Interface packages .................................................................................................... 124 5.2.5.2 Global Package ......................................................................................................... 131

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 3/380

5.2.5.3 Functional Services Packages .................................................................................. 139 5.2.6 Functional Packages ......................................................................................................... 163

5.2.6.1 Data Element package .............................................................................................. 164 5.2.6.2 Lxpu package ............................................................................................................ 172 5.2.6.3 Packages related to functional configuration domains.............................................. 178

6 DYNAMIC BEHAVIOUR............................................................................................................... 220 6.1 Main principles................................................................................................................. 220 6.2 GOM initialisation ............................................................................................................ 221

6.2.1 Initialization before main entry point. ................................................................................. 223 6.2.1.1 OamXXX class building ............................................................................................. 223 6.2.1.2 Declare OamConstructor........................................................................................... 223 6.2.1.3 Declaration of OamCmpsConfigXXX......................................................................... 224

6.2.2 CmlXXX class building....................................................................................................... 225 6.2.2.1 Functional automaton declaration ............................................................................. 225 6.2.2.2 Message generator declaration ................................................................................. 226

6.2.3 DataElementXXX class building ........................................................................................ 227 6.2.3.1 DateElement declaration ........................................................................................... 227 6.2.3.2 DataElementFactory declaration ............................................................................... 228

6.2.4 DownloadManagerXXX class building............................................................................... 229 6.2.5 Rebuild from DM configuration tables ............................................................................... 230 6.2.6 Connection to GEM............................................................................................................ 231 6.2.7 Connection to GAM and Alarms thread initialization ........................................................ 231 6.2.8 Communication layer initialisation ..................................................................................... 232 6.2.9 GOM start up sequences................................................................................................... 232

6.2.9.1 In configuration mode ................................................................................................ 232 6.2.9.2 At cold start in site mode ........................................................................................... 233 6.2.9.3 At switchover in site mode......................................................................................... 234 6.2.9.4 at switchover after a migration................................................................................... 235

6.3 GEM Object management ............................................................................................... 235 6.3.1 Processing messages from GEM ...................................................................................... 235 6.3.2 Board creation.................................................................................................................... 235 6.3.3 Board deletion.................................................................................................................... 236 6.3.4 PcmTtp equipment............................................................................................................. 237 6.3.5 PcmTtp unequipment ( not supported ) ............................................................................. 237

6.4 Common functionnal scenarii ........................................................................................ 238 6.4.1 Mono lxpu CMPS request processing ............................................................................... 238

6.4.1.1 Create request ........................................................................................................... 238 6.4.1.2 Set request ................................................................................................................ 241 6.4.1.3 Delete request ........................................................................................................... 243 6.4.1.4 Action request............................................................................................................ 248 6.4.1.5 Internal action management ...................................................................................... 250

6.4.2 Multi-lxpu CMPS request processing ................................................................................ 252 6.4.2.1 Management in OamCmlAssociator.......................................................................... 252 6.4.2.2 Broadcasted set request............................................................................................ 255 6.4.2.3 Broadcasted delete request....................................................................................... 255

6.4.3 State management............................................................................................................. 257 6.4.3.1 State management in mono lxpu environment.......................................................... 258 6.4.3.2 State management in multi lxpu environment ........................................................... 258

6.4.4 Functional timer management ........................................................................................... 259 6.4.4.1 Arming functional timer .............................................................................................. 259 6.4.4.2 Functional timer expiry............................................................................................... 260

6.4.5 Lxpu registration, and version mapping............................................................................. 260 6.4.5.1 Global registration...................................................................................................... 260 6.4.5.2 Partial reactivation of registration .............................................................................. 263

6.4.6 LXPU unregistration........................................................................................................... 264 6.4.6.1 Global unregistration.................................................................................................. 264 6.4.6.2 Partial unregistration.................................................................................................. 265

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 4/380

6.4.7 Request messages creation .............................................................................................. 266 6.4.8 Processing of confirmations configuration......................................................................... 267

6.4.8.1 During global configuration processing ( Download or MLU )................................... 267 6.4.8.2 During on-line configuration....................................................................................... 269

6.4.9 Invocation of Lxpu-reset. ................................................................................................... 269 6.4.9.1 Invocation from Lxpu Thread..................................................................................... 270 6.4.9.2 Invocation from Admin Thread .................................................................................. 271

6.5 Lxpu management ........................................................................................................... 271 6.5.1 Lxpu connection................................................................................................................. 271 6.5.2 Lxpu disconnection ............................................................................................................ 271

6.5.2.1 Generic behaviour in Cml layer ................................................................................. 272 6.5.2.2 Generic behaviour in CmlXXX classes...................................................................... 272

6.5.3 Indication managed at lxpu level ....................................................................................... 272 6.5.4 LXPU global configuration ................................................................................................. 273 6.5.5 Massive radio configuration change .................................................................................. 277 6.5.6 Lxpu version change and propagation in functional model ............................................... 279 6.5.7 Reconnection timer expiry after a switchover.................................................................... 280 6.5.8 Synchronisation on LXPU after control station switchover................................................ 281 6.5.9 resynchronization after migration....................................................................................... 284

6.6 Particular Processings in functional domain ............................................................... 284 6.6.1 Particular processings in Transport domain ...................................................................... 284

6.6.1.1 Checks made on transport domain objects during CMPS operations ...................... 284 6.6.1.2 LapDLink registration and unregistration................................................................... 284 6.6.1.3 Registration/unregistration of GicGroups .................................................................. 286 6.6.1.4 ReserveGics action.................................................................................................... 288 6.6.1.5 ReserveLapDLink action ........................................................................................... 292 6.6.1.6 End of LapDLink deletion and impacts on cell management domain ....................... 293 6.6.1.7 End of GicGroup deletion and impacts on cell management domain ....................... 294

6.6.2 Particular processing in Gb domain................................................................................... 295 6.6.2.1 Checks made on Gb domain objects during CMPS operation.................................. 295 6.6.2.2 Nse registration/unregistration................................................................................... 295 6.6.2.3 Nse deletion............................................................................................................... 297

6.6.3 Particular processing in radio domain ............................................................................... 298 6.6.3.1 Bss related scenarii ................................................................................................... 298 6.6.3.2 Paging Area and Pilot management.......................................................................... 308 6.6.3.3 Bss reshuffle action and cell mapping in B8.............................................................. 316 6.6.3.4 Reshuffle activation after a cold-startup .................................................................... 325 6.6.3.5 Rebuild of subBss cell list after a switchover ............................................................ 325 6.6.3.6 Bss reshuffle action and cell mapping in B9.............................................................. 327 6.6.3.7 Radio domain resynchronization after a swithover.................................................... 336 6.6.3.8 SubBss last lapDLink deletion ................................................................................... 337 6.6.3.9 SubBss last GicGroup deletion.................................................................................. 338 6.6.3.10 Gsl related scenarii............................................................................................ 338 6.6.3.11 Cell related scenarii ........................................................................................... 343

7 SINGLE SECURED GB................................................................................................................ 356 7.1 Introduction ...................................................................................................................... 356 7.2 Impact in GOM.................................................................................................................. 356 7.3 Implementation ................................................................................................................ 356 7.4 Class and methods modifications ................................................................................. 358

7.4.1 Modifications in OamBss for Single Secured Gb. ........................................................... 358 7.4.2 Modifications in CmlNsvc to check the nsVcStateChangeIndreceived from GPU. .... 358 7.4.3 Modifications in ControlStation to enable or disable Single Secured Gb........................ 359 7.4.4 Creation of SecuredGbManager to manage the Single Secured Gb.............................. 359 7.4.5 Modifications in OamCell to change the bvcid mapping computation rule........................ 360 7.4.6 Common methods for mediation between OamBss and SecuredGbManager. ................ 361

7.5 Sequence diagrams......................................................................................................... 363 7.5.1 Sequence diagram for gb down ...................................................................................... 363

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 5/380

7.5.2 Sequence diagram for gb up ........................................................................................... 364 7.6 State transition diagrams................................................................................................ 365

7.6.1 SecuredGbState description.............................................................................................. 365 7.6.2 State transition diagram for Gb down.............................................................................. 366 7.6.3 State transition diagram for Gb up .................................................................................. 366

8 ALARMS MANAGEMENT............................................................................................................ 367 8.1.1 Object registration/unregistration in(from) RefAlarmTable ................................................ 367 8.1.2 Send alarm to GAM ........................................................................................................... 368

9 OBJECT MAPPING ON THREADS............................................................................................. 369 10 AUTOMATONS ............................................................................................................................ 370

10.1 LxpuManager automaton ................................................................................................ 370 10.2 DownloadManager automaton ....................................................................................... 371

10.2.1 B8 automaton ............................................................................................................ 371 10.3 Admin thread automaton ................................................................................................ 376

11 INTERACTIONS BETWEEN THREADS...................................................................................... 377 11.1 Messages structure ......................................................................................................... 377

12 MESSAGES STRUCTURE BETWEEN ADMIN THREAD AND LXPUN THREADS.................. 378 12.1.1 Message between LXPUn threads and Alarm thread ............................................... 380

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 6/380

TABLE OF FIGURES

Figure 1: Global MFS O&M Architecture............................................................................................... 17

Figure 2: GOM external interfaces ........................................................................................................ 23

Figure 3: GOM architecture................................................................................................................... 25

Figure 4: GOM interactions in configuration mode ............................................................................... 31

Figure 5: GOM interactions in site mode............................................................................................... 34

Figure 6: Interactions between threads on LXPU messages................................................................ 34

Figure 7: BscVersionChange ................................................................................................................ 35

Figure 8: Interactions between threads on GEM messages................................................................. 36

Figure 9: Interactions with GEM to ask a LXPU reset........................................................................... 36

Figure 10: Interactions with GEM at startup.......................................................................................... 37

Figure 11: Interactions with GEM at startup after a switchover ............................................................ 37

Figure 12 migration or not migration ..................................................................................................... 38

Figure 13: Interactions with GAM to send fault reports......................................................................... 38

Figure 14: Mapping between O&M and LXPU models ......................................................................... 47

Figure 15: Software layers structure ..................................................................................................... 49

Figure 16: Component diagram ............................................................................................................ 51

Figure 17: Functional dependency........................................................................................................ 52

Figure 18: Main classes diagram .......................................................................................................... 53

Figure 19: OAM package ...................................................................................................................... 61

Figure 20 : Lxpu thread to Admin thread generic indication ................................................................. 67

Figure 21 : CmpsProxy class ................................................................................................................ 68

Figure 22: CmlCore and CmlCmpsAttribute classes. ........................................................................... 69

Figure 23: Cml contextes and abstract management. .......................................................................... 75

Figure 24 CmlOperationConfirmCtx attributes...................................................................................... 75

Figure 25 CmlOperationConfirmCtx methods....................................................................................... 76

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 7/380

Figure 26 CmlInternalActionCtx class ................................................................................................... 78

Figure 27 CmlInternalActionCtx methods. ............................................................................................ 79

Figure 28: public CML interface of Message ........................................................................................ 79

Figure 29 DataElement attributes. ........................................................................................................ 81

Figure 30 CallBackMsg methods .......................................................................................................... 83

Figure 31 DataElementAbstractBuilder attributes................................................................................. 84

Figure 32 DataElementAbstractBuilder method.................................................................................... 84

Figure 33 DataElementBuilderTmpl class parameter ........................................................................... 85

Figure 34 DataElementBuilderTmpl method......................................................................................... 85

Figure 35 DataElementFactory attributes. ............................................................................................ 85

Figure 36 DataElementFactory methods. ............................................................................................. 86

Figure 37 DataElementFactoryManager attributes ............................................................................... 86

Figure 38 DataElementFactoryManager methods ................................................................................ 87

Figure 39 DataElementFactoryDeclarator attribute. ............................................................................. 87

Figure 40 DataElementFactoryDeclarator method. .............................................................................. 87

Figure 41: CmlManager class ............................................................................................................... 88

Figure 42: Classes managing the LXPU.............................................................................................. 92

Figure 43 Lxpu management and domain management .................................................................... 104

Figure 44 Indication for lxpu thread..................................................................................................... 109

Figure 45: Align State transition diagram............................................................................................ 113

Figure 46: Lxpu State transition diagram ............................................................................................ 115

Figure 47: example of a SET operation on a Bearer channel............................................................. 116

Figure 48: Example of a Bearer channel create. ................................................................................ 118

Figure 49 GOM class attibutes............................................................................................................ 121

Figure 50 GOM class methods. .......................................................................................................... 121

Figure 51 Mode attributes ................................................................................................................... 122

Figure 52 Mode methods. ................................................................................................................... 122

Figure 53 ModeBuilder attribute.......................................................................................................... 122

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 8/380

Figure 54 ModeBuilder methods ......................................................................................................... 123

Figure 55 GomInitControler attributes................................................................................................. 123

Figure 56 GomInitControler methods.................................................................................................. 124

Figure 57 Gem interface class model ................................................................................................. 125

Figure 58 Gam interface class model ................................................................................................. 127

Figure 59 : Inter Thread global services model................................................................................... 132

Figure 60: Secure table generic services model................................................................................. 134

Figure 61: Miscellaneous services ...................................................................................................... 137

Figure 62 To Lxpu Thread indications................................................................................................. 140

Figure 63 Lxpu to Admin messages.................................................................................................... 141

Figure 64 Contextes carried by indications......................................................................................... 142

Figure 65 Download and NackCause management ........................................................................... 144

Figure 66 Functional Automaton related model .................................................................................. 149

Figure 67 multi-interface request messages generation model.......................................................... 152

Figure 68 Cml interface set ................................................................................................................. 158

Figure 69 Miscellaneous common functional classes......................................................................... 161

Figure 70 dataElement package model .............................................................................................. 164

Figure 71 : Lxpu package model......................................................................................................... 172

Figure 72: OamXXX and CmlXXX classes definition.......................................................................... 178

Figure 73 Radio domain global model ................................................................................................ 185

Figure 74: Bss environment ( part 1 ).................................................................................................. 186

Figure 75Bss management ( part 2 ) .................................................................................................. 187

Figure 76 Contextes related to radio domain management................................................................ 194

Figure 77 : Relation between PagingXXX objects .............................................................................. 199

Figure 78 Mapper and version management ...................................................................................... 205

Figure 79 Classes for download of radio configuration....................................................................... 217

Figure 80 Ater/AterMux domain model ............................................................................................... 218

Figure 81 Gb domain model................................................................................................................ 219

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 9/380

Figure 82: GOM global behaviour ....................................................................................................... 220

Figure 83 : Declaration of OamConstructor ........................................................................................ 223

Figure 84 Declaration of OamCmpsConfigXXX.................................................................................. 224

Figure 85 Functional automaton declaration....................................................................................... 225

Figure 86 Message generator declaration. ......................................................................................... 226

Figure 87 DataElement declaration..................................................................................................... 227

Figure 88DataElementFactory declaration ......................................................................................... 228

Figure 89 DownloadManager declaration ........................................................................................... 229

Figure 90: MIB rebuild order ............................................................................................................... 230

Figure 91: MIB rebuild (extract)........................................................................................................... 231

Figure 92 GOM start up sequence in configuration mode .................................................................. 232

Figure 93 GOMs cold start in site mode............................................................................................. 233

Figure 94 GOMs start up after a switchover ...................................................................................... 234

Figure 95 Create request in conf mode............................................................................................... 239

Figure 96 create request with or without Lxpu in site mode. .............................................................. 240

Figure 97 Set request in conf mode .................................................................................................... 241

Figure 98 Set request in site mode with or without Lxpu .................................................................... 242

Figure 99: Check modified attributes .................................................................................................. 243

Figure 100 Asynchronous deletion in conf mode................................................................................ 244

Figure 101 Synchronous deletion in conf mode.................................................................................. 245

Figure 102 Asynchronous deletion in site mode ................................................................................. 246

Figure 103 Synchronous deletion of a cell .......................................................................................... 247

Figure 104 Synchronous action management in configuration mode ................................................ 248

Figure 105 Asynchronous action management in configuration mode............................................... 249

Figure 106 A synchrous action in site mode with a lxpu..................................................................... 250

Figure 107 Oam layer to Cml layer internal action ( extract ) ............................................................. 251

Figure 108 Cml layer to Oam layer internal action (extract ) .............................................................. 252

Figure 109 Broadcast and parameter duplication on internal action................................................ 253

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 10/380

Figure 110 Broadcast and parameter duplication on delete or action indication................................ 254

Figure 111 Broadcast of set request among several CmlXXX instances ........................................... 255

Figure 112 Broadcast of a delete request among several CmlXXX instances. .................................. 256

Figure 113 Completion of broadcated synchronous delete request ................................................... 257

Figure 114 mono lxpu state change management.............................................................................. 258

Figure 115 State correlation in multi lxpu situation ............................................................................. 259

Figure 116 process issued on functional timer expiry......................................................................... 260

Figure 117: Registration of CmlXXX objects....................................................................................... 262

Figure 118: Registration of CmlXXX objects (extract) ........................................................................ 263

Figure 119: Reactivation of registration of CmlXXX objects (extract)................................................. 264

Figure 120: LXPU unregistration......................................................................................................... 265

Figure 121 creation of message sent towards Lxpu .......................................................................... 267

Figure 122: Confirmation treatment .................................................................................................... 268

Figure 123: Confirmation treatment .................................................................................................... 269

Figure 124: Lxpu reset is invoked by Lxpu thread .............................................................................. 270

Figure 125 Lxpu reset is invoked from Admin thread ......................................................................... 271

Figure 126 Lxpu disconnection generic management ........................................................................ 272

Figure 127: LXPU global configuration consecutive to a GEM notification ........................................ 274

Figure 128: LXPU global download consecutive to a LXPU open session ........................................ 275

Figure 129 Extract of download sequence.......................................................................................... 276

Figure 130: Massive change ............................................................................................................... 278

Figure 131 Propagation of a new Lxpus version................................................................................ 279

Figure 132 Lxpu-reconnection timer expiry after a switchover ........................................................... 280

Figure 133 Resynchronisation ( extract ) ............................................................................................ 283

Figure 134 registration on LapDLink. .................................................................................................. 285

Figure 135 unregistration of LapDLink................................................................................................ 286

Figure 136 GicGroup registration........................................................................................................ 287

Figure 137 GicGroup unregistration.................................................................................................... 288

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 11/380

Figure 138: ReserveGics action with GicGroup creation (part 1) ....................................................... 290

Figure 139: ReserveGics action for GicGroup creation: Lxpu message sending (part 2) .................. 290

Figure 140: ReserveGics action with GicGroup creation: differed response sending (part 3) ........... 291

Figure 141: ReserveLapDLink action with LapDLink creation (part 1) ............................................... 292

Figure 142 End of LapDLink deletion.................................................................................................. 293

Figure 143 End of GicGroup deletion.................................................................................................. 294

Figure 144 Nse registration................................................................................................................. 296

Figure 145 Nse unregistration............................................................................................................. 297

Figure 146 bss creation....................................................................................................................... 298

Figure 147 Bss download ( part 1 ) ..................................................................................................... 300

Figure 148 Bss download ( part 2 ) ..................................................................................................... 301

Figure 149 Bss static registration........................................................................................................ 303

Figure 150 Bss on-line registration ..................................................................................................... 304

Figure 151 Bss deletion first part ........................................................................................................ 305

Figure 152 End of Bss deletion ........................................................................................................... 306

Figure 153 Broadcast of MainPa election towards serving Lxpus...................................................... 307

Figure 154 Gsl loss-timer management on CmlBss state change...................................................... 308

Figure 155 Pa building with Bss.......................................................................................................... 309

Figure 156 Pa building with cells......................................................................................................... 310

Figure 157 Pa deletion with Bss.......................................................................................................... 311

Figure 158 Pa deletion with cells ........................................................................................................ 311

Figure 159 Paging Area modification .................................................................................................. 312

Figure 160 What happens on Paging Area when a cell is mapped.................................................... 313

Figure 161 Main lxpu for a Paging Area.............................................................................................. 315

Figure 162 Paging Area rebuild from Mib. .......................................................................................... 316

Figure 163 : BssReshuffle : CMPS request (part 1)............................................................................ 318

Figure 164 : BssReshuffle, compute cells mapping : init GchXXLoad (part 2)................................... 319

Figure 165: BssReshuffle, compute cells mapping : process GchXXLoad (part 3)............................ 320

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 12/380

Figure 166: BssReshuffle, apply registration on cells to be mapped (part 4) ..................................... 321

Figure 167: BssReshuffle, apply mapping on cells to be remapped (part 5)...................................... 322

Figure 168: BssReshuffle, cell create confirmation messages handling (part 6)................................ 323

Figure 169 : BssReshuffle, Cmps response (part 7)........................................................................... 324

Figure 170 Reshuffle at cold-startup ................................................................................................... 325

Figure 171 Association between cells and SubBss after a switchover............................................... 326

Figure 172 Version management in B9............................................................................................... 328

Figure 173 Object model used for B9 mapping and reshuffling.......................................................... 329

Figure 174 B9 mapping....................................................................................................................... 331

Figure 175 B9 mapping, detailed scenario ......................................................................................... 332

Figure 176 B9 reshuffle ....................................................................................................................... 333

Figure 177 B9 reshuffle, detailed scenario ......................................................................................... 334

Figure 178 B9 mappig with cell shared , detailed scenario ................................................................ 335

Figure 179 Radio domain synchronisation after a switchover ............................................................ 336

Figure 180 subBss last lapDLink deletion........................................................................................... 337

Figure 181 Gsl state change and new Pilot selection......................................................................... 339

Figure 182 Global Bss reset after a Gsl State Change....................................................................... 340

Figure 183 Lxpu disconnection on GSL not resulting from Nse deletion............................................ 341

Figure 184 Lxpu disconnection on GSL when this one is resulting from Nse deletion....................... 342

Figure 185 Gsl loss-timer expiry ......................................................................................................... 343

Figure 186 : CREATE request on CELL ............................................................................................. 345

Figure 187: Cell deletion outside reshuffling....................................................................................... 347

Figure 188 Focus on end of cell deletion ............................................................................................ 348

Figure 189 Cell deletion in reshuffling................................................................................................. 349

Figure 190 Cell deletion when Gsl loss-timer is armed ...................................................................... 350

Figure 191 Cell mapping ..................................................................................................................... 351

Figure 192 on-line cell registration outside MLU................................................................................. 352

Figure 193 Cell unregistration ............................................................................................................. 353

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 13/380

Figure 194 Nsei propagation when cell is already mapped ................................................................ 354

Figure 195 lxpu disconnection on cell and link with main lxpu for paging area selection................... 355

Figure 196 Sequence diagram for Gb down sequence ................................................................ 363

Figure 197 Sequence diagram for Gb up sequence..................................................................... 364

Figure 198 Send an alarm to GAM ..................................................................................................... 368

Figure 199: Object mapping on threads.............................................................................................. 369

Figure 200: LXPUn thread automaton ................................................................................................ 370

Figure 201 : B8, LXPU global configuration automaton (part 1) ......................................................... 372

Figure 202 : B8, LXPU global configuration automaton (part 2) ......................................................... 373

Figure 203 : B8, LXPU global configuration automaton (part 3, Bss) ................................................. 374

Figure 204 : B8, LXPU global configuration automaton (part 5, Cell)................................................. 375

Figure 205: Admin thread automaton.................................................................................................. 376

Figure 206: Internal message structure .............................................................................................. 377

Figure 207: ConfigIsReady message structure................................................................................... 378

Figure 208 MassiveChange message structure ................................................................................. 378

Figure 209: Lxpu Reset message structure ........................................................................................ 378

Figure 210: Update message structure............................................................................................... 378

Figure 211: Delete message structure................................................................................................ 379

Figure 212: Align message structure .................................................................................................. 379

Figure 213: Action message structure ................................................................................................ 379

Figure 214: Cml Internal Action message structure............................................................................ 379

Figure 215: Confirm message structure.............................................................................................. 380

Figure 216: Oam Internal Action message structure .......................................................................... 380

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 14/380

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

MFS GOM SW COMPONENT DESCRIPTION RELEASE B9

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 15/380

HISTORY


Ed. 01 RELEASED 04/11/2004 Remarks EVOLIUM/MRD/CNS/2004-4178


Ed. 02 RELEASED 13/09/2005 Remarks EVOLIUM/MRD/CNS/2005-4694

REFERENCED DOCUMENTS

[1] GPRS Management Functional Specification

3BK 09722 JAAA DSZZA [2] GPRS Management API

3BK 09713 GAAA PBZZA [3] MFS Alarm Dictionary

3BK 10204 0560 DTZZA [4] Equipment Management and Alarms API

3BK 09639 GAAA PBZZA [5] MFS O&M MFS Telecom Interface Specification

3BK 09638 JAAA PBZZA [6] Nectar Administration Local Agent Functional Specification

3CM 00335 CAAA DSZZA

RELATED DOCUMENTS

[7] MFS O&M Architecture

3BK 09665 JAAA EBZZA [8] GPRS NE Platform Equipment and Alarm Mngt Func Spec

3BK 09584 JAAA DSZZA

PREFACE

The aim of this document is to present the design of the GOM SW component of the MFS O&M sub-system. This SW component is in charge of the GPRS telecom O&M configuration and supervision.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 16/380

SCOPE

This document specifies the GOM agent of the MFS for the MR3. It is part of the BSS release B9.

This document is mainly intended to:

The developers of the MFS.

The GPRS O&M integration & validation team.

The new features added in GOM are:

starting optimization during control station switchover phase.

additional attributes of objects at MDL interface.

Multiple CML interface facing with GPU in B9 and GPU in B8 at the same time.

The detailed features of the Step 1 phase are described in [1].

The previous B8 features in GOM are still maintained:

Multi-GPU per BSS.

balanced dispatching of cells of overGPUs for each BSC.

Ater interface with BSC.

Additional features related to multi-gpu, such as main gpu election.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 17/380

1 MAIN FEATURES

The GPRS Operation and Maintenance (GOM) Agent on the MFS control station manages the GPRS telecom resources configuration and supervision. It manages the Bearer, Gb interface, GAter/GAterMux interface and Cell Management domains. It is mainly in relation with the TRM (Telecom Resource Manager) Agent on the LXPU. It also interacts with the administrative agents (Q3 agent and craft terminal). The roles of GOM are:

GPRS logical configuration for the Bearer, Gb interface, GAter/GAterMux interface and cell management domains which includes the validity check, the update of the persistent data and the message sending to the LXPU.

Supervision for these domains, i.e. the report of state change notifications to the administrative part and quality of service alarms.

Resynchronisation on the LXPU resource states after a control station switchover.

Global configuration of the LXPU when a LXPU asks for it, after a start, reset or switchover.

CMPS requests processing from the administrative agents.

several LXPU interfaces management to cope with BSS version change feature.

GOM GEM GAM

CraftTerminal

1

32

1

2

4 Interface to GAM

Interface to Admin

Interface to XPU

DM CFG Semi permanent configuration data

DM RSC Dynamic resource data (states).

GPM

XPU board

DMCFGMIB

Q3 AGENT

DMRSCMIB

3 Interface to GEM

4

OMC

5

5 Interface with GPM

Figure 1: Global MFS O&M Architecture

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 18/380

GOM interacts with five components:

The craft terminal and the Q3 Agent for administrative purpose.

The GAM and GEM for alarm and equipment management purpose.

The XPU for telecom resource configuration and supervision.

GOM shares data tables with GPM. It provides a simple interface that allows GPM to retrieve information it will forward in its reports with measurements.

The craft terminal allows to set site parameters through CMPS requests. All other interactions are performed with the Q3 agent.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 19/380

2 DATA MODEL

2.1 CMPS data model

The GOM data model is described in [2].

2.2 Alarms

Table 1 lists the classes on which alarms are reported to the administrative agent according to [3]. The instance of these classes must be referenced to GAM at creation time.

FRBearer

NSVC

PVC

BSS

LapDLink

GicGroup

Table 1: Classes supporting alarms

Some fault reports are sent by GOM to GAM. These fault reports are defined in [3].

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 20/380

3 EXTERNAL INTERFACES

3.1 GEM Interface

3.1.1 Interface with subscription

GOM interacts with GEM to receive the notifications of creation ,deletion of the LXPU, and LXPU state changes, and the associations between the PCM-TTP and the LXPU. The interface is based on a subscription mechanism to GEM. This subscription is made at GOMs start-up in site mode.

As GOM in B9 will be facing two kinds of interface during migration phase ( B8 and B9 ) while O&M interface is in B8, GEM must provide GOM with the interface version. This allows GOM to process the correct mapping between the O&M interface and the LXPU interface

This interface offers five services:

The LXPU notifications through which GEM sends the logical number of the LXPU and its CMPS Distinguished Name (DN) when a new LXPU appears. The version of LXPU interface is also transmitted.

The PCM-TTP notifications through which GEM sends the port number, the CMPS DN and the LXPU DN when a PCM-TTP is equipped. The deletion of PCM-TTP is not notified since it only occurs when the LXPU is deleted.

The LXPU state-change noticifation. This state must be taken into account by GOM when it maps cells on LXPU ( related to multi-GPU feature )

Notification of Lxpu deletion.

GEM grants connections from one or all LXPU (GpuConnectAllowed). We also use this mean to propagate the version identifier of involved lxpu.

All those messages are sent in a CS session opened between GOM and GEM at subscription time

Notifications are performed by the mean of messages received in GOM. The messages are the following:

GEM_BOARD_CREATED: gives to GOM references of the LXPU.

GEM_BOARD_DELETED: informs GOM that an LXPU has been deleted.

GEM_BOARD_STATE_CHANGE : informs GOM that LXPU state has changed. Possible states seen by GOM are : Failed, Locked, Available, Undefined

PCM_TTP_EQUIPPED: gives to GOM references of the PCM-TTP and PCM port number for a given LXPU.

PCM_TTP_UNEQUIPPED: informs GOM that a PCM-TTP has been unequipped. This information is sent e.g. when the remote equipment attribute of the PCM-TTP is set to unknown. In this case, there is no telecom resource on this PCM-TTP. But this feature is not supported by GOM.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 21/380

3.1.2 Interface without subscription

GOM also interacts with GEM for five other purposes:

To ask GEM to reset a given LXPU (LxpuReset) It is made upon a CS question/answer mechanism with GEM.

To notify GEM that the radio file resynchronisation consecutive to a software version change is completed for a given LXPU (StartOperation). It is performed by the mean of a CS datagram

To forward to GEM, notification received from a LXPU on a BSS that indicates a version change. GOM has to calculate the set of LXPU supporting the BSS before sending the message to GEM. It is done with a CS datagram.

To synchronise Q3 agent start-up after a station switchover. GOM asks to GEM, the number of LXPUs full initialization it has to wait before allowing Q3 agent to start. This task is also made by the mean of a CS datagram.

To detect if switchover is a consequence of a migration. GOM requests this information to GEM. This is supported by CS question/answer mechanism. According to the result internal backuped table may be cleaned ( cleaned if not in migration, kept untouched otherwise ).

For the detailed description of this interface, refer to [4].

3.2 LXPU Interface

GOM interacts with TRM on the XPU. TRM reroutes the messages to the BCM, NS and RRM agents. It is the main data flow for GOM.

Furthermore GOM deals with two different interfaces. One with a TRM in B8and one with a TRM in B9. This situation will last until all BSS will have migrated to B8. But both interfaces will remain in code.

Interfaces and protocols are described in [5].

3.3 GAM interface

GOM must indicate to GAM the references of objects supporting alarms. This interface is described in [4].

Moreover, GOM sends fault reports to GAM using the interface described in Erreur ! Source du renvoi introuvable..

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 22/380

3.4 GPM interface

This interface is made of three shared configuration tables ( Extension, Cell and BtsSiteManager ), used by GPM to retrieve information for measurements report building purpose.

3.5 Administrative interface

The administrative interface (Q3 agent and craft terminal) uses CMPS. The SET, CREATE, and ACTION operations are processed by GOM. DELETE operation uses ACTION mean to achive object deletion. Since ACTION can be defined either Synchronous or Asynchronous Action GOM allows to perform both types of deletion, depending on functional needs. Other CMPS operations such as GET, GET_WHEN, are directly managed by the NECTAR NCAC library.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 23/380

4 ARCHITECTURE

4.1 Overview

GOM is a Nectar SCIM in active/standby mode. It interacts with four main entities:

Administrative agents (Q3 agent, craft terminal, ) through a CMPS / CS interface in order to configure and supervise the telecom resources present in GOM.

Running LXPU through XDR / CS communications in order to configure and supervise the telecom resources on the LXPU. XDR encoding is used since the control station and the LXPU have different word representation.

GEM through CS communications in order to be notified of the equipment changes, to be authorised to accept LXPU connections, to ask LXPU reset and to notify the end of radio file resynchronisation after a software version change. This interface does not used XDR encoding since both SCIMs are on the same station.

GAM through XDR/CS communications and shared table in order to report alarms. XDR encoding is used for alarm sending in order to keep the same interface that the one between GAM and LXPU. A shared table is used to store the relation between the reference of the object at the O&M level and the reference of the object in the telecom part.

GPM through shared configuration tables

Sharedtable

AdministrativeServer

CMPS / CS

ObjectControlServer

XDR/CS

CS

AdministrativeAgents

LXPU

GEM

GAM

XDR/CS

GPMSharedtable

Figure 2: GOM external interfaces

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 24/380

4.1.1 Communications flows and constraints

The main communication flow is the one with the LXPU. GOM must be able to download an LXPU configuration in a few seconds when the LXPU asks for a connection with GOM. Moreover, LXPU reports state change notifications that must be notified to the operator as soon as possible.

The second flow of communication comes from the administrative agents. It is composed of administrative requests (object creation, modification or action ( deletion and real actions )). This flow has a lower priority than the previous one. Nevertheless, it may be important, i.e. several requests per second.

The communication flow from the GEM is low since there is only notifications of new boards, board deletion , board state change, and PCM-TTP equipment and unequipment. There is at most two hundred short messages, for instance after a switchover with a maximum MFS configuration.

The communication flow to the GAM transfers alarms. These alarms have the same priority than the state changes. They are limited to a small number of objects. The maximum number of alarm reports occur when a Bsc fails. It may reach two hundred alarms.

There is no traffic with GPM.

4.1.2 GOM internal Architecture

GOM is divided in two main parts:

The administrative server in charge of processing the requests from the CMPS interface, and managing the infomodel provided at this interface level including the MIB storage.

The object control server in charge of the configuration and supervision of the running LXPU.

The Administrative Server part has one main thread (Admin on Figure 3), seen by the GOM application developer. An additional hidden thread (Event Report) is used by the NCAC runtime to process the CMPS GET_WHEN requests (refer to [6] for additional details). A third thread (Equipment) receives the equipment change notifications coming from GEM. This thread is delivered with GEM and is not described any more in this document.

The Object Control Server has :

One main thread (Reception thread on Figure 3) to collect the open session messages arriving from the different LXPU ( session server ). It also manages a pre-allocated set of threads according to the number of running LXPU which are then assigned or re-assigned on demand.

Indeed, there is one LXPUn thread per running LXPU, used to download configuration and to forward state change notifications.

There is also an Alarm Thread that deals with the dynamic part of the interface with GAM.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 25/380

CS Port

Thread

LXPU1

lp3

LXPU2

lp4

LXPUn

lpn

Reception

lp1

Admin

lp0

FAP_GOMLXP

FAP_GOM

FAP GOMADM

Administrative Server

Object Control Server

Equipment

lp2

Event Report

lp0

FAP GOMGEM

Alarm

lp30

Figure 3: GOM architecture

The description of the role of the threads and their interactions are described in next sections.

4.2 Administrative Server

The Administrative Server is mainly responsible for handling CMPS encoded requests with regard to LXPU resources. The following actors may access it:

The operator on the craft-terminal

The Q3 agent after receiving a request from the OMC-R.

The Administrative Server manages the GPRS logical configuration for the Bearer, Gb interface, Gater/GAterMux interface and Cell management domains. It includes the validity check, the update of the persistent data (MIB), the response sending through the CMPS interface. It also computes the set of modified attributes and which messages must be sent on LPXU interface, and sends the indications of modifications to the appropriate LXPUn thread in the Object Control Server if the latter exists. This late message can be duplicated in order to propagate it to several LXPU thread if ever configuration is splitted over several LXPUs.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 26/380

It also propagates messages to several LXPU threads when an previous trigger on this last one implies such a behaviour. That means that dispatching of a message to several LXPU threads must be done under the control of Admin thread whatever the trigger is.

It is also in charge of receiving the LXPU and PCM-TTP creation / deletion / state change notifications coming from GEM through the Equipment thread. On the LXPU creation notification, a global check is performed on the resources related to this LXPU. The Administrative server also indicates (if needed) to the appropriate LXPUn thread in the Object Control Server that the configuration is ready.

The Administrative Server also receives from GEM the authorisation to accept connections from the LXPU, and notifies to GEM the end of the radio file resynchronisation, both for software version change purposes.

Moreover, the Administrative Server registers and unregisters the instances of objects supporting alarms in the GAM shared table.

4.2.1 Managed Objects

The list of managed objects handled by GOM is described in [2].

These objects are a subset of the ones seen through the Q3 interface plus additional objects needed for configuration purpose.

All objects are mostly stored in private secured DM tables (DSIM) with a back up on the shared disks of the pilot stations. Few of them use public secured DM tables to open a static interface with GPM.

There are two types of attributes for a managed object:

Configuration attributes: describe the static data of an object and are exclusively updated by the Administrative Server when receiving a CREATE or SET request. They are in DM tables (configuration tables) which are back-uped on disk. Some of thoses attributes are strictly private to GOM and are used to provided persistency facility in case of switchover.

Resource attributes: describe the dynamic states of an object. The Administrative Server does not update these attributes. They are in DM tables (resource tables) which are secured without back up ( with the only exception of NSE resource table for migration management purpose ). They are allocated at the same time the configuration attributes are on a CREATE request. They must be re-allocated by the application on a control station cold start.

The GOM module (as any NECTAR global agent) has two functional modes:

Configuration mode: the Administrative Server is waiting for CMPS creation request to populate DM tables. A NECTAR platform restart is necessary to switch into site mode. This mode is temporary and is used for configuration purpose only. In this phase, the root objects storing the site parameters are created.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 27/380

Site mode: the GOM module can use all information present in its DM tables. Configuration data have been created by an explicit CMPS CREATE request in configuration mode. In this phase, the main part of the objects managed by GOM are dynamically created, updated and deleted.

4.2.2 Operations

Operations modify the configuration data with the CREATE, SET, , ACTION operations or just read all data (configuration and resource) with the GET operation. DELETION are performed with an ACTION operation.

The Administrative Server uses the NECTAR NCAC library framework to perform these operations. The NCAC function nca_initialize initialises the NCA context (event report thread, data references, ) and nca_operation processes all the requests (operations and actions). Note that a GET operation does not need any specific code to be developed.

For each attribute defined by MDL model NCAC library automatically performs defiend checks, for the CREATE, ACTION-delete and SET operations, checks are associated to each class to be modified. Those checks represents the functional checks that must be performed by GOM when it deals with the request. There is one check per operation and per class. These checks are not mandatory, since there is a suitable default behaviour. The checks on each operation are in charge of the request validity, the response processing and delivering through the CMPS interface, and the message sending to the Object Control Server.

The GET, SET, CREATE operations are processed locally by the Administrative Server. The processing of the request continue on the Object Control Server in order to send (if necessary) the message to the LXPU. For the ACTION operation, there is no default behaviour and the code is entirely user specific, using NCAC facilities.

Note: When an ACTION modifies a resource attribute, it is directly forwarded to handled by the Object Control Server part in order to ensure the configuration and resource data isolation.

It is possible to defined both synchronous and asynchronous ACTION operations. In CMPS terminology asynchronous ACTIONS means that final response is given to a manager when action is performed on GPU, whereas when it is synchronous, response is given immediatly whithout taking care of the processing on the GPU. In the first case the late response must be done by the Admin thread when last confirmation is recevied from LXPU. This implies an uplink message between LXPU thread and Admin thread to change of executing thread.

4.3 Object Control Server

The Object Control Server (OCS) is responsible for the configuration and supervision of the LXPU resources, i.e. the telecom resources of the Bearer, Gb interface, Gater/GAterMux and Cell management domains. This includes the handling of the CS open session and abort session requests arriving from the LXPU, the sending of the configuration message to the LXPU, and the modification of the resource attributes in the DM tables (the report of notifications to the administrative agents is automatically performed by NCAC through the CMPS interface), the message sending towards Admin thread to activate this one when an asynchronous ( in CMPS terminology ) action is fullfilled on LXPU. Furthermore when configuration is splitted over several LXPUs, OCS must first correlate resource attributes before updating DM tables.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 28/380

OCS is also in charge of the global configuration of a LXPU after a XPU start, reset or switchover. This action is performed when the LXPU contact OCS, i.e. when a CS session open request is received by OCS.OCS also handles the resynchronisation on the LXPU resources after a control station switchover.

4.3.1 Reception Thread Role

This thread has three main roles:

Manage (create, reallocate) the LXPUn threads.

Receipt the open session requests coming from all the LXPUs and dispatch them to the appropriate LXPUn thread. The dispatching is performed only if the connection has been allowed by GEM for this LXPU, otherwise the open session is refused.

On reception of a new open session request from a LXPUn, the reception thread looks for a free LXPUn thread. If one is found, it delegates the session to this LXPUn thread. Otherwise, the maximum number of connections is reached and the open session request is refused. A session delegation is a CS service which allows rerouting the messages arriving on a given local port to an other local port. This is performed at CS level. This means that the data messages and the close or abort session messages will be sent directly to the LXPUn thread. The opening may be refused if the Lxpu has not been declared yet by GEM and if its configuration is not considered has ready ( no PCM_TTP yet declared ).

When a LXPU fails (abort session message received by the LXPUn thread), the LXPUn thread must indicate to the Reception thread that the LXPUn thread is free and can be reused for another LXPU. Due to te fatc that NECTAR platfrom does not support SCIM defense, a LXPUn thread must not be destroyed since CS resources are associated with it during its creation, and that local port can be equipped only once. It could not be reused if the thread is destroyed.

4.3.2 LXPUn Threads Role

A LXPUn thread is in charge of all the processing necessary to send a configuration and to supervise a given LXPUn. Its main roles are:

Manage the LXPU discovery (a new XPU board has been plugged, a XPU board asks for its configuration after a XPU reset or switchover).

Download the global LXPU configuration after a LXPU initialisation.

Process the request notifications and confirmations from the LXPU.

Compute resource states and alarms.

Forward message to alarm thread for alam sending

Send one or several configuration message(s) to the LXPU on Administrative Server request, getting the objects and their attribute values from the MIB.

Send late confirmation towards Administrative Server in case of synchronous operation with LXPU.

Resynchronise on the LXPU resources (object states and status attributes) after a control station switchover.

ED 02 RELEASED

Evolium


04/11/2004 3BK 09622 JAAA PEZZA 29/380

4.3.2.1 LXPU discovery

The detection of a running LXPU occurs in several phases. Indeed, the LXPU

mfs gom sw component description b9 ed02.pdf

Documents