Escolar Documentos
Profissional Documentos
Cultura Documentos
Feature Title:
Issue.Version: Authors:
Author: Date:
Accepted QDI ID: 19337 Lucent Technologies - Proprietary Page: Use pursuant to Company Instructions
Issue: 4 1
TABLE OF CONTENTS 1
1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9
FEATURE DESCRIPTION
Scope Guide to Requirements History / Change Record Benchmark Dates Open Issues Implementation Decision Record Competitive Information Relation to Other Features Acknowledgements
814
814 814 814 814 915 915 915 915 915 1016 1016 1016 1218
1.10 Glossary of Terms & Abbreviations 1.10.1 Standard Terms 1.10.2 Standard Acronyms 1.10.3 Lucent Acronyms
2
2.1 2.2 2.3 2.4 2.5 2.6
OVERVIEW
Scope Logical Functionality within the MSC Intra-MSC Messaging Intra-MSC States Message Error Handling Notes for Feature Testers
1319
1319 1319 1319 1319 1420 1420
3 4
4.1
1521 1521
1521 Issue: 4 2
Page:
4.2 Originating Call Scenarios 4.2.1 Sunny Day Call: A-party disconnect 4.2.2 Warning Tone Played - A-party disconnect 4.2.3 Interval Timer Expires 4.2.4 Two Apply Charging Operations 4.2.5 Switch Based Announcement Prior to Call Completion 4.2.6 IP Based Announcement Prior to Call Completion 4.2.7 IP based announcement prior to call to busy B-party 4.3 Terminating Call Scenarios 4.3.1 Basic Mobile Termination with CAMEL 4.3.2 Termination with gsmSCF Modified Number 4.3.3 Mobile Termination with Unmodified Number 4.4 Call Forwarding Call Scenarios 4.4.1 GSM Call Forwarding Unconditional at GMSC 4.4.2 Termination with GSM Call Forwarding on Mobile Not Reachable at GMSC 4.4.3 CAMEL Call Forwarding 4.4.4 GSM Call Forwarding at the VMSC
1521 1521 1723 1824 1925 2026 2127 2127 2228 2228 2430 2531 2531 2632 2733 2935 3036
5
5.1
CAMEL STANDARDS
Standards Documents
3036
3036 3137 3137 3238 3339 3339 3339
5.2 Roadmap to CAMEL Stage 2 5.2.1 Processes and Procedures for Originating Calls 5.2.2 Processes and Procedures for Terminating and Forwarded Calls 5.3 5.4 5.5 CAMEL Standards and FSD Requirements Call Control Function State Machine Service Switching Function State Machine
6
6.1
VLR REQUIREMENTS
CAMEL Subscriber Data
3339
3339
7
7.1 7.2 7.3 7.4 7.5
MSC DATA
Incoming roaming restrictions for CAMEL subscribers Location Numbers CAMEL phase supported Network Operator Specific parameters Announcement identifiers for internal gsmSRF Author: Marianne Picha Lucent Technologies - Proprietary
3440
3440 3440 3541 3541 3642 Issue: 4 3
Page:
7.6
3743
8
8.1 8.2
MSC REQUIREMENTS
Digit Analysis Emergency Calls
3743
3743 3743 3743 3844 3844 4551 5359 6066 6066
8.3 Call Control Function (CCF) 8.3.1 Triggering a gsmSCF Interaction 8.3.2 Originating Call Processing
8.3.3
8.3.4 8.3.5 8.3.6
8.3.6.1 8.3.6.2
8.3.7
6167
8.3.7.1 8.3.7.2 8.3.7.3 8.3.7.4 8.3.7.5 8.3.7.6 8.3.7.7 8.3.7.8 8.3.7.9 8.3.7.10 8.3.7.11 8.3.7.12
Calling Line Identification Presentation (CLIP)....................................................................... 6268 Calling Line Identification Restriction (CLIR)......................................................................... 6268 Connected Line Identity Presentation (COLP)......................................................................... 6268 Call Forwarding ..................................................................................................................... 6268 Call Hold ............................................................................................................................... 6369 Call Waiting........................................................................................................................... 6369 Multi Party............................................................................................................................. 6369 Closed User Group (CUG)...................................................................................................... 6369 Mobile Number Portability (MNP) ......................................................................................... 6470 Advice of Charge (AoC)..................................................................................................... 6470 Call Barring ....................................................................................................................... 6470 Interactions with Lucent proprietary features....................................................................... 6470
8.3.8
6571
8.3.8.1 8.3.8.2
Receipt of ProvideSubscriberInfo operation ............................................................................ 6571 R-FSD19337.2-V1>R-FSD19337.2-V1>Receipt of Suppression of Announcement parameter.. 6571
8.4 Service Switching Function (SSF or gsmSSF) 8.4.1 InitialDP Sent to the SCP 8.4.2 Receiving SCP Call Handling Instructions
8.4.2.1 8.4.2.2 8.4.2.3 8.4.2.4
Receipt of CAP Continue operation ........................................................................................ 6773 Receipt of Connect operation.................................................................................................. 6773 Receipt of ResetTimer operation............................................................................................. 6874 Expiration of SSF guard timer (Tssf)....................................................................................... 6874
8.4.3
6975
8.4.3.1 8.4.3.2
Receipt of RequestReportBCSMEvent.................................................................................... 6975 Receipt of Cancel operation for pending EDPs and reports ...................................................... 7076
8.4.4
Call Termination
7076
Receipt of ReleaseCall operation ............................................................................................ 7076 Call termination due to internal error....................................................................................... 7177 Disconnect from A or B party................................................................................................. 7177 Caller Abandon ...................................................................................................................... 7278
8.4.5
7379
8.4.5.1 8.4.5.2 8.4.5.3 8.4.5.4 8.4.5.5 8.4.5.6 8.4.5.7 8.4.5.8 8.4.5.9 8.4.5.10 8.4.5.11 8.4.5.12 8.4.5.13 8.4.5.14 8.4.5.15
Announcement Configurations................................................................................................ 7379 Contacting an assisting gsmSSF.............................................................................................. 7379 Triggering on an assisting gsmSSF ......................................................................................... 7480 The gsmSSF state machine and the gsmSRF ........................................................................... 7480 Receipt of EstablishTemporaryConnection operation............................................................... 7581 Receipt of DisconnectForwardConnection............................................................................... 7581 Receipt of ConnectToResource............................................................................................... 7682 Receipt of PlayAnnouncement................................................................................................ 7682 Receipt of PromptAndCollectUserInformation ........................................................................ 7682 Receipt of Cancel operation for announcement sessions ...................................................... 7783 Sending CAP Canceled error .............................................................................................. 7884 Sending CAP Cancel Failed error ....................................................................................... 7884 Sending PromptAndCollectUserInformation result.............................................................. 7985 Sending SpecializedResourceReport ................................................................................... 7985 Expiration of Tssf timer during announcement session ........................................................ 8086
8.4.6
8.4.6.1 8.4.6.2 8.4.6.3 8.4.6.4 8.4.6.5
8086
Connection establishment to IP or Assisting SSP..................................................................... 8086 Connection establishment from internal SRF........................................................................... 8187 Connection release to internal SRF ......................................................................................... 8288 Release of Temporary Connection from Call Control............................................................... 8288 Announcement session: miscellaneous.................................................................................... 8389
8.4.7
Monitoring State
8591
Receipt of RequestReportBCSMEvent.................................................................................... 8591 Disconnect or Abandon .......................................................................................................... 8692 Timer Expiration.................................................................................................................... 8692 Receipt of CAP Cancel for pending EDPs and reports ............................................................. 8894 Answer event detected............................................................................................................ 8894 Pre-answer events detected ..................................................................................................... 8995
8.4.8
8.4.8.1 8.4.8.2 8.4.8.3 8.4.8.4
9096
Receipt of ApplyCharging operation ....................................................................................... 9096 Receipt of SendChargingInformation operation....................................................................... 9096 Receipt of FurnishChargingInformation operation ................................................................... 9197 Receipt of CallInformationRequest operation .......................................................................... 9197
ASSISTING MSC
9298
9298 9298 9399 96102 96102 96102
9.1 Assisting Call Control State Machine 9.1.1 Receipt of Initial Request from Initiating MSC 9.1.2 Awaiting Instructions on Announcement Sessions 9.2 Process Assisting_gsmSSF 9.2.1 Requesting Instructions from the gsmSCF
9.2.2
9.2.2.1 9.2.2.2 9.2.2.3 9.2.2.4 9.2.2.5 9.2.2.6 9.2.2.7
gsmSCF Instructions
Receipt of ResetTimer operation............................................................................................97103 Receipt of ConnectToResource operation...............................................................................97103 Receipt of DisconnectForwardConnection operation ..............................................................98104 Receipt of PlayAnnouncement operation................................................................................99105 Receipt of PromptAndCollectUserInformation operation ........................................................99105 Receipt of Cancel operation for announcement sessions........................................................100106 Sending PromptAndCollectUserInformation result ...............................................................101107
Page:
Issue: 4 5
9.2.2.8 9.2.2.9
Sending SpecializedResourceReport ....................................................................................101107 Expiration of Tssf timer during announcement session .........................................................102108
10
MAP REQUIREMENTS
103109
103109 103109 104110 104110 105111 105111 105111 106112 106112 107113 107113 108114
10.1 HLR !" VLR Information Flows 10.1.1 MAP ProvideSubscriberInfo operation 10.1.2 MAP Insert Subscriber Data operation 10.1.3 Map DeleteSubscriberData operation 10.1.4 Map UpdateLocation operation 10.1.5 Map RestoreData operation 10.1.6 Map ProvideRoamingNumber operation 10.2 HLR !" GMSC Information Flows 10.2.1 MAP SendRoutingInfo operation 10.3 VMSC !" GMSC Information Flows 10.3.1 MAP ResumeCallHandling operation 10.4 MSC to gsmSCF Information Flows
11
11.1
CAP REQUIREMENTS
CAP Application Contexts
108114
108114 109115 109115 109115 110116 110116 110116 111117 111117 111117 112118 112118 113119 113119 114120 114120 115121 115121 116122 116122 116122 117123 118124 119125 119125 Issue: 4 6
11.2 CAP Operations 11.2.1 CAP ActivityTest operation 11.2.2 CAP ApplyCharging operation 11.2.3 CAP ApplyChargingReport operation 11.2.4 CAP AssistRequestInstructions operation 11.2.5 CAP CallInformationReport operation 11.2.6 CAP CallInformationRequest operation 11.2.7 CAP Cancel operation 11.2.8 CAP Connect operation 11.2.9 CAP ConnectToResource operation 11.2.10 CAP Continue operation 11.2.11 CAP DisconnectForwardConnection operation 11.2.12 CAP EstablishTemporaryConnection operation 11.2.13 CAP EventReportBCSM operation 11.2.14 CAP FurnishChargingInformation operation 11.2.15 CAP InitialDP operation 11.2.16 CAP ReleaseCall operation 11.2.17 CAP RequestReportBCSMEvent operation 11.2.18 CAP ResetTimer operation 11.2.19 CAP SendChargingInformation operation 11.2.20 CAP PlayAnnouncement operation 11.2.21 CAP PromptAndCollectUserInformation operation 11.2.22 CAP SpecializedResourceReport operation 11.2.23 Operation Timers QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary
Page:
11.3 11.4
120126 120126
12 13
13.1 13.2 13.3
121127 121127
121127 122128 124130
14 15
PERFORMANCE REQUIREMENTS
126133
16 APPENDIX 2: ALGORITHM FOR HANDLING CAMEL DATA RECEIVED AT THE GMSC 130137
Table of Figures
FIGURE 1 - CAMEL ARCHITECTURE FIGURE 2 - SUNNY DAY CALL WITH A PARTY DISCONNECT FIGURE 3 - WARNING TONE PLAYS FIGURE 4 - INTERVAL TIMER EXPIRES, CALL IS DISCONNECTED FIGURE 5 - TWO APPLY CHARGING OPERATIONS FIGURE 6 - SWITCH BASED ANNOUNCEMENT FIGURE 7 - IP BASED ANNOUNCEMENT FIGURE 8 - MOBILE TERMINATION WITH CAMEL AND ANY TIME INTERROGATION FIGURE 9 - TERMINATION WITH GSMSCF MODIFIED NUMBER FIGURE 10 - TERMINATION WITH UNMODIFIED NUMBER FIGURE 11 - CALL FORWARDING UNCONDITIONAL FIGURE 12 - CALL FORWARDING ON MOBILE STATION NOT REACHABLE (PART 1) FIGURE 13 - CALL FORWARDING ON MOBILE STATION NOT REACHABLE (PART 2) FIGURE 14 - CAMEL CALL FORWARDING FIGURE 15 - CALL FORWARDING AT THE VMSC FOR A CAMEL SUBSCRIBER FIGURE 16 - VLR PROCESSING STRUCTURE IN CAMEL SPEC 03.78 FIGURE 17 - TERMINATING ARCHITECTURE FIGURE 18 - CALL FORWARDING STRUCTURE IN CAMEL SPEC 03.78 152 162 172 182 192 202 212 232 242 252 262 272 282 292 302 402 462 542
Page:
Issue: 4 7
1 Feature Description
1.1 Scope
This requirements document specifies CAMEL requirements for the 3G UMTS MSC. The requirements cover mainly feature server functionality, but there is an impact on the LMS, and so the level of this document is technically 3G-MSC.
1.2
Guide to Requirements
Each requirement for the 3G MSC is specified using a RADIX macro. Each RADIX macro is individually labeled " < R-FSD19337.P-XYZV1V1>" ".P" represents the CAMEL phase, e.g., ".2" signifies CAMEL phase 2. "XYZ" is a unique number that identifies the requirement. "V1" signifies the first version of a requirement. Bold text specifying the requirement Notes sections contains information for reference, but is not a normative part of the requirement. used to reference the inputs used for this requirement owner/author of the requirement used to provide a keyword describing the functional area of the requirement.
1.3
20-feb-02
1.4
Benchmark Dates
Original Estimated Date Updated Estimated Date Actual Date Comments
Page:
Issue: 4 8
Benchmark Definition Champion Assigned FDT Assigned Critical Reviewers Assigned Draft Available Review (desktop) Draft 2 Available Review Ready for Approval
Actual Date
Comments
1.5
Open Issues
Date Issue Resolution and date
1.6
1.7
Competitive Information
CAMEL has had a high profile with the advent of prepaid services in GSM networks. Prepaid for voice, short messages and packet data continues to be in demand by network operators. It is safe to say that without a CAMEL product, many operators would consider doing business with Lucent a non-starter.
1.8
CAMEL has known interactions with other GSM standard features such as standards supplementary services, Optimal Routing and Call Completion to Busy Subscriber. Some of these interactions will be detailed in this requirements document.
1.9
Acknowledgements
The author would like to thank all of the people who provided input and advice about the CAMEL product, including all of the systems engineers, developers and feature testers of the 5ESS CAMEL and ETSI INAP products.
Page:
Issue: 4 9
3G 3G MSC
3G MSC/VLR 3G SGSN
Intelligent Network The entire set of network elements used for providing Intelligent Network services, including a Service Swithcing Point, a Service Control Point and a Service Management Point. UMSC UMTS Mobile Switching Center describes a UMTS Core Network (CN) element that contains both the 3G MSC and 3G SGSN functions. UMSC is not described in this document.
Vocoder/Vocoding The functional element/process of converting audio signals into low bit rate encoded signals taking into account, Voice Activity, Background Noise, etc. The process exists in the TX side of the bearer traffic.
Page:
CLIP CLIR COLP COLR CSE DNS EIR ETSI FCAP FTP GGSN GPRS GSM gsmSCF gsmSRF gsmSSF HLR IAM IMSI IMUI IN INAP IP IP ISDN Iu IWF LA LAC LAI LCS LM MAP MM MO MS MSC MT OAM OAM&P NNI OMC OSA PCM PLMN PS PSPDN PSTN PVC QoS RAB RANAP RNC RNS
Calling Line Identity Presentation Calling Line Identity Presentation Restriction Connected Line Identity Presentation Connected Line Identity Presentation Restriction CAMEL Service Environment (logical Service Control Point) Domain Name Server Equipment Identity Register European Telecommunications Standards Institute Fault, Configuration, Accounting, Performance File Transfer Protocol Gateway GPRS Support Node Generalize Packet Radio Services Global System for Mobile Communications CAMEL Service Control Function CAMEL Specialized Resource Function CAMEL Service Switching Function Home Location Register ISUP Initial Address Message International Mobile Station Identification International Mobile User Identification Intelligent Network Intelligent Networking Application Part Internet Protocol Intelligent Peripheral Integrated Services Digital Network Interface between the UTRAN and the Core Network Inter-working Function Location Area Local Area Code Location Area Identification Location Services Location Management Mobile Application Part Mobility Management Mobile Origination Mobile Station Mobile Switching Center Mobile Termination Operation, Administration and Maintenance Operation, Administration, Maintenance & Provisioning Network to Network Interface Operations Management Center Open Services Architecture Pulse Code Modulation Public Land Mobile Network Packet Switched Packet Switched Public Data Network Public Switched Telephone Network Permanent Virtual Circuit Quality of Service Radio Access Bearer Radio Access Network Application Part Radio Network Controller Radio Network System Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 11
RNTI RRC RTCP RTP SoLSA SSCF SSCOP SCF SCP SGSN SMP SMS SMS SMSC SN SNMP SRF SRNS SS7 SSF SSP STP TCP TFTP TMSI UCN UDI UNI URA UTRAN VLR VMS UE UEA UIA VLAN UP USSD
Radio Network Temporary Identifier Radio Resource Control Real Time Control Protocol Real Time Protocol Support of Localized Service Area Service Specific Convergence Function Service Specific Connection Oriented Protocol Service Control Function Service Control Point Serving GPRS Support Node Service Management Point Service Management System (Lucent SMP) Short Message Service Short Message Service Center Service Node Simple Network Management Protocol Specialized Resource Function Serving RNS Signaling System 7 Service Switching Function Service Switching Point Signal Transfer Points Transmission Control Protocol Trivial File Transfer Protocol Temporary Mobile Station Identification UMTS Core Network User Data Input User to Network Signaling UTRAN Routing Area UMTS Terrestrial Radio Access Network Visitor Location Register Voice Messaging Service User Equipment, same as MS in GSM UMTS Encryption Algorithm UMTS Integrity Algorithm Virtual Local Area Network User Plane Unstructured Supplementary Service Data
MMRS
System Requirements Document SoftSwitch Server Platform Trunk Access Gateway Transcoder Traffic Processing Unit Wireless Access Gateway Wireless Signaling Gateway.
Overview
This document contains the feature level requirements for CAMEL phase 2 for the 3G UMTS MSC. CAMEL (Customised Application for Mobile network Enhanced Logic) is a GSM and 3GPP standardized way of allowing mobile subscribers to access IN based services while either in their home or visited networks.
2.1
Scope
The scope of this Feature Specification Document is the functional behavior of the entire MSC for the support of CAMEL. The FSD is designed to give a "black box" view of CAMEL functionality from an MSC perspective, but in addition, it will borrow heavily from the conceptual framework provided by the CAMEL standards, which split the MSC into two functional areas.
2.2
The CAMEL standards -- ETSI GSM 03.78 for CAMEL phases 1 and 2 and 3GPP 23.078 for CAMEL phase 3 -- split the MSC logically into two functional entities: 1. The Call Control Function (CCF) provides call/service processing and control. Basic CCF functionality to support call processing is specified in the Basic Call specifications 03.18 (releases 98 and earlier) and 23.018 (release 99 and later). CAMEL procedures are called from the CCF to determine if the any CAMEL processing is required. 2. The Service Switching Function (SSF or gsmSSF) is a functional entity that interfaces the CCF in the MSC/GMSC to the Service Control Point (SCP). In the CAMEL standards the SSF is referred to as the gsmSSF to differentiate it from the SSF of wireline IN standards and the SCP is referred to as the gsmSCF.
2.3
Intra-MSC Messaging
Messages between the CCF and gsmSSF processes on the MSC cannot be feature tested, although such intra-MSC messaging will be discussed as part of this specification for specifying feature level behavior. Since the software architecture will include internal MSC processes, the design will make use of intra-MSC messages between the CCF and SSF. From a feature test perspective, however, only messages external to the MSC are testable.
2.4
Intra-MSC States
Although internal states are not formally testable, this FSD will use the concept of states as a way to aid precision and brevity in writing requirements as well as to facilitate understanding. The states used for the Service Switching Function will correspond to the states used in the CAMEL standards. Many requirements will have the format: Initial State: Input: QDI ID: 19337 Date: November 18, 2002
Page:
Issue: 4 13
Conditions: Action: Next State: The reason for introducing states is to maintain consistency with the CAMEL standards and to avoid needless repetition. For example, each of about 20 requirements could begin with the statement: "After a SETUP message has been received and an InitialDP operation has been sent to an SCP, but before a Connect, Continue or ReleaseCall operation has been received back from the SCP, " Or we can use a state, called "Waiting For Instructions" which corresponds to the above condition, and introduce the requirement with the statement: Initial State: Waiting for Instructions.
2.5
There are two levels of error checking -- syntactical and semantic. Syntactical level errors occur when required information elements, as specified in ETSI GSM 09.78 or 09.02, are missing or out of range, or when additional information elements are included that are not according to GSM specifications. Semantic level errors occur when the contents of the information elements are not appropriate for the particular context or conditions, as specified in ETSI GSM 03.78 or 03.18. Syntactical checking will be done by the decoding functions, and the specific errors will be specified in the protocol sections, i.e., for CAP and MAP. Semantic errors will be discussed in sections that deal with the actions required when operations are received that have passed syntactical checks.
2.6
Some of the requirements in this FSD will be testable as stand alone entities, e.g., a requirement for being able to provision certain subscriber data. Other requirements will be part of larger call scenarios, and feature tests will need to be written that encompass multiple requirements. An example would be a prepaid call scenario involving the running of timers and the playing of warning tones as credit expiration approaches. In some cases, one requirement may result in multiple feature tests, particularly where more than one state is combined because of identical processing.
Page:
Issue: 4 14
CAMEL Architecture
gsmSCF
(SCP)
HLR
MAP CAP MAP
HPLMN VPLMN
Roaming Leg VLR record CAMEL
MAP
CAP MAP
Incoming Call
Gateway v MSC
info
VMSC/VLR
Forwarding Leg
gsmSSF
Figure 1 - CAMEL architecture The Visited MSC (VMSC) can be either in the home network or a visited network; the latter case is shown in the diagram. CAMEL can be invoked for mobile originations, mobile terminations or call forwarding. The VMSC is responsible for mobile originations and conditional call forwarding (call forwarding on busy, no reply and mobile station not reachable in the case of no paging response). VMSC call forwarding is referred to as late call forwarding. The GMSC is responsible for mobile terminations and call forwarding unconditional and some cases of call forwarding on mobile station not reachable. GMSC call forwarding is referred to as early call forwarding.
4 4.1
In many cases, there will be a direct correlation between internal CCF to gsmSSF messages and external CAP messages. In some cases however, the internal messages will not result in or be the result of an external stimulus.
4.2
The following figures show the call flows for a typical prepaid SIM service.
Page:
Issue: 4 15
MSC
CCF
SETUP (A)
CSE
gsmSCF
InitialDP (DP2) RRBE(7N, 9A-N, 9B-N) CallInformationRequest
gsmSSF
Int_Inv_gsmSSF
Int_Continue
ApplyCharging(interval) Continue
Int_DP_O_Answer
EventReportBCSM (7-N)
Start timer: (Tcp - 30) seconds
DISCONNECT(A)
REL (B)
Int_DP_O_Disc(A)
Stop Timer
Page:
Issue: 4 16
MSC
CCF
SETUP (A)
CSE
gsmSCF
InitialDP (DP2) RRBE(7N, 9A-N, 9B-N) ApplyCharging(interval) FurnishChargingInfo
gsmSSF
Int_Inv_gsmSSF
Int_Continue
Int_DP_O_Answer
In-band tone(A)
Int_Apply_Tone
DISCONNECT(A)
Int_DP_O_Disc(A)
REL (B)
Page:
Issue: 4 17
MSC
CCF
SETUP (A)
CSE
gsmSCF
InitialDP (DP2) RRBE(7N, 9A-N, 9B-N) ApplyCharging(intvl, rel=y) Continue EventReportBCSM (7-N)
gsmSSF
Int_Inv_gsmSSF
Int_Continue
Int_DP_O_Answer
Int_Release
DISCONNECT(A)
ApplyChargingReport
Page:
Issue: 4 18
M SC
CCF
SE TU P (A )
C SE
g sm S C F
In itialD P (D P 2) R R B E(7N , 9 A -N , 9 B -N ) A pply C ha rging(intv l, rel= n ) C o ntinu e E ventR eportB C S M (7-N )
S tart tim er: T cp - 3 0
g sm SS F
In t_In v_g sm S S F
IA M (B ) A N M (B )
In t_ C on tinue
In t_ D P _ O _ A n sw er
Int_A p ply_T one S tart tim er:3 0 second s T cp ex pires, R elease = N o S tart d elta tim er S top delta tim er
In-band tone(A )
D ISC O N N EC T(A )
R E L (B )
Page:
Issue: 4 19
MSC
CCF
SETUP (A)
gsmSSF
gsmSCF
CSE
Int_Inv_gsmSSF
_get_annc_resrc _play_annc(id)
_rt_to_annc
PROGRESS(A)
_Annc_Complete _annc_complete
Int_Continue
Int_DP_O_Answer
EventReportBCSM (7-N)
Start timer: (Tcp - 30) seconds
DISCONNECT(A)
REL (B)
Int_DP_O_Disc(A)
Stop Timer
Page:
Issue: 4 20
CCF
SETUP (A)
MSC
gsmSSF
gsmSCF
InitialDP (DP2)
CSE
Int_Inv_gsmSSF
_route_to_ip
IAM(IP)
PROGRESS(A)
EstablishTemporaryConnection
ANM(IP)
CONNECT(A) REL(IP)
_disc_to_ip
Int_Continue
DisconnectForwardConnection RRBE(7N, 9A-N, 9B-N) CallInformationRequest FurnishChargingInfo ApplyCharging(interval) Continue EventReportBCSM (7-N)
Start timer: (Tcp - 30) seconds
Int_DP_O_Answer
DISCONNECT(A)
REL (B)
Int_DP_O_Disc(A)
Stop Timer
Page:
does not return a PROGRESS to the mobile indicating busy, since a CONNECT has already been sent. Instead, the MSC returns a DISCONNECT with cause = 17 (User Busy) to the mobile.
CCF
SETUP (A)
MSC
gsmSSF
InitialDP
gsmSCF
CSE
Int_Inv_gsmSSF
_route_to_ip
IAM(IP)
PROGRESS(A)
EstablishTemporaryConnection
ANM(IP)
CONNECT(A) REL(IP)
_disc_to_ip
IAM (B)
DISCONNECT(A)
Int_Continue
Int_DP_O_Busy Int_DP_O_Disc(A)
ApplyCharging(interval) Continue
CPG (B-party Busy) REL (B) EventReportBCSM (9A-N) CallInformationReport ApplyChargingReport Prearranged End
4.3
Page:
Issue: 4 22
HLR
2.SRI(1)
8: ATI Ack
gsmSCF_1
10.SRI(2) 4.InitialDP 11: PRN 6: PSI 9. ApplyCharging, Continue 14. IAM (MSRN) (15. ResumeCallHandling*) 13.SRIAck (MSRN)
3.SRIAck (T-CSI)
1.IAM
GMSC/ gsmSSF
VMSC
Page:
Issue: 4 23
IAM
CCF
gsmSSF SRI
HLR
SCP
VMSC
InitialDP Connect(CMN)
Int_Connect
IAM
Figure 10 - Termination with gsmSCF modified number Legend: T-CSI = Terminating CAMEL Subscription Information CMN = CAMEL Modified Number, or gsmSCF translated number
Page:
Issue: 4 24
IAM
CCF
HLR
SCP
VMSC
Int_Inv_gsmSSF
InitialDP Continue
Int_Continue
SRI(2) PRN SRI ack (MSRN) IAM (MSRN) PRN ack (MSRN)
4.4
CAMEL interactions with call forwarding can take place at the GMSC (Call Forwarding Unconditional and Call Forwarding on Mobile Station Not Reachable) or at the VMSC (Call Forwarding on Busy, Call Forwarding on No Reply and some instances of Call Forwarding on Mobile Not Reachable). There are two types of call forwarding in the CAMEL context: 1) standard GSM call forwarding, e.g., Call Forwarding Unconditional or Call Forwarding on Busy; and 2) CAMEL call forwarding, which occurs on a GMSC when a combination of events occur, including the gsmSCF supplying call forwarding parameters. This is described in more detail below.
Page:
Issue: 4 25
gsmSSF
HLR
SCP
C-Exchange
Int_Inv_gsmSSF
InitialDP (FTN, Forwarding flag, DP2) ApplyCharging RRBE (7N, 9N-A,B) Continue Int_Continue IAM ANM Int_DP_O_Answer EventReportBCSM(7N) REL
Int_DP_O_Disconnect
Page:
Issue: 4 26
4.4.2 Termination with GSM Call Forwarding on Mobile Not Reachable at GMSC
The following two figures show the CAMEL interaction for a terminating call where the gsmSCF arms a detection point for busy, which also serves as a detection point for the invocation of Call Forwarding on Not Reachable (CFNRc) and Call Forwarding on No Reply (CFNRy); the latter is applicable for Optimal Routing. For this scenario, there are two transaction active -- one for the termination and one for the call forwarding invocation. Theoretically, there could be two gsmSCFs involved, although in practice, one gsmSCF may handle both dialogues, and the latter is shown in the scenario.
HLR
CFNRc gsmSCF
VMSC
InitialDP (DP12) ApplyCharging (for termination) RRBE (13N, 14N, 15N, 17N-A,B) Continue
Int_Continue
Page:
Issue: 4 27
CCF (GMSC)
HLR SCP InitialDP (DP2, FTN, RedirectingNo=C) ApplyCharging (for CF leg) RRBE (7N, 9N-A,B) Continue Int_Continue IAM (C) ANM (C) Int_DP_O_Answer EventReportBCSM(7N)
Int_Inv_gsmSSF Int_DP_T_Answer
REL (C)
Int_DP_O_Disconnect Int_DP_T_Disconnect
Page:
Issue: 4 28
HLR
SCP1
SCP2 C-Exch
SRI SRI ack (T-CSI, O-CSI) Int_Inv_gsmSSF InitialDP(DP12) Connect(CMN, redirecting info, O-CSI applicable) Int_Connect
Int_Inv_gsmSSF
CPG
InitialDP(DP2) ApplyCharging RRBE (9N-A,B) Continue Int_Continue IAM ANM Int_DP_O_Answer REL Int_DP_O_Disconnect EventReportBCSM(9N-B) ApplyChargingReport
Prearranged end
Prearranged end
Figure 15 - CAMEL Call Forwarding
Page:
Issue: 4 29
gsmSSF
SCP
MS
IAM
5 5.1
Unless otherwise indicated, the standards documents referenced in this specification are highlighted in bold below. The standards referenced are a combination of release 98 and release 99 standards. This combination reflects the belief that for CAMEL Phase 2, the release 98 and release 99 standards are equivalent. The release 98 standards provide a more precise definition of CAMEL Phase 2 because one need not filter out extraneous CAMEL Phase 3 information. Release 99 standards are used either when it is easy to filter out the CAMEL Phase 3 information (e.g. 22.078) or when the standard is shared with other u01.03 features. The relevant standards for CAMEL phase 2 are: # 02.78 v7.1.0 -- CAMEL Phase 2 (release 98), Stage 1 (services description) # 03.78 v7.6.1 -- CAMEL Phase 2 (release 98), Stage 2 (architecture and information flows) # 09.78 v7.1.0 -- CAMEL Phase 2 (release 98), Stage 3 (protocol) QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 30
Page:
# 03.18 v7.4.0 -- Basic Call (release 98) # 04.08 v7.d.0 -- DTAP (release 98) # 08.08 v7.7.0 -- BSSMAP (release 98) The equivalent CAMEL phase 3 and release 99 standards are: # 22.078 v3.8.0 -- CAMEL Phase 3 (release 99), Stage 1 (services description) # 23.078 v3.9.0 -- CAMEL Phase 3 (release 99), Stage 2 (architecture and information flows) # 29.078 v3.7.0 -- CAMEL Phase 3 (release 99), Stage 3 (protocol) # 23.018 v3.8.0 -- Basic Call (release 99) # 24.008 v3.8.0 -- DTAP (release 99) # 29.002 v3.9.0 MAP Spec 3GPP standards for release 99 may be found at the following url: http://www.3gpp.org/ftp/Specs/
5.2
The following section provides a guide to the SDLs contained in 03.78. The SDLs contain both processes and procedures. A process is considered to be running at all times, waiting for input messages, either internal or external. A procedure is called from a process or from another procedure. When it is called it is spawned and when it is done with its processing it dies. A procedure may have internal states and inputs, but it is essentially temporary.
OG_CALL_SETUP_MSC* OCSM OCSM OCSM OCSM OCSM OCSM(35), CAMEL_OCH_MSC_ ANSWER(03.78) OCSM OCSM CAMEL_OCH_MSC_INIT (03.78), CAMEL_OCH_MSC1 (03.78), CAMEL_OCH_MSC2 (03.78), CAMEL_OCH_MSC_DISC2 (03.78) CAMEL_OCH_ETC (03.78), CAMEL_OCH_CTR (03.78)
SEND_ALERTING_IF_REQUIRED, SEND_ACCESS_CONNECT_IF_REQUIRED** *OCSM(OG_CALL_SETUP_MSC) ** Non CAMEL Procedures defined in 023.018 QDI ID: 19337 Date: November 18, 2002
Page:
Issue: 4 31
OG_CALL_SUBSCRIPTION_CHECK_VLR Receives initial input message (Send Info for Reconnected Call) from: CAMEL_OCH_MSC1, CAMEL_OCH_MSC2, CAMEL_OCH_MSC_DISC2
5.2.2 Processes and Procedures for Terminating and Forwarded Calls Name of CAMEL Procedure Calling Procedure Name ( In 23.018 unless
CAMEL_SET_ORA_PARAMETERS CAMEL_Start_TNRy CAMEL_Stop_TNRy CAMEL_MT_GMSC_INIT CAMEL_MT_GMSC_NOTIFY_CF CAMEL_MT_GMSC_ANSWER CAMEL_MT_GMSC_DISC1, CAMEL_MT_GMSC_DISC2 CAMEL_MT_GMSC_DISC3 (CAMEL Phase 1) CAMEL_MT_GMSC_DISC4 CAMEL_MT_GMSC_DISC5 CAMEL_MT_GMSC_DISC6 CAMEL_OCH_MSC_DISC3 (CAMEL Phase 1) CAMEL_OCH_MSC_DISC4 CAMEL_OCH_MSC_DISC1, CAMEL_OCH_MSC_DISC2 CAMEL_CF_MSC_INIT CAMEL_CF_MSC_ANSWER CAMEL_OCH_MSC1 CAMEL_OCH_MSC2 CAMEL_MT_ETC, CAMEL_MT_CTR
other document specified) MT_GMSC MT_GMSC, MT_CF_MSC MT_GMSC, MT_CF_MSC Obtain_Routeing_Address Obtain_Routeing_Address MT_GMSC MT_GMSC, CAMEL_MT_GMSC_ ANSWER(03.78) MT_GMSC, Obtain_Routeing_Address
MT_GMSC MT_GMSC MT_CF_MSC, MT_CF_MSC, CAMEL_CF_MSC_ANSWER(03.78) MT_CF_MSC MT_CF_MSC MT_CF_MSC MT_CF_MSC CAMEL_MT_GMSC_INIT(03.78), CAMEL_MT_GMSC_DISC2(03.78), CAMEL_MT_GMSC_DISC4(03.78) CAMEL_MT_GMSC_DISC5(03.78) CAMEL_CF_MSC_INIT(03.78) ICH_MSC CAMEL_MT_ETC(03.78), CAMEL_CF_ETC(03.78) CAMEL_MT_ETC(03.78), CAMEL_MT_CTR(03.78), CAMEL_CF_ETC(03.78), CAMEL_CF_CTR(03.78) CAMEL_MT_GMSC_INIT(03.78), CAMEL_MT_ETC(03.78), CAMEL_MT_CTR(03.78), CAMEL_CF_ETC(03.78), CAMEL_CF_CTR(03.78) Page: Issue: 4 32
SEND_ACM_IF_REQUIRED**
**Non CAMEL procedure Name of CAMEL Procedure CAMEL_SET_SOA Calling Procedure Name(In 23.018
document specified) unless other
PRN_VLR
5.3
Rather than reproduce an entire standards specification, this FSD will follow a high level approach that parallels the CCF and SSF states as specified in 023.018 and 03.78 respectively. Under the requirement for a particular CCF state, any procedures that are listed in bold will be considered covered under that requirement. Some of the called procedures have their own internal states and in some cases, particularly in the gsmSSF state machine, this FSD will specify requirements dealing with those states. The aim of the FSD is to tie requirements to external events, whenever possible, in order to aid feature testers in grouping requirements into scenarios and mapping feature tests to requirements.
5.4
Basic Call Control functionality (CCF) is specified in ETSI 03.18 for releases through release 98 and in 3GPP 23.018 for release 99 and later. These documents specify where call control calls CAMEL specific procedure. CAMEL procedures called by the CCF are specified in ETSI 03.78 and 3GPP 23.078.
5.5
The gsmSSF state machine is specified in ETSI 03.78 (through release 98) and 3GPP 23.078 (releases 99 and beyond).
6 6.1
ETSI spec 03.08 and 3GPP spec 23.008 contain the data requirements for the HLR and VLR. This FSD will cover VLR data requirements specific to CAMEL. <R-FSD19337.2-2V1.01> The following data is required to be stored on the VLR for CAMEL subscribers. 1. Originating CAMEL subscription information (O-CSI) 2. Supplementary Services notification subscription information (SS-CSI) Notes: This data is sent along with subscriber data to the VLR from the HLR at the time of location update. References: 03.78 section 6; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 33
<End of R-FSD19337.2-2V1> < R-FSD19337.2-4V1.01> Once a subscriber registers on the VLR with a certain level of CAMEL support, that level must be stored for a subscriber. Notes: For example, an MSC may support CAMEL phase 2, but a subscriber may roam in from network that only supports CAMEL phase 1. For this subscriber, only CAMEL phase 1 functionality and operations are applicable. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-4V1>
7 7.1
< R-FSD19337.2-7000V1.02> The MSC/VLR will be able to restrict CAMEL service for roamers. The MSC will store a provisionable and updateable table that can screen incoming roamers for CAMEL at a country level and a PLMN level. The entries in the table can be populated as either "allowed" or "restricted". If CAMEL service is restricted -- because the subscribers home is in a network or country that is restricted -- then the VLR will not indicate CAMEL support in the UpdateLocation operation sent to the HLR, i.e., all phases in the SupportedCamelPhases element of the "vlr-Capability" parameter shall be set to not supported. Notes: 1. It is expected that the country list will be checked first. If the country is allowed or is not restricted, then the PLMN list will be checked. 2. This table will be checked once during location update. If the table is updated during a location update for a subscriber, the restrictions that apply when the data is read will apply. If the restriction data is modified after a subscriber registers, the restriction status applied at the time of registration will still apply until another location registration requiring HLR action occurs. This means that it is not required that, after an update, all VLR records be searched and that remedial action be taken for all subscribers from the affected PLMN or country. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). In version 1.02 removed restriction based on HLR (mr=17999). Owner: Andrew McClurg Keyword: Operations and Maintenance <End of R-FSD19337.2-7000V1>
7.2
Location Numbers
<R-FSD19337.2-7010V1.01> Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 34
Page:
The MSC/VLR will have a table that will have as input the location area and Service Area ID of a subscriber and as output an E.164 location number. The location number will be used to populate the locationNumber field of the InitialDP message. The table will be updatable via administrative terminal, will have insert, delete, update and read capabilities and will contain at least 500 entries. Notes: 1. Thus, for example, a Service Area ID may indicate north Naperville, and this can be mapped to an ISDN number such as 979-1234. 2. This will allow SCPs that are currently set up to use location number to continue to do so without having to modify their service logic to deal with the new CAMEL information in the InitialDP which includes location area and cell ID or Service Area ID. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: Operations and Maintenance <End of R-FSD19337.2-7010V1>
7.3
<R-FSD19337.2-7020V1V1.01> The MSC/VLR will have parameter that will indicate whether CAMEL is active and the particular phase of CAMEL that is supported. This parameter will be updatable via administrative terminal but will be password protected with a password controlled by Lucent. Notes: 1. This could be accomplished by having a single parameter with values: 0 - CAMEL not supported; 1 - CAMEL phase 1; 2 - CAMEL phase 2; 3 - CAMEL phase 3, etc. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: Operations and Maintenance <End of R-FSD19337.2-7020V1V1>
7.4
The CAMEL standards are more specific as to the encodings of network operator specific (NOS) parameters than are the corresponding ETSI CS-1 INAP standards. However, there are some NOSs in CAMEL that are left completely up to network operator discretion, as follows: 1. fCIBillingChargingCharacteristics of the FurnishChargingInformation 2. correlationID of the EstablishTemporaryConnection and AssistRequestInstructions operations 3. sCFID of the EstablishTemporaryConnection and AssistRequestInstructions operations In order to expedite the introduction of CAMEL service into a network, some default values for these parameters have been chosen by Lucent -- these are specified in the CAP protocol section requirements of this document. QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 35
Page:
<R-FSD19337.2-7030V1.01> It shall be possible, for each of the NOS parameters in the list below, to have its value for a particular network operator set at the time of switch initialization. 1. fCIBillingChargingCharacteristics of the FurnishChargingInformation 2. correlationID of the EstablishTemporaryConnection and AssistRequestInstructions operations 3. sCFID of the EstablishTemporaryConnection and AssistRequestInstructions operations Notes: 1. Default values are specified in the CAP protocol requirements section. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: Operations and Maintenance <End of R-FSD19337.2-7030V1>
7.5
The internal gsmSRF will be provided within the UMTS MSC by the Lucent Media Server (LMS). The feature server communicates with the LMS using DSI messages, and specifies announcements to be played using announcement identifiers understood by the LMS. The gsmSCF also sends announcement identifiers to the gsmSSF within PlayAnnouncement or PromptAndCollectUserInformation operations. In order to provide flexibility, it will be useful to maintain a table on the MSC that maps gsmSCF announcement IDs to LMS announcement IDs. <R-FSD19337.2-7040V1.02> The MSC shall have a table that maps gsmSCF announcement IDs to one or more LMS announcement IDs. The table shall be provisionable and modifiable via adminstrative terminal and shall hold a minimum of 500 entries. Notes: Provisioning should allow mapping from gsmSCF announcement ID to up to 6 LMS announcement Ids. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). In version 1.02, clarified that mapping is to one or more LMS Ids (mr=17951) Owner: Andrew McClurg Keyword: Operations and Maintenance <End of R-FSD19337.2-7040V1> <R-FSD19337.2-7045V1.02> The MSC shall have a table that maps gsmSCF Tone IDs to LMS Tone IDs. The table shall be provisionable and modifiable via adminstrative terminal and shall hold a minimum of 30 entries. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: Added new as v1.02 to specify needed tone mapping (mr=17951) Owner: mpicha Keyword: Operations and Maintenance QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 36
<End of R-FSD19337.2-7045V1>
7.6
Populating Global Title tables for Global Title Translation (GTT) will be done by the basic call team. CAMEL makes use of GTT for sending CAP messages to gsmSCFs (SCPs). Global Title addresses for gsmSCFs in supported networks must be populated in the Global Title tables.
8 8.1
When a translated number is returned from an SCP, it is useful to be able to analyze it with different digit analysis tables than is used for the original dialed number. In general, an entry point into a digit analysis tree is called a digit analysis selector (DAS). A separate DAS is required for SCP translated numbers. <R-FSD19337.2-7100V1.01> It shall be possible to specify a unique digit analysis selector for translated numbers returned from a gsmSCF. References: Engineerng Judgement Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-7100V1>
8.2
Emergency Calls
An emergency call can be distinguished in two ways: 1. The 3G-MSC receives a CM Service Request with request type set to Emergency Call, followed by an Emergency Setup (ESETUP) message. 2. Digit analysis of the called party number determines that the call is an emergency call. <R-FSD19337.2-7150V1.01> CAMEL is not applicable to an Emergency Setup call. Notes: This requirement is only applicable to case one above. Any call identified as an emergency call as a result of digit analysis will be subject to CAMEL treatment. References: 03.78 section 1 Feature ID: 50.100 Modification Reason: Added new in version 1.01 (mr=17799). Owner: mpicha Keyword: gsmSSF <End of R-FSD19337.2-7150V1>
8.3
This section deals with functionality that is initiated in the Call Control Function (CCF) as specified in ETSI GSM 03.78. Classifying requirements as being CCF initiated or Service Switching Function (SSF) initiated is designed to provide a correspondence with the standards. The QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 37
Page:
requirements themselves are written from a whole MSC perspective, and requirements in this section may have SSF impacts.
Page:
3. CAMEL_OCH_MSC_INIT (03.78 figure 10). CAMEL_OCH_MSC_INIT may call the following procedures: a) CAMEL_OCH_ETC (03.78 figure 17). Depending on whether ISUP or ISDN signaling is used to an IP or Assisting SSP, this procedure can send and receive ISUP or ISDN signaling messages. b) CAMEL_OCH_CTR (03.78 figure 18). c) CAMEL_OCH_MSC_DISC1 (03.78 figure 14) d) CAMEL_OCH_MSC_DISC2 (03.78 figure 15) Next state: Wait For ACM Notes: 1. Procedure OG_Call_Setup_MSC sends an internal message to process OCH_VLR which calls procedure OG_Call_Subscription_Check_VLR. 2. OG_Call_Subscription_Check_VLR performs various checks of subscriber data, but before outgoing call barring checks are made, a call is made to procedure CAMEL_OCH_VLR. 3. The purpose of CAMEL_OCH_VLR is to allow the procedure CAMEL_OCH_MSC_INIT to run before call barring checks are made, in case the SCP returns a different routing number than was originally dialed. After the actual routing number has been determined, then control is returned to OG_Call_Subscription_Check_VLR which does call barring checks and returns an internal message to the MSC indicating the outcome of the checks, i.e., either positive or negative. 4. CAMEL_OCH_MSC_INIT can initiate an SCP dialogue, the results of which can be: # Continue with the call as dialed. # Route the call to a new SCP supplied number. # Disallow the call (i.e., release the connection to the A-party). When CAMEL_OCH_MSC_INIT returns, a resulting return value of "Pass" means that either of the first two options above occurred. Call control simply proceeds to route the call to whatever number is has been returned -- either the originally dialed number or a new SCP supplied number (translated number). A return value of "Fail" means that the call is to be torn down. References: 03.78; 023.018 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-20V1> The following list describes the inputs and outputs of CAMEL_OCH_MSC_INIT: # External Input: Release from the mobile station # External Output: Progress and Release towards the mobile station # Internal Input: Int_gsmSSF_Invoked, Int_Error, Int_Release_Call, Int_Continue, Int_Connect, Int_Establish_Temporary_Connection, Int_Connect_To_Resource, # Internal Output: Int_Invoke_gsmSSF(O-CSI), Int_DP_Collected_Info, Int_O_Exception, Int_DP_O_Abandon The following figure shows the procedure calls and internal messages used by the procedures involved with VLR processing for the previous requirement. The labels at the tops of the lines represent process and procedure names. The dashed lines represent procedure calls and returns with return values noted.
Page:
Issue: 4 39
OCH_VLR
gsmSSF
Complete Call
CAMEL_OCH _MSC_INIT
Int_Invoke_ gsmSSF
CAP InitialDP
<R-FSD19337.2-40V1.01> Procedure: Outgoing_Call_Setup_MSC (023.018 Figure 8) Initial State: Wait_For_ACM External Input: Address Complete (e.g., ISUP ACM) Action: Processing will be as in 023.018 figure 8, Procedure Outgoing_Call_Setup. 1. The procedure CAMEL_Start_TNRy (03.78 figure 19) is called to start the CAMEL no reply timer. This timer must be less than the network no reply timer (e.g., for ISUP). Next state: Wait_For_Answer References: 023.018, 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-40V1>
<R-FSD19337.2-50V1.01> Procedure: Outgoing_Call_Setup_MSC (023.018 Figure 8) Initial State: Wait_For_Answer External Input: Answer (e.g., ISUP ANM) Action: Processing will be as in the following procedures: 1. 23.018 procedure Outgoing_Call_Setup (23.018 figure 8 sheets 4 and5). QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 40
Page:
2. The procedure CAMEL_Stop_TNRy (03.78 figure 20) is called to stop the CAMEL no reply timer. 3. Procedure CAMEL_OCH_MSC_ANSWER (03.78 figure 11): this procedure is called to notify the gsmSSF that an answer event has occurred and to await possible further instructions from the gsmSSF process. Next state: Wait_For_Clear (via Wait_For_Connect_Ack) Notes: 1. Procedure CAMEL_OCH_MSC_ANSWER is covered under the requirement for Wait_For_ACM state. That procedure can deal with disconnect or release events, meaning that procedures CAMEL_OCH_DISC1 or CAMEL_OCH_DISC2 may be called. Disconnect processing will be handled separately under the requirement for the Wait_For_Clear state in this 23.018 procedure (Outgoing_Call_Setup_MSC). 2. The Wait_For_Connect_Ack state is not considered in this context. References: 23.018, 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-50V1> <R-FSD19337.2-60V1.01> Procedure: Outgoing_Call_Setup_MSC (23.018 Figure 8) Initial State: Wait_For_ACM External Input: Connect (i.e., DTAP CONNECT) from B-party Action: Processing will be as in the following procedures: 1. 23.018 procedure Outgoing_Call_Setup (figure 8 sheets 4 and 5). 2. Procedure CAMEL_OCH_MSC_ANSWER (03.78 figure 11): this procedure is called to notify the gsmSSF that an answer event has occurred and to await possible further instructions from the gsmSSF process. Next state: Wait_For_Clear (via Wait_For_Connect_Ack) Notes: 1. This requirement deals with the case where the B-Party is a mobile subscriber on the same MSC. 2. As with the requirement for the Wait_For_Answer state, procedure CAMEL_OCH_MSC_ANSWER is called which can deal with disconnect or release events. Disconnect processing will be covered separately under the requirement for the Wait_For_Clear state in this same 23.018 procedure (Outgoing_Call_Setup_MSC). 3. The Wait_For_Connect_Ack state is not considered in this context. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-60V1> <R-FSD19337.2-70V1> Procedure: Outgoing_Call_Setup_MSC (23.018 figure 8) Initial State: Wait_For_ACM, Wait_For_Connect_Ack or Wait_For_Answer External Input: A-Party release (e.g., DTAP DISCONNECT) External Output: Release towards B-party (e.g., ISUP REL) Action: Processing will be as in the following procedures: QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 41
1. Outgoing_Call_Setup_MSC (23.018 figure 8) sheets 6 and 7. 2. CAMEL_OCH_MSC_DISC4 (03.78 figure 16): if CAMEL phase 2 is active for the subscriber. 3. CAMEL_OCH_MSC_DISC3 (03.78 Rel 97 figure 8.1-6): if CAMEL phase 1 is active for the subscriber. Next state: Null Notes: 1. The degree of CAMEL support is determined at the time of location registration. 2. From the perspective of CAMEL behavior, the states Wait_For_ACM, Wait_For_Connect_Ack and Wait_For_Answer are equivalent. There are CCBS checks that are performed by call control in the Wait_For_ACM state, but these are independent of CAMEL. References: 23.018; 03.78, 03.78 Rel 97 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-70V1> <R-FSD19337.2-80V1.01> Procedure: Outgoing_Call_Setup_MSC Initial State: Wait_For_ACM External Input: B-Party release (e.g,. ISUP REL) External Output: Release towards A-Party (e.g., DTAP DISCONNECT) Action: Processing will be as in the following procedures: 1. Outgoing_Call_Setup_MSC (23.018 figure 8) sheet 6. 2. CAMEL_OCH_MSC1 (03.78 figure 12): if CAMEL phase 2 is active for the subscriber and the release cause is other than "No answer from user". 3. CAMEL_OCH_MSC2 (03.78 figure 13): if CAMEL phase 2 is active for the subscriber and the release cause is "No answer from user". 4. CAMEL_OCH_MSC_DISC3 (03.78 Rel 97 figure 8.1-6): if CAMEL phase 1 is active for the subscriber. Next state: Null Notes: 1. The degree of CAMEL support is determined at the time of location registration. 2. CAMEL phase 2 adds event detection points for originating busy and no answer and for route select failure. References: 23.018; 03.78. 03.78 Rel 97 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-80V1>
<R-FSD19337.2-90V1> Procedure: Outgoing_Call_Setup_MSC Initial State: Wait_For_Connect_Ack or Wait_For_Answer External Input: B-Party release (e.g,. ISUP REL) External Output: Release towards A-Party (e.g., DTAP DISCONNECT) Action: Processing will be as in the following procedures: QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 42
1. Outgoing_Call_Setup_MSC (23.018 figure 8) sheet 7. 2. CAMEL_OCH_MSC1 (03.78 figure 12): if CAMEL phase 2 is active for the subscriber and the release cause is other than "No answer from user". # If the return from CAMEL_OCH_MSC1 is "reconnect" then procedure CAMEL_Stop_TNRy is called to stop the no reply timer. 3. CAMEL_OCH_MSC2 (03.78 figure 13): if CAMEL phase 2 is active for the subscriber and the release cause is "No answer from user". 4. CAMEL_OCH_MSC_DISC3 (03.78 Rel 97 figure 8.1-6): if CAMEL phase 1 is active for the subscriber. Next state: Null Notes: 1. The degree of CAMEL support is determined at the time of location registration. 2. CAMEL phase 2 adds event detection points for Busy, No Answer and Route Select Failure. 3. From the perspective of CAMEL behavior, the states Wait_For_ACM, Wait_For_Connect_Ack and Wait_For_Answer are equivalent. There are CCBS checks that are performed by call control in the Wait_For_ACM state, but these are independent of CAMEL. References: 23.018; 03.78, 03.78 Rel 97 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-90V1> <R-FSD19337.2-100V1.01> Procedure: Outgoing_Call_Setup_MSC Initial State: Wait_For_ACM, Wait_For_Connect_Ack, Wait_For_Answer or Wait_For_Clear Internal Input: Int_Release_Call -- sent by the gsmSSF when a CAP ReleaseCall operation is received from the SCP. External Output: 1. Release towards A-Party (i.e., DTAP DISCONNECT) 2. Release towards the B-Party (e.g., ISUP REL) Action: Processing will be as in Outgoing_Call_Setup_MSC (23.018 figure 8) sheets 6, 7 and 9. Next state: Null Notes: 1. The degree of CAMEL support is determined at the time of location registration. 2. From the perspective of CAMEL behavior, the states Wait_For_ACM, Wait_For_Connect_Ack and Wait_For_Answer are equivalent. There are CCBS checks that are performed by call control in the Wait_For_ACM state, but these are independent of CAMEL. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-100V1>
Procedure: Outgoing_Call_Setup_MSC Initial State: Wait_For_Answer Internal Input: Expiration of no reply timer (TNRy). External Output: 1. Release towards the B-Party (e.g., ISUP REL) 2. Release towards A-Party (i.e., DTAP DISCONNECT) unless a follow-on call is requested by the SCP. Action: Processing will be as in the following procedures: 1. Outgoing_Call_Setup_MSC (23.018 figure 8) sheet 8 and sheet 2 in the reconnect case. 2. CAMEL_OCH_MSC2 (03.78 figure 13). Next state: Null Notes: 1. The degree of CAMEL support is determined at the time of location registration. 2. From the perspective of CAMEL behavior, the states Wait_For_ACM, Wait_For_Connect_Ack and Wait_For_Answer are equivalent. There are CCBS checks that are performed by call control in the Wait_For_ACM state, but these are independent of CAMEL. 3. CAMEL_OCH_MSC2 handles the internally defined "no answer" event. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-110V1> <R-FSD19337.2-120V1.01> Procedure: Outgoing_Call_Setup_MSC Initial State: Wait_For_Clear External Input: B-Party Release (e.g., ISUP REL) External Output: 1. Release towards the A-Party (DTAP DISCONNECT) either from this procedure or from called procedure CAMEL_OCH_MSC_DISC2, except when a reconnect is to take place. Action: Processing will be as in the following procedures: 1. Outgoing_Call_Setup_MSC (23.018 figure 8) sheet 9 and in the reconnect case, sheet 2. 2. CAMEL_OCH_MSC_DISC2 (03.78 figure 13). Next state: Null Notes: 1. CAMEL_OCH_MSC_DISC2 is the same for both CAMEL phase 1 and phase 2. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-120V1>
<R-FSD19337.2-130V1.01> Procedure: Outgoing_Call_Setup_MSC Initial State: Wait_For_Clear External Input: A-Party Release (i.e., DTAP DISCONNECT) QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 44
External Output: 1. Release towards the B-Party (e.g., ISUP REL) either from this procedure or from called procedure CAMEL_OCH_MSC_DISC1. Action: Processing will be as in the following procedures: 1. Outgoing_Call_Setup_MSC (23.018 figure 8) sheet 9. 2. CAMEL_OCH_MSC_DISC1 (03.78 figure 12). Next state: Null References: 23.018; 03.78 Feature ID: 50.100 Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-130V1>
Page:
Issue: 4 45
HLR
ISUP, TUP,...
VMSC
CCF/SSF
Figure 18 - Terminating Architecture A SendRoutingInfo (SRI) operation is sent from a Gateway MSC to an HLR when a routing request (e.g., ISUP IAM) is received at the Gateway MSC containing a called party number that is an MSISDN number of a subscriber in the GMSC's network. In response to the SRI, if the subscriber is provisioned with CAMEL subscription information, the HLR will send the CAMEL data back to the GMSC in a SRI result. Before sending back the SRI result, the HLR may optionally send a query to the VMSC where the subscriber is registered to get location and/or state information, and this information will be included in the SRI result returned to the GMSC. The HLR can send both terminating CAMEL subscription information (T-CSI) and originating CAMEL subscription information (O-CSI) to the GMSC. CSIs may also include triggering criteria that add conditions on when an IN interaction will take place. The action of the GMSC depends on four factors that can occur in various combinations: 1. T-CSI 2. O-CSI 3. Forwarding information 4. SCP instructions A complete list of combinations and actions is provided in the Appendix entitled Algorithm for handling CAMEL data received at the GMSC. <R-FSD19337.2-300V1.01> Procedure: MT_GMSC (23.018 figure 35) Initial State: Idle Input: Initial routing message from trunk signaling (e.g., ISUP IAM)
Page:
Issue: 4 46
Output: Depending on the outcome of called procedure Obtain_Routeing_Address one of the following outputs will occur: 1. Initial Address Message (or non-ISUP equivalent) 2. Release to A-Party Actions: the behavior will be as specified in process MT_GMSC (23.018 Figure 35). Next state: Depending on the outcome of called procedure Obtain_Routeing_Address, the state will transition to one of the following: 1. Wait for ACM 2. Wait for Forward ACM 3. Idle Notes: 1. Procedure Obtain_Routeing_Address is called, and the bulk of the initial call processing work is done in that procedure. Separate requirements are specified for procedure Obtain_Routeing_Address 2. Unlike the process for originating calls (OCH_MSC), where a called procedure contains the call control states, process MT_GMSC itself contains the full set of call control states. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-300V1>
<R-FSD19337.2-310V1.01> Procedure: Obtain_Routeing_Address (23.018 figure 36) Initial State: Wait_For_Routeing_Info Input: MAP SendRoutingInfo result with terminating CAMEL subscription information. Actions: Processing will be as in 23.018 figure 36. This requirement covers all of the combinations of CAMEL subscription information that may be received from the HLR and all of the possible SCP instructions. The following procedures relevant to CAMEL are covered under this requirement: 1. CAMEL_MT_GMSC_INIT. The requirements for this procedure are covered under this requirement. CAMEL_MT_GMSC_INIT can receive the following external inputs: a) A-Party Release b) B-Party Release In addition, CAMEL_MT_GMSC_INIT may call the following procedures: a) CAMEL_MT_ETC. If ISUP signaling is used for the connection to the IP or Assisting SSP, then both Address Complete and Answer are of interest to this procedure, in addition to release messages from both parties. Other messages may be received, but CAMEL_MT_ETC is not concerned with them and they are simply relayed to Call Control. If ISDN signaling is used then an ISDN Connect message is of interest. b) CAMEL_MT_CTR 2. If CAMEL_MT_GMSC_INIT returns, "CMN" (CAMEL Modified Number): if the route is not permitted, then CAMEL_MT_GMSC_DISC4 is called for mobiles supporting CAMEL phase 2 and CAMEL_MT_GMSC_DISC3 is called for mobiles supporting CAMEL phase 1. QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 47
Page:
3. If CAMEL_MT_GMSC_INIT returns "CAMEL_FTN", then procedure Activate_CF_Process is called which sends a message to process MT_CF_MSC MSC (see Call Forwarding Processing section). 4. If CAMEL_MT_GMSC_INIT returns "GSM_FTN" (standard GSM call forwarding) then CAMEL_MT_GMSC_Notify_CF is called. This procedure notifies the gsmSSF process of a gsm call forwarding event. 5. If CAMEL_MT_GMSC_Notify_CF returns "continue" then the procedure Activate_CF_Process is called which sends a message to process MT_CF_MSC (see Call Forwarding Processing section. 6. If CAMEL_MT_GMSC_Notify_CF returns "reconnect", then this will lead to a reconnection being initiated as per process MT_GMSC, figure 35, sheet 1. 7. If CAMEL_MT_GMSC_INIT returns "MSRN" then normal GSM terminating call processing occurs. Next state: Null Notes: 1. The specific criteria and the matching rules are specified in separate requirements. If there is no terminating CAMEL subscription data or if the triggering criteria do not match, then no IN query is performed, and the state remains NULL. 2. For a complete algorithm covering all of the data combinations that can be received by the GMSC, see the Appendices. References: GSM 23.018 figure 36. 03.78 figure 24 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg <End of R-FSD19337.2-310V1> <R-FSD19337.2-320V1.01> Process: MT_GMSC Initial State: Wait_For_ACM External Input: Address Complete (e.g., ISUP ACM) Action: Processing will be as in 23.018 figure 35, procedure MT_GMSC. 2. The procedure CAMEL_Start_TNRy (03.78 figure 19) is called to start the CAMEL no reply timer. This timer must be less than the network no reply timer (e.g., for ISUP). Next state: Wait_For_Answer References: GSM 23.018 figure 36. 03.78 figure 24 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg <End of R-FSD19337.2-310V1> <R-FSD19337.2-330V1.01> Procedure: MT_GMSC (23.018 Figure 35) Initial State: Wait_For_Answer External Input: Answer (e.g., ISUP ANM) Action: Processing will be as in the following procedures: 1. MT_GMSC (23.018 figure 35 sheet 2). 2. The procedure CAMEL_Stop_TNRy (03.78 figure 20) is called to stop the CAMEL no reply timer. 3. Procedure CAMEL_MT_GMSC_ANSWER (03.78 figure 25): this procedure is called to notify the gsmSSF that an answer event has occurred and if there is a request type detection point armed and to await possible further instructions gsmSSF process. QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 48
Next state: If the return from CAMEL_MT_GMSC_ANSWER is "pass" then the next state is Wait_For_Clear. If it return is "fail" then the next state is "Idle". If the return is "reconnect" then processing is as per the reconnect handling of MT_GMSC sheet 1. Notes: 1. Procedure CAMEL_MT_GMSC_ANSWER is covered under this requirement. That procedure can deal with disconnect or release events, meaning that procedures CAMEL_MT_GMSC_DISC1 or CAMEL_MT_GMSC_DISC2 may be called. Disconnect processing will be handled separately under the requirement for the Wait_For_Clear state in this 23.018 process (MT_GMSC). References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-330V1> <R-FSD19337.2-340V1.01> Process: MT_GMSC (23.018 Figure 35) Initial State: Wait_For_ACM External Input: Connect (i.e., DTAP CONNECT) from B-party Action: Processing will be as in the following procedures: 1. 23.018 procedure MT_GMSC (figure 35 sheet 2). 2. Procedure CAMEL_MT_GMSC_ANSWER (03.78 figure 11): this procedure is called to notify the gsmSSF that an answer event has occurred and to await possible further instructions from the gsmSSF process. Next state: If the return from CAMEL_MT_GMSC_ANSWER is "pass" then the next state is Wait_For_Clear. If it return is "fail" then the next state is "Idle". If the return is "reconnect" then processing is as per the reconnect handling of MT_GMSC sheet 1. Notes: 1. This requirement deals with the case where the B-Party is a mobile subscriber on the same MSC. 2. As with the requirement for the Wait_For_Answer state, procedure CAMEL_MT_GMSC_ANSWER is called which can deal with disconnect or release events. Disconnect processing will be covered separately under the requirement for the Wait_For_Clear state in this same 23.018 procedure (MT_GMSC). References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-340V1> <R-FSD19337.2-350V1.01> Procedure: MT_GMSC (23.018 Figure 35) Initial State: Wait_For_Forward_Answer External Input: Answer (e.g., ISUP ANM) Action: Processing will be as in the following procedures: 1. MT_GMSC (23.018 figure 35 sheet 3). QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 49
2. Procedure CAMEL_MT_GMSC_ANSWER (03.78 figure 25): this procedure is called to notify the gsmSSF that an answer event has occurred and if there is a request type detection point armed and to await possible further instructions gsmSSF process. Next state: If the return from CAMEL_MT_GMSC_ANSWER is "pass" then the next state is Wait_For_Clear. If the return is "fail" then the next state is "Idle". If the return is "reconnect" then processing is as per the reconnect handling of MT_GMSC sheet 1. Notes: 1. The state Wait_For_Forward_ACM and input Address Complete is not covered as there is no specific CAMEL requirements in that case. 2. Procedure CAMEL_MT_GMSC_ANSWER is covered under this requirement. That procedure can deal with disconnect or release events, meaning that procedures CAMEL_MT_GMSC_DISC1 or CAMEL_MT_GMSC_DISC2 may be called. Disconnect processing will be handled separately under the requirement for the Wait_For_Clear state in this 23.018 process (MT_GMSC). 3. Details of how forwarded calls are handled are presented in the Call Forwarding Processing section below. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-350V1> <R-FSD19337.2-360V1.01> Process: MT_GMSC (23.018 Figure 35) Initial State: Wait_For_Forward_ACM External Input: Connect (i.e., DTAP CONNECT) from B-party Action: Processing will be as in the following procedures: 1. 23.018 procedure MT_GMSC (figure 35 sheet 3). 2. Procedure CAMEL_MT_GMSC_ANSWER (03.78 figure 11): this procedure is called to notify the gsmSSF that an answer event has occurred and to await possible further instructions from the gsmSSF process. Next state: If the return from CAMEL_MT_GMSC_ANSWER is "pass" then the next state is Wait_For_Clear. If it return is "fail" then the next state is "Idle". If the return is "reconnect" then processing is as per the reconnect handling of MT_GMSC sheet 1. Notes: 1. This requirement deals with the case where the B-Party is a mobile subscriber on the same MSC. 2. As with the requirement for the Wait_For_Forward_Answer state, procedure CAMEL_MT_GMSC_ANSWER is called which can deal with disconnect or release events. Disconnect processing will be covered separately under the requirement for the Wait_For_Clear state in this same 23.018 procedure (MT_GMSC). References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-360V1>
Page:
Issue: 4 50
<R-FSD19337.2-370V1.01> Process: MT_GMSC (23.018 figure 35) Initial State: Wait_For_Answer Internal Input: Expiration of no reply timer (TNRy). External Output: 1. Release towards the B-Party (e.g., ISUP REL) 2. Release towards A-Party (e.g., DTAP DISCONNECT) unless a follow-on call is requested by the SCP. Action: Processing will be as in the following procedures: 1. MT_GMSC (23.018 figure 35) sheet 5. 2. CAMEL_MT_GMSC_DISC5 (03.78 figure 29). Next state: Null Notes:. 1. CAMEL_MT_GMSC_DISC5 handles the internally defined "no answer" event. Notes: References: 23.018; 03.78 Modification Reason: In version 1.01, modified references (mr=17711). Feature ID: 50.100 Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-370V1> <R-FSD19337.2-380V1.01> Process: MT_GMSC (23.018 figure 35) Initial State: Wait_For_ACM, Wait_For_Forward_ACM, Wait_For_Answer or Wait_For_Forward_Answer External Input: A-Party Release (e.g., DTAP DISCONNECT) External Output: Release towards B-party (e.g., ISUP REL) Action: Processing will be as in the following procedures: 1. MT_GMSC (23.018 figure 35) sheet 6. 2. CAMEL_MT_GMSC_DISC6 (03.78 figure 30): if CAMEL phase 2 is active for the subscriber. 3. CAMEL_MT_GMSC_DISC3 (03.78 v5.8.0 figure 8.2-9): if CAMEL phase 1 is active for the subscriber. Next state: Idle Notes: 1. CAMEL_MT_GMSC_DISC6 handles the abandon event in CAMEL phase 2. The addition for CAMEL phase 2 is that abandon is a detection point, and so an internal notification is sent to the gsmSSF process to indicate that an abandon event has occurred. 2. CAMEL_MT_GMSC_DISC3 handles the abandon event for CAMEL phase 1. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-380V1> <R-FSD19337.2-390V1.01> Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 51
Process: MT_GMSC (23.018 figure 35) Initial State: Wait_For_ACM, Wait_For_Forward_ACM, Wait_For_Answer or Wait_For_Forward_Answer External Input: B-Party release (e.g,. ISUP REL) External Output: Release towards A-Party (e.g., DTAP DISCONNECT) Action: Processing will be as in the following procedures: 1. MT_GMSC (23.018 figure 35) sheets 6. 2. CAMEL_MT_GMSC_DISC4 (03.78 figure 28): if CAMEL phase 2 is active for the subscriber and the release cause is other than "No answer from user". 3. CAMEL_MT_GMSC_DISC5 (03.78 figure 29): if CAMEL phase 2 is active for the subscriber and the release cause is "No answer from user". 4. CAMEL_MT_GMSC_DISC3 (03.78 v5.8.0 figure 8.2-9): if CAMEL phase 1 is active for the subscriber. Next state: Idle Notes: 1. CAMEL phase 2 adds event detection points for terminating busy and no answer. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-390V1> <R-FSD19337.2-400V1.01> Process: MT_GMSC (23.018 figure 35) Initial State: Wait_For_ACM, Wait_For_Forward_ACM, Wait_For_Answer or Wait_For_Forward_Answer, Wait_For_Clear Internal Input: Int_Release_Call -- sent by the gsmSSF when a CAP ReleaseCall operation is received from the SCP. External Output: 1. Release towards A-Party (e.g., DTAP DISCONNECT) 2. Release towards the B-Party (e.g., ISUP REL) Action: Processing will be as in MT_GMSC (23.018 figure 35) sheets 6 and 7. Next state: Idle References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-400V1> <R-FSD19337.2-410V1.01> Process: MT_GMSC (23.018 figure 35) Initial State: Wait_For_Clear External Input: A-Party Release (e.g., DTAP DISCONNECT) External Output: 1. Release towards the B-Party (e.g., ISUP REL) either from this procedure or from called procedure CAMEL_MT_GMSC_DISC1. Action: Processing will be as in the following procedures: QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 52
1. MT_GMSC (23.018 figure 35) sheet 7. 2. CAMEL_MT _GMSC_DISC1 (03.78 figure 12). Next state: Idle Notes: 1. CAMEL_MT_GMSC_DISC1 is the same for CAMEL phases 1 and 2. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-410V1> <R-FSD19337.2-420V1.01> Process: MT_GMSC (23.018 figure 35) Initial State: Wait_For_Clear External Input: B-Party Release (e.g., ISUP REL) External Output: 1. Release towards the A-Party (DTAP DISCONNECT) either from this procedure or from called procedure CAMEL_MT_GMSC_DISC2, except when a reconnect is to take place. Action: Processing will be as in the following procedures: 1. MT_GMSC (23.018 figure 35) sheet 7. 2. CAMEL_MT_GMSC_DISC2 (03.78 figure 13). Next state: Idle Notes: 1. CAMEL_MT_GMSC_DISC2 is the same for CAMEL phases 1 and 2. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-420V1>
Page:
Issue: 4 53
IAM
Forward
PASS Activate_CF_ Process PASS Perform Call Forwarding CAMEL_CF_ MSC_INIT Perform Call Forwarding Ack Internal IAM PASS IAM ACM
ACM
Wait For Forward Answer
Internal ACM
Wait For Answer
Etc...
Etc...
Figure 19 - Call Forwarding structure in CAMEL spec 03.78 Call forwarding may be invoked both through standard GSM call forwarding and through a set of conditions involving both CAMEL subscriber data and SCP instructions. The former is referred as GSM call forwarding and the latter as CAMEL call forwarding. CAMEL call forwarding occurs when all of the following occur: 1. A T-CSI and O-CSI arereturned in the Send Routing Info acknowledgement from the HLR to the GMSC. 2. The SCP returns a Connect operation with the following: # A new translated number (i.e., different from the original dialed number) # An "O-CSI applicable" flag. # Forwarding information (e.g., redirection information) See 03.78 section 7.5.3, "Call Forwarding at the GMSC". The requirements in this section will follow the states in the 23.018 process called "MT_CF_MSC" (figure 42). <R-FSD19337.2-600V1.01> Process: MT_CF_MSC Initial State: Idle Internal Input: "Perform Call Forwarding" from procedure Activate_CF_Process (23.018 figure 41). External Output: Initial Address (e.g., ISUP IAM) Internal Output: "Perform Call Forwarding Ack" or "Perform Call Forwarding negative response". Action: Processing will be as in 23.018 figure 42 "MT_CF_MSC". This process calls procedure CAMEL_CF_MSC_INIT, which may initiate an interaction with an SCP for further QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 54
Page:
call handling instructions. The following procedures relevant to CAMEL are covered under this requirement: 1. CAMEL_CF_MSC_INIT (03.78 figure 39). 2. CAMEL_CF_MSC_INIT may call the following procedures: # CAMEL_CF_ETC # CAMEL_CF_CTR Next state: If CAMEL_CF_MSC_INIT returns "Pass", the next state is "Wait for IAM". If it returns something other than "Pass", then the next state is "Idle". Notes: 1. An SCP interaction due to call forwarding is much like an origination. Thus, as with CAMEL_OCH_MSC_INIT for originations and CAMEL_MT_GMSC_INIT, CAMEL_CF_MSC_INIT can receive internal messages from the gsmSSF process as the latter communicates with an SCP. 2. For forwarded calls, the query message to the SCP indicates that call forwarding has been invoked. See the section on the CAP InitialDP operation. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-600V1> <R-FSD19337.2-610V1.01> Process: MT_CF_MSC Initial State: Wait_For_IAM Internal Input: CF Cancelled (from procedure Activate_CF_Process) External Output: Internal Output: Conditions: Action: Processing will be as in the following procedures: 1. MT_CF_MSC (23.018 figure 42) 2. CAMEL_OCH_MSC_DISC4 (03.78 figure 16): if CAMEL phase 2 is active for the subscriber. 3. CAMEL_OCH_MSC_DISC3 (03.78 v5.8.0 figure 8.1-6): if CAMEL phase 1 is active for the subscriber. Next state: If a CF canceled is received, the next state is "Idle". Notes: 1. The case where an IAM is received from process MT_GMSC in the Wait_For_IAM state is not covered, as there is no specific CAMEL processing involved. The next state in that case is the Wait_For_ACM state. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-610V1>
Page:
Issue: 4 55
<R-FSD19337.2-620V1.01> Process: MT_CF_MSC Initial State: Wait_For_ACM External Input: Address Complete (e.g., ISUP ACM) Action: Processing will be as in 23.018 figure 42, procedure MT_CF_MSC. 1. The procedure CAMEL_Start_TNRy (03.78 figure 19) is called to start the CAMEL no reply timer. This timer must be less than the network no reply timer (e.g., for ISUP). Next state: Wait_For_Answer Notes: References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-620V1> <R-FSD19337.2-630V1.01> Initial State: Wait_For_Answer External Input: Answer (e.g., ISUP ANM) Action: Processing will be as in the following procedures: 1. MT_CF_MSC (23.018 figure 42 sheet 2). 2. The procedure CAMEL_Stop_TNRy (03.78 figure 20) is called to stop the CAMEL no reply timer. 3. Procedure CAMEL_CF_MSC_ANSWER (03.78 figure 40): this procedure is called to notify the gsmSSF that an answer event has occurred and if there is a request type detection point armed and to await possible further instructions gsmSSF process. Next state: If the return from CAMEL_CF_MSC_ANSWER is "pass" then the next state is Wait_For_Clear. If it return is "fail" then the next state is "Idle". If the return is "reconnect" then processing is as per the reconnect handling of MT_CF_MSC sheet 1. Notes: 1. Procedure CAMEL_CF_MSC_ANSWER is covered under this requirement. That procedure can deal with disconnect or release events, meaning that procedures CAMEL_OCH_MSC_DISC1 or CAMEL_OCH_MSC_DISC2 may be called. Disconnect processing will be handled separately under the requirement for the Wait_For_Clear state in this 23.018 process (MT_CF_MSC). References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-630V1> <R-FSD19337.2-640V1.01> Process: MT_CF_MSC (23.018 Figure 42) Initial State: Wait_For_ACM External Input: Connect (i.e., DTAP CONNECT) from B-party Action: Processing will be as in the following procedures: 1. 23.018 procedure MT_CF_MSC (figure 42 sheet 2). QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 56
Page:
2. Procedure CAMEL_CF_MSC_ANSWER (03.78 figure 40): this procedure is called to notify the gsmSSF that an answer event has occurred and to await possible further instructions from the gsmSSF process. Next state: If the return from CAMEL_CF_MSC_ANSWER is "pass" then the next state is Wait_For_Clear. If it return is "fail" then the next state is "Idle". If the return is "reconnect" then processing is as per the reconnect handling of MT_CF_MSC sheet 1. Notes: 1. This requirement deals with the case where the B-Party is a mobile subscriber on the same MSC. 2. As with the requirement for the Wait_For_Answer state, procedure CAMEL_CF_MSC_ANSWER is called which can deal with disconnect or release events. Disconnect processing will be covered separately under the requirement for the Wait_For_Clear state in this same 23.018 procedure (MT_CF_MSC). References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-640V1> <R-FSD19337.2-650V1.01> Process: MT_CF_MSC (23.018 figure 42) Initial State: Wait_For_Answer Internal Input: Expiration of no reply timer (TNRy). External Output: 1. Release towards the B-Party (e.g., ISUP REL) 2. Release towards A-Party (via process MT_GMSC) unless a follow-on call is requested by the SCP. Action: Processing will be as in the following procedures: 1. MT_CF_MSC (23.018 figure 42) sheet 4. 2. CAMEL_OCH_MSC2 (03.78 figure 29). Next state: Null Notes: 1. CAMEL_OCH_MSC2 handles the internally defined "no answer" event. References: 23.018 v6.6.0; 03.78 v6.6.0 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-650V1> <R-FSD19337.2-660V1.01> Process: MT_CF_MSC (23.018 figure 42) Initial State: Wait_For_ACM, Wait_For_Answer External Input: A-Party Release (via process MT_GMSC) External Output: Release towards B-party (e.g., ISUP REL) Action: Processing will be as in the following procedures: 1. MT_CF_MSC (23.018 figure 42) sheet 3. QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 57
2. CAMEL_OCH_MSC_DISC4 (03.78 figure 16): if CAMEL phase 2 is active for the subscriber. 3. CAMEL_OCH_MSC_DISC3 (03.78 v5.8.0 figure 8.1-6): if CAMEL phase 1 is active for the subscriber. Next state: Idle Notes: 1. CAMEL_OCH_MSC_DISC4 handles the abandon event in CAMEL phase 2. The addition for CAMEL phase 2 is that abandon is a detection point, and so an internal notification is sent to the gsmSSF process to indicate that an abandon event has occurred. 2. CAMEL_OCH_MSC_DISC3 handles the abandon event for CAMEL phase 1. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-660V1> <R-FSD19337.2-670V1.01> Process: MT_GMSC (23.018 figure 42) Initial State: Wait_For_ACM, Wait_For_Answer External Input: B-Party release (e.g,. ISUP REL) External Output: Release towards A-Party (via process MT_GMSC) Action: Processing will be as in the following procedures: 1. MT_CF_MSC (23.018 figure 42) sheets 3. 2. CAMEL_OCH_MSC1 (03.78 figure 12): if CAMEL phase 2 is active for the subscriber and the release cause is other than "No answer from user". 3. CAMEL_OCH_MSC2 (03.78 figure 13): if CAMEL phase 2 is active for the subscriber and the release cause is "No answer from user". 4. CAMEL_OCH_MSC_DISC3 (03.78 v5.8.0 figure 8.1-6): if CAMEL phase 1 is active for the subscriber. Next state: Idle Notes: 1. The degree of CAMEL support is determined at the time of location registration. 2. CAMEL phase 2 adds event detection points for busy and no answer. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-670V1> <R-FSD19337.2-680V1.01> Process: MT_GMSC (23.018 figure 42) Initial State: Wait_For_ACM, Wait_For_Answer or Wait_For_Clear Internal Input: Int_Release_Call -- sent by the gsmSSF when a CAP ReleaseCall operation is received from the SCP. External Output: 1. Release towards A-Party (e.g., DTAP DISCONNECT) QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 58
2. Release towards the B-Party (e.g., ISUP REL) Action: Processing will be as in MT_GMSC (23.018 figure 35) sheets 6 and 7. Next state: Idle References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-680V1> <R-FSD19337.2-690V1.01> Process: MT_CF_MSC (23.018 figure 42) Initial State: Wait_For_Clear External Input: A-Party Release (via process MT_GMSC) External Output: 1. Release towards the B-Party (e.g., ISUP REL) either from this procedure or from called procedure CAMEL_OCH_MSC_DISC1. Action: Processing will be as in the following procedures: 3. MT_CF_MSC (23.018 figure 42) sheet 5. 4. CAMEL_OCH_MSC_DISC1 (03.78 figure 14). Next state: Idle Notes: 1. CAMEL_MT_GMSC_DISC1 is the same for CAMEL phases 1 and 2. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-690V1> <R-FSD19337.2-700V1.01> Process: MT_GMSC (23.018 figure 42) Initial State: Wait_For_Clear External Input: B-Party Release (e.g., ISUP REL) External Output: 1. Release towards the A-Party (via process MT_GMSC) either from this procedure or from called procedure CAMEL_OCH_MSC_DISC2, except when a reconnect is to take place. Action: Processing will be as in the following procedures: 3. MT_CF_MSC (23.018 figure 35) sheet 5. 4. CAMEL_OCH_MSC_DISC2 (03.78 figure 15). Next state: Idle Notes: 1. CAMEL_MT_GMSC_DISC2 is the same for CAMEL phases 1 and 2. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 59
Page:
Issue: 4 60
2. DP12 -- TerminationAttemptAuthorized -- for terminations. This DP is triggered when a termination arrives at a Gateway MSC for a terminating mobile subscriber. It is armed via parameters sent by the HLR in response to a routing request from the GMSC. The ETSI CS-1 standards specify other trigger detection points for both originations and terminations, two of which are relevant for mobile subscribers: 1. DP3 -- AnalyzedInfo -- for originations. This DP is triggered after digit analysis and before routing, and is often used for services that are accessed via a special number, e.g., 800 services. 2. DP4 -- RouteSelectFailure -- for both originations and terminations. This DP is triggered when a call cannot be routed for reasons other than busy, no answer or mobile station not reachable. DP4 is widely used for number portability services. DP2 is always provisioned on a subscriber basis for CAMEL. DPs 3 and 4 are often provisioned on a switch basis, e.g., any subscriber (CAMEL and non-CAMEL) can access an 800 service.
Interactions between CAMEL supplementary services will be as specified in ETSI 22.078 section 18 and 03.78 section 10. Notes: 1. The interactions are summarized in this section. 2. The following services are not supported in u01.03: COLP, CUG, AOC, ECT, CCBS and Call Deflection. References: 03.78; 22.078 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711) and added note to reflect unsupported services in u01.03 (mr=17718). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-740V1>
A CAP "Task Refused" error will be returned if these operations are invoked for a held call. These operations shall be blocked to a multi-part call when it is split. Once the multi-party is dropped and the call becomes a regular call then these operations should be allowed.
Page:
For example, access restrictions for a CUG subscriber will take precedence over gsmSCF based VPN access restrictions.
8.3.7.10
The gsmSCF will be able to send the Advice of Charge data (e-values) to the originating MSC. The MSC shall use the e-values received from the SCF, for the purpose of AoC. The gsmSCF evalues shall take precedence over any e-values generated by standard GSM Advice of Charge.
8.3.7.11 8.3.7.12
<End of R-FSD19337.2-750V1>
8.4
The gsmSSF process receives internal inputs from call control (the CCF) for originating, terminating and call forwarded calls. It is the responsibility of the gsmSSF to act as the interface between the CCF and the external SCP (i.e., the gsmSCF). The gsmSSF has a direct interface to the SCP and an indirect interface to subscribers via the CCF.
Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1000V1> <R-FSD19337.2-1005V1.01> Initial State: Wait_For_Request Internal Input: 1. Int_DP_Collected_Info or 2. Int_DP_Termating_Attempt_Authorized Actions: Processing will be as in 03.78 figure 45 sheet 2. 1. Call procedure Check_Criteria for Int_DP_Collected_Info 2. After the InitialDP is sent, start a Tssf timer. 3. Open a control relationship. 4. Set the following: # ACR sent = false # AC pending = false # Outstanding requests = 1 # Outstanding Call Information Requests = 0 5. If Int_T_Exception, Int_O_Exception, Int_DP_T_Abandon or Int_DP_O_Abandon are received, transition to Idle state. External Output: Send a CAP InitialDP operation to the gsmSCF containing all of the mandatory and conditional parameters that are available, as indicated in ETSI GSM 03.78 section 9.1.5, for the indicated call type: mobile origination, mobile termination or call forwarding. Next state: Waiting for Instructions Notes: 3. This requirement covers two gsmSSF states from 03.78 -- "Idle" and the intermediate state "Wait_For_Request" -- as all the information necessary can be transmitted with one internal message and requires only one gsmSSF state. 4. The call type is indicated to the gsmSSF process via the DP number (2 for originations or 12 for terminations) and for call forwarding, by the presence of forwarding information. 5. The mechanism for indicating call forwarding is internal and is a design issue. References: GSM 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1005V1>
Page:
2. If there are outstanding request type event detection points (EDP-R), the next state is "Waiting_For_Instructions". 3. If there are any outstanding notification type event detection points or any pending reports, the next state is "Monitoring". Notes: 1. If no outstanding request type event detection points are armed, the control relationship is terminated. 2. The gsmSSF communicates to the CCF all of the modified calling instructions via the Int_Connect message. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1020V1>
2. Procedure Complete_all_FCI_records is called. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1050V1>
Page:
Issue: 4 69
Page:
Set Tssf timer to default non-user interaction timer and restart it (see section on "Timers and Timer Handling"). Increment the Outstanding_Requests counter. 2. Perform implicit disarming of DPs. 3. Call procedure Handle_ACR with "call active" equal to "False". 4. Call procedure "Handle_CIR". Next state: Waiting_For_Instructions Notes: 1. Implicit disarming rules are covered in 03.78 section 7.4. 2. The CCF will indicate in the internal disconnect message the leg ID of the disconnecting party. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1140V1>
Page:
Issue: 4 72
Page:
3. An SCF ID. The SCF ID is either a gsmSCF address or can be mapped to a gsmSCF address by the assisting SSP or IP. The gsmSCF address is used to route the request for announcement instructions to the correct gsmSCF. The CAMEL standards do not specify how the Correlation ID and SCF ID are transmitted from a gsmSSF to an assisting gsmSSF or IP. ISUP 97 has separate parameters for Correlation ID and SCF ID in the ISUP IAM, but earlier versions do not. Earlier versions have to rely on putting these parameters in existing fields, e.g., appending them to the called party number field. As most networks are running ISUP 88 or ISUP 92, this method will have to be followed. The requirements are contained in this section and in the section entitled "Assisting MSC".
Page:
Issue: 4 74
Page:
Issue: 4 75
Page:
1. Reset the Tssf timer to the last value used and restart it. Next state: Waiting_For_End_Of_User_Interaction Notes: 1. The various gsmSRF configurations are shown in 09.78 section 4.2 "Physical Scenarios". The scenario covered by this requirement is 3. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). In version 1.03 clarified note regarding supported scenarios (mr=19628). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1240V1> <R-FSD19337.2-1242V1.01> Announcement session related operations for an internal gsmSRF -- ConnectToResource, EstablishTemporaryConnection, PlayAnnouncement and PromptAndCollectUserInformation -- will be not be supported in the following circumstances: 1. When the leg for which the announcement operation applies is on hold 2. When the leg for which the announcement operation applies has a data connection If one of these operations is received for the above cases, a CAP "Task Refused" error will be returned to the gsmSCF. Notes: References: SE Judgement Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1242V1> <R-FSD19337.2-1244V1.01> After an announcement session is initiated to either an internal or external gsmSRF, the following messages must be sent back to the A-party: 1. PROGRESS and CONNECT if the connection to the A-party is via BSSAP. 2. Network Setup and Answer (e.g., ISUP ACM and ANM) if the connection to the A-party is via trunk signaling. Notes: References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1244V1>
8.4.5.10
<R-FSD19337.2-1250V1.01>
Page:
Initial State: Waiting_For_End_Of_User_Interaction External input: CAP Cancel operation containing the "invoke ID" parameter. Internal output: CAP Cancel relayed to CCF in some internal format. Action: Processing will be as in 03.78 figure 45 sheet 16. 1. Reset the Tssf timer to the last value used and restart it. Next state: Waiting_For_End_Of_User_Interaction Notes: 1. The various gsmSRF configurations are shown in 09.78 section 4.2 "Physical Scenarios". References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1250V1>
8.4.5.11
<R-FSD19337.2-1260V1.01> Initial State: Waiting_For_End_Of_User_Interaction Internal input: Previous operation "Canceled" error indicated from SRF. External output: CAP Cancel error sent to gsmSCF. Action: Processing will be as in 03.78 figure 45 sheet 18. Next state: Waiting_For_End_Of_User_Interaction Notes: 1. This is one instance where an error indicates the successful execution of an operation -- i.e., a CAP Cancel operation. If the previously requested operation (PlayAnnouncement or PromptAndCollectUserInformation) was successfully canceled, then this error is returned to the gsmSCF in a Return Error. See the definition of the Cancel operation in 09.78. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1260V1>
8.4.5.12
<R-FSD19337.2-1270V1.01> Initial State: Waiting_For_End_Of_User_Interaction Internal input: "Cancel failed" error indicated from CCF. External output: CAP Cancel Failed error sent to gsmSCF. Action: Processing will be as in 03.78 figure 45 sheet 18. Next state: Waiting_For_End_Of_User_Interaction Notes: QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 78
Page:
1. This is the case where a Cancel operation was not successfully carried out, e.g., because the announcement was already successfully played. See the definition of the Cancel operation in 09.78. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1270V1>
8.4.5.13
<R-FSD19337.2-1280V1.01> Initial State: Waiting_For_End_Of_User_Interaction Internal input: Collected digits from user interaction from CCF. External output: CAP PromptAndCollectUserInformation Return Result. Action: Processing will be as in 03.78 figure 45 sheet 18. Next state: Waiting_For_End_Of_User_Interaction Notes: 1. After a caller has entered digits in response to some prompt, the digits are sent back to the gsmSCF. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1280V1>
8.4.5.14
Sending SpecializedResourceReport
<R-FSD19337.2-1285V1.01> Initial State: Waiting_For_End_Of_User_Interaction Internal input: Announcement complete indication from CCF. External output: If the previously received PlayAnnouncement indicated that a response is required, then a CAP SpecializedResourceReport operation is sent to the gsmSCF. Action: Processing will be as in 03.78 figure 45 sheet 18. Next state: Waiting_For_End_Of_User_Interaction Notes: 1. The PlayAnnouncement parameter that controls whether a SpecializedResourceReport is sent is "requestAnnouncementComplete". See 09.78. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1285V1> QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 79
Page:
8.4.5.15
<R-FSD19337.2-1290V1.01> Initial State: Waiting_For_End_Of_User_Interaction Internal Input: Expiration of Tssf timer External Output: TCAP Abort towards SCP Internal Output: Int_Disconnect_Forward_Connection to CCF Action: processing will be as in 03.78 figure 45 sheet 18. Next state: SRF_Release_Pending Notes:
References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1290V1> <R-FSD19337.2-1295V1.01> Process: gsmSSF Initial State: SRF_Release_Pending Internal Input: Int_SRF_Released External Output: Int_Error Action: Processing will be as in 03.78 figure 45 sheet 18 1. Procedure Complete_all_FCI_records is called. Notes: References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1295V1>
# If an ApplyCharging is pending, the call period timer (Tcp) is started. # If the warning timer interval is greater than 0, then the warning timer (Tw) is started. # If any e-parameters are stored, they are sent to the mobile. # Set the Tssf timer to the user interaction timer and restart it. 2. If the connection is unsuccessful: # An EstablishTemporaryConnect error is sent to the SCP with error cause of "ETC failed". # Set the Tssf timer to the last used interval and restart it. Next state: 1. If the connection to the IP or Assisting SSP is successful, then the next state is Waiting_For_End_Of_Temporary_Connection 2. If unsuccessful, then the next state is Waiting_For_Instructions Notes: 1. The Int_Temporary_Connection_Established message is sent by the CCF after it receives an Answer message (e.g., ISUP ANM) from the IP or Assisting SSP. 2. The SCP can send an ApplyCharging to control and monitor the length of the connection to the IP. This is what the Tcp controls. 3. It is possible for Tcp to be less than or equal to 30 seconds, in which case no warning tone is played, and the warning timer (Tw) does not need to be started. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1300V1>
Page:
1. If the connection to the IP or Assisting SSP is successful, then the next state is Waiting_For_End_Of_Temporary_Connection 2. If unsuccessful, then the next state is Waiting_For_Instructions Notes: 1. The SCP can send an ApplyCharging to control and monitor the length of the connection to the IP. This is what the Tcp controls. 2. It is possible for Tcp to be less than or equal to 30 seconds, in which case no warning tone is played, and the warning timer (Tw) does not need to be started. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1305V1>
Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1315V1>
<R-FSD19337.2-1325V1.01> Process: gsmSSF Initial State: TC_Release_Pending Internal Input: Int_TC_Released External Output: Int_Error Action: Processing will be as in 03.78 figure 45 sheet 13 2. Procedure Complete_All_FCI_Records is called. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1325V1>
<R-FSD19337.2-1330V1.01> Process: gsmSSF Initial State: Waiting_For_End_Of_Temporary_Connection, Waiting_For_End_Of_User_Interaction or Monitoring Internal Input: Warning Tone Timer (Tw) expired Internal Output: Int_Apply_Warning_Tone to CCF QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 83
Page:
Action: Processing will be as in 03.78 figure 45 sheets 14 and 15. Next state: the same as the initial state. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1330V1>
<R-FSD19337.2-1335V1.01> Process: gsmSSF Initial State: Waiting_For_End_Of_Temporary_Connection, Waiting_For_End_Of_User_Interaction or Monitoring Internal Input: Tariff Switch Timer (Tsw) expired Internal Output: Send_e_Parameters to CCF Action: Processing will be as in 03.78 figure 45 sheets 14 and 15. 1. If e-parameters are stored then they are sent to the mobile station via the CCF 2. The current value of the call period timer (Tcp) is stored. Next state: the same as the initial state. Notes: 1. The next ApplyChargingReport will contain both the initial tariff switch interval and the time since the last tariff switch. The current value of the Tcp timer is stored so that the time since the tariff switch can be determined. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-1335V1> <R-FSD19337.2-1340V1.01> Process: gsmSSF Initial State: Waiting_For_End_Of_Temporary_Connection, Waiting_For_End_Of_User_Interaction Internal Input: Call Period Timer (Tcp) expired Internal Output: see "Action" section. External Output: see "Action" section. Action: Processing will be as in 03.78 figure 45 sheet 14. If the ApplyCharging report indicated release on Tcp timer expiration, then: # Send a CAP ApplyChargingReport to the gsmSCF. # Send an Int_Disconnect_Forward_Connection to the CCF. # Call procedure Handle_CIR. # Call procedure Complete_All_FCI_Records # Send an Int_Release to the CCF QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 84
Page:
If the ApplyCharging report indicates no release, then: # Procedure Handle_ACR is called. # The Tssf is set to the last used value and restarted. Next state: the same as the initial state. Notes: 1. Whether or not to release the call at the expiration of the Tcp timer is indicated in an ApplyCharging parameter received at the same time as the Tcp interval. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-1340V1>
Page:
state under previous requirements which combine more than one state. The expiration of the call period timer in Monitoring state has some unique handling and is covered here. <R-FSD19337.2-1410V1.01> Process: gsmSSF Initial State: Monitoring Internal Input: Call Period Timer (Tcp) expired Internal Output: see "Action" section. External Output: see "Action" section. Action: Processing will be as in 03.78 figure 45 sheet 15. 1. If the ApplyCharging report indicated release on Tcp timer expiration, then: # Send a CAP ApplyChargingReport to the gsmSCF. # Call procedure Handle_CIR. # Call procedure Complete_all_FCI_records # Send an Int_Release to the CCF # Go to the Idle state 2. If the ApplyCharging report indicates no release, then: # If there are any outstanding EDPs or requests: Call procedure Handle_ACR Remain in the Monitoring state # If no EDPs or requests: Send a CAP ApplyChargingReport to the gsmSCF Call procedure Complete_all_FCI_records Go to the Idle state Next state: Monitoring or Idle Notes: 1. Whether or not to release the call at the expiration of the Tcp timer is indicated in an ApplyCharging parameter received at the same time as the Tcp interval. References: 23.018; 03.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-1410V1>
8.4.7.3.1
A feature developed on the 5ESS for OneTel in Australia allows for different handling when a call period timer expires. Essentially, instead of tearing both legs of the call down, which is the CAMEL standard treatment, if there is an EDP armed as "request" type for B-party disconnect, the B-party leg is torn down but instead of tearing down the A-party leg, the EDP-9R is reported to the SCP. The SCP then has the option of reconnecting the A-party to a new destination, e.g., to a recharge operation. This functionality is not a required feature for R1V2 but is added here for information. The details are as follows.
Page:
Issue: 4 87
1. When the ApplyCharging timer expires (e.g., no time left on prepaid calling card), the gsmSSF process sends an internal message to the CCF. 2. After checking data for whether this functionality is active, and determining that EDP 9B-R is set, the CCF disconnects the B-party but not the A-party. The CCF then sends an internal message indicating that B-party disconnect has been encountered to the gsmSSF. 3. The gsmSSF sends an EventReportBCSM (9B-R) to the gsmSCF. The gsmSSF also sends an ApplyChargingReport as usual, with the CallResult parameter of the ApplyChargingReport operation containing a parameter which indicates how much time has been used. 4. Upon checking the ApplyChargingReport and the EventReportBCSM, the SCP service logic must send back further call handling instructions, e.g., a CAP Connect to the gsmSSF to connect the subscriber to an operator.
5. The rest of the processing is as indicated in figure 45 sheet 19, and depends on whether the corresponding EDP is armed, and whether it is armed as notification or request type. Next state: Waiting_For_Instructions, Monitoring or Idle Notes: 1. The Tcp timer is started at the time of answer so that the duration of the active call can be timed. If other time values are required (e.g., time for call setup), the CallInformationRequest operation can be used. 2. The Tw timer is equal to the Tcp time minus the standard delta value (30 seconds). 3. Implicit disarming rules are covered in 03.78 section 7.4. References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1420V1>
Page:
Issue: 4 89
8.4.8.1.1
As an option for a release past R1V2, the standard 30-second delta timer value before the call period timer expires may be made settable by the operator.
Page:
1. The request is stored and the number of outstanding Call Information Requests is incremented. 2. The Tssf timer is set to the last used value and restarted. Next state: Waiting_For_Instructions References: 03.78; 09.78 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-1530V1>
Assisting MSC
The assisting MSC is used to set up an announcement and digit collection session for another MSC that requests its services. An assisting MSC can have either internal SRF functionality or can connect to an external IP. The exact configuration makes no difference to the initiating MSC, and in fact from the perspective of the initiating MSC, an assisting MSC is the same as an external IP. As with the MSC, there are two distinct models on the assisting MSC: the CCF and the SSF. The assisting CCF requirements are located in 03.78 and not in 23.018, the basic call handling specification. An MSC acting as an assisting MSC will contact an internal SRF similar to the procedures for an initiating MSC that has an internal SRF. The internal SRF will be implemented on the Lucent Media Server (LMS), and internal messages will be passed from call control to the LMS.
9.1
The CAMEL specification 03.78 models events from an internal or external case for the relay case as going directly from the gsmSSF to the SRF. In practice, since the CCF is typically responsible for setting up voice connections to announcement and digit collection functions, whether internal or external to the MSC, these messages will likely pass through the CCF. However, for requirements purposes, this does not have to be shown, and the convention of 03.78 will be followed.
Page:
<R-FSD19337.2-2010V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Wait_for_assisting_gsm_SSF_invoked Internal Input: Int_Assisting_gsmSSF_invoked Action: Processing will be as in 03.78 Figure 53 sheet 1 Next State: Wait_For_Assisting_Event References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2010V1> <R-FSD19337.2-2020V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Wait_for_assisting_gsm_SSF_invoked External Input: Release from Initiating MSC Internal Output: Int_Release_Assisting_gsmSSF Action: Processing will be as in 03.78 Figure 53 sheet 1 Next State: Idle References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2020V1>
9.1.2
<R-FSD19337.2-2030V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Wait_For_Assisting_Event Internal Input: Int_Connect_To_Resource Internal Output: Int_Invoke_SRF (to SRF) Action: Processing will be as in 03.78 Figure 53 sheet 2 1. A connection must be set up to an announcement and digit collection facility. Next State: Await_SRF_Initialization References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2030V1> <R-FSD19337.2-2040V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Wait_For_Assisting_Event QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 93
Page:
Internal Input: Int_assisting_gsmSSF_released External Output: Release message back to initiating MSC Action: Processing will be as in 03.78 Figure 53 sheet 2 Next State: Idle References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2040V1> FUTURE <R-FSD19337.2-2050V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Wait_For_Assisting_Event External Input: Release from initiating MSC Internal Output: Int_release_assisting_gsmSSF Action: Processing will be as in 03.78 Figure 53 sheet 2 Next State: Idle Notes: 1. Figure 53 sheet 2 has an added intermediate state -- "Release_Assisting_gsmSSF" -- which waits for an addition input from process Assisting_gsmSSF -"Int_assisting_gsmSSF_released". However, there process Assisting_gsmSSF has no choice but to send this internal message back, so this added state essentially adds no value, and is skipped. References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2050V1> <R-FSD19337.2-2060V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Await_SRF_Initialization Internal Input: Int_SRF_Connected (from SRF) Internal Output: Int_release_assisting_gsmSSF Action: Processing will be as in 03.78 Figure 53 sheet 3 1. The incoming path must be joined to the SRF. 2. Call procedure Send_ACM_If_Required. 3. Call procedure Send_Answer_If_Required. Next State: Wait_For_Assisting_Event References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2060V1> QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 94
<R-FSD19337.2-2070V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Await_SRF_Initialization Internal Input: Int_SRF_Connection_Failure (from SRF) Internal Output: Int_CTR_Failed Action: Processing will be as in 03.78 Figure 53 sheet 3 Next State: Wait_For_Assisting_Event References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2070V1> <R-FSD19337.2-2080V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Await_SRF_Initialization External Input: Release from initiating MSC Internal Output: Int_Disconnect_SRF (to SRF) Action: Processing will be as in 03.78 Figure 53 sheet 3 Next State: Await_gsmSRF_Disconnection References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2080V1> <R-FSD19337.2-2090V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Await_gsmSRF_Disconnection Internal Input: Int_SRF_Released (from SRF) Internal Output: Int_release_assisting_gsmSSF Action: Processing will be as in 03.78 Figure 53 sheet 3 Next State: Idle Notes: the "Releasing_assisting_gsmSSF" state is not specified separately. References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2090V1> <R-FSD19337.2-2100V1.01> FUTURE Process: CAMEL_Assisting_MSC Initial State: Await_SRF_Initialization Internal Input: Int_assisting_gsmSSF_released (from gsmSSF) QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 95
External Output: Release back to initiating MSC Action: Processing will be as in 03.78 Figure 53 sheet 3 Next State: Idle References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2100V1>
9.2 9.2.1
<R-FSD19337.2-2310V1.01> FUTURE Process: Assisting_gsmSSF Initial State: Idle Internal Input: Int_Assist_Required Internal Output: Int_Assisting_gsmSSF_Invoked External Output: CAP AssistRequestInstructions operation to the gsmSCF Action: Processing will be as in 03.78 Figure 54 sheet 1 1. Set Tssf to default user interaction value (see section entitled "Timers and Timer Handling") 2. Open a control relationship Next State: Waiting_For_Instructions References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2310V1>
Page:
Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2320V1>
Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2350V1> <R-FSD19337.2-2360V1.01> FUTURE Process: Assisting_gsmSSF Initial State: Await_Resource_Connection Internal Input: Int_SRF_Connected Action: Processing will be as in 03.78 Figure 54 sheet 2 1. Reset the Tssf timer to the user interaction value and restart it (see the section entitled "Timers and Timer Handling". Next State: Waiting_For_End_Of_User_Interaction References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2360V1>
Page:
Initial State: Waiting_For_End_Of_User_Interaction Internal Input: Int_SRF_Released Action: Processing will be as for 03.78 figure 54 sheet 3. Next State: Waiting_For_Instructions References: 23.018; 03.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-2380V1>
References: 03.78; 09.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: Assisting gsmSSF <End of R-FSD19337.2-2400V1>
Page:
<R-FSD19337.2-2430V1.01> FUTURE Initial State: Waiting_For_End_Of_User_Interaction Internal input: "Cancel failed" error indicated from SRF External output: CAP Cancel Failed error sent to gsmSCF. Action: Processing will be as in 03.78 figure 54 sheet 4. Next state: Waiting_For_End_Of_User_Interaction Notes: 2. This is the case where a Cancel operation was not successfully carried out, e.g., because the announcement was already successfully played. See the definition of the Cancel operation in 09.78. References: 03.78; 09.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783). Owner: Andrew McClurg Keyword: Assisting gsmSSF <End of R-FSD19337.2-2430V1>
Page:
Next state: Waiting_For_End_Of_User_Interaction Notes: 1. The PlayAnnouncement parameter is called "requestAnnouncementComplete". See 09.78. References: 03.78; 09.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783) . Owner: Andrew McClurg Keyword: Assisting gsmSSF <End of R-FSD19337.2-2450V1>
Page:
<R-FSD19337.2-2480V1.02> FUTURE Process: gsmSSF Initial State: Waiting_For_Instructions, Waiting_For_End_Of_User_Interaction Internal Input: Int_release_assisting_gsmSSF External Output: Int_assisting_gsmSSF_Released Next State: Idle Action: Processing will be as in 03.78 figure 54 sheet 6 1. The control relationship is terminated References: 03.78; 09.78 Feature ID: Modification Reason: In version 1.01, modified references (mr=17711) and marked the requirement as FUTURE (mr=17783). In version 1.02 changed duplicate reqs number (mr=18117/IMR=747756). Owner: Andrew McClurg Keyword: Assisting gsmSSF <End of R-FSD19337.2-2480V1>
10 MAP Requirements
This section contains all of the MAP operations that are affected by CAMEL, including new and modified operations. 03.78 and 23.078 contain the information flow view of the affected MAP operations, with descriptions of the new and modified information elements. 09.02 and 29.002 contain the protocol definitions and message handling. For modified MAP messages, no new message handling is specified in this requirements document. For new MAP messages for CAMEL, the section in 09.02 that must be followed is specified.
10.1 HLR !" VLR Information Flows 10.1.1 MAP ProvideSubscriberInfo operation
<R-FSD19337.2-3000V1.02> The ProvideSubscriberInfo operation, result and errors will be handled as defined in 29.002 and 03.78. 1. The parameters that will be supported in the ProvideSubscriberInfo result for location information will be: Age of location information VLR number Location number Service Area ID or LAI Current Location Retrieved indicator 2. Subscriber state is defined in 03.78 section 9.10.2. Message handling will be as specified in ETSI 29.002 section 21.2.6. Notes: 1. The ProvideSubscriberInfo operation may request subscriber location and/or state information. QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 103
Page:
2. The location number will be derived from the last known Service Area ID and LAI using the table defined in the VLR requirements section. References: 03.78; 29.002 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). In version, 1.02 clarified the parameters of the operation (mr=17861). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-3000V1> <R-FSD19337.2-3005V1.02> Upon receipt of a ProvideSubscriberInfo operation, the MSC must send back the information requested if available. Notes: 1. Information requested can include any or all of: VLR address, location area or Service Area ID, and subscriber state. 2. A separate data requirement covers the table that allows the derivation of geographical position from Service Area ID. References: 03.78; 09.02 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). In version, 1.02 clarified the parameters of the operation (mr=17861). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-3005V1>
The following CAMEL information elements will be supported in the DeleteSubscriberData operation, as specified in ETSI 29.002 and 03.78: 1. Camel Subscription Information Withdraw References: 03.78; 29.002 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-3020V1>
Page:
Notes: 1. Suppression of announcement and alerting pattern are covered in separate requirements below. 2. Refer to 03.78 and its section on the InitialDP information flow for details on the use of the GMSC address parameter. 3. The call reference number is included in the InitialDP sent to the gsmSCF. References: 03.78; 29.002 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-3050V1> <R-FSD19337.2-3052V1.01> After receipt of a ProvideRoamingNumber operation with the "announcement suppression" parameter included, the MSC must not play any switch generated error announcements back to the calling subscriber. Notes: 1. The reason for announcement suppression is so that callers to a CAMEL subscriber will not be able to determine where the CAMEL subscriber is based on a local VMSCs error message (e.g., a Swedish announcement would make it clear the subscriber was in Sweden). References: 03.78; 29.002 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-3052V1> <R-FSD19337.2-3054V1.01> After receipt of a ProvideRoamingNumber operation with the "alerting pattern" parameter included, the MSC will send the alerting pattern to the terminating CAMEL subscriber's mobile. Notes: 1. The mobile may not support the alerting pattern sent. References: 03.78; 29.002 Feature ID: 50.100 Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CCF <End of R-FSD19337.2-3054V1>
10.2 HLR !" GMSC Information Flows 10.2.1 MAP SendRoutingInfo operation
<R-FSD19337.2-3060V1.01> Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 106
Page:
The following CAMEL information elements will be supported in the SendRoutingInfo as specified in ETSI 29.002 and 03.78 section 9.12.1: 1. Alerting Pattern 2. Suppression of announcement (sent only in the second SRI, if available) 3. Suppress T-CSI (sent only in the second SRI) 4. Supported CAMEL phases 5. Call reference number 6. GMSC address The following CAMEL information elements will be supported in the SendRoutingInfo result, as specified in ETSI 29.002 and 03.78 section 9.11.1: 1. Location information 2. Originating CAMEL subscription information (O-CSI) 3. Subscriber state 4. Terminating CAMEL subscription information (T-CSI) 5. Basic Service code 6. GMSC CAMEL phases Notes: 1. The CUG subscription flag parameter will be required when CUG is supported. References: 03.78; 29.02 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-3060V1>
10.3 VMSC !" GMSC Information Flows 10.3.1 MAP ResumeCallHandling operation
<R-FSD19337.2-3070V1.01> The following CAMEL information elements will be supported in the ResumeCallHandling as specified in ETSI 29.02 and 03.78 section 9.12.1: 1. Originating CAMEL subscription information (O-CSI) The procedures for handling this operation will be as in ETSI 29.002 section 21.3. Notes: Optimal Routing will not be supported in R1V2, but other VMSCs may support it. References: 03.78; 29.002 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: gsmSSF <End of R-FSD19337.2-3070V1>
Page:
Issue: 4 107
11 CAP Requirements
11.1 CAP Application Contexts
<R-FSD19337.2-4000V1.01> The following CAP phase 2 application contexts will be supported as per ETSI 09.78 section 6.6: CAP-v2-gsmSSF-to-gsmSCF-AC APPLICATION-CONTEXT CAP-v2-assist-gsmSSF-to-gsmSCF-AC APPLICATION-CONTEXT CAP-v2-gsmSRF-to-gsmSCF-AC APPLICATION-CONTEXT Notes: these application contexts include application service elements (ASEs) that are defined in 09.78 section 6.5. References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4000V1> <R-FSD19337.2-4010V1> The following CAP phase 1 application context will be supported as per ETSI 09.78 release 96 (version 5.7.0) section 6.6 for subscribers whose CAMEL subscription information indicates that CAMEL phase 1 is the highest version supported: QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 108
Page:
CAP-v1-gsmSSF-to-gsmSCF-AC APPLICATION-CONTEXT Notes: 1. This application context includes application service elements (ASEs) that are defined in 09.78 section 6.4. 2. If a mobile subscriber's subscription data indicates CAMEL phase 1, then CAP phase 1 operations must be sent to the gsmSCF. References: 09.78 v5.7.0 Feature ID: 50.100F Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4010V1>
Page:
References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). In version 1.02 changed duplicate requirements number (mr=18117/IMR=747756). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4105V1>
Page:
Notes: This operation sends call related information to the gsmSCF previously requested via a CallInformationRequest operation. References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4130V1>
Page:
Notes: 1. This operation allows the gsmSSF to modify routing instructions. 2. The support of the "na-info" parameter in u01.03 is for further study. 3. The "alertingPattern" parameter, if sent from a gsmSCF to a GMSC in a Connect that does not change the destination number, is sent to the HLR in a second SendRoutingInfo operation. 4. The Generic Numbers received in the Connect operation replace any existing generic numbers. The maximum number of supported generic numbers is left to implementation. That is, supporting a maximum of 2 or 3 generic numbers is acceptable even though the ASN.1 states a maximum of 5. References: 09.78 Sections 9.11, Annex A.2 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). In version 1.03 added note on Generic number and added section numbers to reference. Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4150V1>
11.2.10
<R-FSD19337.2-4170V1.01> The CAP Continue operation will be supported as per ETSI 09.78. Notes: This operation instructs the gsmSSF to continue with call processing from the point at which it was suspended for the CAMEL interaction. . References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4170V1>
Page:
Issue: 4 112
11.2.11
<R-FSD19337.2-4170V1.01> The CAP DisconnectForwardConnection operation will be supported as per ETSI 09.78. Notes: This operation instructs the gsmSSF to tear down an announcement session. . References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4170V1>
11.2.12
<R-FSD19337.2-4180V1.01.03> The CAP EstablishTemporaryConnection operation will be supported as per ETSI 09.78. Contrary to ETSI 09.78 specification, the gsmSSF shall allow receipt of a correlationID parameter in the CAP ETC with a variable length of 2-16 octets. Contrary to ETSI 09.78 specification, the gsmSSF shall allow receipt of an assistingSSPIPRoutingAddresss parameter in the CAP ETC with a variable length of 3-16 octets. Notes: 1. This operation instructs the gsmSSF to set up an announcement session with an external IP or assisting gsmSSF. 2. The requirements to support a maximum of 16 octets for the correlationID and assistingSSPIPRoutingAddress are based on the engineering decision to implement Rel-99 TS 29.078 definition for maximum length of these parameters for CAMEL Phase 2. (In Rel-98 GSM specification 09.078, the correlationID and assistingSSPIPRoutingAddress are both defined to be maximum 11 octets long.) 3. Defining the minimum length of the assistingSSPIPRoutingAddress parameter to 3 octets long (contrary to the 3GPP Standards specification of minimum 2 octets) allows the re-use of the existing 5E code for design/implementation of this parameter. It is also very unlikely that the SCF will send an assistingSSPIPRoutingAddress parameter without the digits included in the parameter. 4. Based on ASN.1 definition in 09.078, the encoding of the scfID is network operator specific. For the correlationID CAP parameter, the encoding is based on the Generic Digits format specified in Figure 24 in ITU-T Recommendation Q.763.
5. If an error is encountered when mapping the scfId and/or correlationId received from the CAP ETC to the outgoing ISUP IAM message (e.g. the value received is 2 octets long but the ISUP parameters for scfId and/or correlation id require minimum length of 3 octets), the gsmSSF shall send an error response indicating ETCFailed to the QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 113
Page:
gsmSCF. For 3G-MSC ISUP requirements on SCF Id and Correlation Id optional parameters, refer to SRD-CC-IMS-IIUC-1. . References: 09.78, 29.078 Feature ID: 50.100F Modification Reason: - In version 1.01, modified references (mr=17711). - Correction of support for scfID and correlationID per MR=19737. Owner: Andrew McClurg, A.T.Remoquillo Keyword: CAP <End of R-FSD19337.2-4180V1.03>
11.2.13
<R-FSD19337.2-4190V1.01> The CAP EventReportBCSM operation will be supported as per ETSI 09.78. Notes: This operation reports an event to the gsmSCF previously requested via a RequestReportBCSMEvent operation. . References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4190V1>
11.2.14
<R-FSD19337.2-4200V1.01> The CAP FurnishChargingInformation operation will be supported as per ETSI 09.78. The format of the fCiBillingChargingCharacteristics parameter is network operator specific (NOS) and will be defined for the first release as follows:
1 2 3 4 5 6 7 8 9 10 11 12
8 Spare
7 FUB ind.
6 Dest. ind
5 Orig. ind.
4 Dial. ind.
3 AC/DC ind.
2 ABN ind
1 Annc
Spare Billing Data (CPS, SIC, BOP, Documentation Type) Announcement Units (optional) Length of Alternate Billing Number (optional) Alternate Billing Number (optional) Length of Account/Department Code (optional) Account/Department Code (optional) Length of Dialed Number (optional) Dialed Number (optional) Length of Originating Number (optional) Originating Number (optional) Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 114
13 14 15 16 17 18 19 20 21 22
Usage count 3 Usage count 7 Usage count 11 Usage count 15 Usage count 19 Usage count 23 Usage count 27 Usage count 31
Length of Destination Number (optional) Destination Number (optional) Usage count 2 Usage count 1 Usage count 6 Usage count 5 Usage count 10 Usage count 9 Usage count 14 Usage count 13 Usage count 18 Usage count 17 Usage count 22 Usage count 21 Usage count 26 Usage count 25 Usage count 30 Usage count 29
spare overflow Usage count 4 Usage count 8 Usage count 12 Usage count 16 Usage count 20 Usage count 24 Usage count 28
Notes: 1. This operation instructs the gsmSSF to create or overwrite a billing record and write information into it. 2. The above NOS format is equivalent to 5ESS SSP value 2 for option 9 of feature I1352. . References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4200V1>
11.2.15
<R-FSD19337.2-4210V1.01> The CAP InitialDP operation will be supported as per ETSI 09.78. Notes: 1. This operation opens a dialogue with a gsmSCF at DP2 or DP12. 2. For mobile originations, the locationNumber parameter is mapped from the location area and Service Area ID using a relation on the MSC. See the requirement in the VLR Requirements section. 3. The iPSSPCapabilities parameter will be as encoded in 09.78. The bilateral part is not specified in this requirements document at this time and will be added later for specific network operators. References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4210V1>
11.2.16
<R-FSD19337.2-4220V1.01> The CAP ReleaseCall operation will be supported as per ETSI 09.78. Issue: 4 115
Page:
Notes: 1. This operation instructs the gsmSSF to tear down a call. 2. The cause value contained in the operation is mapped to any forward and backward RANAP or ISUP release messages. References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4220V1>
11.2.17
<R-FSD19337.2-4230V1.01> The CAP RequestReportBCSMEvent operation will be supported as per ETSI 09.78. Notes: This operation instructs the gsmSSF to monitor for a call related event and then send an EventReportBCSM operation if that event is encountered. References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4230V1>
11.2.18
<R-FSD19337.2-4240V1.01> The CAP ResetTimer operation will be supported as per ETSI 09.78. Notes: This operation instructs the gsmSSF to reset the Tssf timer. References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4240V1>
11.2.19
<R-FSD19337.2-4250V1.03> The CAP SendChargingInformation operation will be supported as per ETSI 09.78. Notes: This operation instructs the gsmSSF to send charging information to a party in the call. It is used for mobile originations to send e-parameters (for GSM Advice of Charge) to a mobile station. QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 116
Page:
Notes: 1. Advice of Charge (AoC) will not be supported in R1V2, i.e., e-values will not be calculated on the MSC. Hence, the e-parameters received in the CAP SendChargingInformation message will not be sent to the MS. In addition, the gsmSSF will not send any error to the gsmSCF to indicate this. References: 09.78 Feature ID: 50.100F Modification Reason: - In version 1.01, modified references (mr=17711). - Modified Notes section per MR= 19740. Owner: Andrew McClurg, A.T.Remoquillo Keyword: CAP <End of R-FSD19337.2-4250V1.03>
11.2.20
<R-FSD19337.2-4260V1.01> The CAP PlayAnnouncement operation will be supported as per ETSI 09.78. The following constraints apply: 1. In the messageID parameter (within the inbandInfo parameter within the informationToSend parameter): elementaryMessageID elementaryMessageIDs variableMessage 2. Although CAP will support "duration" and "interval" parameters up to 32767 seconds, the CCF will support a maximum of 600 seconds (10 minutes) for the total announcement duration, and a maximum of 60 seconds for an announcement interval. Any duration timer value received in a PlayAnnouncement operation of greater than 600 seconds will be reduced to 600 seconds, and any interval timer value greater than 60 seconds will be reduced to 60 seconds. Notes: 1. This operation instructs a gsmSRF (e.g., switch based announcement and digit collection facility) to play an announcement. 2. The "text" parameter within the messageID parameter will not be supported. 3. Each duration and/or interval of 32767 seconds is over 9 hours long. Although the standard specifies this value, no service designer will ever ask for such a value, and if a gsmSCF did, it is considered acceptable for the gsmSSF and CCF to scale back the actual time that an announcement would play. 4. The "variableMessage" contains a "variablePart" that has as input integer numbers and which causes those numbers to be announced interspersed with a standard message. An example would be: "Your balance is five dollars and twenty seven cents", where the italicized numbers are specified in the variablePart parameter as actual integer numbers. The types are as follows: integer number (a string of individual numbers, e.g., telephone number) time date price QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 117
Page:
References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4260V1>
11.2.21
<R-FSD19337.2-4270V1.01> The CAP PromptAndCollectUserInformation operation will be supported as per ETSI 09.78. The following constraints apply: 1. In the messageID parameter (within the inbandInfo parameter within the informationToSend parameter): elementaryMessageID elementaryMessageIDs variableMessage 2. Although CAP will support "duration" and "interval" parameters up to 32767 seconds, the CCF and or LMS retains the right to run guard timers and to cut off announcements when it deems it appropriate. 3. The "voiceInformation" parameter will be supported for "FALSE. 4. An end of reply digit parameter may be included in this operation. It can be one or two digits and can take the value 0-9 "star" (0x0A) or "pound" (0x0B). 5. A cancel digit parameter may be included in this operation. It can be any digit from 0-9 or "star" or "pound". Only one cancel digit can be received for a prompt and collect session before error processing occurs. If a second cancel digit is received (i.e., during the repeat of the prompt and collect sequence caused by the first cancel digit), then this will be treated as an error condition. Note that if the error treatment is "reprompt" then the whole prompt and collect sequence will begin again, and a cancel digit will again be valid one time. 6. A start digit parameter may be included in this operation. It can be any digit from 0-9 or "star" or "pound". 7. The rest of the standard functionality will be supported (see notes). Notes: 1. This operation instructs a gsmSRF (e.g., switch based announcement and digit collection facility) to play an announcement and collect digits or other in band information. 2. For details on the announcement part, see the "PlayAnnouncement" operation above. 3. Text to speech will not be supported in u01.03 for the internal SRF. External IPs may support this. 4. User input can be terminated by one of the following. Once a termination condition is encountered, no more digits will be processed. maximum number of digits reached (this is a parameter of the operation) end of reply received cancel received pre digit timeout inter digit timeout 5. If the minimum number of digits is not received, this is treated as an error condition (see errorTreatment parameter below). The default value is 1. 6. The "voiceBack" parameter will not be supported. 7. The "interruptibleAnnInd" parameter will be supported, i.e., if this value is set to "TRUE" then the first received digit will halt the announcement and that digit will be processed. If this value QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 118
8.
9. 10. 11.
12. 13.
is set to FALSE then the announcement will play to completion while digits may be collected at the same time. The errorTreatment parameter determines what happens if there is an error in the digit collection process. The default is "standard error and info" which means that normal error processing occurs, i.e., a return error is sent to the SCP. The second option is "help" which indicates that no error is returned to the SCP, and instead a network dependent default announcement is played to the caller and digits collection is repeated. The third option is "repeat prompt", where the original announcement is repeated and digits collection is repeated. The second or third option is executed only once. A second error will result in standard error treatment. (see 03.78 section 9.22.3.1). The first received digit that interrupts an announcement may be valid or invalid, and will be processed accordingly. The start digit may be any one or two digit string, as per 09.78. When a cancel digit is received, all previously received digits are discarded and the prompt and collect sequence begins again, i.e., the prompt announcement is replayed and data entry begins again. It makes little sense from a service perspective to have an end of reply or cancel digit as a regular number (0-9). More sophisticated automatic speech recognition is for further study.
References: 09.78, 03.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711) and removed stated support for text to voice, voice recognition and voice back (rm=17783). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4270V1>
11.2.22
<R-FSD19337.2-4280V1.01> The CAP SpecializedResourceReport operation will be supported as per ETSI 09.78. Notes: 1. This operation is used by the gsmSRF to notify a gsmSCF that an announcement session is complete. 2. This is a linked operation -- linked to a previously received PlayAnnouncement operation. Thus the TCAP invoke will include a linked ID that is the invoke ID of the PlayAnnouncement operation to which the SpecializedResourceReport is responding References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4280V1>
11.2.23
Operation Timers
<R-FSD19337.2-4290V1.01> Timers for individual operations will be modifiable through the administrative terminal within the bounds established for the specific timer value -- e.g., short, medium or long. The default values for operation timers are as follows: QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Page: Issue: 4 119
Short: 10 seconds Medium: 30 seconds Long: 120 seconds Notes: 1. Timers for each operation are specified in 09.78 section 6.1. Each operation timer is assigned a value of "short", "medium" or "long", which gives a range for the timer. References: 09.78 Feature ID: 50.100F Modification Reason: In version 1.01, modified references (mr=17711). Owner: Andrew McClurg Keyword: CAP <End of R-FSD19337.2-4290V1>
Page:
Issue: 4 120
13 Billing Requirements
The billing information specified in this section is derived from 3GPP specification 32.005 "GSM call and event data for the Circuit Switched (CS) domain (Release 99)". For further information on the fields, please refer to that document, available from the 3GPP server (see References section).
Page:
Issue: 4 121
Field
Translated Number gsmSCF address Service key Network call reference MSC Address Default call handling Number of DP encountered Level of CAMEL service Free format Data O C C C C O O O C
Description
The called number after digit translation within the MSC (if applicable) Identifies the CAMEL server serving the subscriber. The CAMEL service logic to be applied. An identifier to correlate transactions on the same call taking place in different network nodes, shall be present if CAMEL is applied. This field contains the E.164 number assigned to the MSC that generated the network call reference. Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. Number that counts how often armed detection points (TDP and EDP) were encountered. Indicator for the complexity of the CAMEL feature used. This field contains data sent by the gsmSCF in the FCI message(s). The data can be sent either in one FCI message or several FCI messages with append indicator. Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Indicates whether or not a CAMEL call encountered default call handling for 2nd service such as dialled service. This field shall be present only if default call handling has been applied. Identifies the CAMEL server serving the subscriber for 2nd service such as dialled service. The CAMEL service logic to be applied for 2nd service such as dialled service. nd This field contains data sent by the gsmSCF in the FCI message(s) for 2 service such as dialled service. The data can be sent either in one FCI message or several FCI messages with append indicator. Indicator if free format data for 2nd service from this CDR is to be appended to free format data in previous partial CDR. This is not in 32.005 but is added for this requirements document.
CAMEL call leg information Free format data append indicator Default call handling 2
C C O
C C C
C M
Table 1
Page:
GsmSCF address 2 Service key 2 Free format data append indicator 2 Free format data append indicator 2
2. The following Lucent extensions have been added to the MOC, CF call attempt record for invocation of CAMEL Trigger Detection Points at the GMSC for Lucent's Flexent Packet Gateway (FPG) product: - NAOliInfo - NAChargeNumber Refer to SRD-1992 and SRD-CC-FPG-UPCR-1 for CAMEL billing requirements specific to Lucent's FPG Carrier Select feature. References: 32.005 V3.6.0 Feature ID: 50.100 Modification Reason: Additional notes for clarification (MR= 19742). Owner: Andrew McClurg, A.T.Remoquillo Keyword: Billing and Charging <End of R-FSD19337.2-6010V1.03>
Page:
Issue: 4 123
Field gsmSCF address Service key Network call reference MSC Address CAMEL initiated CF indicator Default call handling Number of DP encountered Level of CAMEL service Free format Data
C C C C C O O O C
CAMEL call leg information Free format data append indicator Default call handling 2
C C O
C C C
Free format data append indicator 2 SCP translated number NAOliInfo NAChargeNumber
C M C C
Description Identifies the CAMEL server serving the subscriber. The CAMEL service logic to be applied. An identifier to correlate transactions on the same call taking place in different network nodes, shall be present if CAMEL is applied. This field contains the E.164 number assigned to the MSC that generated the network call reference. Indicates that the CAMEL server initiated call forwarding. Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. Number that counts how often armed detection points (TDP and EDP) were encountered. Indicator of the complexity of the CAMEL feature used. This field contains data sent by the gsmSCF in the FCI messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Indicates whether or not a CAMEL call encountered default call handling for 2nd service such as dialled service. This field shall be present only if default call handling has been applied. Identifies the CAMEL server serving the subscriber for 2nd service such as dialled service. The CAMEL service logic to be applied for 2nd service such as dialled service. This field contains data sent by the gsmSCF in the FCI message(s) for 2nd service such as dialled service. The data can be sent either in one FCI message or several FCI messages with append indicator. Indicator if free format data for 2nd service from this CDR is to be appended to free format data in previous partial CDR. This is not in 32.005 but is added for this requirements document. Added as a Lucent extension for the Carrier Select feature. This field contains the North America Originating Line Information received from the gsmSCF. Added as a Lucent extension for the Carrier Select feature. This field contains the North America Charge Number received from the gsmSCF.
Table 2
Page:
- NAChargeNumber Refer to SRD-1992 and SRD-CC-FPG-UPCR-1 for CAMEL billing requirements specific to Lucent's FPG Carrier Select feature.
References: 32.005 v3.6.0 Feature ID: 50.100 Modification Reason: Modified to be compliant with R99 Specifications (MR=19742). Owner: Andrew McClurg, A.T.Remoquillo Keyword: Billing and Charging <End of R-FSD19337.2-6020V1.03>
Field Record Type Served IMSI Served MSISDN Recording Entity Int. time stamp CAMEL Destination Number gsmSCF Address Service key Network call reference MSC Address Default call handling Record extensions Called Number Calling Number Incoming TKGP Outgoing TKGP Event time stamps: Description Terminating CAMEL interrogation. IMSI of the called party The MSISDN of the called party. The E.164 number of the GMSC. Time at which the interrogation was invoked. The number available for routing after the CAMEL server enquiry. The CAMEL server serving the subscriber. The CAMEL service logic to be applied. An identifier to correlate transactions on the same call taking place in different network nodes, shall be present if CAMEL is applied. This field contains the E.164 number assigned to the MSC that generated the network call reference. Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. A set of network/ manufacturer specific extensions to the record. The address of the called party as received by the GMSC/gsmSSF. The address of the calling party, if available. The GMSC trunk group on which the call originated. The trunk group on which the call left the GMSC Seizure of incoming traffic channel (for unsuccessful call attempts) Answer (for successful calls) Release of traffic channel The chargeable duration of the connection for successful calls, the holding time of call attempts. The number of data segments transmitted if available at the GMSC The reason for the release of the connection. A more detailed reason for the release of the connection. A local identifier distinguishing between transactions on the same MS Partial record sequence number, only present in case of partial records. Number that counts how often armed detection points (TDP and EDP) were encountered. Indicator of the complexity of the CAMEL feature used. This field contains data sent by the gsmSCF in the FCI message Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Added as a Lucent extension for the Carrier Select feature. This field contains the North America Originating Line Information received from the gsmSCF. Added as a Lucent extension for the Carrier Select feature. This field contains the North America Charge Number received from the gsmSCF.
M M O M M M M M M M O O M C O O C C O M C M O M C O O C C C C
Call duration Data volume Cause for termination Diagnostics Call reference Sequence no. Number of DP encountered Level of CAMEL service Free format Data CAMEL call leg information NAOliInfo NAChargeNumber
<R-FSD19337.2-6030V1.03> (DELETED) QDI ID: 19337 Date: November 18, 2002 Author: Marianne Picha Lucent Technologies - Proprietary Issue: 4 125
Page:
References: 32.005 v3.1.0 Feature ID: 50.100 Modification Reason: Deleted requirement to be compliant with 3GPP specification (MR=19742). Owner: Andrew McClurg, A.T.Remoquillo Keyword: Billing and Charging <End of R-FSD19337.2-6030V1.03>
14 Performance Requirements
The UMTS MSC based on the Lucent SoftSwitch (LSS) platform is required to support 360,000 busy hour calls. In addition, the expectation is that 100% of the subscribers will be CAMEL (or Intelligent Network) subscribers. CAMEL processing requires real time, and thus the baseline capacity of the UMTS MSC without CAMEL must be higher than 360K BHCA.
Page:
Issue: 4 126
CAMEL Originations
C A M E L _ O C H _M S C _ A N S W E R
O G _ C A L L _ S E T U P_ M S C
C A M E L _O C H _M S C _ D IS C 1
C A M E L _ O C H _ M S C _ D IS C 2
C A M E L _ O C H _ M S C _ IN IT
S E N D _ A C C E S S _ C O L L E C T _ IF _ R E Q U IR E D
S E N D _ A L E R T IN G _ IF _ R E Q U IR E D
C A M EL _OC H _C TR
C A M E L _O C H _ E T C C A M E L _ O C H _M S C 1
C A M E L _ S ta rt _ T N R y C A M E L _ O C H _M S C _ D IS C 4
C A M E L _ S to p _ T N R y
Page:
Issue: 4 127
CAMEL Terminations
IN CCF
CAMEL_MT_GMSC_ANSWER MT_GMSC CAMEL_MT_GMSC_DISC1 CAMEL_SET_ORA _PARAMETERS CAMEL_MT_GMSC_DISC2 CAMEL_MT_GMSC_INIT Obtain_Routeing _Address
SEND_ACM_IF_REQUIRED
CAMEL_MT_ETC CAMEL_MT_GMSC_DISC5
CAMEL_MT_GMSC_DISC3
(CAMEL Phase 1 only)
CAMEL_Stop_TNRy
Page:
Issue: 4 128
Call Forwarding
CAMEL_CF_MSC_ANSWER MT_CF_MSC CAMEL_OCH_MSC_DISC1
CAMEL_OCH_MSC_DISC2
CAMEL_CF_MSC_INIT
SEND_ACM_IF_REQUIRED
CAMEL_CF_ETC
SEND_ANSWER_IF _REQUIRED
CAMEL_OCH_MSC_DISC3
Not defined in 03.78?,
CAMEL_OCH_MSC_DISC4*
CAMEL_Start_TNRy
CAMEL_Stop_TNRy
Page:
Issue: 4 129
Page:
O-CSI & FTN (received in either 1st or 2nd SendRoutingInfo result): Use forward to number to launch query to the gsmSCF indicated in O-CSI
Page:
Issue: 4 131