hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
3 Definitions and abbreviations
|
..................................................................................................................7
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
3.1 Definitions
|
......................................................................................................................................................... 7
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
3.2 Abbreviations
|
..................................................................................................................................................... 8
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
4 General
|
.....................................................................................................................................................9
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
4.1 Overview
|
............................................................................................................................................................ 9
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
4.2 Compatibility
|
................................................................................................................................................... 10
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
4.3 Common Functionality of the MNP-SRF
|
........................................................................................................ 10
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
5 Common Architecture for call setup
|
......................................................................................................14
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
6 Functional requirements of network entities
|
..........................................................................................16
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
6.1 Procedure MNP_MT_GMSC_Set_MNP_Parameters
|
..................................................................................... 16
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
6.2 Procedure MNP_MT_GMSC_Check_MNP_Indicators
|
.................................................................................. 17
|
ffe40b581fcac51ed6037bc4a10e59c9
|
123 066
|
6.3 Procedure MNP_SRF_Check_MNP_Indicator
|
............................................................................................... 18 Annex A (normative): IN Call-Related Technical Realisation ........................................................19 A.1 Architecture ...........................................................................................................................................19 A.1.1 Network Options.............................................................................................................................................. 19 A.1.2 No NP Query required – Number is not subject for portability....................................................................... 19 A.1.3 NP Query in Number Range Holder Network................................................................................................. 20 A.1.3.1 TQoD – Number is not ported.................................................................................................................... 20 A.1.3.2 TQoD – Number is ported.......................................................................................................................... 21 A.1.3.3 QoHR – Number is ported ......................................................................................................................... 23 A.1.4 NP Query in Originating Network................................................................................................................... 24 A.1.4.1 OQoD – Number is not ported ................................................................................................................... 24 A.1.4.2 OQoD – Number is ported ......................................................................................................................... 25 A.2 Information flows ..................................................................................................................................26 A.3 Functional requirements of network entities..........................................................................................32 A.3.1 Functional requirement of GMSC ................................................................................................................... 32 A.3.1.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR.................................................................. 32 A.3.1.2 Procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD.................................................................. 34 A.3.2 Functional requirement of MSC ...................................................................................................................... 36 A.3.2.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD ................................................................. 36 A.3.3 Functional requirement of NPDB .................................................................................................................... 38 A.3.3.1 Process IN_QUERY_NPDB...................................................................................................................... 38 A.4 Contents of messages.............................................................................................................................39 A.4.1 Messages on the ISUP interface ...................................................................................................................... 39 A.4.1.1 IAM for ETSI ISUP interface .................................................................................................................... 39 A.4.1.2 IAM for ANSI ISUP interface.................................................................................................................... 39 A.4.2 Messages on the MSC - NPDB interface......................................................................................................... 39 A.4.2.1 INITIAL DP............................................................................................................................................... 39 A.4.2.2 INITIAL DP negative response.................................................................................................................. 40 A.4.2.3 CONNECT................................................................................................................................................. 40 A.4.2.4 CONTINUE ............................................................................................................................................... 40 A.4.2.5 RELEASE CALL....................................................................................................................................... 40 A.4.2.6 ProvideInstruction:Start ............................................................................................................................. 40 A.4.2.7 ConnectionControl:Connect....................................................................................................................... 41 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 4 3G TS 23.066 version 3.3.0 Release 1999 Annex B (normative): Handling of Non-Call Related Signalling....................................................42 B.1 Handling of Non-call Related Signalling...............................................................................................42 B.1.1 Routeing Conventions...................................................................................................................................... 42 B.1.2 Network Architecture ...................................................................................................................................... 42 B.2 Signalling Scenarios ..............................................................................................................................44 B.2.1 Non-call Related Signalling Message for a Non-ported Number – Indirect Routeing .................................... 44 B.2.2 Non-call Related Signalling Message for a Ported or Non-ported Number – Direct Routeing ....................... 45 B.2.3 Non-call Related Signalling Message for a Ported Number - Indirect Routeing............................................. 46 B.3 Functional Requirements of Network Entities.......................................................................................46 B.3.1 Procedure MNP_SRF_Non_Call_Related....................................................................................................... 46 B.4 Signalling Scenarios (informative) ........................................................................................................49 B.4.1 Delivery of SMS to a Non-ported Number – Direct Routeing – MNP-SRF acts as SCCP Relay ................... 49 B.4.2 Delivery of SMS to a Non-ported Number - Direct Routeing – MNP-SRF acts as Higher-level Relay.......... 50 B.4.3 Delivery of SMS to a Ported Number – Indirect Routeing.............................................................................. 51 B.4.4 Delivery of SMS to a Ported Number – Direct Routeing ................................................................................ 52 B.4.5 International SOR for a Non-ported Number .................................................................................................. 53 B.4.6 SOR for a Ported Number – Indirect Routeing................................................................................................ 54 B.4.7 Any Time Interrogation for a Ported Number – Indirect Routeing.................................................................. 55 B.4.8 Any Time Interrogation for a Ported Number – Direct Routeing .................................................................... 56 B.4.9 CCBS where the Busy Subscriber is a Ported Subscriber - Direct Routeing................................................... 57 B.4.10 Calling Name Presentation Flows – MNP-SRF acts as SCCP Relay .............................................................. 58 Annex C (normative): MNP Signalling Relay Function - Call Related Signalling ........................59 C.1 Handling of Call Related Signalling......................................................................................................59 C.2 Functional Requirements of Network Entities.......................................................................................60 C.2.1 Procedure MNP_SRF_MATF_Call_Related................................................................................................... 60 C.2.2 Process SRI_NPLR.......................................................................................................................................... 60 C.3 Call Scenarios ........................................................................................................................................64 C.3.1 Call to a Non-Ported Number or Number Ported into the Network................................................................. 64 C.3.2 Call to a Ported Number – Originating Network = Subscription Network – Direct Routeing......................... 65 C.3.3 Mobile Originated Call to a Ported or not known to be Ported Number – Originating Network ≠Subscription Network– Direct Routeing........................................................................................................ 66 C.3.4 Call to a Ported Number – Indirect Routeing .................................................................................................. 67 C.3.5 Call to a Ported Number – Indirect Routeing with Reference to Subscription Network ................................. 68 C.4 Information Flows..................................................................................................................................69 C.5 Contents of the messages.......................................................................................................................75 C.5.1 Send Routeing Info.......................................................................................................................................... 75 C.5.2 Send Routeing Info ack.................................................................................................................................... 75 C.6 Handling of MAP to ISUP mapping (informative)................................................................................75 C.6.1 ETSI Mapping direction: ISUP to MAP.......................................................................................................... 75 C.6.2 ETSI Mapping direction: MAP to ISUP.......................................................................................................... 75 C.6.3 ANSI Mapping direction: ISUP to MAP......................................................................................................... 76 C.6.4 ANSI Mapping direction: MAP to ISUP......................................................................................................... 76 Annex D (informative): Change history...............................................................................................77 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 5 3G TS 23.066 version 3.3.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document specifies alternatives for the realisation of Mobile Number Portability within the digital cellular telecommunications 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 066 V3.3.0 (2000-06) 6 3G TS 23.066 version 3.3.0 Release 1999 1 Scope The present document describes several alternatives for the realisation of Mobile Number Portability. The present document includes information applicable to network operators, service providers, switch and database manufacturers and national regulators. It is left to operator and implementation decisions which option, or combination of options, is used, taking into account the regulatory and architectural constraints that may prevail. The possible implications of these options on internal node functions and on signalling performance are not covered in the present document. Normative Annex A of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using IN technology. Normative Annex C of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using Signalling Relay technology. Normative Annex A and Normative Annex C describe alternative solutions. The network operator may choose the solution to be used in his network. Normative Annex B of the present document describes the technical realisation of the handling of non-call related SCCP signalling for ported UMTS or GSM mobile subscribers using Signalling Relay technology. The present document does not specify the porting process. 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 TS 21.905: "3G Vocabulary". [2] 3G TS 22.066: "Support of Mobile Number Portability (MNP); Service description. Stage 1". [3] 3G TS 23.018: "Basic call handling; Technical realisation". [4] ETS 300 009 (1991): "Integrated Services Digital Network (ISDN); CCITT Signalling System No. 7 – Signalling Connection Control Part (SCCP) [connectionless services] to support international interconnection". [5] ETS 300 374-1: "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1: protocol specification". [6] ITU-T Recommendation Q.769.1; ISDN User Part (ISUP); Enhancements for the support of Number Portability". [7] draft EN 300 356-2 V4.0.0: "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 4 for the international interface; Part 2: ISDN supplementary services [ITU-T Recommendation Q.730 modified]". [8} CTIA report on Wireless Number Portability, Version 2.0.0. [9] ANSI T1.660 – 1998, American National Standards for Telecommunications – Signaling System Number 7 – NumberPortability Call Completion to a Portable Number. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 7 3G TS 23.066 version 3.3.0 Release 1999 [10] ANSI T1.111-1996, American National Standards for Telecommunication – Signalling System No. 7 (SS7) Message Transfer Part (MTP). [11] ANSI T1.112-1996, American National Standards for Telecommunication – Signalling System No. 7 (SS7) Signalling Connection Control Part (SCCP). NOTE: Translation Types 10 and 14 will be published in the next revision of ANSI T1.112. [12] American National Standard for Telecommunications – Signalling System Number 7 (SS7) - ISDN User Part (ISUP) - ANSI T1.113-1995. [13] American National Standard for Telecommunications - Signalling System Number 7 (SS7) – Transaction Capabilities Application Part (TCAP) - ANSI T1.114-1996. [14] draft EN 302 097 V1.1.2 (1999): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP); Enhancements for support of Number Portability (NP)". [15] TI - Technical Requirements No. 3, April 1999, Number Portability Database and Global Title Translation. [16] GSM 03.96 (TS 101 395): "Digital cellular telecommunications system (Phase 2+); Mobile Name Identification Supplementary Service – Stage 2 ". [17] North American Numbering Council (NANC) Functional Requirement Specification, Number Portability Administration Center- Service Management System (NPAC-SMS), Version 1.0, May 25, 1995; Version 2.0, June 2, 1997. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. donor network: subscription network from which a number is ported in the porting process. This may or may not be the number range holder network interrogating network entity: entity that submits a non-call related signalling message to interrogate the HLR interrogating network: network in which the interrogating network entity resides mobile number portability: ability for a mobile subscriber to change mobile network subscription within the same country whilst retaining his/her original MSISDN(s). Additional regulatory constraints apply in North America. network operator: GSM PLMN operator non-call related signalling message: all signalling messages where the MSISDN is used to route the message on SCCP level except MAP SRI without OR parameter set (i.e. SRI_SMS, SRI for SOR, Send_IMSI, CCBS_Request etc) North American GSM Number portability: the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within a regulated geographical area within North America. number portability database: operational database (used in real time at call set-up) which provides portability information number portability location register: internal MAP application terminating function (MATF) in the MNP-SRF network entity with an (unspecified) interface with a NPDB number range holder network: network to which the number range containing the ported number has been allocated originating network: network where the calling party is located ETSI ETSI TS 123 066 V3.3.0 (2000-06) 8 3G TS 23.066 version 3.3.0 Release 1999 portability domain: set of GSM PLMNs in a country between which MSISDNs may be ported or a set of North American GSM Mobile networks and other subscription networks within a regulated geographical area within North America portability network: a PLMN or ,in North America, a PSTN or an ISDN network portable number: E.164 number that can be ported between networks in one nation ported number: portable number that has undergone the porting process ported subscriber: subscriber of a ported number porting process: description of the transfer of a number between network operators recipient network: network that receives the number in the porting process. This network becomes the subscription network when the porting process is complete routeing number: routeing number is the data stored against the ported number in the Number Portability Database service key: service Key can identify to the entity holding the Number Portability Database that the service logic for Mobile Number Portability should apply. The Service Key value for Mobile Number Portability is administered in the MSC, and is passed transparently to the entity holding the Number Portability Database service provider: entity that offers service subscriptions to individual subscribers and contracts with a network operator to implement services for a specific MSISDN. A service provider may contract with more than one network operator service provider portability: transfer of numbers between two unique Service Providers subscription network: network with which the customer’s Service Provider has a contract to implement the customer’s services for a specific MSISDN NOTE: The term “recipient network” is used during the porting process. The recipient network becomes the ”subscription network” after the completion of the porting process. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CCBS Call Completion on Busy Subscriber CCF Call Completion Function CdPA Called Party Address CgPA Calling Party Address CNAP Calling Name Presentation CNDB Calling Name Database CRMNP Call Related Mobile Number Portability FCI Forward Call Indicator GAP Generic Address Parameter GMSC Gateway MSC GMSCB The GMSC in HPLMNB GTT Global Title Translation HLR Home Location Register HPLMNB The subscription network of the B subscriber IAM Initial Address Message IDP Initial Detection Point IE Information Element INE Interrogating Network Entity IF Information Flow IPLMN Interrogating PLMN MATF MAP application Terminating Function MNP Mobile Number Portability MNP-SRF Signalling Relay Function for support of MNP MSA Mobile Station of the A subscriber MSB Mobile Station of the B subscriber MSC Mobile-services Switching Centre ETSI ETSI TS 123 066 V3.3.0 (2000-06) 9 3G TS 23.066 version 3.3.0 Release 1999 MSISDN Mobile Station International ISDN Number MSRN Mobile Station Roaming Number NANP North American Numbering Plan NAGNP North American GSM Number Portability NPDB Number Portability Database NPLMN The number range holder network of the B subscriber NPLR Number Portability Location Register OQoD Originating call Query on Digit Analysis PLMN Public Land Mobile Network QoHR Query on HLR Release RN Routeing Number SMS Short Message Service SOR Support of Optimal Routeing SRI Send Routeing Information STP Signalling Transfer Point TQoD Terminating call Query on Digit Analysis TT Translation Type VMSC The Visited MSC VMSCB The VMSC of the B subscriber Further GSM related abbreviations are given in 3G TS 21.905: "3G Vocabulary". 4 General 4.1 Overview Mobile Number Portability (MNP) is the ability for a UMTS or GSM mobile subscriber to change the subscription network within a portability domain whilst retaining her original MSISDN or MSISDNs. North American GSM Number Portability (NAGNP) is the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within a regulated geographical area within North America. As part of the porting process administrative actions have to be performed by the network operators of the number range holder network, donor network, recipient network and, as an option, by operators of other national UMTS or GSM networks as follows: a) if the number range holder network is identical with the donor network: Recipient network: add an entry in the HLR; add an entry in the Number Portability Database. Donor network: add an entry in the Number Portability Database; delete the entry related to the ported MSISDNs in the HLR. Other networks in the portability domain: add an entry in the Number Portability Database (if direct routeing is used). b) if the number range holder network is identical with the recipient network: Recipient network: add an entry in the HLR; delete any entry related to the ported MSISDN in the Number Portability Database. Donor network: delete any entry related to the ported MSISDN in the Number Portability Database; delete the entry related to the ported MSISDNs in the HLR. Other networks in the portability domain: delete any entry related to the ported MSISDN in the Number Portability Database. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 10 3G TS 23.066 version 3.3.0 Release 1999 c) if the number range holder network is different from both the recipient and the donor network: Recipient network: add an entry in the HLR; add an entry in the Number Portability Database. Number range holder network: update the Number Portability Database Donor network: delete (or update) the entry in the Number Portability Database; delete the entry related to the ported MSISDNs in the HLR. Other networks in the portability domain: update the Number Portability Database (if an entry for the ported MSISDN exists). Note that the order of sequence for the administrative actions to be performed both within a network and by different network operators is significant with respect to prevention of disruption in service to the mobile subscriber and prevention of looping calls between networks during the porting process. Termination of a subscription for a ported number results in the deletion of any entry in an HLR and NPDB of that number. If a call fails because databases are not correctly synchronised, the network entity that detects the inconsistency will raise an MNP specific alarm to the operation and maintenance subsystem. The present document does not specify the porting process. It specifies the functionality needed to set-up calls to both ported and non ported subscribers (Normative Annex A and Normative Annex C) and the functionality needed to relay non-call related signalling messages to the HLR in the subscription network (Normative Annex B). 4.2 Compatibility The IAM sent to the subscription network may contain additional routeing information. Within a portability domain the method how to convey the Routeing Number in the IAM between two portability networks shall be agreed upon by the two network operators involved (for an ITU-T ISUP solution see [6] and for an ANSI ISUP solution see [8] and [9]). In general, IN-based and MNP-SRF (call-related) solutions are compatible and may coexist in the same portability domain. The only restriction refers to the case where the number range holder network relays call-related MAP messages (i.e. SRI for national calls) to the subscription network. If this solution is selected by at least one network operator within a portability domain, all the portability networks and transit networks affected must fulfil the following requirements: 1. The SCCP interfaces between networks in a portability domain must be agreed. This refers to the SCCP addressing mechanism being used (e.g. number lengths, natures of address and translation types for call-related MAP messages). For messages that do not cross network boundaries the SCCP addressing mechanism is a choice of the network operator. 2. The subscription network must be able to generate the SRI ack to allow the onward routeing of the call from the number range holder network to the subscription network. In the rest of the possible architectures for MNP, no interworking problems have been identified. In these cases, network architectures used within one portability network (e.g. IN, MNP-SRF) are regarded as operator dependent. In order to avoid loops and incompatibility situations, all the networks within a portability domain shall use the same routeing convention either direct routeing, indirect routeing or indirect routeing with reference to the Subscription network. As an alternative, indirect routeing can interwork successfully with direct routeing if the routeing number is transferred in the IAM or if dedicated traffic connections are used. 4.3 Common Functionality of the MNP-SRF In a PLMN that supports mobile number portability, SCCP messages sent to an HLR may be relayed by an MNP-SRF. Depending on the implemented solution (IN-based or MNP-SRF-based), on the type of message (call-related or non- call-related) and on the porting status of the called subscriber, the MNP-SRF may modify the SCCP called party address and route the message to a different HLR or to the subscription network, or terminate the dialogue and response to the INE. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 11 3G TS 23.066 version 3.3.0 Release 1999 Figure 1 shows the general steering functionality for SCCP message routeing. It shows the SCCP routeing principle for mobile number portability within a network. Note that call related messages in the IN-based solution are not routed to the MNP-SRF. Therefore Normative Annex A of the present document does not mention the MNP-SRF. However, the usage of the IN-based solution for the call-related messages should allow operators to have the routeing of the non call-related messages determined in the same database. See [7] for the description of the access of the MNP- SRF (node with relay capability) to the NPDB (external database). In order to guard against the possibility that the porting data for an MSISDN is inconsistent between PLMNs in a porting domain, the SCCP hop counter may be used to prevent indefinite looping of messages between PLMNs. The MNP-SRF would then decrement the SCCP hop counter for every message that is relayed. It should be noted that the use of the SCCP hop counter requires the use of non segmented SCCP XUDT messages as defined in ITU-T 1996 SCCP recommendations or in the ANSI T1.112-1996 SCCP recommendations for North America, reference [11]. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 12 3G TS 23.066 version 3.3.0 Release 1999 general Steering Function for SCCP routeing Process SCCP_Steering_Function 1(1) Idle SCCP message OPTION call related SCCP message to HLR SCCP message to MNP-SRF SCCP message to MNP-SRF Idle Idle Idle IN-based MNP-SRF-based yes no Figure 1: Steering Function for SCCP Message routeing Figure 2 shows the process MNP_SRF in the MNP-SRF. The procedures MNP_SRF_MATF_Call_Related and MNP_SRF_Non_Call_Related are described in Normative Annex C and Normative Annex B of the present document. Note that in networks which support the IN-based solution for call related signalling, a distinction on SCCP level for call related and non-call related messages is needed and that the MNP-SRF does not require to include a MATF since call related messages are not routed to the MNP-SRF. The test "call-related" is a test on the SCCP Translation Type if a dedicated Translation Type value for call related messages is used in the network. The handling of SCCP messages in the MNP-SRF in networks which do not make use of a dedicated Translation Type value for call related messages is for further study. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 13 3G TS 23.066 version 3.3.0 Release 1999 Process in the MNP_SRF to relay SCCP messages Process MNP_SRF 1(1) IDLE SCCP message call-related MNP_SRF_MAT_ Call_Related see Normative Annex C terminate? IDLE MNP_SRF_Non_ Call_Related see Annex D SCCP message SCCP message IDLE IDLE yes no yes no terminate? IDLE yes no Figure 2: Process MNP_SRF ETSI ETSI TS 123 066 V3.3.0 (2000-06) 14 3G TS 23.066 version 3.3.0 Release 1999 5 Common Architecture for call setup Figure 3 shows the general architecture of a portability domain for routeing of calls. The more detailed architecture within the networks depends on the chosen solution (IN-based or MNP/SRF-based) and options and is described in Normative Annex A and Normative Annex C of the present document. The architecture for non-call related signalling is described in Normative Annex B of the present document. Other national network IAM (6) IAM (7) IAM (3) IAM(1) Number range holder network Subscription network SRI (4) SRI ack (5) IAM (2) IAM (8) Portability domain Figure 3: General architecture of a portability domain for routeing of calls The following routeing conventions are identified: 1. Direct Routeing of calls is a PLMN option that allows to route calls directly from the PLMN supporting this option to the ported subscriber's subscription network. 2. Indirect Routeing of calls is a PLMN option which allows to route calls from the PLMN supporting this option via the number range holder network to the ported subscriber's subscription network. 3. Indirect Routeing of calls with reference to the subscription network is a PLMN option for PLMN operators having chosen the MNP-SRF solution for call related signalling described in Normative Annex C. If all PLMNs within a portability domain support this option, calls are routed from the originating network to the number range holder network. The number range holder network obtains onward routeing information from the subscription network and routes the call onward to the ported subscriber's subscription network. The following action in the different networks can be identified: 1. If the call is originated outside the portability domain, the IAM (1) is received by the number range holder network. 2a. If the call is originated in another national network and the other national network does not support originating call query (i.e. Indirect Routeing of calls is applicable), the IAM (2) is received by the number range holder network. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 15 3G TS 23.066 version 3.3.0 Release 1999 2b. If the call is originated in another national network and the other national network supports originating call query (i.e. Direct Routeing of calls is applicable), the IAM (7) containing the routeing number is sent to the subscription network. If the routeing number is not used in the IAM sent from the national originating network to the subscription network, all transit networks involved are required to look up an NPDB in order to retrieve routeing information to route the call to the subscription network without looping. 3a. If the call is originated in the subscription network and the subscription network does not support originating call query (i.e. Indirect Routeing of calls is applicable), the IAM (3) is received by the number range holder network. 3b. If the call is originated in the subscription network and the subscription network supports originating call query (i.e. Direct Routeing of calls is applicable), it sends an IAM (8) containing the MSRN to the visited network of the called subscriber. 3c. If the subscription network receives IAM (6 or 7) containing the routeing number, it sends an IAM (8) containing the MSRN to the visited network of the called subscriber. 4a. If the call is routed via the number range holder network, and the number range holder network supports the MNP-SRF/MATF solution with the option 'MATF in subscription network' described in Normative Annex C of the present document (i.e. Indirect Routeing of calls with reference to the subscription network is applicable), the number range holder network sends SRI (4) to the subscription network. The subscription network returns SRI ack (5) containing the routeing number. The number range holder network then sends IAM (6) containing the routeing number to the subscription network. If the routeing number is not used in the IAM sent from the number range holder network to the subscription network, all transit networks involved are required to look up an NPDB in order to retrieve routeing information to route the call to the subscription network without looping. 4b. If the call is routed via the number range holder network, and the number range holder network supports the IN solution described in Normative Annex A of the present document or the MNP-SRF/MATF solution with the option 'MATF inside number range holder network' described in Normative Annex C of the present document, the number range holder network sends IAM (6) containing the routeing number to the subscription network. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 16 3G TS 23.066 version 3.3.0 Release 1999 6 Functional requirements of network entities 6.1 Procedure MNP_MT_GMSC_Set_MNP_Parameters The procedure MNP_MT_GMSC_Set_MNP_Parameters is shown in figure 4. It is called from the process MT_GMSC defined in 3G TS 23.018 [3]. Procedure MNP_MT_GMSC_Set_MNP_Parameters 1(1) IAM parameters indicate that NPDB query has been done Mark NPDB query done Yes No Figure 4: Procedure MNP_MT_GMSC_Set_MNP_Parameters ETSI ETSI TS 123 066 V3.3.0 (2000-06) 17 3G TS 23.066 version 3.3.0 Release 1999 6.2 Procedure MNP_MT_GMSC_Check_MNP_Indicators The procedure MNP_MT_GMSC_Check_MNP_Indicators is shown in figure 5. It is called from the process MT_GMSC defined in 3G TS 23.018 [3]. Procedure MNP_MT_GMSC_Check_MNP_Indicators 1(1) OPTION NPDB query check supported NPDB query is marked done Result:= Fail Result:= Routeing number Yes No No Yes Figure 5: Procedure MNP_MT_GMSC_Check_MNP_Indicators ETSI ETSI TS 123 066 V3.3.0 (2000-06) 18 3G TS 23.066 version 3.3.0 Release 1999 The procedure MNP_SRF_Check_MNP_Indicator is shown in figure 6. It is called from the procedures MNP_SRF_Non_Call_Related and MNP_SRF_MATF_Call_Related. Procedure MNP_SRF_Check_MNP_Indicator 1(1) yes no Check NPDB query in MNP-SRF? previous NPDB query is done? no set: terminate yes Figure 6: Procedure MNP_SRF_Check_MNP_Indicator ETSI ETSI TS 123 066 V3.3.0 (2000-06) 19 3G TS 23.066 version 3.3.0 Release 1999 Annex A (normative): IN Call-Related Technical Realisation A.1 Architecture A.1.1 Network Options There are two IN-based solutions for querying the NPDB :- i. ETSI Core INAP ii. ANSI IN Query. The following network operator options are defined for the MT calls in the GMSC: - Terminating call Query on Digit Analysis (TQoD); - Query on HLR Release (QoHR). In a GSM network that supports the IN-based approach for call related MNP, each GMSC shall support at least one of these options. The following network operator option is defined for MO calls in VMSCA and for forwarded calls in the GMSC and VMSCB: - Originating call Query on Digit Analysis (OQoD). In a GSM network which supports the IN-based approach for call related MNP, it is a network operator decision, taking into account the regulatory and architectural constraints that may prevail, whether or not VMSCs and GMSCs support this option. The use of OQoD in transit switches in a PLMN while avoiding multiple database interrogations is for further study. The interworking between the CCF and the SSF for MNP is for further study. Note that for different number ranges different options may be chosen. A.1.2 No NP Query required – Number is not subject for portability Figure A.1.2 shows the architecture for a call to a number that is not subject for portability. This can be for several reasons like for example: - the national regulator has stipulated some number series as being non-portable or; - in an initial phase only a limited amount of subscribers might port in certain number blocks and some operators might want to treat the call routeing according to traditional routeing plans without any change. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 20 3G TS 23.066 version 3.3.0 Release 1999 Number range holder/ subscription network HLRB GMSCB Originating Exchange VMSCB/ VLRB 1 2 3 4 5 6 (Inter)national Originating network Visited network Figure A.1.2: Call to a non-ported number, no NP query required 1 From an Originating Exchange a call is set up to MSISDN. The call is routed to the Number range holder network being the Subscription network. 2 When GMSCB receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the HLRB including the MSISDN in the request. 3 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered; 4 The MSC/VLRB returns an MSRN back to the HLRB. 5 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. 6 GMSCB uses the MSRN to route the call to VMSCB. A.1.3 NP Query in Number Range Holder Network A.1.3.1 TQoD – Number is not ported Figure A.1.3.1 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routeing plans for routeing the call to the Number range holder network for further routeing decisions. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 21 3G TS 23.066 version 3.3.0 Release 1999 HLRB NPDB (Inter)national Originating network Visited network GMSCB VMSCB/ VLRB Originating Exchange 1 Number range holder/ subscription network 2 3 4 5 6 7 8 Figure A.1.3.1: Call to a non-ported number using TQoD procedure 1 From an Originating Exchange a call is set up to MSISDN. The call is routed to the Number range holder network being the Subscription network. 2 When GMSCB receives the ISUP IAM, it will send a database query to the NPDB as a result of analysis of the received MSISDN. The MSISDN is included in the query to the NPDB. 3 The NPDB detects that the MSISDN is not ported and responds back to the GMSCB to continue the normal call setup procedure for MT calls. 4 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. 5 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber owning the MSISDN currently is registered. 6 The MSC/VLRB returns an MSRN back to the HLRB. 7 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. 8 GMSCB uses the MSRN to route the call to VMSCB. Note that the NPDB may be outside the number range holder network if a shared NPDB is used. A.1.3.2 TQoD – Number is ported Figure A.1.3.2 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routeing plans for routeing the call to the Number range holder network for further routeing decisions. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 22 3G TS 23.066 version 3.3.0 Release 1999 HLRB NPDB Number range holder network (Inter)national Originating network Visited network Subscription network GMSCA VMSCB/ VLRB Originating Exchange 1 GMSCB 2 3 4 5 8 6 7 9 Figure A.1.3.2: Call to a ported number using TQoD procedure 1 From an Originating Exchange a call is set up to MSISDN. The call is routed to the Number range holder network. 2 When GMSCA receives the ISUP IAM, it will send a database query, including the MSISDN, to the NPDB as a result of analysis of the received MSISDN. 3 The NPDB detects that the MSISDN is ported and responds back to the GMSCA with a Routeing Number pointing out the Subscription network. 4 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message; also the MSISDN is included in IAM. 5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. The capability to route messages to the correct HLR is required. 6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. 7 The MSC/VLRB returns an MSRN back to the HLRB. 8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. 9 GMSCB uses the MSRN to route the call to VMSCB. Note that the NPDB may be outside the number range holder network if a shared NPDB is used. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 23 3G TS 23.066 version 3.3.0 Release 1999 A.1.3.3 QoHR – Number is ported Figure A.1.3.3 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routeing plans for routeing the call to the Number range holder network for further routeing decisions. HLRB NPDB Number range holder network (Inter)national Originating network Visited network Subscription network GMSCA VMSCB/ VLRB Originating Exchange 1 GMSCB 2 3 6 7 10 8 9 11 HLRA 4 5 Figure A.1.3.3: Call to a ported number using QoHR procedure 1 From an Originating Exchange a call is set up to MSISDN. The call is routed to the Number range holder network. 2 When GMSCA receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the HLRA including the MSISDN in the request. 3 The HLRA returns a MAP SRI ack with an “Unknown Subscriber” error since no record was found for the subscriber in the HLRA. 4 When GMSCA receives the error indication form the HLRA, this will trigger the sending of a database query to the NPDB, including the MSISDN in the query. 5 The NPDB detects that the MSISDN is ported and responds back to the GMSCA with a Routeing Number pointing out the Subscription network. 6 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message; also the MSISDN is included in IAM. 7 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. The capability to route messages to the correct HLR is required. 8 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. 9 The MSC/VLRB returns an MSRN back to the HLRB. 10 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. 11 GMSCB uses the MSRN to route the call to VMSCB. Note that the NPDB may be outside the number range holder network if a shared NPDB is used. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 24 3G TS 23.066 version 3.3.0 Release 1999 A.1.4 NP Query in Originating Network A.1.4.1 OQoD – Number is not ported Figure A.1.4.1 shows the architecture for a call where already the Originating network has the knowledge whether the MSISDN is ported or not and can route the call directly to the Subscription network that in this case is the same as the Number range holder network. HLRB NPDB National Originating network Visited network VMSCA VMSCB/ VLRB 2 3 5 6 7 8 1 GMSCB 4 9 Number range holder/ Subscription network Figure A.1.4.1: Call to a non-ported number using OQoD procedure 1 A call is initiated by Mobile Subscriber A towards Mobile Subscriber B, using the MSISDN of the called subscriber. 2 When VMSCA receives the call setup indication, it will send a database query to the NPDB as a result of analysis of the received MSISDN, including the MSISDN in the query. 3 The NPDB detects that the MSISDN is not ported and responds back to the VMSCA to continue the normal call setup procedure for MO calls. Depending on database configuration option, the NPDB could either return a Routeing Number on not ported calls, as done for ported calls, or the call is further routed using the MSISDN number only towards the Number range holder network. 4 The call is routed to the Number range holder/Subscription network based on the MSISDN or Routeing Number carried in ISUP IAM message. 5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. 6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. 7 The MSC/VLRB returns an MSRN back to the HLRB. 8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. 9 GMSCB uses the MSRN to route the call to VMSCB. Note that the NPDB may be outside the national originating network if a shared NPDB is used. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 25 3G TS 23.066 version 3.3.0 Release 1999 A.1.4.2 OQoD – Number is ported Figure A.1.4.2 shows the architecture for a call where already the Originating network has the knowledge that the MSISDN is ported and can route the call directly to the Subscription network without involving the Number range holder network. HLRB NPDB National Originating network Visited network Subscription network VMSCB/ VLRB GMSCB 2 3 4 5 8 6 7 9 VMSCA 1 Figure A.1.4.2: Call to a ported number using OQoD procedure 1 A call is initiated by Mobile Subscriber A towards Mobile Subscriber B, using the MSISDN of the called subscriber. 2 When VMSCA receives the call setup indication, it will send a database query to the NPDB as a result of analysis of the received MSISDN including the MSISDN in the query. 3 The NPDB detects that the MSISDN is ported and responds back to the VMSCA with a Routeing Number pointing out the Subscription network. 4 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message; also the MSISDN is included in IAM. 5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. The capability to route messages to the correct HLR is required. 6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. 7 The MSC/VLRB returns an MSRN back to the HLRB. 8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. 9 GMSCB uses the MSRN to route the call to VMSCB. Note that the NPDB may be outside the national originating network if a shared NPDB is used. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 26 3G TS 23.066 version 3.3.0 Release 1999 A.2 Information flows In the following figures the NPDB is shown as belonging to the Number range holder network or to the national originating network. However, the NPDB may be shared within one portability domain i.e. nation-wide. Figure A.2.1 shows the information flow for successful QoHR. Number range holder network subscription network visited network GMSC HLR NPDB GMSC HLR VLR VMSC IAM ----Æ SRI ---Æ neg. result Å---- "query" ------------------------Æ "routing" Å------------------------ IAM -------------------------------------------- Æ SRI ----Æ PRN ----Æ PRN ack Å---- SRI ack Å---- IAM --------------------------------------------Æ Figure A.2.1 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 27 3G TS 23.066 version 3.3.0 Release 1999 Figure A.2.2 shows the information flow for unsuccessful QoHR (unallocated number). Number range holder network GMSC HLR NPDB IAM -----------------Æ SRI ----------------Æ negative result Å---------------- "query" --------------------------------------------------------------Æ "result" Å-------------------------------------------------------------- REL Å---------------- Figure A.2.2 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 28 3G TS 23.066 version 3.3.0 Release 1999 Figure A.2.3 shows the information flow for successful TQoD. Number range holder network subscription network visited network GMSC HLR NPDB GMSC HLR VLR VMSC IAM ----Æ "query" ------------------------Æ "routing" Å------------------------ IAM -------------------------------------------- Æ SRI ----Æ PRN ----Æ PRN ack Å---- SRI ack Å---- IAM --------------------------------------------Æ Figure A.2.3 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 29 3G TS 23.066 version 3.3.0 Release 1999 Figure A.2.4 shows the information flow for unsuccessful TQoD (number not ported). Number range holder network visited network GMSC HLR NPDB VLR VMSC IAM -------Æ "query" -----------------------------------Æ "result" Å----------------------------------- SRI -------Æ PRN ------------------------------------Æ PRN ack Å------------------------------------ SRI ack Å------- IAM --------------------------------------------------------------------------------------------Æ Figure A.2.4 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 30 3G TS 23.066 version 3.3.0 Release 1999 Figure A.2.5 shows the information flow for successful OQoD (number ported). National originating network A subscription network B visited network B VMSC NPDB GMSC HLR VLR VMSC Set-up -----Æ "query" ------Æ "routin g" Å----- IAM ----------------------------Æ SRI -----Æ PRN -----Æ PRN ack Å----- SRI ack Å----- IAM -----------------------------------------------------Æ Figure A.2.5 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 31 3G TS 23.066 version 3.3.0 Release 1999 Figure A.2.6 shows the information flow for unsuccessful OQoD (number not ported in). originating network Number range holder network VMSCA NPDB GMSC Set-up ----------------Æ "query" ----------------Æ "routing" Å---------------- IAM ----------------------------------------------------------------Æ continue as shown in figures A.2.1, A.2.2, A.2.3 and A.2.4 Figure A.2.6 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 32 3G TS 23.066 version 3.3.0 Release 1999 A.3 Functional requirements of network entities A.3.1 Functional requirement of GMSC A.3.1.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR The procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR is shown in figure A.1.3. It is called from the procedure Obtain_Routeing_Address defined in 3G TS 23.018 [3]. The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. The query to NPDB contains the service key for MNP query and the called party’s MSISDN. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 33 3G TS 23.066 version 3.3.0 Release 1999 Procedure in the GMSC to handle Query on HLR Release for Mobile Number Portability Procedure MOBILE_NUMBER_PORTABILITY_QoHR 1(1) Signals to/from the right are to/from the NPDB QoHR NPDB query is marked done called party number within porting out number range Result := not ported "query" Wait negative Response Abort "result" "routing" Result := not ported Result := Number ported yes no no yes no yes Figure A.3.1.1: Procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR ETSI ETSI TS 123 066 V3.3.0 (2000-06) 34 3G TS 23.066 version 3.3.0 Release 1999 A.3.1.2 Procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD The procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD is shown in figure A.3.1.2. It is called from the procedure Obtain_Routeing_Address defined in 3G TS 23.018 [3]. The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. The "query" to NPDB contains the service key for MNP query and the called party’s MSISDN. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 35 3G TS 23.066 version 3.3.0 Release 1999 Procedure in the GMSC to handle Terminating call Query on Digit Analysis for Mobile Number Portability Procedure MOBILE_NUMBER_PORTABILITY_TQoD 1(1) Signals to/from the right are to/from the NPDB OR TQoD NPDB query is marked done called party number within porting out number range Result := not ported IDP NPDB Query Wait negative Response Abort Continue Connect Result := not ported Result := Number ported false true yes no no yes no yes Figure A.3.1.2: Procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD ETSI ETSI TS 123 066 V3.3.0 (2000-06) 36 3G TS 23.066 version 3.3.0 Release 1999 A.3.2 Functional requirement of MSC A.3.2.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD The procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is shown in figure A.3.2.1. It is called from the procedure Outgoing_Call_Setup_MSC and from the process MT_CF_MSC defined in 3G TS 23.018 [3]. The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. The MSC may recognise own numbers as not being within the ported number range. For foreign numbers however, the MSC will not in general know whether the number is portable. The test “called party number is a portable national MSISDN” takes the “yes” exit if the number is a foreign national MSISDN or an own portable MSISDN. The "query" to NPDB contains the service key for MNP query and the called party’s MSISDN. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 37 3G TS 23.066 version 3.3.0 Release 1999 Procedure in the MSC to handle Originating call Query on Digit Analysis for Mobile Number Portability Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD 1(1) Signals to/from the right are to/from the NPDB OQoD called party number is a portable national MSISDN “query” Wait negative Response Abort “result” “routing” set routeing number for IAM yes no no yes Figure A.3.2.1: Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD ETSI ETSI TS 123 066 V3.3.0 (2000-06) 38 3G TS 23.066 version 3.3.0 Release 1999 A.3.3 Functional requirement of NPDB A.3.3.1 Process IN_QUERY_NPDB The process IN_QUERY_NPDB is shown in figure A.3.3.1. Process in the NPDB to handle NPDB queries Process IN_QUERY_NPDB 1(1) Signals to/from the left are to/from the MSC Idle “query” service key indicates NPDB query Syntax check on CdPA correct? Set error type set: Routeing number negative Response “result” “routing” Idle no yes Number not ported Check Called Party Address Portability Status yes no Send RN on Number Not Ported in OQoD Number ported Figure A.3.3.1: Process IN_QUERY_NPDB ETSI ETSI TS 123 066 V3.3.0 (2000-06) 39 3G TS 23.066 version 3.3.0 Release 1999 A.4 Contents of messages This clause specifies the content of the following messages: On the ISUP interface: IAM. On the MSC - NPDB interface: "query"; "routing"; "result". Messages in the MSC – NPDB interface are mapped into ETSI Core INAP or ANSI IN Query messages according to the protocols on this interface. This is listed in the following table: Messages in MSC-NPDB interface INAP messages ANSI IN Query messages "query" INITIAL DP ProvideInstruction:Start "routing" CONNECT CONTINUE ConnectionControl:Connect "result" CONTINUE RELEASE CALL ConnectionControl:Connect In the tables that follow, information elements are shown as mandatory (M), conditional © or optional (O). A mandatory information element shall always be present. A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional element may be present or absent, at the discretion of the application at the sending entity. A.4.1 Messages on the ISUP interface A.4.1.1 IAM for ETSI ISUP interface This message is specified in [14]. It is necessary for the IAM to contain the information needed to route the call to the subscription network of the ported subscriber. The ways in which this may be coded are shown in [14]. A.4.1.2 IAM for ANSI ISUP interface This message is specified in [8] and [9]. It is necessary for the IAM to contain the information needed to route the call to the subscription network of the ported subscriber. The ways in which this may be coded are shown in [8] and [9]. A.4.2 Messages on the MSC - NPDB interface A.4.2.1 INITIAL DP This message is specified in [5]. The following information elements are required: Information element name Required Description Service Key M Identifies the requested IN service (MNP query) Called Party Number M The possibly ported MSISDN ETSI ETSI TS 123 066 V3.3.0 (2000-06) 40 3G TS 23.066 version 3.3.0 Release 1999 A.4.2.2 INITIAL DP negative response This message is specified in [5]. The negative response information element can take the following values: 1. missing parameter; 2. unexpected data value; 3. unexpected parameter; 4. system failure. A.4.2.3 CONNECT This message is specified in [5]. It shall be ensured that the information in the Connect message shall be aligned with the coding supported in the ISUP signalling. A.4.2.4 CONTINUE This message is specified in [5]. This message does not contain any information element. A.4.2.5 RELEASE CALL This message is specified in [5]. The following information elements are required: Information element name Required Description Cause M Indicates the reason for releasing the call A.4.2.6 ProvideInstruction:Start Parameter Type Number of Octets Contents Package Type Identifier M 1 Query with Permission Component Type Identifier M 1 Invoke (last) Operation Code Identifier M 1 National TCAP Operation Code M 2 provideInstruction:Start (reply required) Service Key M 11* 10 digit called party number digits Digits (calling party number) M 1 6-9 3,6 or 10 ANI digits Digits (LATA) M 1 6 LATA ID Originating Station Type M 1 1 Binary value of ANI II digits Note: * = Value specific for number portability 1 = This mandatory parameter is required for the message but the content is not essential for number portability. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 41 3G TS 23.066 version 3.3.0 Release 1999 A.4.2.7 ConnectionControl:Connect Parameter Type Number of Octets Contents Package Type Identifier M 1 Response Component Type Identifier M 1 Invoke (last) Operation Code Identifier M 1 National TCAP Operation Code M 2 connectionControl:Connect (no reply required) Digits (Carrier) M 1 6 3 or 4 digit CIC Digits (Routing Number) M 9* 10 digit RN or Dialed Number Billing Indicators M 1 4 Unspecified Note: * = Value specific for number portability 1 = This mandatory parameter is required for the message but the content is not essential for number portability. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 42 3G TS 23.066 version 3.3.0 Release 1999 Annex B (normative): Handling of Non-Call Related Signalling B.1 Handling of Non-call Related Signalling B.1.1 Routeing Conventions Figure B.1.1 illustrates the routeing of non-call related signalling messages between networks in a number portability environment. Number Range Holder Network Message (1) Portability domain Subscription Network Other network Message (5) Message (4) Message (2) Message (3) Figure B.1.1: Routeing of non-call related signalling messages in a number portability environment If a non-call related signalling message is originated outside the portability domain, this message (1) is received by the number range holder network. The number range holder network routes the message (5) onward to the subscription network. If a non-call related signalling message is originated in a network inside the portability domain and this network supports direct routeing, this message (3) is routed to the subscription network. If a non-call related signalling message is originated in a network inside the portability domain and this network does not support direct routeing, the message (2, 4) is routed to the number range holder network. The number range holder network routes the message (5) onward to the subscription network. This is referred to as indirect routeing. B.1.2 Network Architecture In a PLMN that supports MNP, non-call related signalling messages as mentioned in section B.1.1 are relayed by an MNP-Signalling Relay Function (MNP-SRF). The MNP-SRF provides re-routeing capability for signalling messages addressed using the MSISDN. The MNP-SRF obtains routeing information from the NP database to identify the subscription network associated with a particular national MSISDN. The interface between the MNP-SRF and the NP database is considered implementation dependent and is not detailed further. For further details see clause 4.3. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 43 3G TS 23.066 version 3.3.0 Release 1999 From the perspective of the PLMN in which the MNP-SRF resides, the MSISDN in the CdPA represents either: 1 An own number ported out. 2 An own number not ported out. 3 A foreign number ported in. 4 A foreign number ported to a foreign network. 5 A foreign number not known to be ported. When a PLMN supports direct routeing (clause B.1.1), all non-call related signalling messages where the MSISDN in the CdPA belongs to a number range owned by a PLMN in the portability domain and all non-call related signalling messages which are relayed towards the network, are routed to the PLMN’s MNP-SRF for treatment. In case 2 and 3 the MNP-SRF relays the message to the Subscriber Database supporting the Network Service e.g. HLR and Calling Name Database. In case 1, 4 and 5 the MNP-SRF relays the message to subscription network. When a PLMN does not support direct routeing, only non-call related signalling messages where the MSISDN in the CdPA belongs to a number range owned by the PLMN itself and all non-call related signalling messages which are relayed towards the network are routed to the PLMN’s MNP-SRF for treatment. All other messages are routed to the number range holder network. For this routeing convention, only cases 1, 2 and 3 are applicable: In case 2 and 3 the MNP-SRF relays the message to the Subscriber Database supporting the Network Service e.g. HLR and Calling Name Database. In case 1 the MNP-SRF relays the message to the subscription network. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 44 3G TS 23.066 version 3.3.0 Release 1999 B.2 Signalling Scenarios B.2.1 Non-call Related Signalling Message for a Non-ported Number – Indirect Routeing Figure B.2.1 shows the MNP-SRF operation for routeing a non-call related signalling message for a non-ported number where the interrogating network is inside the portability domain and indirect routeing is used or the interrogating network is outside the portability domain. Interrogating Network NPDB Number Range Holder Network = Subscription Network HLRB INE MNP SRFB SCCP CdPA = MSISDN, TT=0 ) 1 SCCP CdPA = HLRB address NOTE: that the TT may have a different value, e.g. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI_For_Short Message. Figure B.2.1: MNP-SRF operation for routeing a non-call related signalling message for a non-ported number where the interrogating network is inside the portability domain and indirect routeing is used or the interrogating network is outside the portability domain The Interrogating Network Entity (INE) submits a non-call related signalling message. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported using information that may be retrieved from an NP database. Figure B.2.1 shows an example where the MNP-SRF function then re-routes the message to HLRB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 45 3G TS 23.066 version 3.3.0 Release 1999 B.2.2 Non-call Related Signalling Message for a Ported or Non-ported Number – Direct Routeing Figure B.2.2 shows the MNP-SRF operation for routeing a non-call related signalling message for a ported or non- ported number where the interrogating network supports direct routeing. If the interrogating network is the subscription network, MNP-SRFA and MNP-SRFB coincide; i.e. the signalling message passes the MNP-SRF only once. SCCP CdPA = RN (+ MSISDN), TT=0 )2 Interrogating Network NPDB Subscription Network HLRB INE MNP SRFA SCCP CdPA = MSISDN, TT=0 )1 MNP SRFB NPDB SCCP CdPA = HLRB address NOTE 1: the TT may have a different value, e.g. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI_For_Short Message . NOTE 2: the CdPA may have different values in the GT address and the nature of address fields. Figure B.2.2: MNP-SRF operation for routeing a non-call related signalling message for a ported or non-ported number where the interrogating network supports direct routeing The Interrogating Network Entity (INE) submits a non-call related signalling message. When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the subscription network using information that may be retrieved from an NP database. The MNP-SRF function then modifies the CdPA according to the rules agreed for the portability domain and routes the message to MNP-SRFB in the subscription network. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information that may be retrieved from an NP database. Figure B.2.2 shows an example where the MNP-SRF function then re-routes the message to HLRB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 46 3G TS 23.066 version 3.3.0 Release 1999 B.2.3 Non-call Related Signalling Message for a Ported Number - Indirect Routeing Figure B.2.3 shows the MNP-SRF operation for indirectly routeing (i.e. via the number range holder network) a non- call related signalling message for a ported subscriber. SCCPCdPA = RN (+ MSISDN), TT=0 )2 Interrogating Network NPDB Subscription Network HLRB MNP SRFA SCCPCdPA = MSISDN, TT=0)1 MNP SRFB NPDB SCCPCdPA = HLRB address INE Number Range Holder Network NOTE 1: the TT may have a different value, e.g. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI_For_Short Message. NOTE 2: the CdPA may have different values in the GT address and the nature of address fields. Figure B.2.3: MNP-SRF operation for indirectly routeing (i.e. via the number range holder network) a non-call related signalling message for a ported subscriber The Interrogating Network Entity (INE) submits a non-call related signalling message. This message is routed on MSISDN global title to MNP-SRFA in the number range holder network. When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the subscription network using information that may be retrieved from an NP database. The MNP-SRF function then modifies the CdPA according to the rules agreed for the portability domain and routes the message to MNP-SRFB in the subscription network. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information that may be retrieved from an NP database. Figure B.2.3 shows an example where the MNP-SRF function then re-routes the message to HLRB. B.3 Functional Requirements of Network Entities B.3.1 Procedure MNP_SRF_Non_Call_Related Figure B.3.1 shows the procedure MNP_SRF_Non_Call_Related. This procedure handles non-call related signalling messages. It is called from the process MNP_SRF (see chapter 4.3). The check “CdPA contains own number ported out?” identifies all mobile numbers from number ranges allocated to the network the MNP-SRF is located in and which are ported to other networks. In this case the message is relayed to the subscription network. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 47 3G TS 23.066 version 3.3.0 Release 1999 The check “CdPA contains own number not ported out?” identifies all mobile numbers from the number ranges allocated to the network the MNP-SRF is located in and which are still served by the network the MNP-SRF is located in, i.e. the numbers are not ported out. In this case the message is relayed to the HLR in the network. The check “CdPA contains foreign number ported in?” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are served by the network the MNP-SRF is located in, i.e. the numbers are ported in. In this case the message is relayed to the HLR in the network. The check “CdPA contains foreign number ported to a foreign network?” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are not served by the MNP-SRF is located in and not served by the network the number range is allocated to, i.e. the numbers are ported to a foreign network. In this case the message is relayed to the subscription network. The remaining numbers “CdPA contains number not known to be ported ?” are mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are also not served by the network the MNP- SRF is located in. In this case the message is relayed to the number range holder network. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 48 3G TS 23.066 version 3.3.0 Release 1999 Procedure MNP_SRF_Non_Call_Related CdPA := Subscriber Database Address Yes Procedure in MNP_SRF to handle the Signalling Relay Function of Mobile Number Portability for Non Call Related Messages CdPA := Routing Number (+ MSISDN) Procedure MNP_SRF_Non_Call_Related FPAR IN/OUT Called Address CdPA contains own number ported out? es Yes No No No No CdPA contains a foreign number not known to be ported! CdPA contains own number not ported out? CdPA contains foreign number ported in? CdPA contains foreign number ported to a 3rd network CdPA := Routing Number (+ MSISDN) Yes The use of a routeing number is a matter for agreement within a portability cluster CdPA := Routing Number (+ MSISDN) terminate? No MNP_SRF_Check_ MNP_Indicator Yes Figure B.3.1: Procedure MNP_SRF_Non_Call_Related ETSI ETSI TS 123 066 V3.3.0 (2000-06) 49 3G TS 23.066 version 3.3.0 Release 1999 B.4 Signalling Scenarios (informative) This (informative) chapter contains examples of signalling scenarios. B.4.1 Delivery of SMS to a Non-ported Number – Direct Routeing – MNP-SRF acts as SCCP Relay Figure B.4.1 shows the MNP-SRF operation for delivering an SMS message to a non-ported number. SRI_for_SM (MSISDN) CdPA = MSISDN, TT=0 CgPA = SMS-GMSCA address SRI_for_SM ack (VMSCB address) CdPA = SMS-GMSCA address CgPA = HLRB address National Interrogating Network = Subscription Network Forward_SM (VMSCB address) MSB SMSC VMSCB 6 1 5 MNP SRFB SMS- GMSCA 2 HLRB 4 Forward_SM (MSISDN) SRI_for_SM (MSISDN) CdPA = HLRB address CgPA = SMS-GMSCA address 3 Visited Network Figure B.4.1: SRF operation for delivering an SMS message to a non-ported number where the SRI_for_SM message is submitted by a national interrogating network 1. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface. 2. The SMS-GMSC generates a routeing enquiry for SM delivery. The MAP SRI_for_SM message is routed to the network’s MNP-SRF. 3. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 4. HLRB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC. 5. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message. 6. VMSCB further delivers the message to MSB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 50 3G TS 23.066 version 3.3.0 Release 1999 B.4.2 Delivery of SMS to a Non-ported Number - Direct Routeing – MNP-SRF acts as Higher-level Relay Figure B.4.2 shows the MNP-SRF operation for delivering an SMS message to a non-ported number where the SRI_for_SM message is submitted by a national interrogating network. For further details of the higher level relay function (e.g. TC relay), the reader is referred to [7]. SRI_for_SM (MSISDN) CdPA = MSISDN, TT=0 CgPA = SMS-GMSCA address National Interrogating Network = Subscription Network Forward_SM (VMSCB address) MSB SMSC VMSCB 7 1 6 MNP SRFB SMS- GMSCA 2 HLRB 4 Forward_SM (MSISDN) SRI_for_SM (MSISDN) CdPA = HLRB address CgPA = MNP-SRFB address 3 Visited Network 5 SRI_for_SM ack (VMSCB address) CdPA = MNP-SRFB address CgPA = HLRB address SRI_for_SM ack (VMSCB address) CdPA = SMS-GMSCA address CgPA = MNP-SRFB address Figure B.4.2: SRF operation for delivering an SMS message to a non-ported number where the SRI_for_SM message is submitted by a national interrogating network 1. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface. 2. The SMS-GMSC generates a routeing enquiry for SM delivery. The MAP SRI_for_SM message is routed to the network’s MNP-SRF. 3. When MNP-SRFB receives the message it terminates the TCAP dialogue and an MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the TCAP portion of the message and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database. The MNP- SRF function then initiates a new dialogue and routes the message to HLRB. 4. HLRB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC. 5. MNP-SRFB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC to the SMS-GMSCA. 6. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message. 7. VMSCB further delivers the message to MSB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 51 3G TS 23.066 version 3.3.0 Release 1999 B.4.3 Delivery of SMS to a Ported Number – Indirect Routeing Figure B.4.3 shows the MNP-SRF operation for delivering an SMS message to a ported number where the interrogating network does not support direct routeing. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF(s). If the MNP- SRF(s) use(s) a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. SRI_for_SM (MSISDN) CdPA = RN (+MSISDN) CgPA = SMS-GMSCA address SRI_for_SMS (MSISDN) CdPA = MSISDN, TT=0 CgPA = SMS-GMSCA address SRI_for_SM ack (VMSCB address) CdPA = SMS-GMSCA address CgPA = HLRB address (Inter-)national Interrogating Network Forward_SM (VMSCB address) MSB SMSC VMSCB 7 1 4 SMS- GMSCA HLRB Forward_SM (MSISDN) 2 3 SRI_for_SM (MSISDN) CdPA = HLRB address CgPA = SMS-GMSCA address 6 5 Number Range Holder Network Subscription Network MNP SRFB’ MNP SRFB Visited Network Figure B.4.3: SRF operation for delivering an SMS message to a ported number where the interrogating network does not support direct routeing 1. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface. 2. The SMS-GMSC generates a routeing enquiry for SM delivery. The MAP SRI_for_SM message is routed to the number range holder network’s MNP-SRF. 3. When MNP-SRFB’ receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. 4. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 5. HLRB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC. 6. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message. 7. VMSCB further delivers the message to MSB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 52 3G TS 23.066 version 3.3.0 Release 1999 B.4.4 Delivery of SMS to a Ported Number – Direct Routeing Figure B.4.4 shows the MNP-SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routeing. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. If the MNP- SRFs use a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. SRI_for_SM ack (VMSCB address) CdPA = SMS-GMSCA address CgPA = HLRB address SRI_for_SM (MSISDN) CdPA = MSISDN, TT=0 CgPA = SMS-GMSCA address SRI_for_SM (MSISDN) CdPA = RN (+MSISDN), TT=0 CgPA = SMS-GMSCA address National Interrogating Network Forward_SM (VMSCB address) MSB SMSC VMSCB Visited Network 7 1 4 SMS- GMSCA HLRB Forward_SM (MSISDN) 3 SRI_for_SM (MSISDN) CdPA = HLRB address CgPA = SMS-GMSCA address 6 5 Subscription Network 2 MNP SRFA MNP SRFB Figure B.4.4: SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routeing 1. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface. 2. The SMS-GMSC generates a routeing enquiry for SM delivery. The MAP SRI_for_SM message is routed to the network’s MNP-SRF. 3. When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. 4. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 5. HLRB responds to the routeing enquiry by sending back an SRI_for_SM ack with the address of the VMSC. 6. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message. 7. VMSCB further delivers the message to MSB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 53 3G TS 23.066 version 3.3.0 Release 1999 B.4.5 International SOR for a Non-ported Number Figure B.4.5 shows the MNP-SRF operation for optimally routeing an international call to a non-ported number. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF. If the MNP-SRF uses a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. SRI ack (MSRN) CdPA = GMSCA address CgPA = HLRB address SRI (OR, MSISDN) CdPA = MSISDN, TT=0 CgPA = GMSCA address International Originating/Interrogating Network MSB VMSCB 7 2 4 HLRB SRI (OR, MSISDN) CdPA = HLRB address CgPA = GMSCA address 6 Subscription Network = Number Range Holder Network GMSCA VMSCA 3 IAM (MSISDN) IAM (MSRN) MSA 1 5 MNP SRFB Visited Network Figure B.4.5: SRF operation for optimally routeing an international call to a non-ported number 1. MSA originates a call to MSISDN. 2. VMSCA routes the call to the originating network’s GMSCA. 3. When GMSCA receives the ISUP IAM, it requests routeing information by submitting a MAP SRI with SOR parameter set to the number range holder network of the dialled MSISDN. Within the number range holder network, the message is routed to the network’s MNP-SRF. 4. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 5. When HLRB receives the SRI, it responds to the GMSCA by sending back an SRI ack with a MSRN. 6. GMSCA uses the MSRN to route the call to VMSCB. 7. VMSCB further establishes a traffic channel to MSB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 54 3G TS 23.066 version 3.3.0 Release 1999 B.4.6 SOR for a Ported Number – Indirect Routeing Figure B.4.6 shows the MNP-SRF operation for optimally routeing a call (using SOR) to a ported number where the interrogating network does not support direct routeing. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. If the MNP- SRFs use a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. SRI (SOR, MSISDN) CdPA = RN (+MSISDN), TT=0 CgPA = GMSCA address SRI (SOR, MSISDN) CdPA = MSISDN, TT=0 CgPA = GMSCA address SRIack (MSRN) CdPA = GMSCA address CgPA = HLRB address IAM (MSRN) MSB VMSCB 8 5 HLRB 3 4 SRI (SOR, MSISDN) CdPA = HLRB address CgPA = GMSCA address 7 6 Number Range Holder Network Subscription Network International Originating/Interrogating Network 2 GMSCA VMSCB IAM (MSISDN) MSA 1 MNP SRFB’ MNP SRFB Visited Network Figure B.4.6: MNP-SRF operation for optimally routeing a call (using SOR) to a ported number where the interrogating network does not support direct routeing 1. MSA originates a call to MSISDN. 2. VMSCA routes the call to the network’s GMSCA. 3. When GMSCA receives the ISUP IAM, it requests routeing information by submitting a MAP SRI with SOR parameter set to the number range holder network of the dialled MSISDN. Within the number range holder network, the message is routed to the network’s MNP-SRF. 4. When MNP-SRFB’ receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. 5. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 6. When HLRB receives the SRI, it responds to the GMSCA by sending back an SRI ack with a MSRN. 7. GMSCA uses the MSRN to route the call to VMSCB. 8. VMSCB further establishes a traffic channel to MSB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 55 3G TS 23.066 version 3.3.0 Release 1999 B.4.7 Any Time Interrogation for a Ported Number – Indirect Routeing Figure B.4.7 shows the MNP-SRF operation for routeing an Any_Time_Interrogation message for a ported number where the interrogating network does not support direct routeing. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. If the MNP- SRFs use a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. ATI ack CdPA = gsmSCF address CgPA = HLRB address ATI (MSISDN) CdPA = RN (+MSISDN), TT=0 CgPA = gsmSCF address ATI (MSISDN) CdPA = HLRB address CgPA = gsmSCF address MNP SRFB’ gsmSCF HLRB ATI (MSISDN) CdPA = MSISDN, TT=0 CgPA = gsmSCF address Subscription Network MNP SRFB 4 1 2 Number Range Holder Network 3 Figure B.4.7: MNP-SRF operation for routeing an Any_Time_Interrogation message for a ported number where the interrogating network does not support direct routeing 1. The gsmSCF generates an Any_Time_Interrogation (ATI) message. The message is routed to the number range holder network’s MNP-SRF. 2. When MNP-SRFB’ receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. 3. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 4. HLRB responds to the ATI by sending back an ATI ack with the requested information. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 56 3G TS 23.066 version 3.3.0 Release 1999 B.4.8 Any Time Interrogation for a Ported Number – Direct Routeing Figure B.4.8 shows the MNP-SRF operation for routeing an Any_Time_Interrogation message for a ported number where the interrogating network supports direct routeing. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF. If the MNP-SRF uses a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. gsmSCF 2 HLRB ATI (MSISDN) CdPA = MSISDN, TT=0 CgPA = gsmSCF address Subscription Network ATI (MSISDN) CdPA = HLRB address CgPA = gsmSCF address MNP SRFB ATI ack CdPA = gsmSCF address CgPA = HLRB address 1 3 Figure B.4.8: MNP-SRF operation for routeing an Any_Time_Interrogation message for a ported number where the interrogating network supports direct routeing 1. The gsmSCF generates an Any_Time_Interrogation (ATI) message. The message is routed to the network’s MNP-SRF. 2. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 3. HLRB responds to the ATI by sending back an ATI ack with the requested information. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 57 3G TS 23.066 version 3.3.0 Release 1999 B.4.9 CCBS where the Busy Subscriber is a Ported Subscriber - Direct Routeing Figure B.4.9 shows the MNP-SRF operation for routeing a CCBS Request for a ported number where the interrogating network supports direct routeing. The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. If the MNP- SRFs use a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. CCBS Request (MSISDN) CdPA = RN (+MSISDN), TT=17 CgPA = HLRA address CCBS Requestack CdPA = HLRA address CgPA = HLRB address Release (cause = subscriber busy) busy Network visited by A MSB VMSCB Network visited by B HLRB 1 Subscription Network of B HLRA VLRA/ VMSCA Register_CC_Entry CdPA = HLR address CgPA = VLRA address 2 CCBS Request (MSISDN) CdPA = MSISDN, TT=17 CgPA = HLRA address MNP SRFA 3 4 CCBS Request (MSISDN) CdPA = HLRB address CgPA = HLRA address 5 MNP SRFB 6 Subscription Network of A Figure B.4.9: MNP-SRF operation for routeing a CCBS Request for a ported number where the interrogating network supports direct routeing 1. The VMSCA receives a ISUP Release message with cause value ‘subscriber busy’ from VMSCB. 2. VLRA/VMSCA sends a Register_CC_Entry to HLRA using the HLRA address as CdPA on SCCP. 3. The HLRA sends a CCBS Request message to the networks MNP-SRFA. 4. When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. 5. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 6. HLRB can now respond to HLRA by sending back a CCBS ack message. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 58 3G TS 23.066 version 3.3.0 Release 1999 B.4.10 Calling Name Presentation Flows – MNP-SRF acts as SCCP Relay Figure B.4.10 shows the MNP-SRF operation for delivering an CNAP message to an ANSI Calling Name Database. Query with Permission (MSISDN) CdPA = MSISDN, TT=5 CgPA = MSCA address Query with Permission ack (Calling Name) CdPA = MSCA address CgPA = CNDB address National Interrogating Network = Subscription Network MNP SRFB MSCA 2 CNDB 4 Query with Permission (MSISDN) CdPA = CNDB address CgPA = MSCA address 1 3 Figure B.4.10: SRF operation for delivering an CNAP message to the CNDB 1. An incoming call ( an Initial Address message with Generic Name parameter set to “presentation allowed” is received at a MSC. The MSC inteerogates the VLR to determine if the called party is subscribed to the CNAP service. The VLR Response indicates that the called party is subscribed to CNAP; 2. The MSC generates a TCAP message ”Query With Permission”. The Query With Permission message is routed to the network’s MNP-SRF; 3. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies which CNDB the MSISDN is populated using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an CNDB address. After modifying the CdPA, the message is routed to CNDB; 4. CNDB responds to the routeing enquiry by sending back a Query With Permission ack with the address of the MSC. The MSC can now deliver the Calling Name to the terminating subscriber . ETSI ETSI TS 123 066 V3.3.0 (2000-06) 59 3G TS 23.066 version 3.3.0 Release 1999 Annex C (normative): MNP Signalling Relay Function - Call Related Signalling C.1 Handling of Call Related Signalling The only call related MAP message affected by MNP is the MAP_ SEND_ROUTING_INFORMATION (SRI) message without OR parameter set sent to the HLR. In a PLMN supporting MNP with direct routeing using signalling relay, all incoming calls and calls originated in the network for which the called party number is within the ranges owned by any network in the portability domain, the gateway MSCs will send an SRI such that it will be handled by the MNP-SRF in that network. In a PLMN supporting MNP with indirect routeing using signalling relay, all incoming calls and calls originating in the network for which the called party number is within the range owned by the network, the gateway MSCs will send SRI such that it will be handled by the MNP-SRF in that network. The MNP-SRF obtains routeing information from the NP database to identify the subscription network associated with a particular national MSISDN. The interface between the MNP-SRF and the NP database is considered implementation dependent and is not detailed further. From the perspective of the PLMN in which the MNP-SRF resides, the CdPA represents one of: 1. An own number ported out. 2. An own number not ported out. 3. A foreign number ported in. 4. A foreign number ported to a foreign network. 5. A foreign number not known to be ported. Cases 4 and 5 are applicable only for direct routeing. In case 1, the MNP-SRF may perform one of the following depending on agreements within the number portability domain. a. An SRI response is sent containing the necessary routeing information to route the call to the subscription network. This is performed by an internal MAP Application Termination Function (MATF) known as the Number Portability Location Register (NPLR). b. If indirect routeing of calls with reference to the subscription network is used, the message is relayed to the MNP-SRF in the subscription network, whose NPLR provides the necessary routeing information in an SRI response. The use of an NPLR in the subscription network can only be by agreement within the number portability domain. In cases 2 and 3, the MNP-SRF relays the message to the HLR. For further details of the signalling relay function, the reader is referred to [7]. In case 4, an SRI response is sent, containing the necessary routeing information to route the call to the subscription network. In case 5, an SRI response is sent, containing the necessary routeing information to route the call to the number range holder network. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 60 3G TS 23.066 version 3.3.0 Release 1999 C.2 Functional Requirements of Network Entities C.2.1 Procedure MNP_SRF_MATF_Call_Related Figure C.2.2.2 shows the procedure MNP_SRF_MATF_Call_Related. This procedure handles call-related signalling messages. It is called from the process MNP_SRF (see clause 4.3). The check “message has been relayed” identifies all call related signalling messages which are relayed from the number range holder network towards the subscription network in the case of Indirect Routeing with reference to subscription network implementation. These messages only refer to numbers ported into the network. The check “own number not ported out” identifies all mobile numbers from number ranges allocated to the network the MNP-SRF/MATF is located in and which are not ported to other networks. In this case the call related message is relayed to the HLR in the network. The check “foreign number ported in” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are served by the network the MNP-SRF/MATF is located in. In this case the call related message is relayed to the HLR in the network. The check “foreign number not known to be ported” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are also not served by the network the MNP-SRF/MATF is located in. In this case the call is sent to the SRF_MATF procedure for handling. The check “foreign number ported to foreign network” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are not served by the network the MNP-SRF is located in and not served by the network the number range is allocated to, i.e. the number is ported between two other networks. In this case the call related message is sent to the SRF_MATF procedure for handling. The remaining cases “own number ported out” are mobile numbers allocated to the network the MNP-SRF/MATF is located in and which are served by other networks, i.e. the number is ported out to another network. In this case the call is relayed to the MATF in the subscription network if this option is the one used by the operator, or sent to the SRF_MATF procedure for handling if not. C.2.2 Process SRI_NPLR Figure C.2.2.2 shows the process SRI_NPLR. The check “unknown subscriber” identifies a subscriber without any associated available information. If the GMSC is in the database own network then a routeing number is provided to route to the number range holder network. If the GMSC is not in the database own network then the enquiry has been routed from the number range holder network, so the call should fail. The database query uses the MSISDN received at the application level in the SRI, rather then the CdPA of the SCCP level. If an error must be set as a result of the check “terminate”, the user error “unknown subscriber” shall be used. If version 3 or higher of the MAP protocol is in use, then the diagnostic “NPDB mismatch” may be used. The check “HPLMN MSISDN Range” identifies if the MSISDN received in the SRI exists in a MSISDN Range owned by the HPLMN. This is a North American Network implementation option and allows a MAP Error “Unknown Subscriber” to be sent to the GMSC instead of the MSISDN. The check “HPLMN RN Range” identifies if the Routeing Number assigned to the MSISDN within the SRI_NPLR is assigned to the HPLMN. This is a North American Network implementation option and allows a MAP Error “Unknown Subscriber” to be sent to the GMSC instead of the RN+MSISDN. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 61 3G TS 23.066 version 3.3.0 Release 1999 Procedure in the MNP- SRF for call related signalling Procedure MNP_SRF_MATF_Call_Related 1(1) Query Database message has been relayed own number, not ported out foreign number, ported in foreign number, not known to be ported foreign number, ported to other foreign network CdPA := HLR address MATF set: terminate must be own number, ported out OPTION OPTION MATF MATF routeing error SCCP error handling set: terminate CdPA:= RN + MSISDN set: terminate no yes no yes no yes no yes yes no yes no no yes Indirect Routeing with Reference to Subscription Network to Subscription Network Indirect Routeing with Reference Figure C.2.2: Procedure MNP_SRF_MATF_Call_Related ETSI ETSI TS 123 066 V3.3.0 (2000-06) 62 3G TS 23.066 version 3.3.0 Release 1999 Procedure MATF 1(1) perform TCAP handling this includes passing the operation (SRI) to the application Figure C.2.2.1: Procedure MATF ETSI ETSI TS 123 066 V3.3.0 (2000-06) 63 3G TS 23.066 version 3.3.0 Release 1999 no Process in the NPLR to handle an incoming SRI Process SRI_NPLR 1(1) IDLE SRI from MAP process data missing unexpected data Query Database unknown subscriber OPTION omit routeing number pointing to subscription network Set: RN (+MSISDN) Set: MSISDN Set: RN (+MSISDN) pointing to number range owner network Set: error SRI ack to MAP process no yes no yes yes yes yes OPTION Check HPLMN MSISDN RANGE DN in HPLMN MSISDN Range yes yes OPTION Check HPLMN RN RANGE RN in HPLMN RN Ranges yes yes Set: error Unknown Subscriber Foreign number, Ported in no yes yes GSMC in own network MNP_SRF_Check_ MNP_Indicator terminate no no no no no no no Figure C.2.2.2: Process SRI_NPLR ETSI ETSI TS 123 066 V3.3.0 (2000-06) 64 3G TS 23.066 version 3.3.0 Release 1999 C.3 Call Scenarios The notation TT=SRI in diagrams in this section assumes that SRI=CRMNP for ETSI and SRI = Translation Type 14 for ANSI. The use of other translation types is for further study. The message flows for the following scenarios are based on the use of an SCCP relay function in MNP-SRF(s). The message flows for the higher level relay function (e.g. TC relay) in MNP-SRF are not covered here, but the principle can be found in B.4.2. For further details of the signalling relay function, the reader is referred to [7]. C.3.1 Call to a Non-Ported Number or Number Ported into the Network Figure C.3.1 shows the signalling involved for a call to a non-ported number or number ported into the network (see 3G TS 23.018 [3]). MSB IAM (MSRN) SRI (MSISDN) CdPA = MSISDN, TT=SRI CgPA = GMSCB address SRI (MSISDN) CdPA = HLRB address CgPA = GMSCB address SRI ack (MSRN) CdPA = GMSCB address CgPA = HLRB address GMSCB MNP_SRF/ MATF VMSCB HLRB Subscription Network or number range holder Network if non-ported Visited Network Originating Network IAM ((RN+)MSISDN) Originating Exchange 1 2 3 4 5 6 NPDB Figure C.3.1: Call to a non-ported number 1. From an Originating Exchange a call is set up to MSISDN. The call is routed to the subscription network being the number range holder network, if the number is non-ported. 2. When GMSCB receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the MNP_SRF/MATF. The TT on SCCP may be set to ‘SRI’. 3. When the MNP_SRF/MATF receives the message, the MNP_SRF/MATF analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported. The MNP_SRF/MATF function then replaces the CdPA by an HLRB address. After modifying the CdPA, the message is routed to HLRB. 4. When HLRB receives the SRI, it responds to the GMSCB by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. 5. GMSCB uses the MSRN to route the call to VMSCB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 65 3G TS 23.066 version 3.3.0 Release 1999 C.3.2 Call to a Ported Number – Originating Network = Subscription Network – Direct Routeing Figure C.3.2 shows the signalling involved for a call to a ported number via direct routeing where the call is originated in the subscription network. IAM (MSISDN) IAM (MSRN) SRI (MSISDN) CdPA = MSISDN, TT=SRI CgPA = GMSCA address SRI (MSISDN) CdPA = HLRA address CgPA = GMSCA address SRI ack (MSRN) CdPA = GMSCA address CgPA = HLRA address GMSCA MNP_SRF/ MATF HLRA VMSCA MSA Originating Network = Subscription Network 1 3 4 5 6 2 NPDB Figure C.3.2: Call to a ported number via direct routeing where the call is originated in the subscription network 1. MSA originates a call to MSISDN. 2. VMSCA routes the call to the network’s GMSCA. 3. When GMSCA receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the MNP_SRF/MATF. The TT on SCCP may be set to ‘SRI’. 4. When the MNP_SRF/MATF receives the message, it analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network. The MNP_SRF/MATF function then replaces the CdPA by an HLRA address. After modifying the CdPA, the message is routed to HLRA. 5. When HLRA receives the SRI, it responds to the GMSCA by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. 6. GMSCA uses the MSRN to route the call to VMSCB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 66 3G TS 23.066 version 3.3.0 Release 1999 C.3.3 Mobile Originated Call to a Ported or not known to be Ported Number – Originating Network ≠Subscription Network– Direct Routeing Figure C.3.3 shows the signalling involved for a national mobile originated call to a number not Subscribed in the originating network via direct routeing. The scenario describes signalling in the originating network using direct routeing in the cases when an own number is ported out, a foreign number is not known to be ported or a foreign number is ported to other foreign network. IAM (MSISDN) IAM ((RN +) MSISDN) SRI (MSISDN) CdPA = MSISDN, TT=SRI CgPA = GMSCA address SRI ack (RN + MSISDN) CdPA = GMSCA address CgPA = MNP_SRF address GMSCA MNP_SRF/ MATF VMSCA MSA Originating Network 1 2 3 5 4 NPDB Figure C.3.3: National mobile originated call to a ported number via direct routeing 1. MSA originates a call to MSISDN. 2. VMSCA routes the call to the network’s GMSCA. 3. When GMSCA receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the MNP_SRF/MATF. The TT on SCCP may be set to ‘SRI’. 4. When the MNP_SRF/MATF receives the message, it analyses the MSISDN in the CdPA and identifies the MSISDN as not known to be ported or being ported to another network. As the message is a SRI message, the MNP_SRF/MATF responds to the GMSCA by sending an SRI ack with a RN + MSISDN; For the case the number is not known to be ported the routeing number may be omitted. 5. GMSCA uses the (RN +) MSISDN to route the call to GMSCB in the subscription network. Depending on the interconnect agreement, the RN will be added in the IAM or not. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 67 3G TS 23.066 version 3.3.0 Release 1999 C.3.4 Call to a Ported Number – Indirect Routeing Figure C.3.4 shows the signalling involved for a call to a ported number via indirect routeing. Originating Network IAM (MSISDN) IAM ((RN +) MSISDN) SRI (MSISDN) CdPA = MSISDN, TT=SRI CgPA = GMSCA address SRI ack (RN + MSISDN) CdPA = GMSCA address CgPA = MNP_SRF address GMSCA MNP_SRF/ MATF Originating Exchange Number Range Holder Network 1 2 3 4 NPDB Figure C.3.4: Call to a ported number via indirect routeing 1. From an Originating Exchange a call is set up to MSISDN. The call is routed to the number range holder network. 2. When GMSCA in the number range holder network receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to MNP_SRF/MATF. The TT on SCCP may be set to ‘SRI’. 3. When the MNP_SRF/MATF receives the message, it analyses the MSISDN in the CdPA and identifies the MSISDN as being ported to another network. As the message is an SRI message, the MNP_SRF/MATF responds to the GMSCA by sending an SRI ack with a RN + MSISDN. 4. GMSCA uses the RN + MSISDN to route the call to GMSCB in the subscription network. Depending on the interconnect agreement, the RN will be added in the IAM or not. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 68 3G TS 23.066 version 3.3.0 Release 1999 C.3.5 Call to a Ported Number – Indirect Routeing with Reference to Subscription Network Figure C.3.5 shows the signalling involved for a call to a ported number where indirect routeing with reference to the subscription network is used. (Inter) national Originating Network IAM (MSISDN IAM ((RN +) MSISDN) SRI (MSISDN) CdPA = MSISDN, TT=SRI CgPA = GMSCA address SRI (MSISDN) CdPA = RN + MSISDN, TT=SRI CgPA = GMSCA address GMSCA MNP_SRF/ MATF Originating Exchange MNP_SRF/ MATF IAM (MSRN) SRI ack (MSRN) CdPA = GMSCB address CgPA = HLRB address HLRB Number Range Holder Network Subscription Network 1 2 5 6 8 GMSCB 9 3 4 SRI (MSISDN) CdPA = HLRB address CgPA = GMSCB address 7 SRI ack (RN + MSISDN) CdPA = GMSCA address CgPA = MNP_SRF address SRI (MSISDN) CdPA = MSISDN, TT=SRI CgPA = GMSCB address NPDB NPDB Figure C.3.5: National or international originated call to a ported number where indirect routeing with reference to the subscription network is used 1. From an Originating Exchange a call is set up to MSISDN. The call is routed to the number range holder network. 2. When GMSCA in the number range holder network receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the MNP_SRF/MATF. The TT on SCCP may be set to ‘SRI’. 3. When MNP_SRF/MATF receives the message, MNP_SRF/MATF operation is triggered. The MNP_SRF/MATF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported to another network. As the message is a SRI message, the MNP_SRF/MATF function relays the message to the subscription network by adding a routeing number to the CdPA which information may be retrieved from a database. After modifying the CdPA, the message is routed to the subscription network. 4. When MNP_SRF/MATF in the subscription network receives the SRI, it responds to the GMSCA in the number range holder network by sending a SRI ack with a RN + MSISDN. 5. GMSCA uses the (RN +) MSISDN to route the call to GMSCB in the subscription network; Depending on the interconnect agreement, the RN will be added in the IAM or not. 6. When GMSCB in the subscription network receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to MNP_SRF/MATF. The TT on SCCP may be set to ‘SRI’. 7. When MNP_SRF/MATF receives the message, MNP_SRF/MATF operation is triggered. The MNP_SRF/MATF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network. The MNP_SRF/MATF function then replaces the CdPA by an HLRB address which information may be retrieved from a database. After modifying the CdPA, the message is routed to HLRB. 8. When HLRB receives the SRI, it responds to the GMSCB by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. 9. GMSCB uses the MSRN to route the call to VMSCB. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 69 3G TS 23.066 version 3.3.0 Release 1999 NOTE: The MNP_SRF/MATF in this scenario has only information about all ported numbers to one subscription network, except those for which subscription information is held in the subscription networks HLR. In this scenario the routeing depends always on the number range holder and the subscription network. C.4 Information Flows Figure C.4.1 shows the information flow for a successful delivery of a call to a non-ported number or number ported into the network. The figure is related to figure C.3.1. Subscription Network Visited Network IAM ((RN+ )MSISDN) IAM (MSRN) SRI (MSISDN) CdPA = MSISDN, TT=SRI GMSCB MNP_SRFB/MATF HLRB VMSCB SRI (MSISDN) CdPA = HLRB address SRI ack (MSRN) PRN PRN ack (MSRN) Originating Network Figure C.4.1: Successful delivery of a call to a non-ported subscriber or number ported into the network ETSI ETSI TS 123 066 V3.3.0 (2000-06) 70 3G TS 23.066 version 3.3.0 Release 1999 Figure C.4.2 shows the signalling involved for a call to a ported number via direct routeing where the call is originated in the subscription network. The figure is related to figure C.3.2. National Originating Network = Subscription Network Visited Network IAM (MSISDN) IAM (MSRN) SRI (MSISDN) CdPA = MSISDN, TT=SRI VMSCA GMSCA MNP_SRFA/MATF HLRA VMSCB SRI (MSISDN) CdPA = HLRA address SRI ack (MSRN) PRN PRN ack (MSRN) Figure C.4.2: Successful delivery of a call to a ported number via direct routeing where the call is originated in the subscription network ETSI ETSI TS 123 066 V3.3.0 (2000-06) 71 3G TS 23.066 version 3.3.0 Release 1999 Figure C.4.3 shows the signalling involved for a national mobile originated call to a ported number via direct routeing. The figure is related to figure C.3.3. National Originating Network Visited Network Subscription Network IAM (MSISDN) IAM (MSRN) SRI (MSISDN) CdPA = MSISDN, TT=SRI IAM ((RN +) MSISDN) GMSCA MNP_SRFA/MATF GMSCB MNP_SRFB/MATF HLRB VMSCB SRI (MSISDN) CdPA = MSISDN, TT=SRI SRI (MSISDN) CdPA = HLRB address SRI ack (RN + MSISDN) SRI ack (MSRN) PRN PRN ack (MSRN) Figure C.4.3: Successful delivery of a national mobile originated call to a ported number via direct routeing ETSI ETSI TS 123 066 V3.3.0 (2000-06) 72 3G TS 23.066 version 3.3.0 Release 1999 Figure C.4.4 shows the signalling involved for a national mobile originated call to a not known to be ported number via direct routeing. The figure is related to figure C.3.3. National Originating Network Visited Network Number Range Holder Network IAM (MSISDN) IAM (MSRN) SRI (MSISDN) CdPA = MSISDN, TT=SRI IAM ((RN +) MSISDN) GMSCA MNP_SRFA/MATF GMSCB MNP_SRFB/MATF HLRB VMSCB SRI (MSISDN) CdPA = MSISDN, TT=SRI SRI (MSISDN) CdPA = HLRB address SRI ack ((RN +) MSISDN) SRI ack (MSRN) PRN PRN ack (MSRN) Figure C.4.4: Successful delivery of a national mobile originated call to a not known to be ported number via direct routeing Figure C.4.5 shows the signalling involved for a call to a ported number via indirect routeing. The figure is related to figure C.3.4. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 73 3G TS 23.066 version 3.3.0 Release 1999 Visited Network Subscription Network IAM(MSISDN) IAM (MSRN) SRI (MSISDN) CdPA = MSISDN, TT=SRI IAM ((RN +) MSISDN) GMSCA MNP_SRFA/MATF GMSCB MNP_SRFB/MATF HLRB VMSCB SRI (MSISDN) CdPA = MSISDN, TT=SRI SRI (MSISDN) CdPA = HLRB address SRI ack (RN + MSISDN) SRI ack (MSRN) PRN PRN ack (MSRN) Originating Network Number Range Holder Network Figure C.4.5: Successful delivery of a call to a ported number via indirect routeing ETSI ETSI TS 123 066 V3.3.0 (2000-06) 74 3G TS 23.066 version 3.3.0 Release 1999 Figure C.4.6 shows the signalling involved for a call to a ported number where indirect routeing with reference to the subscription network is used. The figure is related to figure C.3.5. Number Range Holder Network Visited Network Subscription Network IAM (MSISDN ) IAM (MSRN) SRI (MSISDN) CdPA = MSISDN, TT=SRI IAM ((RN +) MSISDN) GMSCA MNP_SRFA/MATF GMSCB MNP_SRFB/MATF HLRB VMSCB SRI (MSISDN) CdPA = RN + MSISDN, TT=SRI SRI (MSISDN) CdPA = MSISDN, TT=SRI SRI (MSISDN) CdPA = HLRB address SRI ack (RN + MSISDN) SRI ack (MSRN) PRN PRN ack (MSRN) Figure C.4.6: Successful delivery for a call to a ported number where indirect routeing with reference to the subscription network is used ETSI ETSI TS 123 066 V3.3.0 (2000-06) 75 3G TS 23.066 version 3.3.0 Release 1999 C.5 Contents of the messages This clause contains detailed description of the messages shown in this part B of the specification. C.5.1 Send Routeing Info The contents of this message are specified in 3G TS 23.018 [3]. C.5.2 Send Routeing Info ack The contents of this message are specified in 3G TS 23.018 [3]. In the case that the message is sent from the NPLR to the GMSC, the following MNP specific information is defined: Information element name Required Description Imsi M The IMSI returned by an NPLR is a generic IMSI, i.e. it is not tied necessarily to the Subscriber. MCC and MNC values in this IMSI shall point to the Subscription Network of the B Subscriber Msrn C When returned from the NPLR, this parameter contains a Routeing Number that points to Subscription Network. If concatenate addressing is used, it also contains the MSISDN in addition to the Routeing Number.In the case of a number which is not known to be ported, the Routeing Number may be omitted as an operator option. If the routeing number is omitted, this parameter contains only the MSISDN. Msisdn C MSISDN of the B subscriber. This information element shall be present if MSRN contains the routeing number to reach the subscription network for B subscriber and the MSISDN is not contained in the MSRN information element. MNP Indicator U Indicates the number portability status of the subscriber. C.6 Handling of MAP to ISUP mapping (informative) Different configurations can be possible within a portability domain depending on the versions of MAP and ISUP protocols being used. The following sections describe possible interworking scenarios. C.6.1 ETSI Mapping direction: ISUP to MAP The GMSC always constructs the Send Routeing Info message using the MSISDN. If the incoming IAM corresponds to a ported number the GMSC shall retrieve the MSISDN from the corresponding parameter in the IAM. C.6.2 ETSI Mapping direction: MAP to ISUP In MAP SRIack messages from NPLR, MAP versions 1 and 2 only support concatenate addressing for MNP. If MSISDN parameter is present in the SRIack, this means that separate addressing is used in MAP; this is only possible if MAP version 3 is used. MAP version 3 can also support concatenate addressing. In all cases, when a Routeing Number is returned, it is included in the MSRN parameter of the SRIack. Regardless of how MAP is established, the possible mappings of the parameters in ISUP IAM message is one of these 4 options (see also [6]): 1. CdPN parameter includes only the MSISDN. 2. CdPN parameter includes both RN and MSISDN concatenated. 3. CdPN parameter includes the MSISDN and NRN parameter includes the Routeing Number. 4. CdPN parameter includes the Routeing Number and CDN parameter includes the MSISDN. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 76 3G TS 23.066 version 3.3.0 Release 1999 In all cases, the method to transport the routeing number in the IAM depends on the interfaces agreed by the operators in the portability domain. C.6.3 ANSI Mapping direction: ISUP to MAP The GMSC always constructs the Send Routeing Info message using the MSISDN. If the incoming IAM corresponds to a ported number the GMSC shall retrieve the MSISDN from the corresponding parameter in the IAM. The IAM message is specified for ANSI ISUP implementation in [8] and [9]. C.6.4 ANSI Mapping direction: MAP to ISUP In MAP SRIack messages from NPLR, MAP versions 1 and 2 only support concatenate addressing for MNP. If MSISDN parameter is present in the SRI Ack, this means that separate addressing is used in MAP; this is only possible if MAP version 3 is used. MAP version 3 can also support concatenate addressing. In all cases, when a Routeing Number is returned, it is included in the MSRN parameter of the SRI Ack. Regardless of how MAP is established, the possible mappings of the parameters in ISUP IAM message is one of these 4 options (see also [8] and [9]): MAP Parameters SRI Ack ISUP Parameters IAM IMSI Subscriber IMSI CdPN MSRN MSRN MSRN MAPS TO GAP N/A MSISDN Not Present FCI Bit M Indicator 1 MNP Indicator Not Present MAP Parameters SRI Ack ISUP Parameters IAM IMSI Default IMSI CdPN Dialled DN MSRN Dialled DN MAPS TO GAP N/A MSISDN Not Present FCI Bit M Indicator 1 MNP Indicator NotKnownToBePorted MAP Parameters SRI Ack ISUP Parameters IAM IMSI Default IMSI CdPN RN MSRN RN MAPS TO GAP Dialled DN MSISDN Dialled DN FCI Bit M Indicator 1 MNP Indicator OwnNumber PortedOut MAP Parameters SRI Ack ISUP Parameters IAM IMSI Default IMSI CdPN RN MSRN RN MAPS TO GAP Dialled DN MSISDN Dialled DN FCI Bit M Indicator 1 MNP Indicator Foreign Number PortedToForeign Network In all cases, the method to transport the routing number in the IAM depends on the interfaces agreed by the operators in the portability domain. ETSI ETSI TS 123 066 V3.3.0 (2000-06) 77 3G TS 23.066 version 3.3.0 Release 1999 Annex D (informative): Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment #03 GSM 03.66 7.1.0 Transferred to 3GPP CN2 Aug 1999 23.066 3.0.0 #05 Oct 1999 23.066 3.0.0 001 3.1.0 Harmonisation of terminology interrogating #05 Oct 1999 23.066 3.0.0 002 3.1.0 Proposed changes to B.4.2 Delivery of SMS to a Non-ported Number - Direct Routeing – MNP- SRF acts as Higher-level Relay #05 Oct 1999 23.066 3.0.0 003 3.1.0 Clarification of NPLR functionality in not known to be ported case #07 Mar 2000 23.066 3.1.0 007r1 R99 3.2.0 Editorial cleanup #07 Mar 2000 23.066 3.1.0 008r4 R99 3.2.0 Alignment of IN interface with Fixed Networks #07 Mar 2000 23.066 3.1.0 009r3 R99 3.2.0 Detection of database synchronisation errors in SRF #07 Mar 2000 23.066 3.1.0 012r2 R99 3.2.0 Result of Public Enquiry 9953 #07 Mar 2000 23.066 3.1.0 015r1 R99 3.2.0 Clarification of NPDB error detection and MNP specific call handling #08 Jun 2000 23.066 3.2.0 019r2 R99 3.3.0 North American Service Provider Number Portability impacts for Mobile Number Portability 78 ETSI ETSI TS 123 066 V3.3.0 (2000-06) 3G TS 23.066 version 3.3.0 Release 1999 History Document history V3.1.0 January 2000 Publication V3.2.0 March 2000 Publication V3.3.0 June 2000 Publication
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
1 Scope
|
........................................................................................................................................................8
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
2 References
|
................................................................................................................................................8
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
2.1 Normative references
|
......................................................................................................................................... 8
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
2.2 Informative references
|
....................................................................................................................................... 8
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
3 Abbreviations
|
...........................................................................................................................................8
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
4 Algorithms
|
...............................................................................................................................................9
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
4.1 Huffman Coding
|
................................................................................................................................................ 9
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
4.2 Character Groups
|
............................................................................................................................................. 10
|
cf071c2eff78867b5741fcef1deef41e
|
123 042
|
4.3 UCS2
|
............................................................................................................................................................... 11
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.