2009年8月26日

CAP Overview

CAP Overview Study:


The following capabilities in CAP4 are added:

  • Interactions with Optimal Routing;
  • Call Party Handling;
  • DTMF Mid call procedure for Mobile Originated and Mobile Terminating calls;
  • Inclusion of flexible tone injection;
  • Provision of location information of called subscriber;
  • Provide location information during ongoing call;
  • CAMEL control over MT SMS;
  • Notification of GPRS mobility management to CSE;
  • Inclusion of ODB data in Any Time Modification;
  • Enhancement of Any Time Interrogation and Provide Subscriber Information for PS Domain;
  • Mobile Number Portability database interrogation;
  • Criteria for the provision of location information during ongoing call;
  • Enhanced Dialled Services;
  • Enhancement to Establish Temporary Connection;
  • CAMEL control of trunk originated calls.
  • CAMEL support for Optimal Routeing of circuit-switched mobile-to-mobile calls;
  • The capability for the CSE to create additional parties in an existing call;
  • The capability for the CSE to create a new call unrelated to any other existing call;
  • Capabilities for the enhanced handling of call party connections;
  • The capability for the CSE to control sessions in the IP Multimedia Subsystem.
  • Enhanced CSE capability for Dialled Services.
  • The capability to report basic service changes during ongoing call.
  • The CSE capability to select between preferred and less preferred bearer service.
  • The capability for the CSE to control trunk originated calls.
  • The capability for the CSE to request additional dialled digits.

CAMEL phase 4 functionalities which may be offered to the gsmSCF are the following:

  • Creating additional parties in a call, Creating a new call (Initiate Call Attempt);
  • Placing an individual call party on hold or moving an individual call party to Call Segment 1, when Call Segment 1 does not exist (Split Leg);
  • Connecting an individual call party to the group (Move Leg);
  • Releasing an individual call party (Disconnect Leg);
  • Indication of the release of a call party or call segment (Entity Released);
  • Enhancements for subscriber interactions with the gsmSCF (Disconnect Forward Connection With Argument);
  • Inclusion of flexible tone injection (Play Tone);
  • DTMF Mid call procedure for MO and VT calls (DP O_Mid_Call, DP T_Mid_Call);
  • Provision of Charge Indicator at answer DP (Charge Indicator at DP O_Answer, DP T_Answer);
  • Support of Alerting DP (DP O_Term_Seized, DP Call_Accepted);
  • Provision of location information of subscriber at alerting DP (Location information at DP O_Term_Seized, DP Call_Accepted);
  • Provision of location information during an ongoing call (DP O_Change_Of_Position, DP T_Change_Of_Position);
  • Interactions with Basic Optimal Routeing (Basic OR Interrogation Requested in Connect and Continue With Argument, Route Not Permitted in DP O_Abandon);
  • Warning tone enhancements (Burstlist for Audible Indicator);
  • Enhancements of Call Forwarding indication (Forwarding Destination Number);
  • Criteria for the provision of location information during ongoing call (Criteria for DP O_Change_Of_Position and DP T_Change_Of_Position);
  • Subscribed Enhanced Dialled services (see description below);
  • Serving Network Enhanced Dialled Services
  • SCUDIF notification during active phase of the call (DP O_Service_Change and T_Service_Change) ;
  • Collection of additional dialled digits (Arming CollectedInfo DP as EDP-R)


Support for the following CAMEL phase 4 CSIs:

  • CAMEL phase 4 O‑CSI;
  • CAMEL phase 4 D‑CSI;
  • CAMEL phase 4 T‑CSI;
  • CAMEL phase 4 VT‑CSI;
  • CAMEL phase 4 MT‑SMS‑CSI;
  • CAMEL phase 4 MG‑CSI;
  • CAMEL control of trunk originated calls;
  • Reporting of additional dialled digits.

CAMEL subscribers have one or more CAMEL Subscription Information (CSI) elements.

  • CAMEL Subscription Information is provided by the HPLMN operator by administrative means.
  • The following CSIs may be administered per subscriber:
D-CSI
  • Dialled Services CAMEL Subscription Information (D-CSI) is transferred to the VPLMN (at location update), IPLMN (for an incoming call in GMSC) or the IM CN subsystem. D-CSI contains trigger information which is required to invoke a CAMEL service logic for subscribers dialled services.

GPRS-CSI

  • GPRS CAMEL Subscription Information (GPRS-CSI) is transferred to the VPLMN. GPRS-CSI contains trigger information which is required to invoke a CAMEL Service Logic for GPRS Sessions and PDP Contexts.

M-CSI

  • Mobility Management CAMEL Subscription Information (M-CSI) is transferred to the VPLMN. M-CSI is used to notify the CSE about Mobility Management events for the CS subscriber.

MG-CSI

  • Mobility Management for GPRS CAMEL Subscription Information (MG-CSI) is transferred to the VPLMN. MG-CSI is used to notify the CSE about Mobility Management events for the GPRS subscriber.

SMS-CSI

  • Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI) is transferred to the VPLMN. MO-SMS-CSI contains trigger information that is required to invoke a CAMEL Service Logic for Mobile Originating Short Message submissions.

MT-SMS-CSI

  • Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI) is transferred to the VPLMN. MT-SMS-CSI contains trigger information that is required to invoke a CAMEL Service Logic for Mobile Terminating Short Message delivery.

O-CSI

  • Originating CAMEL Subscription Information (O-CSI) is transferred to the VPLMN (at location update),to the IPLMN (for an incoming call in the GMSC) and to the IM CN subsystem. O-CSI contains trigger information that is required to invoke a CAMEL Service Logic for Mobile Originating calls (in the VMSC) and Mobile Forwarding calls (in the VMSC and the GMSC).

SS-CSI

  • Supplementary Service Invocation Notification CAMEL Subscription Information (SS-CSI) is transferred to the VPLMN. SS-CSI is used to notify the CSE about the invocation of certain Supplementary Services.

T-CSI

  • Terminating CAMEL Subscription Information (T-CSI) is transferred to the IPLMN for an incoming call in the GMSC. T-CSI contains trigger information which is required to invoke a CAMEL Service Logic for Mobile Terminating calls in the GMSC.

TIF-CSI

  • Translation information Flag CAMEL Subscription Information (TIF-CSI) is transferred to the VPLMN. TIF-CSI is used in the HLR for registering short Forwarded-to-Numbers (FTNs). When TIF-CSI is present, the subscriber is allowed to register short FTNs.
    When the subscriber invokes Call Deflection, TIF-CSI in the VPLMN allows the subscriber to deflect to short Deflected-to-Numbers.

U-CSI

  • USSD CAMEL Subscription Information (U-CSI) is held in the HLR; it is not sent to any other node. U-CSI contains trigger information which is used to invoke a USSD application in the CSE for the served subscriber.

UG-CSI

  • USSD General CAMEL Subscription Information (UG-CSI) is held in the HLR; it is not sent to any other node. UG-CSI contains trigger information which is used to invoke a USSD application in the CSE for all subscribers.

VT-CSI

  • VMSC Terminating CAMEL Subscription Information (VT-CSI) is transferred to the VPLMN at location update and to the IM CN subsystem. VT-CSI contains trigger information which is required to invoke a CAMEL Service Logic for Mobile Terminating calls in the VMSC.
  • Refer to 3GPP TS 23.078 for detailed descriptions of the various types of CAMEL Subscription Information.
  • The CSI may include the Default Call Handling, Default GPRS Handling or Default SMS Handling.
  • The Default Call Handling indicates whether the call shall be released or continued if the contact with the CSE is not confirmed or is interrupted.
  • Network -based services may be provided by the serving PLMN operator. The provisioning mechanism is out of the scope of this specification.
  • Trunk originated services may be provided by the PLMN operator. The provisioning mechanism is out of the scope of this specification.

MO-SMS-CSI (Mobile Originating Short Message Service CAMEL Subscription Information)

  • is transferred to the VPLMN. MO-SMS-CSI contains trigger information that is required to invoke a CAMEL Service Logic for Mobile Originating Short Message submissions.

MT‑SMS‑CSI (Mobile Terminating Short Message Service CAMEL Subscription Information):

  • MT‑SMS‑CSI identifies the subscriber as having MT SMS CAMEL services.

GPRS CAMEL Subscription Information (GPRS‑CSI):

  • GPRS‑CSI identifies the subscriber as having GPRS CAMEL services.

BCSM, DP and PIC (O-BCSM and T-BCSM)

http://docs.google.com/View?id=ddh56dhg_89fhnzq5f2

http://docs.google.com/View?id=ddh56dhg_91g984bzft

BCSM, DP and PIC (for SMS)

http://docs.google.com/View?id=ddh56dhg_93fxhbjw9k

http://docs.google.com/View?id=ddh56dhg_95d2kn6wgm


BCSM, DP and PIA (for GPRS)

http://docs.google.com/View?id=ddh56dhg_97dxh9j6hc

http://docs.google.com/View?id=ddh56dhg_99cjzqzrd4

CAP Overview (22.078) – CAP Procedure & Capability

Not Applicable Here


CAP Overview (23.078) – Information Flows in CAP

  • gsmSSF to gsmSCF information flows
  • gsmSCF to gsmSSF information flows
  • Optional (Service logic dependent) gsmSCF to gsmSRF information flows
  • gsmSRF to gsmSCF information flows
  • gsmSCF to Assisting SSF information flows
  • Assisting SSF to gsmSCF information flows
  • HLR to VLR information flows
  • VLR to HLR information flows
  • HLR to GMSC information flows
  • GMSC to HLR information flows
  • VMSC to GMSC information flows
  • MSC to VLR information flows
  • VLR to MSC information flows
  • gsmSCF to HLR information flows
  • HLR to gsmSCF information flows

CAP Overview (23.078) – Procedure in CAP for SMS

  • gsmSSF or gprsSSF to gsmSCF information flows
  • gsmSCF to gsmSSF or gprsSSF information flows
  • HLR to VLR or SGSN information flows
  • VLR or SGSN to HLR information flows
  • VLR to MSC Information Flows
  • MSC to VLR Information Flows

CAP Overview (23.078) –Procedure in CAP for GPRS

  • gprsSSF to gsmSCF Information Flows
  • gsmSCF to gprsSSF Information Flows
  • HLR to SGSN Information Flows
  • SGSN to HLR Information Flows

CAP Overview (23.078) – Information Flows in CAP for SS (Supplementary Service)

  • MSC to gsmSCF information flows
  • HLR to VLR information flows
  • HLR to gsmSCF information flows
  • VLR to MSC information flows

CAP Overview (23.078) – CAP for MM (Mobility Management)

  • VLR or SGSN to gsmSCF information flows
  • SGSN to HLR information flows
  • VLR to HLR information flows
  • HLR to VLR or SGSN information flows

CAP Overview (23.078) – CAP for Control and Interrogation subscription data

  • gsmSCF to HLR information flows
  • HLR to gsmSCF information flows
  • IP-SM-GW to HLR information flows
  • HLR to IP-SM-GW information flows

CAP Overview (23.078) – CAP for Subscriber Location and State retrieval

  • gsmSCF to GMLC information flows
  • GMLC to gsmSCF information flows
  • gsmSCF to HLR information flows
  • HLR to gsmSCF information flows
  • HLR to SGSN information flows
  • SGSN to HLR information flows

CAP Overview (23.078) – CAP for Subscriber Mobile Number Portability (MNP) status retrieval

  • gsmSCF to MNP SRF information flows
  • MNP SRF to gsmSCF information flows

CAP Overview (29.078) – Detailed operation procedures (1) for CS call control

Detailed operation procedures for circuit switched call control

1 ActivityTest procedure

2 ApplyCharging procedure

3 ApplyChargingReport procedure

4 AssistRequestInstructions procedure

5 CallGap procedure

6 CallInformationReport procedure

7 CallInformationRequest procedure

8 Cancel procedure

8A CollectInformation Procedure

9 Connect procedure

10 ConnectToResource procedure

11 Continue procedure

12 ContinueWithArgument Procedure

13 DisconnectForwardConnection procedure

14 DisconnectForwardConnectionWithArgument procedure

15 DisconnectLeg procedure

16 EntityReleased procedure

17 EstablishTemporaryConnection procedure

18 EventReportBCSM procedure

19 FurnishChargingInformation procedure

20 InitialDP procedure

21 InitiateCallAttempt procedure

22 MoveLeg procedure

23 PlayAnnouncement procedure

24 PlayTone procedure

25 PromptAndCollectUserInformation procedure

26 ReleaseCall procedure

27 RequestReportBCSMEvent procedure

28 ResetTimer procedure

29 SendChargingInformation procedure

30 SpecializedResourceReport procedure

31 SplitLeg Procedure


Detailed operation procedures for SMS control

§ ConnectSMS procedure

§ ContinueSMS procedure

§ EventReportSMS procedure

§ FurnishChargingInformationSMS procedure

§ InitialDPSMS procedure

§ ReleaseSMS procedure

§ RequestReportSMSEvent procedure

§ ResetTimerSMS procedure


Detailed operation procedures for GPRS control

§ ActivityTestGPRS procedure

§ ApplyChargingGPRS procedure

§ ApplyChargingReportGPRS procedure

§ CancelGPRS procedure

§ ConnectGPRS procedure

§ ContinueGPRS procedure

§ EntityReleasedGPRS procedure

§ EventReportGPRS procedure

§ FurnishChargingInformationGPRS procedure

§ InitialDPGPRS procedure

§ ReleaseGPRS procedure

§ RequestReportGPRSEvent procedure

§ ResetTimerGPRS procedure

§ SendChargingInformationGPRS Procedure


CAP Overview – CAMEL & related Recommendations

§ 3GPP TS 22.078: CAMEL Service Description; Stage 1

§ 3GPP TS 23.078: CAMEL Phase 4; Stage 2

§ 3GPP TS 29.078: CAMEL Phase 4; CAMEL Application Part (CAP) specification

§ 3GPP TS 23.278: CAMEL Phase 4 - Stage 2; IM CN Interworking

§ 3GPP TS 29.278: CAMEL Application Part (CAP) Specification for IP Multimedia Subsystems (IMS)

§ 3GPP TR 21.978: Feasibility Technical Report - CAMEL Control of VoIP Services

1 則留言:

  1. In Camel Phase 4, Why is the Routing DP as a branch directly connected O Answer, Is there any specific reason.

    回覆刪除