Escolar Documentos
Profissional Documentos
Cultura Documentos
Page 1 of 159
Table of Content
Table of Content.............................................................................................................................................................................................................................................2 0.0 References.................................................................................................................................................................................................................................................6 0.1 Glossary.....................................................................................................................................................................................................................................................6 1.0 Introduction...............................................................................................................................................................................................................................................8 1.1Assumptions....................................................................................................................................................................................................................................8 2.0 Basic Call State Model (BCSM)..............................................................................................................................................................................................................9 1.2Originating BCSM for CS 1..........................................................................................................................................................................................................10 1.3Terminating BCSM for CS-1.........................................................................................................................................................................................................15 3.0 Trigger and Detection Point .................................................................................................................................................................................................................18 1.4Detection Point.............................................................................................................................................................................................................................18 1.5Arming Mechanism.......................................................................................................................................................................................................................19 1.6Criteria.........................................................................................................................................................................................................................................19 1.7Trigger..........................................................................................................................................................................................................................................21 1.8DP Processing..............................................................................................................................................................................................................................21 4.0 INCM Service Plane...............................................................................................................................................................................................................................23 5.0 Access Network for IN Services............................................................................................................................................................................................................26
Page 2 of 159
Page 3 of 159
Page 4 of 159
Page 5 of 159
0.0..................................................................................................References
1. ITU-T Recommendation Q.1218 Intelligent Network : Interface Recommendation for Intelligent Network 2. Intelligent Network Capability Set 1, Core Intelligent Network Application Protocol (INAP), Part 1 : Protocol Specification (ETS 300 374-1)
0.1
BCSM CAMEL CDR CS-1 CS-2 DP ETSI FSM GUI IN INAP IP ISDN ISUP ITU-T IVR MTP PC POTS PRI PSTN SCCP SCP SLP SRF SS7
Glossary
Basic Call State Model Customised Application Mobile Enhanced Logic Call Detail Record Capability Set 1 Capability Set 2 Detection Point European Telecommunications Standards Institute Finite State Machine Graphical User Interface Intelligent Network Intelligent Network Application Protocol Intelligent Peripheral Integrated Services Digital Network ISDN User Part International Telecommunications UnionTelecommunications Standardisation Sector Interactive Voice Response Message Transfer Part Point Code Plain Old Telephony Service Primary Rate Interface Public Switched Telephone Network Signaling Connection Control Part Service Control Point Service Logic Program Specialised Resource Function Signaling System 7 (also known as CS-Common Signaling)
Page 6 of 159
Page 7 of 159
1.0 Introduction
This document attempts to capture technical information related to CS-1 IN services implementation for easy reference of the user. It serves to provide an overall understanding about the SSP capabilities needed, INAP protocol, and possible ways of implementing the various CS-1 IN services.
1.1 Assumptions
1. The call flows shown in the document assume Fixed service being offered to the subscribers, and not necessarily the Wireless Local Loop service.
Page 8 of 159
Page 9 of 159
Page 10 of 159
O_Abandon
6. O_Exception
10
rig. Attempt_Authorized
2. Collect_Info.
Collected_Info.
3. Analyse_Info.
Analysed_Info. 4 Route_Select_Failure
7 9 O_Disconnect 8 O_Mid_Call
O_Answer
5 O_Called_Party_Busy 6 O_No_Answer
T1136230-91/d005
5. O_Active
Page 11 of 159
Page 12 of 159
Routing_&_Alerting PIC O_Answer DP O_Midcall DP O_Disconnect DP O_Active PIC _Active PIC O_Null_&_Authorize_Origination_Attempt PIC Collect_Information PIC Analyse Information PIC Routing_&_Alerting PIC O_Abandoned DP O_Null_&_Authorize_Origination_Attempt PIC Collect_Information PIC O_Null_&_Authorize_Origination_Attempt PIC Origination_Attempt_Authorized DP O_Exception O_Abandon DP Collected_Information DP Analyse_Information PIC O_Exception O_Abandon DP Analysed_Information DP Routing & Alerting PIC Route_Select_Failure DP O_called_Party_Busy DP O_No_Answer DP O_Answer DP O_Abandon DP Analyze_Information PIC O_Exception
Page 13 of 159
O_Active PIC
O_Exception
O_Null_&_Authorize_Origination_Attempt PIC
Page 14 of 159
1 1 . T _ E x c e p t io n
7 . T _ N u ll & A u t h o r iz e T e r m in a t io n _ A t t e m p t
T e r m . _ A tt e m p t_ A u th o r iz e d
12
18
13
T _ C a lle d _ P a r t y _ B u s y
8 . S e l e c t _ F a c il i t y & P r e s e n t _ C a l l
14
T _N o_A nsw er
9 . T _ A le r t in g
15
T _A nsw er
1 0 . T _ A c tiv e 16 T _ M id _ C a ll T r a n s it io n D e t e c t io n P o in t ( D P ) P o in t In C a ll ( P I C )
17
T _ D is c o n n e c t
T 1 1 3 6 2 4 0 -9 1 /d 0 0 6
F IG U R E 4 -4 /Q .1 2 1 4 T e r m in a tin g B C S M fo r C S -1
Page 15 of 159
Page 16 of 159
T_Exception
Page 17 of 159
A DP can be armed in order to notify the SCF that the DP was encountered, and potentially to allow the SCF to influence subsequent handling of the call. If the DP is not armed, the processing entity continues the processing without SCF involvement. Table below shows the types of DP identified.
Page 18 of 159
1.6 Criteria
Criterias are the conditions that must be met in order for the SSF to request instructions from the SCF. For TDPs, Detection Point Criteria must be met before the SSP can notify SCP that the DP was encountered. Table below shows the various possible DP criteria that can be assigned at the SSP: Legend X Applicable Not applicable
Page 19 of 159
1 X
X X X O
2 O X X X X
X O O X O
3 O X X X X
X X X X O X O X O
4 O O O O O
O X X O O O O X O
5 O O O O O
O X X O O O O X O
6 O O O O O
O X O O O O X O
7 O O O O O
O X X O O O O X O
8 O O O O O
O X X O O O O X O
9 O O O O O
O X X O O O O X O
1 0 O O O O O
O X X O O O O X O
11 X
X O X
12 O
X O O X
1 3 O
X O O X O
14 O
X X O O X O
1 5 O
X X O O X O
16 O
X X O O X O
1 7 O
X X O O X O
1 8
Facility Information (Note 2) Feature Activation (Note 3) Cause Specific abbreviated dialling string (Note 1) Specific Calling Party Number (Note 4) Nature of Address Bearer Capability (Note 5) Trigger Assigned Specific B-channel Identifier
NOTES 1. Same type of trigger requiring analysis of a specific number of received digits. The analysis can be based on the complete number of received digits or can be based on a predefined number of digits starting from the most significant digit of the received information. The inclusion for these criteria for DP 2 is due to the change in the originating BCSM. 2. A match on the Facility Information Element contained in a signalling message as defined in DSS1 and ISUP. 3. In a local exchange only. The BCSM has to analyse (if facility is allowed, stored as Class of Service attribute) the received information and has to initiate an IN trigger if required. A feature activation/indication can be available at DP 1-10 in the originating BCSM for a party served by an ISDN interface and can be available at DP 8 in the originating BCSM for a party served by a non-ISDN line. A feature activation/indication can be available at DP 14-18 in the terminating BCSM for a party served by an ISDN interface and can be available at DP 16 in the terminating BCSM for a party served by a non-ISDN line.
Page 20 of 159
If a criteria is marked with an X for a Detection Point, then this means that a conditional TDP which is armed at the Detection Point may require the criteria as listed in the table to be satisfied before informing the SCF that the TDP was encountered, e.g. a conditional TDP at DP 1 may require the class of service criteria to be satisfied before the SCF is informed that the TDP was encountered. If a criteria is marked with an O for a Detection Point, then this means that it is implementation dependent if the criteria specific information is still present at that DP because not all suppliers may retain this information for the duration of the call/attempt. If the information is still present, the treatment is the same as a criteria marked with a X.
1.7 Trigger
The trigger item is defined as a single set of DP criteria and the associated information that an SSF/CCF uses to determine if the criteria is met and how to process the trigger. The trigger item consists of trigger type, DP criteria, and the SCF routing information. The trigger items are assigned to users by management process. An SSF should use the SCF routing information to format and route the messages to the appropriate SCF application. The SCF may use existing MTP/SCCP capabilities to route to the SCF.
1.8 DP Processing
With reference to ITU-T Q1214 Section 4.2.2.7, DP processing should be performed according to the following rules: Rule 1: At any DP, a specific trigger condition can only trigger one service logic program instance (SLPI) at a time. Rule 2: At any DP, processing of notifications EDP-N and TDP-N has higher priority than processing of requests EDP-R and TDP-R. If several notifications exist, EDP-R and TDP-R are processed when all notifications have been processed. Rule 3: If a DP is both armed as EDP and TDP, then the EDP processing has higher priority than the TDP processing since the EDP has been armed in an already existing SSF-SCF relationship.
Page 21 of 159
Page 22 of 159
CS-1 supports only Type A services like: 1. Number Translation, providing flexible routing and numbering: Abbreviated Dialing Call forwarding Hunting lists Freephone Premium Rate Universal Access Number etc 1. 2. Alternate Billing, providing flexible charging Credit Card Calling Account Card calling Split charging Premium Rate Etc Screening, providing flexible restriction Originating Screening Terminating Screening Security Screening, to grant network access
Page 23 of 159
3.
Others, providing complementary capabilities Televoting VPN Call Completion to Busy Subscriber (Automatic Call Back) Etc
CS-1 defines a set of service features: 1. Numbering : Abbreviated dialing, Private Numbering, One Number 2. Routing : Call forwarding, Time dependant, Origin dependant or A location dependant, Follow me diversion 3. Charging 4. Access/Validation 5. Restriction : Call Gapping, Closed user group, Screening(originating,terminating) 6. Customisation : Profile management, Custom announcement/ringtone 7. User Interaction 8. Others : Call queuing, Call Hold, Call Completion to Busy Subscriber (Automatic Call Back) CS-2 supports only Type A services like: 1. Internetwork Services Internetwork Freephone, the served user may have several phones to be reached with a single number, regardless of the serving network Internetwork Televoting, the calling party can be in another network Global Virtual Network Services, VPN over multiple network Internetwork Rate indicator Fwd/Bwd, across multiple network, ability to show the cost of the call in forward or backward direction Inetrnetwork card validation 2. Mobility Services, Non Call Related services
Page 24 of 159
Page 25 of 159
Fixed Network SCP (INAP) INAP INAP SRF ILT/SSP Other Mobile Service Provider Network
ISUP VMS
E1(V5.2)
DIU
Page 26 of 159
Page 27 of 159
1.11 Charging
Offline-charging method is used whereby the CDRs generated at the SSP will be processed to bill both the service users and service customers in the manner below: 1. Service users free of charge. This can be done based on the called party number (1600 XXXX XXX) in the CDR. 2. Service customer monthly charge and service usage charge. Service usage charge can be done based on the called party number (1600 XXXX XXX), cause value and the duration of the call.
Page 28 of 159
1.12 Scenarios
6.1.1 Scenario 1: Unsuccessful TollFree Call (Barring based on Service Providers predefined incoming Blacklist number at the service level)
Description:
Usually, the freephone number is accessible from all types of phones from any operator. However, sometimes there might be a need to block access to freephone service from a certain type of phones, eg. payphone or operator assisted calls. These kind of calls can be differentiated because they have specific value in calling party category field of the ISUP IAM message. The service logic should have the functionality to allow the network operator to defined a certain list of calling party number or calling party category that is barred from accessing the operators freephone service. When the caller makes the call, he hears an invalid tone played by the switch indicating that it is not a valid call. This is achieved by the SCP by sending a INAP ReleaseCall message to the SSP with certain cause value. The default value of the cause code is Normal Unspecified (31) which corresponds to a 3 beep tone. There is no charge incurred for the call, both for the service user and the service customer.
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 29 of 159
A Party
O-SSP
OSCP
T-SCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String or Prefix = 1600 initiate a Freephone call (eg. dial 1600 123456) BeginMessage {InitialDP (serviceKey, callingPartyNumber, calledPartyNumber, callingPartyCategory)}
Based on serviceKey, freepone service logic is invoked. Verify callingPartyNumber or callingPartyCategory is in Service providers incoming blacklist
Page 30 of 159
6.1.2 Scenario 2: Unsuccessful TollFree Call (Barring based on Service Customers predefined incoming blacklist number)
Description:
Each service customer has its own group of desired/privilege customers and undesired customers. The service customer may wish to have different call routing treatment for different kinds of caller. For the undesired callers, they may want to play an announcement to block the actual routing of the call to its destination. Therefore, the service logic should have the functionality to allow each of the service customer to define its own list of incoming blacklist numbers. When the caller makes the call, the service logic recognizes the calling partys number and plays an announcement to the caller, eg. Sorry, you are not allowed to call this number There is no charge incurred for the caller (or service user), but the service customer needs to pay for the duration of the announcement call as the call is considered successful call with normal call completion (based on cause code).
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 31 of 159
A Party
O-SSP
O-SCP
T-SCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String or Prefix = 1600 initiate a Freephone call (eg. dial 1600 123456) BeginMessage {InitialDP (serviceKey, callingPartyNumber, calledPartyNumber, callingPartyCategory)} ContinueMessage { RequestReportBCSMEvent (oDisconnect) ConnectToResource (resourceAddress), PlayAnnouncement (informationToSend.inbandinfo.messageID.eleme ntaryMessageID)}
Based on serviceKey, freepone service logic is invoked. Verify that the callingPartyNumber or callingPartyCategory is not in Service providers incoming blacklist The service logic search for the corresponding service customer record in DataBase based on calledPartyNumber Verify that the callingPartyNumber is in Service subscribers incoming blacklist
DP: oDisconnect TT: oDisconnect ContinueMessage {ReportBCSMEvent(oDisconnec t)} ContinueMessage { SpecialisedResourceReport (} ENDMessage { DisconnectForwardConnection (),ReleaseCall}
At the end of announcement, the SCP instructs the SSP to end the call and disconnect the connection with the SRF. If the caller hangs up before the end of announcement, the SCP instruct s SSP to disconnect the connection with the SRF.
Page 32 of 159
6.1.3 Scenario 3: Unsuccessful TollFree Call (routing to announcement based on Service Customers predefined time dependant routing at the service customers level)
Description:
Dependant on the individual service customer who owns the particular freephone number, the routing of the calls, when to play announcement or route to which destination number varies. Usually, a service customer will need to play different Welcome announcement depending on the time of the call. When it is non-office hour, the service customer will select a pre-recorded Out of office hour announcement to request the caller to call on the next day. Therefore, the service logic should have the functionality to allow each of the service customer to define its own non-office hour and announcement. When the caller makes the call, the service logic recognizes that it is during the non-office hour of that particular freephone service customer and plays an announcement to the caller, eg. Thank you for calling. Our office is closed. Please call again on the next working day. There is no charge incurred for the caller (or service user), but the service customer needs to pay for the duration of the call announcement as the call is considered successful call with normal call completion (based on cause code).
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 33 of 159
A Party
O-SSP
O-SCP
T-SCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String or Prefix = 1600 initiate a Freephone call (eg. dial 1600 123456) BeginMessage {InitialDP (serviceKey, callingPartyNumber, calledPartyNumber, callingPartyCategory)} ContinueMessage { RequestReportBCSMEvent (oDisconnect) ConnectToResource (resourceAddress), PlayAnnouncement (informationToSend.inbandinfo.messageID.eleme ntaryMessageID)}
Based on serviceKey, freepone service logic is invoked. Verify that the callingPartyNumber or callingPartyCategory is not in Service providers incoming blacklist The service logic search for the corresponding service customer record in DataBase based on calledPartyNumber Verify that the callingPartyNumber is not in Service subscribers incoming blacklist Verify that the time of the call is not during office hour as defined by the service subscriber Play Non-office hour announcement
DP: oDisconnect TT: oDisconnect ContinueMessage {ReportBCSMEvent(oDisconnec t)} ContinueMessage { SpecialisedResourceReport (} ENDMessage { DisconnectForwardConnection (),ReleaseCall}
At the end of announcement, the SCP instructs the SSP to end the call and disconnect the connection with the SRF. If the caller hangs up before the end of announcement, the SCP instruct s SSP to disconnect the connection with the SRF.
Page 34 of 159
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 35 of 159
A Party
O-SSP
DP: Collect_Information or AnalysedInformation TT: Specific Digit String = 1600
OSCP
T-SCP
B Party
ContinueMessage { RequestReportBCSMEvent (bcsmEvent), Connect (destinationRoutingAddress)} DP: O_CalledPartyBusy TT: O_CalledPartyBusy; DP: O_NoAnswer TT: O_NoAnswer ContinueMessage {EventReportBCSM(oCalledPartyBusy/oNo Asnwer)} ContinueMessage { Connect (destinationRoutingAddress)}
Based on serviceKey, freepone service logic is invoked. Verify that the callingPartyNumber or callingPartyCategory is not in Service providers incoming blacklist The service logic search for the corresponding service subscribers record in DataBase based on calledPartyNumber Verify that the callingPartyNumber is not in Service subscribers incoming blacklist Verify that the time of the call is during office hour as defined by the service subscriber Translates the service number to actual destination number based on origin dependent and time dependent routing The intended number is selected based on call distribution mechanism based on key quota/ percentage/nth call Monitor call for busy / no answer/overflow/answer
call setup completed and voice path established DP: O_Answer TT: O_Answer ENDMessage {EventReportBCSM(oAnswer)}
Page 36 of 159
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 37 of 159
A Party
O-SSP
OSCP
T-SCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String or Prefix = 1600 BeginMessage {InitialDP (serviceKey, callingPartyNumber, callingPartyCategorycalledPartyNumber)}
ContinueMessage { ConnectToResource (resourceAddress), PromptAndCollectUserInformation Request (digits), RequestReportBCSMEvent} Repeat Prompt And Collect n times if necessary
Based on serviceKey, freepone service logic is invoked. Verify that the callingPartyNumber or callingPartyCategory is not in Service providers incoming blacklist The service logic search for the corresponding service subscribers record in DataBase based on calledPartyNumber Verify that the callingPartyNumber is not in Service subscribers incoming blacklist Verify that the time of the call is during office hour as defined by the service subscriber Play Welcome Announcement
Page 38 of 159
A Party
O-SSP
OSCP
T-SCP
B Party
DP: O_CalledPartyBusy TT : O_CalledPartyBusy; DP: O_No_Answer TT : O_No_Answer ContinueMessage {ReportEventBCSM(oCalledPartyBusy or oNoAswer)} ContinueMessage { Connect (destinationRoutingAddress)} call setup completed and voice path established DP: O_Answer TT : O_Answer ContinueMessage {ReportEventBCSM(oAswer)} Start Hunting/Call Forward to the next destination number defined
Page 39 of 159
Page 40 of 159
Page 41 of 159
1.15 Scenarios
8.1.1 Scenario 1 : Unsuccessful Premium Rate Call (Barring based on Service Providers predefined incoming Blacklist number at the service level)
Description:
Usually, the freephone number is accessible from all types of phones from any operator. However, sometimes there might be a need to block access to freephone service from a certain type of phones, eg. payphone or operator assisted calls. These kind of calls can be differentiated because they have specific value in calling party category field of the ISUP IAM message. The service logic should have the functionality to allow the network operator to defined a certain list of calling party number or calling party category that is barred from accessing the operators freephone service. When the caller makes the call, he hears an invalid tone played by the switch indicating that it is not a valid call. This is achieved by the SCP by sending a INAP ReleaseCall message to the SSP with certain cause value. The default value of the cause code is Normal Unspecified (31) which corresponds to a 3 beep tone. There is no charge incurred for the call, both for the service user and the service customer.
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 42 of 159
A Party
O-SSP
OSCP
T-SCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String or Prefix = 1600 initiate a Freephone call (eg. dial 1600 123456) BeginMessage {InitialDP (serviceKey, callingPartyNumber, calledPartyNumber, callingPartyCategory)}
Based on serviceKey, freepone service logic is invoked. Verify callingPartyNumber or callingPartyCategory is in Service providers incoming blacklist
Page 43 of 159
8.1.2 Scenario 2: Unsuccessful Premium Rate Call (Barring based on Service Customers predefined incoming blacklist number)
Description:
Each service customer has its own group of desired/privilege customers and undesired customers. The service customer may wish to have different call routing treatment for different kinds of caller. For the undesired callers, they may want to play an announcement to block the actual routing of the call to its destination. Therefore, the service logic should have the functionality to allow each of the service customer to define its own list of incoming blacklist numbers. When the caller makes the call, the service logic recognizes the calling partys number and plays an announcement to the caller, eg. Sorry, you are not allowed to call this number There is no charge incurred for the caller (or service user), but the service customer needs to pay for the duration of the announcement call as the call is considered successful call with normal call completion (based on cause code).
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 44 of 159
A Party
O-SSP
O-SCP
T-SCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String or Prefix = 1600 initiate a Freephone call (eg. dial 1600 123456) BeginMessage {InitialDP (serviceKey, callingPartyNumber, calledPartyNumber, callingPartyCategory)} ContinueMessage { RequestReportBCSMEvent (oDisconnect) ConnectToResource (resourceAddress), PlayAnnouncement (informationToSend.inbandinfo.messageID.eleme ntaryMessageID)}
Based on serviceKey, freepone service logic is invoked. Verify that the callingPartyNumber or callingPartyCategory is not in Service providers incoming blacklist The service logic search for the corresponding service customer record in DataBase based on calledPartyNumber Verify that the callingPartyNumber is in Service subscribers incoming blacklist
DP: oDisconnect TT: oDisconnect ContinueMessage {ReportBCSMEvent(oDisconnec t)} ContinueMessage { SpecialisedResourceReport (} ENDMessage { DisconnectForwardConnection (),ReleaseCall}
At the end of announcement, the SCP instructs the SSP to end the call and disconnect the connection with the SRF. If the caller hangs up before the end of announcement, the SCP instruct s SSP to disconnect the connection with the SRF.
Page 45 of 159
8.1.3 Scenario 3: Unsuccessful Premium Rate Call (routing to announcement based on Service Customers predefined time dependant routing at the service customers level)
Description:
Dependant on the individual service customer who owns the particular freephone number, the routing of the calls, when to play announcement or route to which destination number varies. Usually, a service customer will need to play different Welcome announcement depending on the time of the call. When it is non-office hour, the service customer will select a pre-recorded Out of office hour announcement to request the caller to call on the next day. Therefore, the service logic should have the functionality to allow each of the service customer to define its own non-office hour and announcement. When the caller makes the call, the service logic recognizes that it is during the non-office hour of that particular freephone service customer and plays an announcement to the caller, eg. Thank you for calling. Our office is closed. Please call again on the next working day. There is no charge incurred for the caller (or service user), but the service customer needs to pay for the duration of the call announcement as the call is considered successful call with normal call completion (based on cause code).
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 46 of 159
A Party
O-SSP
O-SCP
T-SCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String or Prefix = 1600 initiate a Freephone call (eg. dial 1600 123456) BeginMessage {InitialDP (serviceKey, callingPartyNumber, calledPartyNumber, callingPartyCategory)} ContinueMessage { RequestReportBCSMEvent (oDisconnect) ConnectToResource (resourceAddress), PlayAnnouncement (informationToSend.inbandinfo.messageID.eleme ntaryMessageID)}
Based on serviceKey, freepone service logic is invoked. Verify that the callingPartyNumber or callingPartyCategory is not in Service providers incoming blacklist The service logic search for the corresponding service customer record in DataBase based on calledPartyNumber Verify that the callingPartyNumber is not in Service subscribers incoming blacklist Verify that the time of the call is not during office hour as defined by the service subscriber Play Non-office hour announcement
DP: oDisconnect TT: oDisconnect ContinueMessage {ReportBCSMEvent(oDisconnec t)} ContinueMessage { SpecialisedResourceReport (} ENDMessage { DisconnectForwardConnection (),ReleaseCall}
At the end of announcement, the SCP instructs the SSP to end the call and disconnect the connection with the SRF. If the caller hangs up before the end of announcement, the SCP instruct s SSP to disconnect the connection with the SRF.
Page 47 of 159
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 48 of 159
A Party
O-SSP
DP: Collect_Information or AnalysedInformation TT: Specific Digit String = 1600
OSCP
T-SCP
B Party
ContinueMessage { RequestReportBCSMEvent (bcsmEvent), Connect (destinationRoutingAddress)} DP: O_CalledPartyBusy TT: O_CalledPartyBusy; DP: O_NoAnswer TT: O_NoAnswer ContinueMessage {EventReportBCSM(oCalledPartyBusy/oNo Asnwer)} ContinueMessage { Connect (destinationRoutingAddress)}
Based on serviceKey, freepone service logic is invoked. Verify that the callingPartyNumber or callingPartyCategory is not in Service providers incoming blacklist The service logic search for the corresponding service subscribers record in DataBase based on calledPartyNumber Verify that the callingPartyNumber is not in Service subscribers incoming blacklist Verify that the time of the call is during office hour as defined by the service subscriber Translates the service number to actual destination number based on origin dependent and time dependent routing The intended number is selected based on call distribution mechanism based on key quota/ percentage/nth call Monitor call for busy / no answer/overflow/answer
call setup completed and voice path established DP: O_Answer TT: O_Answer ENDMessage {EventReportBCSM(oAnswer)}
Page 49 of 159
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 50 of 159
A Party
O-SSP
OSCP
T-SCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String or Prefix = 1600 BeginMessage {InitialDP (serviceKey, callingPartyNumber, callingPartyCategorycalledPartyNumber)}
ContinueMessage { ConnectToResource (resourceAddress), PromptAndCollectUserInformation Request (digits), RequestReportBCSMEvent} Repeat Prompt And Collect n times if necessary
Based on serviceKey, freepone service logic is invoked. Verify that the callingPartyNumber or callingPartyCategory is not in Service providers incoming blacklist The service logic search for the corresponding service subscribers record in DataBase based on calledPartyNumber Verify that the callingPartyNumber is not in Service subscribers incoming blacklist Verify that the time of the call is during office hour as defined by the service subscriber Play Welcome Announcement
Page 51 of 159
A Party
O-SSP
OSCP
T-SCP
B Party
DP: O_CalledPartyBusy TT : O_CalledPartyBusy; DP: O_No_Answer TT : O_No_Answer ContinueMessage {ReportEventBCSM(oCalledPartyBusy or oNoAswer)} ContinueMessage { Connect (destinationRoutingAddress)} call setup completed and voice path established DP: O_Answer TT : O_Answer ContinueMessage {ReportEventBCSM(oAswer)} Start Hunting/Call Forward to the next destination number defined
Page 52 of 159
Page 53 of 159
Page 54 of 159
1.18 Scenarios
9.1.1 Scenario 1 : Successful Virtual Card Call (Point to point card)
Description:
Sometimes, for promotional purposes, the corporate customers will want to issue to the general public or their customers calling cards with predefined denominations with predefined destination number (eg. the corporate customers own hotline or CSR). When the caller dials the VCC service access number, and enters card number / PIN (if CLI is not recognized), the service logic in SCP automatically pulls out the destination number predefined by the corporate customer and connect the call to this number. The caller will not be prompt to enter his/her desired destination. In fact, the caller will not be able to make calls to other destination besides the predefined number.
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 55 of 159
A Party
OSSP
OSCP
TSSP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String = 31822 BeginMessage {InitialDP (serviceKey, callingPartyNumber,calledPartyNumber) }
ContinueMessage { ConnectToResource (resourceAddress.none), PromptAndCollectUserInformation (InformationToSend.inbandinfo.elementaryMe ssgge.MessageID, CollectedInfo.collectedDigits.maximumNbOfDigits)} Establish bearer connection to IP Start announcement Repeat Prompt And Collect n times if necessary A Party inputs 12-digit VCC card number
Play the corresponding Welcome announcement specified for VCC service Prompt user for card number
Page 56 of 159
A Party
OSSP
OSCP
TSSP
B Party
Establish bearer connection to IP Start announcement ContinueMessage { SpecialisedResourceReport} ContinueMessage { PlayAnnouncement (InformationToSend.inbandinfo.elementaryMess gge.MessageIDs)}
Validate card number Check the status of the card (Active or not) If card is active, check balance available and play annoncement notifying user of the remaining balance Check if there is already an ongoing call. If yes, validate time gap between simultaneous calls. Check if there is any service provider /customer defined promotional / marketing messages. Play the promotional message is there is any.
Recognizes the card is a Point to point card : Based on the tariff rate for the destination number, play announcement to indicate the duration allowed for the call.
ContinueMessage { SpecialisedResourceReport}
Dynamically set EDP-R O_Called_Party_Busy O_No_Answer Dynamically set EDP-N O_Answer O_Disconnect
Recognizes the card is a Point to point card : Allocate a threshold to the SSP indicating the time allowed for the call to proceed before reporting SCP the charging report. Connect the call to the predefined destination number for the card.
Page 57 of 159
A Party
OSSP
OSCP
TSSP
B Party
call setup completed and voice path established DP: O_Answer TT : O_Answer ContinueMessage { EventReportBCSM(oAnswer)}
Start the outgoing call rating for this VCC call continue monitoring the call
ContinueMessage {ApplyChargingReport()}
When the threshold is used up, SSP reports that the call has progressed for the allowed time in ApplyChargingRequest
ContinueMessage {ApplyCharging()}
Allocate another threshold to the SSP (if balance is sufficient). continue monitoring the call
Page 58 of 159
OSSP
ContinueMessage {ApplyChargingReport()}
When the threshold is used up, SSP reports that the call has progressed for the allowed time in ApplyChargingRequest
SCP realizes that there is no more balance and play announcement to inform caller that balance is zero.
Page 59 of 159
9.1.3
OSSP
DP: oDisconnect TT : oDisconnect
OSCP
TSSP
B Party
ContinueMessage { EventReportBCSM)}
Stop rating for the call. Play announcement to prompt user for follow-on call/last number redial or speak to CSR.
ContinueMessage { ConnectToResource (resourceAddress.none), PromptAndCollectUserInformation (InformationToSend.inbandinfo.elementaryMe ssgge.MessageID, CollectedInfo.collectedDigits.maximumNbOfDigits)} Establish bearer connection to IP Start announcement Repeat Prompt And Collect n times if necessary A Party inputs 12-digit VCC card number ContinueMessage { ReturnResult (PromptAndCollectUserInformation, digitsResponse)} Page 60 of 159
Validate that nth call limit is not exceeded Check balance available and play annoncement notifying user of the remaining balance Recognizes the card is a Point to point card, connect the call to the predefined destination number for the card.
9.1.5 Scenario 2 : Successful Virtual Card Call (for the first time)
Description:
Because the ACC card can be purchased from the counter and there is no subscription needed, the service provider does not have the details or profile of the user. In order for the user to specify his/her preferred language for the announcement, the user will be prompt a language selection menu upon successful verification of the card number. Afterwhich, the user can proceed to make outgoing calls if the card balance is sufficient.
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 61 of 159
9.1.6 Scenario 3 : Successful Subsequent Virtual Card Call (destination number entered after Card validation)
Description: Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 62 of 159
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 63 of 159
Page 64 of 159
Page 65 of 159
1.21 Scenarios
10.1.1Scenario 1 : Successful Account Card Call (Point to point card)
Description:
The example of the application of this card is a parent giving the point to point card to the child who is studying overseas. This way, the child can use the card to call home while the parents will bear the call charges as according to the VCC monthly bill statement. By indicating a predefined destination number (which is the home number), the parent is able to prevent the child from abusing the cards to make calls to other destinations unnecessarily. When the caller dials the ACC service access number, and enters card number / PIN (if CLI is not recognized), the service logic in SCP automatically pulls out the destination number predefined by the customer and connect the call to this number. The caller will not be prompt to enter his/her desired destination. In fact, the caller will not be able to make calls to other destination besides the predefined number.
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 66 of 159
A Party
OSSP
OSCP
TSCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String / CalledPartyNumber = 31122 BeginMessage {InitialDP (serviceKey, callingPartyNumber,calledPartyNumber)} ContinueMessage { FurnishChargingInformation (), ConnectToResource (resourceAddress.none), PromptAndCollectUserInformation (InformationToSend.inbandinfo CollectedInfo.collectedDigits.maximumNbOfDigits)} Repeat Prompt And Collect n times if necessary
Verify that CLI is not in the database Play the corresponding Welcome announcement specified for VCC service Prompt user for card number
A Party inputs 12-digit ACC card number ContinueMessage { ReturnResult (PromptAndCollectUserInformation, digitsResponse)} ContinueMessage {PromptAndCollectUserInformation () Repeat Prompt And Collect n times if necessary A Party inputs 4-digit ACC pin number ContinueMessage { ReturnResult (PromptAndCollectUserInformation, digitsResponse)}
Validate card number Prompt user for PIN number (message is played based on the language selected for the card type or class of service.
Start announcement
Authenticate the card number and pin entered (System logs all the wrong PIN attempt) Check the status of the card (Active or not). Check if there is already an ongoing call. If yes, validate time
Page 67 of 159
A Party
Dynamically set EDP-R O_Called_Party_Busy O_No_Answer Dynamically set EDP-N O_Answer O_Disconnect
OSSP
ContinueMessage {DisconnectForwadConenction, Connect (), RequestReportBCSMEvent}
OSCP
TSCP
B Party
Pick Up
call setup completed and voice path established DP: O_Answer TT : O_Answer ContinueMessage { ReportEventBCSM)}
Starting (Originating)
Rating
Start the outgoing call rating timer continue monitoring the call
Stop rating for the call. Play announcement to prompt user for follow-on call/last number redial or speak to CSR.
Page 68 of 159
10.1.2Scenario 2 : Successful Account Card Call (destination number entered after PIN verification)
Description: Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 69 of 159
A Party
OSSP
OSCP
TSCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String / CalledPartyNumber = 31122 BeginMessage {InitialDP (serviceKey, callingPartyNumber,calledPartyNumber) } ContinueMessage { FurnishChargingInformation (), ConnectToResource (resourceAddress.none), PromptAndCollectUserInformation (InformationToSend.inbandinfo CollectedInfo.collectedDigits.maximumNbOfDigits) } Repeat Prompt And Collect n times if necessary
Verify that CLI is not in the database Play the corresponding Welcome announcement specified for VCC service Prompt user for card number
ContinueMessage { ReturnResult (PromptAndCollectUserInformation, digitsResponse)} ContinueMessage {PromptAndCollectUserInformation () Repeat Prompt And Collect n times if necessary
Validate card number Prompt user for PIN number (message is played based on the language selected for the card type or class of service
Start announcement
Page 70 of 159
A Party
OSSP
OSCP
TSCP
B Party
ContinueMessage { FurnishChargingInformation (), ConnectToResource (resourceAddress), PlayAnnouncement (InformationToSend)} Start announcement ContinueMessage {SpecialisedResourceReport ()
Authenticate the card number and pin entered Check the status of the card (Active or not) If card is active, check balance available and play annoncement notifying user of the remaining balance Check if there is any service provider defined promotional/Marketing message. If yes, play promotional announcement. After that, Prompt user to enter destination number
ContinueMessage { FurnishChargingInformation (), PromptAndCollectUserInformation (InformationToSend)} Repeat Prompt And Collect n times if necessary A Party inputs destination number
Validate destination number Check White/BlackList (w.r.t.
Dynamically set EDP-R O_Called_Party_Busy O_No_Answer Dynamically set EDP-N O_Answer O_Disconnect
calling as well as called number) On Class of Service (Operator defined) On individual account/subscribers (Subscriber defined)
Page 71 of 159
A Party
OSSP
OSCP
TSCP
B Party
call setup completed and voice path established DP: O_Answer TT : O_Answer ContinueMessage { EventReportBCSM)} Starting (Originating) Rating
Pick Up
Start the outgoing call rating timer continue monitoring the call
Stop rating for the call. Play announcement to prompt user for follow-on call/last number redial or speak to CSR.
Page 72 of 159
10.1.3Scenario 3 : Successful Account Card Call (destination number entered through CLI recognition)
Description: Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 73 of 159
A Party
OSSP
OSCP
TSCP
B Party
DP: Collect_Information or AnalysedInformation TT: Specific Digit String / CalledPartyNumber = 31122 BeginMessage {InitialDP (serviceKey, callingPartyNumber,calledPartyNumber)} ContinueMessage { FurnishChargingInformation (), ConnectToResource (resourceAddress.none), PromptAndCollectUserInformation (InformationToSend.inbandinfo CollectedInfo.collectedDigits.maximumNbOfDigits)} Repeat Prompt And Collect n times if necessary
Verify that CLI is in the database Search for the corresponding customer record in the Database Verify that the card number corresponding to the CLI is active Play the corresponding Welcome announcement in the language specified by the subscriber Prompt user for PIN number
Authenticate the card number and pin entered Check the status of the card (Active or not) If card is active, check balance available and play annoncement notifying user of the remaining balance Prompt user to enter destination number
Page 74 of 159
A Party
OSSP
OSCP
TSCP
B Party
ContinueMessage { FurnishChargingInformation (), ConnectToResource (resourceAddress), PlayAnnouncement (InformationToSend)} Start announcement ContinueMessage {SpecialisedResourceReport ()
Authenticate the card number and pin entered Check the status of the card (Active or not) If card is active, check balance available and play annoncement notifying user of the remaining balance Check if there is any service provider defined promotional/Marketing message. If yes, play promotional announcement. After that, Prompt user to enter destination number
ContinueMessage { FurnishChargingInformation (), PromptAndCollectUserInformation (InformationToSend)} Repeat Prompt And Collect n times if necessary A Party inputs destination number
Validate destination number Check White/BlackList (w.r.t.
Dynamically set EDP-R O_Called_Party_Busy O_No_Answer Dynamically set EDP-N O_Answer O_Disconnect
calling as well as called number) On Class of Service (Operator defined) On individual account/subscribers (Subscriber defined)
Page 75 of 159
A Party
OSSP
OSCP
TSCP
B Party
call setup completed and voice path established DP: O_Answer TT : O_Answer ContinueMessage { EventReportBCSM)} Starting (Originating) Rating
Pick Up
Start the outgoing call rating timer continue monitoring the call
Stop rating for the call. Play announcement to prompt user for follow-on call/last number redial or speak to CSR.
Page 76 of 159
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 77 of 159
Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 78 of 159
A Party
OSSP
OSCP
TSCP
DP: Collect_Information or AnalysedInformation TT: Specific Digit String / CalledPartyNumber = 31122 BeginMessage {InitialDP (serviceKey, callingPartyNumber,calledPartyNumber)} ContinueMessage { FurnishChargingInformation (), ConnectToResource (resourceAddress.none), PromptAndCollectUserInformation (InformationToSend.inbandinfo CollectedInfo.collectedDigits.maximumNbOfDigits)} Repeat Prompt And Collect n times if necessary
Verify that CLI is not in the database Play the corresponding Welcome announcement in the languages specified ACC (there exists a choice for feature selection)
Authenticate the card number and pin entered Check the status of the card (Active or not) If card is active, check balance available and play annoncement notifying user of the remaining balance Prompt user to enter destination number
Page 79 of 159
Page 80 of 159
Page 81 of 159
1.24 Scenarios
11.1.1Scenario 1 : Successful VPN Call (OnNet) through Authentication on CLI
Description: Call Flow:
The following diagram shows the IN call flow for this scenario.
Page 82 of 159
Page 83 of 159
Page 84 of 159
Page 85 of 159
Page 86 of 159
Page 87 of 159
Page 88 of 159
Page 89 of 159
Activity Test
T at
1- 10 sec
3 sec
AnalyseInformation AnalysedInformation Apply Charging Apply Charging Report Assist Request Instruction Call Information Report Call Information Request Cancel CancelStatusReportRequest Collected Information Collect Information Connect Connect To Resource Continue
T ai T adi Tac Tacr T ari T cirp Tcirq T can T csr Tcdi T ci T con T ctr T cue
For future study 1 10 sec 1 10 sec 1 10 sec 1 10 sec 1 10 sec 1- 10 sec For future study For future study 1 60 sec 1 10 sec 1 10 sec 1 10 sec
Not Available 3 sec 3 sec Not Applicable Not Available 3 sec 10 sec Not Available Not Available 3 sec 3 sec 3 sec Not Available SCP or SMP SCP or SMP SCP or SMP SCP or SMP SSP SCP or SMP SCP or SMP
Page 90 of 159
Page 91 of 159
Page 92 of 159
Page 93 of 159
Page 94 of 159
2 7. 2 8. 2 9.
46 43 49
2 4 4
14.1.1ActivateServiceFiltering
This message is used by SCF to instruct the SSF to deal with requests for a specific service (without request for instructions to the SCF) and to count each specific attempt. The count of filtered calls will be returned to the SCF after a special internal.
ActivateServiceFiltering (ASF)
Optional/ Mandatory M
Desired Field
Value Description This parameter specifies how filtered calls are treated. It includes information about announcement to be played, charging approach, number of counters to be used and the release cause to be applied to filtered calls. This parameter determines the charging to be applied for service
SFBillingChargingCharacteristics
Octet string
Page 95 of 159
O M M M O
Integer (0..2147483647) -
MessageContent attributes 2 elementaryMessageIDs 3 variableMessage elementaryMessageID variableParts 0 Integer 1 Number 2 Time 3 Date 4 price 1 NumberOfRepetitions 2 duration
O O M M
This parameter specifies a sequence of announcements. This parameter specifies an announcement with one or more variable parts.
IA5String Octet string Integer (0..2147483647) Integer (0..2147483647) Integer (0..2147483647) Octet string Octet string Octet string Octet string INTEGER (1..127) INTEGER (0..32767) 0 indicates endless repetition.
O O
This parameter indicates the maximum number of times the message shall be sent to the end-user. This parameter indicates the maximum time duration in seconds that the message shall be played/repeated.
Page 96 of 159
M O
INTEGER (0..2147483647) INTEGER (0..2147483647) 0 indicates infinite duration IA5string INTEGER (1..100)
2 displayInformation maximumNumberOfCounters
M O
releaseCause
This parameter indicates a text string to be sent to the end-user. This information cannot be received by a PSTN end-user. This parameter provides number of counters to be allocated as well as number of destinations included in the service filtering, i.e. maximumNumberOfCounters subsequent destination addresses beginning with the destination address provided in filtering criteria are used for service filtering. One counter is assigned to each of these destination addresses. The number of counters may only be >1 if the 'filteringCriteria' are of the type 'addressAndService'. This parameter provides the cause value used for call release after the 'informationToSend' (for example announcement) has been sent to the calling party. This parameter indicates the severity of the filtering and the point in time when the 'ServiceFilteringResponse' shall be sent. It determines whether the 'interval' or the 'numberOfCalls' are used. After expiration of the interval timer, the next call to arrive causes following actions. 1. sending of an 'InitialDP' or a DP-specific operation 2. sending of a 'ServiceFilteringResponse' 3. starting again the interval timer. When filtering is started the first interval is started An interval of 0 indicates that all calls matching the filtering criteria will result in sending of an 'InitialDP' or a DP-specific operation and no filtering will be applied (i.e. no 'ServiceFilteringResponse'
M M
Page 97 of 159
Filtering Time-Out
Duration
INTEGER (-2..86400) 0 remove service filtering 1 indicates infinite duration 2 ndicates network specific duration Octet string
stopTime
Filtering Criteria
DialedNumber
When the 'stopTime' is met then service filtering is stopped and the final report is sent to the SCF. If 'stopTime' was already met, i.e. the value of the stopTime is less than the value of the actual time but the difference does not exceed the value equivalent to 50 years, then service filtering is immediately stopped and the actual counter values are reported to the SCF. This occurs in cases where the SCF wishes to explicitly stop a running service filtering. This parameter specifies which calls are filtered based on 'serviceKey', 'callingAddressValue', 'calledAddressValue' or 'locationNumber'. It is a choice of 'servicekey' or 'addressAndService'. Defined in ITU-T but not in ETSI
Page 98 of 159
M M M O M O
INTEGER (0..2147483647) Octet string Octet string INTEGER (0..2147483647) Octet string
Start Time extensions Type criticality value OPERATION ERRORS Name MissingParameter ParameterOutOfRange SystemFailure TaskRefused UnexpectedComponent sequence Unexpected parameter
O O M O
Octet string
0 - ignore 1 - abort
Desired
Description
Local Value 7 8 11 12 14 16
Page 99 of 159
14.1.2ActivityTest
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 within a given time period, then the SCF will assume that the SSF has failed in some way and will take the appropriate action
ActivityTest (AT)
Optional/Mandatory
Description
Value
14.1.3ApplyCharging
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. As several connection configurations may be established during a call, a possibility exists for the "ApplyCharging" to be invoked at the beginning of each connection configuration, for each party. It may be invoked several times during a call.
ApplyCharging (AC)
Optional/ Mandatory M
Desired Field
Description This parameter 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. Its contents is network operator specific. Defined in ETSI only but not in ITU-T This parameter indicates the party in the call to which the "ApplyCharging" operation should be applied. If it is not present, then it is applied to the A-party.
M O M M O M O
Default-FALSE, always TRUE Leg1 (01H) Leg2 (02H) Leg1 (01H) Leg2 (02H)
This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
Description
Value 7 8 11 12 14 15 16
14.1.4ApplyChargingReport
This operation is used by the SSF to report charging related information to the SCF as requested by the SCF using the 'ApplyCharging' operation. During a connection configuration the 'ApplyChargingReport' operation may be invoked on multiple occasions. For each call party and each connection configuration, the 'ApplyChargingReport' operation may be used several times. Note that at least one 'ApplyChargingReport' operation is to be sent at the end of the connection configuration charging process.
ApplyChargingReport (ACR)
Optional/ Mandatory M
Desired Field
Description This parameter provides the SCF with the charging related information previously requested using the 'ApplyCharging' operation. The 'CallResult' will include the 'partyToCharge' parameter as received in the related 'ApplyCharging' operation to correlate the result to the request. The remaining content of 'CallResult' is network operator specific. Examples of these contents may be: bulk counter values, costs, tariff change and time of change, time stamps, durations, etc. Description
Value
OPERATION ERRORS Name MissingParameter ParameterOutOfRange SystemFailure TaskRefused UnexpectedComponent sequence unexpectedDataValue Unexpected parameter
Local Value 7 8 11 12 14 15 16
14.1.5AssistRequestInstruction
This operation is sent to the SCF by an SSF, which is acting as the assisting SSF in an assist or handoff procedure, or by a SRF. The operation is sent when the assisting SSF or SRF receives an indication from an initiating SSF containing information indicating an assist or handoff procedure.
AssistRequestInformation (ARI)
Optional/ Mandatory O O M
Desired Field
Description This parameter is applicable to this operation only in the physical scenarios corresponding to assist with relay or handoff. The use of this parameter is network operator dependent. This parameter is applicable to this operation only in the physical scenarios corresponding to assist with relay or handoff. The use of this parameter is network operator dependent. This parameter is used by the SCF to associate the 'AssistRequestInstructions' from the assisting SSF or by a SRF with the request from the initiating SSF. The value of the 'correlationID' may be extracted from the digits received from the initiating SSF or be all of the digits. This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
O M O
0 - ignore 1 - abort
value OPERATION ERRORS Name MissingParameter missingCustomerRecord TaskRefused UnexpectedComponent sequence unexpectedDataValue
Description
Value 7 6 12 14 15
14.1.6CallGap
This operation is used to request the SSF to reduce the rate at which specific service requests are sent to the SCF.
CallGap (CG)
Optional/ Mandatory O
Desired Field
Description This parameter indicates the reason for activating call gapping. "manuallyInitiated" indicates that the service and or network/service management centre has detected a congestion situation, or any other situation that requires manually initiated controls 2). "sCPOverloaded" indicates that an automatic congestion detection and control mechanism in the SCP has detected a congestion situation. This parameter indicates the gapping characteristics. This parameter specifies the total time interval during which call gapping for the specified gap criteria will be active.
GapIndicators duration
M M
Integer (-2...86400) 0 indicates that gapping is to be removed 1 indicates an infinite duration 2 indicates a network specific duration Other values indicate duration in seconds.
The controlType "manuallyInitiated" will have priority over "sCPOverloaded" call gap.
It should be noted that also non-IN controlled traffic control mechanism can apply to an exchange with the SSF functionality. The non-IN controlled traffic control may also have some influence to the IN call. Therefore it is recommended to take measures to coordinate several traffic control mechanisms. The non-IN controlled traffic control and coordination of several traffic control mechanisms are out of the scope of INAP.
GapCriteria
This parameter identifies the criteria for a call to be subject to call gapping.
0 calledAddressValue 2 gapOnService serviceKey 2 calledAddressAndService 9 CalledAddressValue serviceKey 3 callingAddressAndService 0 CallingAddressValue serviceKey locationNumber GapTreatment 0 InformationToSend 0 InbandInfo messageID
M M M M M M
This parameter indicates that call gapping will be applied when the leading digits of the dialled number of a call attempt match those specified in "gapCriteria". This parameter indicates that call gapping will be applied when the "servicekey" of a call attempt match those specified in "gapCriteria". This parameter indicates that call gapping will be applied when the "serviceKey" and the leading digits of the dialled number of a call attempt match those specified in "gapCriteria".
Octet string INTEGER (0..2147483647) INTEGER (0..2147483647) Octet string INTEGER (0..2147483647) -
This parameter indicates that call gapping will be applied when the "serviceKey" and the leading digits of the calling party number or the location number of a call attempt match those specified in "gapCriteria". M M O O
Octet string INTEGER (0..2147483647) Octet string This parameter indicates how calls that were stopped by the call gapping mechanism shall be treated. This parameter indicates an announcement, a tone or display information to be sent to the end user by the SRF. This parameter specifies the inband information to be sent This parameter indicates the message(s) to be sent, this can be one of the following:
M M
M O
This parameter indicates a single announcement This parameter indicates a text to be sent. The text shall be transformed to inband information (speech) by the SRF. This parameter consist of two subparameters, messageContent and attributes. The attributes of text may consist of items such as language.
Integer (0..2147483647) -
MessageCont ent attributes 2 elementaryMessa geIDs 3 variableMessage elementaryMe ssageID variableParts 0 Integer 1 Number 2 Time 3 Date 4 price 1 NumberOfRepetition s 2 duration 3 interval
O O M M This parameter specifies a sequence of announcements. This parameter specifies an announcement with one or more variable parts.
IA5String Octet string Integer (0..2147483647) Integer (0..2147483647) Integer (0..2147483647) Octet string Octet string Octet string Octet string INTEGER (1..127) INTEGER (0..32767) 0 indicates endless repetition. INTEGER (0..32767)
O O O
M O
This parameter indicates the maximum number of times the message shall be sent to the end-user. This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. This parameter indicates the time interval in seconds between repetitions, i.e. the time between the end of the announcement and the start of the next repetition. This parameter can only be used when the number of repetitions is > 1. This parameter specifies a tone to be sent to the end-user. This parameter indicates the tone to be sent. This parameter indicates the time duration in seconds of the tone to be sent.
0 - ignore 1 - abort
14.1.7CallInformationReport
This operation is used to send specific call information for a single call to the SCF as requested by the SCF in previous 'CallInformationRequest' operation. The report is sent at the end of a call which is indicated by one of the events specified below.
CallInformationReport (CIR)
Optional/ Mandatory M
Desired field
Description According to the requested information, the SSF sends the appropriate types and values to the SCF. CallAttemptElapsedTime : This parameter indicates the duration between the end of INAP processing of operations initiating call set-up ('Connect', 'AnalyseInformation', 'CollectInformation', 'Continue' and 'SelectRoute') and the received answer indication from the called party side. In case of unsuccessful call set-up the network event indicating the unsuccessful call set-up stops the measurement of 'callAttemptElapsedTime'. CallStopTime : This parameter indicates the time stamp when the connection is released. CallConnectedElapsedTime : This parameter indicates the duration between the received answer indication from the called party side and the release of the connection. CalledAddress : This parameter indicates the incoming called party address that was received by the SSF (i.e. before translation by the SCF) and is as available on the UNI or NNI and interpreted as per the numbering plan. Defined only in ITU-T but not in ETSI
Value CallAttemptElapsedTime (0) CallStopTime (1) CallConnectedElapsedTime (2) CalledAddress (3) ReleaseCause (30)
Correlation ID
This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
14.1.8CallInformationRequest
This operation is used to request the SSF to record specific information about a single call and report it to the SCF using the 'CallInformationReport' operation.
CallInformationRequest (CIQ)
Optional/ Mandatory M
Desired Field
Description According to the requested information, the SSF sends the appropriate types and values to the SCF. CallAttemptElapsedTime : This parameter indicates the duration between the end of INAP processing of operations initiating call set-up ('Connect', 'AnalyseInformation', 'CollectInformation', 'Continue' and 'SelectRoute') and the received answer indication from the called party side. In case of unsuccessful call set-up the network event indicating the unsuccessful call set-up stops the measurement of 'callAttemptElapsedTime'. CallStopTime : This parameter indicates the time stamp when the connection is released. CallConnectedElapsedTime : This parameter indicates the duration between the received answer indication from the called party side and the release of the connection. CalledAddress : This parameter indicates the incoming called party address that was received by the SSF (i.e. before translation by the SCF) and is as available on the UNI or NNI and interpreted as per the numbering plan. Defined only in ITU-T but not in ETSI
Value CallAttemptElapsedTime (0) CallStopTime (1) CallConnectedElapsedTime (2) CalledAddress (3) ReleaseCause (30)
Correlation ID Extensions
O O
0 - ignore 1 - abort
Description
Value 7 8 10 11 12 14 15 16
Here are the details of the time measurement parameters in CIQ/CIR. CAET is callAttemptElapsedTime and CCET is callConnectedElapsedTime. (1) successful call callStopTime
CAET
CCET
IAM
IDP
CON
ANS
REL
14.1.9Cancel
The SCF uses this class 2 operation to request the SRF-SSF to cancel a correlated previous operation. The SRF operation to be deleted can be either a 'PlayAnnouncement' operation or a 'PromptAndCollectUserInformation' operation. The cancellation of an operation is indicated via a respective error indication, "Cancelled", to the invoking entity of the cancelled "PlayAnnouncement" or "PromptAndCollectUserInformation" operation. The 'Cancel' operation can also be used to cancel all outstanding requests and enable the state machine (SSF) to go to idle. In this case the 'Cancel' operation does not specify any specific operation to be cancelled.
Cancel (CAN)
Desired field
Description This parameter specifies which operation is to be cancelled, i.e. PromptAndCollectUserInformation or PlayAnnouncement. This parameter indicates that all active requests for EDP reports (generic or DP specific)EventReportBCSM, "ApplyChargingReport", EventNotificationCharging and "CallInformationReport" should be cancelled. Description
1 7 12
14.1.10
CollectInformation
The CollectInformation is a class 2 operation which is used by the SCF to request the call to return to the Collect_Information PIC, and then perform the basic originating call processing actions associated with this PIC (e.g. the checking of information in the CalledPartyNumber parameter with the supported dialling plan). This operation uses only the resources of the SSF-CCF to collect the information. The use of this operation is only appropriate for a call which had not yet left the set-up phase. When the user provides calledPartyNumber, Collect_Information PIC processing includes collecting of destination information from a calling party. When the calledPartyNumber is included (as dialledDigits) in the Collect_Information operation, further collection is not performed (e.g. SSF-CCF checks the provided calledPartyNumber against the supported dialling plan).
CollectInformation (CI)
Optional/ Mandatory O O
Desired field
Description See Recommendation Q.1290. It only applies if the network signalling support this parameter or if SSF is the terminating local exchange for the subscriber. See Recommendation Q.763 Numbering Plan for encoding.
Value
O O O O O M O
See Recommendation Q.762 Original Called Number signalling information. See Recommendation Q.1290. This parameter contains the travelling class mark information of the calling party. It uses the LocationNumber format which is based on the Q.763 Location Number format. See Recommendation Q.762. This parameter is applied against the supported dialling plan in the SSF-CCF and, if valid, is used in routing of the call. If provided, it replaces the calledPartyNumber for the call. Only this parameter is defined in ETSI This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
Description 7 8 11 12 14 15 16
14.1.11
Connect
This operation is used to request the SSF to perform the call processing actions to route a call to a specific destination. To do so, the SSF may use destination information from the calling party (e.g. dialled digits) and existing call set-up information (e.g. route index to a list of trunk groups) depending on the information provided by the SCF. In general, all parameters which are provided in a Connect operation to the SSF shall replace the corresponding signalling parameter in the CCF, if the relevant parameter has already been received in the CCF, and shall be used for subsequent call processing. Parameters which are not provided by the Connect operation shall retain their value (if already assigned) in the CCF for subsequent call processing.
Connect (CON)
Optional/ Mandatory M
Desired field Y
Description This parameter contains the list of called party numbers (see Recommendation Q.762) towards which the call is to be routed. The encoding of the parameter is defined in Recommendation Q.763. The 'destinationRoutingAddress' may include the 'correlationID' and 'scfID' if used in the context of a hand-off procedure, but only if 'correlationID' and 'scfID' are not specified separately. A specific pattern used to alert a subscriber (e.g. distinctive ringing, tones, etc.). Recommendation Q.931 refers. It only applies if the network signalling support this parameter or if SSF is the terminating local exchange for the subscriber. This parameter is used by the SCF to associate the 'AssistRequestInstructions' operation from the assisting SSF with the Request from the initiating SSF. The 'correlationID' is used in the context of a hand-off procedure and only if the correlation id is not embedded in the 'destinationRoutingAddress'. The network operator has to decide about the actual mapping of this parameter on the used signalling system. This parameter is used by the SCF to instruct the SSF to delete (cut) a specified number of leading digits that it has received from the calling party and to paste the remaining dialled digits on to the end of the digits supplied by the SCF in the 'destinationRoutingAddress'
Alerting Pattern
Octet string
correlationID
Octet string
cutAndPaste
Integer (0..22)
scfID
Octet string
travellingClassMark
Octet string
O O O O O O O Y
Octet string Octet string Octet string Octet string Octet string Octet string
0 - ignore 1 - abort
Description 7 8 11 12 14 15 16
14.1.12
ConnectToResource
This operation is used to connect a call from the SSF to a specialized resource. After successful connection to the SRF, the interaction with the caller can take place. The SSF relays all operations for the SRF and all responses from the SRF.
ConnectToResource (CTR)
Optional/ Mandatory O
Desired field Y
Value -
This parameter indicates the routing address to set up a connection towards the SRF. This parameter indicates that the call party is to be connected to a predefined SRF. Only defined in ITU-T but not ETSI. This parameter indicates the routing address to set up a connection towards the SRF. Only defined in ITU-T but not ETSI.
Octet string Octet string Octet string Octet string Octet string Octet string
receivingSideID Both (iPRoutingAddress & LegID) serviceInteractionIndicators 2 Extensions Type criticality value
O O M O
This parameter contains indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange. This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
Description 7 11 12 14 15 16
14.1.13
Continue
This operation is used to request the SSF to 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.
Continue (CUE)
Parameter N.A.
Optional/ Mandatory
Description
Value
14.1.14
DisconnectForwardConnection
This operation is used in the following two cases: 1. To clear a connection to a SRF This operation is used to explicitly disconnect a connection to a resource (SRF) established previously with a 'ConnectToResource' or an 'EstablishTemporaryConnection' operation. It is used for a forward disconnection from the SSF. An alternative solution is the backward disconnect from the SRF, controlled by the 'DisconnectFromIPForbidden' parameter in the 'PlayAnnouncement' and 'PromptAndCollectUserInformation' operations. 2. To clear a connection to an assisting SSF This operation is sent to the non-assisting SSF of a pair of SSFs involved in an assist procedure. It is used to disconnect the temporary connection between the initiating SSF and the assisting SSF, and the assisting SSF and its associated SRF.
DisconnectForwardConnection (DFC)
ARGUMENT Parameter N.A. OPERATION ERRORS Name MissingParameter SystemFailure TaskRefused UnexpectedComponentSequence UnexpectedDataValue UnexpectedParameter
Optional/ Mandatory
Description
Value
Description 7 11 12 14 15 16
14.1.15
EstablishTemporaryConnection
This operation is used to create a connection between an initiating SSF and an assisting SSF as part of a service assist procedure. It can also be used to create a connection between a SSF and a SRF, for the case where the SRF exists in a separately addressable physical entity.
EstablishTemporaryConnection (ETC)
Optional/ Mandatory M
Desired field
Description This parameter indicates the destination address of the SRF for assist procedure. The 'assistingSSPIPRoutingAddress' may contain embedded within it, a 'correlationID' and 'scfID', but only if 'correlationID' and 'scfID' are not specified separately. This parameter is used by the SCF to associate the 'AssistRequestInstructions' from the assisting SSF (or the SRF) with the Request from the initiating SSF. The 'correlationID' is used only if the correlation id is not embedded in the 'assistingSSPIPRoutingAddress'. The network operator has to decide about the actual mapping of this parameter on the used signalling system. See Recommendation Q.1290. The 'scfID' is used only if the SCF id is not embedded in the 'assistingSSPIPRoutingAddress'. The network operator has to decide about the actual mapping of this parameter on the used signaling system. See Recommendation Q.1290. In this message, the carrier selection field is null (00000000) and Carrier ID indicates the carrier to use for the call. Defined in ITU-T only but not ETSI. This parameter contains indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange.
correlationID
Octet string
scfID
Octet string
carrier
Octet string
serviceInteractionIndicators LegID
O O
Octet string
0 - ignore 1 - abort
Description 3 7 11 12 14 15 16
14.1.16
EventNotificationCharging
This operation is used to create a connection between an initiating SSF and an assisting SSF as part of a service assist procedure. It can also be used to create a connection between a SSF and a SRF, for the case where the SRF exists in a separately addressable physical entity.
EventNotificationCharging (ENC)
Optional/ Mandatory M O O
Desired field
Description This parameter indicates the charging event type which has occurred. Its content is network operator specific, which may be "charge pulses" or "charge messages". This parameter contains charging related information specific to the event. Its content is network operator specific. This parameter indicates the leg id on which the charging event type applies. This parameter indicates the routing address to set up a connection towards the SRF. This parameter indicates that the call party is to be connected to a predefined SRF. This parameter indicates how the charging event is reported. When the "monitorMode" is "interrupted", the event is reported as a request; if the "monitorMode" is "notifyAndContinue" the event is reported as a notification. The "monitorMode" "transparent" is not applicable for the "EventNotificationCharging" operation. This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
O M O
0 - ignore 1 - abort
14.1.17
EventReportBCSM
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 could be requested with a 'RequestReportBCSMEvent' operation, but each of these requested events is reported in a separate 'EventReportBCSM' operation.
EventReportBCSM (ERB)
Optional/ Mandatory M
Desire d field
Value 1 origAttemptAuthorized 2 collectedInfo 3 analysedInformation 4 routeSelectFailure 5 OcalledPartyBusy 6 oNoAnswer 7 oAnswer 8 oMidCall 9 oDisconnect 10 oAbandon 12 termAttemptAuthorized 13 tBusy 14 tNoAnswer 15 tAnswer 16 tMidCall 17 - tDisconnect 18 - tAbandon
O O
Used by the SCF for correlation with a previous operation. Defined in ITU-T only but not ETSI This parameter indicates the call related information specific to the event. For 'CollectedInfo' it will contain the 'calledPartyNumber'. Octet string
0 Request 1 - notification
This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
14.1.18
FurnishChargingInformation
This operation is used to request the SSF to generate, register a call record or to include some information in the default call record. The registered call record is intended for off-line charging of the call. A possibility exists for the FurnishChargingInformation (FCI) operation to be invoked on multiple occasions. FCI could be applied at the beginning of the call in order to request to start call record generation. In addition FCI can also be applied at the end of the call or connection configuration (e.g. for follow-on calls). In this case FCI is used to include charge related information into the call record which was started at the beginning of the call. When additional FCIs are used it is recommended to arm an EDP-R (indicating the end of call or connection configuration) to be able to apply FCI before the termination of the call record generation. The charging scenarios supported by this operation are: 2.2, 2.3 and 2.4 (refer to Appendix II/Q.1214, "Charging scenarios").
FurnishChargingInformation (FCI)
Optional/ Mandatory M
Desire d field
Description This parameter indicates billing and/or charging characteristics. Its content is network operator specific. Depending on the applied charging scenario, the following information elements can be included (refer to Appendix II/Q.1214, "Charging scenarios": complete charging record, charge party, charge level, charge items, correlationID.
Description 7 12 14 15 16
14.1.19
InitialDP
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.
InitialDP (IDP)
Optional/ Mandatory O
Desired field Y
Description This parameter identifies for the SCF unambiguously the requested IN service. It is used to address the correct application/SLP within the SCF (not for SCP addressing). Defined only in ITU-T but not ETSI This parameter contains the number used to identify the called party in the forward direction, i.e. see Recommendation Q.762. This parameter, if present, is used to identify the calling party for the call (see Q.762 Calling Party Number). It may be used for applications such as UPT, where only the SCF can verify the identity of the calling party. See Recommendation Q.762 Calling Party Category signaling information. See Recommendation Q.1290.
O O
Y Y
callingPartysCategory cGEncountered
O O
Octet string 0 noCGEncountered (only in ITU-T but not ETSI) 1 manualCGEncountered 2 scpOverload (optional) Octet string Octet string
iPSSPCapabilities iPAvailable
O O
Indication of which SRF resources are supported, and attached at the SSP from which the call was suspended. (See Recommendation Q.1290.) Indication whether or not an IP is attached, and available at the SSP. (See Recommendation Q.1290.)
MiscCallInfo messageType
0 Request 1 - notification
0 individualline 1 groupbased 2 - officebased Octet string Octet string 0 unknown 1 dialPulse 2 dtmf 3 isdn 4 isdnNoDtmf 16 - spare
highlayerCompatibility
serviceInteractionIndicators additionalCallingPartyNumber
O O
This parameter indicates the type of the high layer compatibility, which will be used to determine the ISDNteleservice of a connected ISDN terminal. For encoding DSS1 (see Recommendation Q.931) is used. The highlayerCompatibility can also be transported by ISUP within the ATP (see Recommendation Q.763) parameter. This parameter contains indicators sent from the SSF to the SCF for control of the network based services at the originating exchange and the destination exchange. The calling party number provided by the access signalling system of the calling user, e.g. provided by a PBX.
bearerCapability
bearerCap
Octet string
tmr
redirectingPartyID redirectionInformation Extensions Type criticality value OPERATION ERRORS Name missingCustomerRecord MissingParameter ParameterOutOfRange SystemFailure TaskRefused UnexpectedComponentSequence UnexpectedDataValue
O O O M O
This parameter, if present, indicates the last directory number the call was redirected from See Recommendation Q.763 Redirection Information signaling information. This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
Description 6 7 8 11 12 14 15
14.1.20
InitiateCallAttempt
This operation is used to request the SSF to create a new call to one call party using the address information provided by the SCF (e.g. wake-up call). An EDP-R must be armed on answer and all the call failure events, in order to have the SCF, treat this call appropriately when either of these events is encountered.
InitiateCallAttempt (ICA)
Optional/ Mandatory O
Desired field
Description This parameter contains the list of called party numbers (see Recommendation Q.762) towards which the call is to be routed. The encoding of the parameter is defined in Recommendation Q.763. The 'destinationRoutingAddress' may include the 'correlationID' and 'scfID' if used in the context of a hand-off procedure, but only if 'correlationID' and 'scfID' are not specified separately See Recommendation Q.1290. It only applies if the network signalling support this parameter or if SSF is the terminating local exchange for the subscriber Carries the same information as the protocol element ISUP Access Transport parameter in Recommendation Q.762 The SCF uses the travellingClassMark parameter to provide essential route selection information to the SSF. The SSF uses this information to populate the outgoing ISUP-IAM message, the population and mapping of this parameter is network operator specific This parameter contains indicators sent from the SCF to the SSF for control of the network based services at the originating exchange and the destination exchange This parameter, if present, is used to identify the calling party for the call (see Q.762 Calling Party Number). It may be used for applications such as UPT, where only the SCF can verify the identity of the calling party.
O O O
serviceInteractionIndicators callingPartyNumber
O O
This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
Description 7 8 11 12 14 15 16
14.1.21
PlayAnnouncement
This operation is used for inband interaction with an analogue user or for interaction with an ISDN user.
PlayAnnouncement (PA)
Optional/ Mandatory M M M M O
Desired field
Description This parameter indicates an announcement, a tone or display information to be sent to the end user by the SRF This parameter specifies the inband information to be sent This parameter indicates the message(s) to be sent, this can be one of the following: This parameter indicates a single announcement This parameter indicates a text to be sent. The text shall be transformed to inband information (speech) by the SRF. This parameter consist of two subparameters, messageContent and attributes. The attributes of text may consist of items such as language.
Value
Integer (0..2147483647) -
MessageContent attributes 2 elementaryMessageIDs 3 variableMessage elementaryMessageID variableParts 0 Integer 1 Number 2 Time 3 Date
O O M M
This parameter specifies a sequence of announcements. This parameter specifies an announcement with one or more variable parts.
IA5String Octet string Integer (0..2147483647) Integer (0..2147483647) Integer (0..2147483647) Octet string Octet string Octet string
O O O
This parameter indicates the maximum number of times the message shall be sent to the end-user. This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. This parameter indicates the time interval in seconds between repetitions, i.e. the time between the end of the announcement and the start of the next repetition. This parameter can only be used when the number of repetitions is > 1. This parameter specifies a tone to be sent to the end-user. This parameter indicates the tone to be sent. This parameter indicates the time duration in seconds of the tone to be sent.
M O
INTEGER (0..2147483647) INTEGER (0..2147483647) 0 indicates infinite duration IA5string Default - TRUE Default - TRUE
displayInformation
M M M O M O
disconnectFromIPForbidden requestAnnouncementComplete Extensions Type criticality value OPERATION ERRORS Name canceled
This parameter indicates a text string to be sent to the enduser. This information cannot be received by a PSTN enduser. This parameter indicates whether or not the SRF should be disconnected from the user when all information has been sent This parameter indicates whether or not a 'SpecializedResourceReport' shall be sent to the SCF when all information has been sent This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
Description 0
14.1.22
PromptAndCollectUserInformation
This operation is used to interact with a call party in order to collect information.
PromptAndCollectUserInformation (PAC)
Optional/ Mandatory M
Desired field
Description This parameter indicates an announcement, a tone or display information to be sent to the calling party. At the end of information sending, the call shall be released If this parameter is missing, the default value is defined to be 1. The "minimumNbOfDigits" specifies the minimum number of valid digits to be collected This parameter should always be present and specifies the maximum number of valid digits to be collected. The following applies: "maximumNbOfDigits" >= "minimumNbOfDigits". This parameter indicates the digit used to signal the end of input In case the "maximumNbOfDigits" = "minimumNbOfDigits", the "endOfReplyDigit" (could be present but) has no further meaning. This parameter can be one or two digits. In case the "maximumNbOfDigits" > "minimumNbOfDigits", the following applies If "endOfReplyDigit" is not present, the end of input is indicated: 1) when the inter-digit timer expires 2) when the number of valid digits received equals the "maximumNbOfDigits" If "endOfReplyDigit" is present, the end of input is indicated
Value INTEGER (1..127) DEFAULT 1 INTEGER (1..127) OCTET STRING (SIZE (1..2))
Y Y Y
cancelDigit
startDigit
firstDigitTimeout
INTEGER (1..127)
interDigitTimeOut
INTEGER (1..127)
errorTreatment
interruptableAnnInd
voiceInformation
Default : FALSE
voiceBack
Default : FALSE
iA5Information disconnectFromIPForbidden
O M Y M M O Y
Integer (0..2147483647) -
MessageContent attributes 2 elementaryMessageIDs 3 variableMessage elementaryMessageID variableParts 0 Integer 1 Number 2 Time 3 Date
O O M M
Y Y
This parameter specifies a sequence of announcements. This parameter specifies an announcement with one or more variable parts.
IA5String Octet string Integer (0..2147483647) Integer (0..2147483647) Integer (0..2147483647) Octet string Octet string Octet string
O O O
M O M O M O
This parameter indicates the maximum number of times the message shall be sent to the end-user. This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. This parameter indicates the time interval in seconds between repetitions, i.e. the time between the end of the announcement and the start of the next repetition. This parameter can only be used when the number of repetitions is > 1. This parameter specifies a tone to be sent to the end-user. This parameter indicates the tone to be sent. This parameter indicates the time duration in seconds of the tone to be sent. This parameter indicates a text string to be sent to the enduser. This information cannot be received by a PSTN enduser. This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
Extensions Type criticality value RESULT digitsResponse iA5Response OPERATION ERRORS Name canceled improperCallerResponse MissingParameter ParameterOutOfRange SystemFailure TaskRefused UnexpectedComponent Sequence
0 - ignore 1 - abort
14.1.23
ReleaseCall
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. This operation may not be sent to an assisting SSF, except in the case of hand-off procedure
ReleaseCall (RC)
Parameter Cause
Optional/ Mandatory M or O
Description A number giving an indication to the SSF about the reason of releasing this specific call. This may be used by SSF for generating specific tones to the different parties in the call or to fill in the 'cause' in the release message
Value
14.1.24
RequestNotificationChargingEvent
This operation is used to instruct the SSF how to manage the charging events which are received from other FEs not under the control of the service logic instance. The operation supports the options to cope with the interactions concerning the charging (refer to Appendix II.4/Q.1214 "Charging scenarios"). As several connection configurations may be established during a call, a possibility exists for the RequestNotificationChargingEvent (RNC) operation to be invoked on multiple occasions. For each connection configuration an RNC may be used several times.
RequestNotificationChargingEvent (RNC)
Optional/ Mandatory M M M
Desired field
Description This parameter contains a list of the charging events and the corresponding monitor types and corresponding legs. For each element in the list the following information elements are included This subparameter indicates the charging event type. Its content is network operator specific, which may be "charge pulses" or "charge messages". This subparameter indicates the monitorMode applicable for the corresponding "eventTypeCharging" subparameter. Monitor may be "interrupted", "notifyAndContinue" or "transparent". This subparameter indicates the leg id of the corresponding event type charging subparameter Used by SSF Description
Value
legID
sendingSideID receivingSideID OPERATION ERRORS Name MissingParameter ParameterOutOfRange SystemFailure TaskRefused UnexpectedComponentSequence
7 8 11 12 14
14.1.25
RequestReportBCSMEvent
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.
RequestReportBCSMEvent (RRBE)
Optional/ Mandatory M M
Desired field Y Y
Description This parameter specifies the event or events of which a report is requested This parameter specifies the type of event of which a report is requested. Values origAttemptAuthorized and termAttemptAuthorized are not valid for the eventTypeBCSM parameter
Value 1 origAttemptAuthorized 2 collectedInfo 3 analysedInformation 4 routeSelectFailure 5 OcalledPartyBusy 6 oNoAnswer 7 oAnswer 8 oMidCall 9 oDisconnect 10 oAbandon 12 termAttemptAuthorized 13 tBusy 14 tNoAnswer 15 tAnswer 16 tMidCall 17 - tDisconnect 18 - tAbandon
legID sendingSideID
Octet string
O O M
Octet string
value OPERATION ERRORS Name MissingParameter ParameterOutOfRange SystemFailure TaskRefused UnexpectedComponentSequence UnexpectedDataValue UnexpectedParameter
Description 7 8 11 12 14 15 16
14.1.26
ResetTimer
This class 2 operation is used by the SCF to refresh the TSSF application timer, in order to avoid the TSSF time-out at the SSF.
ResetTimer (RT)
ARGUMENT Parameter timerID timerValue Extensions Type criticality value OPERATION ERRORS Name MissingParameter ParameterOutOfRange TaskRefused UnexpectedComponentSequence UnexpectedDataValue UnexpectedParameter Optional/ Mandatory M M O M O Desired field Description This parameter has a default value identifying the TSSF timer This parameter specified the value to which the TSSF is to be set This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied. Value Default : TSSF INTEGER (0..2147483647)
0 - ignore 1 - abort
Description 7 8 12 14 15 16
14.1.27
SendChargingInformation
This operation is used to instruct the SSF on the charging information to be sent by the SSF. The sending of charging information can either be by charge pulses or signalling or internal if SSF is located in the Local Exchange (LE). In the LE, either charge meter can be updated or a standard call record created. A possibility exists for the SendChargingInformation (SCI) operation to be invoked on multiple occasions. The charging scenario supported by this operation is: 3.2 (refer to Appendix II/Q.1214, "Charging scenarios").
SendChargingInformation
ARGUMENT Parameter sCIBillingChargingCharacteristics charge level chargePulses chargeMessages partyToCharge 0 SendingSideID 1 receivingSideID Extensions Type criticality value OPERATION ERRORS Name MissingParameter ParameterOutOfRange
Optional/ Mandatory M
Desired field
Description This parameter has a default value identifying the TSSF timer This parameter specified the value to which the TSSF is to be set
Value
O M O
This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied.
0 - ignore 1 - abort
Description 7 8
14.1.28
ServiceFilteringResponse
This message is used by SCF to instruct the SSF to deal with requests for a specific service (without request for instructions to the SCF) and to count each specific attempt. The count of filtered calls will be returned to the SCF after a special internal.
ServiceFilteringResponse (SFR)
ARGUMENT Parameter countersValue 0 counterID 1 counterValue FilteringCriteria 0 DialedNumber 1 callingLineID 2 serviceKey 3 addressAndService 0 calledAddressValue CallingAddressValue serviceKey locationNumber
Optional/ Mandatory M
Desired field
Description The parameter contains the count of calls filtered during the filtering period. It is a list of counter identifications and the related values
Value
INTEGER (0..99) INTEGER (0..2147483647)} M This parameter is used to address the concerned service logic at the SCF Defined in ITU-T but not in ETSI Defined in ITU-T but not in ETSI This parameter identifies unambiguously the requested IN service for which filtering should be applied. This parameter identifies the IN service and dialled number for which filtering should be applied. The geographical area may also be identified ('callingAddressValue' and/or 'locationNumber'). This parameter contains the dialled number towards which filtering shall be applied. The complete called party number shall be specified. This parameter contains the calling party number which identifies the calling party or geographical origin of the call for which filtering shall be applied. This parameter identifies unambiguously the requested IN service for which filtering should be applied. This parameter identifies the geographical area from which the call
M M M O M O
INTEGER (0..2147483647) Octet string Octet string INTEGER (0..2147483647) Octet string
responseCondition
0 -intermediateResponse 1 -lastResponse
O M O
0 - ignore 1 - abort
14.1.29
SpecialisedResourceReport (SRR)
This operation is used as the response to a "PlayAnnouncement" operation when the announcement completed indication is set.
SpecialisedResourceReport (SRR)
Optional/ Mandatory
Desired field
Description
Value