Inter-Working Function (IWF) Overview Circuit Switched Data (CSD) Services

Inter-Working Function (IWF) Overview
Circuit Switched Data (CSD) Services
Suresh Pallikondan
October 25, 2010
All Rights Reserved © Alcatel-Lucent 2007

Agenda
1. Overview Circuit Switched Data and Service Types
2. IWF Configurations
3. ANSI IWF Network
4. IWF Components
5. IWF Architecture
6. CSD Call Scenarios
7. IWF Connections
8. Troubleshooting
9. IWF Past Issues
IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

Overview of CSD Services
 Circuit Switched Data enables GSM subscribers to transfer data,

fax or access the Internet over the wireless network.
 The GSM network provides the Inter Working Function (IWF),

which performs protocol conversion between the radio and the
fixed networks.
 The end users will experience very little difference from that of
using a standard wired phone line.
 Instead of plugging the computer modem into a wired phone jack,

mobile subscribers can connect their computer into their GSM
phone and use the same software as they use for wired access.

CSD Service Types
 Modem Service - to establish data connection to any modem in the

fixed network. This is an asynchronous bearer service (BS20)
supporting both Transparent and Non-Transparent connection. Modem
Service is only available to GSM subscriber.
 Digital Service – to establish data connection to ISDN equipment

with V.110 rate adaptation. This is also an asynchronous bearer
service (BS20) supporting both Transparent and Non-Transparent
connection. Digital Service is only available to GSM subscriber.
 G3 Fax Service – to send or receive facsimile from any fax machine

connected to the fixed network. This is a teleservice (TS62) with
synchronous transparent bearer. Fax transmission rate of 9.6 Kbit/s
and 7.2 Kbit/s are supported. G3 Fax Service is only available to GSM
subscriber.

Acronyms
ANSI – American National Standards Institute

CSD – Circuit Switched Data
EGCP – Enhanced Gateway Control Protocol
ESM – Ethernet Switch Module
ITU – International Telecommunication Union
IWF – InterWorking Function
SAM – System Administration Module
SGW – Signaling Gateway
SIM – Signaling Interface Module
SMIM – Standalone Mobile InterWorking Module
SMIMAP – Standalone Mobile InterWorking Module Application Protocol
MIWB – Mobile InterWorking Unit Version B
MIWD – Mobile InterWorking Unit Version D
MIWX – Mobile InterWorking Generic
UDI – Unrestricted Digital Information
WAP – Wireless Application Protocol

Supported Bearer Services
BS Fixed Nwk Access Transfer Rate QoS GSM UMTS

Code User Rate Structure Capability Adaptatio Attributes Support Support
n
BS20 9.6 kbit/s Asynch 3.1 kHz Transparent Y
9.6 kbit/s Asynch UDI V.110 Transparent Y
0.3 kbit/s Asynch 3.1 kHz Non-Trans Y
9.6 kbit/s Asynch 3.1 kHz Non-Trans Y N
56 kbit/s Asynch 3.1 kHz Non-Trans Y N
9.6 kbit/s Asynch UDI V.110 Non-Trans Y N
56 kbit/s Asynch UDI V.110 Non-Trans N N
BS30 56 kbit/s Synch RDI H.223/245 Transparent N N
64 kbit/s Synch UDI H.223/246 Transparent N Y

IWF supported Configurations
IWF can be deployed in 3 configurations:
 Distributed IWF
 Co-located with WMG
 One IWF per WMG
 Local IWF ( TMO Configuration)
 Co-located with WMG
 Shared IWF between multiple MGW
 Requires interconnect between MGWs
 Remote IWF (Same as local with WCS multiprotocol support)
 Co-located with WCS (SGW-IWF is absent)
 Shared IWF between multiple MGW
 Requires interconnect between MGWs

Shared and Distributed IWF
 Shared IWF configuration – IWF hardware is only connected to

one MGW, but IWF resources are shared by all other MGWs within one
WCS System. This configuration allows all available IWF resources to
be efficiently shared between the MGWs. (TMO Configuration)
 Distributed IWF configuration – each MGW has its own co-located

IWF hardware. Therefore, Interconnect between MGWs is no longer
required for CSD calls. However if Interconnect is configured, WSS
can use the Interconnect to access the IWF resource in other MGW
when there is no local IWF resource available (e.g. local congestion).

Shared IWF Configuration
IP
Mobile Data
Enabled BSSAP IP TDM
Laptop /SS7 IP SMIMAP
/IP Interconnect
ISUP
/SS7
City 2
TDM
City 1 IWF
Interconnect
connect

Distributed IWF configuration
IWF
connect
SMIMAP City 3
/IP
SMIMAP
/SS7
IP
WAP
Handset
SMIMAP
Mobile Data
/SS7
Enabled BSSAP
Laptop /SS7 IP
IP
ISUP
/SS7
City 2
City 1 TDM
Interconnect IWF
connect

WCS IWF Configuration
 Standalone IWF, can WCS

WSS
be connected to IWF Control
MGW-7540 using T1
or E1,signaling
between WCS and
SGW-IWF is SMIMAP BSC
proprietary protocol Signaling IWF Signaling Link
Link SMIMAP
 IWF hardware WMG
consists of a number
of Stand-alone Mobile BSC To Fixed Network
Interworking Modules
(SMIM). T1 or E1
link
 SMIM supports E1
interface with A-law
encoding. An E1/T1
converter is
integrated into the SMIM
IWF to support T1 Radio Network IWF
interface. Protocol Protocol

IWF for ANSI Network
 The IWF is controlled by the WCS with the SMIM Application Protocol
over IP interface.
 The IWF Signalling Gateway (SGW-IWF) provides the functionality to

convert SMIMAP messages from IP to SS7 format. The SS7 SMIMAP
message is sent in the control channel, which is multiplexed with the
T1 channels from the MGW to be connected to the SMIM.

IWF for ANSI Network
IP
WSS IWF-SGW
IWF Signaling (E1)
CH1
: T1
CH12 E1
SMIM
E1/T1 convertor
CH13
: Up to
CH23
8
CH1 SMIM
: T1
CH12 E1
SMIM
CH13
:
WMG CH23
IWF

SGW-IWF Components
Convert SMIMAP messages from IP to SS7 format.
SGW-IWF front view

SGW-IWF Components
SGW-IWF rear view

SGW-IWF Components
SGW-IWF converts SMIMAP messages from IP to SS7 format.
Signaling Interface Module (SIM) - provides signaling to the all the

SMIMs.
 For ANSI network, the signaling is connected through the T1/E1
Converter.
 The T1-E1 converter then multiplexes the signaling channels from the
SIM in the SGW-IWF to the bearer T1 coming from the Media
Gateway and passes it to the SMIMs
System Administration Module (SAM) – provides O&M, similar to

WCS SAM
Ethernet Switch Module (ESM). The ESM provides Ethernet

connectivity, similar to WCS CCPU SIM shelf

IWF-SMIM Components
 Each SMIM provides 12 IWF circuits. A fully equipped standard IWF

frame consists of 8 SMIMs, which provides 96 IWF circuits. A fully
equipped extension IWF frame consists of 10 SMIMs, which provides
120 IWF circuits.
 Each mobile originating or mobile terminating CSD call requires one

IWF circuit. A mobile-to-mobile CSD call requires one IWF circuit in
the originating WSS and one IWF circuit in the terminating WSS.

IWF-SMIM Components
 Interworking Functions (IWFs) - supports non–voice communications by

handling the interworking between the fixed network (normal transmission
mode) and the mobile network (specific digital transmission), by performing
rate and protocol adaptation whenever needed.
 Stand–alone MobileInterworking Module (SMIM) - performs the

Interworking Functions using Alcatel-Lucent proprietary SMIM Application
Protocol (SMIMAP).
 SMIM shelf is comprised of 2 SMIMs, left one and right one.
SMIM (n) Left SMIM (n+1) Right
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33
CONV27A
CONV27A
DTRE
CALC
MIWx
MIWx
MIWx
MIWx
MIWx
MIWx
DTRE
MIWx
MIWx
MIWx
MIWx
CALC
M01 M02 M03 M04 M05 M06 M07 M08 M09 M10 M11 M12 M13 M14 M15 M16

IWF-SMIM Components
SMIM shelf
 1 CALC board (clock + alarm)
 1 DTRE board (digital trunk E1)
 1 CONV board (converter)
 4 MIWx boards (treatment of CSD calls)
MIWx boards (treatment of CSD calls)

 2 versions of MIWx available – MIWB and MIWD
 Different MIWx (MIWB/MIWD) cannot be mixed within SMIM
 1 MIWx can process up to 3 CDS calls, up to 12 calls per SMIM
 Each SMIM is connected to WMG through an E1 (31 TS PCM
through E1-T1 converter)
 Signaling channel TS16
 Traffic channels, TS1-15 for radio, TS17-31 for network
 One CSD call uses TS x and TS x+16 where x is 1-15
 WCS A5060 synchronize and manage SMIM through TS16

IWF Architecture
WSS
S S S S D D C C C C S S E E
I I I I D D C C C C A A S S
M M M M M M M M M M M M M M
BSC
Signaling
IP
T1 T1
H.248/ SMIMAP/
UDP/IP TCP/IP
To BSC
T1
IWF SGW
T1 S S S S E E
I I A A S S
M M M M M M
To Other
MGWs IWF Signaling
T1 E1 E1
E1 SMIM
T1
E1/T1 Converter
T1 E1
T1 SMIM
OC3 E1
To PSTN T1 SMIM
T1 T1 E1 SMIM
T1
MGW DACS IWF

IWF Architecture
 SMIMAP protocol, the SMIM interfaces for data call control

 Bearer Capability (BC), Low Layer Compatibility (LLC), and High Layer
Compatibility (HLC) Information Elements (IEs) may be used to
describe a Tele Service.
 BC–IE indicates a requested bearer service to be provided by the
network and may be used in conjunction with HLC–IE to identify a
tele-service.
 LLC and HLC–IEs are essentially meant for user–to–user
compatibility checking.

IWF Architecture
SgwIwf and SgwIwfProxy are two specific modules in order to make

the WCS run with SMIM equipment. Primarily supports call signaling
towards the SMIM through the SGW-IWF via IP Protocol.
IwfMonitor is monitoring the connectivity between ITU SGW-IWF and
SMIM. Primarily supports reporting SMIM alarms and error reports to
the WCS.
 SgwIwf runs on both ANSI WCS SAMs

 IwfMonitor runs on both ITU SGW-IWF SAMs
 SgwIwfProxy runs on ITU SGW-IWF SIM where SgwMtp3 is running

Simplified Signaling View
WSS SGW-IWF
(MAIN IWF)
To
SIM SAM SAM SIM DIST/EXP
BSS ESM ESM
650 Netra 650 650 IWFs
Or
ISUP IP Network
SgwIwf
IwfMonitor
SgwIwfProxy
SMIM

E1-T1 Converter
E1s to SMIM 1 – T1s to MGW for

Serial control port
SMIM 8 SMIM 1 – SMIM 8
E1 to SIM 2-1 T1 to MGW for

SMIM 10
E1 to SIM 1-1 T1 to MGW for
SMIM 9
E1 to SMIM 10
E1 to SMIM 9

Standard IWF - Patch Panel Connectivity
T1/E1Converter “Inner” 32 port RJ45 “Outer”

Slot3 Port 1 T1 T1
1 1
Slot3 Port 2 T1 T1
2 2
T1 T1
Slot3 Port 3 3 3
Slot3 Port 4
T1 4 4 T1 To WMG
T1 5 5 T1
Slot3 Port 5
T1 6 6 T1 T1 CI ports
Slot3 Port 6 T1
Slot3 Port 7 T1 7 7
T1
(bearer circuits)
T1 8 8
Slot3 Port 8
9 9 Ethernet ESM1 Port
10 10 Ethernet ESM2 Port
E1 E1
Slot2 Port 3 11 11 SIM1 Port 1
E1 E1
E1 E1
E1 E1
15 15
16 16
E1 17 17 E1 SMIM01
Slot1 Port 1
Slot1 Port 2 E1 18 18 E1 SMIM02
E1 19 19 E1
Slot1 Port 3 SMIM03
E1 20 20 E1
Slot1 Port 4 SMIM04
E1 21 21 E1
Slot1 Port 5 SMIM05
25 25
26 26
27 27
28 28
Slot4 Port 1 T1 29 29 T1
Slot4 Port 2 T1 T1 To Dist. IWFs
30 30
Slot4 Port 3 T1
31 31
T1 DACS
Slot4 Port 4 T1 32 32 T1

CSD Call Scenarios
MGW_1 MGW_1
BSC_1 IWF BSC_1 IWF
Circuit Circuit
PSTN
IWF
BSC_2 Circuit
MGW_2 MGW_2
Mobile to Mobile CSD call Mobile to Land CSD call

High Level Call Flow MO
WSS
MS BSS MSC/VLR SMIM PSTN DCE
CM Service Req
CM Service Req
Immediate Assignment
Authentication Request
Authentication Response
CipherModeCmd
CipherModeComplete
Setup (PLMN BC, ITC=3.1khz)
Call Proceeding (Modified PLMN BC)

BC analysis identifies an
Assigment Request (CH. Type) IWF is required
Assigment Complete IAM (ITC=3.1 kHz) Power Ring
Alerting ACM
Off hook
ANM
Connect
XConnReq (modified PLMN BC)
ConnAck
Connect Ack
RLP setup Modem Neg.
Data phase

High Level Call Flow MT
DCE PSTN GMSC HLR MSC/VLR SIMM BSS MS

Off hook
Dial B-number
IAM
SRI (msisdn=B, ISDN BC,
PRN (B’s PLMN BC) Identifies MSB
HLC, LLC)
is configured
SRI Ack (MSRNb) PRN Ack(MSRNb) for Modem
IAM (no BC) Page

Page
Channel Request
Immediate Assignment
MS connect Established Page Rsp
CipherModeCmd
CipherMOdeComplete
Setup (PLMN BC, ITC=3.1kHz)

Call Confirm (Modified BC)
Assignment Request (CH. Type)
Assignment Completee
ACM Alerting
Ring Back ACM
Connect
Connect Ack
AMN XConnReq (Modified PLMN BC)

ConnAck
Modem Neg. RLP setup
Data phase

Single call trace for 3.1K HZ
11:37:47.554 ../OamMtDecode.cc(3354) APP_1 - MQ waterlevel, number queued: 0, 0

Time: 12/02/2008 11:37:47.549
Cat: CCSP Primitive: CCSP_ORIGINATION_ATTEMPT
Src: CP_CALLM_ID (5) Tid: 05000529 Load Factor (0)
Dest: CS_SP_ID (5) Tid: 00000000
IE_INITIAL_ATTEMPT[0x472] 1
IE_PARTY_ID[0x3ff] ORIG_PARTY_ID
IE_IMSI[0x470] 0x0F 0x13 0x80 0x27 0x20 0x27 0x00 0x60 0xF0 0x35 0x72 0x5D ( 310872027200060 )
IE_GENERIC_BEARER_CAP[0x4dd] CS_GSM TC_A31KHZ TM_CIRCUIT TR_64KBIT UL1_DEFAULT
STRUCT_SVC_DATA_UNIT_INTEGRITY ?unknown? RA_NO_RATE_ADAPTION OI_NOTPRESENT ORA_NOTPRESENT
OM_NOTPRESENT LLIN_NOTPRESENT SYNASYNC_ASYNC NEGO_IN_BAND_NOT_POSSIBLE CE_NON_TRANSPARENT
IDS_DTAP INTR_16KBIT NCRX_NOTACC NCTX_NOTREQ UR_9600 SB_1_BIT PAR_NONE DB_8_BITS
FNUR_NOTPRESENT MT_AUTOBAUDING_TYPE1 TR_64KBIT
IE_BSS_POINT_CODE[0x47e] PC:174 NwkId:0 Type:0
IE_CALLED_PARTY_NUMBER[0x3eb] 18720272002 NATIONAL NPI_ISDN PRES_RSTR_ALLOWED
SCR_USER_PROVIDED_NOT_VER GEN_NAME_IND_NOTPRESENT INN_IND_NOTPRESENT NI_IND_NOTPRESENT 11
IE_MOBILE_TYPE[0x485] 1
IE_PCARDNUM[0x47d] 5
IE_CELL_GLOBAL_ID[0x494] 0x03 0x01 0x00 0x09 0x00 0x0F 0x00 0x48 0x00 0x01 0x00 0x00 0x02 0x2D 0x00 0x02
IE_COUNTRY_CODE[0x4a0] 1
IE_BASIC_SVC_CODE[0x4d5] 2 ST_BS BC_DATA_CDA_9600

Single call trace for UDI Call
11:27:52.010 ../OamMtDecode.cc(3354) APP_1 - MQ waterlevel, number queued: 0, 2

Time: 12/02/2008 11:27:52.006
Cat: CCSP Primitive: CCSP_ORIGINATION_ATTEMPT
Src: CP_CALLM_ID (5) Tid: 05000525 Load Factor (0)
Dest: CS_SP_ID (5) Tid: 00000000
IE_INITIAL_ATTEMPT[0x472] 1
IE_PARTY_ID[0x3ff] ORIG_PARTY_ID
IE_IMSI[0x470] 0x0F 0x13 0x80 0x27 0x20 0x27 0x00 0x60 0xF0 0x35 0x6F 0xE1 ( 310872027200060 )
IE_GENERIC_BEARER_CAP[0x4dd] CS_GSM TC_UNRDIG TM_CIRCUIT TR_64KBIT UL1_DEFAULT
STRUCT_SVC_DATA_UNIT_INTEGRITY ?unknown? RA_V110_X30 OI_NOTPRESENT ORA_NOTPRESENT OM_NOTPRESENT
LLIN_NOTPRESENT SYNASYNC_ASYNC NEGO_IN_BAND_NOT_POSSIBLE CE_NON_TRANSPARENT IDS_DTAP INTR_16KBIT
NCRX_NOTACC NCTX_NOTREQ UR_9600 SB_1_BIT PAR_NONE DB_8_BITS FNUR_NOTPRESENT MT_NONE TR_64KBIT
IE_BSS_POINT_CODE[0x47e] PC:174 NwkId:0 Type:0
IE_CALLED_PARTY_NUMBER[0x3eb] 18720272002 NATIONAL NPI_ISDN PRES_RSTR_ALLOWED
SCR_USER_PROVIDED_NOT_VER GEN_NAME_IND_NOTPRESENT INN_IND_NOTPRESENT NI_IND_NOTPRESENT 11
IE_MOBILE_TYPE[0x485] 1
IE_PCARDNUM[0x47d] 5
IE_CELL_GLOBAL_ID[0x494] 0x03 0x01 0x00 0x09 0x00 0x0F 0x00 0x48 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x02
IE_COUNTRY_CODE[0x4a0] 1
IE_BASIC_SVC_CODE[0x4d5] 1 ST_BS BC_DATA_CDA_9600

Trouble Shooting
1. Alarms and Events

2. Key Performance Indicators
3. Auto Monitoring

Alarms and Events
Alarm Source: CSD

Alarm Numbers: 61230 thru 61247

Key Performance Indicators (KPI)
SGWIWFGRPPERF
Provides IWF trunk/group level information like resources availability,
attempts and usage Sec’s
Useful to determine SMIM/ckts OOS, general call failures, resource
planning etc
SYSIWFSMIMPERF
Provides SMIM level information like error/alarm reports received,
connection error received, forced release from IWF etc
Useful to determine SMIM level hardware issues etc

Auto Monitoring
MNMSS943_sam_1_1_1 SAM001:> viewstats -k IWF
Note: defaulting to 1 interval, override with one of -hours -date -intervals -time
KPI IWF 2010-10-21 16:00 -> 2010-10-21 16:15 (1 Intervals)
IWF_ALARM_RX SUM: 0
IWF_CONNREQ_TX SUM: 1
IWF_FORCERLS_RATE CON: 1 FRLS: 0 PERC: 0.00%
IWF_FORCERLS_RX SUM: 0
IWF_INSV_PERC CKTS: 48 INSV: 48 PERC: 100.00% (Critical Alert SMIM OOS at 0%)
IWF_MODIGITALCALLS SUM: 0
IWF_MOFAXCALLS SUM: 0
IWF_MOMODEMCALLS SUM: 0
IWF_MTDIGITALCALLS SUM: 0
IWF_MTFAXCALLS SUM: 0
IWF_MTMODEMCALLS SUM: 1

General Trouble Shooting
Issue: Individual SMIM in IWF is OOS

Check for DPC Pause alarms for SMIM DPC. If alarms are present log into the
SGW-IWF and check signaling link towards respective SMIM is INSV. If OOS
lock and unlock links, reseat DTRE card or power cycle SMIM to get the
link/SMIM in-service.
Issue: All SMIM’s in IWF are OOS
Check for Signaling issues or DPC pause alarms. Check for proxy linkdown/up
alarms. If Proxy link alarms are generated check the IP link status between
the WCS and SGW-IWF. If the IP link is inactive check the IP connectivity
between WCS and SGW-IWF. Ensure that all the process are running on the
SGW-IWF. Restart SGW-IWF cards to restore IP links and bring back IWF in-
service.
Issue: Individual MIWX card is OOS
Check the parent IWF SMIM is INSV. If not bring the SMIM INSV. Look for
Hardware error reports for these MIWX cards if any. If no hardware alarms
try reseat/reset the MIWX card to bring them in-service.
Issue Multiple MIWX card are OOS
Check the parent IWF SMIM is INSV. If not bring the SMIM INSV.
Reseat/reset the DTRE, CALC, or MIWX card to bring them in service

SGW-IWF signaling to IWF SMIM frame

WCS IWF SGW IP group

IWF- SMIM

SMIM-MIWX

Trouble shooting Call failures
Issue: Call failures immediately after call setup

Most call failures after setup are due to bearer issue during Modem in-band negotiations.
Look for any connection error, Conn Ack error or FCD Rel error events on the WCS.
Previous issues seen
Check for any errors in the RADCOM T1/E1 converter
Check for any configuration and errors./alarms in DACS
General steps to follow for bearer errors

(1) Restart of IWF Signaling Gateway SAMS and SIMs
(2) Verification of RAD configuration and operation
(3) Verification of bearer path cross connects
(4) Reset of RAD T1/E1 convertor
(5) Switch of DCL-B (active) to DCL-A (standby)
(6) Verification that IVQE setting is not enabled on Tellabs DAC
Capture SCT for failing call and look for following errors

IWF past issues observed
NYIWF852 – Buzzing noise

Resolution – correct T1 cross-connect from MGW-DACS-IWF
From NYMSS852 logs and failed call SCT traces errors observed:
ERROR - IWF Connection/Bearer error
ERROR - N2_TMES_UNSUCC_RETRSMTD
MODEM_FAIL_DURING_TRAIN
MODEM_DT_PROT_INCOMP
MODEM_NO_ANSWER
ATIWF997 – CSD failure

Resolution – correct DACS
From ATMSS997 logs and failed call SCT traces errors observed:
ERROR -IWF Connection/Bearer error
ERROR - N2_TMES_UNSUCC_RETRSMTD
MODEM_FAIL_DURING_TRAIN
MODEM_NO_ANSWER

CLMSS980/System Wide CSD call failures for Arbitron

Resolution – CpCallm software fix for correct cut through in EGCP when Inter
WMG interconnect are involved.
From CLMSS980 logs and failed call SCT traces errors observed:
ERROR -IWF Connection/Bearer error
SMIM/IWF OOS during patching/SAM switchover at multiple sites

Resolution – TCP connection failures causing status mismatch between SAM’s.
Software fix
From multiple sites involved observed mismatch in SgwIwf diagnostic request
on both SAM’s
PHIWF940 – non transparent call failure
Resolution – clock out of sync, bad Common Logic card, replace RAD box since
firmware/hardware are incompatible.
SFIWF40 – Major alarm BPV error
Resolution – bad connection at the patch panel

XXIWFXX – SMIM/MIWX bouncing

Resolution – correct ESM/Corenet Router settings
SEIWF894 – 30% secure call failure
Resolution – swapped MIWB with MIWD

www.alcatel-lucent.com

Inter-Working Function (IWF) Overview Circuit Switched Data (CSD) Services

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Inter-Working Function (IWF) Overview Circuit Switched Data (CSD) Services

Загружено:

Авторское право:

Доступные форматы

Inter-Working Function (IWF) Overview

Circuit Switched Data (CSD) Services

All Rights Reserved © Alcatel-Lucent 2007

1. Overview Circuit Switched Data and Service Types

3. ANSI IWF Network

6. CSD Call Scenarios

9. IWF Past Issues

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

 Circuit Switched Data enables GSM subscribers to transfer data,

 The GSM network provides the Inter Working Function (IWF),

 Instead of plugging the computer modem into a wired phone jack,

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

 Modem Service - to establish data connection to any modem in the

 Digital Service – to establish data connection to ISDN equipment

 G3 Fax Service – to send or receive facsimile from any fax machine

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

ANSI – American National Standards Institute

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

BS Fixed Nwk Access Transfer Rate QoS GSM UMTS

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

IWF can be deployed in 3 configurations:

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

 Shared IWF configuration – IWF hardware is only connected to

 Distributed IWF configuration – each MGW has its own co-located

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

 Standalone IWF, can WCS

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

 The IWF Signalling Gateway (SGW-IWF) provides the functionality to

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

Convert SMIMAP messages from IP to SS7 format.

SGW-IWF front view

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

SGW-IWF rear view

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

SGW-IWF converts SMIMAP messages from IP to SS7 format.

Signaling Interface Module (SIM) - provides signaling to the all the

System Administration Module (SAM) – provides O&M, similar to

Ethernet Switch Module (ESM). The ESM provides Ethernet

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

 Each SMIM provides 12 IWF circuits. A fully equipped standard IWF

 Each mobile originating or mobile terminating CSD call requires one

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

 Interworking Functions (IWFs) - supports non–voice communications by

 Stand–alone MobileInterworking Module (SMIM) - performs the

SMIM (n) Left SMIM (n+1) Right

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

MIWx boards (treatment of CSD calls)

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

 SMIMAP protocol, the SMIM interfaces for data call control

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

SgwIwf and SgwIwfProxy are two specific modules in order to make

 SgwIwf runs on both ANSI WCS SAMs

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

E1s to SMIM 1 – T1s to MGW for

E1 to SIM 2-1 T1 to MGW for

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010

T1/E1Converter “Inner” 32 port RJ45 “Outer”

IWF Workshop All Rights Reserved © Alcatel-Lucent 2010