Professional Documents
Culture Documents
Release 9.5(2)
Feature Overview, page 1 Supported Platforms, page 14 Provisionable Properties, page 14 Related Documents, page 15 Obtaining Documentation, Obtaining Support, and Security Guidelines, page 15
Feature Overview
Intelligent Network Functional Model
The Intelligent Network (IN) is described in terms of a functional model as presented by ITU-T Q.1214 specifications. The functional entities include the:
Service Control Function (SCF) Service Switching Function (SSF) Call Control Function (CCF)
Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
The PGW 2200 assumes the role of Service Switching Points (SSPs) that contain both the SSF and the CCF. For the purpose of adding IN services, a portion of the CCF behavior is made visible and is described by a Basic Call State Model (BCSM). The SSF interacts directly with the CCF to make this behavior accessible to the SCF. The SSF communicates with the SCF via INAP. A separate relationship is established between the SSF and the SCF for each call. This occurs when the SSF sends an initial request for instruction to the SCF regarding a new call. Either the SCF or the SSF, depending on circumstances, can terminate the relationship.
Calls progress through a series of states that correspond to Points in Call (PICs). Each state change represents a transition that is precipitated by one or more events. Those PICs where a transfer of control can occur between SSP and SCP have an associated detection point (DP). DP processing allows the transition to be seen by the SCF through an event reporting mechanism. Two types of DPs are defined:
trigger DPs (TDPs)statically armed. event DPs (EDPs)dynamically armed under control of the SCF.
Detection points when armed, cause event reports to be sent to the SCP. An event report can be a notification or a request. A notification informs the SCP of an event and a request specifically requests assistance from the SCP. A request implies a transfer of control to the SCP. For the purpose of the PGW, only the Originating BCSM is used.
Figure 1
Numbers in boxes represent the DPs 10 1. Null. Null 6. Exception Analyzed Information (DP3) is statically armed as a trigger detection point in the dialplan. All other detection points are armed dynamically on request in the Request Report BCSM operation (RRBE)
O_Abandon
2. Collect information
Collected_Info
Analyzed_Info
5. Active
Detection Points
Detection points (DP) are defined in the BCSM. The BCSM reflects a separation between the originating and terminating call state logic so that the BCSM is described as two state machines; the Originating BCSM and the Terminating BCSM. Since certain detection points can occur in both state machines, the DP names are prefixed with either O_ or T_ to distinguish the source.
Description This operation is used to check for the continued existence of a relationship between the SCF and SSF. If the relationship still exists, then the SSF responds. If no reply is received, then the SCF assumes that the SSF has failed and takes an appropriate action. This operation is used by the SSF to report charging related information to the SCF as requested by the SCF using the ApplyCharging operation. This operation is used to notify the SCF of a call related event previously requested by the SCF in an RequestReportBCSMEvent operation. The monitoring of more than one event can be requested with a RequestReportBCSMEvent operation. Each requested event is reported in a separate EventReportBCSM operation. This operation is sent by the SSF after detection of a TDP-R in the BCSM to request the SCF for instructions to complete the call.
Table 2
Description This operation is used to check for the continued existence of a relationship between the SCF and SSF. If the relationship is still in existence, then the SSF will respond. If no reply is received, then the SCF will assume that the SSF has failed in some way and will take the appropriate action. This operation is used for interacting from the SCF with the SSF charging mechanisms. The ApplyChargingReport operation provides the feedback from the SSF to the SCF. Several connection configurations can be established during a call; ApplyCharging can be invoked at the beginning of each connection configuration for each party.
This class 2 operation requests that the SSF perform the basic originating call processing actions that collect destination information from a calling party (normally associated with a RequestReportBCSMEvent operation to arm DP2 and to specify the number of digits to be collected). This operation is used to request the SSF to connect the call to a specified destination. This operation requests that the SSF proceed with call processing at the DP at which it previously suspended call processing to await SCF instructions. The SSF continues call processing without substituting new data from the SCF.
Disconnect Forward Connection (DFC) This operation is used to explicitly disconnect a connection to a resource (SRF) established previously with an EstablishTemporaryConnection operation. It is used for a forward disconnection from the SSF. Establish Temporary Connection (ETC) Furnish Charging Information (FCI) This operation is used to create a temporary connection between an initiating SSF and a SRF. This operation is used to request the SSF to generate, register a call record, or include some information in the default call record. The registered call record is intended for offline charging of the call. The FCI operation can be invoked multiple times. This operation is used to tear down (by the SCF) an existing call at any phase of the call for all parties involved in the call.
Table 2
Description This operation is used to request the SSF to monitor for a call-related event (e.g., BCSM events such as busy or no-answer), then send a notification back to the SCF when the event is detected. This operation instructs the SSF on the charging information to be sent by the SCF. The sending of charging information can either be by charge pulses or signalling or internal if SSF is located in the Local Exchange (LE). The SCI operation can be invoked on multiple times.
Note
Parameters not listed against an operation are either not sent to the SCP or are discarded if received from the SCP.
Activity Test
Table 3 Activity Test
Parameter None
Value N/A
Notes None
Apply Charging
Table 4 Apply Charging
Parameter
Value
Notes Specifies the charging related information to be provided by the SSF and the conditions on which this information has to be reported back to the SCF via the ApplyChargingReport operation. Indicates that ApplyChargingReport operations (at least one at the end of the connection configuration charging process) are expected from the SSF.
sendCalculationToSCPIndication
TRUE or FALSE
ApplyCharging Report
Table 5 ApplyCharging Report
Parameter CallResult
Notes Provides the SCF with the charging related information previously requested using the ApplyCharging operation with its sendCalculationToSCPIndication parameter set to TRUE.
Collect Information
Table 6 Collect Information
Parameter None
Value N/A
Notes Normally associated with a RequestReportBCSMEvent operation to arm DP2 and to specify the number of digits to be collected.
Connect
Table 7 Connect
Notes Contains the called party number to which the call is to be routed. Used by the SCF to instruct the SSF to delete (cut) a specified number of leading digits received from the calling party and paste the remaining dialed digits at the end of the digits supplied by the SCF in the destinationRoutingAddress. Used to provide an alternative to the callingPartyNumber supplied by the network. Indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). Carries the dialed digits if the call has met call forwarding on route to the SSP or is forwarded by the SCP. Indicates the directory number the call was redirected from.
Octet string encoded as defined in ETS-300-356-1 1 octet encoded as defined in ETS-300-356-1 Octet string encoded as defined in ETS-300-356-1 Octet string encoded as defined in ETS-300-356-1
redirectingPartyID
Table 7
Connect (continued)
Value Octet string encoded as defined in ETS-300-356-1 The content is network operator specific.
Notes Contains forwarding related information such as redirecting counter. Contains indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange.
Continue
Table 8 Continue
Parameter None
Value N/A
Notes None
Parameter None
Value N/A
Notes None
Value NQI=128 NOA= 3 (national) NPI = 1 (ISDN) Number Incomplete Indicator =0 (number complete) Address signals = Routing Number
Notes Mandatory IVR address to connect call. One address per ICM instance is supported. CorrelationID is appended to this address in the generic NIC for correlation of call at VRU with network request.
CorrelationID
N/A
Correlation Id can be used instead of appending to AssistingSSPIPRoutingAddress if required (requires customization for carrier). Ignored
SCF ID
N/A
Table 10
Parameter eventTypeBCSM
Value 2 (collectedInfo), 4 (routeSelectFailure), 5 (oCalledPartyBusy) 6 (oNoAnswer) 7 (oAnswer) 9 (oDisconnect) 10 (oAbandon) For CollectedInfo contains the calledPartyNumber. For AnalyzedInformation contains the calledPartyNumber. For RouteSelectFailure contains the FailureCause, if available. For O-CalledPartyBusy contains the BusyCause, if available. For O-NoAnswer is empty. For O-Answer is empty. For O-Disconnect contains the releaseCause, if available.
eventSpecificInformationBCSM
legID miscCallInfo
Indicates the party in the call for which the event is reported. Indicates DP related information.
Value The content is network operator specific. Address signals The content is network operator specific.
Notes Indicates billing and/or charging characteristics. The content is recorded in the CDR. Indicates the destination address of the SRF for assist procedure. Contains indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange.
Value Integer Octet string encoded as defined in ETS-300-356-1. Octet string encoded as defined in ETS-300-356-1. 1 octet encoded as defined in ETS-300-356-1. Octet string encoded as defined in ETS-300-356-1. 2 octets encoded as defined in ETS-300-356-1. 3 (analysedInformation) Octet string encoded as defined in ETS-300-356-1. 2 octets encoded as defined in ETS-300-356-1. Octet string encoded as defined in ETS-300-403-1.
Notes Identifies for the SCF, the requested IN service. Contains the number used to identify the called party in the forward direction, for example, the called party number of ISUP. Carries the calling party number to identify the calling party or the origin of the call. Indicates the type of calling party (e.g., operator, payphone, ordinary subscriber). Carries the dialed digits if the call has met call forwarding on route to the SSP. Indicates whether the call is treated as a national or international call. Indicates the armed BCSM DP event resulting i the InitialDP operation. Indicates the directory number the call was redirected from. Contains forwarding related information such as redirecting counter. Indicates the high layer compatibility type.
10
Parameter eventTypeBCSM
Value 2 (collectedInfo) 4 (routeSelectFailure) 5 (oCalledPartyBusy) 6 (oNoAnswer) 7 (oAnswer) 9 (oDisconnect) 10 (oAbandon) 0 (interrupted) 1 (notifyAndContinue) 2 (transparent)
monitorMode
Indicates how the event is reported. If the monitorMode is interrupted, the event is reported as a request. If the monitorMode is notifyAndContinue, the event is reported as a notification. If the monitorMode is transparent, the event is not reported.
legID dpSpecificCriteria
Indicates the party in the call for which the event is reported. Indicates information specific to the EDP to be armed. numberOfDigitsindicates the number of digits to be collected by the SSF for the CollectedInfo event. If the indicated number of digits is collected, the SSF reports the event to the SCF. applicationTimerindicates the application timer for the NoAnswer event.
numberOfDigits applicationTimer
Parameter sCIBillingChargingCharacteristics
11
Call Flows
Typical Dialogue for INAP Call
The call flow below shows a typical dialogue for an INAP call involving charging operations.
ISUP
IAM
PGW
SCP
[DP3]
ReleaseCall REL
ApplyChargingReport
116183
12
ISUP
IAM
PGW
SCP
[DP3]
InitialDp EstablishTemporaryConnection
IAM [to SRF] ANM DisconnectForwardConnection REL [SRF connection] RLC ApplyCharging FurnishChargingInformation SendChargingInformation RequestReportBCSMEvents REL [DP7] EventReportBCSM Connect PGW disconnects from SRF and awauts further instructions
13
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Release Notes for Cisco Media Gateway Controller Software Release 9.5(1).
Provisioning Example
prov-add:APC:NAME="scp",DESC="SCP point code",NETADDR="0.111.2",NETIND=2 prov-add:SS7ROUTE:NAME="ss7r-scp",DESC="SS7 Route towards SCP",OPC="opc-pgw",DPC="scp",LNKSET="lnkset-1",PRI=1 prov-add:SS7SUBSYS:NAME="scp-ss7subs",DESC="SS7 Subsystem for SCP",SVC="scp",PRI=1,MATEDAPC="",LOCALSSN=12,PROTO="SS7-ITU",STPSCPIND=4,TRANSPROTO="SCCP" ,OPC="opc-pgw",SUAKEY="",REMOTESSN=12 numan-add:resultset:custgrpid="PSTN",name="INservice1" numan-add:resulttable:custgrpid="PSTN",name="INtrigger",resulttype="IN_TRIGGER",dw1="24",d w2="4",dw3="0",dw4="6",setname="INservice1" numan-add:resulttable:custgrpid="PSTN",name="Servicekey1",resulttype="IN_SERVICE_KEY",dw1= "1",setname="INservice1" numan-add:resultset:custgrpid="PSTN",name="INservice2" numan-add:resulttable:custgrpid="PSTN",name="INtrigger",resulttype="IN_TRIGGER",dw1="24",d w2="4",dw3="0",dw4="6",setname="INservice2" numan-add:resulttable:custgrpid="PSTN",name="Servicekey2",resulttype="IN_SERVICE_KEY",dw1= "2",setname="INservice2" numan-add:resultset:custgrpid="PSTN",name="INservice3" numan-add:resulttable:custgrpid="PSTN",name="INtrigger",resulttype="IN_TRIGGER",dw1="24",d w2="4",dw3="0",dw4="6",setname="INservice3" numan-add:resulttable:custgrpid="PSTN",name="Servicekey3",resulttype="IN_SERVICE_KEY",dw1= "3",setname="INservice3" numan-add:bdigtree:custgrpid="PSTN",callside="originating",digitstring="1234561",setname=" INservice1" numan-add:bdigtree:custgrpid="PSTN",callside="originating",digitstring="1234562",setname=" INservice2" numan-add:bdigtree:custgrpid="PSTN",callside="originating",digitstring="1234563",setname=" INservice3"
Provisionable Properties
Provisionable Properties
Note
The new resulttype (IN_SERVICE_KEY) has been added. DW1 is used to provision the IN service key to be used when IN triggering is initiated towards SCP.
14
Related Documents
This document contains information that is related to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are at the following url: http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
15
INAP Feature Module Obtaining Documentation, Obtaining Support, and Security Guidelines
16