ss7_inap

S7INAP.1 1999 DataKinetics Ltd.

DataKineticsIntelligent networking


Intelligent Networking

• Overview• Conceptual models• Example services• Configuration• Programming Interface• Programming examples• Example program• Debugging


IN - Introduction

• The Intelligent NetworkArchitecture to quickly create and deploy customer SERVICESSupports many servicesIs a standard - multi-vendorDistributed platform

• Example services supported by INFreephonePremium RateVoice mailCall DiversionCall baringLocal Number PortabilityUPT


The pre-IN years...

• Local switch (service user access point) is monolithic and proprietary

• Local switch supports switching, call processing and database processing

• The same functionality may be duplicated between multiple nodes

• Different implementations create inter-working problems make enhancements complex

• The network operator is unable to quickly respond to customer requests


Pre-IN free-phone service

SSP

SSP

Caller dials free-phone 800 number1-800-1234567

Special ‘800’ exchange

PSTNSSP

Network routes call (signalling and voice) to special free phone exchange/ server

800 translation database

800 number is translated and forward routed to destination

1-755-997612

Local exchange

Local exchange


Classic IN physical Architecture

SSP

IP

SCP

Service Switching Point - physical circuit switching

Intelligent PeripheralPlay-back announcements

Service Control PointControl and database functions

PSTN

SSP

SCEP/SMP

Service Creation Environment Point/Service Management PointService administration

SS7

SS7

SS7

SS7

X.25


Function of the IN SSP

• Point of subscription for the service USER (this is not necessarily the SUBSCRIBER)

• IN featuresDetection of IN callsGeneration and transmission of queries a SCPGenerate and transmit state information to the SCP (B-party busy, B-party no

answer)Record and transmit statistics to the SCPProcess SCP requests and repliesService filtering


Function of the IN SCP

• Parameter (service) validation and authentication• Process requests from SSP, send responses• Call routing, parameter, time, service, subscriber dependant• Control IP to play back standard announcements


Function of the IP

• The functionality integrated into a Service Switching Point often provides

restricted capabilities only, the main application being targeted towards general

announcements.

• IPs are dedicated to user interaction. They provide high storage capacity

together with numerous functions: Standard announcements

Information collection via DTMF

Speaker independent voice recognition

Customized announcements

Fast modification/customization of announcements

Speaker dependent voice recognition

Complex dialogues controlled via internal scripts

Provision of conferencing resources (defined in CS-2)


Function of the SCEP/SMP

• Service Administration• Development and introduction of new services• Modification of exsisting services• Provides a Service Creation Environment (generally a graphical

interface)


Generalised IN call flow

• User communicates with the SSP (dials the called party number).

• The SSP analyses the number and determines that this is an IN call.

• The SSP contacts the SCP to determine how the call should continue.

• The SCP can optionally obtain further caller information by instructing the IP to play back announcements (I.e. to collect PIN).

• The SCP instructs the SSP on how the call should continue, modifying call data as appropriate to any subscribed services.


Simplified IN Call

SSP

IP

SCP

SS7 Network

SSP

1. Off hook and dial number

2 & 5. How should the call be processed?

3 & 6. Instructions4 Announcement

7. Call progressed through to destination


Freephone service Example

SSP

SCP

SSP

1

2,6

3

4 5

SSP

SSP

Multipledestinations


Freephone Service

1. Calling party dials the freephone number (e.g. 0800 123456).

2. A trigger set in the SSP causes an INAP query to be sent to the SCP, containing the called and calling party information. On reception of the Query, the SCP translates the freephone number to the ‘best fit’ destination.

3. The SCP sends the destination number back to the SSP and requests return of charging information once the call has completed.

4. The SSP resumes call processing with the new destination address, routing the call over the PSTN.

5. The call is established.

6. After the call is terminated, the SSP sends charging information to the SCP.


Televoting service Example

SSP

SCP

SSP

1

2,5

3,6

4

IP


Televoting example

1. Calling party dials the televoting number.

2. Switch recognises televoting call and sends a query to the SCP. The SCP analyses the dialled number and increments the appropriate vote count. The SCP determines that a prompt indicating successful registration of the vote is required.

3. The SCP sends a routing number of an appropriate IP able to play the televoting announcement. The IP plays the announcement.

4. The IP informs the SSP that the announcement has been played and is complete.

5. The SSP sends the completion status to the SCP

6. The SCP instructs the SSP to clear the call.


Televoting service method (2)

SSP

SCP

SSP

2

1,3

4

3

IP


Televoting service method (2)

1 SCP initiates service filtering (televoting) at the SSP

2 Subscriber dials, SSP informs SCP that the specified service has been activated

3 SCP instructs the SSP to play an announcement (using the IP) and release the call once the announcement has completed.

4 After a specified time, or at specific defined time intervals set when the service was activated, the SSP reports the televote count to the SCP.

Steps 2 and 3 may be repeated many times!


IN CS-1 Benchmark services

Abbreviated Dialing (ABD)Attendant (ATT)Authentication (AUTC)Autorisation Code (AUTZ)Automatic Call Back (ACB)Call Distribution (CD)Call Forwarding (CF)Call Forwarding on Busy/Don’t AnswerCall Gapping (GAP)Call Hold with Announcement (CHA)Call Limiter (LIM)Call Logging (LOG)Call Queuing (QUE)Call Transfer (TRA)Call Waiting (CW)Closed User Group (CUG)Consultation Calling (COC)Customer Profile Management (CPM)Customized Recorded Announcement (CRA)

Customized Ringing (CRG)Destination User Prompter (DUP)Follow-Me Diversion (FMD)Mass Calling (MAS)Meet-Me Conference (MMC)Multiway Calling (MWC)Off-Net Access (OFA)Off-Net Calling (ONC)One Number (ONE)Origin Dependent Routing (ODR)Originating Call Screening (OCS)Originating User Prompter (OUP)Personal Numbering (PN)Premium Charging (PRMC)Private Numbering Plan (PNP)Reverse Charging (REVC)Split Charging (SPL)Terminating Call Screening (TCS)Time Dependent Routing (TDR)

See Q.1219 Annex A for example service flows


Types of IN signalling

• Between SSPs: To directly control circuit switched connection or exchange information relating to a call that is in progress on a switched circuit (56 or 64kb/s) - Circuit related

• Between SSP and SCP: To exchange control information, no physical bearer circuit exists between the SSP and SCP. This is non-circuit related or transaction based signalling.

• Between SSP and IP, and SCP and IP: May be ISUP, INAP or proprietary.


Protocol Model

SCCP

MTP

TCAP

INAP

MTP

SCCP

TCAP

INAP

ISUP

MTP

ISUP

IPSSP SCP

SCCP

TCAP

INAP

Note: There may also be an ISDN link between the SSP and IP


ISUP

• To directly control switched circuit channels.• Defines message formats, message sequences.


SCCP

• Signalling Connection Control Part• A ‘thin’ protocol layer allowing data to be exchanged between

intelligent entities (sub-systems) through the SS7 network.• Provides routing and addressing control.• Each entity that communicates using SCCP is identified by its

point code and sub-system number (or global title).• Communication may be session based (connection oriented

SCCP) or connectionless


TCAP (or TC)

• Transaction Capabilities Application Part• Provides a structure for the invocation of operations at remote

intelligent entities.• An exchange of messages is called a transaction at the SCCP

interface and a dialogue at the INAP interface.• Unstructured dialogue - non session based, uses TC-UNI

messages• Structured dialogue - session based, requires BEGIN,

CONTINUE, END.• INAP uses structured dialog only.• Operations and their results are conveyed in ‘components’

within each dialogue.


TCAP control state machines

Dialogue handlingEstablishment, maintenance and close down of dialoguesEach dialogue is identified by a dialogue_id.

Component handlingOne state machine per invoked operation on the invoking sideEach operation is identified by an invoke_id.

Operation timerControls the duration of a invocation state machine.


Communication TCAP & TCAP-User

MTP

SCCP

TCAP message

Transaction Sublayer

TC User

ComponentSublayer

1.

2.

3.

1. Single Components (primitives)2. Collect Components3. All collected components of one dialog in one message


TCAP dialogue primitives

TC-Begin.Req; TC-Begin.Ind

TC-Continue.Req; TC-Continue.Ind

TC-End.Req(Basic); TC-End.Ind(Basic)

TC-End.Req(Prearranged): Local termination of the transaction

TC-User-Abort.Req; TC-User-Abort.Ind: ‘User Information’ informs about abort reasons (normal abort, error indication)

TC-Provider-Abort.In: Sent by the transaction sub-layer of TCAP

TC-Notice.Ind: Requested SCCP service was not available


TCAP component primitives

TC-Invoke.Req / Ind

TC-Result.Last.Req / Ind

TC-User-Error.Req / Ind

TC-User-Reject.Req / Ind

TC-Local-Reject.Ind / TC-Remote-Reject.Ind: Errors detected by TCAP: Those errors are indicated to the user. The user decides whether the error shall be sent to the peer entity or not (controlled by sending the respective dialog handling primitive)

TC-Cancel.Req: TCAP user requests locally the abort of a previously invoked operation and the cancellation of the related state

TC-Cancel.Ind: Indication of an operation timer expiration to the local TCAP user. (Interpretation by the TCAP user depends on the operation class!)


IN Conceptual Model

Four planes (Q.120x) are used to model and abstract the IN functionality:

Q.1202 - Service Plane (SP) Uppermost, describes services from the users perspective. Hides details of implementation from the user

Q.1203 - Global Functional Plane (GFP) contains Service Independent Building Blocks (SIBs), reusable components to build services

Q.1204 - Distributed Functional Plane (DFP) models the functionality in terms of units of network functionality, known as Functional Entities (FEs). The basis for IN execution in the DPF is the IN Basic Call State Model.

Q.1205 - Physical Plane (PP) Real view of the physical network.


SP/GFP

Basic call process

Translate

Charging

Screen

One number

Reverse charging

Service Service feature

Service Plane

Global FunctionalPlane

SIB

Q.1213

Q.1212(Not defined!)


SIBs

A SIB has the following characteristics:• Exists in the Global Functional Plane.• It is a re-useable building block, defining a complete activity.• It has a defined interface, with a specified number of inputs and

outputs.• It is independent of the physical implementation.• SIBs are independent of the IN Services.• SIBs are combined to implement a Service.• CS-1 SIB examples: Authenticate, Charge, Log Call Information,

Screen.• Some Service Creation Environments operate on SIBs


BCP and POI

• Special SIB called the Basic Call Process (BCP).• This interacts with the other SIBs.• The GFP defines the Point of Initiation (POI) and the Point of

Return (POR) between the BCP and any other SIB or sequence of SIBs.

CS-1 Points of Initiation

Call originatedAddress collectedAddress analysedCall arrivalBusyNo AnswerCall acceptanceActive stateEnd of call

CS-1 Points of Return

Continue with existing dataProceed with new dataHandle as transitClear callProvide call party handlingInitiate call


Freephone modeling with CS-1 SIBs

POIAddressAnalyzed

TranslateCharge_1(Calling freeof charge)

Charge_2(Record forsubscriber)

Translate Translate

UI

PORProceedwith newdata

POIBusy


POINo Answer


POINo Answer

PORClearCall

BCP

SIB Chain 1 SIBChain 2

SIBChain 3

SIBChain 4

Service FeaturesCalling line is set free of chargeThe service subscriber is to be chargedThe first call attempt shall be routed to an alternative destination if the first destination is busy or does not answer, i.e. rerouting on “busy” or “no answer”If a re-routed call, i.e. due to “busy” or “no answer” during the first attempt, meets a “no answer” situation then an announcement shall be played to the caller. This means that the “busy” situation shall not be monitored for during the second attempt.


BCM

GFP/DFP (For CS-1)

SIB n

SIB n

DistributedFunctional Plane

Global FunctionalPlane

POI

Q.1214

Q.1213Basic call process POR

SCF

SDF

SRF

SSF

CCF

Functional Entity


Functional Entities

• Basic Call handlingCall Control Agent Functions (CCAF) - models the users telephoneConnection Control Function (CCF) - basic switchingSpecialised Resource Function (SRF) - additional media management

• Service Execution FunctionsService Switching Functions (SSF) - interface to SCFService Control Function (SCF) - service logicService Data Function (SDF) - service dataSRF

• Service Management FunctionsSystem Management Functions (SMF) - service provisioning, maintenanceService Management Agent Functions (SMAF) - MMI for SMFservice Creation Environment Function (SCEF) - specification and testing


FE and SIB association (CS-1)

SDF

Basic Call ProcessVerifyUser InteractionTranslateStatus NotificationService Data MgtScreenQueueLog Call InformationLimitDistributionCompareChargeAlgorithmAuthenticate

SRFSCFCCF/SCF


DFP and the Physical Plane

DistributedFunctional Plane

Q.1214SCF

SDF

SRF

SSF

Functional Entity

SSP IP

SCP

SDF

Physical PlaneQ.1215

INAP Communication


CS1 physical FE distribution

SMAF

SMF

SCEFSDF

SMP

SCP

SDP

SS7 Network

IP

SN

SRF

SCF

SDF

SCF

SSFSSF

CCF

SDFSRF

CCF

SRF

CCAF SDF

SSP

Voice Transport

Signaling

Optional FE

SCF


FE definition of IP and SN

Intelligent Peripheral• An IP (Intelligent Peripheral) contains the Specialized Resource Function only, i.e. an IP

provides capabilities necessary for services with user dialogues

• An IP is controlled by the service logic

Service Node• A Service Node (SN) comprises all functions needed to provide services (Service Control

Function, Service Data Function, Service Switching Function, Call Control Function and Specialized Resource Function

• A Service Node is able to provide complete services independent on other networks components

• Service Nodes may be also called Intelligent Network in a Box

• The mentioned functions represent the minimum function set of a Service Node. Obviously there are additional functions useful concerning management, service creation and other areas.


Service Node architecture

Bearer Control(DSS1 or ISUP)

INAP to SSP

INAP to SCPMAP to HLR Management

SSF/CCF

SSF/CCF SRF

SDF

SCEF

SCF


SN features

• Internal proprietary interfaces between its components

• The service logic can directly access the voice channel

• Besides voice now numerous data communication protocols and applications may be used

• Flexible, efficient and cheap (good cost performance ratio) implementation of services for small service providers

• Easy introduction into existing networks based on connection via standard signaling protocols (EDSS1, ISUP)

• Reduction of #7 signaling load

• Lower traffic concentration


Example SN capabilities

• Voice messagingsubscribers record own messages which are distributed through the network(according to a distribution list).

• Fax messagingRecord fax messages during busy hour to retransmit during off-peak charingperiod.

• Short Message ServiceGateway to email networks.

• Electronic mail


Service Modelling in the CS-1 DFP

• SIBs are modelled in the DFP by interactions between Functional entities.

• Each SIB is modelled by the SCF controlling other FE’s.• The BCP is modelled in the DFP by the Basic Call State Model

in the CCF.

Basic call process SIB n

SIB n

SCF

SDFSSF

CCF


The Basic Call State Model

• BCSM• Standard definition of call processing states and events• Switch and manufacturer independent• Trigger Detection Points are pre-defined in both the Originating

Basic Call State Model OBCSM and the Termination Basic Call State Model (TBCSM)

• Non-interruptable sequences of processing are called Points-In-Call (PIC)


IN Triggers

• A normal call becomes an ‘IN call’ if a special condition is recognised during the call handling

• Recognition of such a condition ‘triggers’ a query to an external control component (SCP)

• Recognition takes place at pre-defined Detection Points in the call handling, which may be armed (active) or not armed (inactive)

• DPs may be armed statically for a long period to implement a particular IN Service.

• DPs may be armed dynamically to report particular events and errors.


Types of Triggers

• Two types of processing on satisfying a DP:

Suspend call processing and request instructionsRequest : TDP_R

Continue Call processing and issue Notification to SCFNotification : TDP_N


CS-1 originating BCSM

1. O_Null & Authorise Origination_Attempt

2. Collect_info

3. Analyse_info

4. Routing_&_alerting

5. O_Active

1

6. O_Exception

34

5

67

8

9

10

2

O_Abandon

Orig_attempt Authorised

Collected_info

Analysed _info

O_Answer

Route_select_failure

O_Called_party_busy

O_No_Answer

O_Mid_callO_Disconnect

Point in Call (PIC)

Detection Point (DP)


OBCSM Triggers• DP1 : Origination_attempt_authorized

Call setup is recognized and authorized.

• DP2 : Collected_InformationPre-defined number of dialed digits is collected

• DP3 : Analyzed_InformationDialed digits are analyzed

• DP4 : Route_Select_FailureRouting failed : no free channel, dialed number not available, network overload

• DP5 : O_Called_Party_BusyDestination busy

• DP6 : O_NO_AnswerCaller does not answer in predefined time, Service Logic specifies the “no answer time” for SSP

• DP7 : O_AnswerCalled subscriber answers: SSP receives e.g. an ANM

• DP8 : O_Mid_CallSignal (hook flash, F-key) recognized during call

• DP9 : O_DisconnectA or B side hangs up

• DP10 : O_AbandonCall set-up discontinued by the A-side


CS-1 Terminating BCSM

7. T_Null & Authorise termination attempt

8. Select Facility &Present Call

9. T_Alerting

10. T_Active

12

11. T_Exception18

T_Abandon

Term_attempt Authorised

T_Answer

T_Called_Party_busy

T_No_Answer

T_Mid_call

T_Disconnect

Point in Call (PIC)

Detection Point (DP)

13

14

15

1617


TBCSM Triggers

• DP12 : Termination_attempt_authorizedan incoming call attempt is recognized and authorized

• DP13 : T_Called_Party_BusyDestination busy

• DP14 : T_No_AnswerCalled party does not answer during a given time

• DP15 : T_AnswerCalled line answers, I.e. the SSP receives the ANM

• DP16 : T_Mid_CallSignal (e.g. hook flash, function key) is recognized during the active connection

• DP17 : T_DisconnectEither A-side or B-side hangs up

• DP18 : T_AbandonCall set-up aborted by the A-side, can happen at any time and is considered normal


Information Flows

Two methods exsist for requesting SCF processing at a DP:

DP Generic

Only one information flow is used, ‘Initial DP’. The set of information elements (data) carried depends on the DP encountered.

DP Specific

Dedicated information exchange for each DP. Easy to process, less paring effort. High number of different information flows to analyse. (Not specified for use in ETSI INAP).


Freephone Example

SSF SCF SDF

2

3

7

9

Analyse_info

Route_&_Alert

O_Active

TDP-RTC-BEGIN

Initial DP: fph, 0-800-xxxxxx

TC-CONTINUE

Connect: call, id = xxxxxReq BCSM event:O_Answer, O_Disconn

EDP-N

EDP-N

Event: call, id = xxxxxBCSM O_Answer, timeTC-CONTINUE

Event: call, id = xxxxxBCSM O_Disconnect, timeTC-CONTINUE

TC-END


Operation: Initial DP

• Semantics:Report a trigger detectionEstablishes a control relationship between SSF and SCF

• Arguments:serviceKeycalledPartyNumbercallingPartyNumberbearerCapabilityredirectingPartyId…..


Operation: Connect

• SemanticsTransfer the determined destination number to the SSFContinue the call set-up

• Arguments:destinationRoutingAddresscalledPartyNumbercallingPartyNumberredirectingPartyIdcutAndPaste...


Parameter: Cut and Paste

• Describes how the digit string should be processed.

– The Cut&Paste value instructs the SSP to remove the first “Cut&Paste” digits from the dialed digits.

– The digits received from the SCP then serve as the leading digits of the destination address which has to be formed.

– The digits already existing at the SSP will be added at the end

• Example:

– SSP receives “123456789”

– SCP instructs CutAndPaste = 4 and destination address = 503322

– SSP generates destination address 503322 56789


Operation: RequestReportBCSMEvent

• Semantics:– arming of event detection point at the SSP for call monitoring

• Arguments:– list of elements of type BCSMEvent– Example:

DP5 ( = busy)

DP6 ( = no answer)

…..– Specify DP specific conditions/parameters. (e.g. timer for DP6)


Operation: EventReportBCSM

• Semantics– Reporting of detected event detection points

• Arguments:– eventTypeBCSM– eventSpecificInformationBCSM– legID


INAP

• Allows communication between distributed IN Functional Entities.

• Information flows defined in the DFP are implemented in the physical plane through the SS7 INAP protocol.

• INAP is defined on a FE basis rather than a physical view.• INAP supports interactions between:

CCF/SSF and SCFSCF to SRF

• INAP operations are grouped into Application Service Elements (ASE’s). An ASE may be considered as being a collection of operations.


Capability Sets

• Capability Set = set of supported services and service features• CS-1 Single ended/single point of control services, defined by

Q.121x. Single party (originating or terminating) controls the INAP call.

• CS-2 Enhancement to all CS-1 structure. Defined by Q.122x. Capability for multi-point control.


Protocol layers

MTP Layer 1

MTP Layer 3

MTP Layer 2

TUP

SCCP

ISUPTCAP

INAPMAP

Application


Application Contexts

• Application Service Elements are grouped into Application Contexts (AC’s).

• An AC is typically a sub-set of the total INAP and specifies the parts of the protocol needed in the communication between two type of IN FE’s.

• An AC also defines which operation should initiate the dialogue.• Example Application Contexts:• “IN-CS-1-SSF-to-SCF-Generic-AC”

SCF-activation-ASE, Connect-ASE

• “IN-CS-1-SCF-to-SSF-status-reporting-ACStatus-reporting ASE, Cancel ASE


DataKinetics INAP, Key Features

• Provides the INAP communication capability for the SCF, SSF or SRF.

• FE independent.• Implements the Single Association Control Function (SACF)

defined in ITU-T Q.1218 and ETS 300 374-1• Procedural API interface.• Tailored Suites of ASE’s (INAP operations)• Supported ASE’s may be tailored to support any network or

operator specific IN functions.• Supports application context negotiation• Supports operation with ITU-T/ETSI and ANSI TCAP.


Documentation

• Platform User Guide (Septel cP, PCCS6, SIU)• Software Environment Programmer’s Manual• SCCP Programmer’s Manual• TCAP Programmer’s Manual• INAP Programmer’s Manual


Programming Interface

• INAP is based on invoking an operation at a serving FE by the requesting FE. These operations are invoked within a session or “dialogue” between the two FE’s.

• Functional API library supplied with a procedural interface manages parameter Encoding/decoding as TCAP components, using ASN.1 rules.

• To access the ASN.1 encoded data, the user may access the module directly. (Using MSGs).


Functional Entity Addressing

• When a dialogue is opened, the user application must supply the SCCP address of the local and remote FE’s in the SS7 network.

• These can be included at the start of each dialogue or configured once (at initialisation) and referenced by a local logical code.

• Enables INAP to support more than one local FE. (Hence a SCF and SRF may be implemented on the same stack).

• Each local FE may be handled by a different user task (module_id).


Application Context Handling

• An Application Context (AC) is required for each dialogue between two IN FE’s.

• AC negotiation is required at dialogue initiation to determine if the receiving FE is able to support the requested AC.

• The INAP module can be configured to handle the AC negotiation automatically if the supported AC’s are configured.

• If required, raw AC data may be exchanged between the INAP module and the user allowing the user to perform the AC negotiation.


Module Capability

• Maximum number of FE’s = 32• Maximum number of AC’s = 32• Maximum number of simultaneous dialogues = 2048• Maximum number of simultaneous invocations = 2048• Supports all ETSI CS-1 Core INAP ACs’:

Core-INAP-CS1-SSP-to-SCP-ACCore-INAP-CS1-ASSIST-HANDOFF-TO-SSP-TO-SCPCore-INAP-CS1-IP-TO-SCPCore-INAP-CS1-SSP-to-SCP-ACCore-INAP-CS1-SCP-TO-SSP-TRAFFIC-MANAGEMENTCore-INAP-CS1-SCP-TO-SSP-SERVICE-MANAGEMENTCore-INAP-CS1-SSP-TO-SCP-SERVICE-MANAGEMENT


INAP Configuration

• Single message, INAP_MSG_CONFIGuser_id default application module id if no FE’s configuredTCAP_id module id used by TCAP (normally 0x14)mngt_id, maint_id Module id for management and maintenance event indicationstrace_id Module id for traced messages (debug only)base_usr_ogdlgid 1st dialogue id that will be used by the user for outgoing dialogues base_usr_icdlgid 1st dialogue id that will be used by INAP for incoming dialogues base_tc_ogdlgid 1st outgoing dialogue id to send to TCAPbase_tc_icdlgid 1st incoming dialogue id expected from TCAPnog_dialogues maximum number of outgoing dialogues to supportnig_dialogues maximum number of incoming dialogues to supportnum_invokes maximum number of active invokes (operations) to supportoptions

ANSI or ITU-T component formats, Transparent AC handling, 14 or 24 bit point codes

• Septel-SIU

Set SCCP_LSS <protocol> to INAP


FE Configuration

• Single message per FR, INAP_MSG_CNF_FEfe_reference (0..31). Logical identifier unique to each configured FEFE options Local or RemoteLocal FE module ID Module ID identifying the user application process

handling the local FEFE SCCP address length number of octets of data in the lFE SCCP addressFE SCCP Address FE address formatted according to Q.713, ANSI T1.113

• Septel-SIU

INAP_FE <fe_ref> <options> <fe_addr>


AC Configuration

• Single Message per AC, INAP_MSG_CNF_ACapplication context reference logical identifier referencing the supplied AC.ac_len number of octets of data in application context.Application Context AC data

• Septel-SIU

INAP_AC <ac_ref> <ac>


Complete configuration sequence

• Configure Physical parameters (PCCS6)• Configure MTP3 parameters (links, link sets)• Configure SCCP• Configure SCCP Remote Signalling Points• Configure SCCP Remote sub-systems• Configure SCCP Local sub-systems• Configure INAP• Configure INAP FE’s (optional)• Configure INAP AC’s (optional)


Example configuration

Point code = 1

sub-system number = 0x0cmodule_id = 0x1dFE identifier = 5

sub-system number = 0x0dmodule_id = 0x2dFE identifier = 5

Point code = 2

sub-system number = 0x0aFE identifier = 1

sub-system number = 0x0bFE identifier = 2

LocalRemote


Example INAP configuration (1)

* Issue configuration message to the SCCP module:* --maint_id* --mod_id ----SMB flags* ----options --------pc --SMB id* --sio --mgmt_id --SCCP inst* --ver --mtp_id ----max_sifM-t7740-i0000-fef-d33-r8000-p0083000233229e9e000000010110000000000000000000** Configure Local sub-systems* --mult_ind* --mod_id * --type --ssn* --ver --------spcM-t7741-i0000-fef-d33-r8000-000031401000000000c000000000000000000000000000000000000M-t7741-i0000-fef-d33-r8000-p00031401000000000d000000000000000000000000000000000000* Configure Remote SP'sM-t7741-i0000-fef-d33-r8000-p000100000000000200000000000000000000000000000000000000* Configure Remote sub-systemsM-t7741-i0000-fef-d33-r8000-p00020000000000020a0000000000000000000000000000000000000M-t7741-i0000-fef-d33-r8000-p00020000000000020b0000000000000000000000000000000000000*



* Issue configuration message to the TCAP module:* --mgt_id max_data----* --nsap_id ----nicd --nseq* --usr_id ----nogd ----bog --ndref* --mod_id ----flags ----ncpt --ninst * --ver --maint_id ----ninv ----bic --instM-t7780-i0000-fef-d14-r8000-p001435339e9e00000400040008000010000080000410080200ff0** Issue configuration message to the INAP module:** ----base_tc_icdlg_id* --reserved----base_tc_ogdlg_id* --trace_id options-------- * --Tcap_id ----base_usr_icdlg_id * --user_id ----base_usr_ogdlg_id ----num_invokes* --maint_id ----nic_dlg* --mgmt_id ----nog_dlgM-t77f4-i0000-fef-d35-r8000-p77149e9e9e0000008000000080000400040008000000000000000*


Example INAP configuration (3)* Config Remote Functional Entites* --------addr* --addr len* --local FE module id* ----FE 1 ----optionsM-t77f7-i0001-fef-d35-r8000-p000000044302000aM-t77f7-i0002-fef-d35-r8000-p000000044302000b** Config Local Functional EntitesM-t77f7-i0005-fef-d35-r8000-p00011d044301000cM-t77f7-i0006-fef-d35-r8000-p00012d044301000d*** Config Application Contexts* --AClen* reserved---------------- ----------------------ACM-t77f6-i0000-fef-d35-r8000-p00000000000000000ba109060704000101010000M-t77f6-i0001-fef-d35-r8000-p00000000000000000ba109060704000101010100M-t77f6-i0002-fef-d35-r8000-p00000000000000000ba109060704000101010200M-t77f6-i0003-fef-d35-r8000-p00000000000000000ba109060704000101010300M-t77f6-i0004-fef-d35-r8000-p00000000000000000ba109060704000101010400M-t77f6-i0005-fef-d35-r8000-p00000000000000000ba109060704000101010500M-t77f6-i0006-fef-d35-r8000-p00000000000000000ba109060704000101010600***



** Send UIS (to SCCP), ssn = 0x0c and 0x0d :* --SSAM-tc744-i000c-fef-d33-r8000-p010100000000*M-tc744-i000d-fef-d33-r8000-p010100000000**

Sub-system status is maintained by SCCP, hence all sub-system management requests are made to SCCP and are received from SCCP (module_id 0x33)


Message based API

Receive dialogue event

Issue dialogue command

Receive results or errors from operationsinvoked at a remote FE

Invoke an operation at a remote FE or respondto a invocation received from a remote FE

Usage

0x87f3

0xc7f2

0x87f1

0xc7f0

Value

INAP_DIALOGUE-IND

INAP_DIALOGUE_REQ

INAP-SERVICE-IND

INAP-SERVICE-REQ

Message type


INAP_MSG_DLG_REQ

MESSAGE HEADER

FIELD NAME MEANING

type INAP_MSG_DLG_REQ (0xc7f2)

id dialogue_ID

src Sending module_id

dst INAP_MODULE_ID

rsp_req 0

hclass 0

status 0

err_info 0

len Number of bytes of user data

PARAMETER AREA

OFFSET SIZE NAME

0 1 Dialogue primitive type octet.

1 len - 2 Parameters in Name-Length-Data format.

len - 1 1 Set to zero indicating end of message.

INAP Programmers Manual details other message specifications


Dialogue primitive types

Primitive Value Usage

INAP-OPEN-REQ 0x1 Used to open a dialogue. The INAP moduleassigns resources for the dialogue andawaits any INAP operations the user wishesto open the dialogue with.

INAP-CLOSE-REQ 0x2 Basic End: Used to indicate that anyoperations supplied should now betransmitted to the remote FE. The dialogueis then terminated.

Pre Arranged End: Used to indicate that thedialogue may be terminated locally whenany active invocations have completed. Anypending components sent to the INAPmodule will discarded. The INAP modulewill issue a Close Indication when thedialogue is terminated.

INAP-DELIMIT-REQ 0x3 Used to indicate that any componentssupplied should now be transmitted to theremote FE. The dialogue remains open.

INAP-U-ABORT-REQ 0x4 Used to indicate that the user wishes toabort this dialogue. Any outstandingcomponents are discarded.

INAP-OPEN-RSP 0x81 Used to accept or reject a dialogue requestfrom a remote FE.

INAP User to INAP


Dialogue primitive types

INAP to INAP User Primitive Value Usage

INAP-OPEN-IND 0x1 Used to indicate a dialogue request from aremote FE. The user may subsequentlyreceive service indication messages bearingcomponents. The user should wait toreceive the INAP-DELIMITER-IND beforeaccepting the dialogue with the INAP-OPEN-RSP primitive.

INAP-CLOSE-IND 0x2 Used to indicate that all the componentsreceived have been issued to the user. Thedialogue is terminated.

INAP-DELIMITER-IND 0x3 Used to indicate that all the componentsreceived have been sent to the user. Thedialogue remains open.

INAP-OPEN-CNF 0x81 Used to indicate that the remote FE hasaccepted the user’s dialogue request.

INAP-U-ABORT-IND 0x4 Used to indicate that the remote user hasaborted the dialogue, any outstandingcomponents have been discarded.

INAP-P-ABORT-IND 0x5 Used to indicate that the dialogue has beenaborted because of a network error. Anyoutstanding components have beendiscarded.

INAP-NOTICE-IND 0x6 Used to indicate that an abnormalcomponent was detected.


Dialogue parameters

Parameter

OPEN-REQ

CLOSE–REQ

DELIMITER-REQ

U-ABORT-REQ

OPEN-RSP

Destination address A

Originating address B

Destination reference A

Originating reference B

Result M

Refuse reason O

Release method M

User reason M

Application context name O O O O O

Application context index C O

The INAP Programmers Manual defines the parameters and which are required with each primitive type

M MandatoryO Optional

A Exclusive ORB Exclusive ORC Conditional


Service component primitives


INAP-INVOKE-REQ 0x1 Used by the user application to request anoperation invocation.

INAP-RESULT-REQ 0x2 Used by the user application to provide thesuccessful result of an operation invocation.

INAP-ERROR-REQ 0x3 Used by the user application to provide theunsuccessful result of an operationinvocation.

INAP-REJECT-REQ 0x4 Used by an API decode function to indicatea "provider" problem. This occurs if thedecode function is unable to decode thereceived component.

INAP User to INAP


Service component primitives

INAP to INAP User


INAP-INVOKE-IND 0x1 Used by the INAP module to convey anoperation invocation to the user application.

INAP-RESULT-IND 0x2 Used by the INAP module to convey thesuccessful result of an operation previouslyinvoked by the user.

INAP-ERROR-IND 0x3 Used by the INAP module to convey theunsuccessful result of an operationpreviously invoked by the user.


Service component parameters

Component Type

Parameter INVOKE-REQ

RESULT-REQ

ERROR-REQ

REJECT-REQ

Invoke ID M M M M

Linked ID O

Component M M M

Op code M

Parent Ind O

Class M

Timeout M

Problem code M


Pre-defined operation codes/* * SCF activation ASE */#define INOP_InitialDP (0)

/* * Basic BCP DP ASE (ITU Q.1218 only) */#define INOP_OriginationAttemptAuthorized (1) /* (ITU Q.1218 only) */#define INOP_CollectedInformation (2) /* (ITU Q.1218 only) */#define INOP_AnalysedInformation (3) /* (ITU Q.1218 only) */#define INOP_RouteSelectFailure (4) /* (ITU Q.1218 only) */#define INOP_OCalledPartyBusy (5) /* (ITU Q.1218 only) */#define INOP_ONoAnswer (6) /* (ITU Q.1218 only) */#define INOP_OAnswer (7) /* (ITU Q.1218 only) */#define INOP_ODisconnect (8) /* (ITU Q.1218 only) */#define INOP_TermAttemptAuthorized (9) /* (ITU Q.1218 only) */#define INOP_TBusy (10) /* (ITU Q.1218 only) */#define INOP_TNoAnswer (11) /* (ITU Q.1218 only) */#define INOP_TAnswer (12) /* (ITU Q.1218 only) */#define INOP_TDisconnect (13) /* (ITU Q.1218 only) */

/* * Advanced BCP DP ASE (ITU Q.1218 only) */#define INOP_OMidCall (14) /* (ITU Q.1218 only) */#define INOP_TMidCall (15) /* (ITU Q.1218 only) */

See in_inc.h


Functional API

Message buffer handling functions

IN_alloc_message Allocate a message to send to INAP

IN_free_message De-allocate message

IN_send_message Send message to INAP

Component Handling

IN_init_component

Used to initialise component encoding/decoding. Must be called before encoding or decoding a component. Allows the user to specify the protocol (encoding format).

Parameters are detailedin the INAP Programmer’sManual


Component encoding

CPT

MSG

2. Component Building

Functions

3. Service RequestEncoding Functions

1. Initialise Component


Component building functions

Build Operation in Component Buffer API Functions

IN_set_operation Write the operation code

IN_set_error Write the error code

IN_set_result Write the resultIN_set_component_param Write the requested parameter

All the above functions operate on the component buffer, which must be subsequently formatted into a message


Service request encoding

Service Request Encoding

IN_code_operation_invoke Encode the component in an Invoke component

IN_code_result Encode the component in a Result component

IN_code_error Encode the component in an Error component

IN_code_reject Encode the component in an Reject component


Component decoding

CPT

MSG

1. Initialise Component

3. Read Component Buffer Functions

2. Decode Service Indicatio

n Function

s


De-code service indication

IN_get_component_type Obtain received component type

IN_decode_operation Decode the operation parameter

IN_decode_result Decode a result

IN_decode_error Decode an error component


Read component buffer

IN_get_component_type Return the type of the received component

IN_get_component_first_errorDetermine the first error encountered during encoding

IN_get_operation Get received operation code

IN_get_component_param Retrieve parameter from received component


Dialogue handling API functions

Send dialogue request API functions

IN_set_dialogue_param Set a dialogue request parameter

IN_dialogue_open Builds a dialogue open

IN_dialogue_close Builds a dialogue close

IN_dialogue_delimit Builds a dialogue delimit

IN_dialogue_u_abort Builds a dialogue u_abort

IN_dialogue_open_rsp Builds an open response dialogue primitive

Read dialogue request API functions

IN_get_dialogue_type Determine dialogue type in received message

IN_get_dialogue_param Recover a parameter from a received dialogue


Outgoing dialogue request

INAP User INAP TCAP

INAP_DLG_REQ (OPEN)

INAP_SRV_REQ (INVOKE)

INAP_DLG_REQ (DELIMIT)

INAP_DLG_IND (OPEN-RSP)

INAP_SRV_IND (INVOKE)

INAP_DLG_IND (DELIMIT)

INAP_DLG_IND (CLOSE)

TC-INVOKE

TC-BEGIN

TC-CONTINUE

TC-END

SCCP

N-UNITDATA-REQ

N-UNITDATA-IND

MTP

UDT

UDT

TC-INVOKE


Opening a dialogue

h = IN_alloc_message();IN_set_dialogue_param(INDP_dest_address, len, dptr, h);IN_set_dialogue_param(INDP_orig_address, len, dptr, h);IN_set_dialogue_param(INDP_applic_context_index, len, dptr, h);IN_dialogue_open(dlg_id,h);IN_send_message(user_id,inap_id,h);

Obtain a message structure, enter the parameters and send to INAP. No message is issued to the SS7 network at this point.


Sending an operation

h = IN_alloc_message();IN_init_component(prot_spec, cpt);IN_set_operation(op_name, timeout, cpt);IN_set_component_param( INPN_InvokeID, len, dptr, cpt);IN_set_component_param( param1, len, dptr, cpt);IN_set_component_param( param2, len, dptr, cpt);IN_code_operation_invoke( dlg_id, cpt, h);IN_send_message(user_id, inap_id, h);

This may only be done on an opened dialogue. The user obtains a message, initialises a component structure and sent to the INAP module.


Sending a delimit

h = IN_alloc_message();IN_dialogue_delimit(dlg_id,h);IN_send_message(user_id,inap_id,h);

This is built and sent in a similar method as the Open.


Receiving an Open Response

h = GCT_receive();switch (h->type){ case INAP_MSG_SRV_IND : ... break; case INAP_MSG_DLG_IND : IN_get_dialogue_type(h, dlg_type_ptr); switch (dlg_type_ptr) { case INDT_OPEN_RSP: IN_get_dialogue_param(INDP_result,lenptr,dptr,max_len,h); IN_get_dialogue_param(INDP_refuse_rsn,lenptr,dptr,max_len,h); IN_get_dialogue_param(INDP_applic_context,lenptr,dptr,max_len,h); /* Process the parameters here */ break; } break; } relm(h);

This is achieved by reading a message from the applications message queue using GCT_receive.


Decoding an operation

h = GCT_receive();switch (h->type){ case INAP_MSG_SRV_IND : IN_get_component_type(h, &cpt_type); switch (cpt_type) { case INCPT_INVOKE :

IN_init_component(prot_spec, cpt); IN_decode_operation(cpt, h); IN_get_component_param(param1, lenptr, dptr, buffer_size, cpt); IN_get_component_param(param2, lenptr, dptr, buffer_size, cpt); /* Process Invoke parameter here */

break; } break; ...}relm(h);

This is achieved in the same way as recovering the dialogue open response, with a message type indicating a service indication.


Closing a dialogue

The Close request is sent to end the dialogue with the remote system (this may be pre-arranged or basic).

m = IN_alloc_message():IN_dialogue_close(dlg_id,m);IN_set_dialogue_param(INDP_release_method, len, dptr, m);IN_send_message(user_id,inap_id,m);


Other examples

• The INAP Programmers Manual Provides more API examples and message sequence charts.


Debugging

• Message tracing• Software events• Maintenance events

* Activate Output Event - Trace Mask* --------non_prim_mask* --------ip_evt_mask* --------op_evt_maskM-t57fb-i0000-fef-d35-r8000-p0000000f0000000f0000007f** Active Error Event MaskM-t57fc-i0000-fef-d35-r8000-pff00000000000007ff** Active Maintainence Event MaskM-t57fd-i0000-fef-d35-r8000-p000000000000000001*


INTU example program

INTU INAP

DLG-IND (OPEN)

SRV-IND (Invoke: Initial DP)

DLG-IND (Delimit)

DLG-REQ (OPEN-RESPONSE)

SRV-REQ (Invoke:Connect)

DLG-REQ (DELIMIT)

DLG-REQ (CLOSE)

DLG-IND (CLOSE)

(pre-arranged end)

TC-BEGIN

TC-CONTINUE

TC-END (pre-arranged)

TC-INVOKE

TC-INVOKE


INTU console

H:\SYSTEM7\RUN>intu -b0x8000INTU: Example INAP application (C) 1998-1999 DataKinetics Ltd=============================================================

SS7-INAP-API Version 1.1INTU module ID - 0x3dINAP module ID - 0x35Number of dialogues - 0x0800 (2048)Base dialogue ID - 0x8000Options set - 0x0300

INTU: State change for dialogue 0x8000 from IDLE to OPENINTU: Dialogues: Active [1], Completed [0], Successful [0], Failed [0]INTU: State change for dialogue 0x8000 from OPEN to PENDING_DELIMITINTU: State change for dialogue 0x8000 from PENDING_DELIMIT to CLOSINGINTU: State change for dialogue 0x8000 from CLOSING to IDLEINTU: Dialogues: Active [0], Completed [1], Successful [1], Failed [0]INTU: State change for dialogue 0x8001 from IDLE to OPENINTU: Dialogues: Active [1], Completed [1], Successful [1], Failed [0]INTU: State change for dialogue 0x8001 from OPEN to PENDING_DELIMITINTU: State change for dialogue 0x8001 from PENDING_DELIMIT to CLOSINGINTU: State change for dialogue 0x8001 from CLOSING to IDLEINTU: Dialogues: Active [0], Completed [2], Successful [2], Failed [0]


INTU - notes

• The received service key is checked to determine if it matches a pre-set value

• If the key matches, the service logic performs a number translation (from one known number to another) on receipt of the DELIMIT.

• If the called party address is not recognised, a ReleaseCall will be sent.


ITU-T IN specifications

StructureQ.1200

PrinciplesQ.1201

Serviceplane

Q.1202

GlobalFunctional

PlaneQ.1203

DistributedFunctional

PlaneQ.1204

PhysicalPlane

Q.1205

GeneralAspectsQ.1208

Vocabularyof termsQ.1290

INCM

StructureQ.1210

IntroductionQ.1201

CS-1GFP

Q.1213

CS-1DFP

Q.1214

CS-1PP

Q.1205


UserGuide

Q.1219CS-1

StructureQ.1220

IntroductionQ.1221

CS-2GFP

Q.1223

CS-2DFP

Q.1224

CS-2PP

Q.1225


UserGuide

Q.1229CS-2

CS-2 Serviceplane

Q.1221


ETSI IN specifications

ETS 300-374-1 ETSI Core INAP Part 1




Further reading

• ITU-T Q.1219• ‘The Intelligent Network’ Uyless Black, ISBN0-13-793019-4,

Prentice Hall.• ‘The Intelligent network Standards, Their Application to

Services’ Igor Faynberg, Lawrence R. Gabuzda, Marc P. Kaplan, Nitin J. Shah ISBN 0-07-021422-0 McGraw-Hill

• DataKinetics INAP Programmer’s Manual

Documents

ss7_inap