SMIM Operation

Alcatel 900/1800 NSS
Data transmission
5 : SMIM operation & maintenance
© Alcatel University - 8AS 90200 0675 VT ZZA Ed.01 5.1
© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.1

Alcatel 900/1800 NSS - Data transmission
Objectives
▼ Objective : to maintain and to operate
SMIM's equipment.
5.2

Session presentation
▼ Program: SMIM operation & maintenance
Page
5.1 Description
Review 8
SMIM equipment management 9
Interconnected pair of SMIM 10
Initialisation of the SMIM 11
State and accessibility of SMIM 13
States of MIWx 14
Seizure control of data circuits 15
Seizure control by SMIM 16
Seizure control by RCP 17
5.2 SMIMAP data call control messages
IWF_CON_REQ 19
XCONN_REQ 20
UPD_NO_TCH 21
IWF_CON_REL 22
IWF_CON_ACK 23
IWF_FCDREL 24
5.3

▼ Program: Data transmission call handling
Page
IWF_CONN_ERR 25
IWF_CMM_REQ 26
IWF_CMM_CONF 27
5.3 SMIMAP maintenance messages
SEND_RJA 29
READ_AL_ST 30
SMIM_AL_REP 31
IW_ERROR 32
ANO_REPORT 33
RESET_OBC 34
LOAD_BID 35
RESTART_IND 36
SYS_PARM_RQ 37
SYS_PARM / XSYS_PARM 38
SYS_PARM / XSYS_PARM 39
PLMN parameters - INTSYR 40
CHG_OCC_ST / OCC_ST_RSP 42
5.4

Page
IW_AS_RQ / IW_AS_RSP 43
ALIVE_QUE / ALIVE_ACK 44
TEST_ASGN 45
IW_MNTCMD / IW_MNTRSP 46
5.4 RCP / SSP common rules
Review 48
CIC's declaration 49
5.5 Defence mechanism
SMIM fault reports 52
MIWX fault reports 53
SMIM alarms 54
MIWx alarms 55
MIWx supervision 56
SMIM in test 57
Periodical mechanism to block/unblock SMIM circuits 59
5.5

Page
5.6 Data structure
F-DA-021 61
F-DA-022 62
F-DA-029 63
F-DA-047 64
TPBLUB 65
TWDISO 66
TWDREC 67
TPALVQ 68
TWALVQ 69
CNTAL 70
5.7 Exercise 71
5.8 Evaluation 72
5.6

5.1 Description

5.1 Description
Review
▼ The Stand–alone Mobile Interworking
Module (SMIM) is connected to the SSP by
circuit channels and to the RCP by a Nº7
RCP channel. Those channels are supported by
a PCM link between the SMIM and the
SSP.
INAP (with SSP) ▼ The circuit channels pass through the

SMIMAP SMIM, between the radio side and the
BSSAP (with BSS) network side, so that the SMIM can perform
the interworking between radio side data
SSP
stream and network coded signals.
ISDN ▼ There is a fixed assignment (see table TT4)
SMA BSC BTS
PSTN between a ”radio side” circuit (Time Slot i)
and its associated ”network side” circuit
(Time Slot i+16).
1
▼ The Nº7 channel (Time Slot 16) is
Network side call i Radio side call connected to the RCP through a semi–
(normal transmission Mode) (specific transmission mode) permanent connection so that the RCP can
16 supervise the SMIM for data call control and
Operation and Maintenance of the SMIM.
i+16
▼ Nº7 channel between RCP and SMIM is
Signalisation 31 based on SCCP class 0 protocol, and the
SubSystem Number (SSN) interface 208
loop SMIM associated to the SMIMAP (SMIM
Application Part).
5.8

5.1 Description
SMIM equipment management
▼ By using man–machine commands on the RCP, the operator can perform the
following operations:
z creation of the SMIM (CREMIM), i.e. for each SMIM: SMIM name, SMIM
Distant Point Code, CIC pool base, list of MIWX boards and possibly its
associated SMIM in the cross–over configuration.
z suppression of the SMIM (DELMIM), by using its SMIM name.
z setting the SMIM (SETMIM)
Î ”In Service”, i.e. launching its initialisation and enabling the SSP to seize
circuits towards the SMIM.
Î ”Out of Service”, i.e. preventing the SSP from seizing new circuits towards
the SMIM.
z interrogation of the SMIM(s) (INTMIM) :
Î state,
Î characteristics,
Î alarm states, i.e. the possible SMIM faults, MIWX faults, OCCs faults, the
SMIM state, the MIWX state (with option F–DA–021 active), and when the
SMIM is ”Out of Service” (or the MIWX with option F–DA–021 active) the
cause that has yielded to set it in this state.
z Test the SMIM (TSTMIM) (if option F–DA–022 is active).
5.9
▼ SMIM faults counter :
A SMIM faults counter is implemented to manage some SMIM faults so that RCF processing is dependent on a SMIM
faults threshold (TWDREC ).
Each time one of these faults is signalled by DTRE_CALC alarm report indication, the SMIM faults counter is
increased by one. Then, if the threshold of SMIM faults is reached, SMIM equipment will be set to ”Out of Service”
(view from RCP).
Moreover, this counter is regularly divided in order to avoid faults accumulation.

5.1 Description
Interconnected pair of SMIM
▼ OBCI: On Board Controller Interface,
SMIM1 one per MIWX board, common to all
5 three IW circuits,
4
3
▼ OBC: On Board Controller, one per
Circuit 1
2 Circuit 1
MIWX board, common to all three IW
1 O
Circuit 1
O circuits,
C C
O O
Circuit
Circuit 1 3C
Circuit 2C C
C OBC
▼ OCC: On board Channel Controller, six
Circuit 1O C O C OBC
C
O OO O
C per MIWX board, dedicated to time
O C CO C C OBCIOBC
O C C
C OC C C OBC
OBCI
critical tasks such as Rate Adaptation or
C
C CC C C
C C OBC
OBCI low level modem control; two OCCs are
OBCI used per IW circuit, one for the
OBCI incoming channel, the other for the
outgoing channel.
CALC 1 DTRE 1
2 Mbit/s PCM links
CALC 2 DTRE 2
▼ DTRE: performs PCM interface and
5
general management of the SMIM,
4
3 Circuit 1 ▼ CALC: performs clocking and alarm
2 Circuit 1 supervision,
1 O O
Circuit 1
C C
O
Circuit O OBC
Circuit 1 3C C
Circuit 2C C
O
Circuit 1 C O OBC
C
C C
O OO O OBCIOBC
O C CCO C C
O C C OC C C OBC
OBCI
C C CC C
C
OBC
C C OBCI
OBCI
OBCI
SMIM2 5.10

5.1 Description
Initialisation of the SMIM
▼ The initialisation of a SMIM is launched by the RCP in the three following
cases:
z automatically, when a SMIM Point Code becomes re–available,
z during a ”cold start” of the RCP,
z after an ”SMIM In Service” man–machine command.
▼ The initialisation of a SMIM, view from RCP, is performed in three consecutive
steps:
z initialisation of the DTRE–CALC ensemble,
z transparently with respect to the DTRE–CALC ensemble, initialisation of
each MIWX one by one,
z finally, resetting of the RJA bit
▼ If initialisation is launched after POWER ON of the SMIM, the general part
comprising DTRE, CALC and Nº7 signalling link has first to come up. SMIM
Point Code becomes available at this point.
5.11

5.1 Description
Initialisation of the SMIM
RCF SSP SMIM
POWER
SMIM Point Alarm Indication Signal (AIS) ON
Code
becomes PCM level1 alarm RJA ON
available
Standard Alignment procedure
Reset OBC of CALC
DTRE–CALC Alarm Report
Alarm Report Acknowledge
Reset OBC of MIWX
Load Bid Realised in

System parameters request parallel for
System parameters each MIWx
Change OCCs state initialisation
OCCs state response

Update invoke (2) (1)
Update result 1 ) With option
F–DA–021
Send RJA (OFF) active
2 ) For each
PCM level1 alarm RJA OFF circuit handled
by the MIWX
5.12
▼ DTRE–CALC ensemble Initialisation :

Reset OBC of CALC ( RESET_OBC):
z This message is sent by DA in RCF to reset the CALC OBC. A Fast Test is implicitly requested on the CALC OBC to reset
the CALC alarms state.
DTRE–CALC Alarm Report ( SMIM_AL_REP):
z In case of SMIM initialisation, only the own DTRE and CALC alarms parameters are significant in this message. It gives the
”end of boot” indication.
Alarm Report Acknowledge ( SMIM_AL_REP_ACK):
z This message must be sent by the RCF in order to acknowledge the receipt of the DTRE–CALC Alarm Report.
▼ MIWX element Initialisation :
For the SMIM, the MIWXs initialisation is launched in parallel on request of each MIWX PBA, since Reset CALC OBC is received by
the SMIM.However, in order to acknowledge the alarms sent by the SMIM before it receives the Reset CALC OBC, a time–out is set
by DA in RCP. When this time–out expires, RCP requests to the SMIM a MIWXs initialisation.
The time–out value should be greater than a Hard reset duration of MIWX PBA, which is normally lower than 5 seconds.
The following procedure is therefore repeated for each MIWX PBA:
Reset OBC of MIWX ( RESET_OBC):
z This message is sent to each MIWX by DA in RCF to reset each MIWX OBC.
Load Bid ( LOAD_BID):
z This message is sent by the SMIM to inform the RCF that a reset is running on the MIWX PBA, and a Fast Test has been
performed within the MIWX PBA. The message gives the result of the Fast Test and error information.
System parameters request ( SYS_PARM_RQ):
z After end of MIWX restart or MIWX reset, the MIWX PBA requests operator–dependent information concerning its internal
characteristics and configuration.
System parameters ( SYS_PARM):
System parameters ( XSYS_PARM with option F–DA–021 active):
z Configuration data, depending on the compatibility class present in the System parameter request message, is returned by
the RCF ( SYS_PARM or XSYS_PARM).
Change OCCs state ( CHG_OCC_ST):
z At the end of the MIWX initialisation scenario, default state ”unavailable” of all OCCs must be changed to ”available” by the
RCF.
OCCs state response ( OCC_ST_RSP):
z This indication is sent by each MIWX PBA to inform the RCF about the execution result of the Change OCCs state.
▼ End of SMIM Initialisation :
At the end of the overall SMIM initialisation procedure, the RCP re–enables circuit seizure by the SSP by sending the Send RJA
(OFF) request. Then, a spontaneous message WR_DA_102 is generated by the RCF to indicate that the initialisation has been
completed correctly.

5.1 Description
State and accessibility of SMIM
▼ States of the MIWX boards are handled by the RCP, then this
one needs to know, in addition to SMIM state and SMIM
accessibility, the state of each MIWX making up the SMIM :
z ”Out of Service”,
z ”In Service” or
z ”Fault”.
▼ By this way, a SMIM will be set ”In service” (cold start or MMC) if
at least one MIWX is set ”In service”.
▼ And then, as long as at least one MIWX remains in service, the
SMIM remains ”In service”. If an isolation occurs during a
procedure to set the MIWX into service, the MIWX remains or is
set into service.
5.13

5.1 Description
States of MIWx
▼ MIWX states are then handled in the following way:
z A MIWX state is initialised to ”Out of service”:
Î At the creation of the SMIM by MMC,
Î As soon as ”a setting in service” is requested by MMC, by this way
the MIWX boards (previously faulty) can be (re)initialised.
z A MIWX in the state ”Out of service” becomes ”In service”:
Î After successful (re)initialisation (cold start, MMC)
Î As soon as the SMIM becomes isolated (SMIM previously ”In
service” or ”Being set in service”). An isolated SMIM and then the
MIWX which make it up, are then regarded as ”In service” by the
RCP.
z A MIWX in the state ”In service” becomes ”Out of service”:
Î On setting ”Out of service” of a SMIM (MMC or fault report)
z A MIWX in the state ”In service” becomes ”Fault”:
Î On MIWX board failure or restart threshold overflow: a faulty MIWX
can get out of ”Fault” state only on ”setting in service” MMC request.
5.14
▼ Isolated SMIM :
In case the SMIM Point Code becomes unavailable, all data calls related to this SMIM are locally released by the
RCF.
Spontaneous message WR_DA_104 is generated, and the SMIM becomes ”isolated”.
With option F–DA–021 active, if a SMIM becomes ”Isolated”, state of all MIWX not in ”Fault” will be set to ”In service”
and a timer TWDISO will be started.
z If during TWDISO, the SMIM Point Code becomes re-available, TWDISO is deactivated and SMIM
accessibility becomes ”not isolated”: spontaneous message WR_DA_105 is generated and a re–initialisation
is launched by the RCP for each MIWX found in the state ”In service”.
z On the other hand, in case of timer TWDISO expiry, the SMIM and then all the MIWX not set ”Fault”, are set
”Out of service” by the RCP and spontaneous message WR_DA_115 is generated.
▼ Threshold :
With option F–DA–021 active, if the number of failures of a MIWX board reaches a defined threshold (system
parameter with a default value set to 10) or a failure occurs during the restart of the board, the board is definitely
regarded as faulty and the MIWX is set ”Fault”.
The SMIM stays ”In service” unless all MIWX boards are set ”Fault”.
The restart counters of all MIWX are reset every 2 hours by a background activity.

5.1 Description
Seizure control of data circuits
▼ The SSP must not seize new circuits towards a given SMIM for
data transmission, either when:
z SMIM equipment maintenance is in progress,
z or an initialisation phase is in progress in the SMIM,
z or the SMIM is faulty
z or a MIWX from the SMIM is in a phase of restart
▼ However, with option F–DA–021 active and according to
handling of MIWX card state by the RCP, the SSP must not
seize anymore new circuits dedicated to a given MIWX
belonging to a SMIM in service when this MIWX becomes ”Out
of service” or ”Fault”.
5.15

5.1 Description
Seizure control by SMIM
▼ The SMIM may autonomously set the Remote Junction Alarm (RJA) on the
channel 0, bit 3, in frames not containing the frame alignment pattern on the
PCM link. Such a scenario is launched either :
z when a short disruption of the PCM link occurs, which does not lead to a
failure of the signalling channel (e.g. LFA alarm),
z when a serious PCM link fault is detected which will lead the RCP to set
the SMIM ”out of service” (e.g. EER_1 alarm),
z or in the particular case of SMIM autonomous initialisation phase at the
beginning of the boot. In this case, it is up to the RCP to disable the RJA
at the end of SMIM initialisation.
▼ The SSP analyses this information as a requirement not to seize anymore
circuit towards the SMIM. However, setting the RJA to active state does not
disrupt the Nº7 channel of SMIM command nor the established circuits. So,
on a short disruption of the PCM link, the established calls will not be
released. Nevertheless, on a serious PCM link fault, the data calls will be only
maintained till the RCP sets the SMIM ”out of service”.
5.16
▼ Alarms :
ERR1 = The error bit rate has reached 10-3 (count during 1 second the errors in the frame alignment signal).
LFA = Loss of frame alignment on the PCM link.
( See PMLX/6020 - SMIM FAULT DETECTED ON DTRX BOARD )

5.1 Description
Seizure control by RCP
▼ The RCP may also prevent the seizure of new circuits by the
SSP:
z at the SMIM level by forcing the SMIM to set the RJA by
using ”Send RJA” Nº7 command, in case of : (note 1)
Î man–machine command (set SMIM ”out of service”)
Î RCP processing of SMIM fault reports (counting of
faults, comparison with a threshold, MIWX restart in
progress...).
z With option F–DA–021 active, at the MIWX level (each
time a MIWX becomes ”Out of Service” or ”Fault”) by
sending an UPDATE message towards SSP in order to lead
to a blocking of the MIWX dedicated circuits (case of RCP
processing of MIWX faults reports or the number of restart of
a MIWX has reached a critical threshold). (note 2)
5.17
▼ Note 1 :
Established data calls are released by the RCF when the SMIM is set ”out of service” or when an SMIM isolation is
detected, because it is not suitable to have data calls running without controlling the SMIM.
When a MIWX is in a phase of restart, only the established data calls on the circuits of this MIWX are released by RCF.
▼ Note 2 :
For MIWX in TCH/F9.6 singleslot configuration, the UPDATE message is sent for three circuits for radio side and three
circuits for network side for each declared MIWX.
For MIWB AB in multislot configuration, the UPDATE message is sent only for one circuit for radio side and one circuit for
network side for each declared MIWX.
▼ RCP behaviour :
In any case, it is up to the RCP to re–enable the SSP to seize new circuits towards a SMIM for data transmission :
z At the SMIM level, by forcing the SMIM to reset the RJA by using the same ”Send RJA” Nº7 command, either on
successful completion of an SMIM initialisation or at the successful end of a MIWX restart.
z With option F–DA–021 active, at the MIWX level, by sending a UPDATE message towards SSP in order to lead to
an unblocking of MIWX dedicated circuits (each time the MIWX is set in service including the isolation case).
Î For MIWX in TCH/F9.6 singleslot configuration, the UPDATE message is sent for three circuits for
radio side and three circuits for network side for each declared MIWX.
Î For MIWB AB in multislot configuration, the UPDATE message is sent only for one circuit for radio side
and one circuit for network side for each declared MIWX.
N.B. Circuit Un(blocking) procedure is then linked with the MIWX state.

5.2 SMIMAP data call

control messages

IWF_CON_REQ
▼ IWF Connection Request: IWF_CON_REQ
z Direction : RCF Î SMIM
z Action :
Î to request the connection of an interworking (IWF) circuit on the MIWX
Î It includes all necessary parameters to enable the MIWX OBC to connect the interworking circuit
with the appropriate parameters setting.
Î For data transmissions that require the use of modem in the IWF, all echo suppressors on the
transmission line must be disabled by sending a 2100 Hz in–band answering tone towards the
network. This function is autonomously performed by the SMIM when the data call is a
Terminating Call.
Î For "Unrestricted Digital Transmission" (UDI), where no modem is selected in the IWF, all
switching equipment's on the line must inhibit their local echo suppressor or canceller. This
function is performed by the SSP.
z Parameters :
Î OBCI which identifies the MIWx printed board itself from the CIC "radio side" value (see TT3,
TT4 tables : CIC Î Channel Î OBCI)
Î interworking circuit which identifies one of three pairs of circuits per MIWx board (see TT3, TT4
tables : CIC Î Channel Î OBCI Î IWC Î [OCC1, OCC2])
Î circuit1 (Î OCC1) & circuit2 (Î OCC2) indicators :
' T / NT,
' originating/terminating side,
' Radio channel requirement (full/half rate),
Î bearer capability (UIL2P, ITC, duplex mode, synch. mode, NDB, NIC, NSB, Data compression,
UR, parity, modem type)
Î reference number (to make distinction in acknowledgement message with release message) 5.19
▼ bearer capability :
user information layer 2 protocol ,
duplex mode,
synchronous/asynchronous indicator,
Number of data bits,
NIC on transmission (Tx) indicator,
NIC on reception (Rx) indicator,
Number of stop bits indicator.
Data compression indicator (not used to invoke the service).
Information Transfer Capability,
user rate,
parity information,
modem type.

XCONN_REQ
▼ Extended IWF Connection Request: XCONN_REQ
z Action :
Î to indicate the required configuration of the MIWB AB. It has to be used only with MIWB AB
boards.
Î It is used only if the IWF type of the call is ”HSCSD” and/or for data compression.
z Parameters :
Î reference number (to make distinction in acknowledgement message with release message)
Î configuration type in which the MIWX will be used (single link TCH/F9.6) when data compression
is invoked without HSCSD
Î Mobile Originating Call (MOC) or a Mobile Terminating Call (MTC) flag
Î ”Chosen channel” rate & mode as defined by BSC (in Assignment complete message)
Î GSM-BC octets information's (ITC, data compression, …)
5.20

UPD_NO_TCH
▼ IWF update number TCH: UPD_NO_TCH
z Action :
Î to request an update of the number of real used traffic channels and their coding scheme after a
handover or an user initiated modification.
Î This message is not acknowledged by the SMIM.
z Parameters :
Î ”Chosen channel” rate & mode as defined by BSC (in Assignment complete, Handover
performed & Handover Complete messages)
Î GSM-BC octets information's (ITC, data compression, …)
5.21

IWF_CON_REL
▼ IWF Connection Release: IWF_CON_REL
z Action :
Î to release the data connection. It is also used to acknowledge an ”IWF Connection Forced
Release” message sent by the SMIM.
z Parameters :
Î reference number (to make distinction in acknowledgement message with request message)
5.22

IWF_CON_ACK
▼ IWF Connection Acknowledge: IWF_CON_ACK
z Direction : SMIM Î RCF
z Action :
Î to confirm or reject an establishment or a release of the connection by the MIWX OBC
(respectively on an IWF Connection Request or on an IWF Connection Release).
z Parameters :
Î parameter to indicate if the connection (or disconnection) was successful and the reason :
' successful,
' message not in sequence (if an OCC re–initialisation has not been completed yet)
' wrong message parameter (if the connection has been already established/released)
' COUT port write failure (Channel OUT on MIWX : a hardware error)
Î reference number (in relation with the one sent by request or release message)
5.23
▼ The reason of the failure is output as a software anomaly and may be used for debugging purposes.
If the result of ”IWF Connection Acknowledge” following an ”IWF Connection Request” is not successful, the SMIM
connection must be released by the RCP using ”IWF Connection Release” message. However if the reason of
the failure is ”wrong message parameter” a new trial to connect the call will be done because it is considered that the
previous call was not correctly released. Otherwise the call is released.
If the result of ”IWF Connection Acknowledge” following an ”IWF Connection Release” is not successful, no specific
action is done.

IWF_FCDREL
▼ IWF Connection Forced Release: IWF_FCDREL
z Action :
Î This message is sent by the SMIM to the RCF when the connection of the IWF unit has been
released within the SMIM. The RCF shall then release the data call.
Î It must be acknowledged by the RCF by sending the ”IWF Connection Release” message to the
SMIM.
z Parameters :
Î cause of a forced release :
' Synchronisation problems
' RLP problems
' V42 problems
' X25 problems
' FAX protocol problems
' internal failure
' buffer overflow (included V42bis buffer overflow)
5.24

IWF_CONN_ERR
▼ IWF Connection Related Error: IWF_CONN_ERR
z Action :
Î This message indicates to the RCF an appearance/disappearance of a connection–related error
detected on the MIWX OCC during a stable data call. These error reports from the SMIM give
information about the quality of the data link by indicating loss of V.110 frame, loss of
synchronisation, error counter overflow, ... events. The reception of this message is disabled by
the RCF, by setting the appropriate configuration parameter of the ”System parameters”
message
z Parameters :
Î OCC located on the MIWx board
Î OCC error status (On, Off, IMPULSE)
Î cause of error :
' loss of V.110 frame alignment,
' synchronisation pattern default,
' character framing error,
' error counter overflow,
' RLP (Radio Link Protocol) N2 exceeded (maximum number of retransmissions attempts),
' data queue overflow.
5.25

IWF_CMM_REQ
▼ IWF Channel Mode Modify Request: IWF_CMM_REQ
z Action :
Î This message indicates to the RCF that a change of channel coding due to negotiation of end to
end data rate is requested.
z Parameters :
Î data rate :
' The data rate must be lower or equal to the data rate given at the call initiation and different
from the current data rate. Data rate may have the values: 2400, 4800, 9600.
' This message is only for fax transmission but no control about the type of transmission
running is done at the reception of this message.
' Moreover, in case of a terminating call (in case of TS61, it corresponds to the current call
direction), the timer TSAT is started to delay the ASS–REQ in order to leave enough time
for the in band DCS frame to reach the MS. In case no delay is to be added the value of
the timer TSAT is set to 0 (default value).
5.26

IWF_CMM_CONF
▼ IWF Channel Mode Modify Confirm: IWF_CMM_CONF
z Action :
Î This message is sent by the RCF back to the SMIM to confirm the change of channel coding.
z Parameters :
5.27

5.3 SMIMAP maintenance

messages

SEND_RJA
▼ Send RJA: SEND_RJA
z Action :
Î This message is sent by the RCF to the SMIM to request the SMIM to set the RJA bit ON/OFF in
order to prevent/enable seizure of new circuits towards the SMIM by the SSP.
z Parameters :
Î RJA control to indicates whether RJA must be set active or not.
' (channel 0, bit 3, in frames not containing the frame alignment pattern on the PCM link.)
5.29

READ_AL_ST
▼ Read Alarm READ_AL_ST
z Action :
Î This message is sent by the RCF to request the alarm state of the SMIM, and in particular the
status of the RJA bit. With option F–DA–021 active, it is repeated according to a system
parameter (CNTAL) in case of no answer.
Î It is only used after RCP switchover (no on MMC) and allows to update the SMIM alarms table.
Î The ”DTRE–CALC Alarm Report” message from the SMIM answers the request.
z Parameters :
Î none
5.30

SMIM_AL_REP
▼ DTRE–Alarm Report: SMIM_AL_REP
z Action :
Î to indicate the appearance of an alarm on the own or the peer SMIM due to internal mismatch
between DTRE and CALC elements or due to external errors.
Î It must be acknowledged by the RCF (SMIM_AL_REP_ACK) except if it report the alarms status
of the own and the peer SMIM on a ”Read Alarm Status” request of the RCF.
z Parameters :
Î Reason why this fault report is transmitted to the RCF :
' read request: the message answers a ”Read Alarm Status” request,
' end of isolation: the SMIM pair has recovered a signalling connection to its RCP,
' change detected: the fault report is sent spontaneously when a change in the alarm states
reported by this message has occurred,
' end of boot: the boot of the DTRE–CALC ensemble is completed.
Î Sequence number : this value is incremented on each autonomous fault report and is used for
the supervision of acknowledgement.
Î Own & Other DTRE alarms [
Î SMIM alarms [: status of the peer SMIM converter (”running” or ”failure”), and on the state
requested by the RCP of communication link between SMIM and RCP (RJA bit status is ON or
OFF).
Î CALC alarms [.
Note that each alarm indication is memorised in the SMIM alarms table
5.31
▼ Own & other DTRE alarms :

MSR (Missing Status Report) from DTRE,
RJA (Remote Junction Alarm),
MAC (Missing ACk from CALC),
LKF (Nº7 signalling LinK Failure),
EER_1 (10–3 alarm),
EER_2 (10–5 alarm),
SLIP (SLIP alarm),
AIS (Alarm Indication Signal),
LFA (Loss of Frame Alignment),
LIS (Loss of Incoming Signal),
INT (INTernal DTRE alarm (error in Trunk–Rx–Unit of DTRE)),
EXT (EXTernal DTRE alarm (error in external part of Trunk–Rx–Unit)),
CRC4_1 (10–3 alarm),
CRC4_2 (10–6 alarm),
HDB3 error rate alarm.
See also spontaneous messages :
z PMLX/6020 - SMIM FAULT DETECTED ON DTRX BOARD
z PMLX/6030 - SMIM FAULT DISAPPEARANCE ON DTRX BOARD
▼ SMIM alarms, see also spontaneous messages :

PMLX/6022 - SMIM FAULT DETECTED (Converter)
PMLX/6032 - SMIM FAULT DISAPPEARANCE (Converter)
▼ CALC alarms : (note that these alarms do not lead to service interruption)
IPAD (Input Pulse Absent Detector alarm),
OPAD (Own Pulse Absent Detector alarm),
RPAD (otheR Pulse Absent Detector alarm),
OOR (VCO Out–Of–Range alarm on CALC),
UNL (PLL UNLock on CALC),
MMC (MMC test alarm indicates a problem with MMC interface).
See also spontaneous messages :
z PMLX/6021 - SMIM FAULT DETECTED ON CALX BOARD
z PMLX/6031 - SMIM FAULT DISAPPEARANCE ON CALX BOARD

IW_ERROR
▼ IW Error: IW_ERROR
z Action :
Î This message indicates to the RCF the appearance/disappearance of a hardware error on the
MIWX OCC.
Î It must be acknowledged by the RCF (IW_ERROR_ACK)
z Parameters :
Î OCC located on the MIWx board
Î OCC error status (On, Off, IMPULSE)
Î OCC–error report (cause) :
' none,
' FIFO underrun,
' FIFO overrun
Î error category :
' notify: indication only,
' recoverable: OCC device is still available,
' recoverable with retry: OCC is temporarily unavailable, SMIM tries to recover the error, see
TWDREC timer
' unrecoverable: OCC is unavailable.
5.32
▼ See also spontaneous messages :
PMLX/6027 - OCCS FAULT ON MIWX

PMLX/6028 - OCCS FAULT DISAPPEARANCE ON MIWX
PMLX/6029 - OCCS FAULT IMPULSE ON MIWX

ANO_REPORT
▼ OBC Error: ANO_REPORT
z Action :
Î This message is sent by the SMIM in case a software error is detected on the MIWX OBC.
z Parameters :
Î anomaly report
5.33

RESET_OBC
▼ Reset OBC: RESET_OBC
z Action :
Î to reset the addressed OBC (on CALC PBA or MIWX PBAs). When a Reset OBC of CALC is
sent, a CALC Fast Test is implicitly requested.
z Parameters :
5.34

LOAD_BID
▼ Load Bid: LOAD_BID
Î Sent as an answer to a ”Reset OBC of MIWX” request (SMIM initialisation triggered by RCF) or
Î received on SMIM power–on or
Î on ”hot insertion” of MIWX.
z Action :
Î to inform the RCF that a reset is running on the MIWX.
' MIWX initialisation not requested by RCF : the parameters of Load Bid message are
analysed. Depending on the autotest result, the RCP see MIWX faulty or tries to restart it.
' MIWX initialisation requested by RCF : initialisation is successful if "Fast test" is OK, "Error
Class" = ”end of boot” and if "Error Type" = ”no error”
Î If failure, the "Fast Test" result, the "Error Class" and the "Error Type" parameters, are output and
can be used for debugging purposes Î MIWX is set ”Fault” (with option F–DA–021 active).
z Parameters :
Î fast test result
Î error class
Î error type
Î power–on flag (which force or not the boot)
Î PBA registration number (bearer service variant, fax variant, … Î PBA type to test the SMIM)
5.35
▼ Fast test on following points : ▼ See also spontaneous messages :

memory write protection test,
RAM test, PMLX/6015 - SMIM INITIALIZATION SUCCESS
OBCI test, PMLX/6019 - SMIM REINITIALIZATION IN
OCC test, PROGRESS
sanity timer test,
periodic timer test. ▼ Note :
▼ Error class : that fast test result parameter is memorized in the

SMIM alarms table.
end of boot
OSN recoverable,
user recoverable,
user non recoverable,
CE restart.
…
▼ Error type :
no error,
message not expected,
message timeout,
message out of sequence,
data inconsistency,
SSM call data error,
message data error,
no mail link,
no UMEM block,
OBC cluster com.,
no host alive,
forced restart.
…

RESTART_IND
▼ Restart Indication: RESTART_IND
z Action :
Î This message is sent by the SMIM to inform the RCF that a restart is running on the MIWX and
that is not caused by a reboot.
Î It may be sent by the SMIM either as an answer to a ”Forced Restart” request or as a
spontaneous indication, and must not be acknowledged by the RCF.
Î It includes information that is output as a software anomaly and can be used for debugging
purposes.
z Parameters :
Î error class
Î error type
5.36
PMLX/6025 - MIWX OBC INITIALIZATION FAILURE

SYS_PARM_RQ
▼ System parameters request: SYS_PARM_RQ
z Action :
Î This message is sent by the SMIM to the RCF after end of MIWX initialisation or MIWX restart
phase to request system parameters and to inform the RCF about the availability of hardware
configuration.
Î On MIWX initialisation:
' ”System parameters request” is sent by the SMIM with ”Load Bid” message. Both these
messages are repeated until they are acknowledged by using ”System parameters”
message.
Î On MIWX restart:
' ”System parameters request” is sent by the SMIM after ”Restart Indication”, with ”OBC
error” message.
' These three messages are repeated until they are acknowledged by using ”System
parameters” message.
z Parameters :
Î PBA registration number (bearer service variant, fax variant, … Î PBA type to test the SMIM)
Î Modem information : this parameter indicates the hardware modem types implemented on the
MIWX PBA
Î COMPT_CLASS : this parameter is used to know the functional level of the MIWX board
5.37
▼ Modem information :
this parameter indicates the six hardware modem types implemented on the MIWX PBA. For each of them,
information may indicate the following values:
z none,
z SSI 73K224L, for bearer services BS21, 22 and 24 (V.21, V.22 and V.22bis) for MIWA,
z R96EFX, for MIWA FAX.
z RC144DPL, for MIWB.
z RC288DPL, for MIWB AB.

SYS_PARM / XSYS_PARM
▼ System parameters : SYS_PARM / XSYS_PARM
Î There are two definitions of the SYS_PARM message, the normal one and the extended one.
Some boards can decode both messages while other boards can only decode the normal
SYS_PARM.
Î The SMIM provides the RCP with its capabilities to decode in the COMPAT_CLASS parameter of
the SYS_PARM_RQ message.
Î In the Extended SYS_PARM, if all the parameters are not sent, the SMIM will assume default
parameters values. Furthermore, if unforeseen parameters are received by the SMIM (due for
example to not matching versions between RCP and SMIM), they are ignored.
z Action :
Î This message is used to acknowledge a ”System parameters request” message sent by the
SMIM and allows RCF to transmit configuration data to the SMIM.
z Parameters :
Î All parameters of the message are operator dependent (PLMN data). Some of them can be
managed by MMC.
Î see below
5.38
▼ In particular:
reporting of ”IWF Connection–related errors” by the SMIM is disabled by setting bit 8 of octet 5 to 0.
concerning the recovery actions (Hard Reset) performed by the OBC of the MIWX in case of severe OCC errors
(message IW–ERROR received with OCC–error status to ON and category RECOVERABLE WITH RETRY):
z delay Trecov between two Hard Reset must be greater than Hard Reset duration (maximum 10 seconds).
z number Nrecov of Hard Reset must be greater or equal than 1 value.
If F–DA–029 is active, the RCP requests the SMIM to activate the T30 flag stuffing mechanism for fax Transparent by
giving the appropriate values of parameters FAX_FLAGSTUFF_START (default value = 1,5s) and
FAX_FLAGSTUFF_STOP (default value = 800ms).
z If F_DA_029 is not active, these parameters will not be sent (if the SMIM does not support Extended SYS–
PARM) or sent with 0 value (noflagstuffing).
The DEFAULT_PARMS parameter controls the use of default values for some SYS_PARM parameters (VERSION,
WINDOW_SIZE_IWF, WINDOW_SIZE_MS, TIMER_1, COUNTER_2, TIMER_2 and XID_WAIT). For each
parameter, one bit indicates if the default value has to be used by the SMIM or if the value shall be taken in the
relevant parameter of SYS_PARM.
z For example, in order to modify the value of timer T1, it is required to modify both DEFAULT_PARMS and
TIMER_1 parameters.
The VERSION parameter is used to indicate to the SMIM the maximum version number of RLP which it may use. The
version set in this parameter is always #2 corresponding to authorize the use by the SMIM of RLP2 either for multislot
call or for single slot if RLP_FLAGS requests ”use RLP2 for single link”. In order that the SMIM takes into account the
VERSION parameter, it is necessary to indicate in DEFAULT_PARMS parameter that the default value shall not be
used.
The DEFAULT_FLAGS parameter controls the use of default RLP flags. It indicates whether default values of RLP
options (XID forced or not forced before SABM, SREJ option active or not active, RLP2 for single link used or not
used) will be used or if the values indicated in RLP_FLAGS parameter have to be taken into account.
z When the option F–DA–047 is active, the bits related to SREJ and RLP2 options have to be set to ”SREJ Opt.
from RLP_FLAGS” and ”RLP2 Opt. from RLP_FLAGS”.
The RLP_FLAGS parameter is used to control the RLP options.
z ”l” bit: is set to ”use RLP2 for single link” when the option F–DA–047 is active. In that case the SMIM always
tries to negotiate RLP version 2 for single link non transparent data calls. If the MS does not support this
version a fallback to a lower version is accepted.
z ”s” bit: to optimize the retransmission mechanism this bit should be set to ”SREJ option active” when the
option F–DA–047 is active.

SYS_PARM / XSYS_PARM
The TIMER_1 parameter represents the RLP T1 acknowledgement timer for full rate channels at 12kbps. (see
T1_FR12_RLP)
The HALFRATE_TIMER_1 parameter represents the RLP T1 acknowledgement timer for half rate channels at 6kbps.
(see T1_HR6_RLP)
The ATRAU_TIMER_1 parameter represents the RLP T1 acknowledgement timer for full rate channels at 14.5kbps. (see
T1_FR145_RLP)
The TIMER_2 parameter represents the RLP T2 reply delay. The value given in this parameter is only used in the XID
frame when a negotiation with the MS upon T2 happens. Afterwards the SMIM uses a T2 value of 20ms for its treatments
and ignores the value which has resulted from the parameter negotiation. This 20ms value corresponds exactly to one
RLP frame.
The OCC_FLAGS and AUTO_SPEED fields are used to control the autobauding function. They are therefore only
meaningful to the MIWB AB board with a RC288DPL modem device. OCC_FLAG enables the handling of autobauding.
The DC_DATACOMP_REQ field is used to configure on which direction(s) data compression may be used (MS to fixed
network only, fixed network to MS only, both directions or neither direction).
The DC_NO_CODEWORD field specifies the number of codewords used in the data compression algorithm. It should be
initialized to 11, meaning 2048 (2 at the power of11) possible codewords, this is also the maximum authorized value.
z The possible range is [512–2048]
z It only applies to the MS/IWF section of the call.
z The DC_NO_CODEWORD field corresponds to the P1 parameter of the V.42bis recommendation.
The DC_NO_CODEWORD_NW field specifies the number of codewords used in the data compression algorithm. It
should be initialized to 9 meaning 512 (2 at the power of 9) possible codewords.
z It only applies to the section between the IWF and the end party in the fixed network.
z The DC_NO_CODEWORD_NW field corresponds to the P1 parameter of the V.42bis recommendation.
The DC_MAX_STR_LEN field specifies the maximum length of the strings stored in the dictionaries (should be initialized
to 20). The DC_MAX_STR_LEN field corresponds to the P2 parameter of the V.42bis recommendation.
5.39
These three last parameters (DC_NO_CODEWORD, DC_NO_CODEWORD_NW, and DC_MAX_STR_LEN) are only
significant when DC_DATACOMP_REQ is different from ”neither direction”.
The RLP2_KV2_IWF parameter represents the RLP version 2 maximum window size of the frames received from the MS.
This value is used by the SMIM to negotiate the window size with the MS. (see W_MS_IWF_RLP2)
z The range of the interface parameter is automatically mutiplied by 8 by the SMIM for internal use to obtain the true
window size.
z This parameter must be set when the F–DA–047 option is active
The RLP2_KV2_MS parameter represents the RLP version 2 maximum window size of the frames sent by the SMIM to
the MS. This value is used by the SMIM to negotiate the window size with the MS. (see W_IWF_MS_RLP2)
z The range of the interface parameter is automatically mutiplied by 8 by the SMIM for internal use to obtain the true
window size.
z This parameter must be set when the F–DA–047 option is active.
The FAX_PREA_DLY parameter corresponds to the delay specified in the GSM REC 03.46 about Non Transparent fax. It
has to be configured when non transparent fax is used in a satellite environment. (see FAX_NT_TIMER)
z This parameter must be set when the F–DA–047 option is active.
The RLP2_T4_V110 parameter represents the RLP version 2 T4 resynchronisation timer for full rate channels at 12kbps.
z When the option F–DA–047 is validated this parameter is ignored by the SMIM for RLP version 2 in single slot.
The RLP2_T4_ATRAU parameter represents the RLP version 2 T4 resynchronisation timer for full rate channels at
14.5kbps.
z When the option F–DA–047 is validated this parameter is ignored by the SMIM for RLP version 2 in single slot.

PLMN parameters - INTSYR - (1)
PARNAME VALUE
PARAMETER USE
(RCP)
RLP T1 acknowledgement timer for full rate channels at 14.5kbps.

This value is used by the IWF to negotiate the T1 timer value with the MS.
T1 must follow the rule: T1 > T2 + 2xTD.
T2 is the reply delay, equal to 20ms.
T1_FR145_RLP TD is the transmission delay between the MS and the IWF.
unit : 10ms
minimum value : 0
maximum value : 255 (2550ms)
default value : 52 (520ms)
RLP T1 acknowledgement timer for full rate channels at 12kbps.

T1_FR12_RLP TD is the transmission delay between the MS and the IWF.
unit : 10ms
minimum value : 0
default value :48 (480ms)
RLP T1 acknowledgement timer for half rate channels at 6kbps.

T1_HR6_RLP
TD is the transmission delay between the MS and the IWF.
unit : 10ms
minimum value : 0
5.40

PLMN parameters - INTSYR - (2)
PARNAME VALUE
PARAMETER USE
(RCP)
RLP number of retransmission attempts N2.

This value is used by the IWF to negotiate the N2
number with the MS.
N2_RLP
minimum value : 0
maximum value : 255
default value : 6
RLP version 2 window size from MS to IWF.

This value is used by the IWF to negotiate the window size from MS to IWF.
The value must be a multiple of 8.
W_MS_IWF_RLP2
minimum value : 0
maximum value : 480
default value : 240
RLP version 2 window size from IWF to MS.

This value is used by the IWF to negotiate the window size from IWF to MS.
The value must be a multiple of 8.
W_IWF_MS_RLP2
minimum value : 0
maximum value : 480
default value : 240
Timer defined in GSM REC 03.46 to process fax in non transparent mode.
This value depends on the transmission delay. It must be provided in the case of satellite transmissions.
unit : 10ms
FAX_NT_TIMER
minimum value : 0
5.41
▼ Window size = number of outstanding unacknowledged frames
When a satellite is used between the MSC an the MS, the transmission delay between these two entities is greatly
increased. In the case of Non Transparent data communications, too short window size would cause stop and go
situations :
z A stop and go situation occurs when the transmitting side has exhausted its window size and awaits for an
acknowledgement without being able to send any frame Î the throughput of the channel is not fully exploited.
In such a communication environment the increased window size of RLP2 is required to make up for the lengthened
propagation delay of fax and data transmissions.

CHG_OCC_ST / OCC_ST_RSP
▼ Change OCC's state : CHG_OCC_ST (/ OCC_ST_RSP)
z Direction : RCF Î SMIM (/ SMIM Î RCF)
z Action :
Î This message is sent by the RCF to the SMIM to request the MIWX OBC to change the state of
the OCCs (note that a MIWX OBC never changes an OCC state on its own).
Î It must be used when SMIM is set ”Out of Service” or ”In Service” or during test process
Î A global response (OCC_ST_RSP) is returned when the state of all OCC devices has been
changed.
z Parameters :
Î OBCI
Î modified OCC states : to indicate which OCC's have to modify their device state
Î OCC states :”available” or ”unavailable” value.
Î Response Î (OCC_ST_RSP) Result (each OCC ”result” parameter is memorized in the SMIM
alarms table.) :
' successful,
' message not in sequence,
' wrong message parameter,
' OCC not responding,
' Fast Test failed,
' other OCC error,
' pattern faulty,
' no appl proc,
' COUT port write failure (Channel OUT on MIWX).
5.42

PMLX/6026 - OCC FAILURE ON MIWX

IW_AS_RQ / IW_AS_RSP
▼ MIWx Alarm State Request : IW_AS_RQ / IW_AS_RSP
z Action :
Î This message is sent by the RCF to request the states of all alarms of the MIWX OBC. With
option F–DA–021 active, it is repeated according to a system parameter (CNTAL) in case of no
answer.
Î It is only used after RCP switchover (not on MMC) or, if option F–DA–021 is active after
TWDREC timer expiry, and allows to update the SMIM alarms table.
Î It is acknowledge by the SMIM to RCF message IW_AS_RSP
z Parameters :
Î OBCI
Î Response Î (IW_AS_RSP) OCC–alarms indicators (list) :
' six ”OCC–alarm indicator” of each OCC with the following information elements:
 OCC–error status,
 OCC–error report (each OCC–error report parameter is memorized in the SMIM
alarms table),
 error category.
5.43
▼ See IW_ERROR message description

OCC error status & report & category

ALIVE_QUE / ALIVE_ACK
▼ Availability of MIWx : ALIVE_QUE (/ALIVE_ACK)
z Action :
Î This message is sent by the RCF to a dedicated MIWx to request an answer from this PBA.
Î It is used periodically for the supervision of the MIWx by the RCF.
Î The MIWx answers message ALIVE_ACK.
z Parameters :
Î OBCI
Î timer : used for the SMIM to supervise the RCF. The value must always be 0 to inhibit this
feature thus avoiding the RCF to manage additionally spontaneous reinitialisations of the remote
equipment.
5.44

TEST_ASGN
▼ Test assignment : TEST_ASGN
z Action :
Î This message is sent by the RCF to the SMIM to request the DTRE OBCI to establish a loop
between the given circuits. It is used in the overall test procedure. This message is necessary to
modify the pre–assignment of the circuits in the DTRE (i, i+16). Indeed for overall tests it is
necessary to use two OCCs of the network side or two OCCs of the radio side.
Î This message is not acknowledged.
z Parameters :
Î OBCI
Î interworking circuit 1 & interworking circuit 2 : to identify the two interworking circuits from which
two OCCs will be used for the test process.
Note : the reception of the Connection Release by the DTRE will set back the connections to the
initial state.
5.45

IW_MNTCMD / IW_MNTRSP
▼ Establish test connection, or Release test, or Pattern test : IW_MNTCMD (/ IW_MNTRSP)
z Action :
Î to request the MIWX OBC to set up the test configuration for the OCC circuits in the OBCI of the
MIWX. This message is only used for overall tests.
z Parameters :
Î OBCI
Î OCC_ID & OCC-ID_2 : define the two OCCs circuits used in the test. OCC_ID defines the OCC i
under test, OCCID_2 the OCC j taken as reference.
Î test command Î to characterise the purpose of the IW_MNTCMD message:
' establish test connection or release test or pattern test
Î response (IW_MNTRSP) :
' result of the command and may take the following values (each OCC ”result” parameter is
memorized in the SMIM alarms table) :
 successful,
 message not in sequence,
 wrong message parameter,
 OCC not responding,
 Fast Test failed,
 pattern faulty,
 COUT port write failure (Channel OUT on MIWX).
' test_result : to recall from which type of command the message is answering.
5.46


Review
▼ Several Interworking Function (IWF) types can be connected to an SSP, and
supplied by one or several SMIM elements according to the amount of
expected traffic.
▼ The IWF types correspond to the different types of data transmission (i.e. to
handle different types of Basic Services) and also take into account the
capabilities of the MIWx boards (for instance one call with data compression
per MIWB AB board).
▼ Each IWF type is seen by the SSP through a set of two independent
dedicated trunkgroups of bidirectional circuits:
z the first one, called ”network side” trunkgroup, consists in network
dedicated circuits,
z the second one, called ”radio side” trunkgroup, consists in radio
dedicated circuits.
5.48

CIC's declaration
▼ A data call routed from the SSP towards SMIM on a ”radio side” circuit of CIC
= j, is automatically routed back from the SMIM towards the SSP on a
”network side” circuit of CIC = j, and vice versa.
▼ The CIC j designates :

z a time slot value i on the radio side,
z the time slot being i+16 on the network side,
▼ This requires from the SSP an appropriate declaration of the CICs

assigned to the two associated ”radio side” and ”network side” circuits.
5.49

CIC's declaration
▼ The circuits are managed by the SSP by means of an internal #7 signalling
loop which needs the definition of a couple of virtual Point Codes.
▼ The #7 signalling messages associated to the circuit seizure, release etc ...
are sent on this loop by the SSP from an originating virtual PC to a destination
virtual PC. On receipt the SSP inverts the two virtual PCs (destination
becomes origin and vice versa) to process the message.
▼ The couple of virtual Point Codes is unique for all the SMIMs connected to
the RCP. There is a maximum number (16, for information) of trunkgroups
that this couple can manage.
▼ An IWF type is associated to each one of them.
▼ Up to 4096 circuits can be distributed among these trunkgroups.
▼ The virtual point codes are distinct from the point code assigned to the SMIM
and necessary for the MTP, SCCP and SMIMAP signalling between RCP and
SMIM.
▼ The RCP has also the knowledge of this unique couple of virtual PCs in order
to properly identify a faulty board by a PC plus a CIC when the defence
mechanism at board level is on (option F–DA–021 activated).
5.50


SMIM fault reports
▼ Different types of fault reports are generated by a SMIM towards its controlling
RCP, and these are signalled either :
z with an explicit fault report as :
Î DTRE–CALC Alarm Report,
Î IW error,
z or in a response message as :
Î DTRE–CALC Alarm Report,
Î Load Bid,
Î OCCs state response,
Î or MIWX Alarm State Response.
✹ DTRE–CALC Alarm Report

Î Most of these faults make use of the cross–over configuration. After sending back an
acknowledgement, the RCF shall generate a spontaneous message and, depending
on the fault, prevent the SSP from seizing new circuits by forcing the SMIM to set
the RJA bit.
5.52
▼ PMLX/6020 - SMIM FAULT DETECTED ON DTRX BOARD
Meaning: The SMIM notify to RCP the fault detection on DTRX board.
Fault type on DTRX board
z AIS = Reception of continuous "1" on the PCM link.

z CRC41= The number of multiframes received with a wrong CRC4 indicates an error bit rate greater than 10-3
(analysis during 1 second).
z CRC42= The number of multiframes with a wrong CRC4 indicates an error bit rate greater than 10-6 (analysis
during 1 minute).
z ERR1 = The error bit rate has reached 10-3 (count during 1 second the errors in the frame alignment signal).
z ERR2 = The error bit rate has reached 10-5 (count during 1 minute the errors in the frame alignment signal).
z EXT = Problem, external to the reception trunk of the DTRX board.
z HDB3 = Excessive error rate in the HDB3 coding received.
z LFA = Loss of frame alignment on the PCM link.
z LIS = Loss of incoming signal on the DTRX board.
z LKF = The signalling link (TS16) is out of service.
z INT = Problem detected in the reception trunk of the DTRX board.
z MAC = The CALX board did not acknowledge the DTRX's alarm report (the CALX is probably in an
initialisation phase)
z MSR = The DTRX board does not send any more alarm report to the CALX board (DTRX is probably in an
initialisation phase)
z RJA = The PCM link is seen out of service (loss of frame alignment) by the remote entity (SSP).
z SLIP = Slip of the clock signal.

MIWX fault reports
▼ OBC fault reports
▼ According to the fault reports indicated in the message received by the RCF, three types of faults
must be distinguished at this level :
z Load Bid message (on initialisation request) : Faults are due to hardware errors, and RCF
generates a spontaneous message.
z Autonomous restart (major software failure) or autonomous reset (reception of an
unexpected Load Bid message).
z OBC error (Anomaly Report) : The associated faults are mainly due to software errors.
Information is only output as a software anomaly and may be used for debugging
purposes.
▼ OCCs fault reports
z The OCCs fault reports are mainly due to hardware errors. In this case, the RCF must
generate a spontaneous message and, depending on the fault, prevent the SSP from
seizing new circuits.
z OCCs fault reports may be signalled to the RCP on receipt of the following messages :
Î OCCs state response (on initialisation or maintenance request).
Î IW error. Note that it must be acknowledged by the RCF.
Î MIWX Alarm State Response (after RCP switchover or with option F–DA–021 active
after TWDREC expiry).
5.53

SMIM alarms
▼ ”Start of alarm” : SMIM failure or operator command set the SMIM in the state ”out of service”.
▼ ”End of alarm” : recovery due to an external intervention.
▼ AL_SMIM_001 (R00002) :
z The alarm AL_SMIM_001 is generated when the SMIM is set to or gets out from the state ”out of service”.
Î On MMC command
9 creation of the SMIM by MMC : ”Start of alarm” is generated (after its creation, the SMIM is in the state
”Out of Service”)
9 set SMIM ”in service” : ”end of alarm” is generated when SMIM is successfully set into service.
9 set SMIM ”out of service” : ”start of alarm” is generated
9 suppression of the SMIM : ”end of alarm” is generated.
Î On SMIM failure detected by RCP : If a failure indication leads RCP to set the SMIM ”out of service”, a ”start of
alarm” is generated.
▼ Moreover, an other alarm is generated if the percentage of SMIM ”Out of service” reaches a threshold.
▼ AL_SMIM_002 (R00003) :
z The alarm AL_SMIM_002 is sent after an SMIM alarm AL_SMIM_001, when the change of state of one SMIM leads to
modify the percentage of SMIMs ”out of service” in such a way that the defined threshold is reached or no longer reached.
5.54

MIWx alarms
▼ With option F–DA–021 active, the RCP generates MIWX alarms.
▼ ”Start of alarm” : failure (SMIM / MIWX level) or command set a MIWX board from ”In service” to”Fault” or ”Out of service”.
▼ ”End of alarm” : MIWX enters the state ”In Service”.
▼ AL_MIWX_001 (R00009) :
z generated when the MIWX state is set to ”out of service” or ”Fault” (start of alarm) or ”In service” (end of alarm).
Î On MMC command
9 creation of the SMIM : ”Start of alarm” generated (after creation, MIWX are ”Out of Service”)
9 set SMIM ”in service” : ”end of alarm” generated.
9 set SMIM ”out of service” : ”start of alarm” generated.
9 suppression of the SMIM : ”end of alarm” generated for each MIWX.
Î On SMIM failure detected by RCP
9 RCP set SMIM ”out of service” Î”start of alarm” generated for each MIWX found ”In service”.
Î On MIWX failure detected by RCP
9 RCP set the MIWX ”Fault” Î”start of alarm” generated.
Î On isolation of the SMIM
9 ”end of alarm” generated for MIWX not yet in service (but not faulty).
▼ Moreover, another alarm is generated if the percentage of non operational MIWX reaches a threshold.
▼ AL_MIWX_002 (R00010) :
z sent when the change of state of one (or several) MIWX leads to modify the percentage of non operational MIWX in such
a way that the defined threshold is reached or no longer reached.
z N.B. : Non operational MIWX means MIWX declared ”Out of service” or ”Fault”. Percentage of non operational MIWX is
global to the station (all declared MIWX of all declared SMIM).
z To replace a faulty MIWX, the corresponding SMIM has to be put ”out of service” and then ”in service” after the ”fault”
MIWX has been replaced.
5.55

MIWx supervision
▼ When the SMIM is available for data calls, there is a supervision of the
MIWx's done by RCF :
z RCF control periodically (timer TPALVQ) that ALL the MIWx's belonging
to the SMIM configuration are still alive Î present in their slot and fully
functional.
z If a MIWX of the set does not answer (timer TWALVQ), the control is
repeated once and if again the MIWX remains dumb, a restart of the
MIWX is launched.
z Following SMIMAP messages are used:
Î ALIVE_QUE (Availability of MIWX PBA) sent by RCF to a
dedicated MIWX in the SMIM.
Î ALIVE_ACK (Answer from available MIWX) sent back by a MIWX.
5.56

SMIM in test
▼ The aim of the test procedure is to verify the hardware of the SMIM :
z a default profile will be used for the test process, which will depend from the type of board
z only transparent mode is allowed for the test process).
▼ For the interworking boards MIWX :
z hardware is partly tested by autotests,
z logical access to the modems and to the elements involved in the rate adaptation function is tested :
Î A MIWX board contains 6 processors OCC (1 OCC handles 1circuit)
' 3 to the radio side have only a rate adaptation (RA) function,
' 3 to the fixed network side have both a RA function and a modem function (Note 1).
z The test process is split in two steps :
Î reduced initialisation to get :
' the result of the MIWX autotests and,
' the status of CALC and DTRE.
Î Overall tests performed for each pair of circuits of each MIWX board to test modem & RA
functions (SMIMAP "TEST_ASGN" message is sent by the RCF to the SMIM to request the
DTRE OBCI to establish a loop between the given circuits).
' a pattern received from RCF in the SMIMAP "IW_MNTCMD" message is sent on internal
loop (i is circuit under test, j is the reference) :
' MIWX_OBC Î OCCi Î modem/Codec (or RA) Î MIWX_OBCI Î DTRE_OBCI Î
MIWX_OBCI Î modem/Codec (or RA) ÎOCCj Î MIWX_OBC.
' OBC which compares it. The test result will be sent back to the RCP via the SMIMAP
"IW_MNTRSP" message.
5.57
▼ Note 1 :
except MIWA fax boards which have only modem functions on the network side
▼ Test assignment: TEST_ASGN

This message is sent by the RCF to the SMIM to request the DTRE OBCI to establish a loop between the given
circuits. It is used in the overall test procedure. This message is necessary to modify the pre–assignment of the
circuits in the DTRE (i, i+16). Indeed for overall tests it is necessary to use two OCCs of the network side or two
OCCs of the radio side.
This message is not acknowledged.
Parameters exchanged on the interface :
z OBCI identification
z interworking circuit 1
z interworking circuit 2
▼ Establish test connection: IW_MNTCMD

This message is sent by the RCF to the SMIM to request the MIWX OBC to set up the test configuration for the OCC
circuits in the OBCI of the MIWX.
This message is only used for overall tests.
z OCC_ID (under test)
z test_command used to characterise the purpose of the IW_MNTCMD message :
Î establish test connection
Î release test
Î pattern test
z OCC_ID_2 (reference) if (test_command = "establish test connection"), or
z test_pattern if (test_command = "pattern test"), or
z no info if (test_command = "release test")

SMIM in test
▼Maintenance response : IW_MNTRSP
z OCC_ID
z result :
Î successful,
Î message not in sequence,
Î wrong message parameter,
Î OCC not responding,
Î Fast Test failed,
Î pattern faulty,
Î COUT port write failure (Channel OUT on MIWX).
z test_result : this parameter recalls from which type of command the message is answering
5.58

Periodical mechanism to block/unblock SMIM circuits
▼ If F–DA–021 is active the circuits of a SMIM board MIWX which are ”out of service” or
”fault” are blocked by the SSP on RCP order.
▼ To keep the consistency between the circuits state known by the RCP and the real
state of the circuits at SSP level, a periodical mechanism is performed :
z The identity and the state (”fault”, ”Out of service”, ”In service”) of all the created
MIWX boards are memorised and saved on the standby system.
z Periodically, with a frequency defined by a system parameter (TPBLUB : default
value = 6h, range 1h to 24h) :
Î for all the MIWX known as ”in service” by the RCP an UPDATE message
(unblocked) to SSP, in order to guarantee the unblock state of the
concerned SSP circuits,
Î for all the MIWX known as ”fault” or ”out of service” by the RCP an
UPDATE message (blocked) to SSP in order to guarantee the block state
of the concerned SSP circuits.
5.59

5.6 Data structure

5.6 Data structure
F-DA-021
▼ F-DA-021
z Sys. Par.: PARNAME = none, BOOLVAL

z RTDMS database: RELNAME = PYR_SYSB, attribute: D_DA_021
▼ F-DA-021 determine the level of defence mechanism for SMIM device.
▼ Meaning:
z TRUE: SMIM defence at board level applies, including the periodic
audit on SMIM status.
z FALSE: only SMIM defence at SMIM level applies.
5.61

5.6 Data structure
F-DA-022
▼ F-DA-022
z Sys. Par.: PARNAME = P2B_F_DA_022, BOOLVAL

z RTDMS database: RELNAME = PYR_SY2B, attribute: D_DA_022
▼ F-DA-022 : availability of MMC for SMIM test from RCP.
▼ Meaning:
z TRUE: the MMC allowing the SMIM test is available.
z FALSE: no MMC for SMIM test.
5.62

5.6 Data structure
F-DA-029
▼ F-DA-029
z Sys. Par.: PARNAME = PB_F_DA_029, BOOLVAL

▼ F-DA-029 : activation of T30 Flag stuffing for fax transparent.

z It is useful in a satellite environment to reduce the risk of fax calls failure
due to excessive delay.
▼ Meaning:
z TRUE : the RCP requires the SMIM activation of the T30 flag stuffing
mechanism with Fax Transparent.
z FALSE : T30 flag stuffing is not allowed.
5.63

5.6 Data structure
F-DA-047
▼ F-DA-047
z Sys. Par.: PARNAME = none, BOOLVAL

▼ F-DA-047 : RLP2 in single slot mode is offered in RCP.

z May be activated only if some Non Transparent data or fax services are
activated.
▼ Meaning:
z TRUE : the RCP initialises the IWF in such a way, that concerning fax/data
calls treated in the Non Transparent mode, the IWF always tries to
negotiate with the MS the use of the version 2 of the Radio Link Protocol
on a single channel.
z FALSE : the RCP initialises the IWF in such a way, that concerning fax/data
calls treated in the Non Transparent mode, the IWF always negotiates with
the MS the use of the versions 0 or 1 of the Radio Link Protocol on a single
channel.
5.64

5.6 Data structure
TPBLUB
▼ TPBLUB
z Sys. Par.: PARNAME = none, BINARY

z RTDMS database: RELNAME = PYR_SYSG, attribute: D_TPBLUB
▼ With option F–DA–021 active

▼ TPBLUB : Timer used to active the periodic treatment of blocking /
unblocking the SMIM circuits.
▼ Default value :
z 6h ,range between 1h/24h.
▼ Forbidden value : 0
5.65

5.6 Data structure
TWDISO
▼ TWDISO

z RTDMS database: RELNAME = PYR_SYSG, attribute: D_CNTISO

▼ TWDISO : This timer is used to supervise the isolated state of a SMIM.
z Its is a multiple of TSMPOL (timer used to query about the
accessibility of SMIM DPC when the SMIM is in ISOLATED state).
▼ Default value :
z 20 seconds = 180*TSMPOL in order to cover a cold start of the SSP.
5.66

5.6 Data structure
TWDREC
▼ TWDREC

z RTDMS database: RELNAME = PYR_SYSG, attribute: D_TWREC

▼ TWDREC : Timer used to supervise the disappearance of a hardware
error on the MIWX OCC.
▼ Default value = 2 minutes.
5.67

5.6 Data structure
TPALVQ
▼ TPALVQ

z RTDMS database: RELNAME = RYR_SYSG, attribute: D_TPALVQ
▼ TPALVQ : This periodic timer is used to send SMIMAP message

"ALIVE_QUE" to control the availability of a given MIWx.
▼ Value = 1 minute.
5.68

5.6 Data structure
TWALVQ
▼ TWALVQ

z RTDMS database: RELNAME = RYR_SYSG, attribute: D_TWALVQ
▼ TWALVQ: This timer is used to wait for the reply of a given MIWx Î
SMIMAP message "ALIVE_ACK" to message "ALIVE_QUE".
▼ Value = 5 seconds.
5.69

5.6 Data structure
CNTAL
▼ CNTAL

z RTDMS database: RELNAME = RYR_SYSG, attribute: D_CNTAL

▼ CNTAL : Threshold of no answer to the SMIM maintenance message
READ_AL_ST
▼ Value = 2 seconds.
5.70

5.7 Exercise
'Check the ability of your site to test

SMIM's equipment by MMC
'Interrogate the alarms and states of
your SMIM's, MIWx devices.
'If faults, try to fix them.
Time allowed :
10 minutes
5.71

5.8 Evaluation
▼ Objective : to maintain and to operate

SMIM's equipment.
Thank you for answering

the self-assessment
of the objectives sheet
5.72

SMIM Operation

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

SMIM Operation

Uploaded by

Copyright:

Available Formats

Alcatel 900/1800 NSS

5 : SMIM operation & maintenance

© Alcatel University - 8AS 90200 0675 VT ZZA Ed.01 5.1

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.1

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.2

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.3

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.4

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.5

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.6

© Alcatel University - 8AS 90200 0675 VT ZZA Ed.01 5.7

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.7

INAP (with SSP) ▼ The circuit channels pass through the

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.8

▼ SMIM faults counter :

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.9

2 Mbit/s PCM links

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.10

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.11

Load Bid Realised in

OCCs state response

▼ DTRE–CALC ensemble Initialisation :

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.12

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.13

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.14

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.15

 ( See PMLX/6020 - SMIM FAULT DETECTED ON DTRX BOARD )

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.16

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.17

5.2 SMIMAP data call

© Alcatel University - 8AS 90200 0675 VT ZZA Ed.01 5.18

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.18

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.19

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.20

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.21

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.22

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.23

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.24

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.25

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.26

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.27

5.3 SMIMAP maintenance

© Alcatel University - 8AS 90200 0675 VT ZZA Ed.01 5.28

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.28

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.29

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.30

▼ Own & other DTRE alarms :

▼ SMIM alarms, see also spontaneous messages :

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.31

▼ See also spontaneous messages :

 PMLX/6027 - OCCS FAULT ON MIWX

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.32

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.33

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.34

▼ Fast test on following points : ▼ See also spontaneous messages :

▼ Error class :  that fast test result parameter is memorized in the

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.35

▼ See also spontaneous messages :

 PMLX/6025 - MIWX OBC INITIALIZATION FAILURE

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.36

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.37

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.38

© Alcatel University - 8AS 90200 0675 VH ZZA Ed.01 Page 5.39

RLP T1 acknowledgement timer for full rate channels at 14.5kbps.

RLP T1 acknowledgement timer for full rate channels at 12kbps.

( See PMLX/6020 - SMIM FAULT DETECTED ON DTRX BOARD )

PMLX/6027 - OCCS FAULT ON MIWX

▼ Error class : that fast test result parameter is memorized in the

PMLX/6025 - MIWX OBC INITIALIZATION FAILURE