strategic crs to gsm 03.32, gsm 03.78 and gsm … · corresponding crs to gsm 03.78 and gsm 09.02...
TRANSCRIPT
ETSI SMG#27 Tdoc SMG 0724/98 Praha, 12 to 16 October 1998Agenda Item: 6.3
Source: SMG3Date: September 1998
Strategic CRs to GSM 03.32, GSM 03.78 and GSM 09.02 related toCAMEL Phase 2 (Release 97)
CR 03.16-A016r1 (R97-F) on CAMEL capability handling CR 03.78-A025r2 (R97-F) on CAMEL Phase 2 stage 2CR 03.78-A029r1 (R97-F) on Corrections to Any Time InterrogationCR 03.78-A034r2 (R97-F) on Interworking CAMEL with general Bearer Service CR 03.78-A037r1 (R97-C) on Removal of O_Not_Reachable and T_Not_Reachable detection pointsCR 03.78-A043 (R97-C) on GSM Forwarding Pending Indication in IDP Operation
CR 09.02-A138 (R97-F) on Extending the applicability of GMSC Address in ProvideRoamingNumber CR 09.02-A149 (R97-F) on Clarification of limit on length of O-CSI in MAP_RESUME_CALL-HANDLING CR 09.02-A152r1 (R97-C) on Support of CAMEL Phase 2 CR 09.78-A031r2 (R97-F) on Corrections on GSM 09.78 CR 09.78-A033r1 (R97-F) on Support of CAMEL Phase 2
Corresponding CRs to GSM 03.78 and GSM 09.02 for Release 96 related to CAMEL Phase 1 areforwarded for approval in Tdoc SMG 98-0723:
CR 03.78-A033 (R96-F) on Corrections to Any Time Interrogation
CR 09.02-A137 (R96-F) on Extending the applicability of GMSC Address in ProvideRoamingNumber CR 09.02-A148 (R96-F) on Clarification of limit on length of O-CSI in MAP_RESUME_CALL-HANDLING
Change Request No. A016 rev 1
Technical Specification GSM 03.16 version 6.1.0
Submitted to SMG for approval: without presentation ("non-strategic") [ ]with presentation ("strategic) [ x ]
Status at SMG [#27]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [ X ] Work item: CAMEL Phase 2
Other phase(s) affected: [ ] If yes, linked CR(s):
Proposed change affects: SIM [ ] ME [ ] Network [ X ]
Source: SMG3 Tdoc SMG3 98C490 Date: September 1998
Subject: CAMEL Capability Handling Parameter
Category: F - Correction [ X ]A - Corresponds to a Phase 2 correction [ ]B - Addition of Feature [ ]C - Functional modification of Feature [ ]D - Editorial modification [ ]
Reason for change:
Correction of CAMEL phase 2 data in VLR by including missing CAMEL Capability Handling parameter, which ispart of the O-CSI subscription.VMSC/VLR needs to store the CAMEL Capability Handling to use correct BCSM/SSF and CAP version on SSF -SCF interface.
Sections affected, and additional explanation of details of change (if needed):
4.4 (Fig. 12)
Attached revised pages:
Page(s): 22
If other core Specifications are affected, necessary (and attached) Joint CRs: 03.08-A015
Affects (possibly): MS Test Specs [ ] BSS Test Specs [ ] O&M Specs [ ]Attached CRs?:
Cross Phase Compatibility:Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ]
CR to 09.90 attached:Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ]
CR to 09.91 attached:Phase 2(+) SIM in Phase 1 ME [ ]CR to 09.91 attached:
Other comments:
Page 22GSM 03.16 v5.1.0 April 1997
ÀÄVBS membership List ³ ÃÄGroup-Id(1) ³ ÀÄBroadcast Call Initiation Entitlement ³ ÃÄ..... ³ ÀÄGroup-Id (n) ÀÄBroadcast Call Initiation Entitlement
NOTE: For detailed information see GSM 03.69 and GSM 09.02.
Figure 11: Voice Broadcast Call Data
ÀÄCAMEL Subscription Information ³
ÃÄ CAMEL Capability Handling ³ ÃÄoriginating CAMEL Subscription Info ³ ³ ³ ÃÄO-Bcsm CAMEL TDP Data (1) ³ ³ ³ ³ ³ ÃÄ O-Bcsm TDP ³ ³ ÃÄ DP Criteria ³ ³ ÃÄ Service Key ³ ³ ÃÄ gsmSCF Address ³ ³ ÀÄ Default Call Handling ³ ³ ³ ÃÄ..... ³ ³ ³ ÀÄO-Bcsm CAMEL TDP Data (n) ³ ³ ³ ÃÄ O-Bcsm TDP ³ ÃÄ DP Criteria ³ ÃÄ Service Key ³ ÃÄ gsmSCF Address ³ ÀÄ Default Call Handling
³ ÀÄSS Invocation Notification CAMEL Subscription Info
³ ÃÄ Notification Criteria
ÀÄ gsmSCF address
NOTE: For detailed information see GSM 03.78 and GSM 09.02.
Figure 12: CAMEL subscription info
CHANGE REQUEST No. A025r2
Technical Specification GSM 03.78 version 6.1.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic") [ x ]
Status at SMG [#27]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [R97] Work item: CAMEL Phase 2
Other phase(s) affected: [ ] If yes, linked CR(s):
Proposed change affects: SIM [ ] ME [ ] Network [ ]
Source: SMG3 Tdoc SMG3 98C576 Date: September 1998
Subject: CAMEL Phase 2 Stage 2
Category: F - Correction [ x]
A - Corresponds to a Phase 2 correction [ ]
B - Addition of Feature [ ]
C - Functional modification of Feature [ ]
D - Editorial modification [ ]
Reason for change:
Correction to CAMEL Phase 2 handling of Release notification whilst in states 'Waiting For End Of TemporaryConnection' or 'Waiting For End Of User Interaction' in O_Disconnect or T_Disconnect DP.
Sections affected, and additional explanation of details of change (if needed):
.
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects(possibly):
MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ]
Attached CRs?:
Cross Phase Compatibility:
Other comments:
Page 2CR to GSM 03.78 v6.1.0 September 1998
Procedure in the MSC to performCAMEL handling for an outgoingcall request
Procedure CAMEL_OCH_MSC_ INIT 1(4 )
Signals to/from the right are to/from the gsmSSF.
O-CSI invocation?
Result:=pass
Allocatecall reference
number
Store originalcall parameters
Int_Invoke_gsmSS F(O-CSI)
Wa it_for_gsmSSF_Invoked
Int_error
Result:=fail
Int_gsmSSF_Invoked
Int_DP_Collec ted_Info
DP_Collected_
Info
Release
Int_O_Exception
Res ult :=fail
No
Yes
Page 3CR to GSM 03.78 v6.1.0 September 1998
Procedure in the MSC to performCAMEL handling for an outgoingcall request
Procedure CAMEL_OCH_MSC_ INIT 1(4 )
Signals to/from the right are to/from the gsmSSF.
O-CSI invocation?
Result:=pass
Allocatecall reference
number
Store originalcall parameters
Int_Invoke_gsmSS F(O-CSI)
Wa it_for_gsmSSF_Invoked
Int_error
Result:=fail
Int_gsmSSF_Invoked
Int_DP_Collec ted_Info
DP_Collected_
Info
Release
Int_O_Exception
Res ult :=fail
Call_Ac tive :=False
No
Yes
Page 4CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the MSC to handle an outgoing call
Procedure CAMEL_OCH_MSC_ANSW E R 1(1 )
Signals to/from the left areto/from the BSS; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.gsmSS F
invoked?
Result:=pass
Int_DP_O_Answer
DP_O_Answer
Int_Continue
Send_A ccess_Connect_If_
Required
Procedure definedin GSM 03.18
Result :=pass
Int_Release
Release
Release
Res ult :=fail
Release
CAMEL_OCH_MSC_DISC1
Result :CAMEL_Handling
Release
ReleaseFrom d estinationexchange
CAMEL_OCH_MSC_DISC2
Result=reconnect?
Result:CAMEL_Handling
Release
Result:=rec onnec t
No
Yes
No
Yes
No
No
Yes
Yes
Page 5CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the MSC to handle an outgoing call
Procedure CAMEL_OCH_MSC_ANSW E R 1(1 )
Signals to/from the left areto/from the BSS; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.gsmSS F
invoked?
Result:=pass
Int_DP_O_Answer
DP_O_Answer
Int_Continue
Send_A ccess_Connect_If_
Required
Procedure definedin GSM 03.18
Result :=pass
Int_Release
Release
Release
Res ult :=fail
Release
CAMEL_OCH_MSC_DISC1
Result :CAMEL_Handling
Release
ReleaseFrom d estinationexchange
CAMEL_OCH_MSC_DISC2
Result=reconnect?
Result:CAMEL_Handling
Release
Result:=rec onnec t
Call_Active :=True
Call_A ctive :=False
No
Yes
No
Yes
No
No
Yes
Yes
Page 6CR to GSM 03.78 v6.1.0 September 1998
Procedure in the MSC performhandling for a call release
Procedure CAMEL_OCH_MSC_DISC2 1(2 )Signals to/from the left areto/from the BSS or the processMT_GMSC; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.gsmSS F
invoked?
Int_DP__O_Disconnec t/* legId = 2 */
DP_O _Disconnect_2
Release
Int_DP_O _Disconnect/* legId = 1 */
DP_O_Disconnect
Int_Error
result :=CAMEL_handling
Int_Continue Int_ReleaseCall
Int_Continue
Release
result:=CAMEL_handling
Int_Release_Call Int_error Int_Connect
Modify call parameters with
received information
Destinationm odified?
Send Info ForReconnected Call
To processCAMEL_Reconnected_Call_VLR
Wait_ForRec onnected_
Call_2
S end Info ForReconnected CallNegative Response
From processCAMEL_Reconnected_Call_VLR
Int_DP__O_Disconnec t/* legId = 2 */
DP_O _Disconnect_2
Send Info ForReconnected CallAck
F rom processCAMEL_Reconnected_Call_VLR
Result:=reconnec t
result:=normal_handling
Yes
No
Yes
No
Page 7CR to GSM 03.78 v6.1.0 September 1998
Procedure in the MSC performhandling for a call release
Procedure CAMEL_OCH_MSC_DISC2 1(2 )Signals to/from the left areto/from the BSS or the processMT_GMSC; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.gsmSS F
invoked?
Int_DP__O_Disconnec t/* legId = 2 */
DP_O _Disconnect_2
Release Int_Continue Int_Release_Call Int_error Int_Connect
Int_DP_O _Disconnect/* legId = 1 */
Modify call parameters with
received information
DP_O_Disconnect
Destinationm odified?
Release
Int_Error Int_Continue Int_ReleaseCallSend Info ForReconnected Call
result:=normal_handling
result:=CAMEL_handling
result :=CAMEL_handling
To processCAMEL_Reconnected_Call_VLR
Wait_ForRec onnected_
Call_2
From processCAMEL_Reconnected_Call_VLR
S end Info ForReconnected CallNegative Response
From processCAMEL_Reconnected_Call_VLR
Send Info ForReconnected CallAck
Int_DP__O_Disconnec t/* legId = 2 */ Call_A ctive :=
False
DP_O _Disconnect_2 Result:=
reconnec t
Yes
No
No
Yes
Page 8CR to GSM 03.78 v6.1.0 September 1998
Procedure in the orig inating MSC to handle a Connect To Resourceoperation
Procedure CAMEL_OCH_CTR 2(4 )
Signals to/from the left areto/from the BSS ;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Relay
Int_Disconnec t_Forward_Connection
Int_Disconnec t_SRF
To SRF
Await_SRF_Disconnection_
Continue
Int_SRF_Released
From SRF
Int_SRF_Released
Result:=pass
Release
Int_DP_O_Disconnec t/* legID */
Wa it_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Fail
Page 9CR to GSM 03.78 v6.1.0 September 1998
Procedure in the orig inating MSC to handle a Connect To Resourceoperation
Procedure CAMEL_OCH_CTR 2(4 )
Signals to/from the left areto/from the BSS ;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Relay
Int_Disconnect_Forward_Connection
Release
Int_Disconnect_SRF
To SRFCall_
Active
Await_SRF_Disconnection_
Continue
Int_SRF_Released
From SRFInt_DP_O_Disconnect/* legID */
Int_DP_O_Abandon/* legID */
Int_SRF_ReleasedW ait_For_Disc onnect_Forward_Connection
Wa it_For_Disconnect_Forward_Connection
Result:=pass
Int_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRFInt_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Active
Await_SRF_Disconnection_
Fail
Int_SRF_Released
Result :=P ass
True False
Page 10CR to GSM 03.78 v6.1.0 September 1998
Procedure in the orig inating MSC to handle a Connect To Resourceoperation
Procedure CAMEL_OCH_CTR 4(4 )
Signals to/from the left areto/from the BSS ;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Await_SRF_InitialisationWa it_For_Connect_Ack
Relase
Int_DP_O_Abandon
Int_Disconnect_SRF To SRF
Await_SRF_Disconnection_
Fail
Int_SRF_Released
From SRF
Result:=fail
Page 11CR to GSM 03.78 v6.1.0 September 1998
P rocedu re in the o rigin at ing MSC t o h an dle a C onn ec t To Resourceo p era tio n
Procedure CAMEL_OCH_CTR 4(4)
S ig n als to /from th e le ft areto/ from th e BS S;sign a ls to /from the r ig h t a re to /fromthe g smSSF if not otherwise stated.
A w ait_ S RF_In i tialisa tio nW ait_For_Con nect_Ack
R e lease
C a ll_A ct ive
Int_DP_O_Disconnect/*leg ID */
Int_Disconnect_SRF To SRF
A w ait_SRF_Disconnectio n _
A ctive
Int_SRF_Released
From SRF
R e sult: =p as s
Int _DP _O_A b and on
Int _Disconnec t_S RF To SRF
Await _S RF_Disc on nec tion _
Fail
Int _S RF_R e lease d
From SRF
Result:=fail
Tru e False
Page 12CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_OCH_ETC 1(3 )Signals to/from the left are to/fromthe BSS;signals to/from the right areto/from the gsmSSF;if not otherwise stated.
InitialAddress
To process CAMEL_Assisting_MSCor SRF
Send_Alerting_If_Required
Procedure definedin GSM 03.18
W ait_For_As sisting_ACM
Release ReleaseFrom destinationexchange
Int_DP_O_Abandon Int_ETC_Failed
ReleaseTo processCAMEL_Assist ing_MSC or SRF
Result:=pass
Result:=fail
Page 13CR to GSM 03.78 v6.1.0 September 1998
P rocedu re in the M SC t o h an dle a t em poraryc on nec tion
Proc edure CAMEL_OCH_ETC 1(3)Signals to/from t he left a re to /fromth e BSS;signals to/from the r ig h t areto /from th e gs m SSF;if n ot oth e rwise state d.
Init ialAddress
To process C A ME L _As sisting_MS Cor SRF
S end_A lerting_If_Req uire d
P rocedure definedin GSM 03. 18
W ait_For_Assisting_ACM
Release
Ca ll_Active
Int_DP_O_Disc onn ec t/*legID*/
W ai t_For_Disconnec t_Forward_Connec tion
Int_Disconnect_Forward_Connec tion
ReleaseTo processCAMEL_As sisting_MS C or SRF
Result :=pass
In t_ DP _O _Ab an don
Releas eTo p rocessCAMEL_Assisting_M SC or SRF
Result:=fa il
ReleaseFrom destinationexcha ng e
Int_ E TC_Failed
Result :=pass
True False
Page 14CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_OCH_ETC 3(3 )
Signals to/from the left are to/fromthe BSS;signals to/from the r ight areto/from the gsmSSF;if not otherwise stated.Temporary_Connection_Established
Wa it_For_Assisting_Answer
Release
Int_DP_O_Abandon
ReleaseTo processAssisting_SSFor SRF
Result :=fail
ReleaseFrom destinationexchange
Int_TC_Released
Result:=pass
Int_Disconnect_Forward_Connection
Int_TC_Released
ReleaseTo destinationexchange
Result :=pass
Page 15CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_OCH_ETC 3(3 )
Signals to/from the left are to/fromthe BSS;signals to/from the r ight areto/from the gsmSSF;if not otherwise stated.Temporary_Connection_Established
Wa it_For_Assisting_Answer
Release ReleaseFrom destinationexchange
Int_Disconnect_Forward_Connection
call_Active
Int_TC_Released
Int_TC_Released
Result:=pass
ReleaseTo destinationexchangeInt_DP_O_
Disconnec t/*legID*/
Int_DP_O_Abandon
Result:=pass
W ait_For_Disconnect_Forward_Connection
ReleaseTo processCAMEL_A ssisting_MSC or SRF
Result:=fail
T rue
false
Page 16CR to GSM 03.78 v6.1.0 September 1998
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 2(8 )
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF
wait_for_gsmSSF_Invoked
Int_gsmSSF_Invoked
Int_DP_Termination_attempt_Autorized
DP_Term ination_attempt_Autorized
Release
Int_T_Exception
Result:=aborted
Page 17CR to GSM 03.78 v6.1.0 September 1998
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 2(8 )
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF
wait_for_gsmSSF_Invoked
Int_gsmSSF_Invoked
Int_DP_Termination_attempt_Autorized
DP_Term ination_attempt_Autorized
Release
Int_T_Exception
Result :=aborted
Call_A ctive :=False
Page 18CR to GSM 03.78 v6.1.0 September 1998
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_ANSW E R 1(1 )
Signals to/from the left are to/fromthe orig inating exchange;signals to/from the right are to/fromthe terminating exchange if nototherwise stated.
gsmSSFinvok ed?
Result :=pass
Int_DP_T_Answer to gsmSSF
DP_T_Answer
Int_Release from gsmSSF
Release
Release
Result :=fail
Release
CAMEL_MT_GMSC_DISC1
Result=CAMEL_handling?
Release
Res ult :=fail
Release
CAMEL_MT_GMSC_DISC2
Result=reconnect?
Result=CAMEL_handling?
Release
Result:=rec onnec t
Int_continuefrom gsmSSF
Result:=pass
no
yes
No
Yes
No
No
Yes
Page 19CR to GSM 03.78 v6.1.0 September 1998
Process in th e GMS C t o ha ndle at erm ina ting call request
Procedure CAMEL_MT_GMSC_ANSW E R 1(1)
Sig na ls to/ from t he lef t a re to /fromth e o rig ina ting exch a nge ;sign a ls to /from the r ig h t a re to /fromth e te rminating exchan ge if n otot he rwis e s tate d.
gsm S SFinvoke d?
Result:=pass
In t_ DP _T_A nsw er t o g s m S SF
Call_Active :=Tru e
DP _T_Answer
Int_Release from g s m S SF
Release
Release
Result:=fail
Releas e
C A ME L_MT_GMSC_DISC1
Result=CAMEL_handling?
Releas e
Result:=fa il
Release
CAMEL_MT_GMSC_D IS C2
R esult=recon nect?
R esult=C AMEL_handling?
Release
Call_Active :=False
R e sult: =rec onn ec t
In t_con tinu efrom g s m S SF
R e sult: =p ass
n oyes
No
Yes
N o
N o
Yes
Page 20CR to GSM 03.78 v6.1.0 September 1998
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC2 1(1 )
Signals to/from the left are to/from theoriginating exchange;signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
gsmSSFinvok ed?
Int_DP_T_Disconnect/* legId = 2 */
DP_T_Disconnect_2
Int_Connect
Modify callparameters with
received information
Result:=reconnec t
Int_Error
Release
Result:=CAMEL_handling
Int_Continue Int_Release_Call Release
Int_DP_T_Disconnec t/* legId = 1 */
DP_T_Disconnect
Int_Error Int_Continue Int_ReleaseCall
Result :=normal_handling
Yes
No
Page 21CR to GSM 03.78 v6.1.0 September 1998
Process in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC2 1(1 )
Signals to/from the left are to/from theoriginating exchange;signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
gsmSSFinvok ed?
Int_DP_T_Disconnect/* legId = 2 */
DP_T_Disconnect_2
Int_Connect Int_Error Int_Continue Int_Release_Call Release
Modify callparameters with
received information
ReleaseInt_DP_T_Disconnec t/* legId = 1 */
Call_A ctive :=False
DP_T_Disconnect
Int_Error Int_Continue Int_ReleaseCall
Result :=normal_handling
Result:=reconnec t
Result:=CAMEL_handling
Yes
No
Page 22CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the M SC to handlea Connec t To Resource operat ion
Procedure CAMEL_MT_CTR 2(4 )
Signals to/from the left areto/from the originating exchange;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Relay
Int_Disc onnec t_Forward_Connection
Int_Disc onnec t_SRF
To SRF
Await_SRF_Disconnection_
Continue
Int_SRF_Released
From SRF
Int_SRF_Released
Result:=c ontinue
Release
Int_DP_T_Disconnec t/* legID */
Wa it_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Fail
Page 23CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the M SC to handlea Connec t To Resource operat ion
Procedure CAMEL_MT_CTR 2(4 )
Signals to/from the left areto/from the originating exchange;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Relay
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Continue
Int_SRF_Released
From SRF
Int_SRF_Released
Result:=c ontinue
Release
Int_DP_T_Abandon/* legID */
Call_Active
Int_DP_T_Disconnect/* legID */
Wa it_For_Disconnect_Forward_Connection
W ait_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRFInt_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Active
Await_SRF_Disconnection_
Fail
Int_SRF_Released
Result :=P ass
FalseTrue
Page 24CR to GSM 03.78 v6.1.0 September 1998
Procedure in the MSC to handlea Connect To Resourc e operation
Procedure CAMEL_MT_CTR 4 (4)
Signals to/from the left areto/from the originating exchange;signals to/from the right are to/fromthe gsmSSF if not otherw ise stated.
Await_SRF_InitialisationW ait_For_Connect_Ac k
Relase
Int_DP_T_Abandon
Int_Disconnect_SRF To SRF
Await_SRF_Disconnection_
Fail
Int_SRF_Released
From SRF
Result:=fail
Page 25CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the M SC to handlea Connec t To Resource operat ion
Procedure CAMEL_MT_CTR 4(4 )
Signals to/from the left areto/from the originating exchange;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Await_SRF_InitialisationWa it_For_Connect_Ack
Release
Call_Active
Int_DP_T_Disconnec t/*legID*/
Int_DP_T_Abandon
W ait_For_Disconnect_Forward_Connection
Wa it_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF To SRF Int_Disconnect_SRF To SRF
Await_SRF_Disc onnection_
Active
Await_SRF_Disconnection_
Fail
Int_SRF_Released
From SRFInt_SRF_Released
From SRF
Result:=pass
Result :=fail
True False
Page 26CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_MT _ETC 1(3 )
Signals to/from the left are to/fromthe BSS;signals to/from the r ight areto/from the gsmSSF;if not otherwise stated.
InitialAddress
To process CAMEL_A ssisting_MSC or SRF.
Send_ACM_If_Required
Procedure definedin GSM 03.18
W ait_For_As sisting_ACM
Release
Int_DP_T_Abandon
ReleaseTo processAssisting_MSCor SRF
Result:=fail
ReleaseFrom destinationexchange
Int_ETC_Failed
Result:=pass
Page 27CR to GSM 03.78 v6.1.0 September 1998
P rocedu re in the M SC t o h an dle a tem poraryc on nec tion
Procedure CAMEL_MT_ETC 1(3)
Sig na ls to /from t he lef t a re to /fromth e BS S;sign a ls to /from the r ig h t areto /from th e gs m SSF;if n ot oth e rwise state d.
In i tia lAddress
To process CAMEL_A ssist ing_MSC or S RF.
S en d_ ACM_If_Req uire d
P roced ure de fine din GSM 03. 18
W ait_For_A ssisting_ACM
Release
Call_Act ive
Int_DP_T_Disconnect/*le gID */
W ai t_For_Disc on nec t_Forward_Connec tion
Int_Disconnect_Forward_Connec tion
ReleaseTo processCAMEL_As sistin g_MS C or SRF
R e sult :=pass
In t_D P _T_Ab a ndo n
Releas eTo p rocessCAMEL_ Assist ing _MSC or SRF
R e sult:=fa il
ReleaseFrom d est in atio nexcha ng e
Int_ E TC _Faile d
Result :=pass
Tru e False
Page 28CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_MT _ETC 3(3 )
Signals to/from the left are to/fromthe BSS ;signals to/from the r ight areto/from the gsmSSF;if not otherwise stated.Temporary_Connection_Established
Wa it_For_Assisting_Answer
Release
Int_DP_T_Abandon
ReleaseTo processAssisting_SSFor SRF
Result :=fail
ReleaseFrom destinationexchange
Int_TC_Released
Result:=pass
Int_Disconnect_Forward_Connection
Int_TC_Released
ReleaseTo destinationexchange
Result :=pass
Page 29CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_MT _ETC 3(3 )
Signals to/from the left are to/fromthe BSS ;signals to/from the r ight areto/from the gsmSSF;if not otherwise stated.Temporary_Connection_Established
Wa it_For_Assisting_Answer
Release
call_Active
Int_DP_T_Disconnec t/*legID*/
W ait_For_Disconnect_Forward_Connection
Int_DP_T_Abandon
ReleaseTo processCAMEL_A ssisting_MSC or SRF
Result:=fail
ReleaseFrom destinationexchange
Int_TC_Released
Result:=pass
Int_Disconnect_Forward_Connection
Int_TC_Released
ReleaseTo destinationexchange
Result:=pass
T rue
false
Page 30CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the MSC to handle a forwarded call
Procedure CAMEL_CF_MSC_INIT 1(4 )
Signals to/from the left are to/fromthe process MT_GM SC;signals to/from the right are to/fromthe process gsmSSF if nototherwise stated.
O-CSIstored,
Result :=pass
Int_Invoke gsmSSF(O-CSI)
W ait_For__gsmSSF__Invoked
Int_Error
Release
Result:=fail
Int_gsmSSF Invoked
Int_DP__Collec ted__Info
DP__Collec ted_
_Info
CF Cancelled
Int_O_Except ion
Result :=cancelled
No
Yes
Page 31CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the MSC to handle a forwarded call
Procedure CAMEL_CF_MSC_INIT 1(4 )
Signals to/from the left are to/fromthe process MT_GM SC;signals to/from the right are to/fromthe process gsmSSF if nototherwise stated.
O-CSIstored,
Result :=pass
Int_Invoke gsmSSF(O-CSI)
W ait_For__gsmSSF__Invoked
Int_Error
Release
Result:=fail
Int_gsmSSF Invoked
Int_DP__Collec ted__Info
DP__Collec ted_
_Info
CF Cancelled
Int_O_Except ion
Result :=cancelled
Call_A ctive :=False
No
Yes
Page 32CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the M SC to handlea fowarded call
Procedure CAMEL_CF_MSC_ANSWER 1(1 )
Signals to/from the leftare to/from the processMT_GMSC; signals to/from the rightare to/from the terminatingexchange.
gsmSS Fexists?
result=pass Int_O_Answer to the gsmSSF
DP_O_Answer
Int_Releasefrom thegsmSSF
Release
Release
Result=:fail
Int_continuefrom thegsmSSF
Result:=pass
Release
CAMEL_OCH_MSCDIS C_1
Result=CAMEL_handling?
Release
Result:=fail
Release
CAMEL_OCH_MSCDIS C_2
Result=reconnect?
Result=CAMEL_handling?
Release
Result:=reconnec t
no
yes
No
Yes
No
No
Yes
Page 33CR to GSM 03.78 v6.1.0 September 1998
P rocedure in the M SC to handlea fowarded call
Procedure CAMEL_CF_MSC_ANSWER 1(1 )
Signals to/from the leftare to/from the processMT_GMSC; signals to/from the rightare to/from the terminatingexchange.
gsmSS Fexists?
result=pass Int_O_Answer to the gsmSSF
DP_O_Answer
Int_Releasefrom thegsmSSF
Release
Release
Result=:fail
Int_continuefrom thegsmSSF
Result:=pass
Release
CAMEL_OCH_MSCDIS C_1
Result=CAMEL_handling?
Release
Result:=fail
Release
CAMEL_OCH_MSCDIS C_2
Result=reconnect?
Result=CAMEL_handling?
Release
Result:=reconnec t
Call_Active :=True
Call_A ctive :=False
no
yes
No
Yes
No
No
Yes
Page 34CR to GSM 03.78 v6.1.0 September 1998
Procedure in the GMSC to handle a Connect To Resourceoperation
Procedure CAMEL_CF_CTR 2(4 )
Signals to/from the left areto/from the process MT_GMSC;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.Relay
Int_Disconnec t_Forward_Connection
Int_Disconnec t_SRF
To SRF
Await_SRF_Disconnection_
Continue
Int_SRF_Released
From SRF
Int_SRF_Released
Result:=pass
Release
Int_DP_O_Disconnec t/* legID */
Wa it_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Fail
Page 35CR to GSM 03.78 v6.1.0 September 1998
Procedure in the GMSC to handle a Connect To Resourceoperation
Procedure CAMEL_CF_CTR 2(4 )
Signals to/from the left areto/from the process MT_GMSC;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.Relay
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Continue
Int_SRF_Released
From SRF
Int_SRF_Released
Result:=pass
Release
Call_Active
Int_DP_O_Disconnect/* legID */
W ait_For_Disc onnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Active
Int_SRF_Released
Result :=P ass
Int_DP_O_Abandon/* legID */
Wa it_For_Disconnect_Forward_Connection
Int_Disconnect_Forward_Connection
Int_Disconnect_SRF
To SRF
Await_SRF_Disconnection_
Fail
True False
Page 36CR to GSM 03.78 v6.1.0 September 1998
Procedure in the GMSC to handle a Connect To Resourceoperation
Procedure CAMEL_CF_CTR 4(4 )
Signals to/from the left areto/from the process MT_GMSC;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Await_SRF_InitialisationWa it_For_Connect_Ack
Relase
Int_DP_O_Abandon
Int_Disconnect_SRFTo SRF
Await_SRF_Disconnection_
Fail
Int_SRF_Released
From SRF
Result:=fail
Page 37CR to GSM 03.78 v6.1.0 September 1998
Procedure in the GMSC to handle a Connect To Resourceoperation
Procedure CAMEL_CF_CTR 4(4 )
Signals to/from the left areto/from the process MT_GMSC;signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
Await_SRF_InitialisationWa it_For_Connect_Ack
Release
Call_Active
Int_DP_O_Disconnec t/*legID*/
Int_DP_O_Abandon
Int_Disconnect_SRF To SRF Int_Disc onnect_SRF To SRF
Await_SRF_Disc onnection_
Active
Await_SRF_Disconnection_
Fail
Int_SRF_Released
From SRFInt_SRF_Released
From SRF
Result:=pass
Res ult :=fail
True False
Page 38CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_CF_ETC 1(3 )
Signals to/from the left are to/fromthe BSS;signals to/from the r ight areto/from the gsmSSF;if not otherwise stated.
InitialAddress
To process CAMEL_Assisting_MSC or SRF
Send_ACM_If_Required
Procedure definedin GSM 03.18
W ait_For_Assisting_ACM
Release
Int_DP_O_Abandon
ReleaseTo processCAMEL_Assist ing_MSC aor SRF
Result:=fail
ReleaseFrom destinationexchange
Int_ETC_Failed
Result:=pass
Page 39CR to GSM 03.78 v6.1.0 September 1998
P rocedu re in the M SC t o h an dle a tem poraryc on nec tion
Procedure CAMEL_CF_ETC 1(3)
Sig na ls to /from t he lef t a re to /fromth e BS S;sign a ls to /from the r ig h t areto /from th e gs m SSF;if n ot oth e rwise state d.
Initia lAddress
To process CAMEL_A ssist ing_MSC or SRF
S en d_ ACM_If_Req uire d
P roced ure de fine din G S M 03. 18
W ait_For_A ssisting_ACM
Release
Call_Act ive
Int _DP_O_Disc onn ec t/*le gID */
W ai t_Fo r_Dis con nec t_Forward_Connec tion
Int _Disconnect_Forward_Connec tion
ReleaseTo p roc essCAMEL_A ssistin g_MS C or SRF
R esult :=pass
In t_ DP _O _Ab a ndo n
R e leaseTo p rocessCAMEL_ Assist ing _MSC or SRF
R e sult:=fa il
ReleaseFro m d est in atio nexcha ng e
Int_ E TC _Faile d
Result :=pass
Tru e False
Page 40CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_CF_ETC 3(3 )
Signals to/from the left are to/fromthe BSS;signals to/from the r ight areto/from the gsmSSF;if not otherwise stated.
Temporary_Connection_EstablishedWa it_For_Assisting_Answer
Release
Int_DP_O_Abandon
ReleaseTo processAssisting_SSFor SRF
Result :=fail
ReleaseFrom destinationexchange
Int_TC_Released
Result:=pass
Int_Disconnect_Forward_Connection
Int_TC_Released
ReleaseTo destinationexchange
Result:=pass
Page 41CR to GSM 03.78 v6.1.0 September 1998
Procedure in the M SC to handle a temporaryconnection
Procedure CAMEL_CF_ETC 3(3 )
Signals to/from the left are to/fromthe BSS;signals to/from the r ight areto/from the gsmSSF;if not otherwise stated.
Temporary_Connection_EstablishedWa it_For_Assisting_Answer
Release
call_Active
Int_DP_O_Disconnec t/*legID*/
W ait_For_Disconnect_Forward_Connection
Int_DP_O_Abandon
ReleaseTo processCAMEL_A ssisting_MSC or SRF
Result:=fail
ReleaseFrom destinationexchange
Int_TC_Released
Result:=pass
Int_Disconnect_Forward_Connection
Int_TC_Released
ReleaseTo destinationexchange
Result:=pass
T rue
false
Page 42CR to GSM 03.78 v6.1.0 September 1998
Invocation of gsmSSF in MO,MT or CF call cas e.
Process gsmSSF 7(20)
Signals to/from the left are to/from theprocesses OCH_MSC, MT_GMSC and MT_CF_MSC;signals to/from the r ight areto/from the gsmSCF.
Wa iting_for_Instructions
Int_DP_O__Disconnect/* legID */
DP armed forleg ID?
DP armedas EDP-R?
CAP_Event__Report_BCSM(Notify & Continue)
Reload andrestart Tssf
Handle_ACR
Handle_CIR
Disarm thisDP
The DP is only disarmedfor the leg for whic h theevent was received.
Wa iting_for_Instructions
Handle_ACR
Handle_CIR
CAP_E vent__Report_BCSM(Interrupted)
Set Tssf to defaultnon user interaction
timer value andrestart Tssf
Set Outstanding__Requests =Outstanding_
_Requests + 1
Handle_ACR
Handle_CIR
Int_DP_T__Disconnec t/* legID */
Yes
No
Yes
No
Page 43CR to GSM 03.78 v6.1.0 September 1998
Invocation of gsmSSF in MO,MT or CF call cas e.
Process gsmSSF 7(20)
Signals to/from the left are to/from theprocesses OCH_MSC, MT_GMSC and MT_CF_MSC;signals to/from the r ight areto/from the gsmSCF.
Wa iting_for_Instruc tions,W aiting_for_E nd_Of_Temporary_Connection,W aiting_for_E nd_Of_User_Interaction,A wait_Temporary_Connect ion_Establishment
Int_DP_O__Disconnect/* legID */
Int_DP_T__Disconnec t/* legID */
DP armed forleg ID?
DP armedas EDP-R?
CAP_Event__Report_BCSM(Notify & Continue)
Handle_ACR
Handle_ACRReload andrestart Tssf
Handle_CIR
Handle_CIR Handle_ACRCAP_E vent__Report_BCSM(Interrupted)
Handle_CIRSet Tssf to default
non user interactiontimer value and
restart TssfSet Outstanding_
_Requests =Outstanding_
_Requests + 1
Disarm thisDP
The DP is only disarmedfor the leg for whic h theevent was received.
Wa iting_for_Instructions
Yes
No
No
Yes
CHANGE REQUEST No.A029rev1
Technical Specification GSM 03.78 version 6.1.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic") [x]
Status at SMG [#27]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [R97] Work item: CAMEL Phase 2
Other phase(s) affected: [ ] If yes, linked CR(s): CR 03.78-A033
Proposed change affects: SIM [ ] ME [ ] Network [ ]
Source: SMG3 Tdoc SMG3 98C482 Date: 22-7-98
Subject: Corrections to AnyTimeInterrogation
Category: F - Correction [ x]
A - Corresponds to a Phase 2 correction [ ]
B - Addition of Feature [ ]
C - Functional modification of Feature [ ]
D - Editorial modification [ ]
Reason for change:
Modification of process CAMEL_HLR_INIT,
Addition of the IE SCF Address in the operation AnyTimeInterrogation.
Addition of the case 'NotProvidedFromVLR' in the operations AnyTimeInterrogation ack, SendRouteingInfo ack.
Sections affected, and additional explanation of details of change (if needed):
8.3.2, 9
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects(possibly):
MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications []
Attached CRs?:
Cross Phase Compatibility:
Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ]
CR to 09.90 attached:
Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ]
CR to 09.91 attached:
Phase 2(+) SIM in Phase 1 ME [ ]
CR to 09.91 attached:
Other comments:
Page 3CR on GSM 03.78 v6.1.0 July 1998
8.3.2 Retrieval of routeing information in the HLR
The functional behaviour of the HLR is specified in GSM 03.18 [3]. The procedures specific to CAMEL arespecified in this subclause :
- CAMEL_HLR_INIT,
- CAMEL_CSI_Check_HLR,
- CAMEL_O_CSI_CHECK_HLR,
- CAMEL_T_CSI_CHECK_HLR,
The procedure Provide_Subscriber_Info_HLR is specified in subclause 8.8.
T his proced ure is calle d inS RI _HLR (in GS M 0 3. 18 )
Procedure CAMEL_HLR_INIT 1(1 )
CAMELsubscrib e r
Triggerin g crite r iasto re d?
Triggerin g crite r iafu lf i lled?
G MS C supports CAMEL
p hase 2
G MS C supports CAMEL
p hase 1
C AME L p h ase 1s uff icien t?
Result:=pass
De fa ulth an dling ?
Result:=f ail
Normal call h an dling acc ording
to G S M 03. 18
Result:=p ass
Network specifich an dling
The n et wo rk specific handlingshal l include the result of th e proce du reCAMEL_HLR_INIT (fail, pass)
Yes
Yes
Yes
No
Yes
Y es
No
O DBContinu e
Ne tworkspecific
No
Y es
No
No
No
Page 4CR on GSM 03.78 v6.1.0 July 1998
T his proced ure is calle d inS RI _HLR (in GS M 0 3. 18 )
Procedure CAMEL_HLR_INIT 1(1 )
CAMELsubscrib e r
Triggerin g crite r iasto re d?
Triggerin g crite r iafu lf i lled?
G MS C supports CAMEL
p hase 2
G MS C supports CAMEL
p hase 1
C AME L p h ase 1s uff icien t?
Result:=pass
De fa ulth an dling ?
Result:=f ail
Normal call h an dling acc ording
to G S M 03. 18
Result:=p ass
Network specifich an dling
The n et wo rk specific handlingshal l include the result of th e proce du reCAMEL_HLR_INIT (fail, pass)
Set negativeresponse: Cal l Barred
Yes
Yes
Yes
No
Yes
Y es
No
O DBContinu e
Ne tworkspecific
No
Y es
No
No
No
Figure 1Error! Unknown switch argument.: Procedure CAMEL_HLR_INIT (sheet 1)
Page 5CR on GSM 03.78 v6.1.0 July 1998
*** Next modified section ***
9.7.1 Any Time Interrogation Request
9.7.1.1 Description
This IF is used to request information (subscriber state and location) from the HLR at any time.
9.7.1.2 Information Elements
The following information elements are required:
Information element name Required Description
gsmSCF Address M This IE indicates the address of the interrogating gsmSCF.
Requested Info M This IE indicates the type of subscriber information being requested:
- subscriber location
- subscriber state
Subscriber Identity M This IE identifies the subscriber for which the information isrequested. The identity can be one of:
- IMSI
- MSISDN
M Mandatory (The IE shall always be sent)
*** Next modified section ***
9.8.1 Any Time Interrogation ack
9.8.1.1 Description
This IF is used by the HLR to provide the requested information to the gsmSCF.
9.8.1.2 Information Elements
The following information elements are required:
Information element name Required Description
Location Information C This IE indicates the location of the served subscriber.
Subscriber State C This IE indicates the status of the MS. The possible values of theIEstates are:
- CAMELBusy: The VLR has indicated that Tthe MS is engaged on atransaction for a mobile originating or terminated circuit-switchedcall.
- NetworkDeterminedNotReachable: The VLR has indicated thatTthe network can determine from its internal data that the MS is notreachable.
Page 6CR on GSM 03.78 v6.1.0 July 1998
- AssumedIdle: The VLR has indicated that Tthe state of the MS isneither "CAMELBusy" nor "NetworkDeterminedNotReachable".
- NotProvidedFromVLR: The VLR did not provide any informationon subscriber state even though it was requested.
C Conditional (The IE shall be sent, if requested and available)
Location Information contains the following information:
Information element name Required Description
Location Number C See GSM 03.18 [3].
CellIdOrLAI C See GSM 03.18 [3].
Geographical Information C See GSM 03.18 [3].
Age Of Location Information C See GSM 03.18 [3].
VLR number C See GSM 03.18 [3].
C Conditional (The IE shall be sent, if available)
*** Next modified section ***
9.11 HLR to GMSC information flows
9.11.1 Send Routeing Info ack
9.11.1.1 Description
This IF is specified in GSM 03.18 [3] and is used by the HLR to transfer the requested routeing information to theVLR.
9.11.1.2 Information Elements
Send Routeing Info ack contains the following CAMEL specific IE:
Information element name Required Description
Location Information C This IE indicates the location of the served subscriber.
O-CSI C This IE identifies the subscriber as having originating CAMELservices.
Shall be sent if O-CSI is active, and CFU or CFNRc has been invoked,or if both O-CSI and T-CSI are active.
Subscriber State C This IE indicates the status of the MS. The possible values of theIEstates are:
- CAMELBusy: The VLR has indicated that Tthe MS is engaged on atransaction for a mobile originating or terminated circuit-switchedcall.
- NetworkDeterminedNotReachable: The VLR has indicated thatTthe network can determine from its internal data that the MS is notreachable.
- AssumedIdle: The VLR has indicated that Tthe state of the MS isneither "CAMELBusy" nor "NetworkDeterminedNotReachable".
- NotProvidedFromVLR: The VLR did not provide any information
Page 7CR on GSM 03.78 v6.1.0 July 1998
on subscriber state even though it was requested.
T-CSI C This IE identifies the subscriber as having terminating CAMELservices.
Shall be sent if T-CSI is active and no Suppress T-CSI indicator ispresent in the SRI.
Basic Service Code C This IE indicates the type of basic service i.e., teleservice or bearerservice.
CUG Subscription Flag C This IE indicates if the called party has a CUG subscription. It shallonly be sent if the T-CSI is active and included in the Send RoutingInformation ack.
C Conditional (The IE shall be sent, if available)
C’ Conditional (The IE shall be sent, if available and indicated by Subscriber Information in Send RouteingInformation ack indicator.)
Location Information contains the following information:
Information element name Required Description
Location Number C’ See GSM 03.18 [3].
CellIdOrLAI C’ See GSM 03.18 [3].
Geographical Information C’ See GSM 03.18 [3].
Age Of Location Information C’ See GSM 03.18 [3].
VLR number C See GSM 03.18 [3].
C Conditional (The IE shall be sent, if available)
C’ Conditional (The IE shall be sent, if available and indicated by Subscriber Information in Send RouteingInformation ack indicator.)
O-CSI is defined in section 9.9.2.
T-CSI contains the following information:
Information element name Required Description
gsmSCF Address M This IE is described in section 6.1.
Service Key M This IE is described in section 6.1.
Default Call Handling M This IE is described in section 6.1.
TDP List M This IE is described in section 6.1.
CAMEL Capability Handling C This IE is described in section 6.1. If this IE is absent, this indicatesthat CAMEL phase 1 is asked.
M Mandatory
C Conditional
CHANGE REQUEST No. A034 rev 2
Technical Specification GSM 03.78 version 6.1.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic") [ x ]
Status at SMG [#27]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [Release 97] Work item: CAMEL Phase 2
Other phase(s) affected: [ ] If yes, linked CR(s): 98c441
Proposed change affects: SIM [ ] ME [ ] Network [ ]
Source: SMG3 Tdoc SMG3 98C493 Date: September 1998
Subject: Interworking CAMEL with the General Bearer Service
Category: F - Correction [X]
A - Corresponds to a Phase 2 correction [ ]
B - Addition of Feature [ ]
C - Functional modification of Feature [..]
D - Editorial modification [ ]
Reason for change:
The General Bearer service defined by SMG4 has to be taken into account in 0378
Sections affected, and additional explanation of details of change (if needed):
Paragraf 5.1.2.1 ‘Criteria for a terminating call’
Paragraf 5.1.2.2 ‘Criteria for an originating call or a forwarding call’
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ]
Attached CRs?:
Cross Phase Compatibility:
Change affects operation of:
Change affects operation of:
Other comments:
none
Page 2GSM 03.78 Version 6.1.0
ABSTRACT
The aim of this Change Request is to introduce in 0378 the notion of General Bearer Service as
defined by SMG4.
INTRODUCTION
SMG4 introduce the General Bearer Service (ref GSM 02.01 version 5.3.0) to simplify the
basic service
subscription in the HLR. Single service defined independently of the fixed network user rate are
called General Bearer Service.
A subscription to a general bearer service comprises the subscription to all individual
bearer services.
Note : General Bearer service is not applicable to Teleservice.
Example :
Set Up Subscription Check SS handling
BS21 BS21, BS20, BS Group 2x or BS Group All BS Group 2x
BS34 BS34, BS30, BSGroup 3x or BS Group All BS Group 3x
In this example BS20, BS30, BS21,BS34 are Basic (Bearer) Service code
BS21, BS24 are individual Basic (Bearer) Service
BS20 and BS30 are General Bearer service
BS2x and BS3x are Basic(Bearer) Service Group
PROPOSAL
It is proposed to update 5.1.2.1 and 5.1.2.2 :
5.1.2.1 Criteria for a terminating call
The criteria for a terminating call are checked in the HLR. The HLR may store a list of up to 5 basic service codes,each of which may represent an individual basic service or a basic service group. This list is a triggering list. Thebasic service criterion is met if the basic service for the call matches a stored individual basic service code, or is amember of the group defined by a stored basic service group code. For the purpose of this paragraph a general bearerservice is a member of the corresponding bearer service group..
The HLR shall include the CAMEL subscription information in the subscriber data sent to the GMSC only if thetriggering criteria are met.
5.1.2.2 Criteria for an originating call or a forwarded call
The criteria for an originating or forwarded call are checked in the originating or forwarding MSC.
NOTE: In the case of a forwarded call, the HLR may decide not to include the CAMEL subscriptioninformation in the subscriber data sent to the GMSC if the triggering criteria are not met.
The following criteria are applicable for DP2 :
- Destination number triggering criterion: The HLR may store a list of up to 10 destination numbers and/or upto 3 number lengths. There is no restriction on the nature of address or the numbering plan indicator. Thiscriterion may be defined to be either "enabling" or "inhibiting".
- Basic service triggering criterion: The HLR may store a list of up to 5 basic service codes, each of which mayrepresent an individual basic service or a basic service group. This list is a triggering list.
- Forwarding triggering criterion: The HLR may store an indicator that triggering shall occur only for a callwhich has been subject to GSM or CAMEL call forwarding. This criterion may be defined to be either"enabling" or "inhibiting".
One or more DP criteria may be applicable. All applicable triggering criteria must be satisfied before the dialogue isestablished with the gsmSCF.
If the destination number triggering criterion is enabling, then the gsmSSF may establish a dialogue with the gsmSCFif:
- the destination number matches one of the destination number strings defined in the list, or- the length of the destination number matches one of the destination number lengths defined in the list.
In this test the destination number matches one of the destination number strings in the list if:- the destination number is at least as long as the destination number string in the list, and- all the digits in the destination number string in the list match the leading digits of the destination
number.If the destination number triggering criterion is inhibiting, then the gsmSSF may establish a dialogue with thegsmSCF if:
- the destination number does not match any of the destination number strings defined in the list, and- the length of the destination number does not match any of the destination number lengths defined in the list.
In this test the destination number matches one of the destination number strings in the list if:- the two numbers are the same length, and- the digits in the destination number match the digits of the destination number string in the list.
The basic service triggering criterion is met if the basic service for the call matches a stored individual basic servicecode, or is a member of the group defined by a stored basic service group code. For the purpose of this paragraph ageneral bearer service is a member of the corresponding bearer service group..
If the forwarding triggering criterion is enabling, then the gsmSSF may establish a dialogue with the gsmSCF only ifthe call has been subject to CAMEL or GSM call forwarding. If the forwarding triggering criterion is inhibiting, thenthe gsmSSF may establish a dialogue with the gsmSCF only if the call has not been subject to CAMEL or GSM callforwarding.
CHANGE REQUEST No.A037r1
Technical Specification GSM 03.78 version 6.1.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic") [ x ]
Status at SMG [#27 ]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [R97] Work item: CAMEL Phase 2
Other phase(s) affected: [ ] If yes, linked CR(s):
Proposed change affects: SIM [ ] ME [ ] Network [ ]
Source: SMG3 Tdoc SMG3 98C571 Date: September 1998
Subject: Removal of O_Not_Reachable and T_Not_Reachable detection points.
Category: F - Correction [ ]
A - Corresponds to a Phase 2 correction [ ]
B - Addition of Feature [ ]
C - Functional modification of Feature [x]
D - Editorial modification [ ]
Reason for change:
O_Not_Reachable and T_Not_Reachable detection points are replaced by DP O_Busy and T_Busy in order to alignCAMEL phase 2 and CS2 BCSMs.
Sections affected, and additional explanation of details of change (if needed):
7.2, 7.3, 8.
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects(possibly):
MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications []
Attached CRs?:
Cross Phase Compatibility:
Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ]
CR to 09.90 attached:
Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ]
CR to 09.91 attached:
Phase 2(+) SIM in Phase 1 ME [ ]
CR to 09.91 attached:
Other comments:
Page 3CR on GSM 03.78 v6.1.0 July 1998
7.2.1 Description of O-BCSM
The O-BCSM is used to describe the actions in an MSC during originating (MSC) or forwarded (MSC or GMSC)calls.
When encountering a DP the O-BCSM processing is suspended at the DP and the MSC/GMSC indicates this to thegsmSSF which determines what action, if any, shall be taken in case the DP is armed.
Page 4CR on GSM 03.78 v6.1.0 July 1998
O_Null & Authorise_Origination_Attempt_Collect_Info
DP2
O_Exception
DP9
DP7
Collected_Info
O_Answer
Basic Call transition
Transition beyond Basic Call
DP4
DP5
DP6
O_Disconnect
O_Active
Route_Select_Failure
O_Busy
O_No_Answer
DP10
O_Abandon
& Alerting
Analyse, Routing
DP50O_Not_Reachable
O_Null & Authorise_Origination_Attempt_Collect_Info
DP2
O_Exception
DP9
DP7
Collected_Info
O_Answer
Basic Call transition
Transition beyond Basic Call
DP4
DP5
DP6
O_Disconnect
O_Active
Route_Select_Failure
O_Busy
O_No_Answer
DP10
O_Abandon
& Alerting
Analyse, Routing
Figure 1: Originating BCSM for CAMEL
The following table defines the different DPs which apply to mobile originating and forwarded calls.
Page 5CR on GSM 03.78 v6.1.0 July 1998
Table 1: Description of O-BCSM DPs in the MSC
CAMEL Detection Point: DP Type Description:
DP2 Collected_Info TDP-R Indication that the O-CSI is analysed.
DP 4 Route_Select_Failure EDP-N, EDP-R Indication that the call establishment failed
DP 5 O_Busy EDP-N, EDP-R Indication that :
- a busy indication is received from the terminating party
- a not reachable event is determined upon a cause IEin the ISUP release message.
DP6 O_No_Answer EDP-N, EDP-R Indication that an application timer associated with theO_No_Answer DP expires
DP7 O_Answer EDP-N, EDP-R Indication that the call is accepted and answered by theterminating party.
DP9 O_Disconnect EDP-N, EDP-R A disconnect indication is received from the originatingparty or from the terminating party.
DP 10 O_Abandon EDP-N Indication that a disconnect indication is received fromthe originating party during the call establishmentprocedure
DP 50 O_Not_Reachable EDP-N, EDP-R Not reachable event can be determined upon a cause IEin the ISUP release message.
NOTE : the DPs 2, 4, 5, 6, 7, 9, 10 are defined in ITU-T Q.1214 ([6]).
7.2.1.1 Description of the call model (PICs)
This subclause describes the call model for originating and forwarded calls. For each PIC a description can be foundof the entry events, functions and exit events.
It should be noted that although the names used for PICs match those used in ITU-T Q.1214 [6] the specificdescriptions differ.
7.2.1.1.1 O_Null & Authorise_Origination_Attempt_Collect_Info
Entry events:
- Disconnection and clearing of a previous call (DP9 - O_Disconnect) or default handling of exceptions bygsmSSF/(G)MSC completed.
- Abandon event is reported from Analyse, Routing and Alerting PIC.
- Exception event is reported.
Functions:
- Interface is idled.
- Originating call: SETUP message containing the dialled number is received from MS.
- Originating call: The supplementary service "barring of all outgoing calls" is checked and invoked ifnecessary.
- Originating call: The ODB category "barring of all outgoing calls" is checked and ODB is invoked ifnecessary.
NOTE : the ODB category "barring of all outgoing calls when roaming" causes the HLR to send the category"barring of all outgoing call" if the VLR is not in the HPLMN.
- Originating call: CUG checks done in the originating MSC/VLR are performed.
Page 6CR on GSM 03.78 v6.1.0 July 1998
- Information being analysed e.g., O-CSI is analysed.
Exit events:
- Originating CSI is analysed.
- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions during thePIC processing, the exception event is not visible because there is no corresponding DP. Example exceptioncondition : Calling party abandons call.
7.1.1.1.2 Analyse, Routing & Alerting
Entry events:
- Originating CSI is analysed. (DP2 - Collected Info).
- Busy event, Route Select Failure event, Not Reachable event or No Answer event is reported from AnalyseRouting and Alerting PIC.
- Disconnect event is reported from O_Active PIC.
Functions:
- Information being analysed and/or translated according to dialling plan to determine routeing address.
- Routeing address being interpreted.
- Originating call: Outgoing barring services and ODB categories not already applied are checked and invokedif necessary.
- Call is being processed by the terminating half BCSM. Continued processing of call setup (e.g., ringing) istaking place. Waiting for indication from terminating half BCSM that the call has been answered byterminating party.
Exit events:
- Indication from the terminating half BCSM that the call is accepted and answered by terminating party. (DP7- O_Answer)
- An exception condition is encountered - this leads to the O_Exception PIC.
- Calling party abandons the call- this leads to the O_Abandon DP.
- A busy indication is received from the terminating party - this leads to the O_Busy DP.
- A not reachable indication is received from the terminating party - this leads to the O_BusyNot_ReachableDP.
- Attempt to select the route for the call fails - this leads to the Route_Select_Failure DP.
- If the no reply timer expires and DP O_No_Answer is armed - this leads to the O_No_Answer DP.
7.2.1.1.3 O_Active
Entry events:
- Indication from the terminating half BCSM that the call is accepted and answered by the terminating party.(DP7 - O_Answer)
Functions:
- Connection established between originating party and terminating party. Call supervision is provided.
- Call release is awaited.
Exit events:
Page 7CR on GSM 03.78 v6.1.0 July 1998
- A disconnection indication is received from the originating party, or received from the terminating party viathe terminating half BCSM. (DP9 - O_Disconnect)
- An exception condition is encountered.
7.2.1.1.4 O_Exception
Entry events:
- An exception condition is encountered. In addition to specific examples listed above, exception eventsinclude any type of failure, which means that the normal exit events for a PIC can not be met.
Functions:
- Default handling of the exception condition is being provided. This includes general actions necessary toensure that no resources remain inappropriately allocated such as:
- If any relationship exists between the gsmSSF and the gsmSCF send an error information flow closing therelationships and indicating that any outstanding call handling instructions will not run to completion
- The (G)MSC/gsmSSF should make use of vendor-specific procedures to ensure release of resourceswithin the (G)MSC/gsmSSF, so that line, trunk and other resources are made available for new calls.
Exit events:
- Default handling of the exception condition by gsmSSF/(G)MSC completed.
7.3 Terminating Basic Call State Model (T-BCSM)
7.3.1 Description of T-BCSM
The T-BCSM is used to describe the actions in a GMSC during terminating calls.
When encountering a DP the T-BCSM processing is suspended at the DP and the GMSC indicates this to thegsmSSF which determines what action, if any, shall be taken in case the DP is armed.
Page 8CR on GSM 03.78 v6.1.0 July 1998
T_Null
Terminating Call Handling
DP12
T_Exception
DP17 T_Active
DP15
Terminating_Attempt_Authorised
T_Answer
Basic Call transition
Transition beyond Basic Call
DP51
DP13
DP14
T_Not_Reachable
T_Busy
T_No_Answer
DP18
T_Abandon
T_Disconnect
T_Null
Terminating Call Handling
DP12
T_Exception
DP17 T_Active
DP15
Terminating_Attempt_Authorised
T_Answer
Basic Call transition
Transition beyond Basic Call
DP13
DP14
T_Busy
T_No_Answer
DP18
T_Abandon
T_Disconnect
Figure 2: T-BCSM in the GMSC
In the following table the different DPs (in the T-BCSM) are described.
Page 9CR on GSM 03.78 v6.1.0 July 1998
Table 2: Description of T-BCSM DPs in the GMSC
CAMEL Detection Point: DP Type Description:
DP12Terminating_Attempt_Authorised
TDP-R Indication that the T-CSI is analysed.
DP 13 T_Busy EDP-N, EDP-R Indication that
-a busy indication is received from the destinationexchange.
- Not reachable or call establishment failureevent is determined from the HLR response orupon a cause IE in the ISUP release message.
DP 14 T_No_Answer EDP-N, EDP-R Indication that an application timer associatedwith the T_No_Answer DP expires
DP15 T_Answer EDP-N, EDP-R Call is accepted and answered by terminatingparty
DP17 T_Disconnect EDP-N, EDP-R A disconnect indication is received from theterminating party or from the originating party.
DP 18 T_Abandon EDP-N A disconnect indication is received from theoriginating party during the call establishmentprocedure
DP 51 T_Not_Reachable EDP-N, EDP-R Not reachable or call establishment failure eventcan be determined from the HLR or upon acause IE in the ISUP release message.
NOTE : the DPs 12, 13, 14, 15, 17, 18 are defined in ITU-T Q.1214 ([6]).
7.3.1.1 Description of the call model (PICs)
This subclause describes the call model for terminating calls in the GMSC. For each PIC a description can be foundof the entry events, functions, information available and exit events.
It should be noted that although the names used for PICs match those used in ITU-T Q.1214 [6] the specificdescriptions differ.
7.3.1.1.1 T_Null
Entry events:
- Disconnection and clearing of a previous call (DP 17) or default handling of exceptions by gsmSSF/GMSCcompleted.
- Abandon event is reported from Terminating Call Handling PIC ;
- Exception event is reported.
Functions:
- Interface is idled.
- ISUP_IAM is received, the appropriate information is analysed.
- Send_Routeing_Info information flow is sent to HLR.
- The supplementary services "barring of all incoming calls" and "barring of incoming calls when roaming" arechecked and invoked if necessary.
- The ODB categories "barring of all incoming calls" and "barring of incoming calls when roaming" arechecked and ODB is invoked if necessary.
- The supplementary service "CUG" is checked and invoked if necessary.
Page 10CR on GSM 03.78 v6.1.0 July 1998
- T-CSI is received and analysed.
Exit events:
- Response is received from HLR and terminating CSI (if available) is analysed.
- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions during thePIC processing, the exception event is not visible because there is no corresponding DP.
Example exception condition is:
- Calling party abandons call.
7.3.1.1.2 Terminating Call Handling
Entry events:
- Response is received from HLR and terminating CSI (if available) is analysed. (DP 12Terminating_Attempt_Authorised),
- Busy event, Not Reachable event or No Answer event is reported from Terminating Call Handling PIC,
- Disconnect event is reported from T_Active PIC.
- The terminating party is not reachable.
NOTE : the HLR may use MAP signalling to indicate to the GMSC before the call is extended to thedestination VMSC that the terminating party is not reachable, or the destination VMSC may usetelephony signalling to indicate to the GMSC after the call has been extended to the destination VMSCthat the terminating party is not reachable.
Functions:
- The response from HLR is analysed.
- Routeing address and call type being interpreted. The next route is being selected.
- The terminating party is being alerted. Waiting for the call to be answered by terminating party.
- The GSM supplementary service call forwarding is invoked if necessary.
Exit events:
- Call is accepted and answered by terminating party.
- An exception condition is encountered - this leads to the T_Exception PIC. Example exception conditions:the call setup to the MSC/GMSC was not successful.
- Calling party abandons the call - this leads to the T_Abandon DP.
- A busy indication is received from the destination exchange - this leads to the T_Busy DP.
- Not reachable event detected or failure of attempt to select the route for the terminating leg - this leads to theT_Busy DP.
- If no reply timer expires and DP T_No_Answer is armed - this leads to the T_No_Answer DP.
- Not reachable event detected or failure of attempt to select the route for the terminating leg - this leads to theT_Not_Reachable DP.
7.3.1.1.3 T_Active
Entry events:
- Indication that the call is accepted and answered by the terminating party. (DP15 - T_Answer)
Functions:
Page 11CR on GSM 03.78 v6.1.0 July 1998
- Connection established between originating party and terminating party. Call supervision is being provided.
- Call release is awaited.
Exit events:
- A disconnection indication is received from the terminating party, or received from the originating party viathe originating half BCSM. (DP17 - T_Disconnect)
- An exception condition is encountered. In addition to specific examples listed above, exception eventsinclude any type of failure that means that the normal exit events for a PIC can not be met.
7.3.1.1.4 T_Exception
Entry events:
- An exception condition is encountered. In addition to specific examples listed above, exception eventsinclude any type of failure, which means that the normal exit events for PIC cannot be met.
Functions:
- Default handling of the exception condition is being provided. This includes general actions necessary toensure that no resources remain inappropriately allocated such as:
- If any relationship exists between the gsmSSF and the gsmSCF send an error information flow closing therelationships and indicating that any outstanding call handling instructions will not run to completion
- The GMSC/gsmSSF should make use of vendor-specific procedures to ensure release of resources withinthe GMSC/gsmSSF, so that line, trunk and other resources are made available for new calls.
Exit events:
- Default handling of the exception condition by gsmSSF/GMSC completed.
Page 12CR on GSM 03.78 v6.1.0 July 1998
*** Next modified section ***
Procedure in the MSC in thecase of CAMEL handling toconnect a call at DP Busy,N o t reachable, R o ute select fa i lu re .
Procedure CAMEL_OCH_MSC1 1(3)
Signals to/ from the righ t are to /from the gsmSSF ifnot otherwise stated.
gsmSSFinvoked?
Release cause
Int_DP_O_Busy
DP_O_Busy
In t_C o nnect
Modify ca ll par ameterswith rece ived in formation
Destination numberm odified?
Send Info ForReconnected call
To process CAMEL_Reconnected_Call_VLR
Wait_Forreconnected call
Result_1
Send Info ForReconnected callNegative Response
In t_DP_Route_Select_F ailu re
DP_Route_Select_F ailu re
Send Info ForR e connected callAck
From process CAMEL_Reconnected_Call_VLR
Result:=reconnect
Result:=c ontinue
In t_Continue
Int_DP_O_Not_R e achable
DP_O_Not_Reachable
In t_Error
In t_DP_Route__Select__Failure
DP_Route__Select__Fa ilure
In t_Release_Call
Result:=continue
From proc ess CAMEL_Reconnected_Call_VLR
Yes
Busy
Yes
N o
Subscriber Absent Other cause
No
Page 13CR on GSM 03.78 v6.1.0 July 1998
Proce du re in the M SC in thec ase of CAMEL handl in g t oc onn ec t a call a t DP B usy,Route select failure.
Procedure CAMEL_OCH_MSC1 1(3 )
Signals to/from th e righ t a re t o/f ro m th e gsmSSF i fnot otherwise stated.
gsmSSFinvoke d?
Release cause
In t_DP_O_Busy
DP_O_Busy
In t_Connect
M odify call p arameterswit h receive d in format io n
Destination numbermo dif ie d?
Send Info ForReconnected call
To process CAMEL_Reconnected_Ca ll_VLR
W ait_Forrecon nected call
Result_ 1
Send Info ForReconnected callNegative Response
From pr ocess CA M EL_Recon n ecte d_Ca ll_VLR
Int _DP_Route_Selec t_Failure
DP _Rou te _Selec t_Fa ilure
S end In fo Fo rReconnected ca llA ck
From process CAMEL_Reco n ne ct ed _Call_V LR
Result :=reconnect Result: =
c on tinu e
I nt _C on tinu e
In t_DP_Route __Select__Failure
DP _Route__S ele ct __Fa ilu re
In t_Erro r In t_Re le as e_ Ca ll
Result:=contin ue
Yes
B usy,S ubscriber A bsen t
Y es
No
Other cause
No
Figure 3Error! Unknown switch argument.: Procedure CAMEL_OCH_MSC1 (sheet 1)
Page 14CR on GSM 03.78 v6.1.0 July 1998
Procedure in the MSC in thecase of CAMEL handling toconnect a call at DP Busy,Not reachable, Route select failure.
Procedure CAMEL_OCH_MSC1 2(3)
Signals to/from the left areto/from the BSS; signals to/from the right are to/from the gsmSSF ifnot otherwise stated.
DP_O_BusyDP_O_Not_ReachableDP_Route_Select_Failure
Release
Int_O_Exception
ReleaseTo destinationexchange
Result:=continue
Page 15CR on GSM 03.78 v6.1.0 July 1998
Procedu re in the MSC in thec ase of CAMEL handling toc onnec t a call a t DP B usy,Route select failure.
Procedure CAMEL_OCH_MSC1 2(3 )
Signals to/from the le ft areto /from the BSS; signals to/ from the righ t are to/f rom the gsmSSF ifnot otherwise stated.
DP_O_BusyDP_Route_Select_Failure
Release
Int_O_Exception
ReleaseTo destinationexchange
Result:=continue
Figure 3Error! Unknown switch argument.: Procedure CAMEL_OCH_MSC1 (sheet 2)
Page 16CR on GSM 03.78 v6.1.0 July 1998
Procedure in the MSC in thecase of CAMEL handling toconnect a call at DP Busy,Not reachable, Route select failure.
Procedure CAMEL_OCH_MSC1 3(3)
Signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
DP_Route_Select__FailureDP_O_Not_ReachableDP_O_Busy
Int_Establish_Temporary_Connection
CAMEL__OCH_ETC
Result=fail?
Result:=continue
-
Int_Connect_To_Resource
CAMEL_OCH_CTR
YesNo
Page 17CR on GSM 03.78 v6.1.0 July 1998
Proce du re in the M SC in thec ase of CAMEL handl in g t oc onn ec t a call a t DP B usy,Route select failure.
Procedure CAMEL_OCH_MSC1 3(3 )
Signals to/ from the right are to/fro mth e gsmSSF if no t o therwise stated.
DP_Route_Select__FailureD P _O_Busy
I nt _Es tabl ish_Tempo rary_C onn ec tio n
CAMEL__OCH_E TC
Result =fa il?
Result:=con tinu e
-
In t_ Co n ne ct _To _Resource
CAMEL_OCH_CTR
YesNo
Figure 3Error! Unknown switch argument.: Procedure CAMEL_OCH_MSC1 (sheet 3)
Page 18CR on GSM 03.78 v6.1.0 July 1998
*** Next modified section ***
P rocedure in the GMSC t o pe rf orm CAMEL h a ndl in gf or a terminating call request
Procedure CAMEL_MT_GMSC_INIT 1(8 )
Signals to /from th e rig ht are to/fromth e gsmSSF
Reconnect=true ?
2
CAMEL informationReceived in SRIack?
MSR Nreceived?
FTNReceived?
Result:=FTN
Result:= Fail
Result:=MSR N
Conten t o fSRI ack
se tCS I=T -CSI
Int _Invoke gs mS SF(T- CS I)
wait_for_gsmSSF_Invoked
S et CSI=T-CSI
S tore O-CSI
Set CSI=T-CSI
Store FTN
Set CSI=T-CS I
StoreO-CSI & FTN
Set CS I=O-CS I
set redirectionin form at io n
Result:=FTN
Yes
No
no
No
y es
No
yes
Yes
T -CSI T-CSIO -CSI
T-CSIFTN
T-CS IO-CSIFTN
FTNO-CS I
Figure 4Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_INIT (sheet 1)
Page 19CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o pe rf orm CAMEL h a ndl in gf or a terminating call request
Procedure CAMEL_MT_GMSC_INIT 2(8 )
Sign als to/from the left are to /f ro mth e orgina tin g exchange;sign als to /f ro m t he r igh t ar e to /fromth e gsmSSF
wa it _fo r_gsmSSF _Invoked
I nt _g sm S SF_I nvoked
I nt_ DP _Terminatio n_a tt em pt_A ut orized
DP _Termination_att empt_Aut orized
Release
I nt_T_Exception
Result :=aborted
Figure 24Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_INIT (sheet 2)
Page 20CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o pe rf orm CAMEL h a ndl in gf or a terminating call request
Procedure CAMEL_MT_GMSC_INIT 3(8 )
Sign als to/from the left are to/fromth e orgina tin g exchange;sig n als to /from the right are to/fromth e gsmSSF;if no t oth erwise s tate d.
DP_Termina tio n __Attempt_
_Author ise d
In t_ Co nt in ue
FTNst ored ?
Set T-CS Isuppress io n
SendRoute in gIn fo
To HLR
Wair_For__Rou te in g_
_In fo_ 2
Set redirectionin form at io n
Result:=FTN
In t_ C on nec t
Sen d_ACM_If_Req uire d
Proce dure def inedin G SM 03.18
DestinationNumber Modif ed ?
Mo dify c allpara m ete rs
wit h re ceivedinfo rma tion .
OriginalCalled P arty S ubscribed
To CUG?
CUG inforeceived in
incoming call?
M odify callp arameters
with receivedinform a tio n
A pp ly_O-CSIindicat orp resent?
O-CSIstore d ?
FTN:=Destin atio n Ro ut in g
Address
C M N:=Destination Routin g
Address
Result:=CM N
Int _E xc ep tio n
Result:=f ail
1 2
No
Yes
No
Yes
Yes
No
Yes
Yes
No
No
Yes
No
Figure 24Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_INIT (sheet 3)
Page 21CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o pe rf orm CAMEL h a ndl in gf or a terminating call request
Procedure CAMEL_MT_GMSC_INIT 4(8 )
Sign als to/from the left are to/fromth e orgina tin g exchange;sig n als to /from the right are to/fromth e gsmSSF;if no t oth erwise s tate d.
DP_Termina tion _A ttempt_
A uth o rised
Release
Int _DP__T_Abandon
Result:=aborted
I nt_ R eleaseCa ll
Release
Result :=fa il
In t_Erro r
Default CallHandling = Contin ueCall?
1
No
Yes
Figure 24Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_INIT (sheet 4)
Page 22CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o pe rf orm CAMEL h a ndl in gf or a terminating call request
Procedure CAMEL_MT_GMSC_INIT 5(8 )
Signals to/ from the right are to/fro mth e gsmSSF.
DP_Terminat io n_Attempt_AuthorisedDP_T_Busy
I nt _Es tabl ish_Tempo rary_C onn ec tio n
CAMEL_MT_ETC
Result =fa il?
Result:=fa il
-
In t_ Co n ne ct _To _Resource
CAMEL_MT_CTR
YesNo
Figure 24Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_INIT (sheet 5)
Page 23CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o pe rf orm CAMEL h a ndl in gf or a terminating call request
Procedure CAMEL_MT_GMSC_INIT 6(8 )
Signals to/ from the right are to/fro mth e gsmSSF;if no t oth erwise s tate d.
Wait_For_Ro ut eing _
Info _ 2
Send RouteingIn foNega tive Response
From HLR
Ca us e=Abse nt
Subscriber?
In t_DP_T_Busy
DP _T_Busy
I nt _DP_T_Aban do n
Result:=fa il
In t_ Release_Call
Release
Result:=Fail
Yes
No
Figure 24Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_INIT (sheet 6)
Page 24CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o pe rf orm CAMEL h a ndl in gf or a terminating call request
Procedure CAMEL_MT_GMSC_INIT 7(8 )
Sign als to/from the left are to /f ro mth e orgina tin g exchange;sign als to /f ro m t he r igh t ar e to /fromth e gsmSSF;if no t oth erwise s tate d.
W ait_For__ Ro ut eing _
_ Info _2
Send RouteingIn fo Ack/* FTN */
From HLR
S et re directio nin fo rm a tio n
Result:=F TN
S en d Ro ut eingI nfo A ck/ * FTN, O-CSI */
From HLR
Store O-CS I
Send RouteingIn fo Ack/* M S RN * /
From HLR
Result:=MSRN
Figure 24Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_INIT (sheet 7)
Page 25CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o pe rf orm CAMEL h a ndl in gf or a terminating call request
Procedure CAMEL_MT_GMSC_INIT 8(8 )Sign als to/from the left are to/fro mth e orgina tin g exchange;sign als to /f ro m t he r igh t are to /fromth e gsmSSF;if no t oth erwise s tate d.
DP _T_Busy
Release
In t_T_Exceptio n
Result:=a bo rt ed
I nt _R ele ase
Result:=fa il
In t_Erro r
In t_T_Exc ep tio n
Result:=fa il
In t_ Co nt in ue Int _Connect
2
Figure 24Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_INIT (sheet 8)
Page 26CR on GSM 03.78 v6.1.0 July 1998
Process in the GM SC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 1(8)
Signals to/from the right are to/fromthe gsmSSF
Reconnect=true?
2
CAMEL informa tionR eceive d in SR I ack?
MSRNreceived?
FTNRece ived?
Result:=FTN
Result:= Fail
R esult :=MSRN
Content ofSR I ack
setCSI=T-CSI
Int_Invoke gsmSSF(T- CSI)
wait_for_gs m S SF_Invoked
Set CSI= T- CSI
Store O-C SI
Set CSI= T-C SI
Store FTN
Set C SI=T-CSI
StoreO - CSI & FTN
Set CSI=O-CS I
set redirectioninforma tion
R esult :=FTN
Yes
No
no
No
yes
No
yes
Yes
T -CSI T -CSIO-CSI
T -CSIFTN
T-CSIO-CSIFTN
FTNO-CSI
Figure 24a: Procedure CAMEL_MT_GMSC_INIT (sheet 1)
Page 27CR on GSM 03.78 v6.1.0 July 1998
Process in the GM SC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 2(8)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF
wa it_for_gsmSSF_Invoked
Int_gsm S SF_Invoked
Int_DP_Term ination_attempt_A utorized
DP_Termin ation_attemp t_Autorized
Re lease
Int_T_Exception
Result:=a bor ted
Figure 24b: Procedure CAMEL_MT_GMSC_INIT (sheet 2)
Page 28CR on GSM 03.78 v6.1.0 July 1998
Process in the GM SC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 3(8)
Signals to/from the left are to/fromthe orginati ng exchange;signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
DP_T ermination__Attemp t_
_Au thorised
Int_Continue
FTNstored ?
Se t T -CSIsuppression
SendRo uteingInfo
Wair_For__Routeing_
_Info_2
Set redirectioninformation
Result:=FTN
Int_Connect
Send_ACM_If_Required
Procedure definedin GSM 03.18
DestinationNumber Modifed?
Modify callparame ters
w ith receivedinformation.
OriginalCa lled Par ty Su bscribed
T o C UG?
CUG inforeceived in
incom ing call?
Modify callparameters
with receivedinforma tion
Apply_O-CSIindicatorpresent?
O-CSIstored ?
FTN:=De stin ation Routing
Address
CMN:=Destination Routing
Address
Result:=CMN
Int_Exception
Result:=fail
1 2
To HLR
No
Yes
No
Yes
Yes
No
Yes
Yes
No
No
Yes
No
Figure 24c: Procedure CAMEL_MT_GMSC_INIT (sheet 3)
Page 29CR on GSM 03.78 v6.1.0 July 1998
Process in the GM SC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 4(8)
Signals to/from the left are to/fromthe orginati ng exchange;signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
DP_Termination_Attempt_
Auth orised
Int_ReleaseCa ll
Re lease
Result:=fail
Int_Error
Default CallHandling = C onti nueCall?
1
Re lease
Int_DP__T_Abandon
Result:=aborted
No
Yes
Figure 24d: Procedure CAMEL_MT_GMSC_INIT (sheet 4)
Page 30CR on GSM 03.78 v6.1.0 July 1998
Process in the GM SC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 5(8)
Signals to/from the rig ht are to/fromthe gsmSSF.
DP _Termination_Attemp t_Auth orisedDP_T_Not_Reacha ble
Int_Establish_Temp orary_Connection
CAMEL_M T_ETC
Result=fail?
R esult :=fail
-
Int_Conne ct_To_R esource
CAME L_MT_CTR
YesNo
Figure 24e: Procedure CAMEL_MT_GMSC_INIT (sheet 5)
Page 31CR on GSM 03.78 v6.1.0 July 1998
Process in the GM SC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 6(8)
Signals to/from the rig ht are to/fromthe gsmSSF;if not otherwise stated.
Wait_F or_Routeing_
Info_2
Sen d Ro uteingInfoNegative Response
F rom HLR
Cause=Absent
Subscriber?
Int_DP_T_Not_Reachable
DP_T_No t_Reachable
Int_DP_T_Abandon
Result:=fail
Int_Relea se_Ca ll
Release
Result:=Fail
Yes
No
Figure 24f: Procedure CAMEL_MT_GMSC_INIT (sheet 6)
Page 32CR on GSM 03.78 v6.1.0 July 1998
Process in the GM SC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 7(8)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF;if not otherwise stated.
Wait_For __Rou teing_
_Info_2
Sen d Ro uteingInfo Ack/* FTN */
F rom HLR
Set re direct ioninformation
Result:=FTN
Send Route ingInfo Ack/* FTN, O -CSI */
From HLR
Store O-CSI
Sen d Ro uteingInfo Ac k/* MSRN * /
From H L R
Result:=MS RN
Figure 24g: Procedure CAMEL_MT_GMSC_INIT (sheet 7)
Page 33CR on GSM 03.78 v6.1.0 July 1998
Process in the GM SC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_INIT 8(8)Signals to/from the left are to/fromthe orginating exchange;signals to/from t he right are to/fromthe gsmSSF;if not otherwise stated.
2
Result:=fail
In t_T_ExceptionResult:=
fail
DP_T_ Not Reachable
Release
Int_T_Exception
Result:=aborted
Int_ Release Int_Error Int_Continue Int_Connect
Figure 24h: Procedure CAMEL_MT_GMSC_INIT (sheet 8)
Page 34CR on GSM 03.78 v6.1.0 July 1998
Pr ocedure in the GMSC to ha ndle aterminating call request
Procedure CAMEL_MT_GMSC_DISC4 1(3)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF.
gsmSSFinvoked?
Result:=fail
Cause inrelease message?
Int_DP_T_Busy
DP_T_Busy
Int_Connect
Modify callparameters w ith
rece ived informa tion
Destination Number
Modified?
Result:=reconnect
R esult :=fail
Int_Conti nue Int_Error Int_Release_Call
Int_DP_T_Not_Reacha ble
DP_T_No t_Reachable
Int_D P_T_N ot_Reachable
D P_ T_Not_Reachable
No
Yes
Busy
Yes
No
Subscriber AbsentOther cause
Page 35CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o ha nd le ate rmin at in g c all req ues t
Procedure CAMEL_M T_GMSC_DISC4 1(3 )
Sign als to/from the left are to /f ro mth e orgina tin g exchange;sign als to /f ro m t he r igh t ar e to /fromth e gsmSSF.
gsmSSFinvoke d?
Result:=f ail
I nt _DP_T_Busy
DP _T_Busy
In t_ Co nnect
Mo dif y callparameters with
receiv ed in fo rm a tion
Destination Number
Mo dif ie d?
Result:=recon n ect
Result:=fa il
I nt _C on tinu e In t_Erro r Int _Rele ase _Call
No
Y es
No
Yes
Figure 6Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_DISC4 (sheet 1)
Page 36CR on GSM 03.78 v6.1.0 July 1998
Procedure in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC4 2(3)
Signals to/from the right are to/fromthe gsmSSF if not otherwise stated.
DP_T_BusyDP_T_Not_Reachable
Int_Establish_Temporary_Connection
CAMEL_MT_ETC
Result=fail?
Result:=fail
-
Int_Connect_To_Resource
CAMEL_MT_CTR
YesNo
Page 37CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o ha nd le ate rmin at in g c all req ues t
Procedure CAMEL_M T_GMSC_DISC4 2(3 )
Signals to /from th e rig ht are to/fromth e gsmSSF if no t o therwise stated.
DP _T_Busy
In t_Es tablish _Tem porary_Connec tion
CAMEL_MT_ETC
Result=fa il?
Result :=fa il
DP _T_Busy
I nt_ C on nect_To_Resource
CAMEL_MT_C TR
YesNo
Figure 6Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_DISC4 (sheet 2)
Page 38CR on GSM 03.78 v6.1.0 July 1998
Procedure in the GMSC to handle aterminating call request
Procedure CAMEL_MT_GMSC_DISC4 3(3)
Signals to/from the left are to/fromthe orginating exchange;signals to/from the right are to/fromthe gsmSSF.
DP_T_BusyDP_T_Not_Reachable
Release
Int_T_Exception
Result:=fail
Page 39CR on GSM 03.78 v6.1.0 July 1998
P rocedure in the GMSC t o ha nd le ate rmin at in g c all req ues t
Procedure CAMEL_M T_GMSC_DISC4 3(3 )
Sign als to/from the left are to/fromth e orgina tin g exchange;sig n als to /from the right are to/fromth e gsmSSF.
DP _T_Busy
Relea se
I nt _T_Exception
Result:=fa il
Figure 6Error! Unknown switch argument.: Procedure CAMEL_MT_GMSC_DISC4 (sheet 3)
Page 40CR on GSM 03.78 v6.1.0 July 1998
*** Next modified section ***
8.6 Handling of mobile calls in the gsmSSFHandling of mobile calls in the gsmSSF may involve the following process and procedures :
- gsmSSF,
- Check_Criteria.
- Handle_AC,
- Handle_ACR,
- Handle_CIR,
- Handle_SCI.
The detailed error handling for the process gsmSSF and the associated procedures is specified in GSM 09.78 ([5]).
8.6.1 Information flow for call duration control
The following diagram shows the handling of the different timers that are used in the process gsmSSF and in theprocedures Handle_AC, Handle_ACR, Handle_CIR. Timers Tssf, Tcp, Tsw, Tw and DELTA are defined in theprocess gsmSSF.
AC(Tcp1)
ANSWER
ACR
AC(Tcp2)
RELEASEACR
RRBCSM
CONNECT
SET UP
ALERT
ANSWER
AC(Tcp3)
RELEASEACR
Tsw
Tcp1
Delta
Tcp2-Delta
Tsw
Tcp3
CSE gsmSSF/MSC MSC / TE
ETC/CTR
ERBCSM
Figure 7: Information flow for call control duration
8.6.2 Behaviour of the gsmSSF in the process gsmSSF
The following paragraphs give details on the behaviour of the gsmSSF in the procedure gsmSSF.
Page 41CR on GSM 03.78 v6.1.0 July 1998
8.6.2.1 Actions of the gsmSSF on receipt of CAP_Request_Report_BCSM_Event(at the state Waiting_For_Instructions)
The gsmSSF arms the requested EDP, if the arming rules are fulfilled and returns to state Waiting_For_Instructions.
The gsmSCF may request the monitoring for any one or more Answer, Busy, No Answer, Abandon, Not Reachable,Route Select Failure and Disconnect Event of a party in the call.
8.6.2.2 Actions of the gsmSSF on receipt of CAP_Continue (at the stateWaiting_For_Instructions)
An Int_Continue is sent to request the GMSC/MSC to continue call set-up as originally requested.
8.6.2.3 Actions of the gsmSSF on receipt of CAP_Release_Call (at the stateMonitoring)
When a control relationship exists between the gsmSCF and gsmSSF (at least one EDP-R is armed), the gsmSCFmay spontaneously instruct the gsmSSF to release the call at any time using the Release Call IF. The Release Call IFshall not be sent from the gsmSCF if only monitor relationship exists between the gsmSSF and the gsmSCF.
8.6.3 Procedure Handle_SCI
1) Precondition: before an answer event is detected and no Tsw running:
if 1 set of e-parameters received --> send to the MSC
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> send 1st/start Tsw/store 2nd
2) Precondition: before an answer event is detected and Tsw running and no e-parameters
if 1 set of e-parameters received --> error, no e-parameters stored
if 2 sets e-parameters received --> send 1st/store 2nd
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> error
3) Precondition: before an answer event is detected and Tsw running and e-parameters stored:
if 1 set of e-parameters received --> error
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> error
4) Precondition: after an answer event is detected and no Tsw running:
if 1 set of e-parameters received --> send to the MSC
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> start Tsw/store set
if 2 sets of e-parameters and Tariff Switch received --> error
5) Precondition: after an answer event is detected and Tsw running and no e-parameters
if 1 set of e-parameters received --> store e-parameters
Page 42CR on GSM 03.78 v6.1.0 July 1998
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> error
6) Precondition: after an answer event is detected and Tsw running and e-parameters stored:
if 1 set of e-parameters received --> error
if 2 sets e-parameters received --> error
if 1 set of e-parameters and Tariff Switch received --> error
if 2 sets of e-parameters and Tariff Switch received --> error
NOTE: The MSC shall store the received e-parameters to be sent subsequently to the MS. The MSC shall sendthese e parameters to the MS in a Connect message.
Page 43CR on GSM 03.78 v6.1.0 July 1998
Invocation of gsmSSF in MO,M T or CF call case.
Process gsmSSF 1(20)
Sig nals to/from t he left are to/from theprocesses OCH_M S C, M T_GMSC and MT_CF_MSC;sign als to /from the r ight ar eto/from th e gsm S CF .
T imers used in the gsmSSF process:
T ss f: Application tim er in the ss f.T cp: Time r for call period. This t imer measures the duration of a call period.Tsw: Timer for tariff sw itch. At the expiration of th is t imer, a new tari ff switch s hall be started.Tw: W arning timer. At the expiration of this timer , a warning tone shall b e played to the call ing party.DELTA: time , measured in the gsmSSF, elapsed between the time an ApplyC hargingReport operation is send to the gsm SCF and an ApplyCh arging operation is rece ived from the gsmS CF.
Idle
Int_InvokegsmSSF(CSI)
A rm DPThe received CS I stateswhether DP Col lected_Infoor DP Terminating_ Attempt_Authorised shall be armedas TDP .
Int_gsmSSF Invoked
Wait_For__Request
Int_O_Exception,Int_T_Exception
Idle
Int_DP_O_Answer,Int_DP _T_Answer,Int_DP _O _Ab andon,Int_DP _T_Abandon,Int_DP _Route_Select_Failure,Int_DP_O_No_Answer,Int_DP_T_No_Answer,Int_DP _O _Busy,Int_DP _T_Busy,Int_DP_O_Disconne ct ,Int_DP_T_Disconnect,Int_DP_O_Not_Reachable,Int_DP_T_Not_Reacha ble
In t_Co ntinue
Page 44CR on GSM 03.78 v6.1.0 July 1998
I nvocat ion of gsmSSF in MO,MT or CF ca ll case.
Process gsmSSF 1(2 0)
Signals to/from the le ft are to/ from theprocesses OCH_MSC, MT_GMSC and MT_CF_MSC;sign als to /f ro m th e righ t areto /from the gs mS CF.
Tim e rs use d in th e gsmSSF process:
Tssf: Application timer in the ssf.Tcp: Timer for call p eriod. T his tim er measures the duration of a call p erio d.Tsw: Tim e r for t arif f switch. At the expirat io n of this time r , a new tariff switch shall be started.Tw: W arning tim er. At t he e xpiration o f t his tim er, a wa rn ing to ne shall be played to th e c alling par ty .DELTA: time, measured in the gsmSSF, elapsed between the time an Ap plyChargingReport operation is se nd t o the gsmSCF and an Ap plyCharging opera tio n is received from the gs mS CF.
Idle
Int_ InvokegsmSSF(CS I)
A rm DP
The received CS I st ateswh et he r DP C ollected_Infoor DP Terminat in g_Attempt_Aut ho rise d shall be arm edas TDP .
In t_gsmSSF Invoked
Wait _Fo r__Request
I nt_O_Exception ,I nt_T_Exc ep tion
Idle
In t_DP_O_Answer ,Int _DP_T_Answer,In t_DP_O_Aband on ,In t_DP_T_Aba nd on ,Int _DP_Route_Select_Failure,In t_DP_O_No_A nswer,Int _DP_T_No_Answer,In t_DP_O_Busy,In t_DP_T_Busy,In t_DP_O_Disco nn ect,In t_DP_T_Disco nn ect
In t_ Co nt in ue
Figure 8Error! Unknown switch argument.: Process gsmSSF (sheet 1)
Page 45CR on GSM 03.78 v6.1.0 July 1998
Invocation of gsmSSF in MO,M T or CF call case.
Process gsmSSF 15(20)Sig nals to/from t he left are to/from theprocesses OCH_M S C, M T_GMSC and MT_CF_MSC;sign als to /from the r ight ar eto/from th e gsm S CF .
Monito ring
Int_DP_O_Answer,Int_DP_T_Answer
AC pending
Star t Tcp
Tw>0
Start Tw
Stored e parameters?
Sende parameters
This provoques the M S Cto send e parame ters tothe calling party
DP a rmed?
DP armedas EDP-R?C AP_Event_
_Rep ort_BCSM(Notify & C ontinue)
D isarm th isDP
For DP O/T D is connect the DPis only disarmed for the legfor w hi ch the event wasreceived.
Any rema ining armedEDPs orou tstanding report?
Term inateRelatio nship
Control orMonitorRelatio nship
Int_Continue
Idle
Int_Continue
Monito ring
CAP_Event__Report_BCSM(Interrupted)
Disarm thisDP
For DP O/T Disconnect the DPis only disarmed for the legfor which the event wasreceived.
Set Outstanding__Requests = 1
Set Tssf to defaultnon user interactionTs sf time r value and
restart T ssf
Waiting_For__Instruc tions
CAP_Ca ncel_(All)
Disarm a llEDPs
Cancel allreports
Int_DP_O_No_Answer,Int_DP_T_No_Answ er,Int_DP_O_Busy,Int_DP_T_Busy,Int_DP_Route_Select_F ailure,Int_DP_O_No t_Re achable,Int_DP_T_Not_Reachable,
T rue
Yes
Yes
YesNo
No
Yes
Yes
No
No
No
False
Page 46CR on GSM 03.78 v6.1.0 July 1998
I nvocat ion of gsmSSF in MO,MT or CF ca ll case.
Process gsmSSF 15(20)Signals to/from the le ft are to/ from theprocesses OCH_MSC, MT_GMSC and MT_CF_MSC;sign als to /f ro m th e righ t areto /from the gs mS CF.
M o nitoring
I nt_ D P_O _Answer,I nt_ D P_T_Answer
A C pe nd in g
Star t Tcp
Tw>0
S tart Tw
S tore d e p arameters?
S en de p arameters
Th is pro vo qu e s the MSCt o s en d e p arameters tot he calling pa rty
DP armed?
DP arm e das EDP-R?CAP_Event_
_ Re por t_B CS M(Notify & Cont inue)
Disa rm t hisDP
For DP O/T Disconnect the DPis only disarme d fo r the legfo r which the event wasreceive d.
A ny re m ainin g a rm e dE DPs o ro ut st an ding rep o rt?
TerminateRelationship
Control orM onito rRelat ionship
In t_Cont in ue
Idle
I nt _C on tinu e
M o nitoring
CAP_Event__Report_BCSM(Int erru p ted)
Disarm thisDP
For DP O/T Disconnect the DPis only disar me d f or th e le gfor which the ev ent w asreceived.
Set Ou tsta nd in g __Req uests = 1
Set Tssf to de faultnon user in te ractionTssf t imer value and
restart Tssf
Waitin g_For__Ins tructions
CAP_Cancel_(All)
D is arm a llEDPs
Ca nce l allrepo rts
Int _DP_O_N o_A nswer,Int_DP_T_No_Answer ,Int _DP_O_Busy,Int _DP_T_B usy,Int_DP_R out e_Select_Failurea
Tru e
Yes
Yes
Y esNo
No
Yes
Y es
No
No
No
False
Figure 8Error! Unknown switch argument.: Process gsmSSF (sheet 2)
Change Request No. A043
Technical Specification GSM 03.78 version 6.1.1
Submitted to SMG for approval: without presentation ("non-strategic") [ ]with presentation ("strategic) [ x ]
Status at SMG [#27 ]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [ Release 97 ] Work item: CAMEL Phase 2
Other phase(s) affected: [ ] If yes, linked CR(s):
Proposed change affects: SIM [ ] ME [ ] Network [ X ]
Source: SMG3 Tdoc SMG3 98P191 Date: 15 September 1998
Subject: GSM Forwarding Pending Indication in IDP Operation
Category: F - Correction [ ]A - Corresponds to a Phase 2 correction [ ]B - Addition of Feature [ ]C - Functional modification of Feature [x]D - Editorial modification [ ]
Reason for change:
At SMG#26 CR 03.78-A028 was approved. Unfortunately the contents of that CR was not incorporated inthe present version of the specification. This CR is a renewed duplication of CR 03.78-A028. It is analignment with the present version of GSM 09.78.
CFU and CFNRc (detached in HLR) services are invoked by HLR returning forwarded-to-number in thefirst SRI-Ack to the GMSC. The T-BCSM is invoked before CF is really invoked in GMSC. In IDP for T-BCSM no information about pending GSM forwarding is sent to CSE. So from CSE point of view there isterminating/roaming leg to be managed and, potentially, charged. However, there is no such leg inmentioned scenario.
Therefore CSE has to be informed about pending GSM forwarding in IDP for terminating CAMELservice.
Sections affected, and additional explanation of details of change (if needed): Section 9.1.5.2.
Attached revised pages: 3 pages
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects (possibly): MS Test Specs [ ] BSS Test Specifications [ ] O&M Specs [ ]Attached CRs?:
Cross Phase Compatibility:Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ]
CR to 09.90 attached:Change affects operation of: Phase 1 SIM in Phase 2(+) ME [ ]
CR to 09.91 attached:Phase 2(+) SIM in Phase 1 ME [ ]CR to 09.91 attached:
Other comments: This is a corrective CR because CR0378A028 was not incorporated into version6.1.1 of GSM 03.78.
9.1.5 Initial DP
9.1.5.1 Description
This IF is generated by the gsmSSF when a trigger is detected at a DP in the BCSM, to requestinstructions from the gsmSCF.
9.1.5.2 Information Elements
The following information elements are required:
Information element name MO MF MT Description
Additional Calling PartyNumber
- C C The calling party number provided by the access signallingsystem of the calling user.
Bearer Capability M C C This IE indicates the type of the bearer capability connectionto the user.
Called Party Number - M M This IE contains the number used to identify the called partyin the forward direction.
Called Party BCD Number M - - This IE contains the number used to identify the called partyin the forward direction.
Calling Party Number M C C This IE carries the calling party number to identify the callingparty or the origin of the call.
Calling Partys Category M C C Indicates the type of calling party (e.g., operator, pay phone,ordinary subscriber).
Call Reference Number M M M This IE may be used by the gsmSCF for inclusion in anetwork optional gsmSCF call record.For MO calls, the call reference number is set by the MSCand included in the MO call record.For MT calls, the call reference number is set by the GMSCand included on the RCF call record in the GMSC and on theMT call record in the terminating MSC.For CF calls, the call reference number is set by the GMSCand included on the CF record in the GMSC or the MSC.
Event Type BCSM M M M This IE indicates the armed BCSM DP event (i.e.,Collected_Info and Terminating_Attempt_Authorised),resulting in the Initial DP IF.
Ext-Basic Service Code C C C This IE indicates the type of basic service i.e., teleservice orbearer service.
High Layer Compatibility C C C This IE indicates the type of the high layer compatibility,which will be used to determine the ISDN-teleservice of aconnected ISDN terminal.
IMSI M M M This IE identifies the mobile subscriber.
IP SSP Capabilities C C C This IE indicates which SRF resources are supported withinthe gsmSSF and are available. If this IE is absent, thisindicates that no gsmSRF is attached and available.
Location Information M - C This IE is described in the next table.
Location Number M C C For mobile originated calls this IE representing the location ofthe calling party. For all other call scenarios this IE containsthe location number received in incoming ISUP signalling.
(Continued)
(Concluded)
Information element name MO MF MT Description
MSC Address M M M E.164 address of interrogating MSC in international format.This IE may be used together with the Call ReferenceNumber by the gsmSCF for inclusion in a network optionalgsmSCF call record.For MO calls, the MSC Address is set by the MSC andincluded in the MO call record.For MT calls, the MSC Address is set by the GMSC andincluded on the RCF call record in the GMSC and on the MTcall record in the terminating MSC.
For CF calls, the MSC Address is set by the GMSC or theMSC and included on the CF record in the GMSC or theMSC.
Original Called Party ID - C C This IE carries the dialled digits if the call has met callforwarding on the route to the gsmSSF.
Redirecting Party ID - M C This IE indicates the directory number the call was redirectedfrom.
Redirection Information - M C It contains forwarding related information, such as redirectioncounter.
Service Key M M M This IE identifies for the gsmSCF the requested set of one ormore CAMEL services. It is used to address the correctapplication/SLP within the gsmSCF.
Subscriber State - - C This IE indicates the status of the MS. The states are:- CAMELBusy: The MS is engaged on a transaction for a
mobile originating or terminated circuit-switched call.- NetworkDeterminedNotReachable: The network can
determine from its internal data that the MS is notreachable.
- AssumedIdle: The state of the MS is neither"CAMELBusy" nor "NetworkDeterminedNotReachable".
- Not provided from VLR.
Time And Timezone M M M This IE contains the time that the gsmSSF was triggered,and the time zone the gsmSSF resides in.
GSM Forwarding Pending - - C This parameter indicates that a forwarded-to-number wasreceived and the call will be forwarded due to GSMsupplementary service call forwarding in the GMSC.
M Mandatory (The IE shall always be sent)C Conditional (The IE shall be sent, if available)- Not applicableLocation Information contains the following information:
Information element name MO MF MT Description
Location Number - - C See GSM 03.18 [3].
CellIdOrLAI M - C See GSM 03.18 [3].
Geographical Information C - C See GSM 03.18 [3].
Age Of Location Information M - C See GSM 03.18 [3].
VLR number M - C See GSM 03.18 [3].
M Mandatory (The IE shall always be sent)C Conditional (The IE shall be sent, if available)- Not applicable
CHANGE REQUEST No. A138
Technical Specification GSM 09.02 version 6.0.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic")[ x]
Status at SMG [ #27 ]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [ R’97] Work item: GPRS
Other phase(s) affected: [x] If yes, linked CR(s): CR 09.02-A137
Proposed change affects: SIM [ ] ME [ ] Network [x]
Source: SMG3 Tdoc SMG3 98C418 Date: 20/7/98
Subject: Extending the applicability of GMSC Address in ProvideRoamingNumber.
Category: F - Correction [x]A - Corresponds to a Phase 2 correction [ ]B - Addition of Feature [ ]C - Functional modification of Feature [ ]D - Editorial modification [ ]
Reason for change:
For the use of the parameter GMSC Address and conditions for its presence in the MAPProvideRoamingNumber operation the reader is referred to GSM03.79. However, the GMSC-Address is now applicable in the CAMEL case (Section 9.9.4.2 of GSM3.78 v 6.0.0)
Therefore the purpose of this change request is to extend the applicability of the GMSCAddress used in the MAP ProvideRoamingNumber operation.
Sections affected, and additional explanation of details of change (if needed):
Section 8.2.3
Attached revised pages:
Page(s): 2
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ]Attached CRs?:
Cross Phase Compatibility:Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ]
CR to 09.90 attached:Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ]
CR to 09.91 attached:Phase 2(+) SIM in Phase 1 ME [ ]CR to 09.91 attached:
Other comments:
10.2 MAP_PROVIDE_ROAMING_NUMBER service
10.2.1 Definition
This service is used between the HLR and VLR. The service is invoked by the HLR to requesta VLR to send back a roaming number to enable the HLR to instruct the GMSC to route anincoming call to the called MS.
This is a confirmed service which uses the Primitives described in table 10.2/1.
10.2.2 Service primitives
Table 10.2/1: MAP_PROVIDE_ROAMING_NUMBER parameters
Parameter name Request Indication Response ConfirmInvoke Id M M(=) M(=) M(=)IMSI M M(=)MSC Number M M(=)MSISDN U C(=)LMSI C C(=)GSM Bearer Capability C C(=)Network Signal Info C C(=)Suppression Of Announcement C C(=)Call Reference Number C C(=)GMSC Address C C(=)OR Interrogation C C(=)Alerting Pattern C C(=)Roaming Number C C(=)User error C C(=)Provider error O
10.2.3 Parameter use
See subclause 7.6 for a definition of the parameters used, in addition to the following. Notethat:
- a conditional parameter whose use is defined only in GSM 03.78 shall be absent if thesending entity does not support CAMEL;
- a conditional parameter whose use is defined only in GSM 03.79 shall be absent if thesending entity does not support optimal routeing;
- a conditional parameter whose use is defined only in GSM 03.78 & GSM 03.79 shall beabsent if the sending entity supports neither CAMEL nor optimal routeing.
IMSI
This is the IMSI of the called Subscriber.
MSC Number
This is the ISDN number assigned to the MSC currently serving the MS. The MSC number willhave been stored in the HLR as provided at location updating.
MSISDN
See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.
LMSI
See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.
GSM Bearer Capability
See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.
This information is passed according to the rules specified in TS GSM 09.07.
There may be two GSM Bearer Capabilities supplied.
Network Signal Info
See GSM 03.18 [97] for the conditions for the presence of the components of this parameter.
Suppression Of Announcement
The use of this parameter and the requirements for its presence are specified in GSM 03.78.
Call Reference Number
The use of this parameter and the conditions for its presence are specified in GSM 03.78 [98]and GSM 03.79 [99].
GMSC Address
See GSM 03.79 [99] for tThe use of this parameter and the conditions for its presence arespecified in GSM 03.78 [98] and GSM 03.79 [99].
OR Interrogation
See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.
Alerting Pattern
See GSM 03.78 [98] for the use of this parameter and the conditions for its presence.
Roaming Number
See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.
User error
This parameter is sent by the responder when an error is detected and if present, takes one ofthe following values:
- Absent Subscriber;This error will be returned if the IMSI detach flag is set.
- No Roaming Number Available;- OR Not Allowed;
This indicates that the MAP_PROVIDE_ROAMING_NUMBER indication included theOR interrogation indicator, but the VLR does not support optimal routeing.
- Facility Not Supported;- System Failure;- Data Missing;- Unexpected Data Value.See subclause 7.6 for a definition of these reasons.
Provider error
These are defined in subclause 7.6.
CHANGE REQUEST No. A149
Technical Specification GSM09.02 version 6.1.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic") [ x ]
Status at SMG [#27]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [R97] Work item: Optimal Routeing, CAMEL
Other phase(s) affected: [R96] If yes, linked CR(s): CR 09.02-A148
Proposed change affects: SIM [ ] ME [ ] Network [x]
Source: SMG3 Tdoc SMG3 98C507 Date: September 1998
Subject: Clarification of limit on length of O-CSI in MAP_RESUME_CALL_HANDLING
Category: F - Correction [x]A - Corresponds to a Phase 2 correction [ ]B - Addition of Feature [ ]C - Functional modification of Feature [ ]D - Editorial modification [ ]
Reason for change:
For CAMEL Phase 1 & CAMEL Phase 2 there is a limit of one set of O-BCSM TDP data in the Resume Call Handlingmessage
Sections affected, and additional explanation of details of change (if needed):
Subclause 10.3.3
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ]Attached CRs?:
Cross Phase Compatibility:Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ]
CR to 09.90 attached:Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ]
CR to 09.91 attached:Phase 2(+) SIM in Phase 1 ME [ ]CR to 09.91 attached:
Other comments:
GSM 09.02: version 6.1.0 Release 1997 2 Draft EN 300 974 V6.1.0 (1998-07)
10.3 MAP_RESUME_CALL_HANDLING service
10.3.1 Definition
This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC torequest the GMSC to resume handling the call and forward it to the specified destination.
This is a confirmed service which uses the Primitives listed in table 10.3/1.
10.3.2 Service primitives
Table 10.3/1: MAP_RESUME_CALL_HANDLING parameters
Parameter name Request Indication Response ConfirmInvoke Id M M(=) M(=) M(=)Call Reference Number M M(=)Basic Service Group M M(=)IMSI M M(=)Forwarding Data M M(=)CUG Interlock C C(=)CUG Outgoing Access C C(=)O-CSI C C(=)CCBS Target C C(=)User error C C(=)Provider error O
10.3.3 Parameter use
See subclause 7.6 for a definition of the parameters used, in addition to the following.
Call Reference Number
See GSM 03.79 [99] for the use of this parameter.
Basic Service Group
See GSM 03.79 [99] for the use of this parameter.
IMSI
This is the IMSI of the forwarding Subscriber.
Forwarding Data
Includes the forwarded-to number, the forwarding reason, an indication of whether the calling party is to be notified thatthe call has been forwarded and possibly a forwarded-to subaddress.
CUG Interlock
See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.
CUG Outgoing Access
See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.
O-CSI
See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.
For CAMEL phases 1 & 2, the O-CSI shall contain only one set of O-BCSM TDP data.
CCBS Target
GSM 09.02: version 6.1.0 Release 1997 3 Draft EN 300 974 V6.1.0 (1998-07)
See GSM 03.93 [107] for the use of this parameter and the conditions for its presence.
User error
This parameter is sent by the responder when an error is detected and if present, takes one of the following values:
- Optimal Routeing not allowed;
- Forwarding failed.
Provider error
These are defined in subclause 7.6.
CHANGE REQUEST No. A152r1
Technical Specification GSM 09.02, version 6.1.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic") [x]
Status at SMG [#27]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [R97] Work item: CAMEL R97
Other phase(s) affected [ ] If yes, linked CR(s):
Proposed change affects: SIM [ ] ME [ ] Network [x]
Source: SMG3 Tdoc SMG3 98C579 Date: September 1998
Subject: Support Of CAMEL Phase 2 In GSM 09.02
Category: F - Correction [ ]A - Corresponds to a phase 2 correction [ ]B - Addition of Feature [ ]C - Functional modification of Feature [x]D - Editorial modification [ ]
Reason for change:
Inclusion in MAP of CAMEL Phase 2 SS Invocation Notification SDL diagrams.
Sections affected, and additional explanation of details of change (if needed):
Section 22.
Attached revised pages:
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ]Attached CRs?:
Cross Phase Compatibility:
Other comments:
Page 2GSM 09.02 V.5.7.0 TS 101 046 V 5.0.1 (1997-08)
---------------- first modified section ----------------
22.12 Supplementary Service Invocation Notificationprocedure
22.12.1 General
The Supplementary Service Invocation Notification procedure is used to notify a gsmSCF about the invocation of aGSM Supplementary Service.
The Supplementary Service Invocation Notification procedure is shown in figure 22.12.1/1.
The following services may be used:
MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION (defined in clauses 8 and 25);
Figure 22.12.1/1: Interfaces and services for supplementary service invocation notification
1.
2.
1) MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION (MSC to gsmSCF)2) MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION-ACK (gsmSCF to MSC)
22.12.2 Procedures in the MSC
The supplementary service invocation notification procedure in the MSC is triggered when the requestedsupplementary service is invoked at the MSC. The MSC notifies the gsmSCF of a supplementary service invocationthe MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION service. This is sent in a TCAP TC-BEGIN primitive. The MSC then awaits a positive or negative acknowledgement from the gsmSCF to the MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION. This is received in a TCAP TC-END primitive,and upon receipt the relationship between the MSC and the gsmSCF is terminated. Similarly, the relationship isterminated at the MSC by the sending from or receipt of a TCAP P-ABORT primitive. This is illustrated inFigure 22.12.2.
MSC gsmSCF
Page 3GSM 09.02 V.5.7.0 TS 101 046 V 5.0.1 (1997-08)
Figure 22.12.2 Process SS_Invocation_Notify_MSC (sheet 1 of 1)
Process in the MSC tonotify the gsmSCF that theuser has invoked asupplementary service (CD, ECT or MPTY)
Process SS_Invocation_No tify_MSC SSIN_M1(1)
Signals to /from the leftare to/from the SS handler in the MSC;signals to/from the rightare to/from the gsmSCF
Idle
Notify SSinvocation
MAP_OPEN_req,MAP_SS_INVOCATIO N _NOTIFY_req,MAP_DE LIMITER_req
Receive_O pen_Cnf
Section 24.1
Wa it_For_SCF_Response
MAP_CLOSE_ind,MAP_P_ABORT_ind,MAP_U_ABORT_ind
Set negative response:
Systemfailure
Notify SSinvocation negative response
Idle
MAP_NOTICE_ind
MAP_CLOSE_req
MAP_SS_INVOCATIO N _NOTIFY_cnf
Check_Conf irmation
Section 24.2
Notify SSinvocation ack
Idle
Notify SSinvocat ion negativeresponse
Idle
Abort
Idle
OK
OK
Provider error ,User error,Data error
Vr, Error
Page 4GSM 09.02 V.5.7.0 TS 101 046 V 5.0.1 (1997-08)
22.12.3 Procedures in the gsmSCF
Figure 22.12.3 Process SS_Invocation_Notify_gsmSCF (sheet 1 of 1)
Process in the gsmSCF toreceive a notification that an SS(CD, ECT or MPT) has been invoked
Process SS_Invocation_Notify_gsmSCF SSINSCF1(1)
Signals to/from the leftare to/from the VMSC;signals to/from the rightare to/from the service logicin the gsmSCF
Idle
Receive_Open_Ind
Section 24.1
Wait_For_Service_Indication
MAP_P_ABORT_ind
Idle
MAP_SS_INVOCATION_NOTIFY_ind
Notify SSinvocation
Wait_For_Service_Logic_
Response
Notify SSinvocationack
MAP_SS_INVOCATION_NOTIFY_rsp
MAP_CLOSE_req
Idle
Notify SSinvocationnegativeresponse
Set error
MAP_NOTICE_ind
MAP_CLOSE_req
Idle
Idle
OK Vr, Error
Page 5GSM 09.02 V.5.7.0 TS 101 046 V 5.0.1 (1997-08)
Upon receiving notification of the supplementary service invocation via the MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION service, the gsmSCF analyses the received information. If the gsmSCFunderstands the information sent via the the MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION service then it returns a positive acknowledgement to the MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION, indicating the success of the service. This is returned in a TCAP TC-ENDprimitive, using the basic end procedure.
Otherwise, a negative acknowledgement to the MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION is returned. This is also returned in a TCAP TC-END primitive, again using the basic endprocedure. The gsmSCF TCAP service may also choose to abort the relationship to the MSC by sending a TCAP P-ABORT primitive. It will immediately terminate processing of a MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION should a TCAP P-ABORT primitive be received from the MSC. This isillustrated in Figure 22.12.3.
CHANGE REQUEST No.A031r2
Technical Specification GSM 09.78 version 6.1.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic") [ x ]
Status at SMG [#27 ]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [R97] Work item: CAMEL Phase 2
Other phase(s) affected: [ ] If yes, linked CR(s):
Proposed change affects: SIM [ ] ME [ ] Network [ ]
Source: SMG3 Tdoc SMG3 98C494 Date: 24-7-98
Subject: Corrections on GSM 09.78
Category: F - Correction [ x]
A - Corresponds to a Phase 2 correction [ ]
B - Addition of Feature [ ]
C - Functional modification of Feature [ ]
D - Editorial modification [ ]
Reason for change:
Modification of section 9.18 in order to clarify handling of Furnish Charging Information operation.
Sections affected, and additional explanation of details of change (if needed):
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects(possibly):
MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications []
Attached CRs?:
Cross Phase Compatibility:
Change affects operation of:
Other comments:
CR on GSM 09.78 v6.1.0 July 1998
9.18 FurnishChargingInformation procedure
9.18.1 General description
This operation is used to send charge related information to a logical call record. This logical call record is CAMELspecific. The first FCI of a call leg leads to the generation of a logical call record. Receipt of subsequent FCIs on thesame leg shall overwrite the contents of the logical call record. When additional FCIs are to be used an EDP-R shallbe armed in order to be able to apply FCI before the termination of the call record generation.
If an FCI operation is received for the called party when the gsmSSF is in state ‘Monitoring’, or is suspended in oneof the following DPs then the charging information shall be included in the logical call record for the leg that hasbeen or is to be established:
- Collected_Info,
- O_Answer,
- Terminating_Attempt_Authorised, or
- T_Answer
If an FCI operation is received for the called party when the gsmSSF is suspended in any other DP then the charginginformation shall be included in the logical call record created for the last failed or disconnected called party.
9.18.1.1 Parameters
- FCIBillingChargingCharacteristics:This parameter contains the following sub-parameters;
- FCIBCCCAMELsequence1:This parameter contains the following sub-parameters;
- FreeFormatDataThis parameter indicates free-format billing and/or charging characteristics.
- PartyToChargeThis parameter indicates the party to bill and/or charge.
9.18.2 Spare
CHANGE REQUEST No. A033r1
Technical Specification GSM 09.78, version 6.1.0
Submitted to SMG for approval without presentation ("non-strategic") [ ]
with presentation ("strategic") [ x ]
Status at SMG [#27]: Approved [ ] Rejected [ ] Postponed [ ]
Phase 1: [ ] Phase 2: [ ] Phase 2+: [R97] Work item: CAMEL R97
Other phase(s) affected [ ] If yes, linked CR(s):
Proposed change affects: SIM [ ] ME [ ] Network [x]
Source: SMG3 Tdoc SMG3 98C573 Date: September 1998
Subject: Support Of CAMEL Phase 2 In GSM 09.78
Category: F - Correction [x]A - Corresponds to a phase 2 correction [ ]B - Addition of Feature [ ]C - Functional modification of Feature [ ]D - Editorial modification [ ]
Reason for change:
- correction of ASN.1 errors
- introduction of changes requested by SPS3.
Sections affected, and additional explanation of details of change (if needed):
Section 4.4.2: Removal of Result-NL handling,
Section 6: Correction of reference; addition of rule for BER encoding of constrained octet string,
Section 6.3: CalledPartyBusy changed to Busy
Section 6.3: ASN.1 definitions of charging parameters changed,
Section 6.3: sending and receiving side leg definitions changed,
Section 6.3: sendCalculationToSCPIndication removed, for CS2 compatibility,
Section 6.3: extensions definition error corrected,
Section 6.3: minimumNbOfDigits and maxNbOfDigits changed in CollectedInfo to align with the maximumnumber of digits that can be sent to the gsmSCF, in field ReceivedInformationArg,
Section 6.3: notReachable DP support removed,
Section 6.3: minDigitsLength changed to 2, so that field Digits can carry generic numbers,
Section 9.3: sendCalculationToSCP parameter removed for CS2 alignment,
Section 9.4: sendCalculationToSCP parameter removed for CS2 alignment,
Section 9.17: notReachable DP support removed,
Section 9.25: notReachable DP support removed.
Attached revised pages:
If other core Specifications are affected, necessary (and attached) Joint CRs:
Affects (possibly): MS Test Specifications [ ] BSS Test Specifications [ ] O&M Specifications [ ]Attached CRs?:
Cross Phase Compatibility:
Other comments:
GSM 09.78 Version 6.1.0 Release 1997 2
---------------- next modified section ----------------
6 Abstract syntax of the CAPThis Clause specifies the abstract syntax for the CAP version 1, using ASN.1 as defined in CCITT RecommendationX.208 [9] and ITU-T Recommendations X.680 [18], X.681 [19], X.682 [20] and X.683 [21].
The encoding rules which are applicable to the defined abstract syntax are the Basic Encoding Rules for ASN.1, definedin CCITT Recommendation X.209 [10] and ITU-T Recommendation X.690 [22] with the restrictions as described inITU-T Recommendation Q.773 [6], § 4.1.1, modified by ETS 300 287 [3]. Additional encodings are cited forparameters used in existing ISUP (ETS 300 356-1 [4]) and DSS1 (ETS 300 403-1 [5]) standards.
For the ISUP and DSS1 parameters used in the CAP, only the coding of the parameter value is coded as defined in ISUPor DSS1. The DSS1/ISUP defined parameter identifiers are removed and replaced by the CAP defined parameteridentifiers.
Where possible existing data types from the CS1 ETSI Core INAP (ETS 300 374-1 [14]) and MAP (ETS 300 974 [15])standards have been used. For future compatibility where parameter mappings in CS1 ETSI Core INAP (ETS 300 374-1[14]) are not defined for functions imported from CS1 ETSI Core INAP, but parameter mappings are defined in CS2ETSI Core INAP [30] then the parameter mappings in CS2 ETSI Core INAP [30] shall be used.
OCTET STRING fields shall be encoded as primitives using the ASN.1 Basic Encoding Rules defined in CCITTRecommendation X.209 [10] and ITU-T Recommendation X.690 [22] with the restrictions as described in ITU-TRecommendation Q.773 [6], § 4.1.1, modified by ETS 300 287 [3].
The mapping of OPERATION and ERROR to TCAP components is defined in ITU-T Recommendation Q.773 [6]modified by ETS 300 287 [3]. The class of an operation is not stated explicitly but is specified in the ASN.1OPERATION MACRO, as follows:
class 1: both RESULT and ERRORS appears in the ASN.1 OPERATION MACRO definition;
class 2: only ERRORS appears in the ASN.1 OPERATION MACRO definition;
class 3: only RESULT appears in the ASN.1 OPERATION MACRO definition;
class 4: neither RESULT nor ERRORS appears in the ASN.1 OPERATION MACRO definition.
---------------- first modified section ----------------
4.4.2 Quality of service parameters
The class (class 0 or class 1) of SCCP is set as required by the application. However class 1 shall be requested by anyapplication that can send more than 1 TCAP message to its peer (consecutive TR-CONTINUE) before receiving aresponse from its peer (TR-CONTINUE or TR-END).
On receipt of a TC-RESULT-NL indication, the TC-USER shall request the transfer of a reject component using TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter).
RESULT_NL should not be used. However, if RESULT_NL is used by the application (and thus segmentation isneeded) class 1 shall be set by the application.
According to Q.771, TC imposes no limitation on the number of segments. However if the peer TC users are certain thatthe Network Service used supports segmentation and reassembly of user data, the TC_RESULT_NL (RR_NL) facility isnot necessary and should be avoided.
The return option may be used if requested by the application (Network Operator to determine).
GSM 09.78 Version 6.1.0 Release 1997 3
---------------- next modified section ----------------
6.3 Data types
CAP-DataTypes {ccitt(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1)modules(3)cap-datatypes(52) version2(1)}
-- This module contains the type definitions for the CAP v.2 data types.
DEFINITIONS IMPLICIT TAGS ::=BEGIN
IMPORTS
-- CAP Classes
EXTENSION,ExtensionField
FROM CAP-Classes {ccitt(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1)modules(3) cap-classes(54) version2(1)}
-- This module contains the class definitions for CAP v.2.
-- CS1 Parameters
CallingPartysCategory,Duration,HighLayerCompatibility,Integer4,InvokeID,LegID,MiscCallInfo,MonitorMode,RedirectionInformation,ServiceKey
FROM Core-INAP-CS1-DataTypes { ccitt(0) identified-organization(4) etsi(0) inDomain(1)in-network(1) modules(0) cs1-datatypes(2) version1(0)}
BothwayThroughConnectionIndFROM Core-INAP-cs2-DataTypes { ccitt(0) identified-organization(4) etsi(0) inDomain(1)in-network(1) cs-2(20) modules(0) cs2-datatypes(0) version1(0)}
IMSI,ISDN-AddressString,Ext-BasicServiceCode
FROM MAP-CommonDataTypes { ccitt(0) identified-organization(4) etsi(0) mobileDomain(0)gsm-Network(1) modules(3) map-CommonDataTypes(18) version3(3)}
LocationInformation,SubscriberState
FROM MAP-MS-DataTypes { ccitt(0) identified-organization(4) etsi(0) mobileDomain(0)gsm-Network(1) modules(3) map-MS-DataTypes(11) version3(3)}
CallReferenceNumber,SuppressionOfAnnouncement
FROM MAP-CH-DataTypes { ccitt(0) identified-organization(4) etsi(0) mobileDomain(0)gsm-Network(1) modules(3) map-CH-DataTypes(13) version3(3)};
-- TYPE DEFINITIONS FOR CAP v.2 DATA TYPES FOLLOW
-- Argument Data Types
ApplyChargingArg ::= SEQUENCE {AchBillingChargingCharacteristics [0] AChBillingChargingCharacteristics,
sendCalculationToSCPIndication [1] BOOLEAN DEFAULT FALSE,partyToCharge [2] SendingSideID DEFAULT leg1,extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL, ...
}
-- The sendCalculationToSCPIndication parameter indicates that ApplyChargingReport operations-- are expected from the gsmSSF. This parameter shall always be set to true. -- The partyToCharge-- parameter indicates the party in the call to which the ApplyCharging-- operation should be-- applied.
ApplyChargingReportArg ::= CallResult
GSM 09.78 Version 6.1.0 Release 1997 4
AssistRequestInstructionsArg ::= SEQUENCE {correlationID [0] CorrelationID,iPSSPCapabilities [2] IPSSPCapabilities,extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL, ...
}
-- OPTIONAL denotes network operator specific use. The value of the correlationID may be the-- Called Party Number supplied by the initiating gsmSSF.
CallInformationReportArg ::= SEQUENCE {requestedInformationList [0] RequestedInformationList,extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL,legID [3] ReceivingSideID OPTIONAL,
...}
CallInformationRequestArg ::= SEQUENCE {requestedInformationTypeList [0] RequestedInformationTypeList,extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL,legID [3] SendingSideID OPTIONAL,
...}
CancelArg ::= CHOICE {invokeID [0] InvokeID,allRequests [1] NULL
}
ConnectArg ::= SEQUENCE {destinationRoutingAddress [0] DestinationRoutingAddress,alertingPattern [1] AlertingPattern OPTIONAL,originalCalledPartyID [6] OriginalCalledPartyID OPTIONAL,extensions [10] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL,genericNumbers [14] GenericNumbers OPTIONAL,callingPartysCategory [28] CallingPartysCategory OPTIONAL,redirectingPartyID [29] RedirectingPartyID OPTIONAL,redirectionInformation [30] RedirectionInformation OPTIONAL,suppressionOfAnnouncement [55] SuppressionOfAnnouncement OPTIONAL,oCSIApplicable [56] OCSIApplicable OPTIONAL,...}
ConnectToResourceArg ::= SEQUENCE {resourceAddress CHOICE {
ipRoutingAddress [0] IPRoutingAddress,none [3] NULL},
extensions [4] SEQUENCE SIZE(1..numOfExtensions) OF ExtensionField OPTIONAL,serviceInteractionIndicatorsTwo [7] ServiceInteractionIndicatorsTwo OPTIONAL,
...}
EstablishTemporaryConnectionArg ::= SEQUENCE {assistingSSPIPRoutingAddress [0] AssistingSSPIPRoutingAddress,correlationID [1] CorrelationID OPTIONAL,scfID [3] ScfID OPTIONAL,extensions [4] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL,serviceInteractionIndicatorsTwo [7] ServiceInteractionIndicatorsTwo OPTIONAL,
...}
EventReportBCSMArg ::= SEQUENCE {eventTypeBCSM [0] EventTypeBCSM,eventSpecificInformationBCSM [2] EventSpecificInformationBCSM OPTIONAL,legID [3] ReceivingSideID OPTIONAL,miscCallInfo [4] MiscCallInfo DEFAULT {messageType request},extensions [5] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL,...}
FurnishChargingInformationArg ::= FCIBillingChargingCharacteristics
GSM 09.78 Version 6.1.0 Release 1997 5
InitialDPArg ::= SEQUENCE {serviceKey [0] ServiceKey,calledPartyNumber [2] CalledPartyNumber OPTIONAL,callingPartyNumber [3] CallingPartyNumber OPTIONAL,callingPartysCategory [5] CallingPartysCategory OPTIONAL,iPSSPCapabilities [8] IPSSPCapabilities OPTIONAL,locationNumber [10] LocationNumber OPTIONAL,originalCalledPartyID [12] OriginalCalledPartyID OPTIONAL,extensions [15] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL,highLayerCompatibility [23] HighLayerCompatibility OPTIONAL,additionalCallingPartyNumber [25] AdditionalCallingPartyNumber OPTIONAL,bearerCapability [27] BearerCapability OPTIONAL,eventTypeBCSM [28] EventTypeBCSM OPTIONAL,redirectingPartyID [29] RedirectingPartyID OPTIONAL,redirectionInformation [30] RedirectionInformation OPTIONAL,iMSI [50] IMSI OPTIONAL,subscriberState [51] SubscriberState OPTIONAL,locationInformation [52] LocationInformation OPTIONAL,ext-basicServiceCode [53] Ext-BasicServiceCode OPTIONAL,callReferenceNumber [54] CallReferenceNumber OPTIONAL,mscAddress [55] ISDN-AddressString OPTIONAL,calledPartyBCDNumber [56] CalledPartyBCDNumber OPTIONAL,timeAndTimezone [57] TimeAndTimezone OPTIONAL,gsm-ForwardingPending [58] NULL OPTIONAL,...
}
-- If iPSSPCapabilities is not present then this denotes that a colocated gsmSRF is not-- supported by the gsmSSF. If present, then the gsmSSF supports a colocated gsmSRF capable-- of playing announcements via elementaryMessageIDs and variableMessages, the playing of-- tones and the collection of DTMF digits. Other supported capabilities are explicitly-- detailed in the IPSSPCapabilities parameter itself.
PlayAnnouncementArg ::= SEQUENCE {informationToSend [0] InformationToSend,disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE,requestAnnouncementComplete [2] BOOLEAN DEFAULT TRUE,extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL, ...
}
PromptAndCollectUserInformationArg ::= SEQUENCE {collectedInfo [0] CollectedInfo,disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE,informationToSend [2] InformationToSend OPTIONAL,extensions [3] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL, ...
}
ReceivedInformationArg ::= CHOICE {digitsResponse [0] Digits}
ReleaseCallArg ::= Cause
RequestReportBCSMEventArg ::= SEQUENCE {bcsmEvents [0] SEQUENCE SIZE (1..numOfBCSMEvents) OF BCSMEvent,extensions [2] SEQUENCE SIZE (1..numOfExtensions) OF
ExtensionField OPTIONAL,...}
-- Indicates the BCSM related events for notification.
ResetTimerArg ::= SEQUENCE {timerID [0] TimerID DEFAULT tssf,timervalue [1] TimerValue,extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL, ...
}
SendChargingInformationArg ::= SEQUENCE {sCIBillingChargingCharacteristics [0] SCIBillingChargingCharacteristics,partyToCharge [1] SendingSideID,extensions [2] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL, ...
}
GSM 09.78 Version 6.1.0 Release 1997 6
SpecializedResourceReportArg ::= NULL
-- Common Data Types
AChBillingChargingCharacteristics ::= OCTET STRING (SIZE(minAChBillingChargingLength .. maxAChBillingChargingLength)) (CONSTRAINED BY {-- shall be the result of the BER-encoded value of the type CAMEL-AChBillingChargingCharacteristics --})
-- The AChBillingChargingCharacteristics parameter specifies the charging related information to-- be provided by the gsmSSF and the conditions on which this information has to be reported back-- to the gsmSCF with the ApplyChargingReport operation. The value of the-- AchBillingChargingCharacteristics of type OCTET STRING carries a value of the ASN.1 data type :-- CAMEL-AchBillingChargingCharacteristics. The normal encoding rules are used to encode this-- value.-- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error.
AChBillingChargingCharacteristics ::= CHOICE { timeDurationCharging [50] SEQUENCE { maxCallPeriodDuration [0] INTEGER (1..864000), releaseIfdurationExceeded [1] ReleaseIfDurationExceeded OPTIONAL, tariffSwitchInterval [2] INTEGER (1..86400) OPTIONAL } }
-- The AChBillingChargingCharacteristics parameter specifies the charging related information to be-- provided by the gsmSSF and the conditions on which this information has to be reported back to-- the gsmSCF with the ApplyChargingReport operation. tariffSwitchInterval is measured in 1 second-- units. maxCallPeriodDuration is measured in 100 millisecond units
AdditionalCallingPartyNumber ::= Digits
-- Indicates the Additional Calling Party Number.
AlertingPattern ::= OCTET STRING (SIZE (31))
-- The encoding of the last octet of this parameter is as defined in GSM 09.02 [Reference 15].-- Only the last octet is used. The remaining octets shall be sent with all bits set to zero.-- The receiving side shall ignore the first two octets.
AOCBeforeAnswer ::= SEQUENCE {aOCInitial [0] CAI-GSM0224,aOCSubsequent [1] AOCSubsequent OPTIONAL}
AOCSubsequent ::= SEQUENCE {cAI-GSM0224 [0] CAI-GSM0224 ,tariffSwitchInterval [1] INTEGER (1..86400) OPTIONAL}
-- tariffSwitchInterval is measured in 1 second units
ApplicationTimer ::= INTEGER (0..2047)
-- Used by the gsmSCF to set a timer in the gsmSSF. The timer is in seconds.
AssistingSSPIPRoutingAddress ::= Digits
-- Indicates the destination address of the gsmSRF for the assist procedure.
BCSMEvent ::= SEQUENCE {eventTypeBCSM [0] EventTypeBCSM,monitorMode [1] MonitorMode,legID [2] LegID OPTIONAL,dPSpecificCriteria [30] DPSpecificCriteria OPTIONAL}
-- Indicates the BCSM Event information for monitoring.
BearerCapability ::= CHOICE {bearerCap [0] OCTET STRING (SIZE (2..maxBearerCapabilityLength))}
-- Indicates the type of bearer capability connection to the user. For bearerCap, the value as-- described in ISUP (ETS 300 356-1 [4], User Service Information) shall be used.
CAI-GSM0224 ::= SEQUENCE {e1 [0] INTEGER (0..8191) OPTIONAL,e2 [1] INTEGER (0..8191) OPTIONAL,e3 [2] INTEGER (0..8191) OPTIONAL,e4 [3] INTEGER (0..8191) OPTIONAL,e5 [4] INTEGER (0..8191) OPTIONAL,e6 [5] INTEGER (0..8191) OPTIONAL,
GSM 09.78 Version 6.1.0 Release 1997 7
e7 [6] INTEGER (0..8191) OPTIONAL}
-- Indicates Charge Advice Information to the Mobile Station. For information regarding-- parameter usage, refer to GSM 02.40 [26].
CalledPartyBCDNumber ::= OCTET STRING (SIZE (minCalledPartyBCDNumberLength ..maxCalledPartyBCDNumberLength)
-- Indicates the Called Party Number, including service selection information. Refer to GSM-- 04.08 [25] for encoding. This data type carries only the “type of number“, “numbering plan-- identification“ and “number digit“ fields defined in [25]; it does not carry the “called-- party BCD number IEI“ or “length of called party BCD number contents“.
CalledPartyNumber ::= OCTET STRING (SIZE (minCalledPartyNumberLength .. maxCalledPartyNumberLength))
-- Indicates the Called Party Number. Refer to ETS 300 356-1 [4] for encoding.
CallingPartyNumber ::= OCTET STRING (SIZE (minCallingPartyNumberLength .. maxCallingPartyNumberLength))
-- Indicates the Calling Party Number. Refer to ETS 300 356-1 [4] for encoding.
CallResult ::= OCTET STRING (SIZE (minCallResultLength .. maxCallResultLength)) (CONSTRAINED BY {-- shall be the result of the BER-encodedvalue of type CAMEL-CallResult --})
-- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error.
CallResult ::= CHOICE { timeDurationChargingResult [50] SEQUENCE { partyToCharge [0] ReceivingSideID, timeInformation [1] TimeInformation, callActive [2] BOOLEAN DEFAULT TRUE } }
-- This parameter provides the gsmSCF with the charging related information previously requested-- using the ApplyCharging operation. This shall include the partyToCharge parameter as-- received in the related ApplyCharging operation to correlate the result to the request.
CAMEL-AChBillingChargingCharacteristics ::= CHOICE { timeDurationCharging [0] SEQUENCE { maxCallPeriodDuration [0] INTEGER (1..864000), releaseIfdurationExceeded [1] ReleaseIfDurationExceeded OPTIONAL, tariffSwitchInterval [2] INTEGER (1..86400) OPTIONAL } }-- tariffSwitchInterval is measured in 1 second units.-- maxCallPeriodDuration is measured in100 millisecond units
CAMEL-CallResult ::= CHOICE { timeDurationChargingResult [0] SEQUENCE { partyToCharge [0] ReceivingSideID, timeInformation [1] TimeInformation, callActive [2] BOOLEAN DEFAULT TRUE } }
CAMEL-FCIBillingChargingCharacteristics ::= CHOICE{ fCIBCCCAMELsequence1 [0] SEQUENCE { freeFormatData [0] OCTET STRING (SIZE (minFCIBillingChargingDataLength.. maxFCIBillingChargingDataLength)), partyToCharge [1] SendingSideID DEFAULT leg1 } }
CAMEL-SCIBillingChargingCharacteristics ::= CHOICE { aOCBeforeAnswer [0] AOCBeforeAnswer, aOCAfterAnswer [1] AOCSubsequent }
Cause ::= OCTET STRING (SIZE (minCauseLength .. maxCauseLength))
-- Indicates the cause for interface related information. Refer to the ETS 300 356-1 [4] Cause-- parameter for encoding. For the use of Cause and Location values refer to Q.850.-- Shall only include the cause value.
CollectedDigits ::= SEQUENCE {minimumNbOfDigits [0] INTEGER (1..12716) DEFAULT 1,
GSM 09.78 Version 6.1.0 Release 1997 8
maximumNbOfDigits [1] INTEGER (1..12716),endOfReplyDigit [2] OCTET STRING (SIZE (1..2)) OPTIONAL,cancelDigit [3] OCTET STRING (SIZE (1..2)) OPTIONAL,startDigit [4] OCTET STRING (SIZE (1..2)) OPTIONAL,firstDigitTimeOut [5] INTEGER (1..127) OPTIONAL,interDigitTimeOut [6] INTEGER (1..127) OPTIONAL,errorTreatment [7] ErrorTreatment DEFAULT stdErrorAndInfo,interruptableAnnInd [8] BOOLEAN DEFAULT TRUE,voiceInformation [9] BOOLEAN DEFAULT FALSE,voiceBack [10] BOOLEAN DEFAULT FALSE}
-- The use of voiceBack and the support of voaice recognition via voiceInformation is-- network operator specific. The endOfReplyDigit, cancelDigit, and startDigit parameters-- have been designated as OCTET STRING, and are to be encoded as BCD, one digit per octet-- only, contained in the four least significant bits of each OCTET.-- The usage is service dependent.
CollectedInfo ::= CHOICE {collectedDigits [0] CollectedDigits}
CorrelationID ::= Digits
-- used by gsmSCF for correlation with a previous operation. Refer to clauses 9.5 and 9.15-- for a description of the procedures associated with this parameter.
DateAndTime ::= OCTET STRING (SIZE(7))
-- DateAndTime is BCD encoded. The year digit indicating millenium occupies bits 0-3 of-- the first octet, and the year digit indicating century occupies bits 4-7 of the first octet.-- The year digit indicating decade occupies bits 0-3 of the second octet, whilst the digit-- indicating the year within the decade occupies bits 4-7 of the second octet.-- The most significant month digit occupies bits 0-3 of the third octet, and the least-- significant month digit occupies bits 4-7 of the third octet.-- The most significant day digit occupies bits 0-3 of the fourth octet, and the least significant-- day digit occupies bits 4-7 of the fourth octet.-- The most significant hours digit occupies bits 0-3 of the fifth octet, and the least significant-- digit occupies bits 4-7 of the fifth octet.-- The most significant minutes digit occupies bits 0-3 of the sixth octet, and the least-- significant digit occupies bits 4-7 of the sixth octet.-- The most significant seconds digit occupies bits 0-3 of the seventh octet, and the least seconds-- significant digit occupies bits 4-7 of the seventh octet.-- For the encoding of digits in an octet, refer to the timeAndtimezone parameter.
DestinationRoutingAddress ::= SEQUENCE SIZE (1) OF CalledPartyNumber
-- Indicates the Called Party Number.
Digits ::= OCTET STRING (SIZE (minDigitsLength .. maxDigitsLength))
-- Indicates the address signalling digits. Refer to the ETS 300 356-1 [4] Generic Number-- and Generic Digits parameters for encoding. The coding of the subfields “NumberQualifier“-- in Generic Number and “Type Of Digits“ in Generic Digits are irrelevant to the CAP, the-- ASN.1 tags are sufficient to identify the parameter. The ISUP format does not allow to-- exclude these subfields, therefor the value is network operator specific.---- The following parameters should use Generic Number:-- AdditionalCallingPartyNumber for InitialDP-- AssistingSSPIPRoutingAddress for EstablishTemporaryConnection-- CorrelationID for AssistRequestInstructions---- The following parameters should use Generic Digits:-- CorrelationID in EstablishTemporaryConnection-- number in VariablePart-- digitsResponse in ReceivedInformationArg-- Note that when CorrelationID is transported in Generic Digits, then the digits shall-- always be BCD encoded.
DPSpecificCriteria ::= CHOICE {applicationTimer [1] ApplicationTimer}
-- The gsmSCF may set a timer in the gsmSSF for the NoAnswer event. If the user does not-- answer the call within the allocated time, the gsmSSF reports the event to the gsmSCF.
ErrorTreatment ::= ENUMERATED {stdErrorAndInfo (0),help (1),repeatPrompt (2)}
-- stdErrorAndInfo means returning the “ImproperCallerResponse“ error in the event of an error
GSM 09.78 Version 6.1.0 Release 1997 9
-- condition during collection of user info.
EventSpecificInformationBCSM ::= CHOICE {routeSelectFailureSpecificInfo [2] SEQUENCE {
failureCause [0] Cause OPTIONAL,...},
oCalledPartyBusyBusySpecificInfo [3] SEQUENCE {busyCause [0]Cause OPTIONAL,...},
oNoAnswerSpecificInfo [4] SEQUENCE {-- no specific info defined—...},
oAnswerSpecificInfo [5] SEQUENCE {-- no specific info defined—...},
oDisconnectSpecificInfo [7] SEQUENCE {releaseCause [0] Cause OPTIONAL,...},
tBusySpecificInfo [8] SEQUENCE {busyCause [0] Cause OPTIONAL,...},
tNoAnswerSpecificInfo [9] SEQUENCE {-- no specific info defined—...},
tAnswerSpecificInfo [10] SEQUENCE {-- no specific info defined—...},
tDisconnectSpecificInfo [12] SEQUENCE {releaseCause [0] Cause OPTIONAL,...},
oNotReachableSpecificInfo [50] SEQUENCE { releaseCause [0] Cause OPTIONAL, ... },tNotReachableSpecificInfo [51] SEQUENCE { releaseCause [0] Cause OPTIONAL, ... }
}
-- Indicates the call related information specific to the event.
EventTypeBCSM ::= ENUMERATED {collectedInfo (2),routeSelectFailure (4),oCalledPartyBusyBusy (5),oNoAnswer (6),oAnswer (7),oDisconnect (9),oAbandon (10),termAttemptAuthorized (12),tBusy (13),tNoAnswer (14),tAnswer (15),tDisconnect (17),tAbandon (18),
oNotReachable (50), tNotReachable (51)
}
-- Values collectedInfo and termAttemptAuthorized can only be-- used for TDPs.
ExtensionField ::= SEQUENCE {type EXTENSION.&id ({SupportedExtensions}),
-- shall identify the value of an EXTENSION typecriticality EXTENSION.&criticalityType DEFAULT ignore,
({SupportedExtensions}{@type}),value [1] EXTENSION.&ExtensionType({SupportedExtensions}{@type})}
-- This parameter indicates an extension of an argument data type. Its content is network-- operator specific
GSM 09.78 Version 6.1.0 Release 1997 10
FCIBillingChargingCharacteristics ::= OCTET STRING (SIZE (minFCIBillingChargingLength .. maxFCIBillingChargingLength)) (CONSTRAINED BY {-- shall be the result of the BER-encodedvalue of type CAMEL-FCIBillingChargingCharacteristics --})FCIBillingChargingCharacteristics ::= CHOICE{ fCIBCCCAMELsequence1 [50] SEQUENCE { freeFormatData [0] OCTET STRING (SIZE (minFCIBillingChargingLength.. maxFCIBillingChargingLength)), partyToCharge [1] SendingSideID DEFAULT leg1 } }
-- This parameter indicates the billing and/or charging characteristics.-- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error.
GenericNumber ::= OCTET STRING (SIZE(minGenericNumberLength..maxGenericNumberLength))
-- Indicates a generic number. Refer to ETS 300 356-1 [4] Generic number for encoding.
GenericNumbers ::= SET SIZE(1..numOfGenericNumbers) OF GenericNumber
InbandInfo ::= SEQUENCE {messageID [0] MessageID,numberOfRepetitions [1] INTEGER (1..127) OPTIONAL,duration [2] INTEGER (0..32767) OPTIONAL,interval [3] INTEGER (0..32767) OPTIONAL}
-- Interval is the time in seconds between each repeated announcement. Duration is the-- total amount of time in seconds, including repetitions and intervals. The end of-- announcement is either the end of duration or numberOfRepetitions, whatever comes-- first. Duration with value 0 indicates infinite duration.
InformationToSend ::= CHOICE {inbandInfo [0] InbandInfo,tone [1] Tone}
IPRoutingAddress ::= CalledPartyNumber
-- Indicates the routing address for the IP.
IPSSPCapabilities ::= OCTET STRING (SIZE (minIPSSPCapabilitiesLength..maxIPSSPCapabilitiesLength))
-- Indicates the gsmSRF resources available. The parameter has two parts, a standard and a-- bilateral part. The standard part indicates capabilities defined as optional in CAP V.2-- that shall be recognised (but not necessarily supported) by a CAP V.2 gsmSCF. The bilateral-- part contains further information that is not specified in this standard, but which is set-- according to bilateral agreements between network operators and/or equipment vendors.-- The last octet of the standard part is indicated by bit 7 being set to 0, otherwise Bit 7 of-- a standard part octet is set to 1 indicating that the standard part continues in the following-- octet. Coding is as follows:--
-- Octet 1 Standard Part for CAP V.2-- Bit Value Meaning-- 0 0 IPRoutingAddress not supported-- 1 IPRoutingAddress supported-- 1 0 VoiceBack not supported-- 1 VoiceBack supported-- 2 0 VoiceInformation not supported, via speech recognition-- 1 VoiceInformation supported, via speech recognition-- 3 0 VoiceInformation not supported, via voice recognition-- 1 VoiceInformation supported, via voice recognition-- 4 0 Generation of voice announcements from Text not supported-- 1 Generation of voice announcements from Text supported-- 5 - Reserved-- 6 - Reserved-- 7 0 End of standard part-- 1 This value is reserved in CAP V.2---- Octets 2 to 4 Bilateral Part: Network operator / equipment vendor specific
LegType ::= OCTET STRING (SIZE(1))leg1 LegType ::= ‘01’Hleg2 LegType ::= ‘02’H
LocationNumber ::= OCTET STRING (SIZE (minLocationNumberLength ..maxLocationNumberLength))
GSM 09.78 Version 6.1.0 Release 1997 11
-- Indicates the Location Number for the calling party. Refer to ETS 300 356-1 [4] for encoding.
MessageID ::= CHOICE {elementaryMessageID [0] Integer4,text [1] SEQUENCE {
messageContent [0] IA5String (SIZE(minMessageContentLength..maxMessageContentLength)),
attributes [1] OCTET STRING (SIZE (minAttributesLength..maxAttributesLength)) OPTIONAL
},elementaryMessageIDs [29] SEQUENCE SIZE (1..numOfMessageIDs) OF Integer4,variableMessage [30] SEQUENCE {
elementaryMessageID [0] Integer4,variableParts [1] SEQUENCE SIZE (1..5) OF VariablePart}
}
-- Use of the text parameter is network operator/equipment vendor specific.
OriginalCalledPartyID ::= OCTET STRING (SIZE (minOriginalCalledPartyIDLength .. maxOriginalCalledPartyIDLength))
-- Indicates the original called number. Refer to ETS 300 356-1 [4] Original Called Number-- for encoding.
OCSIApplicable ::= NULL
-- Indicates that the Originating CAMEL Subscription Information, if present, shall be-- applied on the outgoing call leg created with a Connect operation. For the use of this-- parameter see GSM 03.78 [16].
ReceivingSideID ::= CHOICE {receivingSideID [1] LegType}ReceivingSideID ::= [1] LegType
-- used to identify LegID in operations sent from gsmSSF to gsmSCF
RedirectingPartyID ::= OCTET STRING (SIZE (minRedirectingPartyIDLength .. maxRedirectingPartyIDLength))
-- Indicates redirecting number. Refer to ETS 300 356-1 [4] Redirecting number for encoding.
ReleaseIfDurationExceeded ::= SEQUENCE {tone BOOLEAN DEFAULT FALSE,...,extensions [10] SEQUENCE SIZE(1..numOfExtensions) OF
ExtensionField OPTIONAL}
-- Indicates that the call shall be released, with optional warning tone.RequestedInformationList ::= SEQUENCE SIZE (1..numOfInfoItems) OF RequestedInformation
RequestedInformationTypeList ::= SEQUENCE SIZE (1..numOfInfoItems) OF RequestedInformationType
RequestedInformation ::= SEQUENCE {requestedInformationType [0] RequestedInformationType,requestedInformationValue [1] RequestedInformationValue}
RequestedInformationType ::= ENUMERATED {callAttemptElapsedTime (0),callStopTime (1),callConnectedElapsedTime (2),releaseCause (30)}
RequestedInformationValue ::= CHOICE {callAttemptElapsedTimeValue [0] INTEGER (0..255),callStopTimeValue [1] DateAndTime,callConnectedElapsedTimeValue [2] Integer4,releaseCauseValue [30] Cause}
-- The callAttemptElapsedTimeValue is specified in seconds. The unit for the-- callConnectedElapsedTimeValue is 100 milliseconds.
ScfID ::= OCTET STRING (SIZE (minScfIDLength..maxScfIDLength))
-- defined by network operator. Indicates the SCF identifier.
SCIBillingChargingCharacteristics ::= OCTET STRING (SIZE (minSCIBillingChargingLength .. maxSCIBillingChargingLength)) (CONSTRAINED BY {-- shall be the result of the BER-encodedvalue of type CAMEL-SCIBillingChargingCharacteristics --})
GSM 09.78 Version 6.1.0 Release 1997 12
SCIBillingChargingCharacteristics ::= CHOICE { aOCBeforeAnswer [50] AOCBeforeAnswer, aOCAfterAnswer [51] AOCSubsequent }
-- Indicates AOC information to be sent to a Mobile Station-- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error.
SendingSideID ::= CHOICE {sendingSideID [0] LegType}SendingSideID ::= [0] LegType
-- used to identify LegID in operations sent from gsmSCF to gsmSSF
ServiceInteractionIndicatorsTwo ::= SEQUENCE {bothwayThroughConnectionInd [2] BothwayThroughConnectionInd OPTIONAL}
TimeInformation ::= CHOICE { timeIfNoTariffSwitch [0] TimeIfNoTariffSwitch, timeIfTariffSwitch [1] TimeIfTariffSwitch
}
-- Indicates call duration information
TimeIfNoTariffSwitch ::= INTEGER(0..864000)
-- TimeIfNoTariffSwitch is measured in 100 millisecond intervals
TimeIfTariffSwitch ::= SEQUENCE { timeSinceTariffSwitch [0] INTEGER(0..864000), tariffSwitchInterval [1] INTEGER(1..864000) OPTIONAL
}
-- timeSinceTariffSwitch and tariffSwitchInterval are measured in 100 millisecond intervals
TimerID ::= ENUMERATED {tssf (0)}
-- Indicates the timer to be reset.
TimerValue ::= Integer4
-- Indicates the timer value (in seconds)
TimeAndTimezone ::= OCTET STRING (SIZE(minTimeAndTimezoneLength..maxTimeAndTimezoneLength)
-- Indicates the time and timezone, relative to GMT. This parameter BCD encoded.-- The year digit indicating millenium occupies bits 0-3 of the first octet, and the year-- digit indicating century occupies bits 4-7 of the first octet.-- The year digit indicating decade occupies bits 0-3 of the second octet, whilst the digit-- indicating the year within the decade occupies bits 4-7 of the second octet.-- The most significant month digit occupies bits 0-3 of the third octet, and the least-- significant month digit occupies bits 4-7 of the third octet.-- The most significant day digit occupies bits 0-3 of the fourth octet, and the least-- significant day digit occupies bits 4-7 of the fourth octet.-- The most significant hours digit occupies bits 0-3 of the fifth octet, and the least-- significant hours digit occupies bits 4-7 of the fifth octet.-- The most significant minutes digit occupies bits 0-3 of the sixth octet, and the least-- significant minutes digit occupies bits 4-7 of the sixth octet.-- The most significant seconds digit occupies bits 0-3 of the seventh octet, and the least-- significant seconds digit occupies bits 4-7 of the seventh octet.---- The timezone information occupies the eigth octet. For the encoding of Timezone refer to-- Reference [29], GSM 02.42.---- The BCD digits are packed and encoded as follows:---- Bit 7 6 5 4 | 3 2 1 0-- 2nd digit | 1st digit Octet 1-- 3rd digit | 4th digit Octet 2-- .. ..-- nth digit | n-1th digit Octet m---- 0000 digit 0-- 0001 digit 1-- 0010 digit 2-- 0011 digit 3-- 0100 digit 4-- 0101 digit 5-- 0110 digit 6-- 0111 digit 7
GSM 09.78 Version 6.1.0 Release 1997 13
-- 1000 digit 8-- 1001 digit 9-- 1010 spare-- 1011 spare-- 1100 spare-- 1101 spare-- 1110 spare-- 1101 spare---- where the leftmost bit of the digit is either bit 7 or bit 3 of the octet.
Tone ::= SEQUENCE {toneID [0] Integer4,duration [1] Integer4 OPTIONAL}
-- The duration specifies the length of the tone in seconds, value 0 indicates infinite duration.
VariablePart ::= CHOICE {integer [0] Integer4,number [1] Digits,
-- Generic digitstime [2] OCTET STRING (SIZE(2)),
-- HH:MM, BCD codeddate [3] OCTET STRING (SIZE(4)),
-- YYYYMMDD, BCD codedprice [4] OCTET STRING (SIZE(4))}
-- Indicates the variable part of the message. Time is BCD encoded.-- The most significant hours digit occupies bits 0-3 of the first octet, and the least-- significant digit occupies bits 4-7 of the first octet. The most significant minutes digit-- occupies bits 0-3 of the second octet, and the least significant digit occupies bits 4-7-- of the second octet.---- Date is BCD encoded. The year digit indicating millenium occupies bits 0-3 of the first octet,-- and the year digit indicating century occupies bits 4-7 of the first octet. The year digit-- indicating decade occupies bits 0-3 of the second octet, whilst the digit indicating the year-- within the decade occupies bits 4-7 of the second octet.-- The most significant month digit occupies bits 0-3 of the third octet, and the least-- significant month digit occupies bits 4-7 of the third octet. The most significant day digit-- occupies bits 0-3 of the fourth octet, and the least significant day digit occupies bits 4-7-- of the fourth octet.-- Price is BCD encoded. The digit indicating hundreds of thousands occupies bits 0-3 of the-- first octet, and the digit indicating tens of thousands occupies bits 4-7 of the first octet.-- The digit indicating thousands occupies bits 0-3 of the second octet, whilst the digit-- indicating hundreds occupies bits 4-7 of the second octet. The digit indicating tens occupies-- bits 0-3 of the third octet, and the digit indicating 0 to 9 occupies bits 4-7 of the third-- octet. The tenths digit occupies bits 0-3 of the fourth octet, and the hundredths digit-- occupies bits 4-7 of the fourth octet.---- For the encoding of digits in an octet, refer to the timeAndtimezone parameter---- Definition of range constants
minAChBillingChargingLength INTEGER ::= 5maxAChBillingChargingLength INTEGER ::= 177minAttributesLength INTEGER ::= 2maxAttributesLength INTEGER ::= 10maxBearerCapabilityLength INTEGER ::= 11minCallResultLength INTEGER ::= 12maxCallResultLength INTEGER ::= 24minCalledPartyBCDNumberLength INTEGER ::= 1maxCalledPartyBCDNumberLength INTEGER ::= 41minCalledPartyNumberLength INTEGER ::= 3maxCalledPartyNumberLength INTEGER ::= 12minCallingPartyNumberLength INTEGER ::= 2maxCallingPartyNumberLength INTEGER ::= 10minCauseLength INTEGER ::= 2maxCauseLength INTEGER ::= 2minDigitsLength INTEGER ::= 23maxDigitsLength INTEGER ::= 11minFCIBillingChargingDataLength INTEGER ::= 1 maxFCIBillingChargingDataLength INTEGER ::= 40 minFCIBillingChargingLength INTEGER ::= 15maxFCIBillingChargingLength INTEGER ::= 4049minGenericNumberLength INTEGER ::= 3maxGenericNumberLength INTEGER ::= 11minIPSSPCapabilitiesLength INTEGER ::= 1maxIPSSPCapabilitiesLength INTEGER ::= 4minLocationNumberLength INTEGER ::= 2maxLocationNumberLength INTEGER ::= 10minMessageContentLength INTEGER ::= 1
GSM 09.78 Version 6.1.0 Release 1997 14
maxMessageContentLength INTEGER ::= 127minOriginalCalledPartyIDLength INTEGER ::= 2maxOriginalCalledPartyIDLength INTEGER ::= 10minRedirectingPartyIDLength INTEGER ::= 2maxRedirectingPartyIDLength INTEGER ::= 10minScfIDLength INTEGER ::= 2maxScfIDLength INTEGER ::= 10minSCIBillingChargingLength INTEGER ::= 4maxSCIBillingChargingLength INTEGER ::= 69minTimeAndTimezoneLength INTEGER ::= 8maxTimeAndTimezoneLength INTEGER ::= 8numOfBCSMEvents INTEGER ::= 10numOfExtensions INTEGER ::= 10numOfGenericNumbers INTEGER ::= 5numOfInfoItems INTEGER ::= 4numOfMessageIDs INTEGER ::= 5
END
-- The maxACHBillingChargingLength allows 160 octets for the possible inclusion of extension fields-- of the releaseIfDurationExceeded subparameter.
---------------- next modified section ----------------
9.3 ApplyCharging procedure
9.3.1 General description
This operation is used for interacting from the gsmSCF with the gsmSSF function: CSE control of call duration. TheApplyChargingReport operation provides the feedback from the gsmSSF to the gsmSCF.
The charging scenarios supported by this operation are those given in GSM 02.78 for CSE control of call duration.
9.3.1.1 Parameters
- aChBillingChargingCharacteristics:
This parameter specifies a list of parameters required for CSE control of call duration:
The list may contain:
- timeDurationCharging:
This list contains the following parameters:
- maxCallPeriodDuration:
This parameter specifies the period of time for which a call can progress before an ApplyChargingReportshall be sent to the gsmSCF.
- releaseIfdurationExceeded:
This parameter specifies the action to be taken at the gsmSSF when the duration specified above has beenreached. If the parameter is present, then the call is released.
- ToneIf the parameter is present, then a warning tone is played before the call is released.
- tariffSwitchInterval:
This parameter indicates to the gsmSSF the time duration until the next tariff switch. The measurement of theelapsed tariff switch period commences commences immediately upon successful execution of this operation.
- sendCalculationToSCPIndication:
This parameter indicates that ApplyChargingReport operations (at least one at the end of the connectionconfiguration charging process) are expected from the gsmSSF. This parameter is always set to TRUE.
- partyToCharge:
GSM 09.78 Version 6.1.0 Release 1997 15
This parameter indicates a party in the call.
9.3.2 Spare
9.3.3 Responding entity (gsmSSF)
9.3.3.1 Normal procedure
gsmSSF preconditions:
(1) A control relationship exists between the gsmSSFand the gsmSCF.
(2) The gsmSSF is in one of the following states:
“Waiting for Instructions“; or
“Waiting for End of User Interaction“; or
“Waiting for End of Temporary Connection”; or
“Monitoring”
SSF postcondition:
(1) No gsmSSF state transition
On receipt of this operation, the gsmSSF sets the charging data using the information elements included in the operation.
The gsmSSF will start monitoring for the Answer event upon receipt of the ApplyCharging operation if Answer has notalready been received on an outgoing connection to a Called Party, a Temporary Connection or a connection to agsmSRF. Upon subsequent detection of the Answer event on the outgoing connection charging is started. If the Answerevent has been received from an outgoing connection already when the ApplyCharging operation is received thencharging starts immediately.
Upon release of an outgoing conection to the Called Party, the Temporary Connection or the gsmSRF connection anyindication of Answer event receipt on the outgoing connection is cleared i.e. set to Answer event not received.
9.3.3.2 Error handling
MissingParameter: This error is indicated if the “sendCalculationToSCPIndication“ is not provided.
UnexpectedDataValue: This error is indicated if the “sendCalculationToSCPIndication“ is set to FALSE.
TaskRefused: In addition to the generic error handling noted below, this error shall be indicated when:
- a previously received call period duration is pending,
- a tariffSwitchInterval is indicated when a previously received tariffSwitchInterval is pending.
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services used for reportingoperation errors are described in Clause 10.
GSM 09.78 Version 6.1.0 Release 1997 16
---------------- next modified section ----------------
9.4 ApplyChargingReport procedure
9.4.1 General description
This operation is used by the gsmSSF to report charging related information to the gsmSCF as requested by the gsmSCFusing the ApplyCharging operation. A report shall be made either when a call disconnection event is detected by thegsmSSF or when the gsmSSF detects that the call period duration indicated in parameter maxCallPeriodDuration(received in ApplyCharging operation) has been reached.
9.4.1.1 Parameters
- CallResult:This parameter provides the SCF with the charging related information previously requested using theApplyCharging operation with its “sendCalculationToSCPIndication“ parameter set to TRUE. The “CallResult“is a list, and can contain the following parameters:
- timeDurationChargingResult
This is a list, and can contain the following parameters:
- timeInformationThis is a choice of the following parameters:
- timeIfNoTariffSwitchThis parameter will be present if no tariff switch has ocurred since the detection of Answer for theconnection to the Called Party, Temporary Connection or SRF connection, otherwise it will be absent.If present, then the elapsed time since detection of Answer is reported.
- timeIfTariffSwitchThis parameter will be present if a tariff switch has ocurred since the detection of Answer for theconnection to the Called Party, Temporary Connection or SRF connection, otherwise it will be absent.If present, then the parameter may contain the following information:
- timeSinceLastTariffSwitchThe elapsed time since detection of the last tariff switch is reported.
- tariffSwitchIntervalThis parameter is present only if a tariff switch was detected for the connection to the Called Party,the temporary connection or the gsmSRF connection in the reported call period.If present the time interval between either the detection of the Answer event or the previoustariff switch (whichever of these events was last detected) and the last tariff switch is reported.
- partyToCharge
The “partyToCharge“ parameter as received in the related ApplyCharging operation or deduced from thedefault value,to correlate the result to the request.
- CallActive
This parameter indicates whether the call is still active or has been released.
9.4.2 Invoking entity (gsmSSF)
9.4.2.1 Normal procedure
gsmSSF preconditions:
(1) A relationship exists between the gsmSSF and the gsmSCF.
GSM 09.78 Version 6.1.0 Release 1997 17
(2) A charging event has been detected that was requested by the gsmSCF via an ApplyCharging operation or aCalled Party, Temporary Connection or SRF disconnection event has occured.
gsmSSF postconditions:
(1) If release of the call has occurred because the allowed call duration has been reached:
- All outstanding EDPs shall be disarmed,
- ApplyChargingReport shall be sent to gsmSCF followed by any outstanding CallInformationReports,if applicable,
- The gsmSSF shall transit to the ‘Idle’ state
(2) If release of the call has occurred but not because the allowed call duration has been reached:
- If there are any outstanding EDPs or other reports then the gsmSSF shall remain in the same state, else
- The gsmSSF shall transit to the ‘Idle’ state
This operation is invoked if a charging event has been detected that was requested by the gsmSCF.
9.4.2.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services used for reportingoperation errors are described in Clause 10.
9.4.3 Spare
---------------- next modified section ----------------
9.17 EventReportBCSM procedure
9.17.1 General description
This operation is used to notify the gsmSCF of a call related event previously requested by the gsmSCF in anRequestReportBCSMEvent operation. The monitoring of more than one event could be requested with aRequestReportBCSMEvent operation, but each of these requested events is reported in a separate EventReportBCSMoperation.
9.17.1.1 Parameters
- eventTypeBCSM:This parameter specifies the type of event that is reported.
- eventSpecificInformationBCSM:This parameter indicates the call related information specific to the event.
For RouteSelectFailure it will contain the “FailureCause“, if available.
For O- or T-Busy it will contain the “BusyCause“, if available.
For O- or T-NoAnswer it will be empty.
For O- or T-Answer it will be empty.
For O- or T-Disconnect it will contain the “releaseCause“, if available.
GSM 09.78 Version 6.1.0 Release 1997 18
For O- and T-NotReachable it will contain the “releaseCause“, if available.
- legID:This parameter indicates the party in the call for which the event is reported. gsmSSF will use the option“receivingSideID“ only.
- receivingSideID:
If not included, the following defaults are assumed:
“legID“ = 1 for the events O-Abandon and T-Abandon,
“legID“ = 2 for the events RouteSelectFailure, O-CalledPartyBusyBusy, O-NoAnswer, O-Answer, O-NotReachable, T-CalledPartyBusyBusy, T-NoAnswer, and T-Answer and T-NotReachable.
The “legID“ parameter shall always be included for the events O-Disconnect and T-Disconnect.
- miscCallInfo:This parameter indicates DP related information.
- messageType:This parameter indicates whether the message is a request, i.e. resulting from a RequestReportBCSMEventwith “monitorMode“ = “interrupted“, or a notification, i.e. resulting from a RequestReportBCSMEvent with“monitorMode“ = “notifyAndContinue“.
9.17.2 Invoking entity (gsmSSF)
9.17.2.1 Normal procedure
gsmSSF preconditions:
(1) The gsmSSF shall be in the state “Monitoring“; or the gsmSSF may be in state “Waiting for Instructions“ if theDisconnect DP is armed and encountered; or the gsmSSF may be in any state if the Abandon DP is armed andencountered.
(2) The BCSM proceeds to an EDP that is armed.
gsmSSF postconditions:
(1) The gsmSSF stays in the state “Monitoring“ if the message type was notification and there are still EDPs armedor a CallInformationReport or ApplyChargingReport requested.
(2) The gsmSSF moves to the state “Idle“ if the message type was notification and there are no more EDPs armed, orno CallInformationReport or ApplyChargingReport is requested.
(3) The gsmSSF moves to the state “Waiting for Instructions“ if the message type was request. Call processing isinterrupted.
If a EDP-R is met that causes the release of the related leg all EDPs related to that leg are disarmed and the event isreported via EventReportBCSM.
9.17.2.2 Error handling
In case the message type is request, on expiration of TSSF before receiving any operation, the gsmSSF aborts theinteraction with the gsmSCF and instructs the GMSC/MSC to handle the call according to the Default Call Handlingparameter of the valid CSI.
GSM 09.78 Version 6.1.0 Release 1997 19
Operation related error handling is not applicable, due to class 4 operation.
9.17.3 Spare
---------------- next modified section ----------------
9.25 RequestReportBCSMEvent procedure
9.25.1 General description
This operation is used to request the gsmSSF to monitor for a call-related event (e.g., BCSM events such as busy or noanswer), then send a notification back to the gsmSCF when the event is detected.
9.25.1.1 Parameters
- bcsmEvents:
This parameter specifies the event or events of which a report is requested.
- eventTypeBCSM:
This parameter specifies the type of event of which a report is requested. Values collectedInfo andtermAttemptAuthorized are not valid for the RequestReportBCSMEvent operation.
- monitorMode:
This parameter indicates how the event should be reported. When the “monitorMode“ is “interrupted“, theevent shall be reported as a request, if the “monitorMode“ is “notifyAndContinue“, the event shall be reportedas a notification, if the “monitorMode“ is “transparent“, the event shall not be reported.
- legID:
This parameter indicates the party in the call for which the event shall be reported. gsmSCF will use theoption “sendingSideID“ only.
- sendingSideID:
If not included, the following defaults are assumed for LegID:
“legID“ = 1 for the events O-Abandon and T-Abandon,
“legID“ = 2 for the events RouteSelectFailure, O-CalledPartyBusyBusy, O-NoAnswer, O-Answer, O-NotReachable, T-CalledPartyBusyBusy, T-NoAnswer, and T-Answer and T-NotReachable.
The “legID“ parameter shall always be included for the events O-Disconnect and T-Disconnect.
- dPSpecificCriteria:
This parameter indicates information specific to the DP to be armed.
- applicationTimer:
This parameter indicates the NoAnswer timer value for the NoAnswer event. If the user doesnot answer the call within the allotted time the gsmSSF reports the event to the gsmSCF. The timer shall be shorter thanthe network NoAnswer timer.
GSM 09.78 Version 6.1.0 Release 1997 20
9.25.2 Spare
9.25.3 Responding entity (gsmSSF)
9.25.3.1 Normal procedure
gsmSSF precondition:
(1) A control relationship exists between the gsmSSF and the gsmSRF.
(2) The gsmSSF is in either the state “Waiting for Instructions“ or the state “Monitoring“.
Note: In state “monitoring” only requests to disarm detection points (with MonitorMode set to“Transparent”) or send notifications of events (with MonitorMode set to“NotifyAndContinue”) shall be accepted.
gsmSSF postconditions:
(1) The requested EDPs have been armed as indicated.
(2) Previously requested events are monitored until ended by a transparent monitor mode, until the end of the call,until the EDPs are detected or until the corresponding leg is released.
(3) The gsmSSF remains in the same state, unless all EDPs have been disarmed and no CallInformationReport orApplyChargingReport has been requested; in the latter case the gsmSSF moves to the state “Idle“.
9.25.3.2 Error handling
Generic error handling for the operation related errors is described in Clause 8 and the TCAP services which are usedfor reporting operation errors are described in Clause 10.