Content for  TS 23.008  Word version:  18.1.0

This data defines the contents of the Originating CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It consists of:

• A TDP list: The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
  1. DP Value: The DP value identifies the DP in the MO State Model where service triggering may take place.
     For O-CSI, the allowed DP value are DP Collected_info, DP Route_Select_Failure.
  2. A gsmSCF address: It is the gsmSCF address ( E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
  3. A serviceKey: The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.
  4. A default Call Handling: The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
  5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.

• CAMEL capability handling: It gives the CAMEL phase associated to the O-CSI (CAMEL phase 1, phase 2, phase 3, or phase 4).
• The CSI state: The CSI state indicates whether the O-CSI is active or not.
• The notification flag: the notification flag indicates whether changes of the O-CSI shall trigger Notification on Change of Subscriber Data.

This data defines the contents of the terminating CAMEL subscription information used to interwork with the gsmSCF for MT call. It consists of:

• A TDP list: The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
  1. DP Value: The DP value identifies the DP in the MT State Model where service triggering may take place. For T-CSI, the allowed DP value are DP Terminating_Attempt_Authorised, DP T_Busy, DP T_No_Answer.
  2. A gsmSCF address: It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
  3. A serviceKey: The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.
  4. A default Call Handling: The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
  5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.

• CAMEL capability handling: It gives the CAMEL phase associated to the T-CSI/VT-CSI (CAMEL phase1, phase2, or phase3, or phase4).
• The CSI state: indicates whether the T-CSI/VT-CSI is active or not.
• Notification flag: The notification flag indicates whether the change of the T-CSI/VT-CSI shall trigger Notification on Change of Subscriber data.

This data item indicates whether or not the HLR shall send the location information and state of the called subscriber, as available, when a GMSC requests routeing information for an MT call.

This data is used on USSD request receipt from the MS. It consists of a list of:

• a service code: the service code defines a specific application in the gsmSCF;
• a gsmSCFaddress: it is the gsmSCF address (E.164 number) where the USSD application is treated for this subscriber.

This data is used to notify the gsmSCF about Supplementary service invocation. It consists of:

• notification criterion, which may be a list of Supplementary Service(s). The possible Supplementary Services are: ECT, CD or MPTY, CCBS;
• a gsmSCFaddress: it is the gsmSCF address (E.164 number) where the notification of the Supplementary Service invocation is treated for this subscriber;
• CSI state, indicates whether the SS-CSI is active or not;
• notification flag: it indicates whether the change of the SS-CSI shall trigger Notification on Change of Subscriber data.

• TIF-CSI flag is used to indicate that the HLR shall not attempt to perform any actions on the FTN (translation, prohibited FTN checks, call barring checks) at the registration procedure.
• Notification flag. The notification flag indicates whether the change of TIF-CSI flag shall trigger Notification on Change of Subscriber data.

This data indicates which Mobility Management events shall be reported to the gsmSCF. It consists of:

• gsmSCF address: this is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format.
• ServiceKey: the serviceKey is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.
• Mobility Management Triggers: these triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility managements triggers may contain one or any combination of the following elements:
  • Location update in the same VLR service area;
  • Location update to another VLR service area;
  • IMSI attach;
  • MS initiated IMSI detach (explicit detach);
  • Network initiated IMSI detach (implicit detach).
• The CSI state, indicates whether the M-CSI is active or not.
• Notification flag. The notification flag indicates whether the change of M-CSI shall trigger Notification on Change of Subscriber data.

This data defines the contents of the MO SMS CAMEL subscription information. The MO SMS CAMEL Subscription Information is used for the following interworking:

• Interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MO SMS;
• Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MO SMS.

MO-SMS-CSI consists of the following data items:

• TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
     For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.
  2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MO SMS CAMEL Service associated with this TDP, is located for this subscriber.
  3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
  4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF;
• CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service. The CAMEL Capability Handling for MO-SMS-CSI shall have the value CAMEL phase 3.
• CSI state: indicates whether the MO-SMS-CSI is active or not.
• Notification flag indicates whether the change of the SMS-CSI shall trigger Notification on change of subscriber Data or not.

This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for the following interworking:

• Interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MT SMS;
• Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MT SMS.

MT-SMS-CSI consists of the following data items:

• TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
     For MT-SMS-CSI, the only allowed DP value is DP SMS-Delivery-Request
  2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.
  3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
  4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF.
  5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent.

 

• CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4.
• CSI state: indicates whether the MT-SMS-CSI is active or not.
• Notification flag indicates whether the change of the MT-SMS-CSI shall trigger Notification on change of subscriber Data or not.

This data defines the contents of the GPRS CAMEL subscription information. The GPRS CAMEL Subscription Information is used for the interworking between gsmSCF and gprsSSF, for CAMEL control of packet switch call. GPRS-CSI consists of the following data items:

• TDP List. The TDP list is a list of GPRS TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the GPRS State Model where service triggering may take place.
  2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the GPRS CAMEL Service associated with this TDP, is located for this subscriber.
  3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.
  4. Default GPRS handling. The default GPRS handling indicates whether the GPRS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.
• CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the GPRS service. The CAMEL Capability Handling for GPRS-CSI shall have the value CAMEL phase 3.
• The CSI state indicates whether the GPRS-CSI is active or not.
• The notification flag indicates whether the change of the GPRS-CSI shall trigger Notification on change of subscriber Data or not.

This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It is applicable at TDP Analysed Info. It consists of:

• DP Criteria list. This consists of 1 to 10 entries. Each entry shall contain the following items:
  1. DP Criterion. It indicates when the gsmSSF shall request gsmSCF for instructions. It is a destination number.
  2. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion.
  3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion.
  4. A default Call Handling. It indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion.
• CAMEL capability handling. It indicates the CAMEL phase associated to the D-CSI (CAMEL phase3, or Camel phase4 shall be indicated).
• CSI state: indicates whether the D-CSI is active or not.
• Notification Flag. It indicates whether the change of the D-CSI shall trigger the Notification on Change of Subscriber Data.

This data indicates which Mobility Management for GPRS subscriber events shall be reported to the gsmSCF. It consists of:

• gsmSCF address: this is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format.
• Service Key: the service key is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.
• Mobility Management Triggers: these triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility management triggers may contain one or any combination of the following elements:
  • Routeing area update of MS to a different SGSN service area;
  • Routeing area update of MS within the same SGSN service area;
  • GPRS attach (e.g. MS switched on, successful routeing area update after network initiated detach);
  • MS-initiated GPRS detach (e.g. MS switched off);
  • Network-initiated transfer to the "not reacheable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreacheable).
• The CSI state indicates whether the MG-CSI is active or not.
• Notification flag. The notification flag indicates whether the change of MG-CSI shall trigger Notification on Change of Subscriber data.

The HLR shall have a set of negotiated CAMEL Capability Handling variables. Each CSI that may be downloaded to the VLR or to the SGSN shall have a negotiated CAMEL Capability Handling (CCH) variable associated with it. The negotiated CCH variable for a CSI indicates what CAMEL Phase is indicated in that CSI in the VLR or SGSN. When the negotiated CCH variable has a value NULL, it indicates that the given CSI has not been downloaded to the VLR or SGSN. The following table shows the negotiated CAMEL Capability Handling variables.

There is no negotiated CAMEL Capability Handling variable associated with TIF-CSI. The HLR does not store a Negotiated CAMEL Capability Handling for CSIs that are sent to the GMSC, since a subscriber is not permanently registered in a GMSC.

The HLR shall store the supported CAMEL Phases of the VLR where the subscriber is currently registered and the SGSN where the subscriber is currently attached. The following variables are required:

• VLR Supported CAMEL Phases
• SGSN Supported CAMEL Phases

The HLR does not store the Supported CAMEL Phases of the GMSC, since a subscriber is not permanently registered at a GMSC.

The HLR shall store the offered CAMEL4 CSIs of the VLR where the subscriber is currently registered and the SGSN where the subscriber is currently attached. The following variables are required:

• VLR Offered CAMEL4 CSIs
• SGSN Offered CAMEL4 CSIs

The HLR does not store the Offered CAMEL4 CSIs of the GMSC, since a subscriber is not permanently registered at a GMSC.

The USSD general CAMEL service(UG-CSI) is also stored in the HLR. This data is used on USSD request receipt from the MS. It consists of a list of:

• a service code. The service code defines a specific application in the gsmSCF;
• a gsmSCFaddress. It is the gsmSCF address (E.164 number) where the USSD application is treated for this subscriber.

This information element contains the list of gsmSCF address (E.164 address) to which Notification on Change of Subscriber Data is to be sent.

The Originating CAMEL Subscription Information (O-CSI) are stored in the VLR. This data defines the contents of the originating CAMEL subscription information used to interwork with the gsmSCF for MO and CF calls. It consists of:

• A TDP list: The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the MO State Model where service triggering may take place.
     For O-CSI, the allowed DP value are DP Collected_info, DP Route_Select_Failure.
  2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
  3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic.. A serviceKey is associated to each TDP.
  4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
  5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.
• CAMEL capability handling. It gives the CAMEL phase associated to the O-CSI (CAMEL phase1, or phase2, phase3, or phase4).

This data defines the contents of the visited terminating CAMEL subscription information used by the VMSC to interwork with the gsmSCF for an MT call. It consists of:

• A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the MT State Model where service triggering may take place. For VT-CSI, the allowed DP value are DP Terminating Attempt Authorised, DP T_Busy, DP T_No_Answer.
  2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
  3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.
  4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
  5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF.
• CAMEL capability handling. It gives the CAMEL phase associated to the VT-CSI. It is set to CAMEL phase3 or phase4.

This data is used to notify the gsmSCF about Supplementary Service invocation. It consists of :

• a notification criterion, which may be ECT, CD or MPTY
• a gsmSCFaddress. It is the gsmSCF address (E.164 number) where the notification of the Supplementary service invocation is treated for this subscriber.

This data indicates which Mobility Management events shall be reported to the gsmSCF. It consists of:

• gsmSCF address : This is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address must be in E.164 format.
• ServiceKey: The serviceKey is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.
• Mobility Management Triggers. These triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility managements triggers may contain one or any combination of the following elements:
  • Location update in the same VLR service area;
  • Location update to another VLR service area;
  • IMSI attach;
  • MS initiated IMSI detach (explicit detach);
  • Network initiated IMSI detach (implicit detach).

This data defines the contents of the MO SMS CAMEL subscription information used for the interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MO SMS. MO-SMS-CSI consists of the following data items:

• TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
     For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.
  2. gsmSCF Address. The gsmSCF addess is the address (E.164 number) of the gsmSCF.
  3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
  4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF;
• CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service.

The CAMEL Capability Handling for MO-SMS-CSI shall have the value CAMEL phase 3.

This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MT SMS. MT-SMS-CSI consists of the following data items:

• TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
     For MT-SMS-CSI, the only allowed DP value is SMS-Delivery-Request
  2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.
  3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.
  4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF
  5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent.

 

• CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4.

This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It is applicable at TDP Analysed Info. It consists of:

• DP Criteria list, this consists of 1 to 10 entries containing : DP Criterion: It indicates when the gsmSSF shall request gsmSCF for instructions.
  1. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion.
  2. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion.
  3. A default Call Handling. It indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion.
• CAMEL capability handling. It indicates the CAMEL phase associated to the D-CSI (CAMEL phase3 or CAMEL phase4 shall be indicated).

This flag is used to indicate that the VLR shall not attempt to perform any actions on the deflected to number (DTN).

This data defines the contents of the MO SMS CAMEL subscription information. The MO-SMS-CSI in SGSN is used for the Interworking between SGSN and gsmSCF, for CAMEL control of packet switched MO SMS. MO-SMS-CSI consists of the following data items:

• TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
     For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.
  2. gsmSCF Address. The gsmSCF addess is the address (E.164 number) of the gsmSCF where the MO SMS CAMEL Service associated with this TDP, is located for this subscriber.
  3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
  4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.
• CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service.
  The CAMEL Capability Handling for MO-SMS-CSI in SGSN shall have the value CAMEL phase 3.

This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for the Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MT SMS. MT-SMS-CSI consists of the following data items:

• TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
     For MT-SMS-CSI, the only allowed DP value is SMS-Delivery-Request
  2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.
  3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
  4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.
  5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent.

 

• CAMEL Capability Handling: CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4.

This data defines the contents of the GPRS CAMEL subscription information. The GPRS CAMEL Subscription Information is used for the interworkingbetween gsmSCF and gprsSSF, for CAMEL control of packet switch call. The GPRS-CSI consists of the following data items:

• TDP List. The TDP list is a list of GPRS TDP descriptions. Each TDP description contains the following elements:
  1. DP Value. The DP value identifies the DP in the GPRS State Model where service triggering may take place.
  2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the GPRS CAMEL Service associated with this TDP, is located for this subscriber.
  3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.
  4. Default GPRS handling. The default GPRS handling indicates whether the GPRS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.
• CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the GPRS service. The CAMEL Capability Handling for GPRS-CSI in SGSN shall have the value CAMEL phase 3.

This data indicates which Mobility Management for GPRS events shall be reported to the gsmSCF. It consists of:

• gsmSCF address : This is the address of the gsmSCF where the Mobility Management for GPRS event notification shall be sent to. The gsmSCF address must be in E.164 format.
• Service Key: The service key is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.
• Mobility Management Triggers. These triggers define which Mobility Management events shall be reported to the gsmSCF. The mobility management triggers may contain one or any combination of the following elements:
  • Routeing area update of MS to a different SGSN service area;
  • Routeing area update of MS within the same SGSN service area;
  • GPRS attach (e.g. MS switched on, successful routeing area update after network initiated detach);
  • MS-initiated GPRS detach (e.g. MS switched off);
  • Network-initiated transfer to the "not reacheable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreacheable).