Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.097  Word version:  17.0.0

Top   Top   None   None   Next
1…   7…   7.5…   7.6…   7.8…   7.9…   7.11…   A…

 

1  Scopep. 6

The present document specifies the stage 2 description of the Multiple Subscriber Profile (MSP) Supplementary Service Phase 2. MSP Phase 2 is implemented using CAMEL Phase 3.

2  Referencesp. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "3G Vocabulary".
[2]
TS 22.030: "Man Machine Interface (MMI) of the Mobile Station (MS)".
[3]
TS 22.097: "Multiple Subscriber Profile (MSP) Service Description - Stage 1".
[4]
TS 23.008: "Organisation of subscriber data".
[5]
TS 23.015: "Technical realization of Operator Determined Barring (ODB)".
[6]
TS 23.018: "Basic Call Handling - Technical Realization".
[7]
TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 2".
[8]
TS 23.072: "Call Deflection (CD); Stage 2".
[9]
TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) - Phase 3; Stage 2".
[10]
TS 23.079: "Support of Optimal Routeing (SOR); Technical Realisation".
[11]
TS 23.081: "Line identification supplementary services - Stage 2".
[12]
TS 23.082: "Call Forwarding (CF) supplementary services - Stage 2".
[13]
TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2".
[14]
TS 23.084: "Multi Party (MPTY) supplementary services - Stage 2".
[15]
TS 23.085: "Closed User Group (CUG) supplementary services - Stage 2".
[16]
TS 23.086: "Advice of Charge (AoC) supplementary services - Stage 2".
[17]
TS 23.087: "User-to-User (UUS) Supplementary Service; Stage 2".
[18]
TS 23.088: "Call Barring (CB) supplementary services - Stage 2".
[19]
TS 23.090: "Unstructured Supplementary Service Data (USSD) - Stage 2".
[20]
TS 23.091: "Explicit Call Transfer (ECT) supplementary service - Stage 2".
[21]
TS 23.093: "Technical Realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2".
[22]
TS 24.086: "Advice of Charge (AoC) supplementary services - Stage 3".
Up

3  Definitions and abbreviationsp. 7

3.1  Definitionsp. 7

For the purpose of this specification, the following terms and definitions apply:
Default Profile:
profile used when the MSP subscriber roams to a non-supporting network.
MSP Subscriber:
the subscriber provisioned with the MSP service
Profile Identity:
numerical identity (between 1 and 4) of the profile
Profile Status:
specifies if the profile is the registered profile and/or the default profile
Registered Profile:
profile used for all MO calls and short messages if a profile has not been explicitly selected

3.2  Abbreviationsp. 7

The abbreviations used in this specification are listed in 3G TR 21.905.
For the purpose of this specification, the following abbreviations apply:
CD
The Call Deflection supplementary service
MSP
The Multiple Subscriber Profile supplementary service
UUS
The User-to-User Signalling supplementary service
SII2
The Service Interaction Indicators Two parameter (see 3G TS 23.078)

4  Features needed to support MSP Phase 2p. 7

CAMEL Phase 3 is a pre-requisite for MSP Phase 2.
The following CAMEL Phase 3 features are used for MSP Phase 2:
  • SII2;
  • MO SMS interaction;
  • T-BCSM in the VMSC;
  • SS-CSI Invocation Notification for CCBS;
  • Any Time Modification;
  • CUG Handling.
The following CAMEL Phase 2 features are used for MSP Phase 2:
  • Network Indication of Alerting pattern;
  • Event detection points;
  • USSD Interaction;
  • Control of Call Duration;
  • SS-CSI Invocation Notification for CD;
  • Furnish Charging Information.

5  Additional Information stored in network entitiesp. 8

5.1  Data stored in the HLRp. 8

The HLR contains all the common data (the data valid for all profiles) and some data specific to the default profile.
The data stored in the HLR are defined in 3G TS 23.008. The elements specifically used for MSP are:
  • list of MSISDNs and associated Bearer Capabilities for each profile;
  • default profile (associated with the Basic MSISDN);
  • capabilities of VLR (support of CAMEL Phase 2 and 3);
  • supplementary services (per BSG) provisioned per subscriber (CW, CH, MPTY,…);
  • Call Barring Data (see clause 7.8.8: Call Barring);
  • ODB Data (see clause 7.9.5: Operator Determined Barring);
  • HOLD Data (see clause 7.8.2: Call Hold);
  • ECT Data (see clause 7.8.9: Explicit Call Transfer);
  • MPTY Data (see clause 7.8.5: Multi Party);
  • CCBS Data (see clause 7.8.10: Completion of Calls to Busy Subscriber);
  • CW Data (see clause 7.8.3: Call Waiting);
  • CLIR Data (see clause 7.8.1.2);
  • CAMEL data including the MSP service key, O-CSI, T-CSI, VT-CSI, UG-CSI, SS-CSI and Location information / Subscriber state Interrogation.
Up

5.2  Data stored in the VLRp. 8

The data stored in a VLR are defined in 3G TS 23.008. MSP has no impact on the VLR.

6  Additional procedures in network entitiesp. 8

6.1  OCB_flagp. 8

The OCB_flag shall be set in the HLR if Call Barrings are provided in the gsmSCF.
If the OCB_flag is set then:
  • when the subscriber roams to a VLR which supports CAMEL Phase 2 or later, the HLR shall not send any outgoing call barring supplementary services data to the VLR;
  • when the subscriber roams to a VLR which does not support CAMEL Phase 2 or later, the HLR shall send to the VLR outgoing call barring supplementary services data as stored in the HLR;
  • the subscriber shall not be allowed to alter the Call Barring data in the HLR.
Up

6.2  ODB flagsp. 9

The ODB flag for the relevant category shall be set in the HLR if ODB is provisioned in the gsmSCF for that category.
If the ODB flag is set for that category, then:
  • when the subscriber roams to a VLR which supports CAMEL Phase 2 or later, the HLR shall not send any ODB data for that category to the VLR;
  • when the subscriber roams to a VLR which does not support CAMEL Phase 2 or later, the HLR shall send to the VLR ODB data for that category as stored in the HLR.

6.3  HOLD_flagp. 9

The HOLD_flag shall be set in the HLR if the subscriber data for the HOLD SS are controlled by the gsmSCF.
If the HOLD_flag is set, then:
  • when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the HOLD SS as Active and Operative;
  • when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the HOLD SS as stored in the HLR.

6.4  CW_flagp. 9

The CW_flag shall be set in the HLR if the subscriber data for the CW SS are controlled by the gsmSCF.
If the CW_flag is set, then:
  • when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CW SS as Active and Operative;
  • when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CW SS as stored in the HLR;
  • the subscriber shall not be allowed to alter the CW data in the HLR.
Up

6.5  MPTY_flagp. 9

The MPTY_flag shall be set in the HLR if the subscriber data for the MPTY SS are controlled by the gsmSCF.
If the MPTY_flag is set, then:
  • when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the MPTY SS as Active and Operative;
  • when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the MPTY SS as stored in the HLR.

6.6  ECT_flagp. 9

The ECT_flag shall be set in the HLR if the subscriber data for the ECT SS are controlled by the gsmSCF.
If the ECT_flag is set, then:
  • when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the ECT SS as Active and Operative;
  • when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the ECT SS as stored in the HLR.

6.7  CCBS_flagp. 10

The CCBS_flag shall be set in the HLR if the subscriber data for the CCBS SS are controlled by the gsmSCF.
If the CCBS_flag is set, then:
  • when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CCBS SS as Active and Operative;
  • when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CCBS SS as stored in the HLR;
  • the subscriber shall not be allowed to alter the CCBS data in the HLR.
Up

6.8  CLIR_flagp. 10

The CLIR_flag shall be set in the HLR if the subscriber data for the CLIR SS are controlled by the gsmSCF.
If the CLIR_flag is set, then:
  • when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CLIR SS as Active and Operative, and the presentation mode as "temporary (presentation allowed)";
  • when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLRshall send to the VLR the activation state and presentation mode for the CLIR SS as stored in the HLR;
  • the subscriber shall not be allowed to alter the CLIR data in the HLR.
Up

Up   Top   ToC