4.5.1 Overall SDL architecture
23.0783GPPCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4Release 17Stage 2TS
The following mapping from the SDL procedures to the Intelligent Network concepts apply:
|
SDL process |
Description |
SDL process specification |
|---|---|---|
|
CSA_gsmSSF |
Call Segment Association (CSA). The CSA SDL process distributes the CAP operations to the appropriate Call Segment(s). |
3GPP TS 23.078 |
|
CS_gsmSSF |
Call Segment (CS). Controls one or more BCSMs. |
3GPP TS 23.078 |
|
OCH_MSC |
O‑BCSM in VMSC for Mobile Originating call controlling both Leg 1 and Leg 2. If CAP Disconnect Leg (leg 2) is received at the initial detection point (Collected_Info), then the call is not routed to the destination and the process calls the procedure CAMEL_OCH_LEG1_MSC to control Leg 1. If Answer is received, the process spawns the child process CAMEL_OCH_LEG2_MSC to control Leg 2 and calls the procedure CAMEL_OCH_LEG1_MSC to control Leg 1. The handling of the legs after answer is completely separate. |
3GPP TS 23.018 |
|
MT_GMSC |
T‑BCSM in the GMSC controlling both Leg 1 and Leg 2. If CAP Disconnect Leg (leg 2) is received at the initial detection point (Terminating_Attempt_Authorised), then the call is not routed to the destination and the process spawns the child process CAMEL_MT_LEG1_GMSC to control Leg 1. The process MT_GMSC terminates. If Answer is received, the process spawns the child process CAMEL_MT_LEG1_GMSC to control Leg 1 and calls the procedure CAMEL_MT_LEG2_GMSC to control Leg 2. The handling of the legs after answer is completely separate. |
3GPP TS 23.018 |
|
MT_CF_MSC |
O‑BCSM in the redirecting MSC for Call Forwarding supplementary service, or Call Deflection supplementary service, or for CAMEL-based call forwarding. This process controls both Leg 1 and Leg 2. If CAP Disconnect Leg (leg 2) is received at the initial detection point (Collected_Info), then the call is not routed to the destination and the process calls the procedure CAMEL_MT_CF_LEG1_MSC to control Leg 1. If Answer is received, the process spawns the child process CAMEL_MT_CF_LEG2_MSC to control Leg 2 and calls the procedure CAMEL_MT_CF_LEG1_MSC to control Leg 1. The handling of the legs after answer is completely separate. |
3GPP TS 23.018 |
|
ICH_MSC |
T‑BCSM in the VMSC controlling both Leg 1 and Leg 2. If CAP Disconnect Leg (leg 2) is received at the initial detection point (Terminating_Attempt_Authorised), then the call is not routed to the destination and the process spawns the child process CAMEL_ICH_LEG1_MSC to control Leg 1. The process ICH_MSC terminates. If Answer is received, the process spawns the child process CAMEL_ICH_LEG1_MSC to control Leg 1 and calls the procedure CAMEL_ICH_LEG2_MSC to control Leg 2. The handling of the legs after answer is completely separate. |
3GPP TS 23.018 |
|
TO_MSC |
O-BCSM in the inter-connecting MSC for trunk originated calls. This process controls both Leg 1 and Leg 2. If CAP Disconnect Leg (leg 2) is received at the initial detection point (Collected_Info), then the call is not routed to the destination and the process calls the procedure CAMEL_TOC_LEG1_MSC to control Leg 1. If Answer is received, the process spawns the child process CAMEL_MT_CF_LEG2_MSC to control Leg 2 and calls the procedure CAMEL_TOC_LEG1_MSC to control Leg 1. The handling of the legs after answer is completely separate. |
3GPP TS 23.018 |
|
Assisting_MSC |
The process in the MSC to handle an assist request. |
3GPP TS 23.078 |
|
CAMEL_ICA_MSC |
O‑BCSM for gsmSCF initiated new call, or for new party set-up. This process controls the new leg. |
3GPP TS 23.078 |
The following general rules apply:
1 There is only one CSA per CAP dialogue.
2 The CSA controls one or more Call Segments.
3 A Call Segment controls one or more BCSMs. Due to Call Party Handling, legs may be moved from one Call Segment to another and new Call Segments may be created. When legs are moved they take their properties with them, i.e. armed EDPs and pending reports.
4 Legs are not moved between BCSMs.
5 The active legs in the same Call Segment have a voice connection. They hear each other and the same in-band tone and announcements. The following exceptions exist:
– Apply Charging IF: the warning tone associated with the Apply Charging IF is played to a single call party in the Call Segment.
– Play Tone IF: the flexible tone from the Play Tone IF may be played to a single call party in the Call Segment.
The following diagrams shows the overall architecture for the SDL diagrams.
Figure 4.9-1: Outgoing case (gsmSSF relay)
Figure 4.9-2: Outgoing case (direct path gsmSCF to gsmSRF or assist with relay)
Figure 4.9-3: Terminating GMSC case (gsmSSF relay)
Figure 4.9-4: Terminating GMSC case (direct path gsmSCF to gsmSRF or assist with relay)
NOTE: The ICH_MSC may also be connected via an A interface to the terminating Mobile Station.
Figure 4.9-5: Terminating VMSC case (gsmSSF relay)
NOTE: The ICH_MSC may also be connected via an A interface to the terminating Mobile Station
Figure 4.9-6: Terminating VMSC case (direct path gsmSCF to gsmSRF or assist with relay)
Figure 4.9-7: Assisting case
Figure 4.9-8: gsmSCF initiated call case (gsmSSF relay)
Figure 4.9-9: Trunk Originating case (gsmSSF relay)