Change Ocb283 - Hc3.1

DESCRIPTION OF OCB283 HC3.
1 CHANGES
Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001
Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001
Page 1
Page 1
DESCRIPTION OF OCB283 HC3.1 CHANGES

Contents
1. Overview of the product
2. Description of hardware changes
3. Description of functional changes
4. Changes to operation and maintenance
Page 2
NOTES
Page 2

Contents
1.1 OCB 283 architecture
1.1.1 Requirements for change
1.1.2 Solutions
1.1.3 Conditions
1.2 OCB HC2.1 changes
1.2.1 Principle of ATM switching
1.2.2 OCB HC2.1 architecture
1.3 OCB HC3 changes
1.3.1 OCB HC3.1 architecture
1.3.2 Target OCB HC architecture
1.3.4 Performance
1.4 Self-assessment
Page 3
NOTES
Page 3

OS LEVEL
Charging
SMM
SMC
SMC
-----MIS/MAS token ring
SMT2G
SMT2G
STS 1G
PCM
SMX
SMX
E
T
U
SMA
SMA
RCX
LR
LR
Page 4
NOTES
PCM: 32 TS, 8 bits per channel, 2 Mbit/s
LR: 32 TS, 16 bits per channel, 4 Mbit/s
Maximum connection capacity: 2048 LR
Page 4

THE OCB 283 NEEDS TO CHANGE TO ...
Respond to changes in the telecommunications world (more

IN calls, mobile calls, data transfer, etc)
Offer greater connection capacity
Reduce product costs
Improve our responsiveness
Page 5
Page 5

SOLUTIONS
Change of switching network
Change of control
Change of LAN
Federating architecture
Multi-TU architecture
Open access to the Unix world, server connections
Page 6
NOTES
Change of control: performance objectives: 8 MBHCA at 0% IN, 4 MBHCA at 100% IN
Change of switching network: adoption of an ATM switching network
Change of LAN: MIS and MAS are replaced by 16 Mbit/s token ring (2 to 8 rings in N+1 config)
Change of stations: based around new processors (power PC and power QUICC), increasing station
performance by a factor of 10
Federating architecture: stations are standardized (general purpose)
Multi-TU architecture: PCM TUs are now complemented with SDH TUs and ATM TUs (HC3.2)
Open access to the Unix world: to increase our productivity and our responsiveness
Page 6

CONSTRAINTS
To retain a maximum of existing software
To retain compatibility with the current environment
To retain product modularity (range)
Page 7
Page 7

SWITCHING STAGES
VC switching (VCC)
VCI
2
VCI
1
VCI 1
VCI 2
VPI 1
VCI 1
VCI 2
VPI 4
VCI
4
VCI
3
VPI
3'
VPI
1'
VCC
Virtual Channel Connections
VPI
2'
VPI 2
VCI 4
VPI 3
VCI 3
VCI 1
VCI 2
VPC
Virtual Path Connections
VPI 5
VP switching (VPC)
Page 8
NOTES
VCI: Virtual Channel Identifier
Reference of a channel relative to a path. In the RCH-BE context, identifies a cell on a VPC between
two TCAs (temporal to composite ATM links).
VPI: Virtual Path Identifier
Reference of a virtual path.
In the OCB HC2.1 and HC3.1, only VP switching is included.
Page 8

FORMAT OF AN ATM CELL
8
7 6
GFC
VPI
VPI
VCI
2
3
VCI
PT
VCI
Bits
bytes
CLP
HEC
5 Header bytes
4
5
6
PAYLOAD
48 Payload
bytes
Fields
CLP
: Cell Loss Priority
GFC
HEC
: Generic Flow Control

: Header Error Control
PT
: Payload Type
VCI
VPI
: Virtual Channel Identifier

: Virtual Path Identifier
Payload : useful information
53
Page 9
NOTES
GFC
: not used at network level (exists only at the user/network interface)
VPI
: path number (on 8 at the user/network interface

on 12 at the network interface)
VCI
: Virtual Channel Identifier (within the path)

analogy: electrical sheathing
VPI
cable within the sheathing VCI

PT
: type of information conveyed (user, signalling, O&M)
CLP
: cell loss priority

eg: a user is entitled to 2 Mbytes and uses 2.100 Mbytes,
the additional 100 Kbytes have loss priority
HEC
: the header's calculated CRC
Page 9

COMPOSITE ATM CELL
Change from frame format (G.704 PCM) to ATM format
Addition of an adaptation layer (AAL1)
Payload made up of TSs from several N x 64 kbit/s channels
Protection provided by 7 "defence" bytes
ATM cell (53 octets)
1st bit sent

Header
5 bytes
AAL1
1b.
last bit sent

39
40 "speech" bytes (TS_64)
"defence"
7 bytes
Page 10
NOTES
Page 10

OS LEVEL
Charging
SMM
SMC
SMC
-----MIS/MAS token ring
SMT2G
STS 1G
PCM
SCH
SCH
E
T
U
SMA
RCH
SMA
OCB HC2.1
Page 11
NOTES
- The HC2.1 release entails replacing the switching network with an ATM matrix.
- The OCB system at release HC2.1 does not offer additional bit rates to subscribers connected to it.
Page 11

1.4 OCB HC3 changes
OS LEVEL
DHA
Billing
Collector
CDRA
LSN Nectar
SMM
SMB_C
------
SMB_C
OCB HC3.1
Token ring
STS 1G
SMT2G
PCM / SDH
SMA
TS V5.2
SMB_XT
SMB_XT
E
T
U
SMB_A
N7
RCH
Page 12
NOTES
CDRA: Call Detail Record Application
DHA: Data Handling Application
Page 12

1.4 OCB HC3 changes
NMC2
DHA
SMM_IT
SU2A
Billing
Collector
CDRA
LSN Nectar
SMB_C
------
SMB_C
Target OCB HC3
Token ring
SMB_XT
STS 2G
PCM
SDH TDM
SDH ATM
SMB_XT
E
T
U
SMB_A
SMB_A
RCH
Page 13
NOTES
The HC product, from release HC3.2 requires the presence of NMC2.
ALCA: ATM Logical Connection Application
LRCP: Local RCP
Page 13

1.4 OCB HC3 changes
Performance
Number of
subscribers
Number of LR
links
Number of circuits
Number of
signalling routings
Number of
adjacent SPs
Number of SLCs
OCB 283 (R23)

200 000
HC2.1
200 000
HC3.1
200 000
Target
500 000
2048
2048
16 384
16 384
60 000
255
60 000
255
480 000
255
480 000
511
255
255
255
511
434
434
3528
3528
Page 14
NOTES
In call handling terms:
330 CA/s with the conventional OCB, up to 2000 CA/s with the OCB HC.
That is: 1.2 MBHCA with the conventional OCB, 7.2 MBHCA with the OCB HC.
Page 14

1.4 Self-assessment
Allocate the following terms to the appropriate release(s):
OCB
HC2.1
HC3.1
Target OCB HC
CDRA
DHA
LSN NECTAR
MAS
RCH
SMA (SS7)
SMA
SMB_A V5.2
SMB_XT
SCH
SMX
Page 15
NOTES
Page 15

Contents
2.1 Changes to the switching network

2.2 Communication
2.3 SMB basic architecture
2.4 SMB specific architecture
2.5 Nectar platform
2.6 Case study
Page 16
NOTES
Page 16

MIS/MAS token ring
SMT2G
SMT2G
PCM
SMX
SMX
E
T
U
SMA
SMA
Non HC OCB
RCX
LR
Token ring
SMT2G
PCM / SDH
SMA
TS V5.2
SMB_XT
SMB_XT
E
T
U
LR
RCH
SMB_A
N7
OCB HC3.1
Page 17
NOTES
Page 17

ATM matrix
Cell assembly
LR
or
LRH
Cell
switching
ATM links
AEI
80 Gbit/s
(128x622 Mbit/s)
Cell disassembly
1 AEI
622 Mb/s
128 LR
RCTCA2
16 AEI
bidirect.
622 Mb/s
BBASE
Page 18
NOTES
The assembly comprising RCTCA2 boards is for connecting 16384 LR links at 4 Mbit/s.
The assembly comprising BBASE boards switches up to 128 AEI links at 622 Mbit/s, or a switching
matrix at 80 Gbit/s.
Page 18

Connection
+
Cell assembly/disassembly
Connection
+
Cell assembly/disassembly
ATM matrix
BBASE
RCTCA2
128 LR
15
16 AEI ports
RCTCA2
2048 LR capacity
Page 19
NOTES
16 BBASE ports.
128 LR on each RCTCA2.
Or a capacity of 2048 LR.
Page 19

RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
BBASE
N1
BBASE
N2
.
. of 16 384 LR
128 LR * 8 RCTCA2 * 16 BBASE Capacity
.
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
RCTCA2
BBASE
N16
BBASE
N17
.
.
.
.
.
BBASE
N24
Page 20
NOTES
Page 20

Module concept
One pair of SMBs drives up to four modules.
One module can comprise:

Matrix boards only (4 max)
Connection boards only
Matrix boards and connection boards
Two module types: RCH_4 or RCH_6

Four or six slots for boards and appliques
One converter slot
Page 21
NOTES
Page 21

A module is equipped with:

Matrix
BBASEB2 board
BASEE2 applique
Connection
RCTCA2 board, cell assembly/disassembly for 128 LR
RAGLR2, RALALR, RALAH appliques
Power supply
AE35B board, 3.3 V and 5 V dual-voltage converter
AA35B2 applique
Page 22
NOTES
Page 22

Connection appliques
RAGLR2
One AEI link
128 LR
RALALR
One AEI link
64 LR + 1 LAH
RALAH
One AEI link
Two LAH
Page 23
NOTES
LAH: High capacity access link, equivalent to 64 LR (8GLR).
Page 23
3 - PRACTICAL WORK
Using the HC3 GUIMES
3.1. Conformity
Using the GUIMES (Commissioning Guide)
Checking racks and HC3.1 dedicated boards
Checking the programming of HC3.1 boards and appliques
AACRH mini-boards in SM stations
AASBT appliques in SMB stations
IAIDA appliques in IBTUX subracks
Checking HC3.1 inter- and intra-racks connections
Page 24
NOTES:
Page 24
2. Description of hardware changes 2.1

Changes to the switching network
Token Ring
SMB_XT
ETU
SCHA1
SCHAi
Coupleur
Coupleur
I
C
L
/
I
S
L
TCA0
...
TCA2
TCA3
I
C
L
/
I
S
L
...
I
C
L
/
I
S
L
Branche A
...
ASE0
Page 25
NOTES
The BBASE and RCTCA2 boards are managed like ETUs.

The SCH stations (HC2.1) can coexist with SMB_XT stations.
Page 25

2.2 Communication
Requirements
To increase LAN capabilities to respond to increased
SMB performance
To create a LAN to connect local servers to the OCB
platform
Constraints
Compatibility with existing systems
Page 26
NOTES
Page 26

2.2 Communication
Non HC OCB
SMM
One 4 or 16 Mbit/s token ring
MIS
SMC
------
SMC
One to four 4 or 16 Mbit/s token rings

MAS
SMT2G
SMT2G
SMX
SMX
E
T
U
SMA
SMA
RCX
LR
Page 27
NOTES
Each ring comprises two branches A and B operating in loadsharing mode.
Page 27

2.2 Communication
OCB HC3
10 Mbit/s Ethernet bus
Server platform
SMM
SMB_C
-----
Two to eight 16 Mbit/s

token rings
SMB_C
Token ring
STS 1G
SMT2G
PCM / SDH
SMA
TS V5.2
SMB_XT
SMB_XT
E
T
U
SMB_A
N7
RCH
Page 28
NOTES
Page 28

2.2 Communication
In non-HC technology
One MIS token ring at 4 or 16 Mbit/s consisting of two
branches in loadsharing mode
One to four MAS token rings at 4 or 16 Mbit/s
comprising two branches in loadsharing mode
In HC3.1 technology
Two to eight 16 Mbit/s token rings operating in N+1
configuration
Page 29
NOTES
Page 29

2.2 Communication
Communication interface between the OCB platform and
the server platform
Servers
Servers
Servers
Duplicated, loadsharing
SMB GW
SMB GW
Page 30
NOTES
Page 30

OS LEVEL
DHA
Billing
Collector
CDRA
LSN Nectar
SMM
SMB_C
-----
SMB_C
OCB HC3.1
Token ring
STS 1G
SMT2G
PCM / SDH
SMA
TS V5.2
SMB_XT
SMB_XT
E
T
U
SMB_A
N7
RCH
Page 31
NOTES
Page 31

POWER PC, POWERQUICC

High performance processors (7 times better than
previous generation)
Future-proofed production
Page 32
NOTES
These processors replace the Motorola 68020 and 68030 processors.
Page 32

NEW FORMAT
12-layer printed circuits
Appliques supporting wiring connectors
Page 33
NOTES
Page 33

Main concepts
Drawer
Appliques
Back plane
Boards
Page 34
NOTES
Page 34

PowerPC
Page 35
NOTES
Page 35

Connectors
Page 36
NOTES
Page 36

Rear view of the subrack

Appliques inserted
Page 37
NOTES
Page 37

General-purpose control station
Consisting
of a number of agents intercommunicating via an MMB

station bus (Multiprocessor Memory Bus)
Processor for processing
I/O coupler
Signalling coupler
Each
agent physically comprises boards and appliques
Dialogue
between a board and its appliques is conducted via the LAB bus
(Local Access Bus)
Page 38
NOTES
There are three types of agent (processing processor, I/O coupler, sig coupler).
The convention is to refer to a board, an agent and its appliques.
The agents communicate via a Multiprocessor Memory Bus.
Page 38

LR
Token ring, Ethernet, ICL/ISL
SMB
I/O
I/O
I/O
SAB (A)
SAB (B)
LAB BUS
MLA
bus
Signalling
Processor block
Processor block
Processor block
Interchange memory
Interchange memory
Interchange memory
MMB bus (synchronous, 320 Mbit/s, 32 bits)

Call handling processor agent
I/O coupler agent
Signalling coupler agent
Page 39
NOTES
The SMB station comprises five bus types:
MMB bus:
Synchronous, 320 Mbit/s, 32 bits.
Handles interchanges between the various agents within a station.
LAB bus:
Multiplexed at up to 200 Mbit/s, 32 bits.
Handles interchanges between a board, an agent and its appliques. Its architecture
enables several appliques to be linked to one board.
-MLA bus:
Bus multiplexed at 4 * 16 Mbit/s (4 GLR).
Handles interchanges between the SAB functions and signalling coupler agents, conveys
signalling information from the switching network.
ICL bus:
Asynchronous, serial, 4 Mbit/s.
Handles interchanges between the ETUs and the control station.
ISL bus:
Asynchronous, serial, 512 kbit/s or 1 Mbit/s.
Handles interchanges between control and station elements (ETU included) for:
Hardware fault supervision.
Reset control in the context of ETUs.
Page 39

The SMB's agents are implemented on three board types:
ACPWU:
FUNCTION
Call handling processor agent
Token ring I/O coupler agent
Ethernet I/O coupler agent
CONNECTION
Connected to the MMB bus
Connectable to a local LAB bus
IMPLEMENTATION
Motorola Power PC 750 processor
512 Mb of RAM
Page 40
NOTES
The ACPWU board is connected to the MMB bus since, as the station's processor, it has to
exchange information with the SMB's other agents.
It can be connected to the LAB if it has to manage appliques.
Page 40

ACMPR:
FUNCTION
Secondary agent
Multiprotocol signalling coupler agent
CONNECTION
Connected to the MLA bus
Connected to the MMB bus
IMPLEMENTATION
Motorola Power PC 750 processor
512 Mbytes of RAM
Three signalling functions, each comprising:
Eight signal processors, Texas Instruments DSPs
A PQUICC processor
Page 41
NOTES
The ACMPR board has an ADSMO daughter board. Together, they handle the functions described
here.
This board is interfaced with the LA links (from the SAB) that are multiplexed to form the MLA bus.
Page 41

ACAUX:
FUNCTION
ICL/ISL I/O coupler agent
CONNECTION
Connected to the LAB bus
IMPLEMENTATION
Three processing functions, each having:
A PQUICC processor
Page 42
NOTES
The AUCAUX board handles, among other things:
-ICL/ISL coupler
-MAL
-timekeeping
Page 42

To sum up...
Processor
Token ring I/O coupler
Ethernet I/O coupler
ACPWU board + appliques
Signalling coupler
ACMPR board + appliques
ISL/ICL I/O coupler
ACAUX board + appliques
Page 43
Page 43

Appliques
AAETH
Function
Interface for two 10 Mbit/s Ethernet links
Ethernet 0
HUB A
LAB
ACPWU
AAETH
bus
Ethernet 1
HUB B
S
E
R
V
E
R
S
Page 44
NOTES
Page 44

AAAUX
Function
Timebase interface, ICL/ISL and MAL adapter
ACPWU
LAB
bus
ACAUX
AAAUX
External links:
ICL/ISL
clock
MAL
Page 45
NOTES
Page 45

AATRA
Function
Coupler for two token rings, 16 Mbit/s
ACPWU
AATRA
2 Token Ring
AATRA
2 Token Ring
LAB
bus
Page 46
NOTES
Page 46

AAMLA
Function
Link with a switching network. SAB function for 16 LR
ACMPR
AAMLA
16 LR
X
RCH
branch A
MLA
bus
AAMLA
16 LR
X
RCH
branch B
Page 47
NOTES
If an applique develops a fault, the SMB remains operational.
Page 47

AASBT and AATAD polarizing appliques
AASBT
MMB, MLA and ISL impedance matching
MMB station bus arbitration
AATAD
MMB, MLA and ISL bus impedance matching
Alarm ring insertion (MAL)
MMB, MLA and ISL bus

AASBT
AATAD
MAL
SMB agents
Page 48
NOTES
Page 48

AATCU
Function
15 other stations
Connecting stations to a token ring
AATCU
ACPWU
AATRA
AATCU
LAB
bus
AATCU
AATRA
AATCU
Ring 1
Ring 2
Ring 3
Ring 4
Page 49
NOTES
The AATCU appliques does not belong to an appliques but can be installed in it.
It is used to insert 16 stations on the same token ring.
Page 49

SMB power supply:
Board: AE35B
Applique: AA35B2
3.3 V and 5 V dual-voltage converter
48 V power input applique
Page 50
NOTES
Page 50

Basic SMB equipment:
A main multiplex coupler for access to the token rings (CMP)
An alarm collection coupler (TAD)
A bus impedance matching function (SBT)
Page 51
NOTES
Page 51

Additional equipment in an SMB:
One or more secondary multiplex couplers for accessing the token
rings (CMS)
One or more processor units
One or more multiprotocol couplers

An Ethernet coupler
An auxiliary coupler
A token ring distribution frame function
Page 52
NOTES
Page 52

Three types of SMB module
SMB_5
Five board slots
One converter slot
SMB_8
Eight board slots
Two converter slots
SMB_10
Ten board slots
Three converter slots
Page 53
NOTES
Page 53

AA35B2
AASBT
AAAUX
AAxxx
AAxxx
AATAD2
AE35B
ACAUX
ACxxx
ACxxx
ACxxx
One slot reserved for a converter

Five slots for boards and appliques
ACPWU
SMB_5
Page 54
NOTES
Page 54

AAAUX
AATRA
AAxxx
AAxxx
AAxxx
AAxxx
AATAD2
ACAUX
ACxxx
ACxxx
ACxxx
ACxxx
ACxxx
AASBT
ACPWU
ACPWU
AA35B2
AE35B
SMB_8
AE35B
Two slots reserved for a converter

Eight slots for boards and appliques
Page 55
NOTES
Page 55

AASBT
AAAUX
AAxxx
AAxxx
AAxxx
AAxxx
AAxxx
AAxxx
AAxxx
AATAD2
ACxxx
ACAUX
ACxxx
ACxxx
ACxxx
ACxxx
ACxxx
ACxxx
ACxxx
ACxxx
AA35B2
AA35B2
AE35B
SMB_10
AE35B
AE35B
Three slots reserved for a converter

Ten slots for boards and appliques
Page 56
NOTES
Page 56

SMB_XT, RCH + TU control

S
B
T
T
A
D
A
C
P
W
U
A
C
A
U
X
A
C
P
W
U
A
U
X
T
R
A
A
E
3
5
B
Time
ICL/ISL
Two token rings
Page 57
NOTES
Page 57

SMB_CAXT, minimum configuration

S
B
T
T
A
D
A
C
P
W
U
A
C
A
U
X
A
C
M
P
R
A
C
P
W
U
Multiplexed LA
A
U
X
M
L
A
M
L
A
T
R
A
E
T
H
A
E
3
5
B
A
E
3
5
B
Time
ICL/ISL
LR to
network
Two token
rings
Two
Ethernet
links
Page 58
NOTES
Page 58

Subrack : RBRCH
HIGH RATE MATRIX CONTROL STATION
1/2 SCH subrack: two TCA slots, four ASE slots
HC2 version (2048 LR) ASE slots mostly unused
SCH A
SCH B
Page 59
NOTES
Page 59

Subrack : AB2S
Control (SMB_C, SMB_A)
Matrix control (SMB_X)
Termination (trunk) control (SMB_T)
Mix (SMB_CAXT)
SMB
Two local buses with two
slots and two local buses
with three slots
SMB
Two local buses with two
slots and two local buses
with three slots
Page 60
NOTES
Page 60

TU + RCH SUBRACK/TWO BRANCHES : IBTUX
TU modules
12 16 PCM TU or 13 STM1/VC12 TU (including one
backup)
Associated RCH_4 modules
256 LR and one ASE or 512 LR (eight LAH)
TU module that can fitted with a mix (TU_BB, EC)
RCH
Branch A
TU module
RCH
Branch B
Page 61
NOTES
Page 61

Subrack : ABX2S
Subrack comprising two backplanes
One accommodating matrix/trunk control (SMB_XT)
One RCH_6 module
SMB
5 slots
RCH
Branch A
SMB
5 slots
RCH
Branch B
Page 62
NOTES
Page 62

BASIC SUBRACK : ABS2S
Two separate backplanes
Left SMB_8 + STS-SSE
Right SMB_8
Typical SMB_CAXT mixed configuration
SMB 8 slots
Compact
Small
STS + SSE
SMB 8 slots
Compact
Small
Page 63
NOTES
Page 63

Tiroir de lovage
BAIE HC01
Ventilation imprative
UNITE DE VENTILATION
Bac
Scurisation N+1
Bac
Bac
Page 64
NOTES
Page 64

HR_00 rack
HC 2.1. configuration
RBRCH
RBRCH
Page 65
NOTES
En HC2.1, on trouve la baie HR_00 avec le bac du milieu vide.
En HC2, on ne parle pas de module. Un RCH de 2048 LR est constitu physiquement de 4 SCHi (
1<i<4 ). Chaque SCHi gre un maximum de 512 LR en utilisant le bac d extension situ en bas de
baie HR00.
Page 65

SDH connection
E10
ADM
E10
ADM
SDH
2 Mbit/s PCM link
ADM
ADM
E10
E10
Page 66
NOTES
ADM: Add & Drop Multiplexer.
Converts a 2 Mbit/s PCM link to an SDH link.
For example, an STM1 SDH link at 155 Mbit/s (in HC3.1).
Page 66

Requirements
To reduce the cost of interexchange connections

Connecting 63VC12 SDH to SMB
Compliance with reliability standards

Introducing the "ETU backup" function
Introduction of SDH management into the E10

Equipping E10 with SDH ports
Page 67
NOTES
Page 67

Solutions
Introducing SDH management into the E10

Equipping E10 with SDH ports
STM1 VC12 SDH TU

Line backup in 1+1 mode
TU backup in N+1 mode
Page 68
NOTES
STM1: 155 Mbit/s rate

VC12: 2 Mbit/s virtual container
Page 68

Organized into capacity modules
12 TU + one slot for backup
Each module is driven by a pair of SMBs
A pair of SMBs can drive up to four TU modules
The TU module is connected to the RCH by high rate links
(LAH), equivalent to 64 LR
Page 69
NOTES
GLR = group of LR links = 8 LR
LAH = 8 GLR = 64 LR
Page 69

Connecting SDH ETUs
SMB
SMB
Normal STM1-63VC12 SDH line

ICL/ISL bus
External
network
63VC12
ETU
LAH
Internal network
Branch A
Internal network
Branch B
Backup STM1-63VC12 SDH line

Page 70
NOTES
Each TU is managed by a pair of SMBs.
STM1 SDH: 155 Mbit/s.
63VC12: Conveys the equivalent of 63 2 Mbit/s PCM links.
The links between SDH TU and RCH are by LAH, equivalent to 64 LR.
Page 70

Normal operation
RAB bus
SDH lines
ETU
63VC12
SDH lines
ETU
63VC12
SDH lines
ETU
63VC12
SDH lines
ETU
63VC12
LAH
SAB
SAB
Carte
ALS
ALS
board
SAB
SAB
ETU
63VC12
Redundancy appliques
Backup ETU
Page 71
NOTES
Each applique receives two SDH lines (1+1 protection).
The ALS board is for connecting the backup LAH to the protected LAH.
The RAB and ALS boards are controlled from the backup ETU.
Page 71

Backup ETU
ETU to back up
RAB bus
SDH lines
ETU
63VC12
SDH lines
ETU
63VC12
SDH lines
ETU
63VC12
SDH lines
ETU
63VC12
LAH
SAB
SAB
Carte
ALS
ALS
board
SAB
SAB
ETU
63VC12
Redundancy applique
Backup ETU
Page 72
NOTES
Page 72

Boards
ACPSI
Power input to TU subrack
ICALS
TU protection
ICS1C
Processing STM1 links carrying circuits in VC12 mode
Page 73
NOTES
The ICALS board has no applique.
Page 73

Appliques
IASUP
connecting optical STM1
IAS1E
connecting electrical STM1
IAILA
marshalling LAH, timing signal distribution, ICL/ISL interface
IAIRA
redundancy applique
IAIDA
AEI and alarms applique
Page 74
NOTES
On the IASUP appliques, the lines are protected (1+1).
On IAS1E (electrical connection), the lines are not backed up. Lines typically used between two
buildings.
Page 74

IAILA
IAS1E
IAS1E
IAS1E
IAS1E
IAS1E
IAS1E
IAS1E
IAS1E
IAS1E
IAS1E
IAS1E
IAS1E
IAIRA
IAILA
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICS1C
ICALS
IAIDA
12+1 ICS1C ETU boards (SDH connection)

Electrical appliques
ICALS
ACPSI
AAPI48
IBTUX
Page 75
NOTES
Page 75

2.5 Nectar platform
OS LEVEL
DHA
Billing
Collector
CDRA
LSN Nectar
SMM
SMB_C
-----
SMB_C
OCB HC3.1
Token ring
STS 1G
SMT2G
PCM / SDH
SMA
TS V5.2
SMB_XT
SMB_XT
E
T
U
SMB_A
N7
RCH
Page 76
NOTES
Page 76

2.5 Nectar platform
Local OAM
Remote OAM
LAN IP
NECTAR
platform
Worker
STATION
Non control
STATIONS
NECTAR
GATEWAY
(SMB)
OCB
platform
LSN
GATEWAY
(SMB)
GATEWAY
(SMB)
OCB LAN
SM
SM
SM
Page 77
NOTES
Page 77

2.5 Nectar platform
Remote OS Modems Local OS
DS 10
X25, ISDN
Ethernet
Compaq
ROUTER
Basic
Eth 100/10
DS 10
RS232
Compaq
RS232 adapt
Hub or Ethernet switch

(NECTAR LSN)
Eth 100/10
equip-
Basic
equip-
ment
ment
SMB
SCSI
SCSI
Shared disks
Page 78
NOTES
Page 78

2.5 Nectar platform
SV_01 RACK: 19 (0.6 x 0.9 x 2)

Supports standard products
Follows the IT market
220 V power supply
UC-Unix DS 10
UC
Disks
UC
UC
Disks
UC
HUB
HUB
Router
Page 79
NOTES
Page 79

2.6 Case study
Change to the switching network

SMB_XT station
SDH connection
Page 80
NOTES
Page 80

2.6 Case study
You are working with the OCB exchange as shown below ...
OCB HC3.1 exchange
Subscriber line type configuration
OS LEVEL
DHA
CDRA
LSN Nectar
SMM
SMB_C
-----
Billing
Collector
SMB_C
Token ring
STS 1G
SMT2G
SMA
TS V5.2
SMB_XT
SMB_XT
1024 PCM
E
T
U
RCH
SMB_A
N7
=> 128 GLR total
CSNL
Page 81
NOTES
Page 81

2.6 Case study
Question 1: Switching network
How many BBASE boards form the matrix of this exchange (one
branch)?
Tip: the number of LR links means so many RCTCA boards which
means so many BBASE boards.
Question 2: SMB_XT
Draw the rack configuration of an SMB_XT for this exchange in an ABX2S subrack.
Page 82
NOTES
Page 82

2.6 Case study
Question 3: SDH connection
On a transit exchange as follows, draw the rack configuration of the RCH network (one branch) in RCH_4
and RCH_6 subracks
Tip: Appliques are needed for the LR links, and others are needed for the links from the SDH (LAH).
STS 1G
SMT2G
SMA
TS V5.2
SMB_XT
SMB_XT
30 STM1/SDH
E
T
U
16 GLR total
SMB_A
N7
RCH
Page 83
NOTES
Page 83

Contents

3.2 Control stations
3.3 TU management
3.4 Defence
3.5 Case study
Page 84
NOTES
Page 84

Requirements
High capacity exchanges
To increase exchange connection capability
To increase switching network connection capability
Functional impact
The software must be able to address the LR links
beyond the current limit of 2048 LR
Page 85
NOTES
Page 85

Current addressing
16 bits
COM
LRX
3 bits
8 bits
8 COM
TS
5 bits
32 channels
256 LR
Page 86
NOTES
256 LR links addressable on eight different COM, or 2048 LR addressable.
The concept of switch (COM field) is no longer required in LR addressing because it is no longer
representative.
Page 86

To be able to address 16384 LR
Extend the network addressing field
As of now, provide dimensioning supporting a far
greater increase in capabilities
Extension of the address field

Network addressing on 19 bits
Page 87
NOTES
Page 87

Network addressing
ADCX
19 bits
LRX
TS
14 bits
5 bits
RCH internal addressing

ADCX
19 bits
GGLR
GLR
LR
8 bits
3 bits
3 bits
TS
5 bits
Page 88
NOTES
LRX on 14 bits, which provides addressing capability up to 16384 LR
In RCH internal addressing:
256 GGLR adressable, eight GLR in each, eight LR in each GLR, or 16384 LR.
Page 88

FUNCTIONAL IMPACTS
Change of messages using network addressing

Change of software processing the network addressing
fields
Increased size of files for which addressing is by COM/LRX
Page 89
NOTES
Example:
MLMR - MLMQ connection setup mesages
Change of MLCOM, MLURM and other software
Change of ZGX, OM and other archive files
Page 89

UR addressing
Current addressing does not have to change
16 bits
ALR
7 bits
UR
8 bits
256 UR
128 ALR
Page 90
NOTES
128 LR addressable on 256 UR, or 32768 LR addressable.
Page 90

O&M changes
Station management: SMxx, ESMxx
TCA and ASE ETU management: ETUxx
LA control function: GLRCT
GLR interrogation: GLRIL
RCH observation management: OCPRO and OCAGE
Change of LRX and GLR parameters: LDxx, QMCxx, FSMxx, etc
Page 91
NOTES
Page 91

The RCH connection service involves:
Two ML (software machines)

MLGX on SMB_C
MLCOM on SMB_X
Two OL (software units)

OL TCA resident on TCA type ETU
OL ASE resident on ASE type ETU
Page 92
NOTES
Page 92

Change of distribution of functions
ML GX
Connection control
Speech connection service
Overall recognition of MCX breakdown in SMXs
Recognition of SMX positioning
ML GX
Connection control
Speech connection service
Overall recognition of RCH breakdown in SMBs
Recognition of SMB and ETU positioning
ML COM
Detection of faults and reporting to ML GX
Execution of connection controls
Tone connection service
OL TCA
Detection of faults and reporting to ML GX
Execution of connection controls
Tone connection service
ML COM
RCH observation processing
Old architecture
New architecture
Page 93
NOTES
Page 93

Token Ring
SMC or SMB_C
MLGX
SMB_XT
ML SM
ML COM
Branch A
ML SM
ML COM
I
C
L
/
I
S
L
SCHA1
TCA0
...
TCA2
TCA3
I
C
L
/
I
S
L
...
ASE0
Page 94
NOTES
The BBASE and RCTCA2 boards are managed by ETUs.

The SCH stations (HC2.1) can coexist with SMB_XTs.
Page 94

N 7 processing on SMB
The N7 application on SMB provides ...
An increase in traffic capability (7 times better compared to

the SMA)
An increase in the number of signalling links (252 max per

station)
Page 95
NOTES
The HC3.1 product supports the following performance levels:
480 000 CIC
3528 SLC
Page 95

Coupler board capacity
N 7 on SMA
N 7 on SMB_A
ACHIL
16 channel processing capability
ACMPR
63 channel processing capability
Page 96
NOTES
A station can contain up to four ACMPR couplers, or a maximum of 252 channels per station.
14 stations maximum or a maximum of 3528 SLCs.
Page 96

Software architecture
One main component, ML PUPE_N

One secondary component, ML PUPE_I
Up to six coupler components ML PUPE_L
One ML SM for each PQUICC
Page 97
NOTES
Page 97

Software architecture
ACMPR
ACPWU
ACPWU
ML SM_P
ML PUPE_I
ML SM_A
ML PUPE_N
ML SM_A
SM_A
MLML
PUPE_L
ML PUPE_L
(ML AN_P)
(ML ETA_P)
(ML ETA_L)
(MLAN_L)
ETA_L)
(ML
(ML AN_L)
Station bus
Release greater than HC3.1

Page 98
NOTES
In HC3.1, the MLAN and MLETA software machines are on SMA.
N 7 level 2 processing is implemented in the form of two entities:
ML PUPE_L, part of the XUTC archive
ML SM 721, part of the ZSM archive
Page 98

Increase in the number of SLCs per station (255)

Increase in the fields of ACMPR coupler observation messages
Extension to the number of records in the EOCS file
256 records
EOCS
Access by VTSM number
Page 99
NOTES
The EOCS file in the UTC archive is extended to 256 records.
Page 99

Two new counters

WNTPE: number of message signal units lost following congestion
WNTI: number of garbled frames
The records in the EOCS file which stores signalling link observation results have been
changed to accommodate these two counters
Page 100
NOTES
Page 100

SDL concept
To simplify the signalling link management mechanisms
(creating/deleting)
Non-HC technology:
The SDL connection (type 1 or 2 data link) involves the
MLPUPE, MLMR, MLMQ and MLGX
HC3 technology:
The MLPUPE directly sends connect and disconnect
instructions to the MLGX
Concept of SDL eliminated
Page 101
NOTES
Page 101

Connections required
SMT
AFCTE
RCH
AFLRX-E
SMB_A
AFLRX-S
A signalling link set is now created directly with FSMCR.

The concept of SDL disappears, LDCR is no longer used for type 1 or 2 DLs.
Page 102
NOTES
Page 102

Change of O&M, SMB management
Station locavar testing: SMTL
Registration of an SMB with a HUB: HMXMO
Change of O&M, N 7
Description of auxiliary coupler configuration: CFAMO
Signalling link set management: FSMxx
Signalling link interrogation: CSMIN
Observations: TCSxx and SCSxx
Page 103
NOTES
Page 103

Gateway SMBs
Requirement
Access to external services
OCB/server dialogue
Solution
SMB with a gateway functionality
Implementation of TCP/IP and UDP/IP in the SMBs
Page 104
NOTES
TCP/IP will be used for protected dialogue in connected mode.
UDP/IP will be used for datagram mode dialogue.
Page 104

TCP/IP function in the SMB
Implementation of the TCP(UDP)/IP protocol layers on SMB agents
Provision of applications of a set of primitives (TCP and UDP)
Change of routing
Inclusion of observations from the IP world
Page 105
NOTES
The IP packets will need to be able to be routed:
on output: to the MLSM component in charge of the access network at the external address
on input to the destination OCB application
Page 105

Implementation of software on the Ethernet applique
Management of the connection with the outside world
Translation of OCB addresses to IP addresses and vice-versa
Broadcasting of states of external and OCB services required to

dialogue
Page 106
NOTES
In terms of connection management, the software handles, among other things:
distribution of messages over the two Ethernet links
transparency with respect to TCP/IP which sees only one link
The Ethernet coupler provides an IP router function and OCB/Nectar LSN interface
Page 106

Addressing that can be envisaged
Functional: OR group AS
Unit oriented: single AS
Multicast: AND group AS
Page 107
NOTES
Page 107

Situation in the system
SMB agent
Ethernet coupler
Server
ML
Service
TCP UDP
TCP UDP
IP
IP
COM_OCB
COM_OCB
MAC TR
MAC TR
IP
Ethernet
LAN TR
Ethernet
LSN
Page 108
NOTES
Page 108

Addressing - Breakdown into networks
External domain 1
SMB4
SMB1
OCB-1 network
Multiplex
Mli
SMB5
OCB
SMB3
OCB-3 network
MLj
SMB2
OCB-2 network
External domain 2
Page 109
NOTES
The OCB is divided into networks, each comprising a list of ML (AS).
For each pair [OCB network/external domain], election of a priority coupler function from the list of
coupler functions providing access to the external network.
There can be up to 16 OCB networks, described in the FCDOM site file.
Page 109

OCB Server addressing
Domain number
IP address of the service instance
Server OCB addressing

IP address in the OCB domain
Network address
AS of the instance
Page 110
NOTES
The ML OCBs know a service's:
Port number
External OR group AS
Maximum number of instances
OCB Server dialogue:
Selection of an instance of the external service
Choice of the router (Ethernet coupler). Chosen by the COM-OCB
Page 110

Simplex SMB - Duplex SMB
Token Ring
SMB_XT
ETU
ETU
simplex
ETU
simplex
simplex
SMBAi
SMB_XT
ETU
ETU
duplex
ETU
duplex
duplex
Pair of SMB
SMBDi
ETU
ETU
simplex
ETU
simplex
simplex
SMBBi
Page 111
NOTES
To specify a TU from the TCH we have to specify a SMBAi or SMBBi (i=1 to 32)
To specify a TU from the SDH links, we have to specify a SMBDi (Duplex SMB)
Station not involved with ETU : SMBi (i=1 to 88)
Page 111

Other application-oriented impacts
MR extension
Increased processing capabilities
Increase in the number of registers per agent (8192 registers)
MR performance
The MR macro is a critical point in terms of performance
Increase in MACRO_MR performance
Coexistence of PUPE - PC in the same station

sequencing of initialization of these MLs
sequencing of switchover of these MLS
Page 112
NOTES
Page 112

3.3 TU management
A new software machine: ML HD
Supported by SMB_T
Interface with the OM to take account of O&M from or to the
operator
Management of SDH entities (line, protection group, path)

Application-oriented management of ETUs
Page 113
NOTES
The ML HD is located on an SMBD (duplex SMB). An SMBD comprises two SMBe (individual SMBs).
Up to 32 SMBDs can coexist. There can therefore be up to 64 MLHD instances.
Each SMBe has an ICL/ISL link to the 63VC12 ETUs. Consequently, each MLHD can communicate
with all the duplex ETUs of its SMB.
Page 113

3.3 TU management
OM
Operator
(SMM)
Multiplex
ML SM-Ur
ML HD-r
ML SM-Up
ML HD-p
(SMM)
(SMM)
ICL/ISL bus
ICL/ISL bus
Pair of SMBs
supporting ETU
ETU
ETU
SDH
ETU
SDH
SDH
Page 114
NOTES
The MLSM-U is an MLSM component on the management side of the ETUs.
Page 114

3.3 TU management
The ML HD...
is instantiated in each pair of SMBs supporting the

connection function
operates in worker/standby mode
Page 115
NOTES
Page 115

3.3 TU management
Update of worker standby ML HD
The site files must be the same between the two ML HDs.
The worker MLHD notifies the standby MLHD of any change of

site file. The standby MLHD updates its internal files.
The standby MLHD audits the state of its peer to detect any
station crashes and switch to worker mode.
Page 116
NOTES
OM MLHD dialogue
The OM does not know the status (worker or standby) of the ML HDs. It sends its request to the ML
HD group.
Only the worker MLHD processes requests from the OM.
Page 116

3.3 TU management
MLHD / MLURM
Applique
Board
PCM1 termination
Physical
interface
SDH
termination
STM1 SDH
Physical
interface
Managed by MLHD
LAH to the switching

network
PCM63 termination
Managed by MLURM
Page 117
NOTES
The 63VC12 ETU counters are observed using the standard MLURM mechanism.
Page 117

3.3 TU management
Manageable entities
SDH line termination

Path (TP)
Protection group (PG)
Page 118
NOTES
Page 118

3.3 TU management
Functional architecture
PCM 1
SDH
interface
TP
...
SDH line
PCM 63
Protection
group
Protected
SDH line
SDH 0
interface
PCM 1
Protecting
SDH line
SDH 1
interface
...
TP
PCM 63
Page 119
NOTES
Page 119

3.3 TU management
Addressing
Address of the SMB on which the ETU associated with the line is
located
Number of the ETU

Number of the ET
Page 120
NOTES
On a conventional OCB, when addressing a PCM link, AMET = SMT N - Board N - PCM N
Here, the need is for: AM = SMB N, ET=RGTU - RGET
There are two ETs on the ETU (two SDH lines on the 63VC12 board) only in the case of an optical
line. The electrical profile (the default profile) does not support creation of a protection group.
Page 120

3.3 TU management
Administrative status:
Controlled by the operator
ES (in service)
BLOM (isolated by the operator)
Operational status:
The real state of the line
ES (in service)
HS (out of service)
Page 121
NOTES
It is also possible to have NEQ (not equipped) as the administrative state. However, this state is not
directly requested by the operator.
Page 121

3.3 TU management
Additional functions
Automatic laser shutdown (ALS)
Synchronization (Timing marker)
Degraded signal computation
Page 122
NOTES
Page 122

3.3 TU management
Path address:
Address of the SMB on which the associated ETU is
located
Number of the ETU and number of the ET
associated with the path
Operational state:
ES (in service)
HS (out of service)
Page 123
NOTES
There is no administrative state for a path. The operator cannot force its state.
Page 123

3.3 TU management
Address of the protection group:

Address of the SMB on which the associated ETU is
located
Number of the ETU and number of the protection
group
Protection:
APS is the function used to manage the protection
group
Type of protection available: one-way, non
reversible mode
Page 124
NOTES
APS: Automatic Protection Switching
Page 124

3.3 TU management
Protection group: normal operation:
B
A
APS
APS
B
Transmission
equipment
OCB HC
A: SDH line
B : active line
C : passive line
Page 125
NOTES
Page 125

3.3 TU management
Maintenance:
B has failed.
Switchover to C
B
A
C
APS
APS
ONE-WAY
B
Transmission
equipment
B is OK.
No switchover to C
OCB HC
Page 126
NOTES
Page 126

3.3 TU management
Normal operation:
B
A
C
APS
APS
C
B
OCB HC
Transmission
equipment
B is repaired.
Remain on C
Non reversible
Page 127
NOTES
Page 127

3.3 TU management
Flow of messages concerning PCM alarms
63 PCM links per SDH line
facility to connect more than 16000 PCM links
Alarm software processing overload problem
Page 128
NOTES
Page 128

3.3 TU management
Solutions
Disabling PCM alarms if there is an alarm on the SDH path
Alarm confirmation time delay increased from 100 ms to 200 ms
Page 129
NOTES
In the case of an alarm on an SDH path, 63 PCM alarms will not be output (for the 63 PCM links
associated with the SDH line). Only the SDH alarm is output.
Page 129

3.3 TU management
With 128-PCM UR
128 PCM links can be connected to a UR (compared to 16)
223 URs available (no change)
Migration function available, UR (16 PCM) UR (128 PCM)
Page 130
NOTES
The 16-PCM UR to 128-PCM UR migration function means that the objects supported by the PCM
links do not have to be deleted. There is no need to delete before re-creating.
Page 130

3.3 TU management
O&M overview
Linked to extension of URs to 128 PCM links: ABOxx, TAExx, OABLA,
QMCxx ...
SDH line management: LINxx
Protection group management: PGRxx
SDH path management: TPAxx
APS function control: APSMO
SDH element observation: OCPLA
Page 131
NOTES
Page 131

3.4 Defence
Switching network
RCH 16 384 LR
LA
or
LAH
ATM MATRIX
MATRIX
INTERFACE
SAB
LR
or
LRH
8 bits/channel 16 bits/channel
Supp. bit
processing
MATRIX
INTERFACE
AEI
ATM transport and switching

of speech and supp. payload bits
SAB
LR
or
LRH
16 bits/channel
LA
or
LAH
8 bits/channel
Supp. bit
processing
Transmission: traffic duplicated by the SAB function in each branch

Reception: the SAB function selects the TSs on one of the branches of the network
Page 132
NOTES
In reception, the SAB function selects the samples (TS by TS) based on:
the parity bit transported
information computed by system defence
Page 132

3.4 Defence
CONNECTION DEFENCE
RCH is duplicated in two identical branches
Simultaneous connections and disconnections
Containment at SAB level
By selection of the correct sample
Simplified operator actions
By board indication wherever possible
Page 133
NOTES
Page 133

3.4 Defence
CONNECTION SERVICE DEFENCE

To avoid congestion of the ATM switching network following:
Connections not released
Loss of a control unit
Collision detection mechanism
Between two connections having common time-division
multiplex channels
by comparison between the characteristics of
Dthe new connection to be set up (priority)
Dthe old connection (unreleased)
Page 134
NOTES
Collision detection
When a connection is set up, the system checks that the connection does not already exist.
If it does, priority is given to the most recent connection request.
Page 134

3.4 Defence
SCOPE OF RCH DEFENCE OPTIONS
LA control
Local def.
Local def.
GLR defence
LRS
IGID2
SABs
RGTRI
RGCAT
BGQRP
AEI
BGAT6
TCAs
BGAT6
BGHMP
BGQRP
AEI
BGAT6
ASE
BGAT6
BGQRP
LRE
RGTRI
IGID2
LAE
RGTCA
TCAe
SABe
LAS
Local def.
LA control
Ports and AEI
MC1, MC2
Payload CRC, AAL
Page 135
NOTES
MC1,MC2: Maintenance cells
Page 135

3.4 Defence
Control station
Software architecture of an SM (review)
Functional MLs
ML SM:
Primary ML SM: local station defence
Secondary ML SM: agent defence
Hypervisor, supervisor
Defence systems
Station defence
Ring defence
Page 136
NOTES
Page 136

3.4 Defence
Station defence - Fault processing phases
Detection
Detection proper
External supervision
Positioning
Reconfiguration
Reassignment of all of its tasks to a backup station if one exists
Page 137
NOTES
Page 137

3.4 Defence
Defence functions in the system
Centralized defence functions
OM
SM defence
Station management
Ring management
Self-detection
Self-defended means
MLPC
N7 management
MLGX
Connection
management
of communication
Serious fault indication
Page 138
NOTES
Reconfigurations are controlled by:
central defence
the MLPC for MLPUPEs
the MLGX for the MLCOM
Page 138

3.4 Defence
Functional ML redundancy
Loadsharing
ETA, AN, MQ, TR, TX, MR, GX, CC, GS
Worker/standby
URM, HD, PC, OC
Duplicated
COM, GT function ETA
N+1
ML PUPE
Page 139
NOTES
Page 139

3.4 Defence
Requirement
To optimize system availability
reducing degraded operation times
To recognize the new station architecture
To recognize the new agent architecture
Page 140
NOTES
Page 140

3.4 Defence
Changes
Central defence:
reduced switchover time
quicker return to operation
Local defence:
recognition of new fault detectors
new supervision mechanism
Page 141
NOTES
To reduce switchover times, the backup station is preloaded.
Following a software fault, operation is restored by a station reboot with no locavar or reload.
Page 141

3.4 Defence
Preloaded active standby
SMB1
SMB2
SMB3
ML SM
ML SM
ML SM
MLPUPE1
MLPUPE2
MLPUPE3
Starting
MLMR1
MLMR2
MLMR
situation
ML SM
ML SM
MLPUPE2
MLPUPE3
MLMR2
MLMR1
After SMB1
failure
ML SM
ML SM
ML SM
After SMB1
MLPUPE1
MLPUPE2
MLPUPE3
repair
MLMR
MLMR2
MLMR1
Page 142
NOTES
Page 142

3.4 Defence
Server access
Failures to be taken into account
External server failures
Ethernet link failures
Gateway failures
OCB communication level failures
SM failures
Page 143
NOTES
OCB communication level failures are the responsibility of basic defence. No impact on the "server
vision".
Page 143

3.4 Defence
Redundancy
n service instances in loadsharing mode
two parallel Ethernet links
group of n gateways
SM and OCB transport redundancy
Page 144
NOTES
Page 144

3.4 Defence
Independence
There is relative independence between OM (central defence) and the
common servers
The technique used for OCB/NECTAR communication is to
assign an external AS
This means that independence between OCB and the
external world can be controlled as required
Page 145
NOTES
Page 145

3.4 Defence
Defence responsibilities
The OCB sees three separate worlds
Internal
resources
Ethernet media
External AS
Server-related defence
Page 146
NOTES
Page 146

3.4 Defence
Defence responsibilities
To assume total responsibility for internal faults
To recognize and signal external faults

Change of software for allocation between internal faults and faults located
outside the system.
Page 147
NOTES
Page 147

3.4 Defence
Unit-oriented breakdown of service access defence
OM
ALARM appli
SM central defence
OALRM
MLOC
OEASX
Centralized defence
Centralized defence State
Ethernet
External AS
broadcast
Existing message system

ODIEX
SMB local defence
MLSM_p
OALRM
OSETE
SMB
MLSM_eth
Ethernet link control
State publication
Page 148
NOTES
Page 148

3.5 Case study
N 7 signal processing on SMB
SDH TU management
Defence
Page 149
NOTES
Page 149

3.5 Case study
Question 1
Given a non-HC OCB.
Given a list of its SMs and MLs (see ESMIN), draw the architecture of this
exchange starting from the information in the next slide.
Page 150
NOTES
@ESMIN;
CEN=1/99-10-06/18 H 16 MN 48/INTERROGATION D'ETAT DE SM
TRAITEMENT TDRHM0 ACC
AM = SMMA
AF = OCA
AM = SMMB
AF = OCB
AM = SMC1
AF = MR4
ETAT=ES AUTS=NON AGEO=S1-TR02-B04-A109-R000

ETAT=ES
ETAT=ESRE
ETAT=ES AUTS=OUI AGEO=S1-TR02-B04-A033-R015
ETAT=ES
AF = CC4
ETAT=ES
AF = GS4
ETAT=ES
AF = TX2
ETAT=ES
AM = SMC2
AF = MR3

ETAT=ES
AF = CC3
ETAT=ES
AF = GS3
ETAT=ES
AF = TX1
ETAT=ES
AM = SMC3
AF = TR2

ETAT=ES
AF = MQ2
ETAT=ES
AF = GX2
ETAT=ES
AF = PCB
ETAT=ES
AF = MR2
ETAT=ES
AF = CC2
ETAT=ES
AF = GS2
ETAT=ES
AM = SMC4
Page 150

3.5 Case study
AM=SM...
AF=
AF=
AF=
.
PCM
MAS
MIS
Page 151
NOTES
AM = SMC5
AF = TR1

ETAT=ES
AF = MQ1
ETAT=ES
AF = GX1
ETAT=ES
AF = PCA
ETAT=ESRE
AF = MR1
ETAT=ES
AF = CC1
ETAT=ES
AF = GS1
ETAT=ES
AM = SMXA1
AF = COMA1 ETAT=ES
AM = SMXB1
AF = COMB1 ETAT=ES
AM = SMA1
AF = PUPE1 ETAT=ESRE
AF = ETA1
AM = SMA2
ETAT=ES
AF = PUPE2 ETAT=ES
AF = ETA2
AM = SMA3
ETAT=ES
AF = PUPE3 ETAT=ES
AM = SMTA1
AF = URMA1 ETAT=ESRE
AM = SMTB1
AF = URMB1 ETAT=ES
TRAITEMENT TDRHM0 EXC
Page 151

3.5 Case study
Given an OCB HC3.1
DHA
CDRA
LSN Nectar
SMM
SMB1
------
SMB4
Token ring
SMT2G
PCM / SDH
SMBA 1
SMB_XT
SMBB 1
E
T
U
SMA
SMB6
SMB5
RCH
Page 152
NOTES
Page 152
3 3. Description of functional changes

3.5 Case study
Question 1.2
Using the diagram of the HC3.1 exchange on the previous page, and
bearing in mind that:
SMB1 and SMB3 are SMB_Cs
SMB4 to SMB6 are SMB_As
The pair SMBA1 and SMBB1 is an SMB_XT
Finish writing the result of an ESMIN

@ESMIN;
CEN=HC31/00-07-07/18 H 16 MN 48/INTERROGATION D'ETAT DE SM
AM = SM
AF =
Page 153
NOTES
Page 153

3.5 Case study
N 7 processing on SMB
Question 2
How many signalling links (SLC) can you have on the HC3.1 exchange on the
previous page?
Below is an example of creation of a signalling link set on a non-HC exchange.

How would you create the same link set on an HC3.1 exchange?
Reminder: No more SDL concept
No more LDCR commands for type 1 and 2 data links
Page 154
NOTES
@ LDCR:
CEN=1/91-10-22/09 H 50 MN 35/CREATION DE LIAISON DE DONNEES
@ AFCTE=48-1-10,SRV=T1,ILS=L008,TYLD=1;
SRV = T1 , ILS = L008 , NLD = 0002
TYLD = 01 , FSLD = 002 , RCONF = 0 , SURV = 0
AFCTE = 048-1-10
ALRXE = 01-002 , AFVTE = 048-01-10
LSD NON CONNECTEE
@ FSMCR :
CEN=1/96-06-06/09 H 01 MN 00/CREATION D'UN FAISCEAU DE CANAUX SEMAPHORES
@ NFSM=FSM30,COC=4,RANC=3,SRV=T1,ILS=L008,TSV=2,PS=614,LOI=10;
TRAITEMENT TFSMCR ACC
NFSM=FSM30 TYR=RN
PS= 00614 LOI= 010
D= N CORR= BASE
COC RANC LSD SRV ILS

04
03
008 T1
TSV-VTSV TSM-VTSM COM-LRX-IT ETCS
L008 002-02
003-04
2-080-01
NCNT+BLOM
TRAITEMENT TFSMCR EXC
Page 154

3.5 Case study
Defence
Question 3
On the following OCB HC3.1 exchange, SMB1 and SMB2 are active SMB_Cs and
SMB3 is a standby SMB_C.
SMB1 crashes.
List the successive states of the SMBs and the MLs while SMB1 is being reconfigured
(starting from the information given in the next slide).
Page 155
NOTES
@ESMIN;
AM=SMMA
AF=OCA
ETAT=BLOM AUTS=NON AGEO=S1-TR01-B01-A109-R000

ETAT=NES
( . )
AM=SMB1
AF=TR1
AF=MQ1
AF=GX1
AF=PCA
AF=MR1
AF=CC1
AF=GS1
AF=TX1

ETAT=ES
ETAT=ES
ETAT=ES
ETAT=ESRE
ETAT=ES
ETAT=ES
ETAT=ES
ETAT=ES
AM=SMB2
AF=TR2
AF=MQ2
AF=GX2
AF=PCB
AF=MR2
AF=CC2
AF=GS2
AF=TX2

ETAT=ES
ETAT=ES
ETAT=ES
ETAT=ES
ETAT=ES
ETAT=ES
ETAT=ES
ETAT=ES
AM=SMB3
AM=SMB4
AF=PUPE1

ETAT=ESRE
AM=SMB5
AF=PUPE2

ETAT=ES
AM=SMB6
AF=PUPE3 ETAT=ES
TRAITEMENT TDRHM0 EXC
Page 155

3.5 Case study
Defence
Answer 3
Phase 0
AM=SMB1
AF=TR1
AF=MQ1

ETAT=ES
ETAT=ES
AM=SMB3
Phase 1
AM=SMB1
AF=TR1
ETAT=BLOS
ETAT=
...
Page 156
NOTES
Page 156

3.5 Case study
TU management
Given the diagram below showing connection of an optical SDH line...
63VC12 board
VC12 processing
APS
STM1 termination
STM1 SDH lines
RAB bus
Question 4
How can you be sure that this is an optical SDH connection?
Modify the diagram to show connection of an electrical SDH.
Page 157
NOTES
Page 157

Contents
4.1 Control station

4.2 128 PCM links per UR
4.3 SMB specific extensions
4.4 N 7 on SMB
4.5 TU management
4.6 Case study
Page 158
NOTES
Page 158

4.1 Control station
Listing SMs
SMIL:
AM = x, hardware address of the SMB
Page 159
NOTES
The command can be executed without parameters.
@SMIL;
CEN=1/01-04-26/16 H 31 MN 47/SM LISTING
PROCESS TXTGES ACC
...
AM = SMB1
STBA=1-2-2-66
RAIN=2
RGBAC=0
NMCA=AE35B
SFCA=CV48
RGSF=0
* RAIN=9
NMCA=ACPWUB
SFCA=PUP
RGSF=0
* RAIN=21
NMCA=ACPWUB
SFCA=PUS
RGSF=0
* RAIN=27
NMCA=ACPWUB
SFCA=PUS
RGSF=1
* RAIN=33
NMCA=ACPWUB
SFCA=CMPA
RGSF=0
* RAIN=39
NMCA=ACPWUB
SFCA=PUS
RGSF=2
* RAIN=39
NMCA=AAETH
SFCA=ETH
RGSF=0
* RAIN=45
NMCA=AATRA
SFCA=TR
RGSF=1
* RAIN=51
NMCA=AATRA
SFCA=TR
RGSF=2
* RAIN=57
NMCA=AATRA
SFCA=TR
RGSF=3
RAIN=63
NMCA=AATAD2
SFCA=TAD
RGSF=0
RAIN=76
NMCA=AA35B2
SFCA=AB48
RGSF=1
RAIN=2
NMCA=AFS10
SFCA=FDP
RGSF=0
SFCA=UV
RGSF=1
...
STBA=1-2-2-29
* RAIN=2
RGBAC=0
NMCA=ZKUVB
...
Page 159

4.1 Control station
Listing states of the RCH's GLRs
GLRIL
ETAT = x, state of GLR required for listing
ED = x, detailed output
NIV = x, level of supplementary details for the GLRs
AM = SMB-, address of the SMB corresponding to the GLR type to be listed
ETU = x, ETU number in the station (for AM=SMBX or SCH)
GLRA = x, GLR number in the SMB-A
GLRT = x-x, GLR number in the station (number of the ETU in the SMB-T number of the GLR in the ETU)
GLRX = x , internal designation of the GLR within the network
Page 160
NOTES
Note:
You can still interrogate the system with AFGRT, AFGRX, AFGRA, etc.
NIV: level of supplementary detail

T : time network characteristics
A : ATM network characteristics
E : endpoint characteristics
L : characteristics of the LAs of the GLR
Page 160

4.1 Control station
A number of the operator commands have changed:
@ESMIN:
@AM=SMB1;
@ETUCR:
CEN=1/98-10-05/10 H 35 MN 46 /CREATION D 'UNITE DE TERMINAISON
@AM=SMBD1, SFET=TCA, ;
TRAITEMENT TXTGES ACC
SMTL, ESMMO, ETUxx...
Page 161
NOTES
All operator commands with the AM parameter are affected.
In the various operator commands, a duplex SMB station is designated as follows:
- AM=SMBAi or SMBBi (i=1 to 32) for a station supporting simplex + duplex ETUs
- AM= SMBDi for a station supporting duplex ETUs
Page 161

4.1 Control station
Modifying the HUB-TR connection
HMXMO:
AMX = [/] x, ring hardware address
AMH = x, hardware address of the SMB supporting the TR hub for the AMX ring
RAINH = x, absolute slot number in the subrack for the hub element
Page 162
NOTES
@HMXMO:
CEN=1/00-03-30/12 H 18 MN 16/MODIFICATION DES RACC. HUBS - TR
@AM=SMB1,AMX=MASA2,AMH=SMB1,RAINH=59;
TRAITEMENT TXTGES EXC
@HMXMO:
@AM=SMB2,AMX=MASA2,AMH=SMB1,RAINH=59:
@HMXMO:
@AM=SMB1,AMX=/MASA2:
Page 162

4.2 128 PCM links per UR
A number of operator commands have changed
@MICCR:
CEN=1/98-11-13/15 H 59 MN 36/CREATION DE MULTIPLEX
@AFLR=76-38,AMET=2-6-3,...;
TRAITEMENT TPXEXT ACC
@TAELA:
CEN=1/98-10-05/10 H 35 MN 46 /LANCEMENT TESTS D'ANNULEURS D'ECHO
@AFCT=85-27-12,T=3-05,AECHO=ECHOL2+DIR1,..;
TRAITEMENT TOTTAE ACC
ABOxx, MICxx, ...
Page 163
NOTES
The changes concern the parameter output format.
Page 163

4.1 Control station
Modifying the gateway SMB characteristics
RESMO:
NCPL = [/] x, number of the coupler to be created, modified or deleted
MODF = x-y, operating mode of the coupler's interfaces (speed + type of throughput)
AIPPC = x-x-x-x, main IP address of the coupler on the LSN
AIPSC = x-x-x-x, secondary IP address of the coupler on the LSN
AIPBC = x-x-x-x, IP address of the OCB network
Page 164
NOTES
Addition or modification of characteristics of the SMB3's gateway function for coupler board 0.
@RESMO:
CEN=1/00-02-22/14 H 35 MN 41/MODIFICATION DE SMB PASSERELLE
@AM=SMB3,NCPL=0,AIPPC=180-112-225-1,AIPSC=190-213-85-10,AIPBC=129-01-00-02,
MODF=1-1;
Page 164

4.4 N 7 on SMB
Observation changes: SCS
NCEN=<exchange name>/YY-MM-DD/HH-MN-SS/CS SUPERVISION RESULT

HRD=-- -- HRF=-- -TYR=-- NFSM=--- COC=--- NBE=------- NBR=-----NTC=------- NTPR=------NTPE=------ NTI=------NRF1=------ NRF2=------
Two new counters: NTPE and NTI
Page 165
NOTES
Reminder: Result output is obtained when observation is stopped (SCSAR).
NBE : number of blocks of 128 signal units sent for the first time on line
NBR : number of blocks of 128 signal units received for the first time on line
NFSM : name of signalling link set observed
NRF1 : number of forced retransmission cycles after reaching threshold N1
NRF2 : number of forced retransmission cycles after reaching threshold N2
NTC : number of message signal units received with an incorrect CRT (CRC?)
NTPE : number of message signal units (MSU) lost following transmit congestion
NTI : number of garbled frames
NTPR : number of message signal units lost through buffer file congestion
Page 165

4.5 TU management
Designating a PCM link
On non HC OCB : AMET = SMT N-RGTU-RGET
SMT N = number of an SMT2G in the exchange (1 to 16)
RGTU = number of the ETU in the station (1 to 32)
RGET = number of the ET supporting the PCM link on the ETU (1 to 4)
On an OCB HC : AM=SMBDi, MIC=RGTU-RGET-RGMIC

RGTU = number of the ETU in the station (1 to 128)
RGET = RGTU = number of the ET supporting the PCM link on the ETU (=1)
RGMIC = number of the PCM link on the ET (1 to 64)
Page 166
NOTES
The operator commands affected by these changes are: MICxx, QMCxx, EQTxx, TELxx
Page 166

4.5 TU management
Creating an SDH line
LINCR:
ET = x-x, ETU address (RGTU-RGET)
PRF = x, line profile
ALS = x, automatic laser shutdown
TIMQ = x, threshold S1 enabling broadcasting of the receive clock to the STS
SD = x, error ratio for "signal degraded" calculations
Page 167
NOTES
@LINCR:
CEN=1/00-05-22/10 H 55 MN 47/CREATION DE LIGNE
@AM=SMBD1,ET=1-1,PRF=TO1S,ALS=OUI,TIMQ=G812T,SD=DIXM7;
TRAITEMENT THDLPG ACC
AM = SMBD01 ET = 001-01 PRF=TO1S ALS=OUI TIMQ=G812T SD=DIXM7 ADMS=BLOM
TRAITEMENT THDLPG EXC
Page 167

4.5 TU management
Modifying an SDH line
LINMO:
ADMS = x, administrative state of the line
PRF = x, line profile
ALS = x, automatic laser shutdown
TIMQ = x, threshold S1 enabling broadcasting of the receive clock to the STS
SD = x, error ratio for degraded signal calculations
Page 168
NOTES
@LINMO:
CEN=1/00-05-22/10 H 55 MN 47/MODIFICATION DE LIGNE
@AM=SMBD1,ET=1-1,ALS=OUI,TIMQ=G812T;
AM = SMBD01 ET = 001-01 PRF=TE155 ALS=OUI TIMQ=G812T SD=DIXM6
ADMS=BLOM
Page 168

4.5 TU management
Interrogating an SDH line
LININ:
Deleting an SDH line

LINSU:
Page 169
NOTES
@LININ:
CEN=1/00-05-22/10 H 55 MN 47/INTERROGATION DE LIGNE
@AM=SMBD1,ET=1-1<2-2;
AM = SMBD01 ET = 001-01 PRF=TE155 ALS=NON TIMQ=G812L SD=DIXM6
ADMS=BLOM
OPES=ES
AM = SMBD01 ET = 002-01 PRF=TO1S ALS=OUI TIMQ=G812L SD=DIXM6 ADMS=ES
OPES=ES
AM = SMBD01 ET = 002-02 PRF=TO1S ALS=OUI TIMQ=G812L SD=DIXM6 ADMS=ES
OPES=ES
@LINSU:
CEN=1/00-05-22/10 H 55 MN 47/SUPPRESSION DE LIGNE
@AM=SMBD1,ET=1-1;
AM = SMBD01 ET = 001-01 PRF=TE155 ALS=NON TIMQ=G812L SD=DIXM6
ADMS=BLOM
Page 169

4.5 TU management
Testing an SDH line
LINTL:
Page 170
NOTES
@LINTL:
CEN=1/00-02-10/18 H 15 MN 20/TEST DE LIGNE
@AM=SMBD1,ET=126-1;
AM = SMBD01
ET = 126-01
TEST = OK
Page 170

4.5 TU management
Creating an SDH path
TPACR:
PTE = x , path trace of the POH expected in the received SDH frame
PTS = x , path trace of the POH expected in the transmitted SDH frame
PTI = x, disabling errors associated with the path trace
Page 171
NOTES
There are also PTEH and PTSH parameters respectively corresponding to PTE and PTS, but in
hexadecimal
@TPACR:
CEN=1/00-02-21/15 H 47 MN 53/PATH CREATION
@AM=SMBD1,ET=1-1,PTE='PARIS',PTSH='4C616E6E696F6E3031202020202020'H:
AM = SMBD01 ET = 001-01
PTE = 'PARIS
' PTEH = '504152495320202020202020202020'H
PTS = 'L******01
' PTSH = '4C616E6E696F6E3031202020202020'H
PTI = NON
Page 171

4.5 TU management
Modifying an SDH path
TPAMO:
PTE = x , path trace of the POH expected in the received SDH frame
PTS = x , path trace of the POH expected in the transmitted SDH frame
PTI = x, disabling errors associated with the path trace
Page 172
NOTES
@TPAMO:
CEN=1/00-02-21/15 H 47 MN 53/CREATION DE CONDUIT
@AM=SMBD1,ET=1-1,PTE='PARIS1',PTSH=/'4C616E6E696F6E3031202020202020'H:
AM = SMBD01 ET = 001-01
PTE = 'PARIS1
' PTEH = '504152495331202020202020202020'H
PTS =
PTSH = ''H
PTI = NON
Page 172

4.5 TU management
Interrogating an SDH path
TPAIN:
Deleting an SDH path

TPASU:
Page 173
NOTES
@TPAIN:
CEN=1/00-02-21/15 H 59 MN 53/INTERROGATION D'UN CONDUIT
@AM=SMBD1,ET=3-1:
AM = SMBD01 ET = 003-01 PTI = NON OPES = ES
PTE = 'LYON
' PTEH = '4C594F4E2020202020202020202020'H
PTS = 'L******02
' PTSH = '4C616E6E696F6E3032202020202020'H
@TPASU:
CEN=1/00-02-21/15 H 55 MN 47/SUPPRESSION DE CONDUIT
@AM=SMBD1,ET=1-1:
AM = SMBD01 ET = 001-01
PTE = 'PARIS
' PTEH = '504152495320202020202020202020'H
PTS = 'L******01
' PTSH = '4C616E6E696F6E3031202020202020'H
PTI = NON
Page 173

4.5 TU management
Creating a protection group
PGRCR:
NPGR = x-x, identity of the protection group (RGTU-RGPGR)
TYPP = x, protection type
PTED = x, number of the ET of the protected line
PING = x, number of the ET of the protecting line
Page 174
NOTES
@PGRCR:
CEN=1/00-02-10/18 H 15 /CREATION DE GROUPE DE PROTECTION
@AM=SMBD1,NPGR=1-2,TYPP=UNID,PTED=1,PING=2;
AM = SMBD1
NPGR = 001-02
TYPP = UNID
PTED = 01
PING = 02
Page 174

4.5 TU management
Interrogating a protection group
PGRIN:
TYPP = x, protection type
PING = x, number of the ET of the protecting line
Page 175
NOTES
@PGRIN,CEN=1:
CEN=1/00-02-10/18 H 15 /INTERROGATION GROUPE DE PROTECTION
@AM=SMBD1,NPGR=1-2;
AM=SMBD01
PTEDS=OK
NPGR=001-02
PINGS=SD
TYPP=UNID
SST=SWC
PTED=01
PING=02
REQ=CL
SDIR=SWTPG
Page 175

4.5 TU management
Deleting a protection group
PGRSU:
Page 176
NOTES
@PGRSU,CEN=1:
CEN=1/00-02-10/18 H 15 /SUPPRESSION DE GROUPE DE PROTECTION
@AM=SMBD1,NPGR=1-2;
AM=SMBD01 NPGR=001-02 TYPP=UNID PTED=01 PING=02
Page 176

4.5 TU management
Configuring APS
APSMO:
NPGR = x-x, identity of the group (RGTU-RGPGR)
REQ = x, APS function control
Page 177
NOTES
@ APSMO,CEN=1:
CEN=1/00-02-11/14 H 35 /CONFIGURATION APS
@ AM=SMBD1,NPGR=1-2,PTED=1,REQ=CL;
AM = SMBD1
NPGR = 001-02
PTED = 001
REQ = CL
Page 177

4.5 TU management
Example
Creation of an electrical line and the associated path
Creation of line 0
LINCR : AM=SMBD1, ET=1-1, PRF=TE155;
Creation of the path

TPACR : AM=SMBD1, ET=1-1, PTE= ABCD , PTS= EFGH ,
PTI=OUI;
Setting the line to ES

LINMO : AM=SMBD1, ET=1-1, ADMS=ES;
Page 178
NOTES
Page 178

Glossary
AAL1
ADSL
AEI
AFGRA
AFGRT
AFGRX
ALS
APS
ATM
BB
BHCA
CDC
CDRA
CSND
CSNL
DHA
EC
ATM Adaptation Layer 1

Asymetric Digital Subscriber Line
ATM External Interface
Group of LR links of an SMA or SMB_A
Group of LR links of an SMT or SMB_T
Designation of a network GLR
Automatic Laser Shutdown
Automatic Protection Switch
Asynchronous Transfer Mode
Broad Band
Busy Hour Call Attempts
Exchange core subsystem
Call Detailed Record Application
Remote subscriber digital access unit
Local subscriber digital access unit
Data Handling Application
Echo Canceller
Page 179
Page 179

Glossary
EPS
Er
ETA
ETU
FITL
GK
GW
Equipment Protection Switch

Erlang (unit of traffic measurement)
Auxiliary equipment manager
Exchange termination unit
Fibre In The Loop
GateKeeper
GateWay
HC
HLR
HTVC
ICL
IN
ISL
IT
IWU
LAB
High Capacity
Home Location Register
High voltage DC voltage
Internal Communication Link
Intelligent Network
Internal Serial Link
Information Technology
InterWorking Unit
Local Access Bus
Page 180
Page 180

Glossary
LAH
LAN
LC
LR
LRH
LSD
MC
MLA
MMB
MPS
NARCA
NAS
NB
NE
N-ISDN
NMC
High rate access link

Local Area Network
Large Configuration
Matrix links (4 Mbit/s)
High rate matrix links
Signalling data link
Medium Configuration
Multiplex Link Access
Multiprocessor Memory Bus
Modular Power Station
ATM switching network access number
Network Access Server
Narrow Band
Network Element
Narrow - band Integrated Switched Data Network
Network Management Centre
Page 181
Page 181

Glossary
NT
OAM
OMAP
PDH
PLMN
PoP
POTS
PSTN
PVC
RCH
RCX
RDS
REM
PSTN
SAB
SAM
Network Termination
Operation Administration Maintenance
Operation and Maintenance Application Part
Plesiochronous Digital Hierarchy
Public Land Mobile Network
Point of Presence
Plain Old Telephone Service
Public Switched Telecom Network
Permanent Virtual Connection
High rate switching network
Switching network
Catalogue of system data
Alcatel telecommunication management network
Public Switched Telephone Network
Branch selection and amplification (function)
Modular power station
Page 182
Page 182

Glossary
SCF
SCH
SCP
SDE
SDF
SDH
DBMS
SMB
SMC
SMC
SMF
SMM
SMP
SMT2G
SONET
SSE
Service Control Function (IN)

High rate matrix control station
Service Control Point (IN)
Power distribution station
Service Data Function (IN)
Synchronous Digital Hierarchy
DataBase Management System
General purpose control station
Main control station
Switch Management Centre
Service Management Function (IN)
Maintenance control station
Service Management Point (IN)
Second generation SMT (128 PCM)
Synchronous Optical NETwork
Environment subsystem
Page 183
Page 183

Glossary
STM1
STS
SVC
CA
TAP
TCA
TMN
TrSv
TU
VAN
VC 12
VoIP
VPN
V/ V
WLL
Synchronous Transfer Module 1 (155Mb/ sec)

Synchronization and Timebase Station
Switched Virtual Connection
Call Attempt
Call handling (functions)
Temporel to Composite ATM
Telecommunication Management Network
Translation Server
Terminal Unit
Value Added Network
Virtual Container (SDH)
Voice over Internet Protocol
Virtual Private Network
Channel-associated signalling mode
Wireless Local Loop
Page 184
Page 184

Change Ocb283 - Hc3.1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Change Ocb283 - Hc3.1

Uploaded by

Copyright:

Available Formats

DESCRIPTION OF OCB283 HC3.

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

DESCRIPTION OF OCB283 HC3.1 CHANGES

1. Overview of the product

2. Description of hardware changes

3. Description of functional changes

4. Changes to operation and maintenance

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

-----MIS/MAS token ring

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

Respond to changes in the telecommunications world (more

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

: Cell Loss Priority

: Generic Flow Control

: Virtual Channel Identifier

Payload : useful information

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

: not used at network level (exists only at the user/network interface)

: path number (on 8 at the user/network interface

: Virtual Channel Identifier (within the path)

cable within the sheathing VCI

: type of information conveyed (user, signalling, O&M)

: cell loss priority

: the header's calculated CRC

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

1st bit sent

last bit sent

40 "speech" bytes (TS_64)

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

-----MIS/MAS token ring

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

Target OCB HC3

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product

OCB 283 (R23)

Alcatel University - 8AS 90001 1896 VT ZZA ED.03 - November 2001

Alcatel University - 8AS 90001 1896 VH ZZA ED.03- November 2001

1. Overview of the product