in chap 04 inap
Post on 24-Oct-2014
130 Views
Preview:
TRANSCRIPT
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
11 Berlin
The IN Application Protocol - INAP
Overview
Example architecture
Triggering
Network events
Private numbering plans
Call information
Dialogs with the caller
Charging of the caller
Charging of the service subscriber
Overload handling
Precounting
Monitoring of dialog resources
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
22 Berlin
IN Application Protocol - OverviewIN Application Protocol - Overview
Q.1218 describes the IN Application Protocol (INAP) required for CS-1. This covers the communication between the following 4 functional entities: SSF, SCF, SRF, SDF
Signalling system #7 provides the basis of the protocol stack
The INAP uses the TCAP services to establish and maintain dialogues between the entities involved in a control relationship
The INAP operations are completely defined in ASN.1
The INAP comprises all procedures of the concerned functional entities
Q.1218 describes the IN Application Protocol (INAP) required for CS-1. This covers the communication between the following 4 functional entities: SSF, SCF, SRF, SDF
Signalling system #7 provides the basis of the protocol stack
The INAP uses the TCAP services to establish and maintain dialogues between the entities involved in a control relationship
The INAP operations are completely defined in ASN.1
The INAP comprises all procedures of the concerned functional entities
MTP MTP
SCCP SCCP
TCAP
INAP
APPL
TCAP
INAP
APPL
SSP SCP
INAP protocol stack between SSP and SCPINAP protocol stack between SSP and SCP
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
33 Berlin
Typical CS-1-conformable IN SystemTypical CS-1-conformable IN System
SCEPSSP/integrated IP
SSP
IP
#7 SMP
SCP
SCP
PSTN / ISDN
Service User
PC / Workstation
PC / Workstation
Intra
net
WAN/LAN
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
44 Berlin
Features of the example architectureFeatures of the example architecture
Support of Core INAP CS-1 by all components
SSP contains an integrated SRF
SSP capable to be located at all network hierarchies, i.e. at local exchange level as well at transit exchange level
External (co-located) IP
Several levels of user dialogue:
DTMF dialogues within calls
Customer Service Control
Service Customisation
Service Creation
Support of Core INAP CS-1 by all components
SSP contains an integrated SRF
SSP capable to be located at all network hierarchies, i.e. at local exchange level as well at transit exchange level
External (co-located) IP
Several levels of user dialogue:
DTMF dialogues within calls
Customer Service Control
Service Customisation
Service Creation
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
55 Berlin
Overview on INAP OperationsOverview on INAP Operations
Q.1218 contains 2 different options of call control:
DP-specific approach This approach uses specific operations per DP, i.e. TDP resp. EDP There exist specific operations to indicate a detected TDP resp. EDP and specific
operations to continue call processing at specific PICs. Approach is widely used in the U.S. and Canada.
DP-generic approach This approach uses generic operations for all DPs, i.e. TDP resp. EDP There exists one pair of operations to indicate a detected TDP and to set up a call to
a determined destination. There exist another pair of operations to arm EDPs and to report detected EDPs. Approach is driven by most network operators and vendors outside the U.S.
Note: Both approaches are not compatible, i.e. one approach has to be selected on a per network basis.
Q.1218 contains 2 different options of call control:
DP-specific approach This approach uses specific operations per DP, i.e. TDP resp. EDP There exist specific operations to indicate a detected TDP resp. EDP and specific
operations to continue call processing at specific PICs. Approach is widely used in the U.S. and Canada.
DP-generic approach This approach uses generic operations for all DPs, i.e. TDP resp. EDP There exists one pair of operations to indicate a detected TDP and to set up a call to
a determined destination. There exist another pair of operations to arm EDPs and to report detected EDPs. Approach is driven by most network operators and vendors outside the U.S.
Note: Both approaches are not compatible, i.e. one approach has to be selected on a per network basis.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
66 Berlin
Overview on INAP Operations (2)Overview on INAP Operations (2)
Basic Call Handling Connect ReleaseCall ConnectToResource DisconnectForwardConnection InitiateCallAttempt EstablishTemporaryConnection AssistRequestInstructions ResetTimer Continue
Triggering and Event Handling InitialDP CollectInformation RequestReportBCSMEvent EventReportBCSM
Congestion Control CallGap
Service Filtering ActivateServiceFilteringService
FilteringResponse
Basic Call Handling Connect ReleaseCall ConnectToResource DisconnectForwardConnection InitiateCallAttempt EstablishTemporaryConnection AssistRequestInstructions ResetTimer Continue
Triggering and Event Handling InitialDP CollectInformation RequestReportBCSMEvent EventReportBCSM
Congestion Control CallGap
Service Filtering ActivateServiceFilteringService
FilteringResponse
Charging FurnishChargingInformation SendChargingInformation ApplyCharging ApplyChargingReport RequestNotificationChargingEvent EventNotificationCharging
Statistics CallInformationRequest CallInformationReport
Fault Recognition ActivityTest
SRF Control PlayAnnouncement PromptAndCollectUserInformation SpecializedResourceReport Cancel
Charging FurnishChargingInformation SendChargingInformation ApplyCharging ApplyChargingReport RequestNotificationChargingEvent EventNotificationCharging
Statistics CallInformationRequest CallInformationReport
Fault Recognition ActivityTest
SRF Control PlayAnnouncement PromptAndCollectUserInformation SpecializedResourceReport Cancel
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
77 Berlin
Description ApproachDescription Approach
In the following the INAP operations will be explained using examples of processing for IN services.
A short description of the IN-Service as well as of the most important service features of the actual example is described before every protocol flow.
In the interest of the concentration on the essential features and the used operations/procedures, necessary parts of real services, such as charging, and statistics will be omitted for simplification.
Attention: The showed signal flows are not complete and only used for the representation of selected network events!
In the following the INAP operations will be explained using examples of processing for IN services.
A short description of the IN-Service as well as of the most important service features of the actual example is described before every protocol flow.
In the interest of the concentration on the essential features and the used operations/procedures, necessary parts of real services, such as charging, and statistics will be omitted for simplification.
Attention: The showed signal flows are not complete and only used for the representation of selected network events!
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
88 Berlin
TriggeringTriggering
Service: Freephone Ablauf: Procedure:
The calling person dials a freephone number At the IN the number will be converted into an E.164 number.
Service: Freephone Ablauf: Procedure:
The calling person dials a freephone number At the IN the number will be converted into an E.164 number.
BEGIN (Initial DP)BEGIN (Initial DP)
SSP SCP
CONTINUE (Connect)CONTINUE (Connect)
Set UpSet Up
Set UpSet Up
AlertingAlerting
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
99 Berlin
Operation: InitialDP Semantics:
Report a TDP Establishment of a control
relationship between SSF and SCF
Arguments:serviceKey, calledPartyNumber, callingPartyNumber, callingPartysCategory, locationNumber,originalCalledPartyId,highLayerCompatibility,additionalCallingPartyNumber ,bearerCapability,redirectingPartyId,redirectionInformation
Operation: InitialDP Semantics:
Report a TDP Establishment of a control
relationship between SSF and SCF
Arguments:serviceKey, calledPartyNumber, callingPartyNumber, callingPartysCategory, locationNumber,originalCalledPartyId,highLayerCompatibility,additionalCallingPartyNumber ,bearerCapability,redirectingPartyId,redirectionInformation
Operation: Connect Semantics:
Transfer of the determined destination number to the SSF
Continuation of the call setup Arguments:
destinationRoutingAddresscutAndPasteserviceInteractionIndicatorscallingPartyNumbercallingPartysCategoryredirectingPartyIDredirectionInformation
Operation: Connect Semantics:
Transfer of the determined destination number to the SSF
Continuation of the call setup Arguments:
destinationRoutingAddresscutAndPasteserviceInteractionIndicatorscallingPartyNumbercallingPartysCategoryredirectingPartyIDredirectionInformation
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1010Berlin
Semantics of “cutAndPaste”Semantics of “cutAndPaste”
Cut&Paste describes the digit processing of the SSP concerning the destination address received from the SCP. The Cut&Paste value instructs the SSP to remove (‘cut’) 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 (‘paste’).
Example:
The SSP received from the network the digits ‘123456789’. The SCP deliversCutAndPaste = 4 and the destination address ‘503322’. After this the SSP generates the destination address for the call setup as follows:
‘cut’ 4 digits at the SSP: 1234– ‘paste’ the rest ‘56789’ to ‘503322’
– Result: ‘50332256789’
Application:
The ‘Cut&Paste’-mechanism is used by all services where the SCP does not need the complete call information respectively can not decide when the call information is complete.
Cut&Paste describes the digit processing of the SSP concerning the destination address received from the SCP. The Cut&Paste value instructs the SSP to remove (‘cut’) 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 (‘paste’).
Example:
The SSP received from the network the digits ‘123456789’. The SCP deliversCutAndPaste = 4 and the destination address ‘503322’. After this the SSP generates the destination address for the call setup as follows:
‘cut’ 4 digits at the SSP: 1234– ‘paste’ the rest ‘56789’ to ‘503322’
– Result: ‘50332256789’
Application:
The ‘Cut&Paste’-mechanism is used by all services where the SCP does not need the complete call information respectively can not decide when the call information is complete.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1111Berlin
Monitoring of network events (1)Monitoring of network events (1)
Service: Freephone with rerouting on ‘busy’ resp. ‘no answer’
Ablauf: The call setup is monitored referring to ‘busy’/’no answer’.
Upon the detection of one of the events the call will be routed to an alternative destination.
Service: Freephone with rerouting on ‘busy’ resp. ‘no answer’
Ablauf: The call setup is monitored referring to ‘busy’/’no answer’.
Upon the detection of one of the events the call will be routed to an alternative destination.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1212Berlin
Monitoring of network events (2)Monitoring of network events (2)
Route_Select_Failure
o_Null&Auth.Orig.Attempt
DP10
DP1
PIC2:
PIC1:
Collect_Info
PIC6: o_Exception
DP2
PIC3: Analyze_Info
DP3
PIC4: Routing & Alerting
DP7
PIC5: o_Active
DP8
o_mid_Call
DP9
o_Disconnect
o_Abandon
Orig._Attempt_Authorized
Collected_Info
Analyzed_Info
o_Answer
DP4
DP5
DP6
o_Called_Party_Busy
o_No_Answer
DP = Detection PointPIC = Point in Call
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1313Berlin
Monitoring of network events (3)Monitoring of network events (3)
BEGIN (Initial DP)BEGIN (Initial DP)Set Up
CONTINUE (RequestReportBCSMEvent, Connect)CONTINUE (RequestReportBCSMEvent, Connect)Set UpSet Up
Set UpSet Up
AlertingAlerting
Release (busy)Release (busy)
CONTINUE (EventReportBCSM (busy))CONTINUE (EventReportBCSM (busy))
CONTINUE (Connect)CONTINUE (Connect)Set UpSet Up
AlertingAlerting
ConnectConnect Connect Connect
SCPSSP
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1414Berlin
Operation: RequestReportBCSMEvent
Semantics: Arming of Event Detection
Points (EDP) at the SSP for call monitoring
Arguments: List of elements of the type
BcsmEvent‘
Each element specifies the type of the Detection Points to be armed and additional criteria.
Example: DP4 (route select failure) DP5 (busy) DP6 (no answer) DP9 (disconnect)
Operation: RequestReportBCSMEvent
Semantics: Arming of Event Detection
Points (EDP) at the SSP for call monitoring
Arguments: List of elements of the type
BcsmEvent‘
Each element specifies the type of the Detection Points to be armed and additional criteria.
Example: DP4 (route select failure) DP5 (busy) DP6 (no answer) DP9 (disconnect)
Operation: EventReportBCSM
Semantics: Reporting of detected Event
Detection Points Arguments:
eventTypeBCSM
eventSpecificInformationBCSM
legId
miscCallInfo
Operation: EventReportBCSM
Semantics: Reporting of detected Event
Detection Points Arguments:
eventTypeBCSM
eventSpecificInformationBCSM
legId
miscCallInfo
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1515Berlin
Private numbering plans (1)Private numbering plans (1)
Service: Virtual Private Networks
Procedure: The calling person dials a VPN-number
The service logic recognises that further digits are necessary within the scope of digit analysis.
The SCP requests further digits. The dialling of further digits will be monitored.
Service: Virtual Private Networks
Procedure: The calling person dials a VPN-number
The service logic recognises that further digits are necessary within the scope of digit analysis.
The SCP requests further digits. The dialling of further digits will be monitored.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1616Berlin
Private numbering plans (2)Private numbering plans (2)
BEGIN (Initial DP)BEGIN (Initial DP)Set Up
CONTINUE (RequestReportBCSMEvent, Collectinfo)CONTINUE (RequestReportBCSMEvent, Collectinfo)
Set UpSet Up
AlertingAlerting
CONTINUE (EventReportBCSM (DP2))CONTINUE (EventReportBCSM (DP2))
CONTINUE (Connect)CONTINUE (Connect)
Set UpSet Up
AlertingAlerting
ConnectConnect Connect Connect
SSP SCP
SSP expects more digitsSSP expects more digits
SCP needs more digits.
SCP needs more digits.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1717Berlin
Operation:CollectInformation
Semantics: Reset the BCSM & wait for more
digits Arguments:
non
Hints:
CollectInformation can only be used directly after triggering
Before CollectInformation the DP2 must be armed by RequestReportBCSMEvent.
In the context of the DP2 arming the number of expected digits will be defined by the DP criteria.
Operation:CollectInformation
Semantics: Reset the BCSM & wait for more
digits Arguments:
non
Hints:
CollectInformation can only be used directly after triggering
Before CollectInformation the DP2 must be armed by RequestReportBCSMEvent.
In the context of the DP2 arming the number of expected digits will be defined by the DP criteria.
Alternative approach:
There exists also an alternative solution compared to the use of the operation 'CollectInformation'.
That approach requests the use of an 'end of dialling' supervision at the SSP:
End of dialling digitOR
End of dialling timer
This can be easily achieved by administering the respective trigger data in an appropriate way.
Alternative approach:
There exists also an alternative solution compared to the use of the operation 'CollectInformation'.
That approach requests the use of an 'end of dialling' supervision at the SSP:
End of dialling digitOR
End of dialling timer
This can be easily achieved by administering the respective trigger data in an appropriate way.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1818Berlin
Logging of call information (1)Logging of call information (1)
Service: Freephone with logging of call information at the SCP
Procedure: The calling party dials a freephone number.
At the IN the number will be converted into an E.164 number.
With the instruction for call setup, information for the call will be demanded.
The call information will be reported to the SCP at the end of the call.
Service: Freephone with logging of call information at the SCP
Procedure: The calling party dials a freephone number.
At the IN the number will be converted into an E.164 number.
With the instruction for call setup, information for the call will be demanded.
The call information will be reported to the SCP at the end of the call.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
1919Berlin
Logging of call information (2)Logging of call information (2)
SSP SSP
SMP
SCP
PSTN/ISDN
Postprocessing
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2020Berlin
Logging of call information (3)Logging of call information (3)
BEGIN (Initial DP)BEGIN (Initial DP)Set Up
CONTINUE (CallInformationRequest, Connect)CONTINUE (CallInformationRequest, Connect)
Set UpSet Up
AlertingAlerting Set UpSet Up
AlertingAlerting
ConnectConnect Connect Connect
SSP SCP
ReleaseRelease Release Release
CONTINUE (CallInformationReport)CONTINUE (CallInformationReport)
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2121Berlin
Operation: CallInformationRequest
Semantics: The SCP requests the SSP to
record certain information about the actual call and to report the end of the call to the SCP.
Arguments:
RequestedInformationType
callAttemptlapsedTime,
callStopTime,
callConnectedElapsedTime,
releaseCause
Operation: CallInformationRequest
Semantics: The SCP requests the SSP to
record certain information about the actual call and to report the end of the call to the SCP.
Arguments:
RequestedInformationType
callAttemptlapsedTime,
callStopTime,
callConnectedElapsedTime,
releaseCause
Operation: CallInformationReport
Semantics: The SSP reports the requested
information at the end of the call to the SCP.
Arguments:
RequestedInformationValue
callAttemptElapsedTimeValue,
callStopTimeValue,
callConnectedElapsedTimeValue,
releaseCauseValue,
Operation: CallInformationReport
Semantics: The SSP reports the requested
information at the end of the call to the SCP.
Arguments:
RequestedInformationValue
callAttemptElapsedTimeValue,
callStopTimeValue,
callConnectedElapsedTimeValue,
releaseCauseValue,
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2222Berlin
Caller dialogsCaller dialogs
SRF
IPAccessSignalling
AccessSignalling
ISUP
ISUP
DLE
SSP
CCF
SSF
INAP
SCP
SCF
OLEinternesInterface
Configuration of the announcement equipment
Configuration of the announcement equipment
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2323Berlin
Caller dialogs - announcements (1)Caller dialogs - announcements (1)
Service: Freephone with time window
Ablauf: The calling person dials the freephone number.
The set time window will be checked at the IN.
As a result of the check an announcement is played to the calling person. („Our office is already closed. Please call number ‚xyz‘.“
After the announcement the call will be released.
Service: Freephone with time window
Ablauf: The calling person dials the freephone number.
The set time window will be checked at the IN.
As a result of the check an announcement is played to the calling person. („Our office is already closed. Please call number ‚xyz‘.“
After the announcement the call will be released.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2424Berlin
Caller dialogs - announcements (2)Caller dialogs - announcements (2)
BEGIN (Initial DP)BEGIN (Initial DP)
CONTINUE (ConnectToResource, Play Announcement)CONTINUE (ConnectToResource, Play Announcement)
Set UpSet Up
AlertingAlerting
Release Release
SSP SCP
Set Up & PASet Up & PA
AnnCompleteAnnComplete
CONTINUE (SpecializedResourceReport)CONTINUE (SpecializedResourceReport)
CONTINUE (DisconnectForwardConnection, ReleaseCall)
CONTINUE (DisconnectForwardConnection, ReleaseCall)
Release Release
****** Announcement *********** Announcement *****
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2525Berlin
Operation: ConnectToResource
Semantics: The SCP instructs the SSP to
setup a connection to an IP. Arguments:
ResourceAddress
ServiceInteractionIndicator
Operation: ConnectToResource
Semantics: The SCP instructs the SSP to
setup a connection to an IP. Arguments:
ResourceAddress
ServiceInteractionIndicator
Operation: PlayAnnouncement
Semantics: Control announcements
simple announcements composed announcements
Arguments:informationToSend,
messageID,elementaryMessageID,elementaryMessageID,variableMessage,
numberOfRepetitions,
duration,
interval,
disconnectFromIPForbidden,
requestAnnouncementComplete
Operation: PlayAnnouncement
Semantics: Control announcements
simple announcements composed announcements
Arguments:informationToSend,
messageID,elementaryMessageID,elementaryMessageID,variableMessage,
numberOfRepetitions,
duration,
interval,
disconnectFromIPForbidden,
requestAnnouncementComplete
Operation: SpecializedResourceReport
Semantics: Report end of announcement
Arguments:non
Operation: SpecializedResourceReport
Semantics: Report end of announcement
Arguments:non
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2626Berlin
Operation: Disconnect ForwardConnection
Semantics: Release of IP connection
Arguments:non
Operation: Disconnect ForwardConnection
Semantics: Release of IP connection
Arguments:non
Operation: ReleaseCall
Semantics: Call release
Arguments:ReleaseCause
Operation: ReleaseCall
Semantics: Call release
Arguments:ReleaseCause
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2727Berlin
Caller dialogs - digit collection (1)Caller dialogs - digit collection (1)
Service: Account Card Calling The service subscriber (card owner) is charged via a personal account, e.g.
telecard, credit card and so on.
The charging will be carried out via a monthly bill.
Every subscriber has a PIN for the authorization.
Procedure: The calling person dials an ACC-number.
An announcement (Prompt) is played to the calling party. With the announcement the calling party is asked to enter the account number and PIN.
After the calling party has finished the data input the SSP transmits the data to the SCP.
After the verification of data the SCP instructs the SSP to create an IN-AMA record for the service subscriber and to perform a call setup to the destination.
Service: Account Card Calling The service subscriber (card owner) is charged via a personal account, e.g.
telecard, credit card and so on.
The charging will be carried out via a monthly bill.
Every subscriber has a PIN for the authorization.
Procedure: The calling person dials an ACC-number.
An announcement (Prompt) is played to the calling party. With the announcement the calling party is asked to enter the account number and PIN.
After the calling party has finished the data input the SSP transmits the data to the SCP.
After the verification of data the SCP instructs the SSP to create an IN-AMA record for the service subscriber and to perform a call setup to the destination.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2828Berlin
Caller dialogs - digit collection (2)Caller dialogs - digit collection (2)
BEGIN (Initial DP)BEGIN (Initial DP)
CONTINUE (ConnectToResource, PromptAndCollectUserInformation)
CONTINUE (ConnectToResource, PromptAndCollectUserInformation)
Set UpSet Up
AlertingAlerting
ConnectConnect
SSP SCP
Set Up & PCSet Up & PC
AnnCompleteAnnComplete
CONTINUE (RESULT: Digits Response)
CONTINUE (DisconnectForwardConnection, Connect)CONTINUE (DisconnectForwardConnection, Connect)
Release Release
***Prompt*** & DTMF-Input***(Account, PIN, Zielrufnr.)
***Prompt*** & DTMF-Input***(Account, PIN, Zielrufnr.)
Interner IP
Set Up
Alerting
Connect
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
2929Berlin
Operation: PromptAndCollectUserInformation
Semantics: Control announcements
simple announcements composed announcements
AND Collection of DTMF digits resp.
voice input Argumente:
collectedInfo,
minimumNbOfDigits,
maximumNbOfDigits,
endOfReplyDigit,
cancelDigit,
startDigit,
firstDigitTimeOut,
Operation: PromptAndCollectUserInformation
Semantics: Control announcements
simple announcements composed announcements
AND Collection of DTMF digits resp.
voice input Argumente:
collectedInfo,
minimumNbOfDigits,
maximumNbOfDigits,
endOfReplyDigit,
cancelDigit,
startDigit,
firstDigitTimeOut,
interDigitTimeOut,
errorTreatment,
interuptableAnnouncement,
disconnectFromIPForbidden,
informationToSend,
messageID,elementaryMessageID,elementaryMessageIDs,variableMessage,
numberOfRepetitions,
duration,
interval,
disconnectFromIPForbidden,
requestAnnouncementComplete
interDigitTimeOut,
errorTreatment,
interuptableAnnouncement,
disconnectFromIPForbidden,
informationToSend,
messageID,elementaryMessageID,elementaryMessageIDs,variableMessage,
numberOfRepetitions,
duration,
interval,
disconnectFromIPForbidden,
requestAnnouncementComplete
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3030Berlin
Caller Charging (1)Caller Charging (1)
In several services the calling user (access line) needs to be charged. This can be performed in the following ways:
Controlled by the PSTNThe PSTN determines the charge to be applied based on the dialled number ("zoning") ORthe PSTN creates a call record which serves for off-line charging.
Controlled by the INThe service logic determines the charge to be applied and controls the PSTN charging.This requires the following procedure:
transfer charging information from SCP to SSP
send a charge band number from SSP into PSTN/ ISDN
OR
send meter pulses from SSP into PSTN/ ISDN
In several services the calling user (access line) needs to be charged. This can be performed in the following ways:
Controlled by the PSTNThe PSTN determines the charge to be applied based on the dialled number ("zoning") ORthe PSTN creates a call record which serves for off-line charging.
Controlled by the INThe service logic determines the charge to be applied and controls the PSTN charging.This requires the following procedure:
transfer charging information from SCP to SSP
send a charge band number from SSP into PSTN/ ISDN
OR
send meter pulses from SSP into PSTN/ ISDN
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3131Berlin
Caller Charging (2)Caller Charging (2)
SSP SSP
SMP
SCP
PSTN/ISDN
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3232Berlin
Caller Charging (3)Caller Charging (3)
Service: Universal Access Number The calling person will be charged via his line.
The charging is controlled by the IN.
Procedure:
The calling person dials a freephone number.
At the IN the number will be converted into an E.164 number.
For charging purposes, a charge band number will be sent to the originating local exchange.
Service: Universal Access Number The calling person will be charged via his line.
The charging is controlled by the IN.
Procedure:
The calling person dials a freephone number.
At the IN the number will be converted into an E.164 number.
For charging purposes, a charge band number will be sent to the originating local exchange.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3333Berlin
Caller Charging (4)Caller Charging (4)
BEGIN (Initial DP)BEGIN (Initial DP)
CONTINUE (SendChargingInformation, Connect)CONTINUE (SendChargingInformation, Connect)
Set UpSet Up
Set UpSet Up
AlertingAlerting
AlertingAlerting
ConnectConnect
Connect Connect
SSP SCP
ChargeCharge
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3434Berlin
Operation: SendChargingInformation
Semantics: Charging of the calling line
The existing functions of the basic network are used for charging.
At the basic network, charging of the calling line will be fixed corresponding to the instructions of the service logic.
Initiates the message ‘Charge’
Operation: SendChargingInformation
Semantics: Charging of the calling line
The existing functions of the basic network are used for charging.
At the basic network, charging of the calling line will be fixed corresponding to the instructions of the service logic.
Initiates the message ‘Charge’
Arguments: ‘SCP Charge Number’
0 = line is free of charge
1 = charging is done by a subsequent exchange.
2 .. 255 = zone information
Note: The listed arguments are just examples. There are no definitions in the standard.
Arguments: ‘SCP Charge Number’
0 = line is free of charge
1 = charging is done by a subsequent exchange.
2 .. 255 = zone information
Note: The listed arguments are just examples. There are no definitions in the standard.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3535Berlin
Subscriber chargingSubscriber charging
There are several ways to charge the service subscriber:
Creation of IN AMA records at the SSP
Charging at the SCP supported by the SSP
Charging by IN AMA records in the SSP
Here the SCP instructs the SSP to create IN AMA records:
transfer of charging information from SCP to SSP
IN-AMA record created at the SSP.
There are several ways to charge the service subscriber:
Creation of IN AMA records at the SSP
Charging at the SCP supported by the SSP
Charging by IN AMA records in the SSP
Here the SCP instructs the SSP to create IN AMA records:
transfer of charging information from SCP to SSP
IN-AMA record created at the SSP.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3636Berlin
Subscriber records at the SSP (1)Subscriber records at the SSP (1)
SSP SSP
SMP
SCP
PSTN/ISDN
Post processing
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3737Berlin
Subscriber-Records at the SSP (2)Subscriber-Records at the SSP (2)
Service: Freephone Calling person is free of charge (by network administration)
The service subscriber will be charged by the IN-AMA record.
Procedure:
The calling person dials a freephone number.
At the IN, the number will be converted into an E.164 number.
The SCP instructs the SSP to create an IN-AMA record for the service subscriber.
Service: Freephone Calling person is free of charge (by network administration)
The service subscriber will be charged by the IN-AMA record.
Procedure:
The calling person dials a freephone number.
At the IN, the number will be converted into an E.164 number.
The SCP instructs the SSP to create an IN-AMA record for the service subscriber.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3838Berlin
Subscriber-Records at the SSP (3)Subscriber-Records at the SSP (3)
BEGIN (Initial DP)BEGIN (Initial DP)
SSP SCP
Set Up
CONTINUE (FurnishChargingInformation, Connect)
CONTINUE (FurnishChargingInformation, Connect)
Set UpSet Up
Set UpSet Up
AlertingAlerting
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
3939Berlin
Operation: FurnishChargingInformation
Semantics: The SCP requests the SSP
to create an IN AMA record.
A part of the information for the IN AMA record will be delivered by the FCI operation.
The SSP adds call related information to the IN AMA record.
Operation: FurnishChargingInformation
Semantics: The SCP requests the SSP
to create an IN AMA record.
A part of the information for the IN AMA record will be delivered by the FCI operation.
The SSP adds call related information to the IN AMA record.
Arguments: Charged Party Identification
Sequence Information (first IN-AMA, subsequent IN-AMA, last IN-AMA)
Call Type and Status e.g. successful call, successful registration (TVS), successful call for OnNet-to-OnNet calling, catchment area violation
Destination TypeShows the destination type as well as the service features if necessary, e.g. - real B party- real B party, rerouting on Busy and No Answer- customer specific announcement- announcement providing the charge
Arguments: Charged Party Identification
Sequence Information (first IN-AMA, subsequent IN-AMA, last IN-AMA)
Call Type and Status e.g. successful call, successful registration (TVS), successful call for OnNet-to-OnNet calling, catchment area violation
Destination TypeShows the destination type as well as the service features if necessary, e.g. - real B party- real B party, rerouting on Busy and No Answer- customer specific announcement- announcement providing the charge
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4040Berlin
On-line charging at the SCP (1)On-line charging at the SCP (1)
In this scenario the following procedure is used:
The SCP provides charging control information to the SSP.
The SSP performs online charging according to that information and reports the determined charge back to the SCP at the end of the callor
after a given charging account has been completely used by the actual call (charging supervision)
Application:
Account Card Calling
Prepaid Card Service
Call supervision services
In this scenario the following procedure is used:
The SCP provides charging control information to the SSP.
The SSP performs online charging according to that information and reports the determined charge back to the SCP at the end of the callor
after a given charging account has been completely used by the actual call (charging supervision)
Application:
Account Card Calling
Prepaid Card Service
Call supervision services
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4141Berlin
On-line charging at the SCP (2)On-line charging at the SCP (2)
SSP SSP
SMP
SCP
PSTN/ISDN
Post processing
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4242Berlin
On-line charging at the SCP (3)On-line charging at the SCP (3)
Service: Prepaid Card Calling The service subscriber (card owner) is charged on a personal account,
e.g. telecard, creditcard and so on.
The charging is performed online per call.
Procedure:
The calling person is automatically connected to the service after dialling (originating trigger for Prepaid Card Service) or dials an ACC-number.
An authentication procedure is performed by the service logic.
After the verification of data the SCP instructs the SSP to perform online charging for the service subscriber and to perform a call setup to the destination.
Service: Prepaid Card Calling The service subscriber (card owner) is charged on a personal account,
e.g. telecard, creditcard and so on.
The charging is performed online per call.
Procedure:
The calling person is automatically connected to the service after dialling (originating trigger for Prepaid Card Service) or dials an ACC-number.
An authentication procedure is performed by the service logic.
After the verification of data the SCP instructs the SSP to perform online charging for the service subscriber and to perform a call setup to the destination.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4343Berlin
On-line charging at the SCP (4)On-line charging at the SCP (4)
BEGIN (Initial DP)BEGIN (Initial DP)
SSP SCP
Set Up
CONTINUE (ApplyCharging, Connect)
CONTINUE (ApplyCharging, Connect)
Set UpSet Up
Set UpSet Up
AlertingAlerting
Authentication via user interaction or SCP internal
ReleaseReleaseReleaseRelease
CONTINUE (ApplyChargingReport)
CONTINUE (ApplyChargingReport)
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4444Berlin
Overload handling (1)Overload handling (1)
Overload can occur at following places:
Network access/ network exit (subscribers, trunks) - no IN-specific overload
CCS#7 network (signalling between SSP and SCP)
SCP (internal)
SMP - will not be considered here
IN-specific resources at the SSP, IPs
Overload can occur at following places:
Network access/ network exit (subscribers, trunks) - no IN-specific overload
CCS#7 network (signalling between SSP and SCP)
SCP (internal)
SMP - will not be considered here
IN-specific resources at the SSP, IPs
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4545Berlin
Overload handling (2)Overload handling (2)
SCEPSSP/integrated IP
SSP
IP
#7 SMP
SCP
SCP
PSTN / ISDN
Service User
PC / Workstation
PC / Workstation
WAN/LAN
Intra
net
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4646Berlin
Overload handling (3)Overload handling (3)
The overload control is supposed to protect an IN-system against an overload state.
In case of overload, the creation of new load, that means the opening of further dialogues between the SSP and the SCP, has to be prevented.
Process during triggering:
If a call is recognised as an IN-call at the SSP, the needed instructions for a call set-up will be requested from an SCP.
If the number of requests of one SSP or the sum of requests of all SSPs is too big, there is the danger to overload the SCP or the signalling network. Not all requests will be answered in time. Call losses with blind load could be the result.
The overload control must start directly while triggering.
The overload control is supposed to protect an IN-system against an overload state.
In case of overload, the creation of new load, that means the opening of further dialogues between the SSP and the SCP, has to be prevented.
Process during triggering:
If a call is recognised as an IN-call at the SSP, the needed instructions for a call set-up will be requested from an SCP.
If the number of requests of one SSP or the sum of requests of all SSPs is too big, there is the danger to overload the SCP or the signalling network. Not all requests will be answered in time. Call losses with blind load could be the result.
The overload control must start directly while triggering.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4747Berlin
Overload handling (4)Overload handling (4)
Recognition of the overload situation:
The overload is recognised at the SCP.
Overload can be recognised and handled in time by the SCP. Call losses and blind load can be avoided.
The necessary measures will be determined by the SCP and requested by INAP-operations at the SSP(s).
The SSPs carry out the requested steps with the parameters determined by the SCP.
The SCP determines the allowed maximum load, the duration of the load limitation and the calls, the overload criterion is valid for.
Recognition of the overload situation:
The overload is recognised at the SCP.
Overload can be recognised and handled in time by the SCP. Call losses and blind load can be avoided.
The necessary measures will be determined by the SCP and requested by INAP-operations at the SSP(s).
The SSPs carry out the requested steps with the parameters determined by the SCP.
The SCP determines the allowed maximum load, the duration of the load limitation and the calls, the overload criterion is valid for.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4848Berlin
Overload handling (5)Overload handling (5)
At the INAP, the use of the Automatic Call Gapping (ACG) is standardized:
A so called "GapInterval" will be set.
This GapInterval determines the time interval, which must pass until the next request to the SCP is allowed.
The values for the "GapInterval" will be determined by the SCP and transmitted to the SSP.
At the INAP, the use of the Automatic Call Gapping (ACG) is standardized:
A so called "GapInterval" will be set.
This GapInterval determines the time interval, which must pass until the next request to the SCP is allowed.
The values for the "GapInterval" will be determined by the SCP and transmitted to the SSP.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
4949Berlin
Overload handling (6)Overload handling (6)
Call Gapping - basic procedureCall Gapping - basic procedure
incoming callsincoming calls
SCP queriesSCP queries
Gap Interval
Gap Interval
Gap Interval
Gap Interval
Gap Interval
Gap Interval
Gap Interval
Gap Interval
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5050Berlin
Operation: CallGap
Semantics: The SCP requests the SSP
to adjust Automatic Call Gapping corresponding to the transmitted parameters: - ACG activation,- ACG deactivation,- modify an active ACG.
The request for ACG happens either apart from a call related TCAP-dialogue, that means in an own dialogue, or in the context of an existing control relationship.
Operation: CallGap
Semantics: The SCP requests the SSP
to adjust Automatic Call Gapping corresponding to the transmitted parameters: - ACG activation,- ACG deactivation,- modify an active ACG.
The request for ACG happens either apart from a call related TCAP-dialogue, that means in an own dialogue, or in the context of an existing control relationship.
Arguments:gapCriteria,
serviceKey
OR
calledAddress & serviceKey
gapIndicators,
duration,
interval,
gapTreatment,
informationToSend,
OR
releaseCause,
OR
both
Arguments:gapCriteria,
serviceKey
OR
calledAddress & serviceKey
gapIndicators,
duration,
interval,
gapTreatment,
informationToSend,
OR
releaseCause,
OR
both
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5151Berlin
BEGIN (CallGap)
Set Up
Alerting
Release
SSP SCP
Set Up & PA
****Announcement****
Internal IP
Release
Set Up
Alerting
****Announcement****
AnnComplete
Set Up & PA
AnnComplete
Set Up BEGIN (InitialDP)
Alerting
Set Up
Set Up & PA
****Announcement****
Hint:Instead of playing the announcement it’s also possible, that there is a release.
Hint:Instead of playing the announcement it’s also possible, that there is a release.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5252Berlin
Precounting (1)Precounting (1)
A preventive overload control is useful for services with very high traffic volume respectively high peak loads.
Preventive overload control describes fix call limits, which are independent from the load existing in reality. Based on it, the call limits can not adapt themselves to the real existing load.
Service Filtering is an excellent form of preventive overload control. With this method most calls will be treated at the SSP without querying the SCP.
The information necessary for the call processing has been received by the SSP from the SCP before.
Service Filtering is usable for simple services only (e.g. Tele Voting, announcement services with simple charging and simple announcement control). Here, the SSP contains a part of the Service Logic.
The advantage of Service Filtering is that no calls must be thrown away.
A preventive overload control is useful for services with very high traffic volume respectively high peak loads.
Preventive overload control describes fix call limits, which are independent from the load existing in reality. Based on it, the call limits can not adapt themselves to the real existing load.
Service Filtering is an excellent form of preventive overload control. With this method most calls will be treated at the SSP without querying the SCP.
The information necessary for the call processing has been received by the SSP from the SCP before.
Service Filtering is usable for simple services only (e.g. Tele Voting, announcement services with simple charging and simple announcement control). Here, the SSP contains a part of the Service Logic.
The advantage of Service Filtering is that no calls must be thrown away.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5353Berlin
Precounting (2)Precounting (2)
Service: Televoting Counting of calls to certain destinations and playing of confirmation
announcements.
Procedure:
The calling party dials a TVS-number.
As a result of the check, an announcement will be played to the calling party. "Thank you for the call. Your call has been counted“.
After the announcement, the call will be released.
Service: Televoting Counting of calls to certain destinations and playing of confirmation
announcements.
Procedure:
The calling party dials a TVS-number.
As a result of the check, an announcement will be played to the calling party. "Thank you for the call. Your call has been counted“.
After the announcement, the call will be released.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5454Berlin
Precounting (3) - Televoting without PrecountingPrecounting (3) - Televoting without Precounting
BEGIN (Initial DP)BEGIN (Initial DP)
CONTINUECONTINUE
Set UpSet Up
AlertingAlerting
(ConnectToResource, Play Announcement)
Release Release
SSP SCP
Set Up & PASet Up & PA
AnnCompleteAnnComplete
CONTINUE (SpecializedResourceReport)CONTINUE (SpecializedResourceReport)
CONTINUE (DisconnectForwardConnection, ReleaseCall)
CONTINUE (DisconnectForwardConnection, ReleaseCall)
Release Release
******Announcement***********Announcement*****
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5555Berlin
Precounting (4) - Televoting with PrecountingPrecounting (4) - Televoting with Precounting
Service: Televoting Counting of calls to certain destinations and playing of a confirmation
announcement.
Procedure:
The calling party dials a TVS-number.
As a result of the check there will be played an announcement to the calling party: "Thank you for your call. The call is counted.“
Remark:
After the announcement the call will be released.
The announcement will be played by the SSP without request of the SCP. After this the SSP releases the call
In a fix time interval, the SSP reports the SCP the number of processed calls per destination, that means the counted votes.
Service: Televoting Counting of calls to certain destinations and playing of a confirmation
announcement.
Procedure:
The calling party dials a TVS-number.
As a result of the check there will be played an announcement to the calling party: "Thank you for your call. The call is counted.“
Remark:
After the announcement the call will be released.
The announcement will be played by the SSP without request of the SCP. After this the SSP releases the call
In a fix time interval, the SSP reports the SCP the number of processed calls per destination, that means the counted votes.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5656Berlin
Precounting (5) - Televoting with PrecountingPrecounting (5) - Televoting with Precounting
BEGIN (ActivateServiceFiltering)
Set Up
Alerting
Release
SSP SCP
Set Up & PA
**** Announcement ****
Internal IP
Release
Set Up
**** Announcement ****
AnnComplete
Set Up & PA
AnnComplete
Set UpBEGIN (InitialDP)
Alerting
END (RESULT: ActivateServiceFiltering)
BEGIN (ServiceFilteringResponse)
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5757Berlin
Operation: Activate Service Filtering
Semantics: The SCP requests the SSP
to adjust Service Filtering (Pre-counting) corresponding to the transmitted parameters:
SF active,
SF inactive,
modify a present SF.
Operation: Activate Service Filtering
Semantics: The SCP requests the SSP
to adjust Service Filtering (Pre-counting) corresponding to the transmitted parameters:
SF active,
SF inactive,
modify a present SF.
Arguments:filteredCallTreatment,
sFBillingChargingCharacteristics
informationToSend,
maximumNumberOfCounters
releaseCause,
filteringCharacteristics,
interval,
numberOfCalls,
filteringTimeOut,
duration,
stopTime,
filteringCriteria,
addressAndService,
serviceKey,
startTime
Arguments:filteredCallTreatment,
sFBillingChargingCharacteristics
informationToSend,
maximumNumberOfCounters
releaseCause,
filteringCharacteristics,
interval,
numberOfCalls,
filteringTimeOut,
duration,
stopTime,
filteringCriteria,
addressAndService,
serviceKey,
startTime
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5858Berlin
Operation: ServiceFilteringResponse Semantics:
Reports the actual counter values to the SCP.
Reset of the counters
Arguments:
countersValue,
counterID,
counterValue,
filteringCriteria (same as ActivateServiceFiltering)
Operation: ServiceFilteringResponse Semantics:
Reports the actual counter values to the SCP.
Reset of the counters
Arguments:
countersValue,
counterID,
counterValue,
filteringCriteria (same as ActivateServiceFiltering)
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
5959Berlin
Monitoring of dialog resources (1)Monitoring of dialog resources (1)
The dialog between the SSP and SCP is open as long as there exists a control respectively monitoring relationship between both entities. That means, the dialog is open as long as the SCP expects reports in the context of calls from the SSP.
To avoid a waste of resources (for example a report, which indicates a call end, does not arrive at the corresponding service logic), the SCP monitors all open dialogs.
The SCP sends the operation 'ActivityTest' to each instance, it has a dialog with, in a fix time interval to check the existence of the dialog at the corresponding side, that means at the SSP.
The SSP answers with 'TC_RESULT' in case of a successful test, respectively with 'TC_P_ABORT' in case of a non existing dialog.
The dialog between the SSP and SCP is open as long as there exists a control respectively monitoring relationship between both entities. That means, the dialog is open as long as the SCP expects reports in the context of calls from the SSP.
To avoid a waste of resources (for example a report, which indicates a call end, does not arrive at the corresponding service logic), the SCP monitors all open dialogs.
The SCP sends the operation 'ActivityTest' to each instance, it has a dialog with, in a fix time interval to check the existence of the dialog at the corresponding side, that means at the SSP.
The SSP answers with 'TC_RESULT' in case of a successful test, respectively with 'TC_P_ABORT' in case of a non existing dialog.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
6060Berlin
Monitoring of dialog resources (2)Monitoring of dialog resources (2)
Operation: ActivityTest Semantics:
Test of the open dialog
Arguments:
non
Result
The SCP restarts the monitoring timer.
Operation: ActivityTest Semantics:
Test of the open dialog
Arguments:
non
Result
The SCP restarts the monitoring timer.
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
6161Berlin
Monitoring of dialog resources (3)Monitoring of dialog resources (3)
BEGIN (Initial DP)BEGIN (Initial DP)Set Up
CONTINUE (CallInformationRequest, Connect)CONTINUE (CallInformationRequest, Connect)
Set UpSet Up
AlertingAlerting Set UpSet Up
ConnectConnect Connect Connect
SSP SCP
ReleaseRelease Release Release
CONTINUE (CallInformationReport)CONTINUE (CallInformationReport)
CONTINUE (ActivityTest)CONTINUE (ActivityTest)
CONTINUE (RESULT(ActivityTest))CONTINUE (RESULT(ActivityTest))
t > 30 mint > 30 min
IN_Chap_04 INAP.pptProf. Dr. Jörg Lange 2001_10
s Intelligent Network - Basics
6262Berlin
Monitoring of dialog resources (4)Monitoring of dialog resources (4)
BEGIN (Initial DP)BEGIN (Initial DP)Set Up
CONTINUE (CallInformationRequest, Connect)CONTINUE (CallInformationRequest, Connect)
Set UpSet Up
AlertingAlerting Set UpSet Up
ConnectConnect Connect Connect
SSP SCP
ReleaseRelease Release Release
CONTINUE (CallInformationReport)CONTINUE (CallInformationReport)
CONTINUE (ActivityTest)CONTINUE (ActivityTest)
P_ABORTP_ABORT
t > 30 mint > 30 minLoss
top related