Presentation is loading. Please wait.

Presentation is loading. Please wait.

S7INAP.1 1999 DataKinetics Ltd. DataKinetics Intelligent networking.

Similar presentations


Presentation on theme: "S7INAP.1 1999 DataKinetics Ltd. DataKinetics Intelligent networking."— Presentation transcript:

1 S7INAP DataKinetics Ltd. DataKinetics Intelligent networking

2 S7INAP DataKinetics Ltd. Intelligent Networking Overview Conceptual models Example services Configuration Programming Interface Programming examples Example program Debugging

3 S7INAP DataKinetics Ltd. IN - Introduction The Intelligent Network Architecture to quickly create and deploy customer SERVICES Supports many services Is a standard - multi-vendor Distributed platform Example services supported by IN Freephone Premium Rate Voice mail Call Diversion Call baring Local Number Portability UPT

4 S7INAP DataKinetics Ltd. 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

5 S7INAP DataKinetics Ltd. Pre-IN free-phone service SSP Caller dials free- phone 800 number Special 800 exchange PSTN SSP Network routes call (signalling and voice) to special free phone exchange/ server 800 translation database 800 number is translated and forward routed to destination Local exchange

6 S7INAP DataKinetics Ltd. Classic IN physical Architecture SSPIPSCP Service Switching Point - physical circuit switching Intelligent Peripheral Play-back announcements Service Control Point Control and database functions PSTN SSP SCEP/ SMP Service Creation Environment Point/ Service Management Point Service administration SS7 X.25

7 S7INAP DataKinetics Ltd. Function of the IN SSP Point of subscription for the service USER (this is not necessarily the SUBSCRIBER) IN features Detection of IN calls Generation and transmission of queries a SCP Generate and transmit state information to the SCP (B-party busy, B-party no answer) Record and transmit statistics to the SCP Process SCP requests and replies Service filtering

8 S7INAP DataKinetics Ltd. 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

9 S7INAP DataKinetics Ltd. 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)

10 S7INAP DataKinetics Ltd. 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)

11 S7INAP DataKinetics Ltd. 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.

12 S7INAP DataKinetics Ltd. Simplified IN Call SSPIPSCP 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

13 S7INAP DataKinetics Ltd. Freephone service Example SSPSCPSSP 1 2, SSP Multiple destinations

14 S7INAP DataKinetics Ltd. Freephone Service 1.Calling party dials the freephone number (e.g ). 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.

15 S7INAP DataKinetics Ltd. Televoting service Example SSPSCPSSP 1 2,5 3,6 4 IP

16 S7INAP DataKinetics Ltd. 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.

17 S7INAP DataKinetics Ltd. Televoting service method (2) SSPSCPSSP 2 1,3 4 3 IP

18 S7INAP DataKinetics Ltd. Televoting service method (2) 1SCP initiates service filtering (televoting) at the SSP 2Subscriber dials, SSP informs SCP that the specified service has been activated 3SCP instructs the SSP to play an announcement (using the IP) and release the call once the announcement has completed. 4After 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!

19 S7INAP DataKinetics Ltd. 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/Dont Answer Call 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

20 S7INAP DataKinetics Ltd. 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.

21 S7INAP DataKinetics Ltd. Protocol Model SCCP MTP TCAP INAP MTP SCCP TCAP INAP ISUP MTP ISUP IPSSPSCP SCCPTCAPINAP Note: There may also be an ISDN link between the SSP and IP

22 S7INAP DataKinetics Ltd. ISUP To directly control switched circuit channels. Defines message formats, message sequences.

23 S7INAP DataKinetics Ltd. 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

24 S7INAP DataKinetics Ltd. 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.

25 S7INAP DataKinetics Ltd. TCAP control state machines Dialogue handling Establishment, maintenance and close down of dialogues Each dialogue is identified by a dialogue_id. Component handling One state machine per invoked operation on the invoking side Each operation is identified by an invoke_id. Operation timer Controls the duration of a invocation state machine.

26 S7INAP DataKinetics Ltd. Communication TCAP & TCAP-User MTP SCCP TCAP message Transaction Sublayer TC User Component Sublayer Single Components (primitives) 2. Collect Components 3. All collected components of one dialog in one message

27 S7INAP DataKinetics Ltd. 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

28 S7INAP DataKinetics Ltd. 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!)

29 S7INAP DataKinetics Ltd. IN Conceptual Model Four planes (Q.120x) are used to model and abstract the IN functionality: Q Service Plane (SP) Uppermost, describes services from the users perspective. Hides details of implementation from the user Q Global Functional Plane (GFP) contains Service Independent Building Blocks (SIBs), reusable components to build services Q 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 Physical Plane (PP) Real view of the physical network.

30 S7INAP DataKinetics Ltd. SP/GFP Basic call process Translate Charging Screen One number Reverse charging Service Service feature Service Plane Global Functional Plane SIB Q.1213 Q.1212 (Not defined!)

31 S7INAP DataKinetics Ltd. 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

32 S7INAP DataKinetics Ltd. 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 originated Address collected Address analysed Call arrival Busy No Answer Call acceptance Active state End of call CS-1 Points of Return Continue with existing data Proceed with new data Handle as transit Clear call Provide call party handling Initiate call

33 S7INAP DataKinetics Ltd. Freephone modeling with CS-1 SIBs POI Address Analyzed Translate Charge_1 (Calling free of charge) Charge_2 (Record for subscriber) Translate UI POR Proceed with new data POI Busy POR Proceed with new data POI No Answer POR Proceed with new data POI No Answer POR Clear Call BCP SIB Chain 1SIB Chain 2 SIB Chain 3 SIB Chain 4 Service Features Calling line is set free of charge The service subscriber is to be charged The 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.

34 S7INAP DataKinetics Ltd. BCM GFP/DFP (For CS-1) SIB n Distributed Functional Plane Global Functional Plane POI Q.1214 Q.1213 Basic call process POR SCF SDF SRF SSF CCF Functional Entity

35 S7INAP DataKinetics Ltd. Functional Entities Basic Call handling Call Control Agent Functions (CCAF) - models the users telephone Connection Control Function (CCF) - basic switching Specialised Resource Function (SRF) - additional media management Service Execution Functions Service Switching Functions (SSF) - interface to SCF Service Control Function (SCF) - service logic Service Data Function (SDF) - service data SRF Service Management Functions System Management Functions (SMF) - service provisioning, maintenance Service Management Agent Functions (SMAF) - MMI for SMF service Creation Environment Function (SCEF) - specification and testing

36 S7INAP DataKinetics Ltd. FE and SIB association (CS-1)

37 S7INAP DataKinetics Ltd. DFP and the Physical Plane Distributed Functional Plane Q.1214 SCF SDF SRF SSF Functional Entity SSPIP SCP SDF Physical Plane Q.1215 INAP Communication

38 S7INAP DataKinetics Ltd. CS1 physical FE distribution SMAF SMF SCEF SDF SMP SCP SDP SS7 Network IP SN SRF SCF SDF SCF SSF CCF SDF SRF CCF SRF CCAFSDF SSP Voice Transport Signaling Optional FE SCF

39 S7INAP DataKinetics Ltd. 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.

40 S7INAP DataKinetics Ltd. Service Node architecture Bearer Control (DSS1 or ISUP) INAP to SSP INAP to SCP MAP to HLR Management SSF/ CCF SSF/ CCF SRF SDF SCEF SCF

41 S7INAP DataKinetics Ltd. 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

42 S7INAP DataKinetics Ltd. Example SN capabilities Voice messaging subscribers record own messages which are distributed through the network (according to a distribution list). Fax messaging Record fax messages during busy hour to retransmit during off-peak charing period. Short Message Service Gateway to networks. Electronic mail

43 S7INAP DataKinetics Ltd. 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 FEs. The BCP is modelled in the DFP by the Basic Call State Model in the CCF. Basic call process SIB n SCF SDFSSF CCF

44 S7INAP DataKinetics Ltd. 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)

45 S7INAP DataKinetics Ltd. 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.

46 S7INAP DataKinetics Ltd. Types of Triggers Two types of processing on satisfying a DP: Suspend call processing and request instructions Request : TDP_R Continue Call processing and issue Notification to SCF Notification : TDP_N

47 S7INAP DataKinetics Ltd. 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 O_Abandon Orig_attempt Authorised Collected_info Analysed _info O_Answer Route_select_failure O_Called_party_busy O_No_Answer O_Mid_call O_Disconnect Point in Call (PIC) Detection Point (DP)

48 S7INAP DataKinetics Ltd. OBCSM Triggers DP1 : Origination_attempt_authorized Call setup is recognized and authorized. DP2 : Collected_Information Pre-defined number of dialed digits is collected DP3 : Analyzed_Information Dialed digits are analyzed DP4 : Route_Select_Failure Routing failed : no free channel, dialed number not available, network overload DP5 : O_Called_Party_Busy Destination busy DP6 : O_NO_Answer Caller does not answer in predefined time, Service Logic specifies the no answer time for SSP DP7 : O_Answer Called subscriber answers: SSP receives e.g. an ANM DP8 : O_Mid_Call Signal (hook flash, F-key) recognized during call DP9 : O_Disconnect A or B side hangs up DP10 : O_Abandon Call set-up discontinued by the A-side

49 S7INAP DataKinetics Ltd. CS-1 Terminating BCSM 7. T_Null & Authorise termination attempt 8. Select Facility & Present Call 9. T_Alerting 10. T_Active T_Exception 18 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)

50 S7INAP DataKinetics Ltd. TBCSM Triggers DP12 : Termination_attempt_authorized an incoming call attempt is recognized and authorized DP13 : T_Called_Party_Busy Destination busy DP14 : T_No_Answer Called party does not answer during a given time DP15 : T_Answer Called line answers, I.e. the SSP receives the ANM DP16 : T_Mid_Call Signal (e.g. hook flash, function key) is recognized during the active connection DP17 : T_Disconnect Either A-side or B-side hangs up DP18 : T_Abandon Call set-up aborted by the A-side, can happen at any time and is considered normal

51 S7INAP DataKinetics Ltd. 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).

52 S7INAP DataKinetics Ltd. Freephone Example SSFSCFSDF Analyse_info Route_&_Alert O_Active TDP-R TC-BEGIN Initial DP: fph, xxxxxx TC-CONTINUE Connect: call, id = xxxxx Req BCSM event: O_Answer, O_Disconn EDP-N Event: call, id = xxxxx BCSM O_Answer, time TC-CONTINUE Event: call, id = xxxxx BCSM O_Disconnect, time TC-CONTINUE TC-END

53 S7INAP DataKinetics Ltd. Operation: Initial DP Semantics: Report a trigger detection Establishes a control relationship between SSF and SCF Arguments: serviceKey calledPartyNumber callingPartyNumber bearerCapability redirectingPartyId …..

54 S7INAP DataKinetics Ltd. Operation: Connect Semantics Transfer the determined destination number to the SSF Continue the call set-up Arguments: destinationRoutingAddress calledPartyNumber callingPartyNumber redirectingPartyId cutAndPaste...

55 S7INAP DataKinetics Ltd. 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 –SCP instructs CutAndPaste = 4 and destination address = –SSP generates destination address

56 S7INAP DataKinetics Ltd. 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)

57 S7INAP DataKinetics Ltd. Operation: EventReportBCSM Semantics –Reporting of detected event detection points Arguments: –eventTypeBCSM –eventSpecificInformationBCSM –legID

58 S7INAP DataKinetics Ltd. 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 SCF SCF to SRF INAP operations are grouped into Application Service Elements (ASEs). An ASE may be considered as being a collection of operations.

59 S7INAP DataKinetics Ltd. 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.

60 S7INAP DataKinetics Ltd. Protocol layers MTP Layer 1 MTP Layer 3 MTP Layer 2 TUP SCCP ISUPTCAP INAPMAP Application

61 S7INAP DataKinetics Ltd. Application Contexts Application Service Elements are grouped into Application Contexts (ACs). 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 FEs. 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-AC Status-reporting ASE, Cancel ASE

62 S7INAP DataKinetics Ltd. 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 Procedural API interface. Tailored Suites of ASEs (INAP operations) Supported ASEs 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.

63 S7INAP DataKinetics Ltd. Documentation Platform User Guide (Septel cP, PCCS6, SIU) Software Environment Programmers Manual SCCP Programmers Manual TCAP Programmers Manual INAP Programmers Manual

64 S7INAP DataKinetics Ltd. 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 FEs. 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).

65 S7INAP DataKinetics Ltd. Functional Entity Addressing When a dialogue is opened, the user application must supply the SCCP address of the local and remote FEs 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).

66 S7INAP DataKinetics Ltd. Application Context Handling An Application Context (AC) is required for each dialogue between two IN FEs. 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 ACs 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.

67 S7INAP DataKinetics Ltd. Module Capability Maximum number of FEs = 32 Maximum number of ACs = 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-AC Core-INAP-CS1-ASSIST-HANDOFF-TO-SSP-TO-SCP Core-INAP-CS1-IP-TO-SCP Core-INAP-CS1-SSP-to-SCP-AC Core-INAP-CS1-SCP-TO-SSP-TRAFFIC-MANAGEMENT Core-INAP-CS1-SCP-TO-SSP-SERVICE-MANAGEMENT Core-INAP-CS1-SSP-TO-SCP-SERVICE-MANAGEMENT

68 S7INAP DataKinetics Ltd. INAP Configuration Single message, INAP_MSG_CONFIG user_id default application module id if no FEs configured TCAP_id module id used by TCAP (normally 0x14) mngt_id, maint_id Module id for management and maintenance event indications trace_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 TCAP base_tc_icdlgid 1st incoming dialogue id expected from TCAP nog_dialogues maximum number of outgoing dialogues to support nig_dialogues maximum number of incoming dialogues to support num_invokes maximum number of active invokes (operations) to support options ANSI or ITU-T component formats, Transparent AC handling, 14 or 24 bit point codes Septel-SIU Set SCCP_LSS to INAP

69 S7INAP DataKinetics Ltd. FE Configuration Single message per FR, INAP_MSG_CNF_FE fe_reference (0..31). Logical identifier unique to each configured FE FE options Local or Remote Local FE module ID Module ID identifying the user application process handling the local FE FE SCCP address length number of octets of data in the lFE SCCP address FE SCCP Address FE address formatted according to Q.713, ANSI T1.113 Septel-SIU INAP_FE

70 S7INAP DataKinetics Ltd. AC Configuration Single Message per AC, INAP_MSG_CNF_AC application 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

71 S7INAP DataKinetics Ltd. 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 FEs (optional) Configure INAP ACs (optional)

72 S7INAP DataKinetics Ltd. Example configuration Point code = 1 sub-system number = 0x0c module_id = 0x1d FE identifier = 5 sub-system number = 0x0d module_id = 0x2d FE identifier = 5 Point code = 2 sub-system number = 0x0a FE identifier = 1 sub-system number = 0x0b FE identifier = 2 Local Remote

73 S7INAP DataKinetics Ltd. 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_sif M-t7740-i0000-fef-d33-r8000-p e9e * * Configure Local sub-systems * --mult_ind * --mod_id * --type --ssn * --ver spc M-t7741-i0000-fef-d33-r c M-t7741-i0000-fef-d33-r8000-p d * Configure Remote SP's M-t7741-i0000-fef-d33-r8000-p * Configure Remote sub-systems M-t7741-i0000-fef-d33-r8000-p a M-t7741-i0000-fef-d33-r8000-p b *

74 S7INAP DataKinetics Ltd. Example INAP configuration (2) * 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 --inst M-t7780-i0000-fef-d14-r8000-p e9e ff0 * * 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_dlg M-t77f4-i0000-fef-d35-r8000-p77149e9e9e *

75 S7INAP DataKinetics Ltd. Example INAP configuration (3) * Config Remote Functional Entites * addr * --addr len * --local FE module id * ----FE options M-t77f7-i0001-fef-d35-r8000-p a M-t77f7-i0002-fef-d35-r8000-p b * * Config Local Functional Entites M-t77f7-i0005-fef-d35-r8000-p00011d c M-t77f7-i0006-fef-d35-r8000-p00012d d * * Config Application Contexts * --AClen * reserved AC M-t77f6-i0000-fef-d35-r8000-p ba M-t77f6-i0001-fef-d35-r8000-p ba M-t77f6-i0002-fef-d35-r8000-p ba M-t77f6-i0003-fef-d35-r8000-p ba M-t77f6-i0004-fef-d35-r8000-p ba M-t77f6-i0005-fef-d35-r8000-p ba M-t77f6-i0006-fef-d35-r8000-p ba *

76 S7INAP DataKinetics Ltd. Example INAP configuration (4) * * Send UIS (to SCCP), ssn = 0x0c and 0x0d : * --SSA M-tc744-i000c-fef-d33-r8000-p * M-tc744-i000d-fef-d33-r8000-p * 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)

77 S7INAP DataKinetics Ltd. Message based API Receive dialogue event Issue dialogue command Receive results or errors from operations invoked at a remote FE Invoke an operation at a remote FE or respond to 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

78 S7INAP DataKinetics Ltd. INAP_MSG_DLG_REQ INAP Programmers Manual details other message specifications

79 S7INAP DataKinetics Ltd. Dialogue primitive types INAP User to INAP

80 S7INAP DataKinetics Ltd. Dialogue primitive types INAP to INAP User

81 S7INAP DataKinetics Ltd. Dialogue parameters The INAP Programmers Manual defines the parameters and which are required with each primitive type MMandatory OOptional AExclusive OR BExclusive OR CConditional

82 S7INAP DataKinetics Ltd. Service component primitives INAP User to INAP

83 S7INAP DataKinetics Ltd. Service component primitives INAP to INAP User

84 S7INAP DataKinetics Ltd. Service component parameters

85 S7INAP DataKinetics Ltd. 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

86 S7INAP DataKinetics Ltd. 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 detailed in the INAP Programmers Manual

87 S7INAP DataKinetics Ltd. Component encoding CPT MSG 2. Component Building Functions 3. Service Request Encoding Functions 1. Initialise Component

88 S7INAP DataKinetics Ltd. Component building functions Build Operation in Component Buffer API Functions IN_set_operationWrite the operation code IN_set_errorWrite the error code IN_set_resultWrite the result IN_set_component_paramWrite the requested parameter All the above functions operate on the component buffer, which must be subsequently formatted into a message

89 S7INAP DataKinetics Ltd. 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

90 S7INAP DataKinetics Ltd. Component decoding CPT MSG 1. Initialise Component 3. Read Component Buffer Functions 2. Decode Service Indication Functions

91 S7INAP DataKinetics Ltd. 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

92 S7INAP DataKinetics Ltd. Read component buffer IN_get_component_type Return the type of the received component IN_get_component_first_error Determine the first error encountered during encoding IN_get_operation Get received operation code IN_get_component_param Retrieve parameter from received component

93 S7INAP DataKinetics Ltd. 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

94 S7INAP DataKinetics Ltd. Outgoing dialogue request INAP UserINAPTCAP 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 TC-INVOKE

95 S7INAP DataKinetics Ltd. 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.

96 S7INAP DataKinetics Ltd. 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.

97 S7INAP DataKinetics Ltd. 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.

98 S7INAP DataKinetics Ltd. 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.

99 S7INAP DataKinetics Ltd. 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.

100 S7INAP DataKinetics Ltd. 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);

101 S7INAP DataKinetics Ltd. Other examples The INAP Programmers Manual Provides more API examples and message sequence charts.

102 S7INAP DataKinetics Ltd. Debugging Message tracing Software events Maintenance events * Activate Output Event - Trace Mask * non_prim_mask * ip_evt_mask * op_evt_mask M-t57fb-i0000-fef-d35-r8000-p f f f * * Active Error Event Mask M-t57fc-i0000-fef-d35-r8000-pff ff * * Active Maintainence Event Mask M-t57fd-i0000-fef-d35-r8000-p *

103 S7INAP DataKinetics Ltd. INTU example program INTUINAP 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

104 S7INAP DataKinetics Ltd. INTU console H:\SYSTEM7\RUN>intu -b0x8000 INTU: Example INAP application (C) DataKinetics Ltd ============================================================= SS7-INAP-API Version 1.1 INTU module ID - 0x3d INAP module ID - 0x35 Number of dialogues - 0x0800 (2048) Base dialogue ID - 0x8000 Options set - 0x0300 INTU: State change for dialogue 0x8000 from IDLE to OPEN INTU: Dialogues: Active [1], Completed [0], Successful [0], Failed [0] INTU: State change for dialogue 0x8000 from OPEN to PENDING_DELIMIT INTU: State change for dialogue 0x8000 from PENDING_DELIMIT to CLOSING INTU: State change for dialogue 0x8000 from CLOSING to IDLE INTU: Dialogues: Active [0], Completed [1], Successful [1], Failed [0] INTU: State change for dialogue 0x8001 from IDLE to OPEN INTU: Dialogues: Active [1], Completed [1], Successful [1], Failed [0] INTU: State change for dialogue 0x8001 from OPEN to PENDING_DELIMIT INTU: State change for dialogue 0x8001 from PENDING_DELIMIT to CLOSING INTU: State change for dialogue 0x8001 from CLOSING to IDLE INTU: Dialogues: Active [0], Completed [2], Successful [2], Failed [0]

105 S7INAP DataKinetics Ltd. 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.

106 S7INAP DataKinetics Ltd. ITU-T IN specifications Structure Q.1200 Principles Q.1201 Service plane Q.1202 Global Functional Plane Q.1203 Distributed Functional Plane Q.1204 Physical Plane Q.1205 General Aspects Q.1208 Vocabulary of terms Q.1290 INCM Structure Q.1210 Introduction Q.1201 CS-1 GFP Q.1213 CS-1 DFP Q.1214 CS-1 PP Q.1205 General Aspects Q.1218 User Guide Q.1219 CS-1 Structure Q.1220 Introduction Q.1221 CS-2 GFP Q.1223 CS-2 DFP Q.1224 CS-2 PP Q.1225 General Aspects Q.1228 User Guide Q.1229 CS-2 CS-2 Service plane Q.1221

107 S7INAP DataKinetics Ltd. ETSI IN specifications ETS ETSI Core INAP Part 1 ETS ETSI Core INAP Part 2 ETS ETSI Core INAP Part 3

108 S7INAP DataKinetics Ltd. Further reading ITU-T Q.1219 The Intelligent Network Uyless Black, ISBN , Prentice Hall. The Intelligent network Standards, Their Application to Services Igor Faynberg, Lawrence R. Gabuzda, Marc P. Kaplan, Nitin J. Shah ISBN McGraw-Hill DataKinetics INAP Programmers Manual


Download ppt "S7INAP.1 1999 DataKinetics Ltd. DataKinetics Intelligent networking."

Similar presentations


Ads by Google