Logic Modules

Appendix E
GSM Mobile IN Overview

t io
e n na
lly
t
In

Bl n
a
k

EN/LZT 123 3974 R3B

 E Logic Modules

E Logic Modules
Table of Contents

Topic Page

CONTROL TYPES AND LOGIC MODULES IN SERVICE

CREATION.........................................................................................183

CONNECT VERSION 1......................................................................184

GENERAL DESCRIPTION ........................................................................................ 184
DATA.......................................................................................................................... 184
DATA MODULE LEVEL ............................................................................................. 185
ROW LEVEL (CONNECT ARGUMENTS) ................................................................. 185

CUSTOMER CONTROL PARAMETERS ..........................................189

INTERWORK DESCRIPTION.................................................................................... 189

EN/LZT 123 3974 R3B –i–

GSM Mobile IN Overview

t io
e n na
lly
t
In

Bl n
a
k

– ii – EN/LZT 123 3974 R3B

 E Logic Modules

CONTROL TYPES AND LOGIC MODULES IN SERVICE

CREATION
When creating a service, the designer chooses the Control Types
which are to be used in the service and drag and drops them into
the service window. Once in this window, they become known
as Logic Modules (LMs).

The next step is to connect the Logic Modules (LMs) together in

the specified way. At this stage, the service layout should match
the required layout. However, some important work remains
undone.

For every LM, there are many parameters to define. Based on

the values of these parameters, the functionality of the Control
Type will change, e.g. with a parameter setting, the USERINT
Control Type can be defined to play a repeated announcement
instead of the normal single playing.

In this appendix, the parameters used with the CONNECT

Control Type are given as an example of the parameters which
must be defined.

EN/LZT 123 3974 R3B – 183 –

GSM Mobile IN Overview

CONNECT VERSION 1

GENERAL DESCRIPTION
CONNECT orders the SSF to route a call: create and connect a
part to an existing call. Examples of service applications which
can be built with CONNECT are :

• Universal access number - allows a service subscriber to

have one single number to several different locations spread
over an area
• Universal personal telecommunication - enables a user to
initiate any type of service and receive any type of call on the
basis of a unique and personal network-independent number.
• Virtual Private Network - allows a subscriber to define and
use a private numbering plan for communication across one
or more networks between nominated user access interfaces.

DATA
Logic Parameters
Mode Allowed Number of Outlets
Branch YES 2 or 5 depending on mode
specified in IR1
Register YES Fixed 1
Outlets
Mode 0 (IR1 = 0)
0 Answer
1 No answer
2 Busy
3 Not used
4 Error
Mode 1 (IR1 = 1)
0 Continue
1 Error
Input Registers
IR1 Mode
0 - connect with implicit monitoring
1 - connect without implicit monitoring
IR2 KoV for error code (not Service Data)
IR3 Priority on event handling
0 .. 15 (default=7, 0=highest)

Service Data
Data Allowed
Local SA YES
Local SC YES
Global YES

– 184 – EN/LZT 123 3974 R3B

 E Logic Modules

DATA MODULE LEVEL

• Arg. Sel - Argument selection 0 .. 0 (MIS1)
• Appl. Tim - Application timer (no reply time-out): 1 .. 2047
(default=0) (MIS8)

ROW LEVEL (CONNECT ARGUMENTS)

• destinationRoutingAddress>
• number - contains the called party number towards which
the call is to routed
• alertingPattern - indicates a specific pattern that is used to
alert a subscriber. It only applies if the SSF is the
terminating exchange for the subscriber. (0 .. 79)
- 0 : dial tone on
- 1 : ring back tone on
- 2 : intercept tone on
- 3 : network congestion tone on
- 4 : busy tone on
- 5 : confirm tone on
- 6 : answer tone on
- 7 : call waiting tone on
- 8 : off hook warning tone on
- 3F : tones off
- 40 : alerting on - pattern 0
- 41 : alerting on - pattern 1
- 42 : alerting on - pattern 2
- 43 : alerting on - pattern 3
- 44 : alerting on - pattern 4
- 45 : alerting on - pattern 5
- 46 : alerting on - pattern 6
- 47 : alerting on - pattern 7
- 4F : alerting off

EN/LZT 123 3974 R3B – 185 –

GSM Mobile IN Overview

• cutAndPaste - is used by the SCF to instruct the SSF to

delete a specified number of leading digits that it has
received from the calling party and to paste the remaining
dialed digits on to the end of the digits supplied by the SCF
in the destinationRoutingAddress. (0 .. 22)
• originalCalledPartyID - carries the dialed digits if the call
has met callforwarding on route to the SSP or is forwarded
by the SCP
• routeList>routeIndex - specifies one route (0 .. 255)
• extensions>extensionField1 ..7>
• type - indicates type of extension (0 .. 63)
• extensions>extensionField1 .. 7>
• criticality - indicates to the receiver how to treat this
extension when not understood (0 .. 1)
• extensions>extensionField1 .. 7>
• kindOfVariableValue - contains the value of the extension
parameter (0 .. 65535)
• extensions>extensionField1 .. 7>value>
• kindOfLongIntegerValue - contains the value of the
extension parameter (0 .. 4294967295)
• extensions>extensionField1 .. 7>value>
• kindOfNumberValue - contains the value of an extension
parameter
• extensions>extensionField1 .. 7>value>
• kindOfStringValue - contains the value of the extension
parameter (1 .. 127)
• serviceInteractionIndicators - contains indicators used for the
control of the network based services at the originating
exchange and the destination exchange and for providing
call control information to the SSP
• serviceInterationIndicators>
• forwardSeviceInteractionIndicators - contains
information to be sent in the forward direction indicating
actions to be performed in the destination exchange

– 186 – EN/LZT 123 3974 R3B

 E Logic Modules

• ConferenceTreatmentIndicators:
xxxx xx00: no indication
xxxx xx01: accept conference request
xxxx xx10: reject conference request
• CallDiversionTreatmentIndicators:
xxxx 00xx: no indication
xxxx 01xx: call diversion allowed
xxxx 10xx: call diversion not allowed
• CallOfferingTreatmentIndicators:
xx00 xxxx: no indication
xx01 xxxx: call offering not allowed
xx10 xxxx: call offering allowed
• CallTransferTreatmentIndicators:
00xx xxxx: no indication
01xx xxxx: call transfer allowed
10xx xxxx: call transfer not allowed
• serviceInterationIndicators>backwardSeviceInteractionInd
icators - contains information to be sent in the backward
direction indicating actions to be performed in the
originating exchange for calls invoking IN functionality
• ConferenceTreatmentIndicators:
xxxx xx00: no indication
xxxx xx01: accept conference request
xxxx xx10: reject conference request
• CallTransferTreatmentIndicators:
xxxx 00xx: no indication
xxxx 01xx: call transfer allowed
xxxx 10xx: call transfer not allowed
• serviceInteractionIndicators>tSuspendTimer - contains
basic call related control information in order to control the
timer for network initiated Suspend in the SSP node. The
timeout may be reduced as compared to the normal network
timer T6 (0 .. 120)

EN/LZT 123 3974 R3B – 187 –

GSM Mobile IN Overview

• serviceInteractionIndicators>connectedNumberTreatmentI
ndicator - contains supplementary service related control
information in order to control interaction between IN based
services and COLP service and provide COLR IN service
capabilities (0 .. 2)
• callingPartyNumber - is used to provide an alternative to
the calling party number supplied by the network. It may be
used for applications such as UPT, where only the SCF can
verify the identity of the calling party
• callingPartysCategory - indicates the type of the calling
party (0 .. 255)
• redirectingPartyID - indicates the directory number the call
was directed from
• redirectionInformation - indicates forwarding related
information, such as redirecting counter

– 188 – EN/LZT 123 3974 R3B

 E Logic Modules

CUSTOMER CONTROL PARAMETERS

Customer Control is not supported

INTERWORK DESCRIPTION
Operations
If IR1 = 0;
requestReportBCSMEvent connect
If IR1 = 1;
connect

Monitoring
Event Event Priority Leg ID Monitor
Handling Mode
BCSM Event Keep IR3 MIS5 Interrupted
-RouteSelectFailure
-Answer
-NoAnswer
-CalledPartyBusy
-CalledPartyNotReachable
-Disconnect

EN/LZT 123 3974 R3B – 189 –

GSM Mobile IN Overview

t io
e n na
lly
t
In

Bl n
a
k

– 190 – EN/LZT 123 3974 R3B