mfs internal interfaces messages definition b9 ed06.pdf

ED 06 RELEASED MFS INTERNAL INTERFACES - MESSAGES DEFINITION

3bk09638jaaapbzza-ed6rl.doc 21/10/2005

3BK 09638 JAAA PBZZA 1/96

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

Evo

lium

.

Site

VELIZY

EVOLIUM SAS

Originators F Binard

MFS INTERNAL INTERFACES

MESSAGES DEFINITION

Release B9

System : ALCATEL 900/BSS Sub-system : MFS Document Category : INTERFACE SPECIFICATION

ABSTRACT This document describes the internal interfaces within the MFS CF (Control Function)

This edition is valid for the MFS B9 MR3

"Do not edit this document, it has been generated by Data Management Center"

Interface or model type ClearCase Label

Telecom communication channel GOMCML-MFSB9.01-22

DMCGOM-MFSB9.01-17

Performance Manager communication channel GPMCML-MFSB9.01-10

Location service channel DMCGLM-MFSB9.01-02

GLMCML-MFSB9.01-02

Approvals

Name App.

(MFS/DPM) D ALBONICO

(MXMFS/DPM) D COTTIN

(MFS/RTA) L RAPHALEN

Name App.

(MFS/PMU) L PIGEOT




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

Evo

lium

.

REVIEW Ed. 01 Proposal 02 2004/04/29 no formal review meeting due to minor comments received by mail

only.

Ed. 03 Proposal 01 2004/12/09 no formal review meeting due to minor comments received by mail only.

Ed. 04 Proposal 01 2005/01/23 no formal review meeting due to minor comments received by mail only.

HISTORY

Ed. 01 Proposal 01 2004/04/08 Creation of the document.

Ed. 01 Proposal 02 2004/04/26 Update of the document by taking into account the following comments: ! at GPM/ TPM interface, generic messages must be used on a

cell class basis due to the high number of counters (LPI, IPE) ! in Cell create in GPU use case, the Cell-Set-Req/ Cell-Set-Cnf

is missing (PDE) ! few mistakes (FBI)

Ed. 01 Released 2004/05/03 Document is released

Ed. 02 Released 2004/06/21 Document is generated from DMC-MFSB9.01-02 database (location 60)

Document is released

Ed. 03 Proposal 01 2004/10/27 Update of the document for B9 Pack 2 Enhancement of chapter 3 to 5 description add dimensionning chapters for messages length

Ed. 03 Released 2004/12/09 take into account comment recieved from OBE (upd of msg list #5.5). Document is released

Ed. 04 Proposal 01 2005/02/04 Update of the document based on DMCGOM-MFSB9.01-11. Update GPM/TPM interface by adding the BTP block.

Ed. 04 Released 2005/02/23 take into account comment recieved by mail: ! max Buffer size for GPM/TPM reportCnf message ! Linked reply not used at GPM/TPM ! Computation of BTS_NB_EXTRA_ABIS_TS (GPM/TPM) Document is released

Ed 05 Proposal 01 2005/05/20 Update pf the document based on: ! 3BKA13FBR161783: in GPM file, BTS id is missing ! 3BKA13FBR164326:Generic PM report cnf description

aligned on dev

Ed 05 Released 2005/07/20 No comment is received - Document is released

Ed 06 Released 2005/10/18 Update pf the document based on 3BKA20CBR163136: BTP: introduction of new MXMFS capacity for MR3

As CRQ is RFC, the modification is included without review. Then Document is released




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

Evo

lium

.

TABLE OF CONTENTS

1 SCOPE ..........................................................................................................................................................7 2 OVERVIEW ...................................................................................................................................................8 3 COMMUNICATION PRINCIPLES BETWEEN GM AND LM .......................................................................9 4 GM/ LM PROCEDURES ............................................................................................................................10

4.1 Successfull requests.........................................................................................................................10 4.1.1 Request transactions (Create, Delete, Set, Lock, Unlock)........................................................10 4.1.2 Request transactions (report)....................................................................................................10 4.1.3 Synchonization point (end of config request usage). ................................................................10

4.2 Successfull Indications.....................................................................................................................11 4.2.1 State change, EventReport indications .....................................................................................11 4.2.2 Ready, Fault Report indications ................................................................................................12

4.3 Requests Failure................................................................................................................................12 4.3.1 ALL REQUESTS cause.............................................................................................................12 4.3.2 CREATE REQUEST cause.......................................................................................................12 4.3.3 DELETE REQUEST cause .......................................................................................................13 4.3.4 SET REQUEST cause...............................................................................................................14 4.3.5 END OF CONFIGURATION REQUEST cause ........................................................................14 4.3.6 LOCK REQUEST cause............................................................................................................15 4.3.7 UNLOCK REQUEST cause .....................................................................................................15

4.4 Indications Failure .............................................................................................................................15 4.4.1 Generic READY cause..............................................................................................................15

5 OVERALL DESCRIPTION OF CLASS AND MESSAGES........................................................................16 5.1 Interface models ................................................................................................................................16 5.2 Entity description...............................................................................................................................17

5.2.1 AmP entity description...............................................................................................................17 5.2.2 BmP entity description...............................................................................................................17 5.2.3 PcmPort entity description.........................................................................................................17 5.2.4 BcmP entity description .............................................................................................................18 5.2.5 LapDBc entity description..........................................................................................................18 5.2.6 FrBc entity description ...............................................................................................................18 5.2.7 RrmP entity description .............................................................................................................18 5.2.8 smlcP entity description.............................................................................................................18 5.2.9 Bss, lcsBss entities description .................................................................................................18 5.2.10 Cell (+DistCell) entity description ..............................................................................................19 5.2.11 lcsCell entity description............................................................................................................19 5.2.12 GchGroup entity description......................................................................................................19 5.2.13 Gsl entity description .................................................................................................................19 5.2.14 LapDLink entity description .......................................................................................................19 5.2.15 NsP entity description................................................................................................................19 5.2.16 Nse entity description ................................................................................................................20 5.2.17 NsVc entity description ..............................................................................................................20 5.2.18 Pvc entity description.................................................................................................................20 5.2.19 Cnx entity description ................................................................................................................20

5.3 State 21 5.4 Reference............................................................................................................................................21 5.5 Messages list......................................................................................................................................23

5.5.1 SCA-SCA Interface....................................................................................................................23 5.5.2 GEM-SCA Interface...................................................................................................................23 5.5.3 GEM-BAM interface...................................................................................................................24 5.5.4 GAM-BAM interface...................................................................................................................24




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

Evo

lium

.

5.5.5 GOM-BCM interface ..................................................................................................................25 5.5.6 GOM-RRM interface..................................................................................................................25 5.5.7 GOM-NS interface .....................................................................................................................27 5.5.8 GLM-LRM interface ...................................................................................................................28 5.5.9 GPM-TPM interface...................................................................................................................29

6 MESSAGES CONTENTS ...........................................................................................................................30 6.1 Header.................................................................................................................................................31

6.1.1 Class..........................................................................................................................................31 6.1.2 msgType....................................................................................................................................32 6.1.3 Request identifier.......................................................................................................................33 6.1.4 Data Element layout ..................................................................................................................33

6.2 Application Data ................................................................................................................................36 6.2.1 Generic Format..........................................................................................................................37 6.2.2 Generic Confirmation/ Response format...................................................................................37 6.2.3 Confirmation reportCnf format...................................................................................................37 6.2.4 Generic Fault report indication format .......................................................................................38 6.2.5 Generic fault report response format.........................................................................................39

6.3 DIMENSIONING ..................................................................................................................................40 7 DETAILED INTERFACES DESCRIPTION.................................................................................................42

7.1 GEM-BAM INTERFACE DESCRIPTION............................................................................................42 7.1.1 Overview....................................................................................................................................42 7.1.2 BmP entity .................................................................................................................................42 7.1.3 PcmPort entity ...........................................................................................................................44 7.1.4 Cnx entity...................................................................................................................................47

7.2 GOM-BCM INTERFACE DESCRIPTION ...........................................................................................49 7.2.1 Overview....................................................................................................................................49 7.2.2 BcmP entity................................................................................................................................49 7.2.3 LapDBc entity ............................................................................................................................52 7.2.4 FrBc entity..................................................................................................................................53

7.3 GOM-RRM INTERFACE DESCRIPTION ...........................................................................................55 7.3.1 Overview....................................................................................................................................55 7.3.2 Bss.............................................................................................................................................55 7.3.3 Cell.............................................................................................................................................57 7.3.4 FrBc ...........................................................................................................................................57 7.3.5 GchGroup ..................................................................................................................................58 7.3.6 Gsl .............................................................................................................................................58 7.3.7 LapDBc......................................................................................................................................59 7.3.8 LapDLink ...................................................................................................................................59 7.3.9 Nse ............................................................................................................................................60 7.3.10 NsVc 60 7.3.11 Pvc 61 7.3.12 RrmP 61 7.3.13 Dynamic description ..................................................................................................................62

7.4 GLM-LRM INTERFACE DESCRIPTION ............................................................................................69 7.4.1 Overview....................................................................................................................................69 7.4.2 LcsBss .......................................................................................................................................69 7.4.3 LcsCell .......................................................................................................................................70 7.4.4 SmlcP ........................................................................................................................................71

7.5 GOM-NS INTERFACE DESCRIPTION...............................................................................................71 7.5.1 Overview....................................................................................................................................71 7.5.2 Nse entity...................................................................................................................................74 7.5.3 NsVc entity.................................................................................................................................75 7.5.4 Pvc entity ...................................................................................................................................78 7.5.5 FrBc entity..................................................................................................................................81

7.6 GAM-BAM INTERFACE DESCRIPTION............................................................................................81 7.6.1 Overview....................................................................................................................................81




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

Evo

lium

.

7.6.2 amP entity..................................................................................................................................81 7.7 SCA-SCA INTERFACE DESCRIPTION.............................................................................................82

7.7.1 Messages description................................................................................................................82 7.8 GEM-SCA INTERFACE DESCRIPTION ............................................................................................84

7.8.1 Managed object (coherent with CS) ..........................................................................................84 7.8.2 Messages ..................................................................................................................................86

7.9 GPM-TPM interface DESCRIPTION ..................................................................................................88 7.9.1 Overview....................................................................................................................................88 7.9.2 PmP entity .................................................................................................................................88 7.9.3 BSC entity..................................................................................................................................94 7.9.4 FrBc entity..................................................................................................................................94 7.9.5 lapDLink entity ...........................................................................................................................95

8 GLOSSARY AND ABBREVIATIONS ........................................................................................................96




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

Evo

lium

.

INTERNAL REFERENCED DOCUMENTS

Not applicable

REFERENCED DOCUMENTS [ 1 ] MFS O&M architecture

3BK 09665 HAAA EBZZA

[ 2 ] MFS GPRS Management Functional Specification 3BK 09722 JAAA DSZZA

[ 3 ] MFS SMLC Management Functional Specification 3BK 29225 HAAA DSZZA

[ 4 ] MFS Internal Interfaces: Data Catalogue 3BK 09721 JAAA PQZZA

RELATED DOCUMENTS [ 5 ] OMC-R/ MFS interface [part 1]: Management Information Model

3BK 11204 0323 DSZZA

[ 6 ] OMC-R/ MFS interface [part 2]: Implementation Profile 3BK 11204 0324 DSZZA

[ 7 ] LMT interface specification 3BK 09589 JAAA DSZZA

[ 8 ] LMT interface specification 3BK 09589 JAAA DSZZA

[ 9 ] MFS/ OMC PM FILE INTERFACE SPECIFICATION 3BK 11204 0325 dszza

PREFACE This document describes the internal interfaces within the MFS CF (Control Function).

Only the messages are defined in this document.

Scenario are described in documents [ 2 ] and [ 3 ]

Parameter and structures used in the messages are described in document [ 4 ].

OPEN POINTS / RESTRICTIONS

None




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

Evo

lium

.

1 SCOPE This document describes the internal interfaces within the MFS CF (Control Function).

This document is valid for the MFS B9, interface Global Managers to B9 Local Managers.

Please, for MFS B9, interface Global Managers to B8 Local Managers, refer to B8 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

Evo

lium

.

2 OVERVIEW

CF

Global Manager Local Manager(1)

(3)(2)

Q3 agent

LMT

(4)

(5)

This document provides a description of interfaces of type

(1): interface between Global Managers and Local Managers: e.g. GOM & TRM, GLM & LRM, GAM & BAM, GEM & BAM, GPM & TPM. These interfaces support exchanges related to the management of GPRS and SMLC services.

(2): interface between Global Managers: e.g. GOM & GAM, GEM & GAM, GOM & GEM, GLM & GEM, GOM & GPM. These interfaces support exchanges related to coordination information between global manager.

Following interfaces are not described in this document: (3): interface between Local Managers: e.g. TRM & BAM

(4): this interface is described only in document [ 5 ] and [ 6 ]

(5): this interface is considered as an external one and is described in document [ 7 ]

The interface (1) between Global Managers and Local Managers (called CML - CoMmunication Layers-) consists of parameters put into structures, embedded into messages related to a class. During the BSS migration (Vn to Vn+1), the O&M of the MFS is able to handle two versions of SW GPU: one for GPU boards in version (Vn), and another in version (Vn+1).

Global Manager(Vn+1)

Local Manager(Vn)

Local Manager(Vn+1)

Msg #1 (Vn)

Msg #2 (Vn+1)




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

Evo

lium

.

3 COMMUNICATION PRINCIPLES BETWEEN GM AND LM

One Global Manager (GM), located on control station, may be either GOM, GLM, GPM, GEM or GAM.

One Local Manager (LM), located on GPU board, may be either TRM, LRM, TPM or BAM

It deals with the following type of exchanges:

• Equipment manager (GEM & GAM) and the Board Manager (BAM).

• Application manager (GOM & GLM & GPM) and the Telecom Application manager (TRM & TPM & LRM),

For the following communication channels (e.g. GOM�TRM, GEM�BAM, GLM-LRM �), messages are sent in a sequential way (one request at a time for each communication channel -ie messages window = 1-)

For the following communication channel (e.g. GPM�TPM), messages are sent in a burst way. At GP expiry, GPM sends the whole set of xx-report-req message to TPM to collect every history data. There is one xx-report-req message per measured class. GPU returns the history data built at the last GP for all instances of the related class in a xx-report-cnf message.

The transaction number element is used for message numbering and to link one request (resp one indication) to one confirmation (resp one response) message. The initiator of one transaction (i.e. GM or LM) is responsible for generating the right transaction number. The responder replies always with the same transaction number (the responder uses the transaction number retrieved in the message emitted by the initiator).

In each way, almost all messages are acknowledged (except for State Change indication). The messages are sent in a sequential way: the next in sequence message is not sent while the acknowledgement of the previous one is not received (per communication channel).

One request message may address several objects, instances of the same class. Therefore, the related acknowledgement message applies to the same set of objects than the request message (i.e. the creation of n instances of a class by one message is acknowledged by one message).

Therefore in case of a communication loss, the non-acknowledged message can be sent again, and no synchronization mechanism is needed (to retrieve the history).

Since state change indications are not confirmed, in case of a loss of communication, a resynchronization is required on object states.

As a basic rule, the Data repository is the Global Manager. Thus, checks are always performed at GM level: parameter value, integrity checks, mandatory rule between parameters... In consequence, the LM always accept an alignment requested by the GM. A message rejected by the LM is considered as a SW bug, and then, GOM performs a reset data of the board.




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

Evo

lium

.

4 GM/ LM PROCEDURES

4.1 Successfull requests

4.1.1 Request transactions (Create, Delete, Set, Lock, Unlock)

GM LM

XXX-req( transaction # y )

XXX-cnf( transaction # y )

GM ensures that only one request is sent at a time (i.e. GM waits for a confirmation coming from LM before sending a second request) for one LM instance.

GM is responsible for generating the right transaction number.

4.1.2 Request transactions (report)

GM LM

XXX-req( transaction # y, class #A )

XXX-cnf( transaction # y, class #A, inst 1 )

XXX-req( transaction # z, class #B )

XXX-cnf( transaction # z, class #B, inst 1 )

GM sends a report-req on a class basis.

GM is responsible for generating the right transaction number.

4.1.3 Synchonization point (end of config request usage).

The synchronization point is used for different usages:

1. The creation of one object may lead to several exchanges of Set messages. The EndOfConfig means that all data are load into the GPU and the related objects can start from a telecom point of view.




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

Evo

lium

.

GM LM

Set-req( transaction # y2, Class , instance) (*)

Set-cnf( transaction # y2, Class, instance) (*)N timesN >= 1

Create-req( transaction # y1, Class , instance)

EndOfConfig-req( transaction # y3, Class, instance)

Create-cnf( transaction # y1, Class , instance)

EndOfConfig-cnf( transaction # y3, Class, instance)

2. The creation of one object may lead to the creation of several contained objects.

GM LM

Create-req( transaction # y2, Class, ObjectId = Tel-ref #z, instance #i) (*)

Create-cnf( transaction # y2, Class, Objectid) (*)N timesN >= 1

Create-req( transaction # y1, Class, ObjectId = Tel-ref #z)

EndOfConfig-req( transaction # y3, Class, ObjectId = Tel-ref #z)

Create-cnf( transaction # y1, Class, ObjectId = Tel-ref #z)

EndOfConfig-cnf( transaction # y3, Class, ObjectId)

4.2 Successfull Indications

4.2.1 State change, EventReport indications

GM LM

XXX-ind( transaction # x)

LM is responsible for generating the right transaction number.




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

Evo

lium

.

4.2.2 Ready, Fault Report indications

GM LM

XXX-ind( transaction # x)

XXX-rsp( transaction # x)

LM is responsible for generating the right transaction number.

4.3 Requests Failure

When an error occurs during the Request message, a NACK FAILURE is returned by the LM to the GM in the confirmation message (see Generic Confirmation message format).

Whatever is the CAUSE of the NACK FAILURE, the GM applies a Reset Data procedure of the GPU.

The differents causes are described in the followin chapters.

4.3.1 ALL REQUESTS cause

Cause Value Description

UnknownRequest 0001H The request is not implemented at GPU side. • HeaderT.classId is not relevant at GPU side • HeaderT.msgType is not relevant at GPU side

ResetLxpu 0100H * * *GOM internal cause * * For pending requests, when the session is lost with the GPU, GOM confirms them with this cause.

Not initialised 0053H TRM is not fully initialised

4.3.2 CREATE REQUEST cause


InvRequest 0000H The BAM couldn�t process the SET request message. This is a software problem that should never occure: the BAM finds the information sent by the GEM is inconsistent. The DebugInfo field will possibly give more detail.

Out of Range 0010H The Bss Reference is out of the authorized range Already exists 0011H An instance was already created with the same Bss

Reference




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

Evo

lium

.

TdmSwitchError 0052H An error has been returned when calling the TDM driver to establish the connection. The DebugInfo field gives the TDM driver error code, as described in the TDM driver interface specification.

PcmPort is locked 0054H The PcmPort given in reference is locked PcmPort Out of Range 0055H The BSS ref of PcmPort is out of the authorized range Unknown NseRef 0060H The Nse given in reference is not configured Unknown BssRef 0061H The Bss given in reference is not configured Unknown LapDBcRef 0062H The LapDBc given in reference is not configured Unknown PvcRef 0063H The Pvc given in reference is not configured Unknown FrBcRef 0064H The LapDBc given in reference is not configured

4.3.3 DELETE REQUEST cause

Cause Value Description InvRequest 0000H The BAM couldn�t process the SET request message.

This is a software problem that should never occure: the BAM finds the information sent by the GEM is inconsistent. The DebugInfo field will possibly give more detail.

Unknown instance 0020H The Bss Reference of the instance is unknown (never created)

Not Locked 0030H The instance is not locked TdmSwitchError 0052H An error has been returned when calling the TDM driver

to program idle patterns on the outgoing mic time slots which where used by this connection. The DebugInfo field gives the TDM driver error code, as described in the TDM driver interface specification.

PcmPort is locked 0054H The PcmPort given in reference is locked Unknown GicBase 0065H The GicBase is not configured LapDLink(s) still exist 0080H LapDLinks exist under this BSS Gsl still exists 0081H Gsl exists under this BSS GchGroups still exist 0082H GchGroups exist under this BSS Cells still exist 0083H Cells exist under this BSS Pvc still exists 0084H Pcv exists for this FrBc Bss stil exists 0085H Bss using this Nse like reference exists Nsvc still exists 0086H NsVc exists under this NsVC LastLapdlink 0087H it is not allowad to delete all lapdLink related to a BSS

by DELETE REQUEST operation. The last one is necesarily deleted via a BSS DELETE REQUEST.




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

Evo

lium

.

4.3.4 SET REQUEST cause


InvRequest 0000H This is a software problem that should never occured: The DebugInfo field will possibly give more detail.

NotAllowedRunTime 0002H It is not allowed to update a RrmP parameters when TRM is fully initialised.


TdmError 0050H (PcmPort-SET-Cnf) An error has been returned when calling the TDM driver. The DebugInfo field gives the TDM driver error code, as described in the TDM driver interface specification.

TdmSwitchError 0052H An error has been returned when calling the TDM driver to program idle patterns on the outgoing mic time slots which where used by this connection. The DebugInfo field gives the TDM driver error code, as described in the TDM driver interface specification.

PcmPort is locked 0054H The PcmPort given in reference is locked Unknown GicBase 0065H The GicBase is not configured Traffic not interrupted 00A0H NsVc not locked

4.3.5 END OF CONFIGURATION REQUEST cause


Unknown Instance 0020H The Bss Reference of the instance is unknown (never created)

LapDLink missing 0070H The LapDLink is not configured Gsl missing 0071H The GSL is not configured GchGroup missing 0072H The GchGroup is not configured NsVc missing 0076H NsVc is not configured Traffic Allowed missing 0090H Traffic allowed is not configured Cell Information Missing 0091H Cell is not configured RrmP Information Missing 0092H RrmP is not configured PAG-ASSIGN missing 0095H BSS is not fully configured PSI2 missing 0098H BSS is not fully configured BssSetMissing 00A5H BSS is not fully configured LxpuStateMissing 00A7H BSS is not fully configured CellMappingMissing 00A8H BSS is not fully configured




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

Evo

lium

.

4.3.6 LOCK REQUEST cause


InvRequest 0000H The BAM couldn�t process the SET request message. This is a software problem that should never occure: the BAM finds the information sent by the GEM is inconsistent. The DebugInfo field will possibly give more detail.


TdmFramerError 0051H An error has been returned when calling the TDM driver to disable interrupt from the framer for that Pcm port. The DebugInfo field gives the TDM driver error code, as described in the TDM driver interface specification.

TdmSwitchError 0052H An error has been returned when calling the TDM driver to program idle pattern on the outgoing mic. The DebugInfo field gives the TDM driver error code, as described in the TDM driver interface specification.

4.3.7 UNLOCK REQUEST cause

Cause Value Description InvRequest 0000H This is a software problem that should never occure.

The DebugInfo field will possibly give more detail. Unknown instance 0020H The Bss Reference of the instance is unknown (never

created) TdmFramerError 0051H An error has been returned when calling the TDM driver

to enable interrupt from the framer for that Pcm port. The DebugInfo field gives the TDM driver error code, as described in the TDM driver interface specification.

4.4 Indications Failure

4.4.1 Generic READY cause

Cause Value Description InvRequest 0000H The BAM couldn�t process the SET request message.

This is a software problem that should never occure: the BAM finds the information sent by the GEM is inconsistent. The DebugInfo field will possibly give more detail.

Invalid logical number 0040H The logical number given by GPU is not valid Invalid Tsap 0041H The Tsap given by GPU is not valid




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

Evo

lium

.

5 OVERALL DESCRIPTION OF CLASS AND MESSAGES

5.1 Interface models

RrmP

GslCell

Bss

11

11**

Nse

NsP

11

NsVc

**

LapDLink1..4

BmP

Cnx

**

GchGroup

**

LapDBc

1

1

1

1

BcmP1..21..2

Pvc**

1

1

1

1

FrBc**

*1 *1

PcmPort

1616 11From

11To

3..4 13..4 1

1

1

1

1

1

1

1

+11

GEM-BAMGOM-RRM

GOM-NSGOM-BCM

TRM

GAM-BAM

AmP

BAM

1

1

*

1

smlcP

lcsBss

lcsCell

*

1

LRM

Figure 1: Global Interface model (Configuration)

PmP

Pvc Bsc lapDLink FrBc* *1 1..4

Cell distCell lcsCell* * *

BTS*

Figure 2: Global Interface model (Performance)




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

Evo

lium

.

5.2 Entity description

5.2.1 AmP entity description

AmP manages all information concerning Alarm Management Parameters.

5.2.2 BmP entity description

Bmp manages all information concerning Board Management Parameters: clock synchronisation rules for a GPU.

The GPU could use several synchronisation sources and there are:

• Input PcmPorts (up to 2)

• RSCB bus

Use Synchrosisation Input Synchronisation source Input

Description Synchronisation Output

(RSCBiA bus)

MFS Input PcmPorts Up to 4 PcmPorts No Ouput

SGSN (Master GPU) Input PcmPorts Up to 4 PcmPorts - RSCB0A output

- RSCB0B Output

- No Ouput

SGSN (Slave GPU using the RSCBiA bus)

RSCBiA bus - RSCB0A

- RSCB1A

No Ouput

Free Run Nothing Nothing Nothing

5.2.3 PcmPort entity description

The PcmPort (Pulse Code Modulation Port) represents the end-point of a 2 Mbps link (trunk) connected to one GPU.

GPU

Applique

PcmPort

PortNB

0

1

15

ExternalPCM Links




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

Evo

lium

.

5.2.4 BcmP entity description

The BcmP represents the Bearer Channel Management Parameters repository.

BcmP manages all information concerning the Bearer Channel Management.

BcmP entity is identified by

- a logical number

- and a physical identifier

Note : The Physical identifier (Tsap) of a BcmP entity is encoded as follows:

8 8 2 6 8

00H FFh Rack

Subrack Slot

5.2.5 LapDBc entity description

A LapDBc (Lap D Bearer Channel) is a nx64 Kbps circuit/channel. It represents a physical link between the BSC and the MFS used to carry signalling.

Note: n = 1 up to Step 1

5.2.6 FrBc entity description

A FrBc (Frame Relay Bearer Channel) is a nx64 Kbps circuit/channel. It represents a physical link between the MFS and the SGSN used to carry signalling and traffic.

5.2.7 RrmP entity description

RrmP manages all information concerning Bss and Radio Resource Management for GPRS

5.2.8 smlcP entity description

smlcP manages all information concerning Bss and Cell Management for LCS

5.2.9 Bss, lcsBss entities description

Bss (& lcsBss) provides the radio access to mobile stations in a limited geographical area. There is one or more BSS per GRS. It is defined as a collection of one or several Cells (supported by one BTS/BTS) controlled by a single BSC and a single 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

Evo

lium

.

5.2.10 Cell (+DistCell) entity description

A cell defines a limited geographical area where the GPRS service is allowed.

Note that the distCell entity is defined at GPM/ TPM interface to support the distribution counters, in term of telecom entity distCell is equivalent to cell.

5.2.11 lcsCell entity description

A lcsCell defines a limited geographical area where the LCS service is allowed.

5.2.12 GchGroup entity description

The GchGroup represents a set of GCHs carried by an Ater link issued from the BSC and which is multiplexed on a Ater Mux link.

A GCH (GPRS Channel) is a 16 Kbps circuit, between one BSC and one MFS, which can be used for GPRS traffic.

The BSC identifies one Gch towards the MFS by using the following identification:

• a PCM identifier (Ater PCM) also called GicBase

• and a timeslot identifier (64 Kps circuit).

On the MFS side, the same Gch is identified by a different way (internal). Hereafter, they are described:

• a PcmPort identifier

• a timeslot identifier

• a nibble identifer (16 Kps circuit)

During the communication (using Gsl), the MFS translates the internal identification into the corresponding GPRS channel identification: GIC = GicBase + TsNb.

5.2.13 Gsl entity description

A GSL (GPRS Signaling Link) is a signaling link between the MFS and the BSC (Base Station Controller). It is composed of two 64 Kbps LAPD links (over 2 different PCM) which are used in load sharing.

The GPU does not control the 2 LapDlinks are on different PcmPorts.

5.2.14 LapDLink entity description

A LapDLink is a data link between two equipment mapped on a bearer channel (64 Kbps link).

5.2.15 NsP entity description

NsP manages all information concerning Network Service.




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

Evo

lium

.

5.2.16 Nse entity description

Network Service Entity represents, on Gb interface, GPRS traffic associated to a couple GPU-BSS. It groups together all NS-VCs which provide communication between the same peer NS entities. This grouping has end-to-end significance across Gb interface. NSE is defined as the connection of one BSS to a GPU.

5.2.17 NsVc entity description

A NsVc (Network Service Virtual Connection) is an end-to-end virtual connection between the BSS and SGSN.

5.2.18 Pvc entity description

A PVC is a frame relay Permanent Virtual Connection mapped on a bearer channel on Gb interface.

5.2.19 Cnx entity description

A Cnx represents a cross connection between two PcmPort instances of a GPU.




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

Evo

lium

.

5.3 State

Class Administrative State Operational State

GEM � BAM interface BmP

PcmPort X X OpeState = Not LOS CrossConnection (Cnx)

GOM � BCM interface BcmP

LapDBc FrBc

GLM � SMLC interface smlcP lcsBss lcsCell

GOM � RRM interface RrmP Bss X X Cell X X

GchGroup Gsl X OpeState =

combinaison of up to 2 LapD link OpeState

LapDLink X X GOM � NS interface

NsP Nse

NsVc X X Pvc X FrBc X

5.4 Reference

GEM � BAM Interface

Class OmRef BssRef

Name Range Name Range

BmP OmBmPRef BmPRef 0

PcmPort OmPcmPortRef PcmPortRef 0..15

Cnx OmCnxRef CnxRef 0..7




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

Evo

lium

.

GAM � BAM Interface

AmP OmAmPRef AmPRef 0

PcmPort OmPcmPortRef PcmPortRef 0..15

GOM � BCM Interface

BcmP OmBcmPRef BcmPRef 0

LapDBc OmLapDBcRef LapDBcRef 0..7

FrBc OmFrBcRef FrBcRef 0..127 (1)

GOM � RRM Interface

RrmP OmRrmP RrmP 0

Bss OmBssRef BssRef 0

Cell OmCellRef CellRef 0..263

GchGroup OmGchGroupRef GchGroupRef 0..31 (MFS)

0..55 (MFS EVOLUTION)

Gsl OmGslRef GslRef 0

LapDLink OmLapDLinkRef LapDLinkRef 0..7 (MFS)

0..13 (MFS EVOLUTION)

GOM � NS Interface

NsP OmNsPRef NsPRef 0

Nse OmNseRef NseRef 0

NsVc OmNsVcRef NsVcRef 0.. (1)

Pvc OmPvcRef PvcRef 0.. (1)

FrBc OmFBcRef FrBcRef 0.. 127(1)

GPM � PM Interface

PmP OmPmPRef PmPRef 0

Bsc OmBssPmRef BssPmRef 0

lcsBsc OmBssPmRef BssRef 0

Cell OmCellPmRef CellPmRef 0

Cell OmCellRef CellRef 0..263

lcsCell OmCellRef CellRef 0..263

distCell OmCellRef CellRef 0..263

Pvc OmPvcPmRef PvcPmRef 0

FrBc OmFrBcPmRef FrBcPmRef 0

LapDLink OmLapDlinkPmRef LapDLinkPmRef 0

Note: a Gpu can not support more than 128 bearer channels (Hardware limit of the HDLC component). Then, FrBc instances + LapDBc instances <= 128.

(1) : MFS maximum configuration values : FrBcRef=127, PvcRef=127, NsVcRef=127 (1PVC per bearer channel)

(2) 3BKA20CBR163136 MFS EVOLUTION ONLY. With BSC EVOLUTION introduction, 14 E1 can be configured for Ater. Regarding GchGroup, 4:1 multiplexing scheme only is supported.




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

Evo

lium

.

5.5 Messages list

5.5.1 SCA-SCA Interface

The following list doesn�t respect the message format describe in clause 2.4.

Message name Type Semantic Version

R

e

q

I

n

d

R

s

p

C

n

f

SCA � SCA Interface

FAPI STATE CHANGE REQUEST Ask the state of an ifap (Normally local to

the destinator ).

FAPI STATE CHANGE RESPONSE

Give the state of an ifap (Normally localized on the originator).

FAPI STATE CHANGE INDIC Indicate a change of state of an ifap local to the originator.

5.5.2 GEM-SCA Interface

The following list doesn�t respect the message format describe in clause 2.4.


R

e

q

I

n

d

R

s

p

C

n

f

GEM � SCA Interface

GEM_GPU_FAP_REQ Declare a FAP on GPU GEM_GPU_FAP_REP Accept the FAP declaration GEM_GPU_IFAP_REQ Declare an IFAP on the GPU GEM_GPU_IFAP_REP Accept the IFAP declaration GEM_CONF_INSTALL_REQ Declare a �Local port� on the GPU GEM_CONF_INSTALL_REP Accept the �Local port� declaration




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

Evo

lium

.

5.5.3 GEM-BAM interface


R

e

q

I

n

d

R

s

p

C

n

f

GEM � BAM Interface

BcmP READY X X To indicate the availability SET X X To set the synchronisation Input and Ouput

sources

END-OF-CONFIG X X To indicate the end of configuration PcmPort

SET X X To give the PcmPort configuration UNLOCK X X To put in service the PcmPort LOCK X X To put out of service the PcmPort STATE-CHANGE X To report the states change of the PcmPort END-OF-CONFIG X X To indicate the end of configuration

CrossConnection (Cnx) CREATE X X To create a cross connection between

Timeslots carrying the voice.

DELETE X X To delete/remove a cross connection SET X X To modify a cross connection

5.5.4 GAM-BAM interface


R

e

q

I

n

d

R

s

p

C

n

f

GAM � BAM Interface

BmP READY X X




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

Evo

lium

.

5.5.5 GOM-BCM interface


R

e

q

I

n

d

R

s

p

C

n

f

GOM � BCM Interface

BcmP READY X X To indicate the avaibility END-OF-CFG X X To indicate the end of configuration END-OF-SYNCHRO X X To indicate the end of synchro

LapDBc CREATE X X To create a Lap D Bearer channel (on a

given PcmPort) carrying the Lap D link

DELETE X X To remove the Lap D Bc SET X X To modify the Lap D Bc on a given

PcmPort (increase/decrease the Timeslot numbers)

Not used

FrBc CREATE X X To create a Frame Relay bearer (on a

given PcmPort) channel carrying PVCs

DELETE X X To delete/erase the FrBc SET X X To increase/decrease the timeslot number

on the PcmPort

5.5.6 GOM-RRM interface


R

e

q

I

n

d

R

s

p

C

n

f

GOM � RRM Interface

RrmP READY X X To raise the availability END-OF-SYNCHRO X X To indicate the end of Synchro SET X X To set the parameters




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

Evo

lium

.

Bss VERSION X To raise the BSS version change CREATE X X To create a Bss DELETE X X To remove a Bss END-OF-CFG X X To indicate the end of configuration LOCK X X To lock the Bss (to put out of service).

A shutdown can be requested to smoothly put out of service (new incoming/outgoing calls are rejected)

UNLOCK X X To unlock the Bss (to put in service STATE-CHANGE X To raise the state change SET X X To set BSS configuration SET-LXPU-STATUS X X SET-PAGING-AREA-MAIN X X SET-CELL-MAPPING X X SET-BSSGP X X To set the parameters related to

BSSGP interface

Cell CREATE X X To create a cell DELETE X X To delete a cell END-OF-CFG X X To indicate the end of configuration LOCK X X To lock the cell (to put out of service) A

shutdown can be requested to smoothly put out of service (new incoming/outgoing calls are rejected)

UNLOCK X X To unlock the cell (to put in service the cell)

STATE-CHANGE X To raise the states change SET X X To set the parameters SET-BVCI-MAPPING X X to map the cell-Gb onto a LXPU

GchGroup CREATE X X To create a GchGroup DELETE X X To delete a GchGroup SET X X To modify a GchGroup

(increase/decrease the number of Gch in the targetted PcmPort)

Gsl CREATE X X To create a GPRS signalling link DELETE X X To delete a Gsl STATE-CHANGE X To indicate a states change

LapDLink CREATE X X To create a Lap D link




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

Evo

lium

.

DELETE X X To delete a Lap D link LOCK X X To lock the Lap D link (to put out of

service)

UNLOCK X X To unlock the Lap D link (to put in service)

STATE-CHANGE X To indicate the states change

5.5.7 GOM-NS interface


R

e

q

I

n

d

R

s

p

C

n

f

NsP

READY X X To report the NsP is operational for configuration

SET X X To set configuration on a NsP instance END-OF-CFG X X to indicate the GPU the end of the

NsP�s configuration only for SGSN

END-OF-SYNCHRO X X To to indicate the Control Station the end of Synchronisation

Nse CREATE X X To create a Network Service Entity DELETE X X To delete a Network Service Entity END-OF-CFG X X to indicate the GPU the end of the

Nse�s configuration

Pvc CREATE X X To create a Permanent Virtual

Connection

DELETE X X To delete a Permanent Virtual Connection

STATE-CHANGE X To report the change of a Permanent Virtual Connection state

SET X X NsVc

CREATE X X To create a Network Service Virtual Connection

DELETE X X To delete a Network Service Virtual Connection

LOCK X X To lock (put out of service) a Network Service Virtual Connection




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

Evo

lium

.

UNLOCK X X To unlock (put in service) a Network Service Virtual Connection

STATE-CHANGE X To report the change of a Network Service Virtual Connection

SET X X To modify a Network Service Virtual Connection

FrBc

STATE-CHANGE X To report the change of a FR Bearer

Channel state

5.5.8 GLM-LRM interface


R

e

q

I

n

d

R

s

p

C

n

f

GLM � LRM Interface

smlcP READY X X To raise the availability SET X X To set SMLC configuration END OF SYNCHRO X X X

lcsBss CREATE X X To create a Bss for LCS SET X X To set BSS configuration for LCS VERSION X To raise the BSSLP version change

lcsCell CREATE X X To create a cell for LCS SET X X To set cell configuration for LCS DELETE X X




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

Evo

lium

.

5.5.9 GPM-TPM interface


R

e

q

I

n

d

R

s

p

C

n

f

GPM � TPM Interface

PmP READY X X To report the PM is operational for

configuration

SET X X To set configuration on PM

This message gives Granularity Period and the start-time of observation on a PmP instance.

When the GPU receives this message, PmP is initialized.

REPORT X X To report the observation for all the cell, distCell and lcsCell instances

Pvc REPORT X X to report observation for all the Pvc

instances.

FrBc REPORT X X to report observation for all the FrBc

instances.

LapD REPORT X X to report observation for all the LapD

instances.

Bsc REPORT X X to report observation for all the Bsc

instances.




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

Evo

lium

.

6 MESSAGES CONTENTS

The message has the same format whatever the GPU release .

Each message shall be described using the XDR format which allow the portability and solve the problem of the conversion (little endian to big endian).

XDR is a standard for the description and encoding data. XDR uses a language to describe data formats.

The description of data formats is contained in a file (.x) which is compiled using rpcgen tool. Rpcgen produces two files:

! A header file (.h) containing the C structure of messages

! A source file (.c) contained the filters and functions/procedures to be used to encode/decode and access to the message content.

Note: the use of �variable length array� XDR type is forbidden, because DIGITAL does not support it.

The message consists of 2 parts:

! A header including all information elements necessary to route the message.

! An application data. An Application Data is making of a set of Data Elements. It may include also a filler, used for linked replies (confirmation). A data element layout depends on the couple (Class, message type)

v

HEADERDATA ELEMENT #1 DATA ELEMENT #2 DATA ELEMENT #3

APPLICATION DATA

.............. FILLER

GPM/ TPM: reportCnf

A specific header including the begin and end collection time which are the same for all cells. This part is present for message where the data element is a ReportCnf.

Due to the limitation at GPM side (reception buffer = 100 000 bytes, CS segmentation), all Cells may not be filled into one reportCnf message. So, reporting will be done by sending a set of messages. Note that there is no filler. TPM sends reportCnf message for a set of cells, and send as many message as required. GPM is waiting reportCnf during a GPmin period. All coming message are handled as they come. v

HEADERDATA ELEMENT #1 DATA ELEMENT #2

APPLICATION DATA

..............SPECIFIC HEADER




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

Evo

lium

.

6.1 Header

Parameter Semantic Coding Type

Header (12 bytes)

Class Class Identifier unsigned short

MsgType Message Type unsigned short

RequestId Request Identifier u_int

Nb Number of Data Element 1..N u_int

6.1.1 Class

Coding Class

GEM � BAM interface 0000H BmP 0001H PcmPort 0002H Cnx(CrossConnection)

GOM � BCM interface 0100H BcmP 0101H LapDBc 0102H FrBc

GLM � SMLC interface 0900H smlcP 0901H lcsBss 0902H lcsCell

GOM � RRM interface 0200H RrmP 0201H Bss 0202H Cell 0203H GchGroup 0204H Gsl 0205H LapDLink

GOM � NS interface 0300H NsP 0301H Nse 0302H NsVc 0303H Pvc

GAM � BAM interface 0400H AmP 0FFFH Extension

GPM - PM interface 0700H PmP 0102H FrBc 0201H Bss 0205H LapDLink 0303H Pvc




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

Evo

lium

.

6.1.2 msgType

A msgType is the combination (logical OR) of an operation and a direction.

DirectionO p e r a t i o n

31.....24........16........8.........0

Direction

Coding Direction

XXX0H Req (Request)

XXX1H Cnf (Confirmation)

XXX2H Ind (Indication)

XXX3H Rsp (Response)

Operation

MsgValue MsgType

0x0002 ReadyInd

0x0003 ReadyRsp

0x0010 SetReq

0x0011 SetCnf

0x0020 UnlockReq

0x0021 UnlockCnf

0x0030 LockReq

0x0031 LockCnf

0x0040 EndOfCfgReq

0x0041 EndOfCfgCnf

0x0062 StateChangeInd

0x0070 CreateReq

0x0071 CreateCnf

0x0080 DeleteReq

0x0081 DeleteCnf

0x00B0 ReportReq

0x00B1 ReportCnf

0x00C0 EndOfSynchroReq




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

Evo

lium

.

MsgValue MsgType

0x00C1 EndOfSynchroCnf

0x00C2 EndOfSynchroInd

0x00C3 EndOfSynchroRsp

0x00D2 VersionInd

0x00E0 SetBvciMappingReq

0x00E1 SetBvciMappingCnf

0x00F2 AlarmReportInd

0x00F3 AlarmReportRsp

0x0100 StopAlarmsSynchroReq

0x0101 StopAlarmsSynchroCnf

0x0110 StartAlarmsSynchroReq

0x0111 StartAlarmsSynchroCnf

0x0120 SetBssGpReq

0x0121 SetBssGpCnf

0x0280 SetPagingAreaMainReq

0x0281 SetPagingAreaMainCnf

0x0290 SetCellMappingReq

0x0291 SetCellMappingCnf

0x02F0 SetLxpuStatusReq

0x02F1 SetLxpuStatusCnf

0x0340 SetB8Req

0x0341 SetB8Cnf

6.1.3 Request identifier

The request identifier is a transaction number that is used for message numbering and to link one request (resp one indication) to one confirmation (resp one response) message.

The initiator of one transaction (i.e. GM or LM) is responsible for generating the right transaction number.

The responder replies always with the same transaction number (the responder uses the transaction number retrieved in the message emitted by the initiator).

6.1.4 Data Element layout

The set of Data Element are making the Application Data.

A Data Element is defined for each meassage type:




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

Evo

lium

.

6.1.4.1 Ready Indication

Init Information

6.1.4.2 Ready Response

AckContent

6.1.4.3 Set/Create Request

IE #1

Object Identifier #n

Object description

6.1.4.4 Lock/ Unlock Request

Object Identifier #1Result description per object

6.1.4.5 Delete Request


6.1.4.6 End-of-Cfg Request


6.1.4.7 Report Request (Generic)

IE #1


Object description




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

Evo

lium

.

6.1.4.8 Report Request (Class basis)


6.1.4.9 Report Confirmation

IE #1


Object description

6.1.4.10 Lock/ Unlock Confirm

AckContent

Object Identifier #1

Result description per object

6.1.4.11 Create Confirm

AckContent



6.1.4.12 Set Confirm

AckContent



6.1.4.13 Delete Confirm

AckContent






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

Evo

lium

.

6.1.4.14 End-of-Cfg Confirm

AckContent



6.1.4.15 State Change Indication

OamState


6.1.4.16 Event Report Indication

Event description


6.1.4.17 Fault Report Indication

Fault description


6.2 Application Data

By software (emission/ reception buffer), there is a limitation of the message length.

Regarding the current release, the maximum size of a data element is about 5500 bytes. As the maximum buffer size at GPU is XXXX. Then, the Application data can consist of up to 5 Data Elements.

DataElement Naming rule:

<class id><message Type><operation>DataElement




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

Evo

lium

.

6.2.1 Generic Format

The general format that applies to the following requests:

! LOCK REQUEST

! UNLOCK REQUEST

! DELETE REQUEST

! END OF CONFIG REQUEST

! REPORT REQUEST (When class basis)


DataElement

OmRef see 5.4 u_int

BssRef see 5.4 u_int

6.2.2 Generic Confirmation/ Response format

The general format is applied for a response or a confirmation command. The data element consists in the AckContent structure.

The Application data can consist of several Data Elements.


DataElement

OmRef see 5.4 u_int


AckContent

AckNack Result of the Request 00h = Ack (Success), 01h = Nack (Failure) u_int

Cause Cause of the refusal / failure u_int

DebugInfo Debug Information u_int

6.2.3 Confirmation reportCnf format

6.2.3.1 specific header: PmHeader


PmHeader (8bytes)

BeginColTime Begin Collection Time

GMT, number of seconds since the 1st of Jan 1970

0..n u_int

EndColTime End Collection Time

GMT, number of seconds since the 1st of Jan 1970

0..n u_int

Whatever is the release of the GPU, the same specific header format is implemented. No differences at all.




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

Evo

lium

.

6.2.3.2 Data Element

DataElement: class based Message (see GPM/ TPM chapter)

DataElement (*)


XXXXXReportCnf[ max size ] an array of instances.

Each instancereport a list of counters with a max size.

EndOfInfo Filler to report more than max size instances.

DataElement: Generic Message (see GPM/ TPM chapter)

DataElement (*)


class header report class identifier, number of counters, number of instances

body report List of instance, counters results

EndOfInfo not used

6.2.4 Generic Fault report indication format

The number of data element is always 1.

Generic format for fault report indication is as follows:


DataElement

OmRef see 5.4 u_int


Alarm Id Alarm identifier. 1..1000h: Tomas (alarmId = Probable cause = enum) 1001..2000h: GEM/Jbeti layer 2001..3000h: SGSN 3001..4000h: GOM 4001..5000h: BAM

9001..A000h: RRM

C001..D000h: GLM

E001..F000h: SMLC

u_int

Validity Cleared or not Cleared Enum u_int

Date GMT, number of seconds since the 1st of Jan 1970 0..n u_int

Rack Rack number. 1..2 (1) U_int

Subrack Subrack number 0..3(1) U_int




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

Evo

lium

.

Slot Slot number 4..23 if used

FFFFh if not used (1)

Component 1 Additionnal fault source identifier 0..n or FFFFh if not applicable

U_int

U_int

Component 2 Additionnal fault source identifier 0..n or FFFFh if not applicable U_int

Tsap GPU tomas physical address 0..n or FFFFh (JBETI alarm) U_int

(1): �FFFF� can be used by GOM when it generates an alarm.

Special case: AlarmId = FFFFH and Validity = Cleared : this case corresponds to a �Clear MFS event� message which clears all the current alarms associated to the objet (Omref)

! MFS A GPU can be located in one of the 16 possible slots but there are up to 11 GPUs in the subrack (power limitation).

6.2.5 Generic fault report response format

Generic format for fault report response is as follows:


DataElement

OmRef see 5.4 u_int


Optional data depends on the Request/Indication command

AckContent

AckNack Result of the request 00h = Ack, 01h = Nack u_int

Cause Cause of the refusal / failure 00h : No failure

01h : DM table full

02h : MFS_EVENT already exists

03h : CONF_ALARM associated not found

04h : REF_ALARM associated not found

05h : MFS_EVENT associated not found

06h : other failure

u_int





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

Evo

lium

.

6.3 DIMENSIONING

Header = 12 bytes

Itf Class Message size of ONE dataElement

(in bytes) Nb of DE

Max size of the msg

Bss CreateReq 56 5(1) 292 Cell CreateReq 46 5(1) 242 Cnx CreateReq 20 5(1) 100 FrBc CreateReq 16 5(1) 92 GchGroup CreateReq 204 5(1) 1032 Gsl CreateReq 12 5(1) 72 LapDBc CreateReq 14 5(1) 82 LapDLink CreateReq 24 5(1) 132 LcsBss CreateReq 38 5(1) 202 LcsCell CreateReq 64 5(1) 332 Nse CreateReq 10 5(1) 62 NsVc CreateReq 40 5(1) 212 Pvc CreateReq 46 5(1) 242 Bss DeleteReq 8 1 20 Cell DeleteReq 8 1 20 Cnx DeleteReq 8 1 20 FrBc DeleteReq 8 1 20 GchGroup DeleteReq 8 1 20 Gsl DeleteReq 8 1 20 LapDBc DeleteReq 8 1 20 LapDLink DeleteReq 8 1 20 LcsCell DeleteReq 8 1 20 Nse DeleteReq 8 1 20 NsVc DeleteReq 8 1 20 Pvc DeleteReq 8 1 20 Bss EndOfCfgReq 8 1 20 Cell EndOfCfgReq 8 1 20 Nse EndOfCfgReq 8 1 20 NsP EndOfCfgReq 8 1 20 PcmPort EndOfCfgReq 8 1 20 SmlcP EndOfSynchroReq 8 1 20 Bss LockReq 8 1 20 Cell LockReq 8 1 20 LapDLink LockReq 8 1 20 NsVc LockReq 8 1 20 PcmPort LockReq 8 1 20 Bss ReportReq 8 1 20 FrBc ReportReq 8 1 20 LapDLink ReportReq 8 1 20 PmP ReportReq 20 1 32 Pvc ReportReq 8 1 20 NsP SetB8Req 26 5(1) 142 NsP SetB8Req 40 5(1) 212 Cell SetBvciMappingReq 16 5(1) 92 Bss SetCellMappingReq 3172 5(1) 15872 Bss SetLxpuStatusReq 230 5(1) 1162 Bss SetPagingAreaMainReq 1588 5(1) 7952 Bss SetPagingAreaMainReq 1060 5(1) 5312 Bss SetReq 640 5(1) 3212 Cell SetReq 5430 5(1) 27162 Cnx SetReq 20 5(1) 112 FrBc SetReq 8 5(1) 52 GchGroup SetReq 196 5(1) 992 Gsl SetReq 4 5(1) 32 LapDBc SetReq 6 5(1) 42 LcsBss SetReq 30 5(1) 162




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

Evo

lium

.

LcsCell SetReq 64 5(1) 332 NsVc SetReq 40 5(1) 212 PcmPort SetReq 28 5(1) 152 PmP SetReq 16 5(1) 92 Pvc SetReq 46 5(1) 242 RrmP SetReq 170 5(1) 862 SmlcP SetReq 58 5(1) 302 Bss UnlockReq 8 1 20 Cell UnlockReq 8 1 20 LapDLink UnlockReq 8 1 20 NsVc UnlockReq 8 1 20 PcmPort UnlockReq 8 1 20

note (1): GPU limitation. Was 10 at GOM in 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

Evo

lium

.

7 DETAILED INTERFACES DESCRIPTION

7.1 GEM-BAM INTERFACE DESCRIPTION

7.1.1 Overview

There are three entities managed at this interface: BmP (Board Management Parameter), PcmPort and Cnx(CrossConnection).

7.1.2 BmP entity

7.1.2.1 Interface structure description

The BmP parameter groups are classified into 1 functional area:

• BmP Synchronisation configuration




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

Evo

lium

.

7.1.2.2 Messages description

7.1.2.2.1 BmP-READY-ind

This message is used to report the Control station the BamP is operational for configuration.

. Message type: BmP-READY-ind Direction: GPU to Control Station


Header

BmPReadyIndDataElement

OmRef (1) OmBmPRef U_int

BssRef (1) BmPRef U_int

BmPReadyIndContent

InitStatus Initialisation status 0 = not initialised

1 = initialised

U_int

LogicalNumber

Tsap U_int

(1) These parameters are set to NIL.

7.1.2.2.2 BmP-READY-rsp

This message is used to confirm that the Control Station is ready as well.

. Message type: BmP-READY-rsp Direction: Control Station to GPU

This message is generic. Please, refer to 6.2.1 Generic Confirmation/Response format

7.1.2.2.3 BmP-SET-req

This message is used to set configuration on a BmP instance. Message type: BmP-SET-req Direction: Control Station to GPU.


Header

BmPSetReqDataElement

OmRef OmBmPRef U_int

BssRef BmPRef U_int

BmPSetReqContent

LogicalNumber U_int

BmPSynchroCfg BmP Configuration structure (**)

(**) SynchroOut attribute is encoded as follows: 0:RSCB0, 1:RSCB1, FFH:None




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

Evo

lium

.

7.1.2.2.4 BmP-SET-cnf

This message is used to confirm a set of BmP on an objet instance. Message type: BmP-SET-cnf Direction: GPU to Control Station.


7.1.2.2.5 BmP-END-OF-CFG-req

This message is used to indicate the GPU the end of the BmP�s configuration. Message type:

BmP-END-OF-CFG-req Direction: Control Station to GPU


Header

BmPEndOfCfgReqDataElement

OmRef OmBmPRef u_int

BssRef BmPRef u_int

BmPEndOfCfgContent

ProtectedBoard Back panel slot of the protected board

Relevant only for spare board

2..17 U_int

7.1.2.2.6 BmP-END-OF-CFG-cnf

This message is used to confirm the end of BmP�s configuration. Message type: BmP-END-OF-CFG-cnf Direction: GPU to Control Station


7.1.3 PcmPort entity

7.1.3.1 PcmPort structures description

The PcmPort parameter groups are classified into functional areas:

• PcmPort configuration

• PcmPort state.

These parameter groups are described in [14].




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

Evo

lium

.

7.1.3.2 PcmPort messages description

7.1.3.2.1 PcmPort-SET-req

This message is used to set attributes in the PcmPort. Message type: PcmPort-SET-req Direction: Control Station to GPU.


Header

PcmPortSetReqDataElement

OmRef OmPcmPortRef (1) u_int

BssRef PcmPortRef (1) u_int

PcmPortSetReqContent

PcmPortCfg PcmPort Configuration structure (*)

(1): set by GEM

7.1.3.2.2 PcmPort-SET-cnf

This message is used to confirm the setting of attributes in a PcmPort. Message type: PcmPort-SET-cnf Direction: GPU to Control Station.


7.1.3.2.3 PcmPort-LOCK-req

This message is used to ask to lock the PcmPort.

Message type: PcmPort-LOCK-req Direction: Control Station to GPU

REPORTING: the lock of a PcmPort leads to the deletion of any cross-connection implicating this PcmPort in the GPU matrix, so that when the pcmPort is set unlocked, cross-connection creation requests should be send to the GPU.


Header

PcmPortLockReqDataElement

OmRef OmPcmPortRef (1) u_int

BssRef PcmPortRef (1) u_int

(1): set by GEM




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

Evo

lium

.

7.1.3.2.4 PcmPort-LOCK-cnf

This message is used to confirm the lock of the PcmPort. Message type: PcmPort-LOCK-cnf Direction: GPU to Control Station


7.1.3.2.5 PcmPort-UNLOCK-req

This message is used to ask to unlock the PcmPort. Message type: PcmPort-UNLOCK-req Direction: Control Station to GPU


Header

PcmPortUnlockReqDataElement

OmRef OmPcmPortRef (1) U_int

BssRef PcmPortRef (1) U_int

(1) set by GEM

7.1.3.2.6 PcmPort-UNLOCK-cnf

This message is used to confirm the lock of the PcmPort. Message type: PcmPort-UNLOCK-cnf Direction: GPU to Control Station


7.1.3.2.7 PcmPort-STATE-CHANGE-ind

This message is used to report the Control station the PcmPort state changed. Message type: Pcm-STATE-CHANGE-ind Direction: GPU to Control Station


Header

PcmPortStateChangeIndDataElement

OmRef OmPcmPortRef u_int

BssRef PcmPortRef u_int

PcmStateChangeIndContent

PcmPortState PcmPort State structure




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

Evo

lium

.

7.1.3.2.8 PcmPort-END-OF-CFG-req

This message is used to indicate the GPU the end of the PcmPort�s configuration. Message type: PcmPort-END-OF-CFG-req Direction: Control Station to GPU


Header

PcmPortEndOfCfgReqDataElement

OmRef OmPcmPortPRef u_int

BssRef PcmPortRef u_int

7.1.3.2.9 PcmPort-END-OF-CFG-cnf

This message is used to confirm the end of PcmPort�s configuration. Message type: PcmPort-END-OF-CFG-cnf Direction: GPU to Control Station


7.1.4 Cnx entity

7.1.4.1 Cnx entity description

A Cross Connection represents the connections between 2 physical trunks: nx(64 Kbps to 64Kps) connections.

TS0

TS1

TS2

TS3

TS4

�

TS29

TS30

TS31

TS0

TS1

TS2

TS3

TS4

�

TS29

TS30

TS31

TS5 TS5

Never cross connected

CrossConnection

TSx is connected to TSx

TSx is never connected to TSyWhere x different of y




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

Evo

lium

.

7.1.4.2 Cnx structures description

The CrossConnection parameter groups are classified into functional area:

• CNX configuration .

7.1.4.3 Cnx messages description

7.1.4.3.1 Cnx-CREATE-req

This message is used to create a CrossConnection. Message type: CNX-CREATE-req Direction: Control Station to GPU


Header

CnxCreateReqDataElement

OmRef OmCnxRef u_int

BssRef CnxRef u_int

CnxCreateReqContent

CnxCfg CrossConnection Configuration structure

7.1.4.3.2 Cnx-CREATE-cnf

This message is used to confirm the Cnx creation. Message type: Cnx-CREATE-cnf Direction: GPU to Control Station


7.1.4.3.3 Cnx-DELETE-req

This message is used to delete a Cnx. Message type: Cnx-DELETE-req Direction: Control Station to GPU


Header

CnxDeleteReqDataElement


BssRef CnxRef u_int

CnxDeleteReqContent

CnxCfg CrossConnection Configuration structure (*)




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

Evo

lium

.

7.1.4.3.4 Cnx-DELETE-cnf

This message is used to confirm the Cnx deletion. Message type: Cnx-DELETE-cnf Direction: GPU to Control Station


7.1.4.3.5 Cnx-SET-req

This message is used to set attributes in the Cnx Message type: Cnx-SET-req Direction: Control Station to GPU.


Header

CnxSetReqDataElement


BssRef CnxRef u_int

CnxSetReqContent

CnxCfg Cnx Configuration structure (*)

7.1.4.3.6 Cnx-SET-cnf

This message is used to confirm the setting of attributes in a Cnx Message type: Cnx-SET-cnf Direction: GPU to Control Station.


7.2 GOM-BCM INTERFACE DESCRIPTION

7.2.1 Overview

There are several entities managed at this interface: BcmP (Bearer Management Parameter), LapDBearerChannel, FrameRelayBearerChannel.

7.2.2 BcmP entity

7.2.2.1 BcmP structures description

None




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

Evo

lium

.

7.2.2.2 BcmP messages description

7.2.2.2.1 BcmP-READY-ind

This message is used to report the Control station the BcmP is operational for configuration.

. Message type: BcmP-READY-ind Direction: GPU to Control Station


Header

BcmPReadyIndDataElement

OmRef OmBcmPRef U_int

BssRef BcmPRef U_int

BcmPReadyIndContent


1 = initialised

U_int

LogicalNumber 0..21 U_int

Tsap (1) U_int

(1) Described in the § 5.2.4

7.2.2.2.2 BcmP-READY-rsp

This message is used to confirm the Control Station is ready as well.

Message type: BcmP-READY-rsp Direction: Control Station to GPU


Header

BcmPReadyRspDataElement



BcmPReadyRspContent

StateRequest Request of current states of all object instances of Bcm 0 = No

1 = Yes

U_int

AckContent

AckNack Result of the Request 00h = Ack (Success), 01h = Nack (Failure)

U_int

Cause Cause of the refusal / failure U_int

DebugInfo Debug Information U_int




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

Evo

lium

.

7.2.2.2.3 BcmP-END-OF-CFG-req

This message is sent to indicate the end of the BCM initialisation step. Message type: BcmP-END-OF-CFG-req Direction: Control Station to GPU


Header

BcmPEndOfCfgReqDataElement



7.2.2.2.4 BcmP-END-OF-CFG-cnf

This message is sent to confirm the end of the BCM initialisation step.

Message type: BcmP-END-OF-CFG-req Direction: GPU to Control Station


7.2.2.2.5 BcmP-END-OF-SYNCHRO-IND

This message is used to indicate the Control Station the end of the BcmP�s synchronisation. Message type:

BcmP-END-OF-SYNCHRO-IND Direction: GPU to Control Station


Header

BcmPEndOfSyncIndDataElement

OmRef OmBcmPRef u_int

BssRef BcmPRef u_int

7.2.2.2.6 BcmP-END-OF-SYNCHRO-RSP

This message is used to respond to the end of BcmP�s synchronisation indication. Message type: BcmP-END-OF-SYNCHRO-RSP Direction: Control Station to GPU





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

Evo

lium

.

7.2.3 LapDBc entity

7.2.3.1 LapDBc structures description

The LapDBc parameters are classified into one functional areas:

• LapDBc configuration.

Refer to [14] for LapDBc configuration description.

7.2.3.2 LapDBC messages description

7.2.3.2.1 LapDBc-CREATE-req

This message is used to create a LapD Bearer Channel Message type: LapDBc-CREATE-req Direction: Control Station to GPU


Header

LapDBcCreateReqDataElement

OmRef OmLapDBcRef u_int

BssRef LapDBcRef u_int

LapDBcCreateReqContent

LapDBcCfg LapDBc Configuration structure (*)

7.2.3.2.2 LapDBc-CREATE-cnf

This message is used to confirm the LapDBc creation. Message type: LapDBc-CREATE-cnf Direction: GPU to Control Station


7.2.3.2.3 LapDBc-DELETE-req

This message is used to delete a LapDBc. Message type: LapDBc-DELETE-req Direction: Control Station to GPU


Header

LapDBcDeleteReqDataElement






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

Evo

lium

.

7.2.3.2.4 LapDBc-DELETE-cnf

This message is used to confirm the LapDBc deletion. Message type: LapDBc-DELETE-cnf Direction: GPU to Control Station


7.2.3.2.5 LapDBc-SET-req ( not used )

This message is used to set configuration on a LapDBc instance. Message type: LapDBc-SET-req Direction: Control Station to GPU.


Header

LapDBcSetReqDataElement



LapDBcSetReqContent

LapDBcCfg LapDBc Configuration (*)

7.2.3.2.6 LapDBc-SET-cnf (not used )

This message is used to confirm a set of LapDBc on an objet instance. Message type: LapDBc �SET-cnf Direction: GPU to Control Station.


7.2.4 FrBc entity

7.2.4.1 FrBc structures description

The FrBc parameter groups are classified into functional areas:

• FrBc configuration.

• FrBc state (cf GOM-NS part).

The ProtocolType is always "user" at GPU/CS.

The TS 0 shall never be used for a bearer channel.

A given PcmPort can support up to 31 FrBcs and there are 16 PcmPorts. But LapDBc instances + FrBc <= 128 (Hardware limit, linked to the HDLC controller)




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

Evo

lium

.

7.2.4.2 FrBc messages description

7.2.4.2.1 FrBc-CREATE-req

This message is used to create an Frame Relay Bearer Channel. Message type: FrBc-CREATE-req Direction: Control Station to GPU


Header

FrBcCreateReqDataElement

OmRef OmFrBcRef u_int

BssRef FrBcRef u_int

FrBcCreateReqContent

FrBcCfg FrBc Configuration structure (*)

7.2.4.2.2 FrBc-CREATE-cnf

This message is used to confirm the FrBc creation. Message type: FrBc-CREATE-cnf Direction: GPU to Control Station


7.2.4.2.3 FrBc-DELETE-req

This message is used to delete a FrBc. Message type: FrBc-DELETE-req Direction: Control Station to GPU


Header

FrBcDeleteReqDataElement

OmRef OmFrBcRef u_int

BssRef FrBcRef u_int

7.2.4.2.4 FrBc-DELETE-cnf

This message is used to confirm the FrBc deletion. Message type: FrBc-DELETE-cnf Direction: GPU to 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

Evo

lium

.

7.3 GOM-RRM INTERFACE DESCRIPTION

7.3.1 Overview

We decides to focus only on the Request and Indication messages as the CoNFirmation message have always the same format .


Header

GPU CLASS - MSG CNF DataElement

OmRef Om GPU CLASS Ref u_int

BssRef GPU CLASS Ref u_int

GPU CLASS MSG CNF Content

AckContent

7.3.2 Bss

7.3.2.1 CreateReq

Direction ..........: GOM to TRM

Header.ClassId .....: Bss (0x0201)

Header.msgType .....: CreateReq (0x0070)

Data Contents ......: BssBasicCfg(Ref [4])

7.3.2.2 SetBssGpReq



Header.msgType .....: SetBssGpReq (0x0120)

Data Contents ......: BssSetGpContentCfg(Ref [4])

7.3.2.3 SetCellMappingReq



Header.msgType .....: SetCellMappingReq (0x0290)

Data Contents ......: BssCellMappingListCfg(Ref [4])




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

Evo

lium

.

7.3.2.4 SetLxpuStatusReq



Header.msgType .....: SetLxpuStatusReq (0x02F0)

Data Contents ......: BssLxpuStatusContent(Ref [4])

7.3.2.5 SetPagingAreaMainReq



Header.msgType .....: SetPagingAreaMainReq (0x0280)

Data Contents ......: BssLACMainLXPUListCfg(Ref [4])

7.3.2.6 SetReq



Header.msgType .....: SetReq (0x0010)

Data Contents ......: BssSetReqContentCfg(Ref [4])

7.3.2.7 StateChangeInd

Direction ..........: TRM to GOM


Header.msgType .....: StateChangeInd (0x0062)

Data Contents ......: BssState(Ref [4])

7.3.2.8 VersionInd



Header.msgType .....: VersionInd (0x00D2)

Data Contents ......: BssVersionCfg(Ref [4])




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

Evo

lium

.

7.3.3 Cell

7.3.3.1 CreateReq


Header.ClassId .....: Cell (0x0202)


Data Contents ......: CellCreateReqContentCfg(Ref [4])

7.3.3.2 SetBvciMappingReq



Header.msgType .....: SetBvciMappingReq (0x00E0)

Data Contents ......: CellBvciMappingContentCfg(Ref [4])

7.3.3.3 SetReq




Data Contents ......: CellSetReqContentCfg(Ref [4])





Data Contents ......: CellState(Ref [4])

7.3.4 FrBc

7.3.4.1 CreateReq


Header.ClassId .....: FrBc (0x0102)


Data Contents ......: FrBcCfg(Ref [4])




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

Evo

lium

.

7.3.4.2 SetReq




Data Contents ......: FrBcCfg(Ref [4])





Data Contents ......: FrBcState(Ref [4])

7.3.5 GchGroup

7.3.5.1 CreateReq


Header.ClassId .....: GchGroup (0x0203)


Data Contents ......: GchGroupCfg(Ref [4])

7.3.5.2 SetReq


Header.ClassId .....: GchGroup (0x0203)


Data Contents ......: GchGroupCfg(Ref [4])

7.3.6 Gsl

7.3.6.1 CreateReq


Header.ClassId .....: Gsl (0x0204)


Data Contents ......: GslCfg(Ref [4])




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

Evo

lium

.

7.3.6.2 SetReq




Data Contents ......: GslCfg(Ref [4])





Data Contents ......: GslState(Ref [4])

7.3.7 LapDBc

7.3.7.1 CreateReq


Header.ClassId .....: LapDBc (0x0101)


Data Contents ......: LapDBcCfg(Ref [4])

7.3.7.2 SetReq


Header.ClassId .....: LapDBc (0x0101)


Data Contents ......: LapDBcCfg(Ref [4])

7.3.8 LapDLink

7.3.8.1 CreateReq


Header.ClassId .....: LapDLink (0x0205)


Data Contents ......: LapDLinkCfg(Ref [4])




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

Evo

lium

.



Header.ClassId .....: LapDLink (0x0205)


Data Contents ......: LapDLinkState(Ref [4])

7.3.9 Nse

7.3.9.1 CreateReq


Header.ClassId .....: Nse (0x0301)


Data Contents ......: NseCfg(Ref [4])

7.3.10 NsVc

7.3.10.1 CreateReq


Header.ClassId .....: NsVc (0x0302)


Data Contents ......: NsVcCfg(Ref [4])

7.3.10.2 SetReq




Data Contents ......: NsVcCfg(Ref [4])





Data Contents ......: NsVcState(Ref [4])




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

Evo

lium

.

7.3.11 Pvc

7.3.11.1 CreateReq


Header.ClassId .....: Pvc (0x0303)


Data Contents ......: PvcCfg(Ref [4])

7.3.11.2 SetReq




Data Contents ......: PvcCfg(Ref [4])





Data Contents ......: PvcState(Ref [4])

7.3.12 RrmP

7.3.12.1 SetReq


Header.ClassId .....: RrmP (0x0200)


Data Contents ......: RrmPSetReqContentCfg(Ref [4])




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

Evo

lium

.

7.3.13 Dynamic description

7.3.13.1 BSS create in GPU

GOM/ GPU GPU Class Msg Type Comments

---------> Bss CreateReq Locked

<--------- Bss CreateCnf

---------> LapDLink CreateReq Locked

<--------- LapDLink CreateCnf

---------> Gsl CreateReq Locked

<--------- Gsl CreateCnf

---------> GchGroup CreateReq

<--------- GchGroup CreateCnf

---------> Bss SetLxpuStatusReq

<--------- Bss SetLxpuStatusCnf

---------> Bss SetPagingAreaMainReq

<--------- Bss SetPagingAreaMainCnf

---------> Bss SetCellMappingReq

<--------- Bss SetCellMappingCnf

---------> Bss EndOfCfgReq

<--------- Bss EndOfCfgCnf

<--------- Gsl StateChangeInd Enabled/ Disabled

<--------- Bss StateChangeInd Enabled/ Disabled, Unlocked

---------> LapDLink UnlockReq if LapDLink.lockrequest is locked

<--------- LapDLink UnlockCnf

<--------- LapDLink StateChangeInd Unlocked

<--------- Gsl StateChangeInd Unlocked

---------> Bss UnlockReq if BSS.lockrequest is locked




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

Evo

lium

.

<--------- Bss UnlockCnf

<--------- Bss StateChangeInd Enabled/ Disabled, Unlocked

7.3.13.2 BSS delete in GPU


---------> Cell LockReq

<--------- Cell LockCnf

<--------- Cell StateChangeInd Locked

---------> Cell DeleteReq

<--------- Cell DeleteCnf

---------> Bss LockReq

<--------- Bss LockCnf

<--------- Bss StateChangeInd Locked

---------> Bss DeleteReq GPU removes GSL, LapDLink anf GicGroup objects

<--------- Bss DeleteCnf

7.3.13.3 Cell create in GPU


---------> Cell CreateReq

<--------- Cell CreateCnf

---------> Cell SetReq

<--------- Cell SetCnf

---------> Bss SetCellMappingReq


---------> Cell EndOfCfgReq

<--------- Cell EndOfCfgCnf

<--------- Cell StateChangeInd




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

Evo

lium

.

---------> Cell UnlockReq if Cell is unlocked

<--------- Cell UnlockCnf

<--------- Cell StateChangeInd unlocked

7.3.13.4 Cell delete in GPU


---------> Cell LockReq

<--------- Cell LockCnf

<--------- Cell StateChangeInd locked

---------> Cell DeleteReq

<--------- Cell DeleteCnf

---------> Bss SetCellMappingReq to all LXPUi


7.3.13.5 Cell modification in GPU






7.3.13.6 FRBearer delete


---------> FrBc DeleteReq

<--------- FrBc DeleteCnf

---------> Pvc DeleteReq

<--------- Pvc DeleteCnf




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

Evo

lium

.

7.3.13.7 GPU plug/switchover: Bcm init (not-initialized)


---------> BcmP ReadyInd not-initialized

<--------- BcmP ReadyRsp

---------> FrBc CreateReq

<--------- FrBc CreateCnf

---------> LapDBc CreateReq

<--------- LapDBc CreateCnf

---------> BcmP EndOfCfgReq BCM is initialized

<--------- BcmP EndOfCfgCnf

7.3.13.8 GPU plug/switchover: Ns init (not-initialized)


---------> NsP ReadyInd not initialized

<--------- NsP ReadyRsp

---------> NsP SetReq

<--------- NsP SetCnf

---------> FrBc StateChangeInd

---------> Pvc CreateReq

<--------- Pvc CreateCnf

---------> Nse CreateReq

<--------- Nse CreateCnf

---------> NsVc CreateReq Locked

<--------- NsVc CreateCnf

---------> Nse EndOfCfgReq

<--------- Nse EndOfCfgCnf initialized

---------> Pvc StateChangeInd Enabled/Disabled

---------> NsVc StateChangeInd Enabled/Disabled




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

Evo

lium

.

---------> NsVc UnlockReq is NSVC.lockrequest is Unlocked

<--------- NsVc UnlockCnf

---------> NsVc StateChangeInd Unlocked

7.3.13.9 GPU plug/switchover: Rrm init (not-initialised)


<--------- RrmP ReadyInd not initialized

---------> RrmP ReadyRsp

<--------- RrmP SetReq

---------> RrmP SetCnf

---------> Bss CreateReq Locked

<--------- Bss CreateCnf

---------> Bss SetReq

<--------- Bss SetCnf



---------> Gsl CreateReq

<--------- Gsl CreateCnf

<--------- LapDLink StateChangeInd

---------> GchGroup CreateReq

<--------- GchGroup CreateCnf

---------> Bss SetLxpuStatusReq to all LXPUi

<--------- Bss SetLxpuStatusCnf

---------> Bss SetPagingAreaMainReq

to all LXPUi

<--------- Bss SetPagingAreaMainCnf

---------> Bss SetCellMappingReq to all LXPUi





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

Evo

lium

.

---------> Bss EndOfCfgReq

<--------- Bss EndOfCfgCnf initialized

---------> Bss UnlockReq if BSS is unlocked

<--------- Bss UnlockCnf

<--------- Bss StateChangeInd unlocked

---------> LapDLink UnlockReq if lapDLink is unlocked


<--------- LapDLink StateChangeInd unlocked

<--------- Gsl StateChangeInd

---------> Cell CreateReq

<--------- Cell CreateCnf





<--------- Cell StateChangeInd

---------> Cell UnlockReq if Cell is unlocked

<--------- Cell UnlockCnf

<--------- Cell StateChangeInd unlocked

7.3.13.10 LapDLinks creation in GPU


---------> LapDBc CreateReq

<--------- LapDBc CreateCnf



---------> LapDLink UnlockReq if lapDLink.lockrequest is unlocked




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

Evo

lium

.


<--------- LapDLink StateChangeInd Unlocked

7.3.13.11 LapDLinks deletion in GPU


---------> LapDLink DeleteReq if not the last of the BSS and in a LXPU

<--------- LapDLink DeleteCnf

---------> LapDBc DeleteReq

<--------- LapDBc DeleteCnf

7.3.13.12 NSE create


---------> Nse CreateReq NSE is created in the LXPU when the first NSVC of this NSE is created: its related PVC, with the PVC FRBearer PCM-TTP, gives the LXPU.

<--------- Nse CreateCnf

7.3.13.13 NS-VC delete


---------> NsVc DeleteReq NSVC must be Locked

<--------- NsVc DeleteCnf

7.3.13.14 NS-VC lock


---------> NsVc LockReq

<--------- NsVc LockCnf

---------> NsVc StateChangeInd Locked




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

Evo

lium

.

7.3.13.15 NS-VC unlock


---------> NsVc UnlockReq

<--------- NsVc UnlockCnf

---------> NsVc StateChangeInd Unlocked

7.3.13.16 SW change: BSC SW change


<--------- Bss VersionInd During the BSS Reset procedure, the BSC and the MFS exchange their BSCGP version. Then, the BSCGP version information coming from the BSC is sent to the GOM.

7.4 GLM-LRM INTERFACE DESCRIPTION

7.4.1 Overview

We decides to focus only on the Request and Indication messages as the CoNFirmation message have always the same format .


Header

GPU CLASS - MSG CNF DataElement

OmRef Om GPU CLASS Ref u_int

BssRef GPU CLASS Ref u_int

GPU CLASS MSG CNF Content

AckContent

7.4.2 LcsBss

7.4.2.1 CreateReq

Direction ..........: GLM to LRM

Header.ClassId .....: LcsBss (0x0901)




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

Evo

lium

.


Data Contents ......: LcsBssCreateReqContent(Ref [4])

7.4.2.2 SetReq




Data Contents ......: LcsBssSetReqContent(Ref [4])

7.4.2.3 VersionInd

Direction ..........: LRM to GLM


Header.msgType .....: VersionInd (0x00D2)

Data Contents ......: LcsBsslpVersionCfg(Ref [4])

7.4.3 LcsCell

7.4.3.1 CreateReq


Header.ClassId .....: LcsCell (0x0902)


Data Contents ......: LcsCellCreateReqContent(Ref [4])

7.4.3.2 SetReq


Header.ClassId .....: LcsCell (0x0902)


Data Contents ......: LcsCellSetReqContent(Ref [4])




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

Evo

lium

.

7.4.4 SmlcP

7.4.4.1 ReadyInd

Direction ..........: LRM to GLM

Header.ClassId .....: SmlcP (0x0900)

Header.msgType .....: ReadyInd (0x0002)

Data Contents ......: SmlcPReadyInfoCfg(Ref [4])

7.4.4.2 SetReq


Header.ClassId .....: SmlcP (0x0900)


Data Contents ......: SmlcPSetReqContent(Ref [4])

7.5 GOM-NS INTERFACE DESCRIPTION

7.5.1 Overview

7.5.1.1 NsP entity

7.5.1.1.1 NsP structures description

The NsP parameter groups are classified into 2 functional areas:

• NsP configuration

• Frame Relay configuration .

Refer to [14] for the description of these groups.

7.5.1.2 NsP messages description

7.5.1.2.1 NsP-READY-ind

This message is used to report the Control station the NsP is operational for configuration. Message type: NsP-READY-ind Direction: GPU to 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

Evo

lium

.


Header

NsPReadyIndDataElement

OmRef OmNsPRef u_int

BssRef NsPRef u_int

NsPReadyIndContent


1 = initialised

u_int

LogicalNumber u_int

Tsap u_int

ipAddr IP address of the GPU u_int

7.5.1.2.2 NsP-READY-rsp

This message is used to acknowledge the NsP-READY-rsp. Message type: NsP-READY-rsp Direction: Control Station to GPU


7.5.1.2.3 NsP-SETB8-req

This message is used to set configuration on a NsP instance. It also provides the O&M Reference of NsP to the MFS Telecom part. Message type: Erreur ! Source du renvoi introuvable. Direction: Control Station to GPU.


Header

NsPSetB8ReqDataElement


BssRef NsPRef u_int

NsPSetB8ReqContent

NsPCfg NsP Configuration structure (*)

NsPFrCfg Fr Configuration structure (*)

7.5.1.2.4 NsP-SETB8-cnf

This message is used to confirm a set of NsP on an objet instance. Message type: Erreur ! Source du renvoi introuvable. Direction: GPU to 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

Evo

lium

.

7.5.1.2.5 NSP-END-OF-CFG-req

This message is used to indicate the GPU the end of the NsP�s configuration Message type: NsP-END-OF-CFG-req Direction: Control Station to GPU


Header

NsPEndOfCfgReqDataElement


BssRef NsPRef u_int

7.5.1.2.6 NSP-END-OF-CFG-cnf

This message is used to confirm the end of NsP�s configuration. Message type: NsP-End-OF-CFG-cnf Direction: GPU to Control Station


7.5.1.2.7 NsP-END-OF-SYNCHRO-ind

This message is used to indicate the Control Station the end of the NsP�s synchronisation Message type: NsP-END-OF-SYNCHRO-ind Direction: GPU to Control Station


Header

NsPEndOfSyncIndDataElement


BssRef NsPRef u_int

7.5.1.2.8 NsP-END-OF-SYNCHRO-rsp

This message is used to respond to End of configuration indication. Message type: NsP-END-OF-SYNCHRO-rsp Direction: Control Station to GPU





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

Evo

lium

.

7.5.2 Nse entity

7.5.2.1 Nse structures description

The Nse parameter groups are classified into 1 functional area:

• Nse configuration.

Nse configuration structure is defined in [14].

7.5.2.2 Nse messages description

7.5.2.2.1 NSE-CREATE-req

This message is used to create a Network Service Entity. Message type: NSE-CREATE-req Direction: Control Station to GPU


Header

NseCreateReqDataElement

OmRef OmNseRef u_int

BssRef NseRef u_int

NseCreateReqContent

NseCfg Nse configuration structure (*)

7.5.2.2.2 NSE-CREATE-cnf

This message is used to confirm the Network Service Entity creation. Message type: NSE-CREATE-cnf Direction: GPU to Control Station


7.5.2.2.3 NSE-DELETE-req

This message is used to delete a Network Service Entity. Message type: NSE-DELETE-req Direction: Control Station to GPU


Header

NseDeleteReqDataElement


BssRef NseRef u_int




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

Evo

lium

.

7.5.2.2.4 NSE-DELETE-cnf

This message is used to confirm the Network Service Entity destruction. Message type: NSE-DELETE-cnf Direction: GPU to Control Station


7.5.2.2.5 NSE-END-OF-CFG-req

This message is used to indicate the GPU the end of the Nse�s configuration.

Message type: NSE-END-OF-CFG-req

Direction: Control Station to GPU


Header

NseEndOfCfgReqDataElement


BssRef NseRef u_int

7.5.2.2.6 NSE-END-OF-CFG-cnf

This message is used to confirm the end of Nse�s configuration. Message type: NSE-END-OF-CFG-cnf Direction: GPU to Control Station


7.5.3 NsVc entity

7.5.3.1 NsVc structures description

The NsVc parameter groups are classified into 2 functional areas:

• NsVc configuration

• NsVc State





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

Evo

lium

.

7.5.3.2 NsVc messages description

7.5.3.2.1 NsVc-CREATE-req

This message is used to create a Network Service Virtual Connection. Message type: NsVc-CREATE-req Direction: Control Station to GPU


Header

NsVcCreateReqDataElement

OmRef OmNsVcRef u_int

BssRef NsVcRef u_int

NsVcCreateReqContent

NsVcCfg NsVc configuration structure (*)

7.5.3.2.2 NsVc-CREATE-cnf

This message is used to confirm the Network Service Virtual Connection creation. Message type: NsVc-CREATE-cnf Direction: GPU to Control Station


7.5.3.2.3 NsVc-DELETE-req

This message is used to delete a Network Service Virtual Connection. Message type: NsVc-DELETE-req Direction: Control Station to GPU


Header

NsVcDeleteReqDataElement



7.5.3.2.4 NsVc-DELETE-cnf

This message is used to confirm the Network Service Virtual Connection deletion. Message type: NsVc-DELETE-cnf Direction: GPU to 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

Evo

lium

.

7.5.3.2.5 NsVc-LOCK-req

This message is used to delete a Network Service Virtual Connection. Message type: NsVc-LOCK-req Direction: Control Station to GPU


Header

NsVcLockReqDataElement



7.5.3.2.6 NsVc-LOCK-cnf

This message is used to confirm the Network Service Virtual Connection deletion. Message type: NsVc-LOCK-cnf Direction: GPU to Control Station


7.5.3.2.7 NsVc-UNLOCK-req

This message is used to delete a Network Service Virtual Connection. Message type: NsVc-UNLOCK-req Direction: Control Station to GPU


Header

NsVcUnlockReqDataElement



7.5.3.2.8 NsVc-UNLOCK-cnf

This message is used to confirm the Network Service Virtual Connection deletion. Message type: NsVc-UNLOCK-cnf Direction: GPU to 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

Evo

lium

.

7.5.3.2.9 NsVc-SET-req

This message is used to set the Network Service Virtual Connection attributes. Message type: NsVc-SET-req Direction: Control Station to GPU


Header

NsVcSetReqDataElement



NsVcSetReqContent

NsVcCfg NsVc configuration structure (*)

7.5.3.2.10 NsVc-SET-cnf

This message is used to confirm the set of Network Service Virtual Connection attributes. Message type: NsVc-SET-cnf Direction: GPU to Control Station


7.5.3.2.11 NsVc-STATE-CHANGE-ind

This message is used to report the Control station the NSVC state changed. Message type: NsVc-STATE-CHANGE-ind Direction: GPU to Control Station


Header

NsVcStateChangeIndDataElement



NsVcStateChangeIndContent

NsVcState NsVc States structure (*)

7.5.4 Pvc entity

7.5.4.1 Pvc structures description

The Pvc parameter groups are classified into 2 functional areas:

• Pvc Telecom configuration

• Pvc State.





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

Evo

lium

.

7.5.4.2 Pvc messages description

7.5.4.2.1 PVC-CREATE-req

This message is used to create a Permanent Virtual Connection. Message type: PVC-CREATE-req Direction:

Control Station to GPU


Header

PvcCreateReqDataElement

OmRef OmPvcRef u_int

BssRef PvcRef u_int

PvcCreateReqContent

PvcCfg Pvc configuration structure (*)

7.5.4.2.2 PVC-CREATE-cnf

This message is used to confirm the Permanent Virtual Channel creation. Message type: PVC-CREATE-cnf Direction: GPU to Control Station


7.5.4.2.3 PVC-DELETE-req

This message is used to delete a Permanent Virtual Connection. Message type: PVC-DELETE-req Direction: Control Station to GPU


Header

PvcDeleteReqDataElement


BssRef PvcRef u_int




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

Evo

lium

.

7.5.4.2.4 PVC-DELETE-cnf

This message is used to confirm the Permanent Virtual Channel deletion.

Message type: PVC-DELETE-cnf Direction: GPU to Control Station


7.5.4.2.5 PVC-SET-req

This message is used to set the attributes of a Permanent Virtual Connection. Message type: PVC-SET-req Direction: Control Station to GPU


Header

PvcSetReqDataElement


BssRef PvcRef u_int

PvcSetReqContent

PvcCfg Pvc configuration structure (*)

7.5.4.2.6 PVC-SET-cnf

This message is used to confirm the Permanent Virtual Channel attribute set. Message type: PVC-SET-cnf Direction: GPU to Control Station


7.5.4.2.7 PVC-STATE-CHANGE-ind

This message is used to report the change of a Permanent Virtual Connection state. Message type: PVC-STATE-CHANGE-ind Direction: GPU to Control Station


Header

PvcStateChangeIndDataElement


BssRef PvcRef u_int

PvcStateChangeIndContent

PvcState Pvc States structure (*)




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

Evo

lium

.

7.5.5 FrBc entity


The FrBc parameter group has one functional area (on GOM-NS Interface):

• FrBc State (FrBcState in [14])

Note :The operational state of FrBc is �enabled� when the PcmPort is �enabled� and link polling procedure complete.


7.5.5.2.1 FRBC-STATE-CHANGE-ind

This message is used to report the change of a FR Bearer Channel state. Message type: FRBC-STATE-CHANGE-ind Direction: GPU to Control Station


Header

FrBcStateChangeIndDataElement

OmRef OmFrBcRef U_int

BssRef FrBcRef U_int

FrBcStateChangeIndContent

FrBcState FrBc State structure (*)

7.6 GAM-BAM INTERFACE DESCRIPTION

7.6.1 Overview

The BAM is responsible for sending GPU alarms to the Control Station.

Alarms report messages formats are defined in §6.2.3.

7.6.2 amP entity

amP entity manages all information concerning Alarm Management parameters

7.6.2.1 amP structure description

The amP parameters group are classified itno one functional area:

- amP synchronisation configuration




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

Evo

lium

.

7.6.2.2 amP message description

7.6.2.2.1 BamP-READY-ind

This message is used to report the control station that the BamP is operational for alarm reporting.

Message type: BamP-READY-ind Direction: GPU to Control Station


Header

BamPReadyIndDataElement

OmRef OmBamPRef NIL u_int

BssRef BamPRef 0 u_int


1 = initialised

u_int

Tsap (1) u_int

(1) set by BAM

7.6.2.2.2 BamP-READY-rsp

This message is used to acknowledge the BamP that the GAM has received the BamP READY indication. Message type:

BamP-READY-rsp

Direction: Control Station to GPU


7.7 SCA-SCA INTERFACE DESCRIPTION

7.7.1 Messages description

7.7.1.1 FAPI_INFO_REQ

This message is used by both SCA . Message type: FAPI_INFO_REQ Direction: Both


Header

Type FAPI_INFO_REQ FAPI_INFO_REQ int

FapId FAP Identifier Unsigned int

IFapId IFAP Identifier Unsigned int




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

Evo

lium

.

7.7.1.2 FAPI_INFO_RESP

This message is used by both SCA . Message type: FAPI_INFO_RESP Direction: Both


Header

Type FAPI_INFO_RESP int



DataElement

state FAPI State CS defined Unsigned int

substate FAPI substate CS defined Unsigned int

Tsap If the state is ON indicates the tsap on which is localised the FAPI

Unsigned int




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

Evo

lium

.

7.7.1.3 FAPI_INFO_EVT

This message is used by both SCA . Message type: FAPI_INFO_EVT Direction: Both


Header

Type FAPI_INFO_EVT int



DataElement

state FAPI State CS Defined Unsigned int

substate FAPI substate CS Defined Unsigned int

Tsap If the state is ON indicates the tsap on which is localised the FAPI

Unsigned int

7.8 GEM-SCA INTERFACE DESCRIPTION

7.8.1 Managed object (coherent with CS)

7.8.1.1 GEM_ncs_fapcre_t structure


fap Fap identifier Unsigned int

addmod Adressing mode NCS_FUNCORG, NCS_PHYSICAL, NCS_ORGANIC

Unsigned int

dispmod Dispatching mode CS Defined Unsigned int

reconf Is the FAP Reconfigurable (NB always at NO for PSOS FAP). CS Defined Unsigned int

ifaptablsize Size of its iIFAP table Unsigned int

tsapgr TSAP group Unsigned int

7.8.1.2 GEM_ncs_ifapcre_t structure


fap Fap identifier Unsigned int

ifap Adressing mode CS Defined Unsigned int

loadthrs Load threshold CS Defined Unsigned int

7.8.1.3 GEM_ncs_counters_t


Max_dtg Maximum number of datagramme Unsigned int

Max_qst Maximum number of question Unsigned int

Max_ses Maximum number of session Unsigned int

Max_cred_ses Maximum number of credit session. Unsigned int




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

Evo

lium

.

7.8.1.4 GEM_ncs_thres_t


Beg_cong Begin of congestion threshold Unsigned int

End_cong End of congestion threshold Unsigned int

Inc_dest Begin of destruction threshold Unsigned int

7.8.1.5 GEM_ncs_pcre _t


fap FAP identifier Unsigned int

ifap IFAP identifier Unsigned int

timer Time out value Unsigned int

counters Dimensionning value Gem_ncs_counters_t

Dtg_thres Datagramme dimensionning values GEM_ncs_thres_t

Qst_thres Question dimensionning values GEM_ncs_thres_t

Ses_thres Session dimensionning values GEM_ncs_thres_t

7.8.1.6 GEM_nxa_pcre_t


P_dsim DSIM value. Unsigned int

Ncs_pcre Port configuration GEM_ncs_pcre _t

7.8.1.7 GEM_ncs_rfcre_t


rf Remote fap Id Unsigned int

fap Fap Id Unsigned int

priority Priority int

allowacc Allowed direction NCS_IN, NCS_OUT,NCS_INOUT int

7.8.1.8 GEM_psos_port


port Port comfiguration Gem_nxa_pcre_t

nbrf Number of remote fap 0-64 Unsigned int

tabrf Array of 64 containing the remote fap GEM_ncs_rfcre_t [64]




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

Evo

lium

.

7.8.2 Messages

7.8.2.1 GEM_GPU_FAP_REQ

This message is used by GEM. Message type: GEM_GPU_FAP_REQ Direction: Control Station to GPU


Header

Type GEM_GPU_FAP_REQ int

Inv_id lndicates if it is the last message of this type GEM_LAST, GEM_NOT_LAST int

Length Length of the data part Unsigned int

DataElement

Faplist_len Number of GEM_ncs_fapcre_t structures following this field int

Description of each fap GEM_ncs_fapcre_t []

7.8.2.2 GEM_GPU_FAP_REP

This message is used by GEM. Message type: GEM_GPU_FAP_ REP Direction: GPU to Control Station


Header

Type GEM_GPU_FAP_ REP Int

Inv_id Install OK or not OK GEM_OK, GEM_NOK int

Length Always 0 Unsigned int

7.8.2.3 GEM_GPU_IFAP_REQ

This message is used by GEM. Message type: GEM_GPU_IFAP_REQ Direction: Control Station to GPU


Header

Type GEM_GPU_IFAP_REQ Int

Inv_id lndicates if it is the last message of this type GEM_LAST, GEM_NOT_LAST Int


DataElement




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

Evo

lium

.

hostname Name of the station on which are localized the IFAP Char[32]

Tsap TSAP of the station on which are localized the IFAP Unsigned int

LogicalNumber Logical number of the station on which are localized the IFAP Unsigned int

Ifaplist_len Number of gem_ncs_ifapcre_t following this field Unsigned int

Description of each ifap gem_ncs_ifapcre_t[]

7.8.2.4 GEM_GPU_IFAP_REP

This message is used by both SCA. Message type: GEM_GPU_IFAP_ REP Direction: GPU to Control Station


Header

Type GEM_GPU_IFAP_ REP Int

Inv_id Install OK or not OK GEM_OK, GEM_NOK Int


DataElement

tsap TSAP of the card Unsigned int

7.8.2.5 GEM_CONF_INSTALL_REQ

This message is used by GEM. Message type: GEM_CONF_INSTALL_REQ Direction: Control Station to GPU


Header

Type GEM_CONF_INSTALL_REQ Int

Inv_id lndicates if it is the last message of this type GEM_LAST, GEM_NOT_LAST Int


DataElement

Tabport_len Number of gem_psosport structure following this field 0-256 Unsigned int

Description of each port gem_psosport[]




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

Evo

lium

.

7.8.2.6 GEM_CONF_INSTALL_REP

This message is used by both SCA. Message type: GEM_CONF_INSTALL_REP Direction: GPU to Control Station


Header

Type GEM_CONF_INSTALL_REP Int

Inv_id Install OK or not OK GEM_OK, GEM_NOK Int


7.9 GPM-TPM interface DESCRIPTION

7.9.1 Overview

GPM is an Real Time Agent multi-releases. Thus, the same GPM software must be able to handle GPU messages whatever is the software release of the GPU (GPM does not know the release of the GPU).

For the external interface to NPA/OMC, there is only one format, defined in the doc ref [ 9 ]

7.9.2 PmP entity

7.9.2.1 PmP structures description

7.9.2.2 PmP messages description

7.9.2.2.1 PmP-Ready-Ind Message type: PmP-Ready-Ind Direction: Control Station to GPU


OmRef OmPmPRef u_int

BssRef PmPRef u_int

PmPReadyIndContent


1 = initialised

u_int

logical_number u_int




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

Evo

lium

.

7.9.2.2.2 PmP-Ready-Rsp

Message type: PmP-Ready-Rsp Direction: GPU to Control Station



BssRef PmPRef u_int

PmPReadyRspContent

StateRequest Request of current states of all object instances 0 = No

1 = Yes

u_int

AckContent

AckNack Result of the request 00h = Ack (Success), 01h = Nack (Failure)

u_int



7.9.2.2.3 PmP-Set-Req

Message type: PmP-Set-Req Direction: Control Station to GPU



BssRef PmPRef u_int

PmPSetReqContent

PmPCfg

7.9.2.2.4 PmP-Set-Cnf

Message type: PmP-Set-Cnf Direction: GPU to Control Station



BssRef PmPRef u_int

AckContent

AckNack Result of the request 00h = Ack (Success), 01h = Nack (Failure)

u_int






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

Evo

lium

.

7.9.2.2.5 PmP-Report-Req (Generic Report Message)

Message type: PmP-Report-Req Direction: Control Station to GPU


OmRef OmPmPRef U_int

BssRef PmPRef 0 U_int

PmPReportReqContent

ObjectIdsCfg * * * for further use * * *

ReportingClassCfg Identifier of the class on which the results are requested classId can be

cell OR distCell OR lcsCell OR BTS

7.9.2.2.6 PmP-Report-Cnf (Generic Report Message)

Message type: PmP-Report-Cnf Direction: GPU to Control Station


PmPReportCnfGlobal

PmClassHeaderReportCfg Header of the report 8 bytes see ref [4)

list of instnaces/ counters reports

details instances and counters reports

Here is the detailed format of the PmPReportCnf DataElement:

nbOfInstances instances of classId

PmClassHeaderReportCfg:classIdnbOfPmItemReportnbOfInstances

PmInstanceReportCfg:sif

PmItemReportCfg:valueid

nbOfPmItemReport




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

Evo

lium

.

Here is a different way to describe the Data Element.

Note that the PmHeader is not Part of the Data Element.

Data Element is always equal to 1. This is due to RTA simulator limitation.

nbOfInstances instances of classId

PmClassHeaderReportCfg: classId nbOfPmItemReport nbOfInstances

PmInstanceReportCfg: sif

PmItemReportCfg: value id nbOfPmItemReport

PmItemReportCfg: value id

Nb Data

Element

The nbOfInstances is the number of instance reported in the current message. It is not the total number of cells created at TPM side (case where TPM used several messages to report cell reportCnf)

An item can be a parameter or a counter. A counter ID value is always in the [0...9999] range, a parameter ID value is always in the [10000...19999] range

The configuration data are always placed first in the count list by the TPM. Then, come the counters.

The Class that reports Counters by using the Generic messages are: lcsCell, DistCell, Cell, BTS class.

7.9.2.2.6.1 lcsCell The expected parameters are (in this order):

- 10001 BSS - 10768 CI - 10769 LAC

7.9.2.2.6.2 DistCell The expected parameters are (in this order):

- 10001 BSS - 10768 CI - 10769 LAC - 11665 PD_DL_PDCH_UNIT_ALLOC_THR_1 - 11666 PD_DL_PDCH_UNIT_ALLOC_THR_2 - 11667 PD_DL_PDCH_UNIT_ALLOC_THR_3 - 11668 PD_DL_PDCH_UNIT_ALLOC_THR_4 - 11669 PD_DL_PDCH_UNIT_ALLOC_THR_5 - 11670 PD_DL_PDCH_UNIT_ALLOC_THR_6 - 11671 PD_DL_PDCH_UNIT_ALLOC_THR_7 - 11672 PD_DL_PDCH_UNIT_ALLOC_THR_8 - 11673 PD_DL_PDCH_UNIT_ALLOC_THR_9 - 11629 PD_DL_TBF_DURATION_THR_1 - 11630 PD_DL_TBF_DURATION_THR_2




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

Evo

lium

.

- 11631 PD_DL_TBF_DURATION_THR_3 - 11632 PD_DL_TBF_DURATION_THR_4 - 11633 PD_DL_TBF_DURATION_THR_5 - 11634 PD_DL_TBF_DURATION_THR_6 - 11635 PD_DL_TBF_DURATION_THR_7 - 11636 PD_DL_TBF_DURATION_THR_8 - 11637 PD_DL_TBF_DURATION_THR_9 - 11647 PD_DL_TBF_VOLUME_THR_1 - 11648 PD_DL_TBF_VOLUME_THR_2 - 11649 PD_DL_TBF_VOLUME_THR_3 - 11650 PD_DL_TBF_VOLUME_THR_4 - 11651 PD_DL_TBF_VOLUME_THR_5 - 11652 PD_DL_TBF_VOLUME_THR_6 - 11653 PD_DL_TBF_VOLUME_THR_7 - 11654 PD_DL_TBF_VOLUME_THR_8 - 11655 PD_DL_TBF_VOLUME_THR_9 - 11656 PD_UL_PDCH_UNIT_ALLOC_THR_1 - 11657 PD_UL_PDCH_UNIT_ALLOC_THR_2 - 11658 PD_UL_PDCH_UNIT_ALLOC_THR_3 - 11659 PD_UL_PDCH_UNIT_ALLOC_THR_4 - 11660 PD_UL_PDCH_UNIT_ALLOC_THR_5 - 11661 PD_UL_PDCH_UNIT_ALLOC_THR_6 - 11662 PD_UL_PDCH_UNIT_ALLOC_THR_7 - 11663 PD_UL_PDCH_UNIT_ALLOC_THR_8 - 11664 PD_UL_PDCH_UNIT_ALLOC_THR_9 - 11620 PD_UL_TBF_DURATION_THR_1 - 11621 PD_UL_TBF_DURATION_THR_2 - 11622 PD_UL_TBF_DURATION_THR_3 - 11623 PD_UL_TBF_DURATION_THR_4 - 11624 PD_UL_TBF_DURATION_THR_5 - 11625 PD_UL_TBF_DURATION_THR_6 - 11626 PD_UL_TBF_DURATION_THR_7 - 11627 PD_UL_TBF_DURATION_THR_8 - 11628 PD_UL_TBF_DURATION_THR_9 - 11638 PD_UL_TBF_VOLUME_THR_1 - 11639 PD_UL_TBF_VOLUME_THR_2 - 11640 PD_UL_TBF_VOLUME_THR_3 - 11641 PD_UL_TBF_VOLUME_THR_4 - 11642 PD_UL_TBF_VOLUME_THR_5 - 11643 PD_UL_TBF_VOLUME_THR_6 - 11644 PD_UL_TBF_VOLUME_THR_7 - 11645 PD_UL_TBF_VOLUME_THR_8 - 111646 PD_UL_TBF_VOLUME_THR_9 - 10003 DSF

7.9.2.2.6.3 Cell The expected parameters are (in this order):

- 10001 BSS - 10768 CI - 10769 LAC - 10005 BTS - 10049 BS_PBCCH_BLKS - 10050 BS_PRACH_BLKS - 11127 MAX_PDCH - 11128 MIN_PDCH

7.9.2.2.6.4 BTS entity Cell The expected parameters are (in this order):

- 10001 BSS - 10005 BTS - 11565 BTS_NB_EXTRA_ABIS_TS




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

Evo

lium

.

BTS_NB_EXTRA_ABIS_TS value is the value coming from BSCGP, in EXTRA ABIS POOL CONFIGURATION REQUEST/ EXTRA ABIS POOL CONFIGURATION INDICATION.

The O&M values, sent by the OMC-R to the MFS on a cell basis (N_EXTRA_ABIS_TS_MAIN -number of Extra TS configured on the main sector of a cell-, N_EXTRA_ABIS_TS_SECONDARY -the number of Extra TS configured on the secondary sector of a cell in case of cell shared-) are not used (and not present at O&M/ telecom interface)

7.9.2.3 pvc structures description

7.9.2.4 pvc messages description

7.9.2.4.1 PVC-SET-req

This message is used to request the observation on PVC instances. Message type: PVC-SET-req Direction: Control Station to GPU


PvcReportReqDataElement

OmRef OmPvcPmRef U_int

BssRef PvcPmRef U_int

7.9.2.4.2 PVC-SET-reqREPORT-Cnf

This message is used to request the observation on PVC instances. Message type: PVC-SET-reqCnf Direction: GPU to Control Station


PvcReportCnfDataElement

PvcReportCnf [127] maximum of 127 instances. To report more instances, the linked replies must be used (filler).

EndOfInfo 01h = Not the last info 00h = Last Info

unsigned short




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

Evo

lium

.

7.9.3 BSC entity

7.9.3.1 bsc structures description

7.9.3.2 bsc messages description

7.9.3.2.1 Bsc-Report-Req

This message is used to request the observation on Bsc instances. Message type: PVC-SET-req Direction: Control Station to GPU


BscReportReqDataElement

OmRef OmBscPmRef U_int

BssRef BscPmRef U_int

7.9.3.2.2 Bsc-Report-Cnf

This message is used to report the observation on bsc instances. Message type: PVC-SET-reqCnf Direction: GPU to Control Station


FrBcReportCnfDataElement

BscReportCnfGlobal only one bsc per GPU.

7.9.4 FrBc entity



7.9.4.2.1 FrBc-Report-Req

This message is used to request the observation on FrBc instances. Message type: PVC-SET-req Direction: Control Station to GPU


FrBcReportReqDataElement

OmRef OmFrBcPmRef U_int

BssRef FrBclPmRef U_int




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

Evo

lium

.

7.9.4.2.2 FrBc-Report-Cnf

This message is used to report the observation on FrBc instances. Message type: PVC-SET-reqCnf Direction: GPU to Control Station



FrBcReportCnf [127] maximum of 127 instances. To report more instances, the linked replies must be used (filler).


unsigned short

7.9.5 lapDLink entity

7.9.5.1 lapDLink structures description

7.9.5.2 lapDLink messages description

7.9.5.2.1 LapD-Report-Req

This message is used to request the observation on LapD instances. Message type: PVC-SET-req Direction: Control Station to GPU


LapDReportReqDataElement

OmRef OmLapDlinkPmRef U_int

BssRef LapDlinkPmRef U_int

7.9.5.2.2 LapD-Report-Cnf

This message is used to report the observation on LapD instances. Message type: PVC-SET-reqCnf Direction: GPU to Control Station



LapDReportCnf [8] maximum of 8 instances. To report more instances, the linked replies must be used (filler).


unsigned short




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

Evo

lium

.

8 GLOSSARY AND ABBREVIATIONS

BAM Board and Alarm Management

BCF Base Station Control Function (BTS)

BCM Bearer Channel Management

BSC Base Station Controller

CML Communication Management Layer

FAP Functional Access Point

GEM Global Equipement Manager

GLM General LCS Manager (manages LCS logical data model)

GOM GPRS O&M

GPU GPRS Processing Unit

GRS GSM Radio System

IFAP Instance of Functional Access Point (TOMAS)

LCS LoCation Service

LRM smLc Resource Manager (interfaces all other components with O&M subsystem for configuration and state management)

MFS Multi-Function Fast Server

PLMN Public Land Mobile Network

RRM Radio Resource Management

TRM Telecom Resource Management

END OF DOCUMENT

mfs internal interfaces messages definition b9 ed06.pdf

Documents