hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.12 Procedure Check_ACM_gsmSCF | ........................................................................................................ 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.13 Process AoC_MSP_gsmSCF | ................................................................................................................ 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.14 Procedure AoCI_gsmSCF | .................................................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.15 Procedure AoCC_gsmSCF | ................................................................................................................... 28 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.16 Procedure Outgoing_Barring_Check_gsmSCF | .................................................................................... 28 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.17 Procedure Incoming_Barring_Check_gsmSCF | .................................................................................... 28 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.18 Procedure Check_ECT_gsmSCF | .......................................................................................................... 28 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.19 Procedure Check_CCBS_gsmSCF | ....................................................................................................... 28 ETSI ETSI TS 123 097 V3.1.1 (2000-04) 4 3G TS 23.097 version 3.1.1 Release 1999 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.4 Information flows | ....................................................................................................................................... 48 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.6 SMS handling | .................................................................................................................................................. 50 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.7 Call Independent SS handling | .......................................................................................................................... 52 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8 Interaction with Supplementary Services | ........................................................................................................ 52 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.1 Line Identification services | ........................................................................................................................ 52 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.1.1 CLIP | ..................................................................................................................................................... 52 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.1.2 CLIR | ..................................................................................................................................................... 52 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.1.3 COLP | .................................................................................................................................................... 52 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.1.4 COLR | ................................................................................................................................................... 52 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.2 Call Hold (HOLD) | ..................................................................................................................................... 52 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.3 Call Waiting (CW) | ..................................................................................................................................... 53 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.4 Call Forwarding | ......................................................................................................................................... 53 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.5 Multi Party Service (MPTY) | ...................................................................................................................... 53 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.6 Closed User Group (CUG) | ......................................................................................................................... 53 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.7 Advice of Charge (AoC) | ............................................................................................................................ 53 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.8 Call Barring | ................................................................................................................................................ 54 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.9 Explicit Call Transfer (ECT) | ...................................................................................................................... 54 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.10 Completion of Calls to Busy Subscriber (CCBS) | ...................................................................................... 54 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.11 enhanced Multi-Level Precedence and Pre-emption (eMLPP) | .................................................................. 54 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.12 User-to-User Signalling (UUS) | .................................................................................................................. 55 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.8.13 Call Deflection (CD) | .................................................................................................................................. 55 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.9 Interaction with other services | ......................................................................................................................... 55 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.9.1 The Multi-Numbering Scheme | ................................................................................................................... 55 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.9.2 The Short Message Service | ........................................................................................................................ 55 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.9.3 Interactions with CAMEL | .......................................................................................................................... 55 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.9.4 Interactions with OR | .................................................................................................................................. 55 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.9.5 Operator Determined Barring | ..................................................................................................................... 56 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.9.6 Roaming Restrictions | ................................................................................................................................. 56 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.10 Data stored in the gsmSCF | .............................................................................................................................. 57 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11 Equivalent services implemented by the gsmSCF | ........................................................................................... 58 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.1 Call Forwarding | ......................................................................................................................................... 58 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.1.1 Call Forward Unconditional | ................................................................................................................. 60 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.1.2 Call Forward on Busy | ........................................................................................................................... 60 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.1.3 Call Forward on No Reply | .................................................................................................................... 61 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.1.4 Call Forward on Not Reachable | ........................................................................................................... 62 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.1.5 Early CFNRc | ........................................................................................................................................ 62 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.1.6 Late CFNRc | .......................................................................................................................................... 63 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.2 Call Barring | ................................................................................................................................................ 63 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.3 Operator Determined Barring (ODB) | ......................................................................................................... 64 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.11.4 Advice of Charge (AoC) | ............................................................................................................................ 64 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.12 Exceptional Procedures | .................................................................................................................................... 64 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.12.1 Roaming into a network not supporting CAMEL Phase 3 | ......................................................................... 64 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.12.2 Roaming into a network not supporting CAMEL Phase 2 | ......................................................................... 65 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.12.2.1 Actions required on Location Update | ................................................................................................... 65 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.12.2.2 MO call handling | .................................................................................................................................. 65 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.12.2.3 MT call handling | .................................................................................................................................. 65 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.12.2.4 MO short message handling | ................................................................................................................. 65 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.12.3 Lack of availability of the Network Indication of Alerting feature | ............................................................ 65 Annex A (informative): Provision and Withdrawal of MSP..............................................................66 A.1 Provision of MSP...................................................................................................................................66 A.2 Withdrawal of MSP ...............................................................................................................................66 Annex B (informative): Change history...............................................................................................67 ETSI ETSI TS 123 097 V3.1.1 (2000-04) 5 3G TS 23.097 version 3.1.1 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document defines the location management procedures within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 6 3G TS 23.097 version 3.1.1 Release 1999 1 Scope 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 References 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. [1] 3G TR 21.905: " 3G Vocabulary". [2] 3G TS 22.030: " Man Machine Interface (MMI) of the Mobile Station (MS)". [3] 3G TS 22.097: " Multiple Subscriber Profile (MSP) Service Description – Stage 1". [4] 3G TS 23.008: "Organisation of subscriber data". [5] 3G TS 23.015: "Technical realization of Operator Determined Barring (ODB)". [6] 3G TS 23.018: "Basic Call Handling – Technical Realization". [7] 3G TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) – Stage 2". [8] 3G TS 23.072: "Call Deflection (CD); Stage 2". [9] 3G TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) – Phase 3; Stage 2". [10] 3G TS 23.079: "Support of Optimal Routeing (SOR); Technical Realisation". [11] 3G TS 23.081: "Line identification supplementary services – Stage 2". [12] 3G TS 23.082: "Call Forwarding (CF) supplementary services – Stage 2". [13] 3G TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services – Stage 2". [14] 3G TS 23.084: "Multi Party (MPTY) supplementary services – Stage 2". [15] 3G TS 23.085: "Closed User Group (CUG) supplementary services – Stage 2". [16] 3G TS 23.086: "Advice of Charge (AoC) supplementary services – Stage 2". [17] 3G TS 23.087: "User-to-User (UUS) Supplementary Service; Stage 2". [18] 3G TS 23.088: "Call Barring (CB) supplementary services – Stage 2". [19] 3G TS 23.090: "Unstructured Supplementary Service Data (USSD) – Stage 2". [20] 3G TS 23.091: "Explicit Call Transfer (ECT) supplementary service – Stage 2". [21] 3G TS 23.093: "Technical Realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2". [22] 3G TS 24.086: "Advice of Charge (AoC) supplementary services – Stage 3". ETSI ETSI TS 123 097 V3.1.1 (2000-04) 7 3G TS 23.097 version 3.1.1 Release 1999 3 Definitions and abbreviations 3.1 Definitions 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 Abbreviations The abbreviations used in this specification are listed in 3G TR21.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 2 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. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 8 3G TS 23.097 version 3.1.1 Release 1999 5 Additional Information stored in network entities 5.1 Data stored in the HLR 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 subclause 7.6.8: Call Barring); - ODB Data (see subclause 7.7.5: Operator Determined Barring); - HOLD Data (see subclause 7.8.2: Call Hold); - ECT Data (see subclause 7.8.9: Explicit Call Transfer); - MPTY Data (see subclause 7.8.5: Multi Party); - CCBS Data (see subclause 7.8.10: Completion of Calls to Busy Subscriber); - CW Data (see subclause 7.8.3: Call Waiting); - CLIR Data (see subclause 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. 5.2 Data stored in the VLR 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 entities 6.1 OCB_flag 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. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 9 3G TS 23.097 version 3.1.1 Release 1999 6.2 ODB flags 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_flag 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_flag 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. 6.5 MPTY_flag 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_flag 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. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 10 3G TS 23.097 version 3.1.1 Release 1999 6.7 CCBS_flag 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. 6.8 CLIR_flag 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. 7 Description of Multiple Subscriber Profile 7.1 Overview The MSP service allows the served subscriber to have several profiles, to distinguish between different telecommunication service requirements (e.g. business and home). This is described in 3G TS 22.097. Subscriber data specific to MSP is stored in the HLR and the gsmSCF. 7.2 Registration of a Profile Registration of a profile allows the subscriber to register a provisioned profile to be used for mobile originated calls and activities. The request to register a profile shall contain the MSP code and the profile identity and will be sent to the gsmSCF using USSD, see 3G TS 23.078 and 3G TS 23.090. The registered profile is stored in the gsmSCF. In response to a successful registration request, the gsmSCF shall return a positive acknowledgement, including the identity of the registered profile, using USSD. The registration process in the gsmSCF is shown in figure 2. The information flow for successfully registering a profile is shown in figure 1. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 11 3G TS 23.097 version 3.1.1 Release 1999 MS MSC VLR HLR gsmSCF USSD Request (MSP code, Profile ID) USSD Request (MSP code, Profile ID) Process USS Request (MSP code, Profile ID) Process USS Request (MSP code, Profile ID) Process USS Request ack (Profile ID) Process USS Request ack (Profile ID) USSD Response (Profile ID) USSD Response (Profile ID) Figure 1: Registration Process: information flow ETSI ETSI TS 123 097 V3.1.1 (2000-04) 12 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to register a profile. Process Register_MSP_gsmSCF Reg_MSP_G_1(1) Signals to/from the left are to/from the HLR Idle Process USS Request (MSP code, Profile ID) MSP provisioned? Profile provisioned? Registered profile := Profile ID Process USS Request ack (Profile ID) Idle Error := Profile not provisioned Process USS Request ack (Error) Error := MSP not provisioned Yes Yes No No Figure 2: Process Register_MSP_gsmSCF 7.3 Interrogation The MS can interrogate MSP, using USSD, to identify which profiles are provisioned and which of the provisioned profiles is the currently registered profile. The interrogate MSP operation shall contain the MSP code and will be sent to the gsmSCF using USSD. In response to a successful interrogation request, the gsmSCF shall return the profile identity and profile status for each provisioned profile. If the MSP service is not provisioned then the gsmSCF shall return the service status indicating not provisioned. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 13 3G TS 23.097 version 3.1.1 Release 1999 The interrogation process is shown in figure 4. The information flow for interrogation of MSP is shown in figure 3. MS MSC VLR HLR gsmSCF USSD Request (MSP code) USSD Request (MSP code) Process USS Request (MSP code) Process USS Request (MSP code) Process USS Request ack (MSP info) Process USS Request ack (MSP info) USSD Response (MSP info) USSD Response (MSP info) Figure 3: Interrogating MSP: information flow ETSI ETSI TS 123 097 V3.1.1 (2000-04) 14 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to interrogate MSP. Process Interrogate_MSP_gsmSCF Int_MSP_G_1(1) Signals to/from the left are to/from the HLR Idle Process USS Request (MSP code) MSP provisioned? MSP info := (Default profile ID, Registered profile ID, Other provisioned profiles) Process USS Request ack (MSP info) Idle Error := MSP not provisioned Process USS Request ack (Error) Yes No Figure 4: Process Interrogate_MSP_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 15 3G TS 23.097 version 3.1.1 Release 1999 7.4 Call Handling for an MSP subscriber The procedure for handling MSP calls can be divided into two areas: mobile originating call handling and mobile terminating call handling. 7.4.1 Mobile Originating (MO) call handling The served subscriber may use the registered profile or explicitly select a provisioned profile to set up an MO call. If the profile is explicitly selected, the selection information will be included in the called party BCD number and transported to the gsmSCF. If the gsmSCF recognises that a profile has not been explicitly selected (there is no profile selection information in the called party BCD number) then the registered profile is used. The MMI for explicitly selecting a profile is defined in 3G TS 22.030. The information flow for an MO call is shown in figure 28. When the gsmSCF receives an Initial_DP message containing MO call parameters from the gsmSSF, the process MO_MSP_Call_gsmSCF will be invoked, see figure 5. All other call handling is described in 3G TS 23.018 and 3G TS 23.078. 7.4.2 Mobile Terminating (MT) call handling The profile used for an MT call to the served subscriber is determined by the called MSISDN. The information flow for an MT call is shown in figure 29. When the gsmSCF receives an Initial_DP message containing MT call parameters from the gsmSSF, the process MT_MSP_Call_gsmSCF will be invoked, see figure 8. All other call handling is described in 3G TS 23.018 and 3G TS 23.078. 7.5 Functions and Information Flows 7.5.1 MO call handling in the gsmSCF 7.5.1.1 Process MO_MSP_Call_gsmSCF Handles an MO call for an MSP subscriber. See figure 5. 7.5.1.2 Procedure Set_Calling_Profile_gsmSCF Sets the correct parameters for the calling profile. See figure 6. 7.5.1.3 Procedure Send_FCI_gsmSCF Sends a Furnish Charging Information message to the gsmSSF. See figure 7. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 16 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to handle an MO call for an MSP subscriber. Process MO_MSP_Call_gsmSCF MO_MCG_1(4) Signals to/from the left are to/from the gsmSSF. Idle Initial_DP (MO Parameters) Forwarded Call? Forwarded_MSP _Call_gsmSCF Idle Set_Calling_ Profile_gsmSCF Response_msg = Release? Outgoing_Barring_ Check_gsmSCF Result = Pass? Check_ACM _gsmSCF Result = Pass? Send_FCI_ gsmSCF 1 Release Call (Cause) Idle Yes No No Yes Yes No No Yes Figure 5a: Process MO_MSP_Call_gsmSCF (sheet 1 of 4) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 17 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to handle an MO call for an MSP subscriber. Process MO_MSP_Call_gsmSCF MO_MCG_2(4) Signals to/from the left are to/from the gsmSSF. 1 Request Report BCSM Event Contains: O_Answer as EDP-R O_Disconnect as EDP-N Check_CLIR _gsmSCF Check_CW _gsmSCF Check_HOLD _gsmSCF Check_MPTY _gsmSCF Check_ECT _gsmSCF Check_CCBS _gsmSCF 2 Figure 5b: Process MO_MSP_Call_gsmSCF (sheet 2 of 4) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 18 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to handle an MO call for an MSP subscriber. Process MO_MSP_Call_gsmSCF MO_MCG_3(4) Signals to/from the left are to/from the gsmSSF. Signals to/from the right are to/from the HLR. 2 SII2 = True? Response_msg = Connect? Continue Wait_for_Event_Report Event BCSM (Notify and Continue) This will be O_Disconnect Idle Event BCSM (Interrupted) This will be O_Answer 3 SS Invocation Notification (CCBS request) Wait_for_CCBS _Setup SS Invocation Notification (CCBS call setup) Store CCBS call information Cancel All Idle Connect Connect may contain Destination Routing Address, Generic Number and SII2 No No Yes Yes Figure 5c: Process MO_MSP_Call_gsmSCF (sheet 3 of 4) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 19 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to handle an MO call for an MSP subscriber. Process MO_MSP_Call_gsmSCF MO_MCG_4(4) Signals to/from the left are to/from the gsmSSF. Signals to/from the right are to/from the process AoC_MSP_gsmSCF. 3 Start AoC (Call Information) Wait_for_AoC_ack AoC ack Request Report BCSM Event (O_Disconnect) Continue Ongoing_call Event BCSM This will be O_Disconnect Call ended Idle Release call (Cause) Release call (Cause) Figure 5d: Process MO_MSP_Call_gsmSCF (sheet 4 of 4) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 20 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to set the correct parameters for the calling profile. Procedure Set_Calling_Profile_gsmSCF SCPG_1(1) Signals to/from the left are to/from the gsmSSF. Is profile explicitly selected in Called Party Number Calling profile := Registered profile Calling profile = Default profile? Set Additional Calling Party Number to MSISDN of Calling profile Response_msg := Connect Response_msg := Continue Calling profile := Selected profile Destination Routing Address := Called Party Number without explicit profile selection Calling profile = Default profile? No No Yes Yes No Yes Figure 6: Procedure Set_Calling_Profile_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 21 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to send a Furnish Charging Information message. Procedure Send_FCI_gsmSCF SFCIG_1(1) Signals to/from the left are to/from the gsmSSF. Set data for Furnish Charging Information Furnish Charging Information (Profile ID) Figure 7: Procedure Send_FCI_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 22 3G TS 23.097 version 3.1.1 Release 1999 7.5.2 MT call handling in the gsmSCF 7.5.2.1 Process MT_MSP_Call_gsmSCF Handles an MT call for an MSP subscriber. See figure 8. A process in the gsmSCF to handle an MT call for an MSP subscriber. Process MT_MSP_Call_gsmSCF MT_MCG_1(5) Signals to/from the left are to/from the gsmSSF. Idle Initial_DP (MT parameters) Set Called profile according to called MSISDN Check_CFU _gsmSCF Result = Continue? Incoming_Barring _Check_gsmSCF Result = Pass? Check_ACM _gsmSCF Result = Pass? Idle 1 Yes Yes No Yes No No Figure 8a: Process MT_MSP_Call_gsmSCF (sheet 1 of 5) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 23 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to handle an MT call for an MSP subscriber. Process MT_MSP_Call_gsmSCF MT_MCG_2(5) 1 Check_Early_CF _gsmSCF Send_FCI _gsmSCF Result = Continue? Idle Check_Late _CF_gsmSCF Check_CW _gsmSCF Check_HOLD _gsmSCF Check_MPTY _gsmSCF Check_ECT _gsmSCF Check_CCBS _gsmSCF 2 No Yes Figure 8b: Process MT_MSP_Call_gsmSCF (sheet 2 of 5) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 24 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to handle an MT call for an MSP subscriber. Process MT_MSP_Call_gsmSCF MT_MCG_3(5) Signals to/from the left are to/from the gsmSSF. 2 Check_CD _gsmSCF Does Called profile require specific Alerting Pattern? Set Alerting Pattern Connect Contains SII2 and/or Alerting pattern if applicable Wait_For_Event _Report SII2 = True? Continue Yes No No Yes Figure 8c: Process MT_MSP_Call_gsmSCF (sheet 3 of 5) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 25 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to handle an MT call for an MSP subscriber. Process MT_MSP_Call_gsmSCF MT_MCG_4(5) Signals to/from the left are to/from the gsmSSF. Wait_For_Event _Report Event BCSM (Notify and Continue) T_Abandon, T_Busy or T_No_Answer Cancel all Idle Event BCSM (Interrupted) T_Answer, T_Busy or T_No_Answer Event = T_Answer? 3 Event = T_No_Answer? Cause = Busy? Check_CFNRc _gsmSCF Result = Continue? Continue Idle Check_CFB _gsmSCF Check_CFNRy _gsmSCF Yes No No No Yes No Yes Yes Figure 8d: Process MT_MSP_Call_gsmSCF (sheet 4 of 5) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 26 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to handle an MT call for an MSP subscriber. Process MT_MSP_Call_gsmSCF MT_MCG_5(5) Signals to/from the left are to/from the gsmSSF. Signals to/from the right are to/from the process AoC_MSP_gsmSCF unless stated otherwise. 3 Start AoC (Call Information) Wait_for_AoC_ack AoC ack Continue Ongoing_Call Release call (Cause) Release call (Cause) Idle Event BCSM (Notify and Continue) This will be T_Disconnect Call ended Wait_For_Event _Report SS Notification Invocation (CD) From MSC Store CD call information Cancel All Idle Figure 8e: Process MT_MSP_Call_gsmSCF (sheet 5 of 5) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 27 3G TS 23.097 version 3.1.1 Release 1999 7.5.3 SS handling in the gsmSCF 7.5.3.1 Procedure Check_CLIR_gsmSCF Checks whether the CLI Presentation Indicator shall be set to Presentation Restricted. See figure 9. 7.5.3.2 Procedure Forwarded_MSP_Call_gsmSCF Sets the parameters for a forwarded or deflected call. See figure 10. 7.5.3.3 Procedure Check_CFU_gsmSCF Applies CFU to the MT Call if Active and Operative for the Called profile. See figure 11. 7.5.3.4 Procedure Check_Early_CF_gsmSCF Checks whether any early Call Forwarding apply to the Called profile. See figure 12 7.5.3.5 Procedure Check_Late_CF_gsmSCF Arms the detection points required for the provisioned late Call Forwardings on the Called profile. See figure 13. 7.5.3.6 Procedure Check_CFNRy_gsmSCF Applies CFNRy to the MT call if Active and Operative for the Called profile. See figure 14. 7.5.3.7 Procedure Check_CFB_gsmSCF Applies CFB to the MT call if Active and Operative for the Called profile. See figure 15. 7.5.3.8 Procedure Check_CFNRc_gsmSCF Applies CFNRc to the MT call if Active and Operative for the Called profile. See figure 16. 7.5.3.9 Procedure Check_CW_gsmSCF Checks whether CW is allowed during the current call. See figure 17. 7.5.3.10 Procedure Check_HOLD_gsmSCF Checks whether a HOLD request shall be accepted or rejected during the ongoing call. See figure 18. 7.5.3.11 Procedure Check_MPTY_gsmSCF Checks whether an MPTY request shallbe accepted or rejected during the ongoing call. See figure 19. 7.5.3.12 Procedure Check_ACM_gsmSCF Ensures that ACMmax is not exceeded for the profile in use. See figure 20. 7.5.3.13 Process AoC_MSP_gsmSCF Applies AoC per profile. See figure 21. 7.5.3.14 Procedure AoCI_gsmSCF Applies AoCI per profile. See figure 22. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 28 3G TS 23.097 version 3.1.1 Release 1999 7.5.3.15 Procedure AoCC_gsmSCF Applies AoCC per profile. See figure 23. 7.5.3.16 Procedure Outgoing_Barring_Check_gsmSCF Checks the outgoing call barrings for an MSP subscriber. See figure 24. 7.5.3.17 Procedure Incoming_Barring_Check_gsmSCF Checks the incoming barrings for the Called profile. See figure 25. 7.5.3.18 Procedure Check_ECT_gsmSCF Checks whether an ECT request shall be accepted or rejected during the ongoing call. See figure 26. 7.5.3.19 Procedure Check_CCBS_gsmSCF Checks whether a CCBS request can be planted by/against the MSP subscriber. See figure 27. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 29 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to set the CLI Presentation Indicator. Procedure Check_CLIR_gsmSCF C_CLIR_G_1(1) CLIR provisioned per profile? CLIR set to "Restricted" for calling profile? Calling Party Restriction Indicator := Presentation Restricted In SII2 SII2 := True Yes Yes No No Figure 9: Procedure Check_CLIR_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 30 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to set the correct parameters for a forwarded or deflected call. Procedure Forwarded_MSP_Call_gsmSCF FWD_MCG_1(1) Call Forwarding provisioned per subscriber? CD provisioned per subscriber? Retrieve stored CD Call Information Call Deflection A&O for Calling Profile? Send_FCI _gsmSCF Calling Profile = Default Profile? Set Additional Calling Party Number to MSISDN of Calling Profile Connect (Generic Number) Continue Set Cause Release Call (Cause) No No Yes No Yes Yes Figure 10: Procedure Forwarded_MSP_Call_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 31 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to apply CFU to the MT call if Active and Operative for the Called profile. Procedure Check_CFU_gsmSCF C_CFU_G_1(1) Signals to/from the left are to/from the gsmSSF. CFU provisioned per profile? CFU A&O for Called profile? Set CFU data Outgoing_Barring_ Check_gsmSCF Result = Pass? Result := Forward Connect (FTN, Original Called Party ID, Redirecting Info) Result := Release Result := Continue Release Call (Cause) Yes Yes Yes No No No Figure 11: Procedure Check_CFU_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 32 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to check if any early Call Forwardings apply to the called profile. Procedure Check_Early_CF_gsmSCF CECFG_1(1) Signals to/from the left are to/from the gsmSSF. Subscriber State = Not Reachable? Subscriber State = Busy? Subscriber State = CAMEL busy? Result := Continue Check_CFB _gsmSCF Result = Continue? Result := Forward Result := Release Set Cause Release Call (Cause) Check_CFNRc _gsmSCF Result = Continue? Result := Forward No No No Yes No Yes Yes Yes Yes No Figure 12: Procedure Check_Early_CF_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 33 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to arm the detection points required for the provisioned late Call Forwardings on the Called profile. Procedure Check_Late_CF_gsmSCF CLCFG_1(1) Signals to/from the left are to/from the gsmSSF. Arm_DP_List := (T_Answer as EDP-R T_Abandon as EDP-N) CFB A&O For Called profile? CFNRc A&O for Called profile? Add T_Busy to Arm_DP_List as EDP-N CFNRy A&O for Called profile? Add T_No_Answer to Arm_DP_List as EDP-N Request Report BCSM_Event (Arm_DP_List) Add T_No_Answer to Arm_DP_List as EDP-R Add T_Busy to Arm_DP_List as EDP-R No No No Yes Yes Yes Figure 13: Procedure Check_Late_CF_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 34 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to apply CFNRy to the MT call if Active and Operative for the Called profile. Procedure Check_CFNRy_gsmSCF C_CFNRy_G_1(1) Signals to/from the left are to/from the gsmSSF. CFNRy A&O for Called profile? Set CFNRy data Outgoing_Barring_ Check_gsmSCF Result = Pass? Result := Forward Connect (FTN, Original Called Party ID, Redirecting Info) Result := Release Result := Continue Release Call (Cause) Yes Yes No No Figure 14: Procedure Check_CFNRy_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 35 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to apply CFB to the MT call if Active and Operative for the Called profile. Procedure Check_CFB_gsmSCF C_CFB_G_1(1) Signals to/from the left are to/from the gsmSSF. CFB A&O for Called profile? Set CFB data Outgoing_Barring_ Check_gsmSCF Result = Pass? Result := Forward Connect (FTN, Original Called Party ID, Redirecting Info) Result := Release Result := Continue Release Call (Cause) Yes Yes No No Figure 15: Procedure Check_CFB_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 36 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to apply CFNRc to the MT call if Active and Operative for the Called profile. Procedure Check_CFNRc_gsmSCF C_CFNRc_G_1(1) Signals to/from the left are to/from the gsmSSF. CFNRc A&O for Called profile? Set CFNRc data Outgoing_Barring_ Check_gsmSCF Result = Pass? Result := Forward Connect (FTN, Original Called Party ID, Redirecting Info) Result := Release Result := Continue Release Call (Cause) Yes Yes No No Figure 16: Procedure Check_CFNRc_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 37 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to check if CW is provisioned for the current profile. Procedure Check_CW_gsmSCF C_CW_G_1(1) CW provisioned per profile? CW A&O for current profile? CW Treatment Indicator := CW Not Allowed In SII2 SII2 :=True Yes No Yes No Figure 17: Procedure Check_CW_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 38 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to check if HOLD is provisioned for the current profile. Procedure Check_HOLD_gsmSCF C_HOLD_G_1(1) HOLD provisioned per profile? HOLD A&O for current profile? HOLD Treatment Indicator := Reject HOLD Request In SII2 SII2 :=True Yes No Yes No Figure 18: Procedure Check_HOLD_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 39 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to check if MPTY is provisioned for the current profile. Procedure Check_MPTY_gsmSCF C_MPTY_G_1(1) MPTY provisioned per profile? MPTY A&O for Current profile? Conference Treatment Indicator := Reject Conference Request In SII2 SII2 := True Yes No Yes No Figure 19: Procedure Check_MPTY_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 40 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to ensure that ACMmax is not exceeded for the profile in use. Procedure Check_ACM_gsmSCF C_ACM_G_1(1) Signals to/from the left are to/from the gsmSSF. AoCC A&O for current profile? Call chargeable to MSP subscriber? ACM >= ACMmax? Result := Pass Result := Fail Set Cause Release Call (Cause) Yes Yes No Yes No No Figure 20: Procedure Check_ACM_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 41 3G TS 23.097 version 3.1.1 Release 1999 A process in the gsmSCF to apply AoC per profile. Process AoC_MSP_gsmSCF AoC_MG_1(1) Signals to/from the left are to/from the process MO_MSP_Call_gsmSCF or the process MT_MSP_Call_gsmSCF. Idle Start AoC (Call Information) AoCI A&O for profile? AoCC A&O for profile? AoCC_gsmSCF Idle AoC ack AoCI_gsmSCF No Yes No Yes Figure 21: Process AoC_MSP_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 42 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to apply AoCI per profile. Procedure AoCI_gsmSCF AoCI_G_1(1) Signals to/from the right are to/from the process MO_MSP_Call_gsmSCF or the process MT_MSP_Call_gsmSCF. Start charge calculations AoC ack AoCI_active Call ended Stop charging calculations Figure 22: Procedure AoCI_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 43 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to apply AoCC per profile. Procedure AoCC_gsmSCF AoCC_G_1(1) Signals to/from the left are to/from the process MO_MSP_Call_gsmSCF or the process MT_MSP_Call_gsmSCF. Signals from the right are internal. Start charge calculations AoC ack AoCC_active ACM >= ACMmax Set Cause Release call (Cause) Call ended Stop charging calculations Figure 23: Procedure AoCC_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 44 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to check the outgoing call barrings for an MSP subscriber. Procedure Outgoing_Barring_Check_gsmSCF OBCG_1(1) Signals to/from the left are to/from the gsmSSF. ODB applicable to current profile? BAOC applicable to current profile? BOIC-exHC applicable to current profile? BOIC applicable to current profile? Set Cause Result := Fail Result := Pass No No No Yes No Yes Yes Yes Figure 24: Procedure Outgoing_Barring_Check_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 45 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to check the incoming barrings for the called profile. Procedure Incoming_Barring_Check_gsmSCF IBCG_1(1) Signals to/from the left are to/from the gsmSSF. ODB applicable to Called profile? BAIC applicable to Called profile? BIC-roam applicable to Called profile? Set Cause Result := Fail Release Call (Cause) Result := Pass No No Yes No Yes Yes Figure 25: Procedure Incoming_Barring_Check_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 46 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to check if ECT is provisioned for the current profile. Procedure Check_ECT_gsmSCF C_ECT_G_1(1) ECT provisioned per profile? ECT A&O for current profile? ECT Treatment Indicator := Reject ECT Request In SII2 SII2 :=True Yes No Yes No Figure 26: Procedure Check_ECT_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 47 3G TS 23.097 version 3.1.1 Release 1999 A procedure in the gsmSCF to check if CCBS is provisioned for the current profile. Procedure Check_CCBS_gsmSCF C_CCBS_G_1(1) CCBS provisioned per profile? MO call? Calling profile can plant CCBS? Call Completion Treatment Indicator := Reject Call Completion Service Request SII2 :=True Called profile can be a CCBS target? Yes Yes Yes No No No Yes No Figure 27: Procedure Check_CCBS_gsmSCF ETSI ETSI TS 123 097 V3.1.1 (2000-04) 48 3G TS 23.097 version 3.1.1 Release 1999 7.5.4 Information flows The information flow for a successful MO call by an MSP subscriber is shown in figure 28. The information flow for a successful MT call to an MSP subscriber is shown in figure 29. MS MSC VLR gsmSSF gsmSCF Destination Network Setup SIFOC Complete call (O-CSI) Call proceeding Invoke gsmSSF gsmSSF invoked DP_Collected_Info Initial_DP (MO parameters) Furnish Charging Information (Profile ID) Continue / Connect (Generic Number, SII2) Continue / Connect (Generic Number, SII2) Progress SIFOC Complete call Initial Address Message Figure 28: Information flow for a successful MO call ETSI ETSI TS 123 097 V3.1.1 (2000-04) 49 3G TS 23.097 version 3.1.1 Release 1999 GMSC HLR gsmSSF gsmSCF VLR Terminating MSC Send Routing Info Provide Subscriber Info Obtain Subscriber Info Obtain Subscriber Info ack Provide Subscriber Info ack Send Routing Info ack (T-CSI) Invoke gsmSSF gsmSSF invoked DP_Termination_Attempt_Authorised Initial DP (MT parameters) Furnish Charging Information (Profile ID) Continue / Connect (Alerting Pattern, SII2) Continue / Connect (Alerting Pattern, SII2) Send Routing Info (Suppress T-CSI, Alerting Pattern) Provide Roaming Number (Alerting Pattern) Provide Roaming Number ack Send Routing Info ack (MSRN) Initial Address Message Figure 29: Information flow for a successful MT call to a profile that has no Call Forwardings Active and Operative in the gsmSCF NOTE: For information flows to a profile that has Call Forwarding services Active and Operative in the gsmSCF, see subclause7.11.1: Call Forwarding. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 50 3G TS 23.097 version 3.1.1 Release 1999 7.6 SMS handling MSP Phase 2 does not apply to MT short messages. The MSP subscriber will receive MT short messages but no profile indication will be given. When the gsmSCF receives an Initial SMS Event message from the gsmSSF, the process MO_MSP_SMS_gsmSCF will be invoked, see figure 30. A process inthe gsmSCF to handle an MO short message for an MSP subscriber. Process MO_MSP_SMS_gsmSCF MO_MSG_1(2) Signals to/from the left are to/from the gsmSSF. Idle Initial SMS Event Is profile explicitly selected in Destination Subscriber address? SMS sender := Registered profile SMS sender = Default profile? Set Calling Party Number to MSISDN of SMS sender Response_msg := Connect 1 Response_msg := Continue SMS sender := Selected profile Remove Profile ID from Destination Subscriber Address SMS sender = Default profile? No No Yes Yes No Yes Figure 30a: Process MO_MSP_SMS_gsmSCF (sheet 1 of 2) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 51 3G TS 23.097 version 3.1.1 Release 1999 A process inthe gsmSCF to handle an MO short message for an MSP subscriber. Process MO_MSP_SMS_gsmSCF MO_MSG_2(2) Signals to/from the left are to/from the gsmSSF. 1 Outgoing_Barring _Check_gsmSCF Result = Pass? Furnish SMS Charging Information (Profile ID) Response_msg = Connect? Continue SMS Idle Connect SMS Contains Calling Party Number and/or Destination Subscriber Address Release SMS (Cause) Yes No Yes No Figure 30b: Process MO_MSP_SMS_gsmSCF (sheet 2 of 2) ETSI ETSI TS 123 097 V3.1.1 (2000-04) 52 3G TS 23.097 version 3.1.1 Release 1999 7.7 Call Independent SS handling Supplementary Services provisioned per subscriber will be handled in the usual way. Supplementary Services provisioned per profile will be controlled using USSD, sent via the VLR and HLR to the gsmSCF. If Call Barring is provisioned per profile, if the outgoing call barring data for the default profile is changed, the HLR shall be informed using Any Time Modification. On receipt of an Any Time Modification message from the gsmSCF for a subscriber with the OCB_flag set, the HLR will modify the stored Call Barring information for the default profile in accordance with the information in the Any Time Modification message. 7.8 Interaction with Supplementary Services 7.8.1 Line Identification services 7.8.1.1 CLIP No interaction. 7.8.1.2 CLIR CLIR can be provisioned per subscriber or per profile. If CLIR is provisioned per subscriber and CLIR is active, it will be active for all profiles. Data for the CLIR Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. CLIR will function as specified in 3G TS 23.081 and will not distinguish between MSP and non-MSP subscribers. If CLIR is provisioned per profile then the CLIR_flag shall be set in the HLR (see subclause 6.8: CLIR_flag) and the CLIR subscription information for the default profile shall be stored in the HLR in the usual manner. For an MO call, if the CLIR subscription information for the Calling profile indicates that the CLI shall be restricted, the gsmSCF shall set the Calling Party Presentation Indicator to Presentation Restricted in the SII2 parameter. 7.8.1.3 COLP No interaction. 7.8.1.4 COLR No interaction. 7.8.2 Call Hold (HOLD) Call Hold can be provisioned per subscriber or per profile. If Call Hold is provisioned per subscriber and Call Hold is active, it will be active for all profiles. Data for the Call Hold Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. Call Hold will function as specified in 3G TS 23.083 and will not distinguish between MSP and non-MSP subscribers. If Call Hold is provisioned per profile then the HOLD_flag shall be set in the HLR (see subclause 6.3: HOLD_flag). On receipt of an Initial_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If HOLD is not active and operative, then the SII2 will be included in the Connect message with the HOLD Treatment Indicator set to Reject HOLD Request. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 53 3G TS 23.097 version 3.1.1 Release 1999 7.8.3 Call Waiting (CW) Call Waiting can be provisioned per subscriber or per profile. If Call Waiting is provisioned per subscriber and Call Waiting is active, it will be active for all profiles. Data for the Call Waiting Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. Call Waiting will function as specified in 3G TS 23.083 and will not distinguish between MSP and non-MSP subscribers. If Call Waiting is provisioned per profile then the CW_flag shall be set in the HLR (see subclause 6.4: CW_flag). On receipt of an Initial_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If Call Waiting is not active and operative, then the SII2 will be included in the Connect message with the CW Treatment Indicator set to CW Not Allowed. The subscriber shall be able to modify CW information per profile by making contact with the gsmSCF using USSD. However, the subscriber shall not be able to modify CW data for the default profile. 7.8.4 Call Forwarding The Call Forwarding Supplementary Services, described in 3G TS 23.082, can only be provisioned per subscriber. However, services equivalent to the Call Forwarding Supplementary Services, implemented in the gsmSCF, will be available to the MSP subscriber per profile. This is described in subclause 7.11.1: Call Forwarding. If the Call Forwarding Supplementary Services are provisioned per subscriber, then Call Forwarding will function as specified in 3G TS 23.082 and will not distinguish between MSP and non-MSP subscribers. NOTE 1: If Call Forwarding is provisioned per subscriber in the HLR then Call Forwarding should not be provisioned per profile in the gsmSCF, as this may cause unpredictable behaviour. NOTE 2: If Call Forwarding is provisioned per subscriber in the HLR then Call Deflection should not be provisioned per profile in the gsmSCF, as this may cause unpredictable behaviour. 7.8.5 Multi Party Service (MPTY) The Multi Party Supplementary Service can be provisioned per subscriber or per profile. If MPTY is provisioned per subscriber and MPTY is active, it will be active for all profiles. Data for the MPTY Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. MPTY will function as specified in 3G TS 23.084 and will not distinguish between MSP and non-MSP subscribers. If MPTY is provisioned per profile then the MPTY_flag shall be set in the HLR (see subclause 6.5: MPTY_flag). On receipt of an Initial_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If MPTY is not active and operative, then the SII2 will be included in the Connect message with the Conference Treatment Indicator set to Reject Conference Request. 7.8.6 Closed User Group (CUG) The Closed User Group Supplementary Service can be provisioned per subscriber or per profile. If CUG is provisioned per subscriber and CUG is active, it will be active for all profiles. Data for the CUG Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. CUG will function as specified in 3G TS 23.085 and will not distinguish between MSP and non-MSP subscribers. The interaction between CAMEL and CUG is defined in 3G TS 23.078. CUG provisioning per profile is supported by CAMEL Phase 3 and is FFS. 7.8.7 Advice of Charge (AoC) The Advice of Charge Supplementary Service can be provisioned per subscriber. However, services equivalent to the Advice of Charge supplementary services, implemented in the gsmSCF, will be available to the MSP subscriber per profile. This is described in subclause 7.11.4: Advice of Charge (AoC). Signalling on the access interface will be as specified in 3G TS 24.086. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 54 3G TS 23.097 version 3.1.1 Release 1999 If AoC is active, it will be active for all profiles. Data for the AoC Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. AoC will function as specified in 3G TS 23.086 and will not distinguish between MSP and non-MSP subscribers. 7.8.8 Call Barring The Call Barring Supplementary Services, described in 3G TS 23.088, can only be provisioned per subscriber. However, services equivalent to the Call Barring Supplementary Services, implemented in the gsmSCF, can be provided to the MSP subscriber per profile. This is described in subclause 7.11.2: Call Barring. This requires the OCB_flag mechanism described in section subclause 6.1: OCB_flag. 7.8.9 Explicit Call Transfer (ECT) The Explicit Call Transfer supplementary service can be provisioned per subscriber or per profile. If ECT is provisioned per subscriber and ECT is active, it will be active for all profiles. Data for the ECT Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. ECT will function as specified in 3G TS 23.091 and will not distinguish between MSP and non-MSP subscribers. If ECT is provisioned per profile then the ECT_flag shall be set in the HLR (see subclause 6.6: ECT_flag). On receipt of an Initial_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call leg. If ECT is not active and operative, then the SII2 will be included in the Connect message with the ECT Treatment Indicator set to Reject ECT Request. 7.8.10 Completion of Calls to Busy Subscriber (CCBS) CCBS can be provisioned per subscriber or per profile. If CCBS is provisioned per subscriber and CCBS is active, it will be active over all profiles. Data for the CCBS Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. If CCBS is provisioned per profile then the CCBS_flag shall be set in the HLR (see subclause 6.7: CCBS_flag). On receipt of an Initial_DP message for an MO call, the gsmSCF will check the subscription information for the calling profile. If CCBS is not active and operative, then the SII2 will be included in the Connect message with the Call Completion Treatment Indicator set to Call Completion Not Allowed. On receipt of an Initial_DP message for an MT call, the gsmSCF will check the subscription information for the called profile. If CCBS is not active and operative, then the SII2 will be included in the Connect message with the Call Completion Treatment Indicator sent to Call Completion not allowed. The subscriber shall be able to modify CCBS information per profile by making contact with the gsmSCF using USSD. However, the subscriber shall not be able to modify CCBS data for the default profile. If a CFU-equivalent service is activated while there are queue entries in MS-B's target queue, HLR-B will not know about this activation and will process these queue entries as normal. As a consequence, the CCBS calls related to these queue entries will be forwarded to the new destination. CCBS activation is not possible if this forwarded call meets NDUB. This results in expiry of recall timer T9 and deletion of the queue entry from MS-B's target queue. For further details on the interaction between CCBS and CAMEL, refer to 3G TS 23.093. The same applies to Incoming Call Barring-equivalent services which are activated while there are queue entries in MS- B's target queue. An MSP subscriber will have CCBS set in the SS-CSI. The gsmSCF will be informed of CCBS Request and CCBS Setup messages for the MSP subscriber. This allows the service logic in the gsmSCF to assign the correct profile to the CCBS call. 7.8.11 enhanced Multi-Level Precedence and Pre-emption (eMLPP) eMLPP will be provisioned per subscriber. If eMLPP is active, it will be active for all profiles. Data for the eMLPP Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. eMLPP will function as specified in 3G TS 23.067 and will not distinguish between MSP and non-MSP subscribers. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 55 3G TS 23.097 version 3.1.1 Release 1999 7.8.12 User-to-User Signalling (UUS) The User-to-User Supplementary Service will be provisioned per subscriber. If UUS is active, it will be active for all profiles. Data for the UUS Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. UUS will function as specified in 3G TS 23.087 and will not distinguish between MSP and non-MSP subscribers. 7.8.13 Call Deflection (CD) The Call Deflection Supplementary Service will be provisioned per subscriber. If CD is active, it will be active for all profiles. Data for the CD Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. CD will function as specified in 3G TS 23.072 and will not distinguish between MSP and non-MSP subscribers. When the MSP subscriber deflects an MT call, it triggers an interrogation of the gsmSCF for an MO Call. Using the call reference number, the gsmSCF can recognise that there is an ongoing dialogue for the MT call, and can then retrieve the profile to apply for the deflected call. This gives the gsmSCF the opportunity to reject the call deflection per profile, providing the MSP subscriber is in a supporting network. NOTE: Call Deflection should not be provisioned per profile if Call Forwardings are provisioned per subscriber in the HLR as unpredictable behaviour may occur. 7.9 Interaction with other services 7.9.1 The Multi-Numbering Scheme If the MSP subscriber has different MSISDNs allocated for different Basic Services, all MSISDNs and associated Basic Services will be stored in the HLR. Each MSISDN and associated Basic Services will also be stored in the gsmSCF with associated profile ID. 7.9.2 The Short Message Service Mobile terminated short messages can be received on any profile although the profile will not be indicated to the user. It shall be possible to select a profile for mobile originated short messages. If a profile is explicitly selected, the MO short message will be sent by and charged to the selected profile. If a profile is not explicitly selected, the MO short message will be sent by and charged to the registered profile. 7.9.3 Interactions with CAMEL An MSP subscriber will, by definition, have a CAMEL subscription. If other CAMEL services are designed in such a way that an MSP subscriber can use them, they will be available to the MSP subscriber. It is a network option to design CAMEL services that interact with MSP. 7.9.4 Interactions with OR The GMSC in the Interrogating PLMN (IPLMN) needs to support CAMEL Phase 2 capability if the called subscriber is an MSP subscriber. If an interrogation request is received for an MSP subscriber from a GMSC in the IPLMN that does not support the CAMEL Phase 2 capability, the HLR shall return an OR not allowed negative response (see 3G TS 23.079) to the GMSC. This will force the call to be routed to a GMSC supporting CAMEL Phase 2 capabilitity in the HPLMN. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 56 3G TS 23.097 version 3.1.1 Release 1999 7.9.5 Operator Determined Barring ODB, as described in 3G TS 23.015, can only be provisioned per subscriber. A service, implemented in the gsmSCF equivalent to the ODB service will be available for an MSP subscriber per profile. This is described in subclause 7.11.3: Operator Determined Barring (ODB); it requires the mechanism described in subclause 6.2: ODB flags.. Outgoing ODB for the default profile will be stored in the HLR for use when the subscriber roams into a non- supporting network, see subclause 7.11.3: Roaming into a network not supporting CAMEL Phase 2 for further details. 7.9.6 Roaming Restrictions Roaming Restrictions will apply per subscriber. Data for the Roaming Restrictions will be stored in the HLR in the usual manner. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 57 3G TS 23.097 version 3.1.1 Release 1999 7.10 Data stored in the gsmSCF The gsmSCF contains all the data needed to control the MSP service. These data can be divided into the common data (the data valid for all profiles) and the profile specific data. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 58 3G TS 23.097 version 3.1.1 Release 1999 7.11 Equivalent services implemented by the gsmSCF 7.11.1 Call Forwarding Call Forwarding services will be provided in the gsmSCF per profile. An MT call to an MSP subscriber will be subject to the provided call forwardings for the called profile. The Call Forwarding services, implemented by the gsmSCF, should operate in the same way as the Call Forwarding Supplementary Services. The MSP subscriber should have control over the call forwarding data (Registration, Erasure, Activation, Deactivation, and Interrogation). The method for controlling this data is a network option. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 59 3G TS 23.097 version 3.1.1 Release 1999 GMSC HLR gsmSSF gsmSCF VLR Termintating MSC Send Routing Info Provide Subscriber Info Obtain Subscriber Info Obtain Subscriber Info ack Provide Subscriber Info ack Send Routing Info ack (T-CSI) Invoke gsmSSF gsmSSF invoked DP_Termination_Attempt_Authorized Initial_DP (MT parameters) Furnish Charging Information (Profile ID) Request_Report_BCSM_Event (see Note) Continue / Connect (Alerting Pattern, SII2) Continue / Connect (Alerting Pattern, SII2) Send Routing Info (Alerting Pattern) Provide Roaming Number (Alerting Pattern) Provide Roaming Number ack (MSRN) Send Routing Info ack (MSRN) Initial Address Message NOTE: Request_Report_BCSM_Event will contain the list Arm_DP_List (see figure 1). This list will contain the following elements: T_Answer EDP-N T_Abandon EDP-N T_Busy EDP-N (Unless CFB and/or CFNRc are A&O for the called profile, in which case EDP-R) T_No_Answer EDP-N (Unless CFNRy is A&O for the called profile, in which case EDP-R) Figure 31: Information flow for a successful MT call to a profile with some Call Forwardings Active and Operative ETSI ETSI TS 123 097 V3.1.1 (2000-04) 60 3G TS 23.097 version 3.1.1 Release 1999 7.11.1.1 Call Forward Unconditional GMSC gsmSSF gsmSCF Invoke gsmSSF (T-CSI) gsmSSF Invoked DP_Termination_Attempt_Authorized Initial_DP (MT parameters) Furnish Charging Information (Profile ID) Connect (FTN) Connect (FTN) Figure 32: Information flow for an MT call to a profile with CFU active and operative in the gsmSCF 7.11.1.2 Call Forward on Busy GMSC gsmSSF gsmSCF MSC Initial Address Message Release (Busy) DP_T_Busy Event Report BCSM (interrupted) Connect (FTN) Connect (FTN) Figure 33: Information flow for an MT call to a profile with CFB active and operative in the gsmSCF, where the called subscriber is NDUB or UDUB ETSI ETSI TS 123 097 V3.1.1 (2000-04) 61 3G TS 23.097 version 3.1.1 Release 1999 7.11.1.3 Call Forward on No Reply GMSC gsmSSF gsmSCF MSC Initial Address Message Address Complete Message TNRy Expired Release DP_T_No_Answer Event Report BCSM (interrupted) Connect (FTN) Connect (FTN) NOTE: The timer TNRy is started in the GMSC after the Address Complete Message has been received from the destination exchange. If this timer expires before an Answer message is received from the destination exchange, a release message is sent to the destination exchange and the detection point T_No_Answer is reached. This is specified in 3G TS 23.018 and 3G TS 23.078. Figure 34: Information flow for an MT call to a profile with CFNRy active and operative in the gsmSCF, where the called party does not answer ETSI ETSI TS 123 097 V3.1.1 (2000-04) 62 3G TS 23.097 version 3.1.1 Release 1999 7.11.1.4 Call Forward on Not Reachable 7.11.1.5 Early CFNRc Early Call Forwarding on Not Reachable will apply if the gsmSCF receives the parameter "subscriber state" set as Not Reachable. Due to the presence of the Location information / Subscriber state Interrogation parameter in the CAMEL data, stored in the HLR, the HLR sends a Provide Subscriber Information message to the VLR. This determines if the subscriber state is Not Reachable. GMSC HLR gsmSSF gsmSCF VLR Destination MSC Send Routing Information Provide Subscriber Info Obtain Subscriber Info Obtain Subscriber Info ack (Network Determined Not Reachable) Provide Subscriber Info ack (Network Determined Not Reachable) ting Information ack (Network Determined Not Reachable) Invoke gsmSSF (T-CSI) gsmSSF Invoked DP_Termination_Attempt_Authorized Initial_DP (MT parameters) Furnish Charging Information (Profile ID) Connect (FTN) Connect (FTN) Figure 35: Information flow for an MT call to a profile with CFNRc active and operative in the gsmSCF, where early CFNRc is invoked ETSI ETSI TS 123 097 V3.1.1 (2000-04) 63 3G TS 23.097 version 3.1.1 Release 1999 7.11.1.6 Late CFNRc GMSC gsmSSF gsmSCF MSC Initial Address Message Release (Not Reachable / Other (any other cause except "Busy")) DP_T_Busy (Release Cause) Event Report BCSM (interrupted) Connect (FTN) Connect (FTN) Figure 36: Information flow for an MT call to a profile with CFNRc active and operative in the gsmSCF, where late CFNRc is invoked 7.11.2 Call Barring Call Barring services can be provided by the gsmSCF per profile. An MO call made by an MSP subscriber will be subject to the outgoing call barrings provided for the Calling profile. An MT call to an MSP subscriber will be subject to the incoming call barrings provided for the Called profile. If an MT call to an MSP subscriber is forwarded, the forwarded call will be subject to the outgoing call barrings provided for the Called profile. The Call Barring services available per profile are: - Barring of all outgoing calls (BAOC); - Barring of outgoing international calls (BOIC); - Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC); - Barring of all incoming calls (BAIC); - Barring of incoming calls when roaming outside the home PLMN country (BIC-roam). The Call Barring services, implemented by the gsmSCF, should operate in the same way as the Call Barring Supplementary Services. The MSP subscriber should have control over the call barring data (Registration, Erasure, Activation, Deactivation, and Interrogation). The method for controlling this data is a network option. If the MSP subscriber changes the Outgoing Call Barrings for the default profile by contacting the gsmSCF, the gsmSCF will change the barrings stored in the gsmSCF and inform the HLR using ATM to change the barrings stored in the HLR. The Call Barring Supplementary Services may require a password before Call Barring data can be changed. For the Call Barring Services implemented in the gsmSCF, use of a password is a network option. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 64 3G TS 23.097 version 3.1.1 Release 1999 The operator should ensure that if the equivalent call barring service is provided then: - the OCB_flag is set in the HLR (See subclause 6.1:OCB_flag); - if an equivalent outgoing call barring service is in a "Provisioned and Active" state in the gsmSCF for the default profile, that outgoing call barring supplementary service will be in a "Provisioned and Active" state in the HLR; - if an equivalent outgoing call barring service is in a "Not Active" state in the gsmSCF for the default profile, that outgoing call barring supplementary service will be in a "Not Provisioned" state in the HLR; - incoming Call Barrings shall not be provisioned in the HLR; NOTE: Barrings will not apply to MT short messages. 7.11.3 Operator Determined Barring (ODB) Operator Determined Barring will be available per profile in the gsmSCF for the following categories: - Barring of outgoing calls; - Barring of incoming calls; - Barring of roaming; - Barring of outgoing Premium Rate Calls; - Barring specific to the home PLMN; - Barring of registration of call forwarding; - Barring of invocation of call transfer. However, if zone related barring is implemented in the gsmSCF, the appropriate data will be needed in the gsmSCF as well as the HLR. For barring of incoming calls when roaming outside the zone of the home country, the gsmSCF will need to use Any Time Interrogation to establish the location of the called party. Management of ODB data is operator specific. The operator should ensure that if the equivalent ODB service for an ODB category is provided then: - the ODB flag for the correct category is set in the HLR (See subclause 6.2: ODB flags); - the ODB data for that category for the default profile is duplicated in the HLR. NOTE: Barring of incoming calls in the gsmSCF will not disallow MO or MT short messages. 7.11.4 Advice of Charge (AoC) Advice of Charge is available per profile in the gsmSCF. This is detailed in the SDL diagrams in Section 7.5: Functions and Information flows. 7.12 Exceptional Procedures 7.12.1 Roaming into a network not supporting CAMEL Phase 3 When roaming into a network not supporting CAMEL Phase 3, only the functionality of MSP Phase 1 will be available to an MSP subscriber. The default profile subscription information shall apply to all supplementary services, excluding Call Forwarding and Call Barring, provisioned per profile. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 65 3G TS 23.097 version 3.1.1 Release 1999 7.12.2 Roaming into a network not supporting CAMEL Phase 2 This subclause details MSP specific handling for roaming into a network not supporting CAMEL Phase 2. Other handling for this scenario is described in 3G TS 23.078. 7.12.2.1 Actions required on Location Update The HLR will send the outgoing call barring data and outgoing ODB data, specific to the default profile, to the VLR. 7.12.2.2 MO call handling When an MSP subscriber roams into a network not supporting CAMEL Phase 2, the default profile will be used for all outgoing traffic. 7.12.2.3 MT call handling MT calls to any profile will be received by the subscriber (subject to call forwardings and call barrings provided in the gsmSCF on the called profile), although no indication of the called profile will be received. The HLR will not allow OR, this means that for MT calls, the GMSC will always support CAMEL Phase 2, allowing the gsmSCF to invoke appropriate Call Forwardings and Call Barrings. 7.12.2.4 MO short message handling MO short messages will be sent from and charged to the default profile. If an MSP subscriber roams into a network not supporting the Network Indication of Alerting feature, or is using an MS that does not support the Network indication of Alerting feature, then the subscriber will still receive all MT calls, but no indication of the called profile will be given. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 66 3G TS 23.097 version 3.1.1 Release 1999 Annex A (informative): Provision and Withdrawal of MSP A.1 Provision of MSP MSP will be provisioned by prior arrangement with the service provider. For an existing subscriber converting to an MSP subscriber, all profile specific data will be stored in the gsmSCF and removed from the HLR, and MSP will be provisioned in the HLR. For a new subscriber provisioned with the MSP service, all profile specific data will be stored in the gsmSCF and MSP will be provisioned in the HLR. Data specific to the Default Profile will be stored in both the HLR and the gsmSCF. A.2 Withdrawal of MSP MSP will be withdrawn when there is only one profile remaining. In this event, the subscriber data will be stored in the HLR and removed from the gsmSCF, and the HLR will remove all MSP markings. The subscriber will then be treated as a normal subscriber. ETSI ETSI TS 123 097 V3.1.1 (2000-04) 67 3G TS 23.097 version 3.1.1 Release 1999 Annex B (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 03.97 7.1.0 Transferred to 3GPP CN CN#04 23.097 3.0.0 CN#05 23.097 3.0.0 001 3.0.1 Various editorial corrections CN#06 23.097 3.0.1 002 R99 3.1.0 Inclusion of MSP Phase 2 functionality CN#06 23.097 3.0.1 003 R99 3.1.0 Interaction MSP and CF CN#07 23.097 3.1.0 004 R99 3.1.1 Minor editorial corrections 68 ETSI ETSI TS 123 097 V3.1.1 (2000-04) 3G TS 23.097 version 3.1.1 Release 1999 History Document history V3.1.1 April 2000 Publication |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 0 Scope | ........................................................................................................................................................5 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 0.1 References | .......................................................................................................................................................... 5 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 0.2 Abbreviations | ..................................................................................................................................................... 5 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1 Advice Of Charge (Information) (AoCI) | .................................................................................................5 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.1 Definition | ........................................................................................................................................................... 5 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.2 Description | ......................................................................................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.2.1 Description | ................................................................................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.2.2 Applicability to telecommunication services | ............................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.3 Normal procedures with successful outcome | ..................................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.3.1 Provision | ...................................................................................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.3.2 Withdrawal | ................................................................................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.3.5 Activation | ..................................................................................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.3.6 Deactivation | ................................................................................................................................................. 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.3.7 Invocation | ..................................................................................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.3.8 Normal operation with successful outcome | ................................................................................................. 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.4 Exceptional procedures or unsuccessful outcome | .............................................................................................. 7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.4.1 Operation in a PLMN that is unable to support AoC | ................................................................................... 7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.4.2 AoC when MS is switched off or out of coverage | ....................................................................................... 7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.4.3 Operation with a MS unable to support AoC | ............................................................................................... 7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.5 Alternate procedures | .......................................................................................................................................... 7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.6 Interactions with other supplementary services | ................................................................................................. 7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 1.7 Interworking considerations | ............................................................................................................................... 6 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2 Advice Of Charge (Charging) (AoCC) | ....................................................................................................7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.1 Definition | ........................................................................................................................................................... 7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.2 Description | ......................................................................................................................................................... 8 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.2.1 Description | ................................................................................................................................................... 7 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.2.2 Applicability to telecommunication services | ............................................................................................... 8 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.3 Normal procedures with successful outcome | ..................................................................................................... 8 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.3.1 Provision | ...................................................................................................................................................... 8 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.3.2 Withdrawal | ................................................................................................................................................... 8 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.3.5 Activation | ..................................................................................................................................................... 8 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.3.6 Deactivation | ................................................................................................................................................. 8 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.3.7 Invocation | ..................................................................................................................................................... 8 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.3.8 Normal operation with successful outcome | ................................................................................................. 9 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.4 Exceptional procedures or unsuccessful outcome | .............................................................................................. 9 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.4.1 Operation in a PLMN that is unable to support the Charging Service | ......................................................... 9 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.4.2 Charging when the MS is switched off or out of coverage | .......................................................................... 9 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.4.3 Operation with a MS unable to support AoC | ............................................................................................... 9 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.5 Alternate procedures | .......................................................................................................................................... 9 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.6 Interactions with other supplementary services | ................................................................................................. 9 |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 2.7 Interworking considerations | ............................................................................................................................... 8 Annex A (informative): Change history...............................................................................................10 History..............................................................................................................................................................11 3G TS 22.086 version 3.1.0 Release 1999 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 4 3G TS 22.086 version 3.1.0 Foreword This Technical Specification has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; 3G TS 22.086 version 3.1.0 Release 1999 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 5 3G TS 22.086 version 3.1.0 0 Scope The present document describes the supplementary services belonging to the group Charging Supplementary Services. The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004. Charging services are the supplementary services associated with charging aspects. The group of supplementary services Charging Supplementary Services comprises two services: - Advice of Charge (Information) - clause 1; - Advice of Charge (Charging) - clause 2. Advice of Charge (AoC) supplementary services will use the Charge Advice Information described in 22.024. In principle, the same type of Mobile Station (MS) can be used for both services of Advice of Charge (AoC), except where the application demands special features - e.g. the payment mechanism in a payphone. Only one of these services may be subscribed to at any one time. 0.1 References 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. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004: General on supplementary services". [3] TS 22.024Description of Charge Advice Information (CAI). [4] TS 21.905: "Vocabulary for 3GPP Specifications". [5] TS 22.135: "Multicall stage 1". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04 and TS 21.905. 1 Advice Of Charge (Information) (AoCI) 1.1 Definition This service permits MS to display an accurate estimate the size of the bill which will eventually be levied in the Home PLMN. 3G TS 22.086 version 3.1.0 Release 1999 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 6 3G TS 22.086 version 3.1.0 1.2 Description 1.2.1 Description This supplementary service provides the MS with the information to produce an estimate of the cost of the service used. Charges are indicated for the call(s) in progress when mobile originated or for the roaming leg only when mobile terminated. Any charges for non-call related transactions, and for certain supplementary services, such as Call Forwarding are not indicated. The MS will receive at the beginning of each call (and as necessary during the call) a message, the Charge Advice Information. This message contains the elements which together define the rate at which the call is to be charged, time dependence, data dependence and for unit increments - see TS 22.024. The MS shall still indicate appropriate charges even when roaming, based on Home PLMN units. Where applicable, the volume charge for Packet data service, in addition to the normal time dependent and incremental charges, shall be indicated. To indicate the charge per call the Mobile station shall display the units consumed so far during the present call(s) and maintain this value until the MS is switched off or a new call set-up is attempted. Where required to indicate the total accumulated charge, the MS shall be able to display, and the SIM/USIM shall store in the ACM, the running cumulative unit charge. This value must be stored securely, and all reasonable steps shall be taken to ensure that the written value cannot be interrupted, reset or corrupted (except resetting under control of the unblocking key). 1.2.2 Applicability to telecommunication services The applicability of this supplementary service is defined in TS 22.004. 1.3 Normal procedures with successful outcome 1.3.1 Provision This supplementary service will be provided after prearrangement with the service provider. 1.3.2 Withdrawal This service will be withdrawn at the subscriber's request or for administrative reasons. 1.3.5 Activation This supplementary service will be activated by the service provider as a result of provision. 1.3.6 Deactivation This supplementary service will be deactivated by the service provider as a result of withdrawal. 1.3.7 Invocation This supplementary service will be automatically invoked by the network for the use of all applicable telecommunications services. 1.3.8 Normal operation with successful outcome For every applicable usage of telecommunications services, the served MS will be provided with charging information. 3G TS 22.086 version 3.1.0 Release 1999 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 7 3G TS 22.086 version 3.1.0 The MS shall send to the network a confirmation of receipt of this information. 1.4 Exceptional procedures or unsuccessful outcome 1.4.1 Operation in a PLMN that is unable to support AoC Since AoC (Information) is used only to provide an indication to the user, even if the network is unable to support AoC, calls may still be set up as normal, only the AoC indication will not be given. For this reason charges incurred on a network that is unable to support AoC will not be shown on the AoC indicator. 1.4.2 AoC when MS is switched off or out of coverage No AoC information is given by the network. 1.4.3 Operation with a MS unable to support AoC Since AoC (Information) is used only to provide an indication to the user, even if the ME is unable to support AoC, calls may still be set up as normal, only no AoC information will be provided to the user. 1.5 Alternate procedures None identified. 1.6 Interactions with other supplementary services No interaction. Invocation of this supplementary service does not prevent use of any other Supplementary Service. |
710eec07b0a2dd46f7d1997a4c21303f | 122 086 | 8.2 Multicall | See TS 22.135 [5]. 1.7 Interworking considerations When interworking with PSPDN, a volume related charge may be incurred, as described in TS 22.024. 2 Advice Of Charge (Charging) (AoCC) 2.1 Definition This service provides the means by which the MS may indicate the charge that will be made for the use of telecommunication services. It is intended for applications where the user is generally not the subscriber but is known to the subscriber, and where the user pays the subscriber, rather than the Service Provider. The charge information is based as closely as possible on the charge that will be levied on the subscriber's bill in the Home PLMN. Where this charge cannot be stored in the MS, use of the telecommunications service shall be prevented as described below. 3G TS 22.086 version 3.1.0 Release 1999 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 8 3G TS 22.086 version 3.1.0 2.2 Description 2.2.1 Description This supplementary service provides the MS with the information to produce an estimate of the cost of the service used. Charges are indicated for the call(s) in progress when mobile originated or for the roaming leg only when mobile terminated. Any charges for non-call related transactions, and for certain supplementary services, such as Call Forwarding are not indicated. The MS will receive at the beginning of each call (and as necessary during the call) a message, the Charge Advice Information. This message contains the elements which together define the rate at which the call is to be charged, time dependence, data dependence and for unit increments - see TS 22.024. The MS shall still indicate appropriate charges even when roaming, based on Home PLMN units. Where applicable, the volume charge for Packet data service, in addition to the normal time dependent and incremental charges, shall be indicated. To indicate the charge per call the Mobile station shall display the units consumed so far during the present call(s) and maintain this value until the MS is switched off or a new call set-up is attempted. Where required to indicate the total accumulated charge, the MS shall be able to display, and the SIM/USIM shall store in the ACM, the running cumulative unit charge. This value must be stored securely, and all reasonable steps shall be taken to ensure that the written value cannot be interrupted, reset or corrupted (except resetting under control of the unblocking key). 2.2.2 Applicability to telecommunication services The applicability of this supplementary service is defined in TS 22.004. 2.3 Normal procedures with successful outcome 2.3.1 Provision This supplementary service will be provided after pre-arrangement with the service provider. 2.3.2 Withdrawal This service will be withdrawn at the subscriber's request or for administrative reasons. 2.3.5 Activation This supplementary service will be activated by the service provider as a result of provision. 2.3.6 Deactivation This supplementary service will be deactivated by the service provider as a result of withdrawal. 2.3.7 Invocation This supplementary service will be automatically invoked by the network for the use of all applicable telecommunications services. 3G TS 22.086 version 3.1.0 Release 1999 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 9 3G TS 22.086 version 3.1.0 2.3.8 Normal operation with successful outcome For every applicable usage of telecommunication services, the served MS will be provided with charging information. The MS shall send to the network a confirmation of receipt of this information. 2.4 Exceptional procedures or unsuccessful outcome 2.4.1 Operation in a PLMN that is unable to support the Charging Service If the local PLMN is unable to support this service, all chargeable calls shall be prevented. This is determined either by the use of an HLR list of VPLMNs which support the service, or by the HLR interrogating the VPLMN. Prevention is achieved by refusing a Location Update Request to the VPLMN that does not support the service. 2.4.2 Charging when the MS is switched off or out of coverage No AoC information is given by the network. 2.4.3 Operation with a MS unable to support AoC If the MS does not support AoC, no advice of charge information will be provided to the user. Any calls attempted to be set up will be quickly terminated, once the network has failed to receive a positive acknowledgement of receipt of the Charge Advice Information, within a suitable time. 2.5 Alternate procedures None identified. 2.6 Interactions with other supplementary services No interaction. Invocation of this supplementary service does not prevent use of any other Supplementary Service, but in certain cases no charging information will be indicated. In this case, the subscriber should not subscribe to those Supplementary Services which need to be charged for, thereby inhibiting their use by another user. 2.7 Interworking considerations When interworking with PSPDN, a volume related charge may be incurred, as described in TS 22.024. 3G TS 22.086 version 3.1.0 Release 1999 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 10 3G TS 22.086 version 3.1.0 Annex A (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.86 7.0.0 Transferred to 3GPP SA1 SA#04 22.085 3.0.0 SA#05 22.085 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. 3G TS 22.086 version 3.1.0 Release 1999 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 11 3G TS 22.086 version 3.1.0 History Document history V3.0.0 August 1999 Transferred to TSG SA at ETSI SMG#29. Under TSG TSG SA Change Control. V3.1.0 October 1999 Inclusion of CR at SA#05 3G TS 22.086 version 3.1.0 Release 1999 12 ETSI ETSI TS 122 086 V3.1.0 (2000-03) 3G TS 22.086 version 3.1.0 Release 1999 History Document history V3.1.0 March 2000 Publication |
ffe40b581fcac51ed6037bc4a10e59c9 | 123 066 | 1 Scope | ........................................................................................................................................................6 |
ffe40b581fcac51ed6037bc4a10e59c9 | 123 066 | 2 References | ................................................................................................................................................6 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.